yashsingh1/xdaforums huggingface dataset:
[HTC One E8] tom7647:
above rom installed with flash man software.. in flash man i know my device refurbished !! after flashing rom . my device bootloader 3.18 change to 3.19 / all of my problem for this.3.18

now your rom and every rom can install / your rom is the best for every user / nfc not working but not important for me

you are great person you are best:highfive:
[HTC One E8] dapolicy:
Great work

Just installed the rom on e8d, it's running smoothly. Great work. Thanks
[HTC One E8] tarkzim:
How about NFC?
[HTC One E8] dapolicy:
I don't use NFC so I haven't been able to test it
[HTC One E8] tarkzim:
If it's showing in your settings and can be toggled, then it's basically working.
[HTC One E8] dapolicy:
It's showing and can be toggled on and off
[HTC One E8] tarkzim:
Thanks so much for the confirmation, mind if I know your actual variant?

AFAIK some dual/single sim variant ships different nfc chip, I want to collect all info about it to make an automatically compatibility checking scripts.
[HTC One E8] dapolicy:
Its m8sw
[HTC One E8] SWEVEX:
NFC doesn't work, and every time the phone is restarted, the Micro SD is corrupted, I use exfat
[HTC One E8] tarkzim:
Okay, i need your variant info to fix the NFC problems.

can you give me your MID and your model?

adb shell
getprop | grep mid
getprop | grep product

Run the above command from PC with MY TWRP booted and plugged into the PC then let me know the result.

I have no idea about the SDcard problems for now...
[HTC One E8] SWEVEX:
htc_mecdwgl:/ # getprop | grep mid

getprop | grep pr[ro.boot.ddrmid]: [(0x1)]

[ro.boot.mid]: [0PAJ40000]

ohtc_mecdwgl:/ # getprop | grep product

[ro.build.product]: [htc_mecdwgl]

[ro.product.board]: [MSM8974]

[ro.product.brand]: [htc]

[ro.product.cpu.abi]: [armeabi-v7a]

[ro.product.cpu.abi2]: [armeabi]

[ro.product.cpu.abilist]: [armeabi-v7a,armeabi]

[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]

[ro.product.cpu.abilist64]: []

[ro.product.device]: [htc_mecdwgl]

[ro.product.locale]: [en-US]

[ro.product.manufacturer]: [htc]

[ro.product.model]: [HTC One_E8 Dual Sim]

[ro.product.name]: [omni_e8]

[ro.vendor.product.brand]: [htc]

[ro.vendor.product.device]: [htc_mecdwgl]

[ro.vendor.product.manufacturer]: [htc]

[ro.vendor.product.model]: [HTC One_E8 Dual Sim]

[ro.vendor.product.name]: [omni_e8]
[HTC One E8] tarkzim:
TEST build released

[MENTION=10950289]tom7647[/MENTION] [MENTION=7897653]SWEVEX[/MENTION] [MENTION=5958636]dapolicy[/MENTION]

Alright guys, i hope you can try my TEST build via my TWRP, to see if NFC works for every case that you've reported it was not working,

this build will automatically detect your variant and setup the NFC packages for your device so that PN547 won't effect PN544, and vice versa.

SINGLE SIM: HERE

DUAL SIM: HERE

If you encountered any flash error please attach screenshot of TWRP and recovery.log

Thanks.

#UPDATE: Fixed an installation issue, re-uploaded.
[HTC One E8] dapolicy:
Unable to install

I was unable to install it. It ended with error 6
[HTC One E8] tarkzim:
I just re-uploaded it, link updated!
[HTC One E8] Natxus:
Tried both the Unofficial & test builds.....

First of all, thanks a lot for all you work - you are amazing.

I flashed the unofficial build - the one posted by you on the first page of this thread. It shows NFC in my quick toggles (NOT grayed out) & also in settings, but I am unable to toggle it.

I also tried your test build, and the NFC option is grayed out in quick toggles & in settings there is no tab for NFC at all!
[HTC One E8] dapolicy:
unable to download

I'm unable to download from the link u sent, it says 404 not found
[HTC One E8] tarkzim:
Can you give me your variant info like a few post earlier?

