yashsingh1/xdaforums huggingface dataset:
[One (M8) Original Android Development] Forsaked:
[MENTION=1162986]Captain_Throwback[/MENTION]:

Im using your TWRP 2.8.9.0 which is pretty fast, about 1/3 faster then the offical 2.8.7.0.

The only thing i noticed since im using it (done around 30 backups then) is a relativ big battery drop while backup.

For a backup which only needs 168 seconds i drop down from 100% to 90-85% while the charger (18W) is plugged in, while 2.8.7.0 drains only 4% for a backup which takes around 260 seconds.

Is this just a visual battery stats bug or did the changes in your version which let the backup process run on lightspeed, drain this much?
[One (M8) Original Android Development] Captain_Throwback:
I can honestly say I have no idea. I don't even know why backups are faster all of a sudden, or why battery appears to be draining faster, because I didn't actually change anything between the two :confused:.
[One (M8) Original Android Development] fyarf:
Good show, I like the honesty. Maybe TWRP source updated some things that made it faster, and your most recent builds include those?
[One (M8) Original Android Development] Captain_Throwback:
Quite possible. The updated code since the Marshmallow merge would likely account for the better efficiency for the backup/restore process. I did update the kernel as well, but I didn't change anything related to battery - just added f2fs encryption support and updated that code.
[One (M8) Original Android Development] TheNewNEXUS:
Is the 3.0 build released for the htc one m8?

EDIT: Officially... I tried looking in the site and it wasn't there ;(
[One (M8) Original Android Development] dragontology:
It isn't released for just about anything. XDA's news portal jumped the gun saying it was available for all supported devices. I think TeamWin only supports Nexus devices anyway, or at least a small subset of Android devices. Captain is the maintainer for the m8.

I know 2.8.9.0 is on its way (and there are betas that are mostly good according to people who have tried it). I was wondering if it would just get called 3.0.0-0 (from the screenshots, the last zero is separated by a dash, not a dot) or if the 3.x code is different. Probably is. Who knows. But 2.8.7.0 works for Marshmallow ROMs, and the M8 will most likely never see an official update past Marshmallow (or possibly Lollipop on Verizon — looks like the official release is up in the air) so it doesn't matter too much, at least for compatibility.
[One (M8) Original Android Development] _that:
The news article in twrp.me was published at the same time when builds were started. Downloads for those devices where the build worked should appear in the next few hours.

When I looked at the build server status shortly after the web page update, there were ~250 devices in the queue. Yes, that is a small subset of Android devices, but vastly more than only Nexus devices. However it's true that we don't have a maintainer for most of them.

2.8.9 is not an official release, but it's close to 3.0. There were a few fixes and additions between that and 3.0.
[One (M8) Original Android Development] jaydubbs:
Official Marshmallow for Verizon is most certainly on it's way ?
[One (M8) Original Android Development] Forsaked:
TWRP 3.0.0.0 for the M8 is up and can be found here!
[One (M8) Original Android Development] fyarf:
v3.0.0.0 flashed, will report any bugs/errors as I encounter them. Thanks [MENTION=1162986]Captain_Throwback[/MENTION]
[One (M8) Original Android Development] MJPollard:
Glad to see that TWRP 3 is out. However, I'm going to wait on flashing it, for two reasons: (1) I prefer to let the inevitable bugs after a major new release shake themselves out first, and (2) the TWRP Materialized theme has yet to be updated for it, and I simply refuse to use TWRP without it. ;) (I don't have a choice on my Nexus 10, alas, as there are no landscape TWRP Materialized themes for it [landscape themes are scarcer than an honest politician, in fact]. Fortunately, @z31s1g had released a beta of the new TWRP default theme some time back, which is what I'm currently using on it.)
[One (M8) Original Android Development] old.splatterhand:
[MENTION=1162986]Captain_Throwback[/MENTION]

Wanna say thank you for your work doing for our community :good:

And again, thank you, for listening to folks, like us. Not always easy i think...;):D

A nice feature, are language settings.

Nevertheless i ha a little misalignment caused by setting the language to german:

The " Partition SD Card" text is a little bit out of the button.

I wonderif its, possible to grab the text in two lines or something like that?
[One (M8) Original Android Development] mrrocketdog:
glad to see that [MENTION=4258784]MJPollard[/MENTION] is out.:thumbup:

"err on the side of kindness"

---------- Post added at 09:44 PM ---------- Previous post was at 09:31 PM ----------

[MENTION=1162986]Captain_Throwback[/MENTION] , me again. :) just made a backup with the blazingly fast v.3.0 and unfortunately same error as with 2.9. everything good. no problem with phone or restoring backup or anything. guess is just my setup. attached log anyway.

thanks for sharing your work.

https://www.dropbox.com/sh/x9fjif0l8ris2o9/AAA8Yt4gX8lqymSCW7lbudvDa?dl=0

"err on the side of kindness"
[One (M8) Original Android Development] dragontology:
It's in testing. Which means if it fails the test, they go back to the drawing board. And at this point, coming up on 2 years since it's been out, that might not be so much a performance issue as a business decision. And HTC is suffering. They need M8 users to buy M10s. I've seen this happen before. And you say, "But Sprint has it! The International M8 has it!" Again, business decision. Motorola updated the Bionic in 2012, but the Photon and Electrify, both a generation newer, never got a single update. That update was in testing, too. And it "failed." Even though the less powerful Bionic got the update. How is a more powerful phone not able to run an update satisfactorily, but a lesser one is? Business decision.
[One (M8) Original Android Development] jaydubbs:
All true and fair points.

Perhaps I'm testing right now.

Perhaps not.
[One (M8) Original Android Development] _that:
Currently not possible, unfortunately. German simply sucks. ;)
[One (M8) Original Android Development] old.splatterhand:
I guess i stick to english anyway, cause i'm used to :cool:

Thanks anyway for the fast answer.
[One (M8) Original Android Development] morr22066:
TWRP Material Themes

I am leaning the same way, I really enjoy the material themes for TWRP as well as the new splash screens and I'm not sure if I want to go back to the 'stock' TWRP theme again if I don't have to...

I do hope the material themes get updated quickly. Even better would be if TWRP were to update the 'stock' theme and decide to use a material theme. ;)
[One (M8) Original Android Development] MJPollard:
While acknowledging the great work that [MENTION=4878287]_that[/MENTION], [MENTION=1162986]Captain_Throwback[/MENTION], and others are doing keeping TWRP going, I nevertheless also believe that its dated UI is due for a complete redesign, rather than just warm over the current layout (mad props to [MENTION=2719389]z31s1g[/MENTION] for doing so), but as long as it works -- and as long as we have great themes like Materialized -- I'm not going to sweat it. :)
[One (M8) Original Android Development] z31s1g:
The new stock theme bests materialised in efficiency. Its itsybitsytiny small in file size, which is a requirement on a lot of devices with small recovery partitions. Materialised is humongous in comparison.

And the looks were chosen on purpose, as there are quite a few users out there that dislike materialised. And they should not be alienated by the reworked ui they have to use.

Materialised will become a lot like the stock ui in terms of "under the hood changes". I do not intend to change the look.
[One (M8) Original Android Development] MJPollard:
Can't say I agree with that -- progress isn't achieved by clinging to antiquity, and Android users have adapted to its many UI changes that have been forced on them over the years (and there are people who will grumble and yell at the clouds no matter what) -- but that's just my opinion, and no disrespect intended to you or the TWRP team.

