yashsingh1/xdaforums huggingface dataset:
[Sprint HTC One (M7)] winsettr:
You have to be rooted (obviously) and have fastboot installed on your PC (which you probably have if you have adb installed). Boot into bootloader/fastboot; the command is "fastboot flash recovery *recoveryfilename*.img"
[Sprint HTC One (M7)] Brandon8276:
Subject:Watch "How to Root the HTC One (Internat, https://www.youtube.com/watch?v=rRkAHw_GmIs&feature=youtube_gdata_player
[Sprint HTC One (M7)] androidforeve:
Great thanks for the help
[Sprint HTC One (M7)] systemshock869:
Any chance of us getting a newer version of this recovery? It's definitely the best recovery for our device, but USB OTG support is BROKEN. PLEASE FIX!!!! this is a major problem, and it is sad that the best recovery we have is plagued with it. I don't want to sound unappreciative or anything, I know the devs don't have our phone, but when an older version had this function and they break it, then never fix it, hundreds or even thousands of people are being affected! Thanks for your work devs, please help us out!
[Sprint HTC One (M7)] Brandon8276:
You can always use clockwork if it's bothering you that much. Or better yet an older version of twrp.
[Sprint HTC One (M7)] drlzanej:
Agreed, Im useing 2.5 with no issues. Youll have to downgrade your tp firmware and youre good.

Just because somethings newer doesnt mean its better.
[Sprint HTC One (M7)] elvisypi:
[MENTION=4988866]tdhite[/MENTION] Any progress mate? Can I help you with anything?
[Sprint HTC One (M7)] tdhite:
It's ok. I went down the path of building with CM 11 as the base. Had to back off due to some issues as it didn't work quite yet. That was probably too aggressive an approach for first builds. Live and learn. Going back to basing on CM 10.2 so building that this weekend. Then I'll upgrade once I get a stable build. That should cover things.

You probably also noticed I've been working with PhilZ trying to fix the screen blank there too (only manifests itself on toggle, but the issue is the same here so trying to nail that one both places).

One thing that would be interesting is if you could link me the 2.6.3.x repos you were referencing in your earlier post regarding changes.
[Sprint HTC One (M7)] elvisypi:
Yes I saw Phil is trying to fix it. I can give you the link to the github commits https://github.com/TeamWin/Team-Win-Recovery-Project/

I thought only the partition sizes were different from the M7, but I see we also have different touch drivers. http://xdaforums.com/showthread.php?t=2236254 the partition table

I am new to this stuff really, so sorry if that's not what you wnated, but I wanted to make myself useful. I can test smth if you need. Thanks for your effort I really appreciate it
[Sprint HTC One (M7)] tdhite:
No worries -- I have the github general sources. I thought you might have been looking at a specific fork on the 2.6.3.3 comments.

Anyway -- I'm dropping the device info here as well for future reference: https://github.com/CyanogenMod/android_device_htc_m7spr

There are new commits that take the board info to CM 11, bit like I said, going back a rev to get at least a working build.
[Sprint HTC One (M7)] elvisypi:
Thanks. Actually the latest version is 2.6.3.4, although on twrp website they are on .3. The verizon HTC one is on 2.6.3.4 too. Maybe it would be easier to look at it's commits than m7? http://xdaforums.com/showthread.php?t=2416431

2.6.3.3 seems to have a charging bug
[Sprint HTC One (M7)] tdhite:
Wanted to throw out an update so we know where things are:

I have dual builds going -- one based on CM11, one on CM10.2. First I'm making sure the builds produce valid CWM 6 recoveries (this takes a bit, so hang in). Once that's good to go, I'm actually going to go with the 2.7 TWRP sources and fix 'em up as necessary (if possible). I sent a post to the OP here because I cannot find, for the life of me, his original source commits. While not absolute necessity, it'd be nice to have to compare/contrast with the 2.7 mods I'll ultimately make.

Anyway -- this could take a week to stabilize -- I'm working on it, I promise -- I've just not yet delved into recovery builds as a full delivery to folks. Want to be extremely careful and just getting to build the entire sets took a bit to get used to. Not too bad -- just a lot of trial/error up front. Builds work now, though, so I can much both versions simultaneously.

