yashsingh1/xdaforums huggingface dataset:
[Sprint HTC One (M7)] tdhite:
I'll assume /data was mounted and you didn't flash a ROM first that unmounted /data and left it that way, or you unmounted it yourself. With that said, when you enter the Backup screen, just above the "Enable Compression" you will see a line (it's really a button) that says "Storage: ..." where ... is either nothing, or some text. No matter what it says, touch that button and it will pop up a menu for either internal storage or OTG. Just pick the right one and try again.

Truth is this is a development thread. You need to use the Q&A forum for general support. I'll help as I can, but there are a lot more folks who can help in the Q&A area that will see your questions.
[Sprint HTC One (M7)] Docarut:
Deleted.
[Sprint HTC One (M7)] systemshock869:
Were you talking to me? Sorry I didn't see. Here is my log. https://www.dropbox.com/s/0zfvk7r6he7fs9z/last_log

To remind you I was having problems with the settings (specifically screen time out) staying after reboot.
[Sprint HTC One (M7)] benny3:
I always thought Team twrp asked for the curtain not to be changed

http://www.teamw.in/twrp2-theme-guide
[Sprint HTC One (M7)] elvisypi:
That does not stop you from changing it for personal use ;)
[Sprint HTC One (M7)] benny3:
True
[Sprint HTC One (M7)] tdhite:
Screen timeout setting saving works on all devices but yours apparently. Here is your issue:

I:Attempt to load settings from settings file...

I:Settings file '/data/media/TWRP/.twrps' not found.

It should look like this:

I:Attempt to load settings from settings file...

I:Loading settings from '/data/media/0/TWRP/.twrps'.

I can't tell you why you have no settings file , maybe you cleaned internal storage, or some installer did that. Twrp writes that file on changes to settings.
[Sprint HTC One (M7)] elvisypi:
Maybe he is still on 4.1.2, which has the old file structure look here http://xdaforums.com/showthread.php?t=2304138

Before the path would be /data/media/, after 4.2.2 it is data/media/0/
[Sprint HTC One (M7)] drlzanej:
May have already been answerd and sorry if it has, but is OTG in recovery working for 2634, just curious. Thank you
[Sprint HTC One (M7)] Ph33zy:
Is there a way to turn brightness down? I recall being able to do this before, but can't seem to find the option anymore.

Sent from my HTCONE
[Sprint HTC One (M7)] Th3Bill:
From OP:

What Works (see also Change Logs and Issues List):

It appears everything, including OTG Support, off-line charging with notifications (LED and UI), screen-blank, and much more. Alas, bugs happen so if you find one, please post the relevant information about the bug here and create an issue on the github project for TWRP2 Sources given below.
[Sprint HTC One (M7)] tdhite:
I'll look at adding that over the weekend.
[Sprint HTC One (M7)] rootlinux:
Hey tdhite bro.

I made this just for you guys in here.

It is your recovery flashable via recovery.

You are welcome to do with it as you wish.

I can keep it hosted and update it as need be or you can host it if you want.

I will also change the boot splash if you want to provide one just for your recovery.

If you don't want me to keep it going at anytime just say the word. :)

http://d-h.st/lxj
[Sprint HTC One (M7)] tdhite:
Weekly Build Toys ...

All,

couple toys coming (the latter only if I can assure everything is stable and consistent):

1) Screen brightness setting (now works, good call by the poster that brought that up);

2) multi-core support: this is more esoteric -- I am generally disappointed in the backup / restore speeds with TWRP, especially since it uses pigz/unpigz (parallel gzip/gunzip). With that said, I notice it used only one core of our quad-core processor, so I forced the other cores on in the kernel. Presto: changes my backup time from 493 seconds down to 356. 72% of the original time. Realize we'll never get much more -- can't do *all* things truly parallel, but ~30% drop is a very good drop considering disks and other holdups are in the mix.

So, brightness setting is a lock. Multi-core support -- well, I'll let users decide. It will run warmer when working on things like backups / restores (there's some throttling for thermal by the kernel, but it's not like you get all the toys you're used to, like Trickster -- it's a recovery, not a full build). So -- you folks want two builds? One with multi-core and one without? Or just flip the switch and go multi-core?
[Sprint HTC One (M7)] Ph33zy:
Flip the switch!

Sent from my HTCONE
[Sprint HTC One (M7)] Rydah:
Flip the switch!!!

Sent From My HTC One! ?
[Sprint HTC One (M7)] tdhite:
LOL -- maniacs ...

