I'm gonna put those two 2.28. versions on the first post, assuming the "Wipe" issue I experienced seems to have been random.
If you encounter a wipe on a NoWipe, please do report and let me know the following info:
1.) S-OFF with Bootloader Locked/Unlocked?
2.) FW version running before flash?
3.) ROM version running before flash?
4.) Last but not least: which of my packs did you flash that wiped your phone?
Stuff to consider when swapping to Android N (7.0.0):
If you encounter a wipe on a NoWipe, please do report and let me know the following info:
1.) S-OFF with Bootloader Locked/Unlocked?
2.) FW version running before flash?
3.) ROM version running before flash?
4.) Last but not least: which of my packs did you flash that wiped your phone?
Stuff to consider when swapping to Android N (7.0.0):
- TWRP is not compatible with Android 7 on the HTC10 yet. People are working on it. This means you need to downgrade to old firmware with TWRP before flashing a ROM or an OTA, because that won't currently work.
- Downgrading firmware from 2.xx to 1.xx has so far worked (testing with Team Venom people) - although there was a brick while downgrading on a phone running an earlier test base. So be careful. We at team venom do not yet feel quite safe with this, neither should you!
- In some scenarios, you WILL lose all your data (a.k.a have a wipe) even if you use the NoWipe - the exact scenario isn't clear yet, I am still looking for info to figure this out. Most likely using 2.28 NoWipe on a 1.95 based FW and ROM setup is causing a wipe - the guess goes towards changed encryption causing it).
- Should you ever encounter a "Semi-Brick" where you can still get into bootloader-mode but NOT into download, recovery or system, you can use the Bootloader mode to flash all images of a firmware pack manually by running "htc_fastboot flash recovery recovery.img" (there is a full list of flash commands and corresponding images somewhere, but basically its the image name that is the flash command, e.g. for recovery its "flash recovery recovery.img." and for adsp its "flash adsp adsp.img").
- This type of Semi-Brick happens when people try to swap out keymaster-image, e.g. flash keymaster from 2.28 into 1.95 environment or vice versa (people trying to get TWRP to work did that and broke their phones with that), but it is likely that mixing other firmware images from different generations can also cause this or worse. Little reminder: the HTC10 is quite the finnicky device - it really doesn't like non-standard procedures. It easily breaks.
Last edited: