yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note 4] lacz713:
i dont think the note 4 had face recognition at all on the software
[General Topics] erwinsie:
hi guys,

Just wondering if any player software for playing flv files in PPC - winmob 2003? (videos downloaded from youtube, etc)

Thanks..
[General Topics] Ultimate Chicken:
Not as far as I know, I still had to run my FLV files through eRightSoft SUPER. Take a look at thread here:

http://www.aximsite.com/boards/showthread.php?p=1159947

(note, someone's going to say SUPER sucks because of sync, to which I say try the 29.97 fps setting.)
[General Topics] StellaDel:
Nothing wrong with SUPER, does the job well and it's free.
[One (M9) Original Android Development] Captain_Throwback:
[CENTER]*** Disclaimer ***

All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does![/CENTER]

Introduction

Images

Installation instructions

Device Changelog

TWRP Official Changelog

Downloads

FAQ

- Post #3

Known Issues

We need your help!

Bug Reporting

Additional Help/Support:

XDA:DevDB Information

TeamWin Recovery Project (TWRP), Tool/Utility for the HTC One (M9)

Contributors

Captain_Throwback, Dees_Troy, bigbiff, _that, nkk71

Source Code: https://github.com/TeamWin/android_bootable_recovery

Version Information

Status: Stable

Current Stable Version: 3.4.0-0

Stable Release Date: 2020-06-24

Created 2015-03-28

Last Updated 2020-06-25
[One (M9) Original Android Development] Captain_Throwback:
TWRP now supports flashing of zips up to 4GB in size!

In order for ROM zips to function properly, ROM devs may need to change the way they're used to performing mount commands in their updater-scripts. Many ROM devs like to use busybox to mount system, like this:

run_program("/sbin/busybox", "mount", "/system");

However, on the M9, this will not always be effective, due to the variable state of system when booting into TWRP (more information in the below post). The most reliable way to mount system in TWRP is to use the below command:

run_program("/sbin/mount", "-t", "ext4", "/dev/block/bootdevice/by-name/system", "/system");

Since this calls the mount binary and specifies the proper filesystem of /system, it will work regardless of the mount state of /system within TWRP.

The reason people are having issues booting ROMs flashed without the above command is because custom ROMs typically include a command to format system within the updater-script, like this one:

run_program("/sbin/mke2fs", "-t", "ext4", "-m", "0", "/dev/block/bootdevice/by-name/system");

Notice that this calls the mke2fs binary directly and specifies the filesystem, so this command will run properly and format system. However, when the script attempts to mount system using the busybox mount command, it's unsuccessful, resulting in a failed ROM install (even though there likely isn't an error message) and an empty system partition. The same command format should be used both to format system and to mount it.

So, the solution is easy - replace your busybox mount commands with the direct version noted above. Running it that way should work regardless of the update-binary used, since it's not running mount directly but calling it (this makes a difference to some binaries for some reason). This will even work in situations where system has been mounted read-only by TWRP (more on that in the below post).

ROM Devs - please consider making this change going forward. The above method will ALWAYS WORK. Please use this and discontinue whatever other methods to mount system that you have previously used, as they will have inconsistent results, leading people to flash old versions of TWRP or blame TWRP for their errors.

I know the M9 is a very different device than we're all used to, and the rules have all changed. Let's all adapt to the change together. :).

UPDATE: Thanks to [MENTION=2605798]nkk71[/MENTION]'s patch, TWRP now supports flashing of zips up to 4GB in size! However, for this to work, a compatible update-binary must be used that includes the updated code. If AROMA is being used, it must also include the updated code. Fortunately, he has graciously provided these updated binaries pre-compiled for any that need them. They are attached to this post. Everyone please thank him for his work on this!! :) Additional information can be found here.
[One (M9) Original Android Development] DroidShift79:
Nice, I was able to make a system backup with your beta version. But I'm still not able to get SuperSU installed. Recovery sais installation went fine, but it doesn't.
[One (M9) Original Android Development] Captain_Throwback:
Recovery log?
[One (M9) Original Android Development] DroidShift79:
could you tell me how to get it, Sir?
[One (M9) Original Android Development] Captain_Throwback:
adb pull /tmp/recovery.log

OR

Advanced -> Copy Log to SD. Console output will tell you where it copied.
[One (M9) Original Android Development] DroidShift79:
adb won't find my Device when in recovery mode, why?

