yashsingh1/xdaforums huggingface dataset:
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] btonetbone:
Using LeeDroid, he has an option in the AROMA installer to choose whether you are on Marshmallow or Nougat firmware. I don't know if Viper is the same or not, so this might be different for you. I also did this originally on 3.0.2-6 TWRP, so again things might be different because the new one functions fully.

But basically I just flashed in TWRP the Nougat LeeDroid ROM, selected that I was on MM firmware, and it worked. I did have to adjust the APN settings in the ROM itself after it booted to get on the network (I think that's now automatic), but that was easy. Since then, I've just updated ROM and TWRP as usual.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] skatin707:
Seems like it wouldn't hurt to give leedroid a try! I watched this video (https://www.youtube.com/watch?v=FZtvdA0wRW0) about viper and was intrigued by it but leedroid seems to be a solid performer too.

I do remember looking at the leedroid thread and seeing the red note recommending latest firmware. Fingers crossed aroma handles all of that!

And now root explorer and TiBu don't see my external SD card but in settings > storage I see it. I'm having hell today...
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] jtf420:
Viper has the firmware selection option too. And the option to choose to run it decrypted or encrypted.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
Just posted 3.0.2-7_UNOFFICIAL TWRP to the Downloads tab. [MENTION=2605798]nkk71[/MENTION] did some code cleanup on the vold decrypt stuff, and I reverted the kernel to a version with the stock f2fs stuff and the texfat module, to be more stable. So, this should be a good, stable build to use going forward. Thus, I've officially removed the "TEST" moniker. You can keep using the previous version if you want. No big difference, imo.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
So here goes (again):

So first off, small notice:

Android 7 (Nougat)

ROM

s will change the decryption mechanism, so please follow the below instructions

(Obviously this does not apply if you are already on "non-matching" firmware and ROM version)

Instructions for upgrading from Android 6 (Marshmallow) to Android 7 (Nougat)

Using TWRP 3.0.2-6

flash Android 7 (Nougat) ROM of your choice

boot it up

it will "change" (for lack of better understanding, at the moment) the encryption/decryption

--> so decryption of your data partition will no longer be possible with TWRP 3.0.2-6

.

Update (for applicable devices) your firmware to 2.xx.xxx.x series

.

Flash TWRP 3.0.2-7 series

3.0.2-7 series is known to work for: Android N ROMs

+

2.xx.xxx.x firmware

It may (or may not) boot on

other/older

firmware

I can neither confirm, nor deny whether TWRP 3.0.2-7 series can work on 1.xx.xxx.x firmware or not, it has not for me, it may have for some.

The above information is from my personal experience, and confirmed working for

me

I'll leave it up to everyone else to choose their own method of upgrading; this is my personal recommendation.

EDIT: Small update, it seems the current version of TWRP 3.0.2-7 will boot on 1.xx.xxx.x firmware.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] jtf420:
FYI for statistical/observational use.

#. Was on Viper M and 1.9x firmware.

#. Had pattern for auth

1. Repacked Sneakyghost's no wipe firmware zip with the latest TWRP recovery(unofficial/test)

2. Updated the phone with new firmware and recovery in dowload mode (zip in extSD). Phone boot looped on red test device warning, as it's viper M still on system.

3. Booted into TWRP recovery. Decryption failed with pattern as Data was from viper M (my guess)

4. Formatted Everything, except for extSD once in new TWRP.

5. Wiped Data to remove pattern.

6. Installed viper N from extSD.

7. Set it up from scratch.

P.s. maybe I have lot of free time or I like a fresh system, I never restore backups. So the above chain of event is acceptable, even expected by me (bootloops etc). It also gives an opportunity to curate the apps and remove faulty tweaks from the past. Most probably a Hangover from the past. HD2, task 29)), member?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] donmarkoni:
Hey mate! :) First of all, thank you and [MENTION=2605798]nkk71[/MENTION] for the great effort. :good:

Unrelated to that, but related to TWRP, I gotta ask you something that is bothering me for quite some time... Well, since M9... TWRP 3.0.0-2 was doing very fast backups/restores, around 120/140 seconds for 5.2-5.3GB of data (system, data, boot) for me. Version 3.0.2-0 for M9 and now 3.0.2-6 and -7 for 10 are 1.5/2.5 times slover. Restore takes almost 6 minutes, aproximately same size, internal/very fast external, no compression of course.

So, the question is: can you look at what has changed between 3.0.0 and 3.0.2 , and if you have time and will, make some hybrid version for me to test? Well, not just me, everybody will be happy with more speed. :D
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
If there were upstream changes that affected the speed of backups, that's not my realm of expertise. I'm just a device maintainer. The TWRP code is out there for anyone to look at, and is open source so anyone that has an issue can troubleshoot it and submit a patch set to fix it. I have no issue with the speed of my backups or restores, so I won't be looking into it. Feel free to take a look at the code and propose some changes to fix it - after all, this is a Development community and everyone's contributions are what makes it great!

P.S. You can always go to the TWRP IRC and ask them if they've noticed any such changes, and maybe they'll look into it for you? You'll have to give them some quantifiable evidence, and demonstrate that it's not just an HTC-device-specific issue as well. With every major TWRP version update we move to newer device trees, so that could very well be part of it too. If so, there's nothing I can do about that.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] CharliesTheMan:
Are you running high speed SD cards upgraded with the times? I'm pulling down around 200-230 seconds for a backup of approximately the same size, but I've got a "V30" SD Card that's UHS 3 (I think) and it seems like backup speed has mostly been scaling to be equivalent to the increased rom size, although I didn't have an M9. However, it seems like my backup is about 1/2 the time yours is taking or maybe a little less than that, so I'm thinking of variables that could be causing it to take yours so long. I'm backing up to both internal and external SD cards and haven't noticed that long of backups.

It's not kernel related I don't think because of TWRP using it's own source for recovery, so I'm trying to think of other variables. Available space (I haven't paid enough attention to speed when internal memory is full vs empty to know if it's a problem on flash chips) or read/write speeds of the memory is about all I can think of, and it's possible some hardware uses different components that just don't like TWRP as much, or maybe it's the device trees. I just figured I'd throw that out there for your benefit and because I know [MENTION=1162986]Captain_Throwback[/MENTION] pays attention to everything
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Sneakyghost:
Lol man yeah task29... That's where my full nuke habit started :D

Sorry for the OT guys... This just made me laugh...

[EDIT]

A note on the speed issue: it's terrible. I'm using a SanDisk 128GB ultra, classed as 10 and UHS-I (not 1). It's quite fast but not the V30/ UHS-III grade. I have been using that on the M9 too. It's been doing great backups, very fast. About 300 seconds or so on M9 and suddenly TWRP started to use 1000 - 1200 seconds (8 to 12 GB backups).

There's been a notable change for sure.

And [MENTION=1162986]Captain_Throwback[/MENTION], you've been hanging out with us long enough to know that neither [MENTION=2977387]donmarkoni[/MENTION] nor me nor anyone from beta team can code. We specialize in observation, mate. Part of our job ;)

So no patches into TWRP Git from us obviously. That was a nice way to tell Don to F off. Could've come from me :D
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] fairyshacker:
will this erase internal storage?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] HD2Owner:
hahaha good man. task 29 rings a bell. :laugh:

a fresh setup is the best setup. i even fullRUU it on major os updates usually. :cool:

thanks [MENTION=1162986]Captain_Throwback[/MENTION] and the others involved for working on twrp for this awesome phone.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] DeeZZ_NuuZZ:
i remember task29 too xD that were times lol,

sorry for OT
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] donmarkoni:
Yes, I have Samsung Pro 32GB UHS-1 and SanDisk Extreme Pro UHS-3 which are rated at over 80-90MB/s both read and write.

Also, same happens with internal memory, its just slightly better, so it's not caused by slow microSD card.

My backup is faster then yours, you misread that. Check results below.

Almost full vs almost empty doesn't yield such a difference, tested that before and now too.

For example I did tests last night with nandroid backup of 4495MB:

1. Backup to internal 137 seconds

2. Backup to external 164 seconds

3. Restore from internal 374 seconds

4. Restore from external 445 seconds

As you can see, restore is catastrophically slow.

Same was on M9 with TWRP 3.0.2, but not with 3.0.0 which would do backup/restore in 100/120 seconds considering the sizes.

Also check [MENTION=1102297]Sneakyghost[/MENTION]'s reply to my post, for confirmation of what's happening.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
Not exactly - I just wanted to emphasize that I'm not the person to talk to about fixing this issue if it's an upstream problem. The TWRP devs on IRC are the people to talk to. Maybe they're aware of the issue, but maybe not. Or maybe firmware & kernel updates have negatively impacted TWRP on HTC devices - either way, I'd start there.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
It didn't for me, but for some it did. You should check the firmware thread.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] keaheng:
does not work on november build 2.28.401.9. successfully flash via fastboot but when I go to recovery it stuck at htc logo for 5sec and boot straight to the phone.

edit: never mind.. I'm gonna try wrp-3.0.2-7_UNOFFICIAL-pme.img and lets see if it works

edit1: okay working now :D
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] knochnkopf:
Flashing TWRP on Stock Build

So I'm seeing a lot of stuff on this thread about which firmware to flash and which version of TWRP to use depending on which version of Android your phone is running. It's all getting very confusing. I'm on stock US Unlocked Nougat RUU so everything is 100% stock. Am I good to go with flashing the latest 3.0.2.7 UNOFFICIAL version and getting ICE installed? Sorry if this was answered somewhere else in the thread.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] ordeniz:
And same question for me,but I am on MM 1.95.401.4 international. I am wondering the steps.

