yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] donmarkoni:
You should have said so. It seems your file manager is to blame. Also, you can't move stock system backup to external SD if it's FAT32 formated, you need exFAT.

There is a thread here, with RUU's and stock nandroid backups, so it's not all so black for you.

Also, there is a S-OFF thread here, so you can forget about limitations and do whateve you want.
[One (M9) Original Android Development] winshen0429:
I have made a nandroid backup and i can't flash it due to read-only problem. I have seen from the OP.

NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.

I have searched my backup files. there is no system.emmc.win. There is only boot.emmc.win and system.ext4.winooo

How can i restore my nandroid backup now?

Thanks
[One (M9) Original Android Development] Boostjunky:
Sounds like you never made a proper backup of system image prior to mounting as read/write.
[One (M9) Original Android Development] winshen0429:
i never put it as read/write. Or I should mount it as read/write before restoring my backup?

And can i know what options should i tick during backup? I know it's stupid to ask. Thanks.
[One (M9) Original Android Development] Captain_Throwback:
If you never mounted system read-write, then why are you trying to restore it?
[One (M9) Original Android Development] winshen0429:
update: Problem solved. I want to restore my backup because i was having problem during flashing custom ROM. Now i can restore the backup by upticking mount as read only. Thanks for your reply.
[One (M9) Original Android Development] Captain_Throwback:
But you still don't have a stock system image backup . . . but I guess you don't need one if you're flashing a custom ROM (and never plan on taking an OTA).
[One (M9) Original Android Development] RootNew:
Emulator problem

im trying to flash the twrp i have s-off and unlocked but its telling me i have a emulator also listed

I cant seem to find it and dont know how to kill the emulator or uninstall it

Any help would be great thanks!
[One (M9) Original Android Development] Adromir:
Do you have Bluestacks, Genymotion or something similar installed?
[One (M9) Original Android Development] bdarius:
so... I recently unlocked my bootloader, installed TWRP 3.0.0-2 and tried rooting with supersu 2.68. The flashing of supersu went fine, rebooted to system and now I am stuck with a bootloop. I made a backup of my stock system image before trying to root, but if I restore it, I still get the bootloop. Is there any way out of the situation? Thanks

m9 is s-on
[One (M9) Original Android Development] Captain_Throwback:
I've heard that there are issues with the latest BETA SuperSU and the M9. Try the stable version (v2.65) and see if that works. What you need to restore is stock boot to get you booting again.
[One (M9) Original Android Development] hallstevenson:
One "issue" was a user trying to install it on a phone with a locked bootloader.
[One (M9) Original Android Development] bdarius:
Thank you, sir. I am going to try the 2.65 later today and see how it works
[One (M9) Original Android Development] alhuang69:
I am using SuperSU v2.65.