Doing one better. Going to set in some properties that flip to full multi-core for nandroid operations and install operations, then turn off three cores for heat and battery savings otherwise. Might take some testing and time tomorrow, but it'll work.

Screen bugs me -- there's issues between Aroma and screen timing. Hmmm -- I'm all about safety and *not* ending up, ever, ever, ever again with a screen that won't turn on. Saw that once in testing after an long (really long) Aroma based install.

I'm telling you folks, I'm not putting out a build that has anything like we've seen before. It spooks users too much and what really concerns is that bad install scripts that fail to either 1) sync; or 2) unmount partitions will leave bad crap out there, possibly causing a boot loop if one has to hard-reset.

We are on the edge of the TWRP code now -- very fresh, so safety is king. But cores? We can do that for sure. I'm on it. I'll put out a beta build with the screen dimming option, we'll see how that goes.
[Sprint HTC One (M7)] Rydah:
I'm ready for testing as well. ?

Sent From My HTC One! ?
[Sprint HTC One (M7)] tdhite:
Beta is out, boys and girls: Go To Downloads and look for the Beta build.

Also be sure to check out the change logs.

Let me know how it goes -- the only anomoly I have seen is on one test I got a non-recoverable blank screen with a complicated Aroma install. I can't repeat it -- just looking for other's comments in general. The multi-core is quite stable so no worries (I believe). Dramatic speed improvements -- I even shaved another 50 seconds off my backups (so now upwards of 35% savings in time.
[Sprint HTC One (M7)] mikeius89:
Great job on the brightness. And a backup time was much better 350 secs compared to 410+ secs.
[Sprint HTC One (M7)] rootlinux:
Awesome job tdhite
[Sprint HTC One (M7)] Ph33zy:
[MENTION=4988866]tdhite[/MENTION]

some feedback on beta recovery. Installed a ROM just fine. Ran an ODEX script and it was blazing fast compared to previous recovery. Only weird quirk I had was installing the latest KitKat kernal from Thick Lizard (Weeping Angel). That usually installs very quickly, but on new recovery, it hung for a good minute or 2. I thought the recovery had froze, but it ultimately finished. I don't have a log or anything, but that was the only weird thing I saw.
[Sprint HTC One (M7)] tdhite:
thanks -- still concerned about the one time I saw the screen not wake up. I don't want *any* of that. Hopefully someone can verify I'm not nuts and give me their logs.

Either way -- I'm posting the multi-core as a release by end of tomorrow. That is a must have, imho -- way better speeds on all operations (not just nandroids, *all* operations that start with a UI request for an action.

Worst case leaving the beta with the screen dim for a week so I can get more comfortable that it was a build error or something strange. I remain a stickler for bugs -- hate them, hate it when I can't recreate because that means I can't find 'em.
[Sprint HTC One (M7)] tdhite:
"Ran an ODEX script and it was blazing fast" -- THAT's what I'M talkin' about! :good:

As for the Weeping Angel installer -- seriously, flash installers *really* need to give feedback on every little thing they do, with little messages like 'this could take a while' or similar. Otherwise, folks never know what's up, and there's no real way the recovery can jump in the middle and start jamming messages in between so you know it's not hung. Would be good if you let Thick Lizard know you saw that and could use some feedback (that isn't the only one -- others need it too, we just have to get them to do the 'user friendly thing' one by one). The 'I thought it hung' is a classic situation without user feedback -- people go nuts and have no idea what's at issue. As I've mentioned before -- it's actually rarely the recovery (assuming it's built properly) -- TWRP2 for instance is highly threaded and is alway up unless a dramatic catastrophe happened (e.g., a kernel panic, quite rare indeed).

Thanks regardless for the info -- also glad you let it finish because that's how folks end up boot looping and wondering why 'the recovery blew it' -- in fact it didn't, the user just has no clue what the installer was doing so instead hard reset in the middle of a disk write (poof goes the file system integrity).

[edit: adding comment]: Just so you get a hint -- lots of kernel installers run fstrim in the middle (or end, or somewhere anyway) of the install. That can go like lightning, or like molasses, depending on a number of things. The point is -- a little notice right before running something like fstrim, which can be all over the map in time to run, helps mitigate user concern. That's all I ask of flash writers -- a little more info so the user isn't spooked into rash thinking.

[edit2: update]: While my prior edit remains correct, there's another issue that multi-core is causing, so I am quite possibly wrong about how your issue manifested itself. Still could be fstrim or similar, but could also be a timeout on a mutex or similar, so hang in if that's the issue, there's fix, just gonna take me a bit as it's somewhat complicated in that area of the code.
[Sprint HTC One (M7)] rootlinux:
I will update my files once you post the release recovery.