a-Flash ICE

b-Flash Nougat firmware 2.28.401.9 from Sneakyghost's thread

c-Flash TWRP 3.0.2.7 from you

What is the order?Thanks.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] cadkey:
Read on the previous page
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] ordeniz:
Instructions for upgrading from Android 6 (Marshmallow) to Android 7 (Nougat)

Using TWRP 3.0.2-6

flash Android 7 (Nougat) ROM of your choice

boot it up

it will "change" (for lack of better understanding, at the moment) the encryption/decryption

--> so decryption of your data partition will no longer be possible with TWRP 3.0.2-6

.

Update (for applicable devices) your firmware to 2.xx.xxx.x series

.

Flash TWRP 3.0.2-7 series

3.0.2-7 series is known to work for: Android N ROMs + 2.xx.xxx.x firmware

It may (or may not) boot on other/older firmware

So,from this I understand :

From 1.95.401.4 to ICE

First ICE rom

Then update firmware to 2.28.401.9 from Sneakyghost's thread

Last TWRP 3.0.2.7

Is tihis correct?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
Here's the test build: http://xdaforums.com/devdb/project/dl/?id=18249

I have a feeling it won't boot, and if it doesn't, that's all I need to know. If someone could confirm that, I'd appreciate it. If it boots (which would greatly surprise me), please report that too :).
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] buckmarble:
[MENTION=1162986]Captain_Throwback[/MENTION] since the non-US twrp build booted on the US variant, does that mean the kernel you used may work on all variants?(in terms of the device tree blobs)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
The dtbs between the Int'l and US Unlocked versions appear to be identical, so yes, that's the indication.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] buckmarble:
That's excellent news
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
I just realized you said "all" variants. It won't work on the Sprint variant, for sure.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] benny3:
Here's the boot img from the Unlocked version. I can test the recovery later when i get more time
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] jollywhitefoot:
I can test. Just let me know when it's up
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] benny3:
Its up in post 101
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] jollywhitefoot:
twrp-3.0.2-3-pmewl.img boots AND externalSD mounts. I didn't test any further than that.

---------- Post added at 11:10 AM ---------- Previous post was at 11:07 AM ----------

Anyone care to help get this finished? We now have 2 stock boot images that have been uploaded in the thread, but need someone to pull the stock recovery. Anyone?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] sorg:
Can i restore boot backup or flash custom boot in TWRP with S-ON on HTC10?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
That is very interesting. I manually combined the dtb in this one to include Sprint support. I think the problem might be that I need Sprint kernel source for it to boot on the Sprint variant. Guess I'll need to find someone on Sprint to test for me....

Perhaps the retail devices will behave differently than the test devices.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
So apparently the updated version also boots on Sprint. I've updated the official TWRP to include support for all variants (including Sprint). Version 3.0.2-2 is now available from the official download site.

I've also included the patch that reads/writes TWRP Settings from the external SD card, since currently having decrypted data isn't an option on this device (if we get decryption in TWRP working, I'll revert that patch).

I think this should hold us until kernel source is available. Don't forget to pester HTC on social media about it so I can get TWRP working properly and [MENTION=2967322]buckmarble[/MENTION] and [MENTION=4684315]flar2[/MENTION] can do their kernel magic!
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] buckmarble:
I need root/s-off also. Ugh.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Ratief:
I'm I correct that this is from a US phone with version 1.21.617.3? I want to make sure before I attempt to grab the corresponding recovery image. I just want to make sure as the filename doesn't say.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
Yes it is, as is the backup on the page before it.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Ratief:
I'm sharing the recovery image version 1.21.617.3 at the following URL for the next hour or so. I don't know where else to host it.

https://file.pizza/dill-salami-limburger-meatballs

Edit: The MD5 hash is C579578C59B55AE99D8108278C0C1C06
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] jollywhitefoot:
Thanks! Stock recovery, right? You can zip it and attach it to your post If you want

Edit: Too big to attach, I guess
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Ratief:
I didn't think that it would be small enough zipped, but it is!

The MD5 is included.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] FreydNot:
Dumb question, but can I just "fastboot flash recovery HTC10-recovery-1.21.617.3.img" and be back to stock (assuming system was never modified)?

Or does this need to be renamed to "recovery.emmc.win" (and also recovery.emmc.win.md5), copied into the TWRP "BACKUPS" folder structure on the external memory card and then a do a "full" restore from inside TWRP?

My goal is to get back to 100% stock so I can accept an OTA.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] benny3:
Yes you can fastboot flash it just like TWRP and it can be named to whatever you want.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] xchang168:
I am flashed the unoffical verision on android N RUU with s-off. I place the file /system/build.prop with File Manager.But the phone dos not booting after show logo.At fact, I can't doing this on any files now.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
Have you read the FAQ?