. so I copied file to external_sd.
[One (M9) Original Android Development] Captain_Throwback:
Probably drivers. Have you installed the latest ones from HTC Sync Manager (and then uninstalled the program if you don't use it)?
[One (M9) Original Android Development] DroidShift79:
good hint, I'll have to clean the driver mess :D

You have a clou why SuperSu doesn't surrive reboot after flashing with BETA TWRP ?
[One (M9) Original Android Development] Captain_Throwback:
There's no installation of SuperSU in that log.

But if you already have a stock backup, let's do this:

Under Advanced, choose Terminal, press the select button to start it in the root folder, and then type this command:

mount -t ext4 /dev/block/bootdevice/by-name/system /system

Then run the SuperSU installer zip.
[One (M9) Original Android Development] DroidShift79:
does doing this kills the OTA updates? Or are they killed, cos installing the beta version ?
[One (M9) Original Android Development] Captain_Throwback:
Yes it will kill OTA ability (but weren't you trying to root?). So will root. But you have a fully intact stock system backup now, so you should be fine.

No, the whole point of the beta version was to leave system intact if it was previously untouched.
[One (M9) Original Android Development] DroidShift79:
That did the trick. now SuperSU got installed.

Thanks for your help.

Now, If I want to go back and want to receive OTAs again, what are the needed steps?

Is flashing the OTA firmeware.zip enough?
[One (M9) Original Android Development] Captain_Throwback:
You'll need to take the stock system backup you took (from before you rooted) from the TWRP backup folder, rename to system.img, and flash via fastboot to restore stock system (fastboot flash system system.img). That'll restore system to full stock so you can take the OTA (you'll also need to flash stock recovery if you want to do a full OTA update, but the zip itself *should* flash with TWRP and you'll need to flash the firmware manually).

Once the OTA is complete, you can boot into TWRP, take another stock system backup so you have a good starting point for the next OTA, and then either mount system manually to install SuperSU (as above) or flash a custom rooted ROM.

I'm sure you or someone else can put together a guide with the exact steps. After all, this is just a humble recovery thread ;).
[One (M9) Original Android Development] Electronic Punk:
Cheers for this and your reasoning is sound, we are very lucky on the M9 to have 401 (at least) RUUs on our device before most have received theirs!

I will check out the new beta shortly but won't be able to tell you if mounting system is disabled for unmodified systems! Got a one sentence description of how you are doing that? :D

Surely a simpler approach to allow SuperSU would be to allow /mount system but hide it from the GUI or via console a warning displayed, but again beyond that myself -but hopefully [MENTION=631273]Chainfire[/MENTION] will know what to do!
[One (M9) Original Android Development] Captain_Throwback:
The issue appears to be how the SuperSU zip is mounting system. Since TWRP is mounting system, but read-only, SuperSU thinks it should be writable, and doesn't try further attempts to mount it as such. [MENTION=631273]Chainfire[/MENTION] should be able to find a way around it, though, as ROM zips mount system as ext4 and can then write to system with no issues. It's only an issue until system is mounted once in recovery - in subsequent boots, it will be writable normally.
[One (M9) Original Android Development] Rsotbiemrptson:
Hello,

I am wondering if I can do fastboot boot "recovery.img" and do a backup that way to give me a clean untouched copy of my system and recovery imgs. I understand that there is going to be some changes from the old htc ways. Just trying to get something that can get me back to OTA status. With no RUU for T-Mobile yet I want to have a recovery.img as well as system.

Thanks,

Rsotbiemrptson
[One (M9) Original Android Development] Captain_Throwback:
Try it and let us know.
[One (M9) Original Android Development] Rsotbiemrptson:
Hello,

Get my device tomorrow, just doing homework now. Will let you know.

Rsotbiemrptson
[One (M9) Original Android Development] gffmac:
I took a stock nandroid backup with 2.8.6.4, so my plan later is to restore backup with twrp, find stock recovery and flash that back, boot up then see if I have any updates, then flash twrp and make a nadroid backup.
[One (M9) Original Android Development] m03sizlak:
Good luck with that. Even after restoring the clean system backup and the stock recovery the OTA is failing for most people.
[One (M9) Original Android Development] kertong:
Thanks - but that's the part I don't understand. AFAIK, there is no way to flash the stock AT&T recovery right now, is there? I haven't seen any RUUs or stock AT&T recovery .img's floating around (I've looked, but maybe I suck at searching). And I am unable to back my stock recovery partition up, since there is no way to get root without flashing TWRP first, and I can't seem to 'fastboot boot twrp-XXX.impg' to run twrp without blowing out the stock recovery partition...

edit: might be a really stupid question, but what would happen if I took twrp.img and flashed the system partition instead? would it attempt to boot normally, launch TWRP, and allow me to back up the stock/untouched recovery partition via adb shell / dd?
[One (M9) Original Android Development] Captain_Throwback:
One last thing before I go -

Just added this sentence to post #2: "After fastboot flashing the backup file, you *may* also need to restore it in TWRP for the OTA to take." I don't know why that is, but it might make a difference. Give it a shot and post back how it goes. I won't likely be logging on, but I may peek back at the thread and see how things are going.
[One (M9) Original Android Development] m03sizlak:
Well I'll be damned. That did the trick. Thanks!

Question: I don't know what method your TWRP uses to detect an "untouched" system partition. AFTER taking the OTA, will TWRP 2.8.6.4 still detect the system as untouched and allow me to back it up (so I can take the next OTA)?
[One (M9) Original Android Development] B-Man2005:
i want to restore a backup from another m9 i got on the sd card from a friend...

recovery does not see it

can i manage it somehow ??

thanks
[One (M9) Original Android Development] jauhien:
First make a backup, then put your 'strange' backup into TWRP created folder next to the just created backup - and your recovery will start successfully seeing both backups.. :)
[One (M9) Original Android Development] Captain_Throwback:
Yes.
[One (M9) Original Android Development] gffmac:
Would restoring the twrp backup with twrp not be enough? Why is the fastboot flash critical?
[One (M9) Original Android Development] Captain_Throwback:
Questions like this are why I'm taking a break :rolleyes:.

READ POST #2.

I'M OUT

*drops mic*
[One (M9) Original Android Development] gffmac:
It's the also restoring in twrp bit I was questioning as the system is mounted read only ... Or do you mean to restore the other partitions once system had been restored via fastboot.
[One (M9) Original Android Development] solver404:
So many of us understand your feelings on all the levels and glad you are deciding to catch a break. Thanks for everything you have done thus far- not only your development work and site work, but actually answering so many "silly" questions for so many years. It doesn't go past many of us that you modified this recovery to work properly for the M9. Personally, I would still be stuck in stupid land for two weeks now if it weren't for this project of yours.

I have been having such issues updating from SPR .17 to .30, and was going to RUU after work tonight since Sprint users got a .30 RUU today, but since you had asked for feedback, I decided to try fastboot flashing system then recovery restoring system before taking the update. It works, by the way, for anyone that couldn't boot after just fastboot flashing system.

Invaluable advice. Invaluable Captain. :D

That is all.
[One (M9) Original Android Development] B-Man2005:
O Captain! My Captain!
[One (M9) Original Android Development] migascalp:
I finally managed to update 1.32.401.6-> 1.32.401.15 From my backup (TWRP 2.8.6.4)

But not without problems

Flash system.emmc.win -> bootloop

Restore backup via TWRP -> OTA -> Error Mount r / w

factory reset (if I remember correctly)

Flash again system.emmc.win -> OTA via adb sideload

success

I used the recovery 1.32.401.15
[One (M9) Original Android Development] weasley:
Do I need S-OFF to Flash twrp-recovery-2.8.6.0-hima-cptb?

Thanks
[One (M9) Original Android Development] gffmac:
No you can flash in download mode.
[One (M9) Original Android Development] vizzy:
im going to assume we have to re-mount the system using mount -t ext4 /dev/block/bootdevice/by-name/system /system, every time we install a different TWRP? I installed the latest TWRP through download mode and the system was not mounted. So I just assume every time we new install we mount as well? Then going forward for that version mount sticks until you change to a different version?

Just checking im not entering this text for no reason, I would test it but i'm currently at work with no cable
[One (M9) Original Android Development] Captain_Throwback:
It really depends on what you're trying to do.

You should NEVER have to manually mount system. If you've just taken an OTA, system is mounted read-only so that you can take a clean system backup. Once you do that, you can flash the BETA SuperSU to root. Or, you can flash a custom ROM. As long as the ROM's updater-script is done correctly, it should flash with no problem. If it isn't, then you may need to reboot into recovery and flash again, or manually mount system and then flash.

The Beta versions of TWRP linked in Post #2 will detect if your system is untouched. It has nothing to do with what specific Beta version you're using; they all have the same detection built in. So, your post confuses me.
[One (M9) Original Android Development] Slagathor01:
ok:

New One M9 Check

Unlocked Bootloader Check

Install custom recovery......... Do I want 2.8.50, 2.8.6.0, 2.8.6.3 or 2.8.6.4??? Been reading for the last couple of hours, it sounds like I want 2.8.6.4, but I just want to clarify before jumping in....
[One (M9) Original Android Development] hgoldner:
Buried in Post #2; must've taken hours to miss it:

C'mon, people, PLEASE read the thread. It's not that long and you also have the ability to use "search."

I am using 2.8.6.4 and everything is hunky-dory. Do you think you can find the link to that?
[One (M9) Original Android Development] Slagathor01:
Well shizzle, read that post a few times, oh well......

Thanks, I think...
[One (M9) Original Android Development] Captain_Throwback:
Alright, I've again rearranged post 2. This time I set it up as an FAQ, which will hopefully make it easier for people to understand. If not, I'm not sure what else I can do, tbh.
[One (M9) Original Android Development] TMartin:
Can you fly here and do all this for me? Maybe? ;)
[One (M9) Original Android Development] guidogsbn:
I think, there is no way to explain it better. It's easy to understand the whole problem now! Thanks!:good:
[One (M9) Original Android Development] ItsMeMasih:
Crap, I jumped into rooting too quickly and didn't take a system backup prior to rooting. Is there anyway I can download or use someone else's stock T-Mobile US TWRP backup to restore for when I want to take an OTA?
[One (M9) Original Android Development] Captain_Throwback:
Sure, but this isn't the place to ask for it. If you look, there's probably already a thread with what you're looking for.
[One (M9) Original Android Development] Provencebiker:
Thank Captain_Throwback (and all the others). After reading your thread (several times, I admit) all worked flawless with the latest TWRP and SuperSu.

Made also clean system backup to external sd (international version).

Waiting for Leedroid's new release to flash his rom (hopefully tomorrow).

Thanks for all the efforts.
[One (M9) Original Android Development] Roninrc51:
Stuck, :/ verizon ..

Ok, i can get to bootloader menu and toggle download mode, but after flash i get this :

FAILED (remote: 9: SD_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCK)

Ideas?
[One (M9) Original Android Development] miggsr:
...is your bootloader ***LOCKED*** or ***UNLOCKED***
[One (M9) Original Android Development] Roninrc51:
locked, on verizon.
[One (M9) Original Android Development] miggsr:
That's your problem.... You can not flash a recovery if your Bootloader is locked. Since im not familiar with vzw unfortunately I cannot help you unlock your Bootloader. I'd say go try htcdev.com
[One (M9) Original Android Development] hgoldner:
... permission to smack the moron.....

Seriously. You need to put the phone down and get out of here. You are way over your head. Or you have a twisted sense of humor.

My name is Harold and I'm a flashaholic.....
[One (M9) Original Android Development] miggsr:
Granted ??
[One (M9) Original Android Development] Roninrc51:
Gotta love,

Ya know, I'll take the smack.. 14 hr work day, probably shouldn't be attempting anything coherent. Misread with optimism the twrp page posted under the Verizon section... Moron.. Yeah, count on xda to spew elitist drivel. Thx for knocking me back to my senses.
[One (M9) Original Android Development] hgoldner:
Forgiven. The Verizon M9 is okay. Just gotta wait patiently for Sunshine. It'll happen eventually. It always does.

My name is Harold and I'm a flashaholic.....
[One (M9) Original Android Development] billyjonstevens:
Hi guys I apologise if this is noobish or an obvious answer, but I am a noob when it comes to the m9 which is why I'm asking this question.. Im not new to flashing and have been on htc devices since the touch diamond but clearly flashing is somewhat different on this device, I've read the first posts and understand the implications that rooting / installing twrp will have but my question is I've never gone back to stock previously as I've always been on custom roms, is there a reason other than receiving ota's that I would need to go back to stock? I've held of unlocking / rooting etc for now as I just want to be sure of everything, I appreciate the device is early in its life as is the development, any help or advice is appreciated keep up the good work all..
[One (M9) Original Android Development] miggsr:
Well I'd say first off... Wrong place for this post... And as for the reply to your question... Going back to stock is good for taking OTA's, troubleshooting hardware (sometimes custom software doesn't play nice and you can't tell if its hardware or software) , returning device for repair, or you need a change of scenery.

Be sure to read first few post from OP several times make sure you understand it well. If not you'll need to do ruu to get your OTA.
[One (M9) Original Android Development] billyjonstevens:
Great thanks for your reply
[One (M9) Original Android Development] BUBBA DUB'S:
You sir are one funny man! Thanks for making my night reading your witty posts.

Bubba

Also to prevent miggsr from posting his witty banter, read first two posts. If you still have questions reread first two posts. :highfive:
[One (M9) Original Android Development] cbrown245:
KAO ,,,, Hey I thought you got banned ????
[One (M9) Original Android Development] JagSem:
I've taken a backup of the stock ROM and I've downloaded the firmware update to my device. I've not gone any further than flashing TWRP and taking a backup. However, I don't have the stock recovery image for my phone. I don't believe I'll be able to flash the updated firmware manually as I don't have S-Off. Where do I go from here in order to update the firmware and flash a custom ROM?
[One (M9) Original Android Development] BillTheCat:
Cross-posting, because I really could use some help.

Without getting into all the painful details, I wiped all partitions and had to use TWRP's 'Fix Permissions' function to be able to copy a ROM back to the internal storage. However the new flashing just doesn't load right. Thought I'd try to restore a Nandroid image, and that's not working right either. Now, when I boot to ADB and I try to create a folder on the internal SD card by using ADB Shell, I get this:

D:\adb>adb shell

~ # ←[6n

It sure looks like I screwed the pooch somewhere along the line. Can someone help?
[One (M9) Original Android Development] Electronic Punk:
Thats what it the console looks like in TWRP, never understood why :)
[One (M9) Original Android Development] SRQ Rick:
I downloaded and flashed TWRP 2.8.6.4 today, did my backup and saved it to my computer and when I opened the file, there were three backups there. Mine, one from a month ago and one from December last year named this serial number: HT44****7803.
[One (M9) Original Android Development] niceguy0815:
Hello I have installed the newest twrp-recovery-2.8.6.4-hima recovery and wen i do a backup my data Partition is bigger than 8gb.