Looking forward to checking it out.

Is it backwards compatible with 2.6.3.0 or still no?

Not a big deal as users can just use the multi flash recovery.

It isn't something I would stress over. :)
[Sprint HTC One (M7)] tdhite:
New Toy for Devs: updater-binary (I'll keep it up to date)

Devs (and others who can spread the word),

I got sick and tired of looking for an easy way to shore up the way forward for everyone regarding updater-binary for the new TWRP. Well, if I'm sick of looking, I'm certain *your* sick of looking. So I just bit the bullet and am now providing up to date updater-binaries along-side the TWRP code. With each build, I'll now add an updater-binary-(date_goes_here) and the MD5 related to it. I'll also post it on the Downloads Post in this thread.

This updater-binary is built, as is the new TWRP, fully from 4.4 sources as provided *in* the TWRP code itself. So we will have what TeamWin provides, and more if we need it (I'll add reasonable tools for ROM devs).

With that said -- repack some ROMS with the new updater-binary and see how it unfolds with this (I have to say superior recovery, not patting myself at all, just TeamWin fixed a lot of things plus the toys I've added are simply better). Let's git frickin' down the road and off the old stuff (including old TWRP) if possible. There should be no real reason we can't utterly unify all ROMS on Aroma, and where not Aroma, the updater-binary I provide in this thread to match TWRP (though, frankly, PhilZ could use it too, so could other CWM based recoveries, instead of taking over the functionality and blowing off the flash included updater-binaries, thereby asserting on other things folks aren't used to, like format calls).

Anyway -- time to unify a bit, imho. It'll take some time, but I'm not one to look back, rather forward, so here we (should) go. I'm here to support this tool as we need. Find bugs, I'll squash 'em. For you SuperWipe fans -- that was the straw that broke the camel's back (some poster suggested getprop didn't work -- good grief -- that's total misinformation (not the poster's fault other than ignorance of the truth -- Google changed it, so *updater-binary* executables don't work properly, particularly on asserts looking at getprops)).
[Sprint HTC One (M7)] rootlinux:
What is the update going to be?

2.6.3.5
[Sprint HTC One (M7)] tdhite:
Heck no -- that'd be, like, claiming to the world we're ahead. LOL. Hey, now, maybe so. We do have battery LEDS, and a working, maintained updater-binary, and even multi-core processing. Think 2.6.3.5? :cool:

Actually I was inclined to call it 2.6.3.4a. That'd be stupid maybe?
[Sprint HTC One (M7)] rootlinux:
Call it ThunderBOOM. :)
[Sprint HTC One (M7)] tdhite:
Documentation for the updater-binary provided in Downloads

You will find documentation on the updater-binary provided within this thread in this post. I will keep it updated as necessary. As well, the Downloads post links to this page so it doesn't get lost over time.

Documentation on updater-script syntax as supported by the provided updater-binary:

It's easy to read and understand the calls by looking at the source code to the updater-binary. To read the source, go to the following links and search for the name of the function with 'Fn' appended to it. For instance, to read on ifelse, go to the links and search for "IfElseFn" and that is the actual implementation of the 'ifelse' updater-script call. The comments to most (though certainly not all) calls have the documentation of interest -- no need to duplicate here. Where the source does not have comments, the code is quite easy to read and understand but I'm always willing to help where there's a need.

Links to general and specific documentation:

General Documentation on Edify

Sources for 'Built-Ins' functions

Sources for 'Installer' functions

Supported Functions:

abort

apply_patch

apply_patch_check

apply_patch_space

assert

concat

delete

delete_recursive

file_getprop

format

getprop

greater_than_int

ifelse

is_mounted

is_substring

less_than_int

mount

package_extract_dir

package_extract_file

read_file

run_program

set_metadata

set_metadata_recursive

set_perm

set_perm_recursive

set_progress

sha1_check

show_progress

sleep

stdout

symlink

ui_print

unmount

wipe_cache

write_raw_image
[Sprint HTC One (M7)] YACO:
Awesome stuff happening here! but I got something to report on the latest beta (2/22). Just ran a backup of boot/system/data/cache and before it started backing up it hang for about 4min on "Updating Partition Details...". Don't think this was supposed to happen so I thought you should know.

YACO
[Sprint HTC One (M7)] tdhite:
I've now heard two folks report delays, and in fact I swear I saw one (but can't reproduce). That tells me the multi-core is, while working, causing some mutexes (forced delays when multiple threads of execution try to access a shared resource, like a partition table or something). I'm going to have to clamp down just how much is allowed to run multi-core. I'll find it, I know where this is rearing it's ugly head -- I think.

That also explains (finally, I believe) the screen blank/stuck I could never reproduce. Right after a nandroid, my bet is the recovery was updating system details and stuck on the mutex for a while. So you in fact helped a bunch. Thanks. Tells me screen blank is still ok, multi-core needs a tad of work -- backwards to what I was thinking earlier!
[Sprint HTC One (M7)] cschmitt:
I'd go with 2.6.3.4a for versioning.

[MENTION=4988866]tdhite[/MENTION] I'm building from your repo for m7, do you have any issue with me posting TWRP over in m7 forums with proper create to you, et. al.?
[Sprint HTC One (M7)] tdhite:
My only request is that you do give proper credits, but also generate Pull Requests so we can keep the code merged and clean for our devices. I'm assuming, of course, by m7 you're meaning the international phone, right?
[Sprint HTC One (M7)] Ph33zy:
I have this problem right now as we speak. I'm still waiting for the Nandroid to start....

EDIT: hung for about 10 min for me. I long pressed power to reboot, but as soon as I long pressed, nandroid starting working...
[Sprint HTC One (M7)] cschmitt:
Absolutely. Yes, m7(ul, att, tmo)
[Sprint HTC One (M7)] tdhite:
No doubt -- I located the bug, but it's not in TWRP source. It's in the C++ std::vector template iterator. After many operations, TWRP wants to update partition details. It then loops through (with a vector iterator, if you know coding) all the partitions and detects backup sizes, etc. Randomly, in the midst of that loop, the vector code (which is pure C++ code as part of the SDK/NDK) is hanging until some other event takes place. In fact, I can put random timing delays in the loop and it will work perfectly. Obviously, that's not a fix, that's a hack and we don't do hacks. I'll figure it out, it's just gonna take a few -- multi-threading bugs, particularly with true multi-core processing is very difficult to debug.

Interestingly -- if you 'adb shell' into the recovery while it's hung, it'll go again. I have to go into the std template code to figure out what the heck it's hanging on (like I said -- very likely a mutex and a bug related to that). This is a truly wicked bug. :(

My take is, given the nature of this issue, I'm going to release the screen dim code, and work at the multi-core bug over this week. We all know what it can do now, for speed, but it has to be something that doesn't confuse the user with delays.
[Sprint HTC One (M7)] tdhite:
Heh -- my take was premature (I think?).

I clamped down the areas allowed to move into performance mode. The fixes to the TWRP and C++ vector code necessary to make *all* operations cleanly threadable are rather difficult, and not something I can tackle in just a few days. With that said I put up a beta that clamps down on the areas allowed to enter performance mode to (I believe) preclude entering into the danger zones. That leaves us with speed gains for the important things (flashes, nandroids backup/restore) and non-performance (single core, generally) for other areas.

I ran so many tests my phone got warm and thermal throttling dropped the max CPU frequencies, so if you do notice slow nandroids, check your CPU temps when you get back into your normal ROM -- they probably are a little higher than normal.

See the Downloads post for the new beta.
[Sprint HTC One (M7)] NachoB:
[MENTION=4988866]tdhite[/MENTION] did you mean to date it 02-16-2014?
[Sprint HTC One (M7)] tdhite:
Huh? Date what? The beta is ...02-23-2014-beta -- dunno what you're referencing.
[Sprint HTC One (M7)] NachoB:
Part of the filename contains 02-16-2014 in it which I interpreted as a date. I looked at the wrong download link, my bad.
[Sprint HTC One (M7)] tdhite:
LOL -- it *is* a date -- each release will have a version and the date on which it went to release. We won't release 'til everyone around here (within reason) says there's no more problems.

The 02-16-2014 build is the current stable release. The 02-17.2014 are the same code, with 'cooler' graphics for off-line charging contributed by [MENTION=3173383]elvisypi[/MENTION]. Others are beta or other related items. Just read the Downloads post, if it doesn't make sense, let me know.
[Sprint HTC One (M7)] Ph33zy:
I know its a small sample size, but I've installed roms, odex scripts, and nandroids three times without any hiccup on the latest beta.
[Sprint HTC One (M7)] tdhite:
Anyone seeing anything at all? I'll tell you all what I do:

1) I install plenty of things, including Aroma based installs;

2) I repack those plenty of things with the updater-binary I compiled for the devs and replace either the update-binary for normal, or update-binary-installer for Aroma, then install 'em again.