Everything is working fine
[One (M9) Original Android Development] jtr01:
i also has a issue i now had no Rom on the phone... TWRP can't Mount /System so i can't install a Rom if i try it the phone restarts
[One (M9) Original Android Development] bryanus:
Error executing updater binary in zip (Can't install any ROM)

Hi guys, I have a new (ATT/SIM Unlocked) m9, and just unlocked the bootloader this afternoon. Now I'm trying to install _any_ custom ROM, but it always fails.

I have tried every TWRP version from 2.8.50 - 3.0.0-2 with the same error every time.

Only versions below 3.0.0-1 will actually load TWRP, though. Versions 3.0.0-1 and -2 say 'failed to boot to recovery mode"

When I try to flash a custom ROM, it gives me an error like this:

Comparing TZ version TZ.BF.3.0.R1-00142 to TZ.BF.3.0.R1-00115
Comparing TZ version TZ.BF.3.0.R1-00193 to TZ.BF.3.0.R1-00115
assert failed: hima verify_trustzone("TZTZ.BF.3.0.R1-00142, "TZ.BF.3.0,R1-00193") == "1"
E: Error executing updater binary in zip '/path/to/rom.zip'

I don't understand what's going on. I've flashed many devices and never had a problem like this before. DO I need S-OFF to install a custom ROM?

Any help/tips would be appreciated. TIA.
[One (M9) Original Android Development] teddy0209:
No you don't need S-off to flash a Rom. I'm not sure about your error, i've never flashed any Rom on my M9 (just stock w/ xposed)...
[One (M9) Original Android Development] Captain_Throwback:
Update your firmware. This requires the specific signed firmware for your variant, since you're S-ON. The ROM you're trying to install is looking for a specific version of the trust zone firmware which you apparently don't have installed. I'm sure the ROM thread from which you got the ROM would have more information on that.

The 3.0.0 versions of TWRP require Marshmallow firmware in order to work properly on the device. If you haven't updated to Marshmallow yet, then you need to use an older version.
[One (M9) Original Android Development] bryanus:
Ahh, thanks so much for that tip! Now to figure out to do the firmware upgrade...thanks again!
[One (M9) Original Android Development] bdarius:
OK, I can confirm, 2.65 does work with TWRP 3.0.0-2
[One (M9) Original Android Development] 2WildFirE:
Agree, 2.65 works fine, all other give bootloop or stuck on boot

Powered by SkyDragon ROM
[One (M9) Original Android Development] cloves:
Question About Restoring TWRP Backup

Hi everyone,

Specs:

- HTC M9 T-Mobile (Running Marshmallow 6)

- unlocked (htcdev)

- Rooted (superSU (beta 2.65) installed via TWRP)

- S-on

Issue installing ARHD Rom, and I want to roll back to my TWRP backup. When I goto restore and pick my backup, TWRP says:

Cannot restore System -- mounted read only

I understand that the new TWRP by default asked me whether to mount in read only or read/write.

So in order to restore my backup, do I have to go into Mount/ and uncheck "Mount system partition read-only"

What impact will doing that have on my ability to restore to stock in the future? I can't understand even after reading the FAQ. :confused:
[One (M9) Original Android Development] jt85:
_________________________________________________________________

I have HTC One M9 unlocked BL, Beta Super su v2.68 rooted, no backups cuz I mounted as r/w on twrp initial install. The HTC was stock prior to unlocking BL, and twrp and super su installs. I have tried to back up multiple times, but it always says( displays everyone below inside of the quotation marks)

"[Back up started]

*backup folder:/data/media/0/TWRP/BACKUPS/HT53ryj01217/2016-03-11--19-58-25/

Backing up system. . .

E:back up file size for '/data/media/0/TWRP/BACKUPS/HT53RYJ01217/2016-03-11--19-58-25//system.Emma.win' is 0 bytes.

Back up failed.

Cleaning up back up folders

Updating partition details . . .

. . .done

* total number of partitions to back up : 1

* total size of all data : 5658 mb

* available space : 17084mb"

The reason I'm asking is I'm running Android 5.0.2., and I would like to upgrade to marshmallow! The problem is I don't know how to go about updating to it. I don't know who, what, when or where about the absolute best highest quality way of doing this( I can be a perfectionist when it comes to something I'm working on).

I did however watch a tutorial on updating Android to 6.x.x., and did as the tutorial said and went to rootjunkysdl.com and downloaded the twrp 2.8.6.0 to my PC. I then launched platform tools>cmdprompt>rebootDownloadmode>fastbootflashrecoverytwrp-2.8.6.0.img» enter.

Then followed the instructions on the phone to reboot to recovery>then install> then twrp2.8.6.0. After the install while still in recovery I went to reboot>reboot system, and it said are you sure u want to reboot no o.s. so after hours of deliberation on whether or not I should reboot. I decided to reboot system and it booted up just fine, but there is no change of anything that I can tell. Then went to the info in phone setting under about device and it says version 5.0.2 as it did before I flashed the twrp I mentioned above. So anyone think they can help me out? Thanks in advance!!! Seriously!
[One (M9) Original Android Development] weinberk:
[MENTION=1162986]Captain_Throwback[/MENTION] -

Having just left my phone in a cab (but gotten it back) and having that fear that my data would get into the wrong hands, would you consider further modifying TWRP to limit the number of pin attempts before it automatically wipes the device? (dare I say it, like Apple does)

Also, Google's device manager will wipe your phone remotely, but if it's encrypted when TWRP boots, it stops and asks for the pin. Is there some magic way for TWRP to know if it's been started because a remote or regular wipe was issued by the OS and just wipe without trying to decrypt data?

Thank you for the consideration.
[One (M9) Original Android Development] Captain_Throwback:
You'll want to talk to the TWRP devs on IRC about that. That's not a device-specific thing you're requesting.
[One (M9) Original Android Development] weinberk:
Thanks for the quick reply Capn. Do you think my ideas make sense and are worth bringing up?
[One (M9) Original Android Development] Captain_Throwback:
It doesn't matter what I think. I'm just a device maintainer - I don't control what goes into upstream TWRP.
[One (M9) Original Android Development] weinberk:
I think those of us here would say, or at least I would, "YOU'RE CRAZY if you think it doesn't matter what you think. You're our hero and we respect your thoughts." !!!! :D
[One (M9) Original Android Development] eskriminal:
Hi guys, I just received my m9 and am in the process of rooting with intent to update to marshmallow (I have Hong Kong CID)

However, after unlocking bootloader through htc-dev and flashing via fastboot twrp 3.0.0-2 - which processed successfully, I'm being given a 'failed to enter recovery mode' message.

I retried the download, and checked md5 and it was fine - any advice?

Thanks in advance.
[One (M9) Original Android Development] Captain_Throwback:
You have to be on Marshmallow firmware to use the 3.x TWRP. Use an older version if you haven't updated yet. I'll have to add this to the FAQ, since it seems to be happening a lot.
[One (M9) Original Android Development] Captain_Throwback:
Updated FAQ #2:
[One (M9) Original Android Development] ratratrat:
Hello! I'm finally Almost ready to root my htc m9. After reading the FAQ, I still have 2 more questions.

1) I don't quite follow bullet 7 in the faq. How to backup stock recovery. To my understanding, is it fastboot flash twrp, and then boot into twrp and find recovery backup option?

2) I read somewhere that SD cards greater then 32gig is not compatible. Is it true? Cause I have an 64. . .

Thanks!!! I'm still a little nervous with the whole process.

I'm on a Full Stock MM.
[One (M9) Original Android Development] computerslayer:
You'll need to fastboot boot into your recovery image file - which doesn't require you to flash it. Then you can backup the stock recovery from there. Here are the instructions for booting your recovery via fastboot without flashing:

- Copy the downloaded recovery image (.img file) to the folder where you have placed your ADB and Fastboot tools.

- Launch terminal (or command prompt on Windows).

- Navigate to the directory where you have placed the ADB, Fastboot and .img file together.

- Shut down your phone and reboot into boot loader.

- Connect your phone to your computer.

- On terminal (or command prompt) window, write fastboot boot <img file name>, e.g. fastboot boot twrp.img.

- Your phone will restart and will boot into the recovery mode.

I'm afraid I don't know anything about any size limit.
[One (M9) Original Android Development] ratratrat:
thx computerslayer for clearing it up.

Will this be also a good time to backup System Image?

Or will I need to have flash twrp first before being able to use that feature.
[One (M9) Original Android Development] jbfountain:
I guess I'm a little behind. I thought with the M9 you can't boot into TWRP anymore. You had to extract the stock recovery from a OTA last time I had to do it.
[One (M9) Original Android Development] computerslayer:
I'm not sure what you mean here. TWRP has been available for the M9 for quite some time.

Perhaps its time for you to post a new thread in the Q&A section so you can explain what you're hoping to accomplish.
[One (M9) Original Android Development] efrant:
Prior to MM firmware, that was the case. If you are running MM firmware, the fastboot boot command has been re-enabled.

http://xdaforums.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720/post65030756
[One (M9) Original Android Development] jbfountain:
That's nice to know. Thanks for your useful reply.

---------- Post added at 05:28 PM ---------- Previous post was at 05:24 PM ----------

You didn't realize what I was asking in my post. I know TWRP has been available for the M9 as I have been using it for almost a year. What I was saying is that it couldn't be booted into TWRP. Twrp had to be flashed before. You couldn't boot into it.
[One (M9) Original Android Development] Captain_Throwback:
I do update the FAQ as these things are discovered (most are actually discovered in this thread, actually), so it might be a good idea to refer back to it occasionally. Especially when I post in the thread and say I've updated it (which I've done on several occasions).
[One (M9) Original Android Development] computerslayer:
Ah - I definitely did not get that from your previous post. That makes sense.
[One (M9) Original Android Development] Adromir:
I have a 128GB SD-Card just working fine to that question
[One (M9) Original Android Development] bigfr0g:
What could possibly be wrong?