The good thing is, while Sprint is not an officially supported TWRP build yet, it *is* officially in the CM tree, so we're starting from a good base.
[Sprint HTC One (M7)] elvisypi:
Great! Take your time, we are in no hurry. The latest commits from Deed-Troy are these https://github.com/TeamWin/Team-Win-Recovery-Project/commit/d63c7643fd7749de1723ce1adc5907fed1c1a11c
[Sprint HTC One (M7)] pmacevad:
OT

Glad to see there is some development going on here. Thank you.

/OT

Sent from my rooted & s-off'd Sprint HTC One, powered by Android OS ?
[Sprint HTC One (M7)] Kraizk:
Your best bet to get a hold of anyone for TWRP is to join the #twrp channel of IRC. Chances are they have a TWRP post up for every modern device so they've said they do not monitor their XDA posts in most cases.
[Sprint HTC One (M7)] SuperiorEVOlution18:
Agreed! Seems the TWRP TEAM isn't getting it done....

Sent from my HTCONE
[Sprint HTC One (M7)] tdhite:
They don't promise updates, and it is open source, after all. We got a good start from the 2.6.3 update and i think we can take care of our phones, just will take a little work. For all the great stuff I am privileged to use from guys like [MENTION=4457281]hawknest[/MENTION], [MENTION=506238]O.M.J[/MENTION], [MENTION=4684315]flar2[/MENTION] and others, it's the least I can add is my elbow grease here. In the mean time, I trust PhilZ.
[Sprint HTC One (M7)] tdhite:
Just another update -- progress. Have stable CM11 and CWM builds now (actually setup my own Jenkins server to take care of constant updates).

Also built down a TWRP image -- who knows if it works (seriously). That's progress, though. I have a Q in to some recovery geniuses to assure how to debug a recovery without bricking the device (S-OFF obviously gives lots of room for bad scenarios).

Anyway -- got 'er building, now have to fix. Alas -- working through a USB PhilZ issue with the author there gave me some pretty good insight (I think). Also have to add to the makefiles some repacking -- want to go with stock kernel, not the CWM kernel, if possible. So just an update. Took a solid day of work (since early AM) to get where I am, that's just a day. That means I have another day tomorrow! hack hack hack (but good hacks, not cowboy hacks).
[Sprint HTC One (M7)] systemshock869:
You're doing the lords work!
[Sprint HTC One (M7)] tdhite:
She Boots!!

Alas, she dies in boot loop -- my fault, some broken mount specs and similar -- took a few secs to figure that out -- have to catch the recovery log before it loops, LOL. Not that it's the last issue, but we're getting close. I think tomorrow we can get some test builds. [MENTION=2610120]avwheeler[/MENTION] graciously offered to test so give him some props -- always spooky when you mucking in the guts of things, particularly the recovery because that *has* to work.
[Sprint HTC One (M7)] systemshock869:
Awesome news! I could test as well but I don't know how helpful my feedback would be. haha

Maybe OP would update the thread once you get it working. I am excite!
[Sprint HTC One (M7)] tdhite:
If someone has a Sprint One that is S-On and locked bootloader, and also understand the risks of testing alpha recoveries, and is willing to test the latest TWRP build, please PM me. I want to see how it goes on such a device. I will explain how you boot it without flashing.
[Sprint HTC One (M7)] elvisypi:
Is it too risky for s-off? I can lock bootloader, but s-on is too much a hassle

---------- Post added at 11:40 PM ---------- Previous post was at 11:37 PM ----------

BTW congrats for getting it to boot. I think the most of the work is done, right?
[Sprint HTC One (M7)] tdhite:
Nah -- it should not be all that dangerous in either case, you don't flash this, rather boot it via fastboot boot recovery.img and it just mounts things read/write. Since we are mounting some partitions in rw, just wanted to see how life went for those s-on.

As for the work -- yes, the vast majority is out of the way. Builds now are quite easy as are fixes where needed. I'm considering kernels at the moment -- whether to use stock or go ahead with the CM built kernel. I'll commit everything to github soon. I also took a slightly more flexible path in terms of setting up the Android build. If you study what's really going on in the Android build tree, turns we can isolate all the custom stuff for our phone in a single place and leave the entirety of the CM11 or CM10.2 build process completely untouched -- makes for far easier work when someone wants to build their own copy of this version.

