yashsingh1/xdaforums huggingface dataset:
[Sprint HTC One (M7)] tdhite:
At lunch -- took a quick look and have some ideas. Can you tell me the following please?

1) What format is the USB (ntfs? exfat? ext3? fat? -- what is it); and

2) Is there a special partition on it for ISO access in Windows to install software.

Thanks.
[Sprint HTC One (M7)] THADDIUS25:
I think it's exfat and there is no special partition on it.
[Sprint HTC One (M7)] tdhite:
[prior text removed -- had a senility moment ]

-----------------------

Edit: -- I was wrong (upon rechecking my code, exfat is there)

I feel like an idiot -- I totally forget I added the FUSE supported TWRP needed before the compile. I just tested an exfat device, works perfectly. [MENTION=4300407]THADDIUS25[/MENTION] -- I'd love to debug with your usb stick, but there's simply no way I can get disks to fail. I'm sure there's some teeny incompatibility with the kernel I'm building and your USB, but I sure can't figure it out.

So that leaves me with this -- so far, I can't reproduce any error on USB OTG. Maybe you could give me a dump of the USB stick info? I honestly am at a loss without the more murky details of your USB stick.
[Sprint HTC One (M7)] tdhite:
New build coming ...

All,

I'm cutting a new build to try to help out the (very, very few) folks reporting inability to mount USB drives. It also has support for /misc and /recovery as partitions. Just fyi. It's not dramatically different for the vast majority of folks, it just modifies slightly the fstab entries to try to coerce some USBs to come in and play.

I now have automated tests so need not risk my phone (most of the time) so it'll be out in the AM worst case. I plan to replace the existing Release Candidate with this build. Like I said, it does not affect the vast (seriously, very vast) majority of users, but might help some having USB stick troubles.

For those wondering, USB is tricky -- kernels, timing, bla bla bla. It's not unheard of that some sticks simply don't work. The key, usually, is try to mount it in your daily driver ROM. If it won't mount, you might want to reconsider it.
[Sprint HTC One (M7)] cschmitt:
Just to chime in, I've seen general flaky-ness with USB otg on CM and in TWRP since it was first supported.

Sometimes the drive mounts, other times the drive led just flashes a couple of times, but no mount. Reboot, or power cycle and it will usually mount OK.

Then there are the random drive disconnects during backups or restores.

Tried several thumb drives, some just work better than others.

My point, it's probably not anything specific in your build that causing issues.
[Sprint HTC One (M7)] tdhite:
All users are worth a fight. My mantra . ;)
[Sprint HTC One (M7)] tdhite:
Slipstreamed new build in to Release Candidate #2

As noted, new build committed -- old build no longer available (very minor changes, may help some troublesome USB sticks - see above posts).

All relevant posts updated:

Downloads Post; Change Logs; and Disclaimer Post.
[Sprint HTC One (M7)] hb17:
Thanks for the hard work on this. I appreciate what you've done so far.
[Sprint HTC One (M7)] THADDIUS25:
Thanks a lot tdhite, whatever you did on the latest release Otg cable now works. Thanks for the hard work.
[Sprint HTC One (M7)] lambofgod13:
Quick question. Coming from 2.6 i noticed that 2.7 wouldn't restore backups from previous versions. Is this fixed now?

HTC one bitten by gruesomewolf sense 6
[Sprint HTC One (M7)] tdhite:
Nope -- it's buried in the TWRP2 code basis and I've never had a moment to dig in to the issue. No one has ever complained, so frankly I never gave it much effort either (being totally honest).
[Sprint HTC One (M7)] lambofgod13:
I wouldn't have known this issue existed until i had a bad down load rom not flash and i had no other zip rom to flash on my storage and when i tried to restore from a nan out basically flashed nothing so i was literally without any os on my device. So what your saying is every twrp update i should make a new nan every time? I just want to make sure i don't end up in that situation again. Thanks for the nice job on recovery.

HTC one bitten by gruesomewolf sense 6
[Sprint HTC One (M7)] tdhite:
You didn't read the info in the original OP set -- it's all stated right there. See http://xdaforums.com/showpost.php?p=50383578&postcount=4 in the "Prior Releases" under "Noted Issues." Now that I look at it, it is kind of buried -- crap, I'll pull that out to be more obvious. :o

In any event -- major releases, yea -- I'd plan on potentially broken backup upgrades. Releases laid out for the foreseeable future -- not a problem. This is a one time hit. Backup away and feel good.
[Sprint HTC One (M7)] lambofgod13:
Thank you.

HTC one bitten by gruesomewolf sense 6
[Sprint HTC One (M7)] slyest12:
If you download RootLinux's Recovery Flasher, you can flash TWRP 2.6.3 and restore your backup. Then, flash tdhite's latest masterpiece (using the Recovery Flasher) and redo your backup. I've done it a couple of times and it works like a champ.
[Sprint HTC One (M7)] tdhite:
Build to Work Around Sense 6 ROM Failures

All,

A question for you. To cover for the issues some folks are having when installing Sense 6 ROMS, I've added an option to my build of TWRP to disable the multi-core performance mode. The issue with the ROM failures is the ext4/jbd2 file system are failing lengthy operations under high performance multi-core mode, so the kernel detects a metadata error and remounts the file system (usually /system) in read-only mode. After that, the recursive metadata permissions settings fail (obviously) -- thus the 'some file failed' error.

So, after debugging extensively, I added an option to turn off performance mode and run with a single core. That prevents what I'll simply call a multi-core bug -- the ROM install succeeds.

So the question is -- want a separate build, or just one still. The reason I ask is since it's a setting, I added a checkbox to the Settings page. I'll document it for Theme writers, but most existing themes won't have the option, so it'll not appear.

Anyway -- just asking. I'll put the build out either way so everyone gets the best of both worlds -- speed when you want, and slow it down when the installer simply can't handle it.

One, or two builds? As I said, I'll document the theme info (really quite simple).
[Sprint HTC One (M7)] Sloth:
So if I'm reading this correctly...when installing a rom it will "slow down" to 1 core?

When doing a backup or restore it will still be multi core?
[Sprint HTC One (M7)] tdhite:
It's optional -- either you turn on performance mode, or turn it off.

But it's not enough, I'm finding. The bug is fundamental to the Android ext4 file systems. I can still get it to fail in single cpu mode if I push on it.

I'm going to cherry-pick a proper fix to the file system itself into the kernel. That'll cover us for good.

--------

Edit: a little more info...

we're not alone, btw: http://xdaforums.com/showpost.php?p=51519763&postcount=271

That's the exact same bug. It's never reared it's head because frankly the ROMs weren't as big as the Sense six /system dumps (that's my current take, anyway). All recoveries are subject to the bug -- it's just a matter of time, place, ROM -- all sorts of variables -- as to whether it shows up.
[Sprint HTC One (M7)] hb17:
I like the idea of having a single build with the option of single core operations.
[Sprint HTC One (M7)] elvisypi:
I have never had any problem installing any rom, except for the Eclipse sense 6. Even in that case if I installed it again without wiping it would finish successfuly. With O.M.J sense 6 there's no such problem

Gesendet von meinem HTC One mit Tapatalk
[Sprint HTC One (M7)] tdhite:
That's my point, my friend. The bug is random. It's not new either:

http://xdaforums.com/showpost.php?p=40716971&postcount=576

Older recoveries are blowing off the file system error and *not* remounting the file systems read-only. I can also have the kernel blow off the errors, and then let the DEV deal with the outcome: bootloops. Fix after that is either have the ROM dev force a file system check after flashing (which, as it turns out, [MENTION=4457281]hawknest[/MENTION] does, so that's why some recoveries work with his install -- the recovery blows off the file system error, and by happenstance [MENTION=4457281]hawknest[/MENTION] is checking the file system at the end of his install). Doesn't work with 2.7.0.4, though, because I have the kernel remount the file systems read only if there's *any* error that could cause corruption.

Contemplating just following suit and blowing off errors if they occur. Hate that thought, but it seems the standard (ick!).

-----------

edit: not all recoveries are ignoring errors, the bug just doesn't necessarily show up -- it's simply randomly triggered, which means, to me, a hardware controller thing (not unlikely -- lots of scsi RAID devices showing similar issues in big servers). More digging required.
[Sprint HTC One (M7)] XxCE0xX:
server is dead. needs mirrors.
[Sprint HTC One (M7)] tdhite:
From goo.im: "Today you have a total of 144 files ..."

not so dead. :) -- possibly you have a poor connection, maybe some troubles elsewhere, but the servers are all up.
[Sprint HTC One (M7)] tdhite:
Well, now, maybe it's not a new bug, but it sure is more possible now. The newer kernels have far more sophisticated caching and checking on things. That's why it's popping up.

So, LOL, if you saw this: https://github.com/tdhite/android_kernel_htc_m7wls

I'm betting you know my plan to fix. :)
[Sprint HTC One (M7)] raptoro07:
Are you talking to yourself?!?!

lol
[Sprint HTC One (M7)] tdhite:
crazy devs do that. :cyclops:
[Sprint HTC One (M7)] GadgetFreak:
:eek: Oh, lord. tdhite has cracked...

:cool:
[Sprint HTC One (M7)] rootlinux:
LMAO :)

I feel like I am normal in here. :eek:
[Sprint HTC One (M7)] mrshades812:
Who you talkin' to bro?? :eek:
[Sprint HTC One (M7)] rootlinux:
Was I talking to myself again?
[Sprint HTC One (M7)] tdhite:
NOPE! Got it! Bug squashed (long story how). Just have to package it up for a test build, but [MENTION=3173383]elvisypi[/MENTION], ecliptic now fully installs, no errs. :D

Soon. gonna need a few testers, but the basic difference is I swapped out the ext4 implementation in the AOSP kernel for the HTC Dev released 4.4.2 kernel. Add a few tweaks to stop the formatting time madness and we have a good build for any size ROMs.

I'll build 'er down, test, and then post. I have a ton of day-job work to do today, so will check in now an then, but I suspect the build will be accepted, trust me.:good:
[Sprint HTC One (M7)] rootlinux:
Awesome.. When it is up I will add it to the flasher as well.

Fantastic work brother.
[Sprint HTC One (M7)] tdhite:
Release Candidate 2.7.0.4b -- Fix for "some files failed" (ext4 bug)

For now, this is a release candidate for testers. It will not change if it goes ok and will get uploaded to the Goo.im official site.

Download: http://goo.im/devs/tdhite/twrp2//openrecovery-m7wls-2.7.0.4b-04-06-2014.img

MD5 Hash: 84f2c210b0cf4dcc5e00d6e7becec636

[MENTION=4457281]hawknest[/MENTION] / [MENTION=3173383]elvisypi[/MENTION] -- for the most part it was Ecliptic that gave us this warning about the future (:good:) of the ROM sizes and file system bugs within some newer ext4 file system implementations. Ecliptic installs flawlessly for me, now.

This release candidate uses the HTC Dev ext4 implementation from the most recent (4.4.2 Sense) kernel -- let's call that the 'offically released' implementation by HTC. If you two are satisfied with the Ecliptic installs, then frankly it's a release. Would love any other feedback, though, from those who can test for a bit.

Anyone building off my repositories need not rebuild/release unless you're using the msm8960 kernel -- this is purely kernel work. If you are using the m7 (ul) kernel sources, they did not yet get around to updating the ext4 system to match the msm8960 kernel -- so you're fine. Just watch out over time as there's probably a merge coming at some point. Just switch to the HTC ext4 implementation as it's close to the new sources, but does not exhibit the issue.

Let me know, but I don't foresee troubles with this build. :cool:
[Sprint HTC One (M7)] Rydah:
Would love your work on the Sprint M8, they don't make em like you did. ?