So far, I've seen no errors. With that said, I'd like to hear if *anyone*, *anywhere* has seen anything strange. Like I always say around here, recoveries spook people because it all seems like black magic (and it's not). So I really want to be absolutely sure on any beta we all promote to an actual release.

??
[Sprint HTC One (M7)] manup456:
Beta working well for me nothing to complain about.
[Sprint HTC One (M7)] Paleryder:
Awesome and thanks for this! I am S-off and thought I could have my boot loader locked and still flash a recovery but it error-ed until i unlocked my bootl oader again is this right?
[Sprint HTC One (M7)] tdhite:
Your welcome. Indeed, that is correct.
[Sprint HTC One (M7)] tdhite:
Like you noted -- always would appreciate if you just attached the log, but it appears there's no problem after all? If you ever see this again:

E:Unable to mount '/usb-otg'

That means the flash was, for whatever reason, not properly attaching to the kernel drivers. What you can do in such cases is this:

1) Open up the TWRP terminal;

2) Type exactly this in the command line:

dmesg >/sdcard/dmesg.txt

3) Then attach that file (/sdcard/dmest.txt) to a post here.

In the end, the kernel will tell us what's wrong with the flash drive, but apparently you got it working.
[Sprint HTC One (M7)] tdhite:
Time to let 2.6.3.4a fly I think ...