I'll get out a broadly available test version very shortly (meaning, only days now, not weeks.
[Sprint HTC One (M7)] elvisypi:
Looking forward to testing it than:good:
[Sprint HTC One (M7)] budeone:
Looks like you are making great progress
[Sprint HTC One (M7)] tdhite:
Drag folks -- after testing remote booting recover images with [MENTION=2610120]avwheeler[/MENTION] -- turns out HTC rigged us out of the deal (intentionally or negligently is unclear).

I was hoping to have everyone test *without* flashing (I flash because there was no real other way to debug anything). Alas -- HTC removed the ability to run "fastboot boot <whatever.img>" starting at hboot 1.54, so we're screwed for the safest possible testing. Avwheeler tried for me and just got a hung phone -- required a hard reset. I couldn't figure out why I can boot, but he cannot, so looked into hboot -- presto: http://xdaforums.com/showpost.php?p=43690808&postcount=2.

I'll just have to put up builds and for those brave souls ready to fight the war -- you'll have to flash all test recoveries and boot into them from the phone. Frickin!
[Sprint HTC One (M7)] jskup:
If you are open to using a modified hboot, I have had no difficulty using the Rumrunner version on my Sprint HTC One:

http://rumrunner.us/hboots/

They specifically state that all flash commands should be valid.
[Sprint HTC One (M7)] tdhite:
Yes, looked at loading it, but flash is not the problem, the boot command is what we want. Nothing states the custom hboots fixed up the kernel tags setup to support proper remote image boot. I'm asking the authors about that.

I put up a couple builds and will publish info later this week once I see a few of us get things booted. [MENTION=4457281]hawknest[/MENTION] and [MENTION=2610120]avwheeler[/MENTION] signed up to help out as guinea pigs, so we have great people in the trenches.

I put the build device tree on my github account with our own branch so we never have to hunt things down in the future. Honestly info digging was the worst part of getting builds working at all. I'll add the correct roomservice.xml file as well (for those wondering, that is the file in an Android build that let's you do surgery to the build tree).

When we are done, we will have branches for CM11 and CM10.2 that will build for anyone setting up an Android build. There are differences in how the updater asserts work between 4.3 and 4.4 Android builds, which is why there end up Kitkat only recoveries.
[Sprint HTC One (M7)] tdhite:
Good news folks -- no longer overly spooked about folks trying out test versions on the device (after flash). There's always risk, but everyone already knows the standard "you brick it it ain't my issue or liability" risk we deal with every day flashing roms, kernels and firmwares.