Also, you may want to search Google for dm-verity and how it works...:rolleyes:
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] xchang168:
But it works on android M with Twrp 3.0.2.6, and early when I have the M9. I always use this way to make custom rom for myself. For this way, I did not need flash rom,no root,only use the File Manager in TWRP to replace or delete the apks,xml and so on, there is no red text on booting logo.I have do this on andoird M on htc 10, L on M9.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
Has nothing to do with TWRP. You need to patch your boot.img, otherwise it won't boot.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] xchang168:
I am not understand. Please tell me how to do?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] j to the 4n:
This is nothing that should belong in the TWRP thread.

But to answer your question anyway, so you stop abusing the TWRP thread:

You modify the system what leads the rom not to boot anymore because of dm_verity

You need to disable dm_verity in the kernel ramdisk...easiest way is to flash the latest SuperSU..it will do that by default.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] xchang168:
My means I can do that on Android M or L without root or without any except a TWRP via File Manager in TWRP. We know dm-verity is from Android5.x.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] CharliesTheMan:
The boot.img, Randi's, selinux requirements and dm-verity changed for nougat. Before it was kind of like a suggestion. Now it's actually enforced.

Here's a quick Google search result to get your research started https://www.google.com/amp/thehackernews.com/2016/07/android-verified-boot.html?amp=1

Even though the guys above are unknowns in the community, they somehow answered your question correctly. We learned in our kernel experiments when trying to port over a nougat kernel before source, google has taken a whole new approach.

You might find or develop a workaround, but the discussion needs to be moved to a new thread as its not related to TWRP development.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] acupunk:
The latest version will not boot into recovery on my Verizon HTC 10.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] p50kombi:
Well, without any form of log you're not really going to be getting any help I'm afraid...
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] acupunk:
I'm not sure how to capture said log. It hot reboots into the system without loading recovery. Official 3.0.2.6 works fine. I'm s-off.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
If the official works fine, then why are you trying to flash a different version?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] acupunk:
Your recovery is the one suggested for upgrading to viper10 nougat varieties. ^_^
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] xunholyx:
Did you flash the ROM first before the recovery? You should if you didn't

Flash the ROM first, then firmware, then recovery
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] acupunk:
Thanks! Maybe that's the issue. I have not flashed the rom yet. I'm on Verizon, so AFAIK there is no new firmware... But good to know. ROM first.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] xunholyx:
I don't think it won't work without N firmware.....
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] 2WildFirE:
It won't work with without N firmware. CTP told a couple pages before it won't boot on MN firmware.

Powered by HTC 10
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
I did say that, but then I also said I don't know for sure. I can confirm that it does at least boot on MM US Unlocked firmware, though decryption doesn't work with Marshmallow.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] acupunk:
I missed that post. I can confirm it doesn't work with mm firmware for Verizon. ?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
I could've sworn [MENTION=2967322]buckmarble[/MENTION] confirmed the exact opposite...:confused:
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] buckmarble:
I did. I'm using it right now on vzw 1.85 firmware.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] acupunk:
Hmm. I'm not sure what to say. ;)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] xchang168:
My htc 10 is brick by my stupid, I modify the hboot for remove redtext "This build......",and the I turning the S-ON, so......,anyone can help me?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] yldlj:
Try run RUU. Its not twrp related
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] xunholyx:
Just a thought, but maybe US Unlocked converted to work with Verizon is different than a 10 bought from Verizon?

Like I said, just a thought. After some maybe ingesting something that may skew my judgement on this or any other matter. **for clarification please refer to my sig**
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
[MENTION=1102297]Sneakyghost[/MENTION]
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] xunholyx:
I don't quite understand what you are saying here.

Modified hboot I get.

After that.............

You went back to S-On or you were always S-On?

What do you get now that you boot, and say you are bricked?

The information you are giving is lacking in a lot of relevant stuff.

You will have to elaborate on your post if you want help.

ALSO!! This is not the proper place for this discussion. PM me and I'll try to help you out.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] xchang168:
http://xdaforums.com/htc-10/help/htc-10-brick-t3521251

I am sorry.

My phone was S-off before brick,becase I have the xtc2clip.

I use "htc_fastboot oem writesecureflag 3" turning ro S-on avoid lose warranty.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Ivanovic:
You always write writesecireflag3 after running an official ruu
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] mrro82:
What is the big deal with that red text? Why do people just have to get rid of it?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] xchang168:
no, just change unlocked to locked need S-on and then do S-off by the xtc2clip.

---------- Post added at 03:17 AM ---------- Previous post was at 03:13 AM ----------

modify the aboot_signed.img with HEX edit. so it lost signed. it works good before S-on.then I turned S-On,the spl is not signed.