But i actually update the link, i will make a new Test build soon.
[HTC One E8] dapolicy:
OKay, I also noticed that the rom lags sometimes, see if you can correct that in your next build. My variant is m8sw, Mec_dugl. Thanks a lot
[HTC One E8] tarkzim:
Okay, here is another updated TEST build with some minor nfc adjustments:

SINGLE SIM: HERE

DUAL SIM: HERE
[HTC One E8] warper99:
Thank you so much for the ROM build ??

I installed the 2020/07/13 build using your TWRP build. The ROM is basically stable with only several animation hiccups here and there but can be made more fluid.

Dual SIM works, NFC works as it can receive beam from another phone and can be toggled on and off. I can make short phone call and end it successfully. Data on lte and 3g also works well.

This build can recognize a half filled SD card, but if I tell it to use it as portable storage, it will hang for a while and cannot use it. Even a format command on this ROM doesn't make it usable, the card is just untouched and the content on the card is still intact and accessible on a PC.

The camera app on this build is usable but the hdr mode is not always working. Sometimes the app will close itself because of "media server is closed/unavailable".

My unit is M8SD, Vietnam version:

version-bootloader: 3.19.0.0000

version-baseband: 1.24.30306251.15G

version-main: 2.35.425.6

version-misc: PVT SHIP S-ON

product: mec_dugl

platform: hTCBmsm8974

modelid: 0PAJ20000

cidnum: HTC__059
[HTC One E8] tarkzim:
Thanks for your useful feedback, can you take logcats while the camera HDR problems or SDCard problems happens?

That'd be helpful for solving those issues.
[HTC One E8] Natxus:
Sorry for the late reply....

Sorry for replying so late.

my device is m8sw, htc_mecdwgl.

After flashing this test build everything works perfectly except the sd card.

Camera is fine when using Footej camera 2, NFC is working fine.

The UI is somewhat smooth with little of jitter, to get over this I overclocked my CPU & that gave a significant performance boost.
[HTC One E8] warper99:
I have attached the logcats for SDCard issue. This time the card is inaccessible after being formatted by this build.

I can't reproduce the camera app stability issue (app auto closed), but I still have to press the HDR button once to get a real preview on screen, otherwise the preview pic is too dark for indoor scene.

On my unit I experienced DT2W failure after several uses. Only reboot will make DT2W works again temporarily.

Thank you for your kind attention.
[HTC One E8] tarkzim:
I can't seems to download the attachment, maybe it's XDA website problem?

for HTC gestures: you have to lift your phone before double tapping your screen to trigger the gesture actions.
[HTC One E8] warper99:
Thank you for your notice. Please get the file here

Yes, I have lifted the phone and tilt it to normal usage position before double tapping the screen. It works perfectly for several times only. Reboot will resolve the problem temporarily.
[HTC One E8] tarkzim:
Okay thanks, i've seen the crash logs, but no idea for now,

I can't even reproduce this on my Desire EYE either (same hardware and sources)
[HTC One E8] warper99:
Perhaps my hardware is defective.
[HTC One E8] :
Nope. I have the same problem. It doesnt response after some time. So i think dt2w is kinda buggy.

My second issue. First (left) half of brightness slider do nothing. Brightness is the same 0% (or what is the lowest number). So 0-50% brightness numbers = in reality is the same lowest brightness and its only changed when 51-100% = from 0% (lowest) to 100%.

My english is bad. Maybe someone can understand and confirm or not.
[HTC One E8] warper99:
Thank you. I can confirm your second issue about brightness. There is a hint about it on my posted logcat.
[HTC One E8] tarkzim:
No idea about DT2W issues, but i will try to tweak the auto brightness values.
[HTC One E8] vaezmath:
hello

I get error 7. no MD5 file found. How I can solve it
[HTC One E8] tarkzim:
new build released

Updated to Android 10.0.0_r41 with August security patches.

Upstream updates and fixes.

Optimized adaptive brightness.

Added MEMCG kernel patches, switched to LMKD for better performances.

Fixed NFC for more variants (htc_mecul_emea, htc_mecdwgl)
[HTC One E8] dovah15:
SD card fs

Thanks for your amazing works! :good::good:

My 64GB SD card couldn't be accessed after formatting, I tried:

1. fat32: the SD card is detectable, but it hangs when I try to access the SD card via a file explorer

2. exfat: the system keeps showing "SD card corrupted" :crying:

3. NTFS: seems working... but not sure whether it is correct
[HTC One E8] arsham25:
I installed this on HTC One E8 Dual Sim (M8sw)

sim card in not working.
[HTC One E8] slash1432422:
Hey guys, i have installed this ROM, and had serious heat problems, any of you have had them? I went back to los 16, and there's no more heat, and i may be doing something wrong. Greetings!
[HTC One E8] vh1981:
very good, it works perfectly. Thanks you!
[HTC One E8] tarkzim:
new build released

Updated with September security patches.

Upstream updates and fixes.
[HTC One E8] Pr@yag:
Thanks you

Hi, thanks for the rom

I got 2 problems

TWRP -- It freezes while formating cache

and second is 32gb sdcard is not working , It works with sense based rom i was using earlier,

It has weird problem i am able to write on sdcard with full speed but can't read sd card even when using MTP (Windows PC)

I tried all file format fat32, exfat, NTFS

It read speed is very slow, but it was fine with Sense based rom, i tried with other devices and Sd card works

Again to confirm its not sd cards fault i also tried another 16 GB sd card same issue

Device is M8SD

Indian version

Thanks
[HTC One E8] keeper18:
Perfect rom and works like a charm but i used older version of TWRP 3.1 or 3.0 because of bootlop or freeze !
[HTC One E8] gugepr:
You can see in his github device codes, e8 only support htc_mecul (htc_asia_tw :6.0.1 ) e8d only support htc_mecdug ( htccn_chs_cu :5.0.2 ).
[HTC One E8] iOriginals:
I respect what you do, it's really great. This is the best rom made for this device, I'm not exaggerating. But I haven't used lineage os 18.0 yet.

There's a problem, I think that's the general problem with lineage os. Screen mirroring does not work, please consider this if you are considering updating in the future.

There is a problem about TWRP 3.4.0.0.

I'm restoring the backup I made, but the device remained on the boot screen, it didn't open, I had to flash the ROM again. Is there a solution?

Thank you @tarkzim
[HTC One E8] sun9xhd:
Thanks you very much ^^

smoothly <3

Im from Viet Nam

my phone : HTC E8 Dual
[HTC One E8] lavnishxda:
No signal.. used different Sim cards even then no signal.. please help..
[HTC One E8] zaqiezsbelelzsinski:
I've flash the rom for E8 dual.. it's very smooth, but for me there are one problem. SD CARD detected, but cannot be format, if i format the sd card, very long time and the result is sd card is corrupt and make device very lag.

And I try to SD Card format as internal storage, it's not work, SD Card says Corrupt and system lag.. if you are willing to be able to fix the as internal format, because the ROM storage for the HTC One E8 dual is only 16GB .. I want to get more storage .. :)
[HTC One E8] lavnishxda:
Bro.. Have you tried SIM card in it?? Actually i am not getting any signal..
[HTC One E8] Artyom K:
Which ROM is the fastest and more stable if all I need is Android 7+, phone, camera, bluetooth, WiFi, GPS and don't care about anything else?
[OnePlus 7T Questions & Answers] ystokar:
Can someone please upload as i accidentally rebooted after update and lost root
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] trelokeeper:
The procedure is very simple. DFE or OFOX are NOT required. I myself flashed TWRP on an encrypted device and it boots and works as expected. Also twrp does not go away if you follow the steps correctly. No format needed either. Just remember your password.

0. First of all an unlocked bootloader is required. If this is your first time, go to miui.com/unlock. Backup your personal data before unlocking.

1. On windows install ADB DRIVERS and download PLATFORM-TOOLS and TWRP. Also download Magisk and move it to the phone, or to a type C usb stick if the device is encrypted.

2. In Developer Options Enable USB Debugging, then reboot to fastboot (Vol Down + PWR Button).

3. Connect the device to PC. Extract the platform tools folder and in it press Shift+Left Click and open a powershell window. Type

fastboot flash recovery [twrp version name]

4. Type fastboot reboot and hold Vol+ to go staight into TWRP.

5. From there flash magisk, wipe caches and reboot to system.