Sent From My HTC One (M8)
[Sprint HTC One (M7)] Ph33zy:
+1...I know the M8 is new , but it's been a nightmare for me to use the current recovery. My heart stopped for a bit when I couldn't restore my backup knowing that a RUU does not exist at the moment. Please dev for us!
[Sprint HTC One (M7)] cschmitt:
[MENTION=4988866]tdhite[/MENTION], building with the m7 kernel on the GSM model appears to have fixed the format bug for us, thanks for the tip.
[Sprint HTC One (M7)] lambofgod13:
Will 2.7.0.4b restore back ups from 2.7.0.4?

HTC one bitten by gruesomewolf sense 6
[Sprint HTC One (M7)] tdhite:
Should be fine. Try it.
[Sprint HTC One (M7)] Rydah:
So buddy ol pal, care to take a stab at the m8?

Sent From My HTC One (M8)
[Sprint HTC One (M7)] METHOD1911:
Rydah have you tried it on m8

One method1911
[Sprint HTC One (M7)] Rydah:
Wouldn't it not work since we have different mount points?

Sent From My HTC One (M8)
[Sprint HTC One (M7)] rootlinux:
I wouldn't try it.
[Sprint HTC One (M7)] tdhite:
Correct. Bad idea.
[Sprint HTC One (M7)] retiredtrebor:
TWRP Stay Awake

I am not a dev, just had a thought that might be worth passing along. I do not know if this is possible.

One of the things that sorta concerns me, when flashing a rom, is the screen timing out and going black. I don't know, at first glance, if something failed or if screen timed out, always expecting the worse. Is there a way to enable the stay awake mode while in TWRP, when flashing a rom? As long as I can see TWRP and the progress it is making, I don't get excited. In the past, I almost bricked a phone when flashing a rom using TWRP.

Since this is the development thread, I thought posting it here would be appropriate.
[Sprint HTC One (M7)] tdhite:
TWRP 2.7.0.4b Touch Recovery Released

Just informational ...

Lotsa runs, Lotsa hits, no errors. It's a release. All posts updated and goo.im developer notes updated.

No need to redownload/reflash -- it's just notice of upgrade from release candidate to release.
[Sprint HTC One (M7)] rootlinux:
Well, the flasher is good to go then. :)

Great work as always brother.
[Sprint HTC One (M7)] METHOD1911:
Cool just checking. Thanks for the heads up. Fellas I had a really weird situation earlier. To make a long story short, I had to restore a nandroid of my phone that I had from a backup right after I rooted my Sprint M8. When I did it said it failed so I rewiped and restored the nandroid. It said it failed right before it restored my data but my phone still booted up with the nandroid. This has never happened to me before. Any ideas.

One method1911
[Sprint HTC One (M7)] tdhite:
M8? This is m7wls.
[Sprint HTC One (M7)] METHOD1911:
Oh damn my bad.

One method1911
[Sprint HTC One (M7)] tdhite:
This is gonna sound really bad, not meant to insult at all, but it works:

"If you leave the lights on, I won't be scared."

I think what you need to do is simply turn off screen blank when you start a long process that concerns you. Just my take.
[Sprint HTC One (M7)] retiredtrebor:
I try to remember to activate stay awake in developers options, but in my old age sometimes forget in the rush to flash a new rom.

What can I say? :)
[Sprint HTC One (M7)] systemshock869:
I always turn screen timeout off.. FYI if you wipe internal storage it will reset that option.. Caused me a brief moment of panic when it timed out on me while flashing after I disabled timeout. The config file is stored on internal storage.
[Sprint HTC One (M7)] Aldo101t:
in settings on twrp to turn off screen time out.......
[Sprint HTC One (M7)] retiredtrebor:
Damn, that was quick work for a suggestion just made on the spur of the moment.

Thanks. I have left the settings alone previously because most of them don't mean anything to me. I figured just leave the defaults as is, better safe than sorry.