Dose TWRP in newer versions also include "data/media" / "internal sorage" in DATA Partition backups?

System Size ist normal 1,7gb

My Device is S-Offed Unlocked with Super Cid
[One (M9) Original Android Development] 5m4r7ph0n36uru:
Only thing I know, is that the backup has to include all directories that are present in the factory image, as otherwise the md5 would change and your backup would loose the ability to perform an ota.

As all RUU - at least those ones I downloaded - are 2.1 GB in size your referred 1.7GB to me appearr a bit too few regarding a full backup.

Folks, please correct me if I'm wrong .

Btw. how did you obtain this!?
[One (M9) Original Android Development] gffmac:
Sunshine now supports the m9' :)
[One (M9) Original Android Development] niceguy0815:
No it was S- Offed and super Cid in a Repair center in Berlin Germany.

And i hav locked a bit into it and it seams so the delivery cache is very big folder, it is 3,5gb because now you hav "amr" and "amrx64" folder??

onmy

One M7 with the same apps installed its only 1,2gb.
[One (M9) Original Android Development] bpdamas:
I am trying to flash the system via fastboot and get the error "invalid sparse file format at header magi" and then it seems fastboot hangs. Not sure if this is 2.8.5.0 related or not or if I don't have a valid system file. I am one of the unlucky who flashed 2.8.5.0 and tried to root without a valid system file backup. Any help would be appreciated.

---------- Post added at 02:38 PM ---------- Previous post was at 02:03 PM ----------

Don't mind me. I am an idiot. I just realized it was more than likely hanging because it is trying to download over a 4 GB file. Could be wrong, though. I am letting it run and see if it will work. I am giving it some time before I give up. Nothing to see here.

EDIT: Everything worked flawlessly once I realized it was flashing. However, it did require me to flash through TWRP (I used 2.8.6.4) due to the unexpected contents error. Thanks post #2. I figured I'd post in case anyone else was having similar trouble.
[One (M9) Original Android Development] robshabazz:
Deleted