TWRP Version 3.0.0.0 works, also every 2.x Version on my HTC One M9.

When I install Version 3.0.0.1 or 3.0.0.2 everything is fine, but I cant boot to recovery anymore after a reboot. A red error-message appears on the boot-screen says I cant boot to recovery.

What can I do or what do you need to help me?
[One (M9) Original Android Development] Boostjunky:
Post # 3, FAQ. Look at number 2.
[One (M9) Original Android Development] Leebert225:
3.0.0.2

Hi everyone,

I updated to 3.0.0.2 via the TWRP Manager and I am seeing an error and a bunch of "jibberish", see screenshot.

https://drive.google.com/open?id=0B6h472CfIX0gYlIySUdwdnpHbE0

Even though there is an error when flashing CM nightly's the flash is successful so that's good. I just wanted to know if there is a fix for this or does anyone else have these errors?

Thanks.
[One (M9) Original Android Development] Captain_Throwback:
1) Screenshot in TWRP is Power+Volume Down.

2) A screenshot isn't as helpful as a recovery log. Please provide one.

P.S. It says in the OP what to do when reporting a bug . . .
[One (M9) Original Android Development] Leebert225:
Thanks, attached log(s) hopefully I did it correctly.
[One (M9) Original Android Development] Captain_Throwback:
Please attach as a text file. What is the twrps file for? Where does it say anything about that?
[One (M9) Original Android Development] Leebert225:
re-attached, I just wasn't sure if you needed that file too.

Sorry I'm not a power user.
[One (M9) Original Android Development] Captain_Throwback:
Where are you getting that twrps file from, and why are you attaching it?
[One (M9) Original Android Development] Captain_Throwback:
I'm not sure what you did to the log, but that's not how it should look. If you just use the "Copy Log" feature in TWRP, and then attach that file, it's sufficient. It seems you've converted the file at some point, which is making it difficult to view.
[One (M9) Original Android Development] Leebert225:
Hopefully this works, sorry about that.
[One (M9) Original Android Development] Captain_Throwback:
Yes, that log is good, thanks.

I'm not sure what that gibberish is about; it seems related to the assert check for the SBL firmware version. I'll see if any of the TWRP devs have a clue about it. In the meantime, do you have a link to the CM zip you flashed? I need to take a look in the updater-script of the ROM to see what it's doing.

To get rid of that /carrier error, you could try formatting Carrier, but I don't know what that would get rid of and if your device really needs it (probably). You might want to copy whatever's on it over to a safe location while booted into a rooted ROM, format it in TWRP, and then copy the files back (that might be too advanced for you, though, so I'd just ignore that error for now).
[One (M9) Original Android Development] Leebert225:
I flashed today's nightly http://get.cm/?device=himaul and yea, the rom still flashes successfully so I'm not going to monkey with things.

Thanks for looking into this, I'll keep an eye on the thread for any updates.
[One (M9) Original Android Development] Golv:
[MENTION=1162986]Captain_Throwback[/MENTION]

But where is dowload link? Is it 1 April joke? :)

Last on https://dl.twrp.me/hima - 3.0.0-2

THX!!!
[One (M9) Original Android Development] Captain_Throwback:
[IMG="Patience."]http://jenrulon.com/wp-content/uploads/2015/02/53219408-300x300.jpg[/IMG]
[One (M9) Original Android Development] BR7fan:
I had that carrier error. To get rid of it,I just downloaded one the builds like viper and let it sign in with google and got to home screen. I deleted ROM and tried flashing cm and other ROMs and the issue was no longer there.
[One (M9) Original Android Development] mfg81:
Hi,

I'm also seeing those weird characters, but in my case, I cannot install the cyanogen nightly. I'm probably doing something wrong, but hopefully one of you can sort me out.

View attachment 3715601

View attachment 3715602

The other really odd problem is that I can't install 3.0.2-0 or 3.0.1-0. It flashes fine (fastboot or twrp) but then the white HTC screen says it failed to boot to the bootloader.

Apologies if I'm repeating something or asking something that has already been answered. I think I'm up to date on this thread.
[One (M9) Original Android Development] Captain_Throwback:
Your firmware isn't up to date, as the error message indicates. Update your firmware and the ROM will flash.

The FAQ mentions the reason for this. Please read it.
[One (M9) Original Android Development] nkk71:
Congratulations [MENTION=1162986]Captain_Throwback[/MENTION]