For the next question, I have been reading/seeing about TWRP 2.7, but goo manager is still reporting 2.6.3 as latest available.
[Sprint HTC One (M7)] tdhite:
Goo manager never seems to get things right. The title of this thread tells you the most recent version you can get. Is that what you are asking?
[Sprint HTC One (M7)] dafluke24:
If you "browse all files" in goo manager and look for the tdhite folder, the latest recovery is there. I just checked.
[Sprint HTC One (M7)] retiredtrebor:
Ok, so I have the 2.7.0.4b img file, downloaded thru TWRP. TWRP indicated it was installed. Upon reboot into recovery, TWRP still indicates 2.6.3. The .img file doesn't mean anything to me. What do I do with it, how? Honestly guys, the old flashable zip was a lot easier to use.
[Sprint HTC One (M7)] slyest12:
You could always try using Flashify. I've used it a couple of times on tdhite's TWRP and it worked like a champ.
[Sprint HTC One (M7)] rootlinux:
I have this recovery in my flasher thread.

It is continually updated with latest recoveries .

If you want to update via recovery, check my thread then come back here. ;)
[Sprint HTC One (M7)] retiredtrebor:
Finally got TWRP updated. Thanks for the info rootlinux.
[Sprint HTC One (M7)] rootlinux:
Anytime my friend.
[Sprint HTC One (M7)] systemshock869:
Gotta say this is an amazing tool.. Been hoping one of these would pop up for a long time.
[Sprint HTC One (M7)] budeone:
Yea.. It's amazing..
[Sprint HTC One (M7)] systemshock869:
Anyone having any problems flashing? I'm on the latest 2.7.0.4b, flashed from RootLinux's tool. Noctournal's GE 4.0.6 and RootLinux's HBoot flasher both fail to start. I've tried re-downloading them both a few times, the only thing I haven't tried is re-flashing recovery. ViperOne and RootLinux's recovery flasher both start up just fine.. I've got Viper booting now. For some reason the Rootlinux recovery flasher on my USB drive is an old version, will download the new one and re-flash recovery when I have time.
[Sprint HTC One (M7)] tdhite:
I flash *gobs* of things (my own kernel I'm working on, CM 11 builds I'm modifying, zips for other tools I need, etc.). Daily -- seriously. No probs at all.

Post up a recovery.log and let's see what's up.
[Sprint HTC One (M7)] systemshock869:
I am suspecting my work computer of screwing up the download.. I'll have to try it again when I get home.

Thanks for the help!
[Sprint HTC One (M7)] budeone:
I have this on three phones and no problems
[Sprint HTC One (M7)] systemshock869:
Yeah I'm blaming my work computer.. I assumed it was reliable because it's a Mac but I think it caused an issue with my USB drive.
[Sprint HTC One (M7)] tdhite:
LOL -- there AIN'T NO frickin' bugs in this. LOL -- at least none found yet.

BUT -- there's an update coming ... hang in. Some nice adds recently for AOSP users (gee -- imagine that given I'm maintaining pac-man ROM now). Heh.
[Sprint HTC One (M7)] slyest12:
And just as I was settling in with Sense 6... I'm extremely interested to see what Pac could be like with a dev like you maintaining it.

Great job on TWRP, btw. I only use your latest updates- looking forward to the next one.
[Sprint HTC One (M7)] tdhite:
Cyanogenmod (CM11) Based ROMs Broken!

All,

I'll send out an updated build soon due to terrible decision by the CM folks. They modified their recovery updater-script in a way that effectively invalidates any recovery built prior to April 30.

If you're not using CM-11 based ROMs, no biggee, if you are, you'll need to use the new build. I'll get it out today (hopefully).
[Sprint HTC One (M7)] tdhite:
New twrp2 2.7.0.9 released

Fixed:

All updated, new CM-11 based ROMs now flash ok (assuming they were right in the first place, obviously). To everyone's surprise, it was well known to the CM-11 team this mess would occur and they still released and to quote the change author (who at least tried to stop the mess): "Direct users here when all hell breaks loose . . . ." See http://review.cyanogenmod.org/#/c/62852/.

See the Downloads Post, Changelogs Post and as always it's important to (re)read the DISCLAIMER Post.

We're covered now anyway.
[Sprint HTC One (M7)] rootlinux:
Flasher updated. :)
[Sprint HTC One (M7)] tdhite:
"get prop error" -- that is an issue with the 4.4 builds (all) of Android, on which this recovery is based. Google changed the way getprop works and it's problematic with old updater-binary executables. Can you point me to what you're using? I can try to discern a fix for the general case.
[Sprint HTC One (M7)] bearw815:
[MENTION=4988866]tdhite[/MENTION]

Superwipe script

https://www.dropbox.com/s/73oprshdgjrj7ky/smw6180_Superwipe.zip

sent from my-beanstalk-one
[Sprint HTC One (M7)] Sloth:
Is this new or the same one posted in the forum?
[Sprint HTC One (M7)] benny3:
Cool , i have a theme maybe thats my problem

EDIT: Yes the theme was it, Thank you again!
[Sprint HTC One (M7)] bearw815:
Same one as in forum.

sent from my-beanstalk-one
[Sprint HTC One (M7)] Sloth:
That's the one I have always used hmmm

---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------

[MENTION=4988866]tdhite[/MENTION] any thought why it's unable to mount cache?
[Sprint HTC One (M7)] bearw815:
That's why I uploaded it so maybe he can fix it :)
[Sprint HTC One (M7)] tdhite:
Ok -- two big problems with your superwipe zip:

1) The updater-binary is ancient:

-rw-rw-r-- 1 tdhite tdhite 224260 Aug 31 2011 META-INF/com/google/android/update-binary

That's well over two years old, and it will not work with any 4.4 based recovery (that include PhilZ and CWM as well). Tell the developer to update the updater-binary -- that should have been done long ago, imho.

2) The work taking place in the zip is effectively useless to new recoveries -- they all do the same work automatically for you, so I don't see the need for the flash at all:

$:~/Desktop/unzipped$ cat setup/datawipe.sh

#!/sbin/sh

cd /data; find . -maxdepth 1 ! -name 'media' ! -name '.*' -exec rm -rf {} \;

That command is nothing more than a removal of everything on /data but excludes the internal SD card. TWRP does now, and has for a very long time, taken care of that already.

Edit: adding] The rest of the partitions / directories cleaned are wiping /boot (kernel), /system (standard for recovery wipes), /devlog (/dev/mmcblk0p22), and

/cache (recoveries wipe this). Not sure why anyone would want to dump /devlog, but I can add that to the TWRP if desired. As for wiping /boot, all ROMs writing /boot 'dd' it into place anyway, so wiping it prior is fruitless.

In the end, I'm not sure there's really any value spending much time on arguably superfluous tools like that within the recovery itself, but if I can help, I will talk to the dev and help him update the update-binary for you. That would fix it if you really want it. Regardless, the value is gone, effectively, with new recoveries (that include PhilZ and CWM as well as this one).

One thing I think I can do is prevent any flash from running at all if there's an ancient updater-binary in the zip. I'll look at that.
[Sprint HTC One (M7)] Sloth:
I got the same error "unable to mount cache" when I wiped manually also

Advance Wipe>Wipe

Chose cache/dalvik cache/data/system

Failed
[Sprint HTC One (M7)] benny3:
I ask him a while ago if he would update it and he said he would look into it when he had time.

it would great if you did work him and get us a useful superwipe back for us. Im sure its a placebo effect but its one that i and many of us like...lol
[Sprint HTC One (M7)] Aldo101t:
BD just for ****s and giggles, did you try wiping one at a time.
[Sprint HTC One (M7)] Sloth:
Nope got frustrated and re-flashed 2.6.3.0
[Sprint HTC One (M7)] Riff76:
Quitter!