The builds are now flashable and boot every time on the device and come all the way up. [MENTION=2610120]avwheeler[/MENTION] and I worked through a bug (in the very weeeeee hours) this morning, I think I nailed it but we have to wait for a build later today (takes hours as I had to 'make clobber' the whole cm11 build and start it all compiling again from scratch, sigh -- I build all of Android to assure everything is correct for the recovery build even though it's just a subset of the build -- better safe then sorry imho).

Anyway -- our shiny new TWRP booted on multiple devices, only a graphics smear bug keeps it from going up for wider testing (current thinking).
[Sprint HTC One (M7)] Cj719:
Sounds great
[Sprint HTC One (M7)] adamlee011:
Hello all. I recently updated to 2.6.3 on my sprint htc one. Sometimes I'll reboot to recovery and the screen will be off. If i tap it and hit power a couple times and wait, sometimes it comes on after a few sec. Sometimes it doesn't and i have to hold power until it restarts. Sometimes this happens between batch flashes or at the end of a restore. Any idea what could be going on here? Any similar experiences?
[Sprint HTC One (M7)] mrshades812:
Turn off screen timeout in recovery. It is one of the MANY issues with our out-of-date recovery.

Peace.
[Sprint HTC One (M7)] adamlee011:
Oh god am i glad it's that simple. Thanks so much. But it of date? I updated a couple days ago.
[Sprint HTC One (M7)] tdhite:
Ok -- first copy for folks to TEST! Don't start thinking we're all the way there, but it works so far:

First -- the normal rule: You are responsible for whatever you do with this recovery. You agree not to hold me liable for anything that might happen, directly or indirectly by your use of this recovery.

With that said:

Download TWRP recovery nightly build

Download / View MD5 Hash for above build

Those are nightly builds (I'll do them as needed from here on out).

They are the 4.4 (cm11) build of the recovery. It may assert on you and give errors for older (non-updated) ROM updater files. The file manager works, graphics smear bug is gone (well, could depend on another firmware version -- we'll see). BTW -- don't worry that it still says 2.6.3.0 -- I simply haven't updated the VERSION stamp in the code yet. I'll get there when we all decide we like it. If a few folks take a look and let me know what's up with any issue, we'll open a new thread for the new builds.

Let me know what you think. It looks nice on my phone! TWRP always did :).
[Sprint HTC One (M7)] avwheeler:
First of all wanted to put out a big thank you to [MENTION=4988866]tdhite[/MENTION]for taking the time and associated risks to get our recovery current, this is awesome.

Just wanted to report that everything in the TWRP buildappears to be functioning properly.

OTG works perfectly, I just flashed rom from OTG.

There are still functions I have not tested, but mostimportantly all standard features are functional.
[Sprint HTC One (M7)] elvisypi:
Just tested the recoery. So far nearly everything works . Files flash properly, clock and battery % are shown properly. I also tried wipe and backup which work without any problems. Sideload works too. When charging it doesn't show the + sign unless the screen goes off, also after removing the charger the + sign stays on until screen goes off(not sure how it was before). I noticed that the vibration feedback is extremely high and there's no option to turn it off or reduce at least. Screen timeout works great, no more freezes! USB OTG works, tried flashing sth.

Mount function doesn't seem to work, if I try to mount /system, /cache, etc it says "E:Unable to mount '/cache'

When I try to mount USB-Storage it says E: Unable to locate volume information for USB. Overall I say it's pretty damn good!!! :good::good::good::good:

If I may ask can you please change the splash screen, I find it terribly ugly, or teach me how to change it myself.

Edit: Found out how to replace the splash screen, pretty simple,use this tool http://xdaforums.com/showthread.php?t=2073775 and unpack the img, replace the curtain.jpg in \Android Image Kitchen\ramdisk\res\images\curtain.jpg

repack
[Sprint HTC One (M7)] tdhite:
For Vibration: go to advanced settings and vibrations are there -- just turn 'em all down to your liking.

For the spash screen -- yea, well, I'm no artist, but if anyone has a cool one, I'll include it in the next build. Need 1920x1080, obviously.

For usb mounts -- geeze, didn't even notice the mount usb button -- that's totally unnecessary any more, the USB auto-mounts and the otg-usb option is already in the mounts list. I'll remove that button so it doesn't confuse further.

For the other mounts, hmmmmm, those should work. I'll take a look when I get a chance later this evening. Can you send me your /cache/recovery/last_log file(s) that relate to the attempts to mount cache and /system -- hopefully they'll clue me in, but if not I'll figure it out anyway. Don't post them, at least not without removing your serial number from the file if it shows. PM me if you prefer.
[Sprint HTC One (M7)] elvisypi:
You were right about vibration, the problem was that I was using an old theme which didn't show that option. Sometimes, right after flashing the recovery it can't mount (not just this version), you need to reboot to system first to make it work. Anyway I'm not sure that the mount function works, I'll attach a log.
[Sprint HTC One (M7)] systemshock869:
I think that's a left over function from older devices that let you mount to windows as a disk drive from recovery.
[Sprint HTC One (M7)] YoungCorruptionV2.0:
And its something that should never be left now. I don't get why they would do that
[Sprint HTC One (M7)] KidCarter93:
Ok cool. If it is included, maybe Dees_Troy should add it to the OP so that others are aware of it.
[Sprint HTC One (M7)] Dees_Troy:
Dumlock was developed by me and was originally part of TWRP more than a year ago even before we released 2.1. We include Dumlock on any device that needs it. To me it's a ubiquitous feature of TWRP and I don't feel a strong need to specifically state that a certain build of TWRP has Dumlock or not.
[Sprint HTC One (M7)] acme64:
forgive my ignorance, but shouldn't this post have been put in android general? since this built isn't specific to the one but adding support for it? at the very least it will keep poor viper from having a stroke :D
[Sprint HTC One (M7)] -viperboy-:
It's not my thread, I just try to help out. And it should be here because it has the first build for our device. All TWRP threads belong in Original Development, and so they all are :)
[Sprint HTC One (M7)] NachoB:
MMM-boy
[Sprint HTC One (M7)] robenwzrdhat:
I flashed TWRP on my HTC One - ATT version and it was successful, however, TWRP was unable to mount /data or /sdcard. Consequently, it was unable to root when I went into system - reboot, and I could not root it via flashing a .zip on my sdcard either.

I tried to install manually first, then flashed via goo manager, then tried manually again - each time the same v2.5.0.0 (was just hopeful :D ).

If you have the ATT version, I recommend CWM no touch, as it worked for me. Looking forward to TWRP working on the ATT brand soon!

Thanks!
[Sprint HTC One (M7)] erikivy:
I can't seem to get beyond the bold item above. Instead of rebooting into TWRP, I see the splash screen with the "entering recovery..." message and after about 15 seconds, end up with a black screen. It takes a hard reset to get out of it from that point. I've downloaded three times, flashed manually 4 times (all with no errors or issues) and even tried installing via GOO Manager, all with the exact same results.

I had no problems unlocking the bootloader and have been tinkering with it for an hour or so now trying to get TWRP installed. Does anyone have any thoughts?

Thanks!
[Sprint HTC One (M7)] Quizo:
im having the same exact issue
[Sprint HTC One (M7)] erikivy:
That's actually comforting. I've been toying with android for a few years now and thought flashing a recovery was pretty easy. I was beginning to think I was missing something really simple. :)

Quizo, Dees helped me in IRC. He uploaded a new file to the download site to correct the issue. Try that one and it should work for you.
[Sprint HTC One (M7)] jmlott:
It took me a few tries, but I finally got it to boot into TWRP. Go through the whole process each time. Also make sure you md5sum the file you downloaded and make sure it didn't get corrupted or something.
[Sprint HTC One (M7)] Dees_Troy:
erikivy joined our IRC channel. I'm not sure why the download was broken (md5's matched and everything) but I deleted the download and recreated it and now it seems fine. Sorry for the troubles.
[Sprint HTC One (M7)] jbradshw:
I was also having problems with getting a working recovery to boot after unlocking.

What worked for me: After installing the recovery, I chose "Power Down" off the Bootloader menu. I then turned the power back on, let it boot up to Android normally. I then rebooted into Recovery and it finally worked.
[Sprint HTC One (M7)] magnumtripod:
Took me a bit to get this working, only because I had to read between the lines a bit and walk myself through a few things. BUT, I did it and I'm rooted without any issues. Just got my TB installed and ready to tear this phone up!

Thanks Dees_Troy
[Sprint HTC One (M7)] SuperiorEVOlution18:
I'm seeing issues with paid apps installing possibly due to the Root method are any of you experiencing these?
[Sprint HTC One (M7)] youkosnake:
Its the fault of the ROMs. they weren't developed while the dev had a device onhand, so there are bound to be issues. Stock with root works fine.
[Sprint HTC One (M7)] ronniemayo:
:confused: viper had the phone pre release, which is how he was able to build the ROMs...
[Sprint HTC One (M7)] youkosnake:
Lol. I knew that, htc elevate. I don't even know why I said that. but yeah. It has to be the roms, as I'm running absolute stock with root and it works fine.

edit: its late. like two devs here were developing without devices and I didnt sleep much last night.
[Sprint HTC One (M7)] magnumtripod:
I've installed a few paid apps and I'm not having any issues at all.
[Sprint HTC One (M7)] raptoro07:
All the **Tampered** and Red Words on the splash screens are scarry looking huh? Guess they try to make you worried about rooting and installing custome recoveries. :)
[Sprint HTC One (M7)] OMJ:
thx for the recovery TW!

Am I missing something or is mounting the storage not working?
[Sprint HTC One (M7)] systemshock869:
Maybe they still port this to older phones? Philz has it too
[Sprint HTC One (M7)] elvisypi:
Spash screen

http://postimg.org/image/om3mzr1gv/