And rightly so. If TWRP changes can make the Materialized themes more efficient while maintaining the current look and feel, then it's only right to take advantage of them. I'd expect no less, actually. ;)
[One (M8) Original Android Development] _that:
Progress is achieved by keeping good stuff and replacing bad stuff with better stuff. Progress is not achieved by replacing something that works with something that works differently and looks differently. On the contrary, it confuses and alienates users - see the Windows 8 debacle (read https://www.nngroup.com/articles/windows-8-disappointing-usability/ for example).

Let's ignore the cosmetic differences - they are subject to fashion and trends. What real usability advantages does Material bring? What should be changed in the stock theme?
[One (M8) Original Android Development] TheNewNEXUS:
My device keeps saying " Failed to mount 'reserve' (Invalid argument)"

I haven't heard of this in the past.
[One (M8) Original Android Development] Imotep95:
Gonna make new orange/gray theme and translate to my Language in next few days. :good:
[One (M8) Original Android Development] c5satellite2:
If it fails, they do not "go back to the drawing board", they fix the problems they have. They are testing VZW specific features/functions, radio, does it play nice with their network, etc. It is out for carrier testing currently. The chance that it doesn't get MM is next to nil. Yes anything is possible, but all M8 getting MM has already been confirmed.
[One (M8) Original Android Development] morr22066:
Verizon M8

The most recent tweet on Twitter I have seen from Mo Versi of HTC dated February 3rd said that Verizon approval may be a few weeks away and that he was looking towards the end of the month. It looks like it is just Verizon dragging their feet as usual...
[One (M8) Original Android Development] mrrocketdog:
[MENTION=1162986]Captain_Throwback[/MENTION] , happy to report that previous error "/failed to mount carrier/ (invalid argument)" (post #1359) is no longer appearing. long story short , got into a tight , flashed an ruu , reflashed hboot and reflashed v3.0.0.0. no more error. thank you again for lightening fast twrp and checking log provided earlier.:good:
[One (M8) Original Android Development] dragontology:
Just flashed 3.0.0-0 and it looks absolutely beautiful. Hard to say, but it feels a little faster. Making a Nandroid now, 7496MB. (I miss when they were closer to 2GB. Haha.) 465 seconds.

Wiping — internal storage is fifth after all? I see in the root Wipe menu it says wiping data, cache, and Dalvik is all you will ever need most times. I see that the ROM I'm flashing formatted system before installing. Is that standard? I want to say I remember some ROMs not formatting system, but I could be wrong.

Anyway, good job all around.
[One (M8) Original Android Development] Captain_Throwback:
Yes, that's standard. Most (if not all) custom ROMs will wipe/format /system prior to install.

I'm not the only one who uses this recovery, so even though I'll argue my points and reasons for changing things, it doesn't mean I won't eventually listen in the end ;).
[One (M8) Original Android Development] jkolner:
If you opgrade to TWRP 3.0.0 can you then restor the nandroids you have made with 2.8.7.0?
[One (M8) Original Android Development] thelangosta:
Yes, it worked for me.
[One (M8) Original Android Development] Jakvett:
All is well for me with basic functions. Great work devs, the new design looks nice! I made backups using 2.8.7.0, and restored with TWRP 3 without issue.

As for functionality, I've haven't done much other than what's required to flash ROMs and change time/settings, and no bugs have come up. Backups and restores do seem to be a bit quicker too. Well done!
[One (M8) Original Android Development] remix92:
How can i Flash cm13/aosap based Roms with TWRP 3.0.0? It fails always.. But sense based Roms works fine :)
[One (M8) Original Android Development] dragontology:
You're a good guy, in addition to being a great developer. You weren't exactly wrong. It was a Nexus I screwed up on, so presumably my next phone (Nexus 6P) will have the same issue. I will certainly be paying attention. It's just worse for a Nexus because you don't have the SD card to fall back on. Without an OTG cable or micro USB flash drive (which I have both of), a Nexus with no ROM installed and internal storage wiped is up a certain creek.
[One (M8) Original Android Development] EVOuser94:
For HTC ONE M8 MHWL (SPRINT) and Harmon Kardon Edition (SPRINT)

https://www.dropbox.com/s/jc7pubpvu09tt81/0P6BIMG-2.7.1.0.zip bootloader flashable

https://www.dropbox.com/s/m0r66i3gdpbmbu8/0P6BIMG-2.7.1.0-hk.zip bootloader flashable Harmon/Kardon
[One (M8) Original Android Development] NYCHitman1:
Satisfied now?
[One (M8) Original Android Development] colthekid:
Recovery Backup

Im running TWRP 2.7.1.0 and it doesn't give me the option to backup the recovery, just Boot, System, Cache & Data are the Partitions it allows me to backup.

When I use the TWRP Manager app, the app lets me select the recovery partition, but the recovery log then says "E:Unable to locate '/recovery' partition for backup calculations."

Previous TWRP 2.7.0.2, also the same.

On my previous M7 and EVO 3D, the recovery was part of the Nandroid, has this changed?
[One (M8) Original Android Development] Chrysis:
Apologies if this is a stupid question, but I've searched quite a bit and can't find anything. How do I mount USB storage in recovery? I get a bunch of options of which storage to select, but no button or anything to actually mount it. At least not how I remember it from previous TWRP versions on my One XL. On 2.7.1.0 at the moment, but tried 2.7.0.2 and got the same thing. Any ideas?
[One (M8) Original Android Development] PhoenixMert:
Mount otg?
[One (M8) Original Android Development] old.splatterhand:
This does not exist for M8, because it came with MTP out of the box.