After so many downloads, and no verifiable issues, I think it's time to let 'er fly.

[MENTION=3173383]elvisypi[/MENTION] -- I'm inclined to leave the off-line battery graphics exactly as they are and just commit them as the standard for our phone. They are in a separate build, away from the system/core of the android build now, so we can do that easily.

If you want to make cooler ones, no prob, but for this release, I say we call it done and no more 'elementary, square-like goofy images' imho.

Agreed?
[Sprint HTC One (M7)] elvisypi:
Couldn't agree more my friend. I haven't encountered any issues so far, this thing is rock solid!
[Sprint HTC One (M7)] systemshock869:
I made the dmesg.txt.. Does it continuously add to the log or would it just show info from this recovery session? If it's got relevant info in it I'll post it up; looks like a long file.
[Sprint HTC One (M7)] tdhite:
No need to post a file from a new session. The dmesg utility shows the kernel's real-time ring buffer, so only current sessions. Only useful if you see something you think should work, but the kernel says otherwise (for whatever reason -- but the kernel is king so the reason is almost always valid, just not obvious).
[Sprint HTC One (M7)] tdhite:
TWRP 2.6.3.4a Touch Recovery Released

TWRP 2.6.3.4a Touch Recovery was released. See the download page for download link. For those running the beta -- the only change is the version number, so you are in no rush. Update at your leisure.
[Sprint HTC One (M7)] rootlinux:
Awesome.. Will add to flashable zip later today.

Thanks bro.
[Sprint HTC One (M7)] tdhite:
v2.6.3.4b Feature Requests

Well, here it is -- my build server already notified me it merged in latest code from the TeamWin project, built and is ready for use. That's not really the point here (though there's interesting adds), rather what do we think we need next?

Feature requests for the next beta?
[Sprint HTC One (M7)] elvisypi:
Make the phone waterproof?

Gesendet von meinem HTC One mit Tapatalk
[Sprint HTC One (M7)] rootlinux:
I installed VMware on my ubuntu box and am now installing Win 8.1 on it.

Once it is done I will work on adding this to the recovery flasher. :)
[Sprint HTC One (M7)] ctiger:
wasn't that the leading feature of 2.5.4.0 release? At least I got the impression.:p
[Sprint HTC One (M7)] cschmitt:
Checkbox for reboot after operation (flash/restore/etc.)

PIN protected access to menu (after recovery starts, of course.)
[Sprint HTC One (M7)] rootlinux:
Will work on flasher first thing tomorrow.

Got busy with other projects and forgot my five year old had kindergarten orientation today.
[Sprint HTC One (M7)] systemshock869:
Wipe cache/dalvik option in wipe menu?
[Sprint HTC One (M7)] rootlinux:
2.6.3.4a Recovery Flasher

TWRP-2.6.3.4a_Recovery_Installer.zip - 14.36 MB
[Sprint HTC One (M7)] tdhite:
You should be able to do that with a theme via tw_wipe_list. Just look at some existing themes, particularly at the Advanced wipe pages.
[Sprint HTC One (M7)] Danger Dan:
You can always use flash image gui
[Sprint HTC One (M7)] rootlinux:
That's true, if you have an OS installed.
[Sprint HTC One (M7)] Danger Dan:
Why wouldn't you have OS installed?
[Sprint HTC One (M7)] Sloth:
Lol it happens more times then you think :D