6. Come back here and hit that thanks button. :good:
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] kibria.mgk:
It was always the trick to survive twrp is to boot into recovery and flash magisk. Anyway, good to have a clean thread.

Mi 9T Pro ll Tapatalk
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] hoopsnake:
Hasn't this been the preferred method since forever? And dfe just isn't needed at all encrypted unencrypted doesn't matter you can still flash magisk, and since when would twrp not work on stock miui roms?

It's just a update of a skinned Android, not a major android os update like android 11, really very little has changed to warrant making this thread, sorry.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] trelokeeper:
Preferred? I think it's the only one. But many people are asking about miui 12 and what's changed. Many things have changed with Android 10 and/or miui 12 in many other xiaomi devices and extra things are needed (especially on mediatek devices). Also there are some lies being spread about the need of DFE and alternative recoveries as "better".

Not everyone is familiar with the method of rooting and no one cared to create a straightforward how-to without spreading BS with idiotic recoveries and unnecessary things. Have a nice day. ;)
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] Snah001:
Nothing changed regarding unlocking, flashing TWRP/Orangefox and rooting regarding the 9T Pro since it's release.

There is NO special method for Miui 12 and the method is overall as good as the same for all Xiaomi/Poco devices.

And the "many people" you mentioned is just 1 person who asked for it in the Questions/FAQ section so no need for unnecessary cluttering of threads.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] AvgZing:
It sometimes takes a while after flashing magisk for the phone to boot up. Make sure you double check that it was successful by using the Magisk Manager app!
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] hoopsnake:
Yes but is it really relevant to discuss changes on other devices on this forum? No

If those people can't do some simple basic research they shouldn't be rooting in the first place it's designed to be simple and easy and if people can't get that they should have never unlocked their bootloader in the first place. Nothing but clutter here. Give one example of someone speading as you say "lies" about dfe.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] jugul:
Is there a way to fix the "ctsProfile: false" ?

Tried a couple modules but they didn't work.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] zgfg:
First of all, make sure that Magisk Hide option is enabled in Magisk Manager settings (reboot afterwards) - but if it's not enabled then Basic Integrity would also fail

Problem with CTS Profile failing started about month ago (it has been thoroughly discussed in the general Magisk thread) when Google enforced Hardware backed attestation for CTS Profile (for certain phones / stock firmwares). In that case Magisk Hide cannot hide that Bootloader is unlocked and therefore CTS Profile fails

If so, try how it works for Mi 9T, MIUI 11:

https://xdaforums.com/showpost.php?p=83035713&postcount=40681

In short, install Magisk Hide Props Config module and use its option to delete ro.product.model and reboot afterwards.

The post above describes also how to get back Device is certified in Google Play settings, as well as about a sidefect with Settings/About that will no more properly display your phone model

There is a more 'generic' fix you will also find a link in the post above, to use a particular hardwareoff module for Magisk but that module redefines several ro.product.* props (not only ro.product.model), to cover for other phones like Samsung, etc - IMO, better not to redefine props whose redefinition is not needed for MIUI to pass CTS Profile
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] jugul:
That worked. Thanks!
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] BhagatManan:
Hey there I am a completely newbie in this thing, can you please guide me through dm's or anybody else there to help me . I am from India I bought k20 pro in alpha sale and it's warranty is now over so I wanted to root my phone.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] Marco2701:
I patched the b0ot file of my ROM with magisk and then I flashed it with fastboot. My devices is rooted but I have a issue with WiFi, suggestions?
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] kedzior94:
I'm install twrp on powershell. I got information, is it succesful and when i want to go to recovery i see only miui recovery,. Not twrp. Where is a problem? Bootloader unlocked
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] nigol:
Hi, through OrangeFox I tried to install the version miui_RAPHAEL_20.8.7_e721f66562_10.0.zip on my MI 9T Pro, starting from miui_RAPHAELEEAGlobal_V12.0.1.0.QFKEUXM_68e06ebeaa_10.0.zip.

Apparently everything went smoothly, but when the reboot starts again with OrangeFox.

Can someone help me?

Thank you

nigol
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] zgfg:
Did you Format (not Wipe) Data?
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] mustali:
if i just use rooted miui , do i still need to flash dfe? what are the benefits of decryption?