You need adb commands to pull/push files.
[One (M8) Original Android Development] Chrysis:
Got it that makes sense, guess I was just used to how it was with the One X, thanks!
[One (M8) Original Android Development] scottguest11:
i have a problem like that im s-off unlocked and rooted and installed twrp so when i try to do a backup it tells me that it fails due to it cant mount system. went into mounts and tried to do it there still wont work need some help on this please any help would be great
[One (M8) Original Android Development] Tiffany84:
That's one feature I really miss.
[One (M8) Original Android Development] Shudder123:
haven't read through the whole thread yet, but whenever I turn off my phone to charge, it seems to automatically boot into recovery. is there a fix around this glitch? I'm on the latest 2.7.1.0
[One (M8) Original Android Development] MrMarkEdward:
Dont have that problem.
[One (M8) Original Android Development] RedBullet:
problems with 2.7.1.0?

I am running latest (2.7.1.0) and noticed that it didn't properly mount my data partition, so can't do things like backup/restore.

Is this recovery working for folks OK???
[One (M8) Original Android Development] RedBullet:
OK, I tried flashing 2.7.0.2 behaved the same way...

Honestly I had a build that work... Apparently it wasn't an official build??
[One (M8) Original Android Development] Shudder123:
how do I rename backups? I remember seeing an option to do that but can't seem to find it now
[One (M8) Original Android Development] Brooklynsour:
Cool thanks!!
[One (M8) Original Android Development] larapr:
I have been trying to solve a problem that I got with my ext card but no luck everytime I boot to recovery my ext SD card gets erased completely, can't use it unless I format it again, and then same thing keeps happening any ideas? I'm on Stock rooted Rom and TWRP 2.7.1.0 please help :(
[One (M8) Original Android Development] skulldreamz:
Can you elaborate like a lot more and a log would work wonders to help your issue

---------- Post added at 06:29 AM ---------- Previous post was at 06:25 AM ----------

Only way I can see that happening is that you have a script that loads upon recovery that is suppose to wipe because this is a openrecovery meaning it loads scripts on queue
[One (M8) Original Android Development] larapr:
Thanks for your reply, I'll look into it, gonna try to format again to see if that solves it.
[One (M8) Original Android Development] c5satellite2:
Possible fix for missing os version:

http://xdaforums.com/showthread.php?p=53733669

Would be great if this could be fixed in official version.
[One (M8) Original Android Development] old.splatterhand:
[MENTION=912474]Dees_Troy[/MENTION] [MENTION=2638973]bigbiff[/MENTION] [MENTION=1219335]jmz[/MENTION]

Could you guys check that please?
[One (M8) Original Android Development] jsbrigo:
Hi guys,

here is my problem:

M8

Android 5.0.1

Sense 6.0

sw 4.19.707.4

I cannot update TWRP after 2.8.1.0 :(

My phone is S-OFF, rooted and superSU is installed 2.46 (I'd like to update it)

Flashing a new version cannot boot the phone in recovery mode... it fails and bootloader is starting

any idea?

Thanks for helping
[One (M8) Original Android Development] Captain_Throwback:
Update your firmware.
[One (M8) Original Android Development] jsbrigo:
to do that, I should flash a stock recovery... unfortunately I cannot find the right one for my sw :confused:
[One (M8) Original Android Development] mervin989:
Hey there, just get your phone supercid since you are S-off and flash firmware updates via fastboot. No need to flash stock recovery. Realised you might not know what to do, download and update all the firmware incrementally, the latest being on wwe 6.12.401 and not what we have wwe asia 4.xx.707. Do a backup of all the info you currently have using fastboot getvar all, keep it somewhere safe on word/text document. Follow this guide and get super cid: http://xdaforums.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727

Follow this guide: http://xdaforums.com/showthread.php?t=2696282 since it covers all the steps. Download the corresponding version of 401 to your 707 and flash in fastboot. Always flash firmware twice, regardless of it being sucessful or a failure. Flash incremental updates to avoid any problems(maybe its just me, err on the side of caution)

Download your latest firmware x.xx.401 here: http://xdaforums.com/htc-one-m8/development/progress-fuu-m8-t2813792 scroll down to the bottom of the post where it says all downloads fuu and zips. Download the latest zip correspondingly under the nowipe in the excel sheet, follow the guide and then do the no red text hboot mod accordingly if you want to.

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

Hey guys, updated to latest twrp and keep seeing failed to mount carrier message pop out all the time when updating cm13 nightly and somebody solved it. Anybody give me a run down of the issue?
[One (M8) Original Android Development] jkolner:
Downloaded TWRP 3.0.0.1 and flashed it. Downloaded a new TWRP 3 them and everything works with no problems.

Thanks for this.
[One (M8) Original Android Development] fyarf:
Is there a point update? I thought 3.0.0-0 was the latest, but you said you have 3.0.0.1. I have not seen a link and OP doesn't state a changelog entry for it.

Edit: it's on the twrp website. Will try it out and report back.
[One (M8) Original Android Development] jkolner:
Found 3.0.0.1 here: https://dl.twrp.me/m8/

/ Sent from my phone /
[One (M8) Original Android Development] fyarf:
3.0.0-1 seems to be working great. External SD seems to have full support, and all seems good. No bugs thus far. Another good update it seems, [MENTION=1162986]Captain_Throwback[/MENTION]

Edit: OS line in bootloader is still getting wiped. My steps were factory reset, advanced wipe, art cache, cache, system. Upon flashing custom cm13 based rom, bootloader OS is blank. Other than that, seems good.
[One (M8) Original Android Development] Captain_Throwback:
What do you mean, "still"? That was fixed a while ago. I find it interesting that CM13 is the cause of the wipe, though. I've flashed CM13 and didn't notice the OS version being wiped on my device. Are you sure that's the cause?

Also, it seems like you're doing a lot of redundant, unnecessary wiping. Factory reset will wipe art/dalvik cache and cache, so you're essentially wiping that twice. If you're going to use Advanced Wipe, there's really no need to use Factory Reset.

Can you flash a firmware package to restore your OS version, and then boot into recovery and perform only a factory reset? Then reboot to bootloader and confirm whether the OS line is still there? If it is, try doing an Advanced Wipe of Cache, Data & System, and then check the OS line again. If it's still there after both of those actions, the problem is with the CM13 zip itself. If either of the previous actions wipes it, I'll look into it.

I might need to build this recovery with the Marshmallow kernel source. Hopefully we can work out the slow flashing issue, otherwise that's not a viable solution.
[One (M8) Original Android Development] fyarf:
Still as in I have seen this in earlier test builds, but it seems inconsistent. The redundant wipe was to make sure the factory reset didn't reset my cache to exfat, as my data and cache partitions are f2fs.
[One (M8) Original Android Development] Captain_Throwback:
/cache would never be exfat. I think you mean ext4 - but TWRP uses whatever filesystem you have currently to format, and it tells you exactly how it formatted in the console, so the redundancy still doesn't make sense to me :confused:.

At any rate, without any additional testing/feedback, there's nothing I can do for you. So hopefully you can perform that testing soon.

Is anyone else seeing a blank OS version in bootloader after flashing the latest version?
[One (M8) Original Android Development] fyarf:
True, I just double check everything. I'll test and get back to you.

---------- Post added at 01:36 PM ---------- Previous post was at 01:07 PM ----------

[MENTION=1162986]Captain_Throwback[/MENTION] I flashed a no wipe firmware zip, then reflashed twrp 3.0.0-1 and now get invalid carrier argument. US dev edition unlocked model. I saw a post earlier in this thread that they fixed it by flashing the full RUU. Are there any other workaround besides the RUU to fix this message?
[One (M8) Original Android Development] fyarf:
Just did a factory reset only after flashing firmware, and OS line in bootloader is blank.
[One (M8) Original Android Development] Captain_Throwback:
That message shouldn't be hurting anything. I'd just proceed.

---------- Post added at 02:43 PM ---------- Previous post was at 02:42 PM ----------

Wait, you're not doing a factory reset in the bootloader, are you? You're doing it in TWRP, right?
[One (M8) Original Android Development] fyarf:
Factory reset from TWRP only, correct. Just did the factory reset, and rebooted to bootloader.

Whats the reason for carrier message?
[One (M8) Original Android Development] Captain_Throwback:
I don't know. /carrier is in fstab. I'm guessing that's part of the issue you're seeing though.