very well deserved new title :good::good:
[One (M9) Original Android Development] disconnecktie:
The latest recovery fails to create backups for me. I'm on the latest firmware.
[One (M9) Original Android Development] lcronos:
Hi, I have a vzw one m9, and flashed TWRP and CM13. I have found though that when I am using TWRP it "drains" the battery extremely quickly. In under 2 minutes it dropped from >60% to under 20%. I highly doubt the battery is actually dying since the phone doesn't get hot or anything, and when I charge it after booting it "charges" about 2x faster than normal. Because of that drop off though I am concerned about actually ever booting up into TWRP because I have no clue what would happen should it actually hit 0% there, even if the battery is not actually dead. I have seen a thread on that issue from a few years back, and the solutions was to use a newer version of TWRP. The guide I followed had me change the name of the file to twrp.img so I can't find the version number right now, but it was the latest version as of April 19, specifically I believe it was a BETA (in hindsight that may be what is causing this, though it's possible it was recommended because it played best with the m9). Any ideas? If you need me to reboot into TWRP to get information I can, though I'd prefer to try and access it by some other means so I don't mess with the battery status again.
[One (M9) Original Android Development] Captain_Throwback:
If you're saying you're not using the latest TWRP, I would update ASAP.
[One (M9) Original Android Development] lcronos:
Well I feel like a complete moron lol. The guide I was following didn't give a link to the most recent version. It was 2.8.7.1, it looks like it's working properly now. That explains why I was seeing an issue that was fixed I guess lol.
[One (M9) Original Android Development] bpdamas:
Can't install Supersu V2.65

First, let me say I read all of the latest posts (they stopped being relevant the farther back I went). Second, I read all of the FAQ.

I have the sprint HTC one M9, am s-off, locked bootloader, lastest firmware, stock rom, and currently unrooted. I can flash TWRP (3.0.2-0) just fine. Recovery seems to work perfectly. The first time it booted it asked me if I wanted to keep system read only and I said yes. I back a system image backup. Then I tried to flash supersu v2.65 to no avail. It seems as if it works properly but I am not rooted when I reboot and supersu is not installed. I have tried mounting the system, installing supersu 2.65, trying different recovery versions, and still get the same result (no root).

I guess my question is do I have to have an unlocked bootloader to flash supersu even though I am s-off? I have tried many combinations of checking and unchecking mounting the system and it still won't install supersu. Is this an issue with supersu and not TWRP? I did at one point modify a dev block and reset my software status to original but I can't remember if I wiped my phone since then. I am not sure if that would affect what is happening. I have attached my recovery log for any assistance you may be able to give. I simply want to gain root access. Thanks for your help and great work.
[One (M9) Original Android Development] teddy0209:
Well, as far as I know, you need to unlock the bl to be able to modify the boot.img... It is needed for systemless su...
[One (M9) Original Android Development] bpdamas:
That must be exactly why it is failing. I guess I need to unlock the bootloader or revert back to an older su version prior to systemless.
[One (M9) Original Android Development] Captain_Throwback:
If you're on M, the latter isn't an option. You're going to have to backup (to external SD or USB Storage), unlock, restore, then root.
[One (M9) Original Android Development] bpdamas:
Bummer. Thanks for the info and keeping me from trying to install a supersu that won't work. When you say backup and restore, which partitions will make it easiest? Do all I need is system and data?
[One (M9) Original Android Development] Captain_Throwback:
System won't be touched. Data will get wiped when you unlock which is why I suggest backing it up.

Although.....since you're S-OFF, it is possible for you to unlock from a root shell in recovery, which shouldn't write the factory reset action to /misc. To be safe, you could also zero that out (the factory reset command, in case it's there), and then you shouldn't have to worry about backing up anything.
[One (M9) Original Android Development] bpdamas:
I think you just went over my head. How would I go about doing that? I am stumbling through TWRP looking for that and then will try and find the right commands. My guess is set up the root shell and then echo the command from the following link? I'm willing to try if you get me to the right root shell spot in TWRP.

http://xdaforums.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
[One (M9) Original Android Development] Captain_Throwback:
Sorry I went on a tirade there. Yeah, while in TWRP, just follow the instructions in that thread for unlocking the bootloader. You won't need the "su" command as recovery shell is always root. Just make sure you backup data and copy anything you want to save from internal storage over to a PC in case it gets deleted after you unlock.