what are problems with leaving encrypted partition... pls help
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] zgfg:
Just for rooting you don't need DFE, nor to format (neither to wipe) Data.

You need it if you go to flash custom ROM

Btw, rooting can be done without TWRP, just by patching boot.img and flashing the patched image from Fastboot
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] nigol:
No, I just installed the zip with OrangeFox.

How can I fix it?

Orange restarts every time you restart ...

nigol
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] zgfg:
Try to Format Data from TWRP: Wipe, Advance, Format Data
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] nigol:
ok thanks, I'll try

nigol

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

On OrangeFox in the Wipe directory there are only these entries:

Dalvik / ART Cache, Cache, System, Vendor, Data, Internal Sorage, USB-Storage.

Which entries should I format?

Thank you

nigol
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] zgfg:
I'm no more using OF, you are probably in the right tab - or not.

It is important that is says "FORMAT", not "Wipe" - Wipe is much less than Format

There must be something like Advance and then FORMAT (I don't understand why ppl mix it with Wipe, it is not the same), and there you must choose to FORMAT DATA - nothing less/different or more than that
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] mustali:
Thanks for prompt reply.

Will I need to falsh patched boot after every ota ?

Will magisk modules work perfectly without twrp flashing ?

Similarly will the OTA work without orangefox recovery? (Read somewhere that to get OTA updates ofox is required)

Also, can you point me to the thread that gives stock boot patching instructions.

Thanks again
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] zgfg:
There was one under Guides here on Mi 9T Pro, you can search for (yourself), and two under Mi 9T

Method is absolutely the same, not depending on Xiaomi phone or MIUI version (at least since MIUI 10).

In short (some points more than there):

- Download zip/recovery (full, 2,4 GB or so) corresponding exactly to your installed MIUI firmware:

https://c.mi.com/oc/miuidownload/detail?device=1700361

- Open that zip and extract boot.img

- alternatively, if you already have TWRP, make backup of Boot partition and use the file boot.emmc.win instead of boot.img (you can copy and rename to boot.img, but names do not matter for patching)

- Alternatively, disk-dump from Fastboot:

>> dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img

it will create boot.img on the phone, Internal memory

- Install Magisk Manager app (latest Stable or latest Canary):

https://github.com/topjohnwu/Magisk

open and go to Install Magisk, take Patch boot img, from three options leave the first two checked in: Preserve AVB and Encryption but uncheck Recovery option

- Flash the resulted patched_boot.img:

>> fastboot flash boot patched_boot.img

or Install (Install Image) from TWRP to Boot

- Boot to Android and start using Magisk

You flash Magisk modules from Magisk Manager, they have nothing with TWRP, no matter if TWRP installed or not

Before OTA you must restore stock Boot (instead of the patched with Magisk), so follow as above but flashing/installing your original boot.img instead.

Also, OTA requires stock Recovery, hence flash/install stock recovery.img over TWRP/,OrangeFox if installed (you can also extract recovery.img from zip/recovery package).

Once upgraded by OTA, patch and flash its new boot image and continue using Magosk and all your previous modules, and everything

Alternatively, do not accept OTA (disable automatic install from System Update) but download the full zip/recovery firmware corresponding to OTA, extract and patch its boot image (as described above), then from TWRP:

- flash zip/recovery firmware

- do not reboot but also flash its new patched_boot.img, then reboot ro Android: it will preserve both TWRP and Magisk (and all apps, settings, data)
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] zakariya tomal:
Sadly the magisk link isn't working, anyone can provide one please?
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] zgfg:
Link from my post one above yours does work:

https://github.com/topjohnwu/Magisk

Scroll down and download - see the screenshot.

A moment ago downloaded both Stable (7.5.1) and Canary (292) Magisk Managers.

Official distribution of Magisk is only through GitHub (make sure your firewall, ad-blocker or something does not block you access)

Once you install Magisk Manager, it will also need access to GitHub to install Magisk
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] zgfg:
If you are only installing Magisk, you should not format/wipe anything

If you're switching the ROM (like going to custom ROM), you must FORMAT DATA

Better use the official TWRP from TWRP.me
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] Doren18:
It was not workiing for me at started i forget one previous installation of magisk be sure no residual app for flashing work properly !