yashsingh1/xdaforums huggingface dataset:
[Redmi Note 10 Pro] Elinx:
Your problem is imho the encryption of the custom rom which happens with starting up that custom rom.

A custom rom has indeed a vendor too.

So imho the best chance is to flash vendor after custom, but before you start up that custom.

With format data you remove the encryption. wipe isn't enough
[Redmi Note 10 Pro] Conundroy:
You'll need to extract dtbo.img and boot.img from MIUI13 (13.0.15.0 worked for me), flash those 2 to dtbo and boot respectively in TWRP and you should have touch input back on any custom ROM. I found TWRP touch input to still be broken even with those 2 images flashed, if you have usb otg on hand you should use that with TWRP.
[Redmi Note 10 Pro] Elinx:
(y)

Flashing an original kernel from a working Miui rom came to my mind later too, but also thought that a Miui kernel wouldn't work with a (non_Miui) custom rom. Which custom rom had you flashed?
[Redmi Note 10 Pro] Dreedi:
Thanks a lot @Conundroy , the touch screen works when I flash boot.img and dtbo.img after the Custom Rom

However, I have a new problem :

Now I have no lamp (not accessible), no camera (crash), no sound

On several Customs Roms it is the same problem (CrDroid, ArrowOS, ... )

I don't know how to solve this ?
[Redmi Note 10 Pro] Sheist!:
If fts_ts is the FocalTech touchscreen, then my RN11 Redmi Note 11 Global has the same name, vendor and product, and ID 2. (with qpnp_pon ID 3). Touchscreen works with fw_spes_miui_SPESGlobal_V13.0.6.0.SGCMIXM_d8718d8a07_12.0.

My RN10P has the gtx8/goodix_ts.

Using the A13 crD9.1 recovery on both my phones; I encountered issues with TWRPs on both RN11 and RN10P.

I am also interested in seeing if someone can create FocalTech drivers going forward, assuming just flashing its fw does not "fix it" for anyone.
[Redmi Note 10 Pro] s3andnexus5:
I just got the note 10 pro 8/256 and the touch screen doesn't work with the newest version of twrp and it doesn't work with the newest version of crdroid as of this message. Today is march 23 so whichever version is closest to that day. I can only use the phone with a mouse connected.

I'm not a developer so can't really help. Unless there's something you can tell me to do. I can flash magisk to root the phone, but I'd have to do everything with a mouse. I can follow directions if you want me to. I'm Just a user who loves flashing custom roms. As of now I kinda have a paper weight, I don't know why but I'm unable to flash any stock roms, including the eu version. I can't use the official flash tool because my computer won't download the drivers needed for the it to work. I can ONLY flash custom roms. If I flash a stock rom, it just boots into twrp like it has no operating system.

Is there any time table on when this new Note 10 pro display will be worked with? Such a bummer that my new phone that I was expecting to be able to use custom roms on is actually unusable at this point for me. I just spent $250 plus tax on this phone.
[Redmi Note 10 Pro] Fostel:
I just ordered sweet last night from Xiaomi UK and later read all these FocalTech touch and different camera chips (Sunny) stories. Heartbreaking as I planned to use it with Lineage OS. Not sure what I will do yet. Will check with Device Info HW when the phone arrives. Considering returning if the hardware does not work with custom ROMs.
[Redmi Note 10 Pro] Fostel:
https://xdaforums.com/t/xiaomi-sensor-lottery-the-ultimate-poll.4524979/
[Redmi Note 10 Pro] YuRuMii:
what roms did you try? stock eea rom work? or eu rom? im still waiting for my bootloader to be unlock.
[Redmi Note 10 Pro] unlokomukuerdo:
Custom roms are incompatible.

No problem with miui roms, If you want to flash with custom recovery you will need a mouse cause touch dont work
[Redmi Note 10 Pro] fobtob387:
256gb variant works fine with ROMs and recoveries, I'm running LineageOS and TWRP on my 256gb RN10P. It's the specific display hardware which is the problem, not related to storage.
[Redmi Note 10 Pro] Fostel:
Mine came with goodix_ts so I should be safe.

Your problem is touchscreen related. AFAIK there is no driver for FocalTech 'fts_ts' in custom ROMs yet.

You gotta replace the phone or wait for development.
[Redmi Note 10 Pro] unlokomukuerdo:
The custom roms don't work for me, they all fail in something, camera, sound, WiFi..., flashing the boot.img and dtbo.img from stock rom fixes the touch problem
[Redmi Note 10 Pro] pnin:
FYI, I have a Focaltech (fts_ts) panel and I'm currently on latest stable Xiaomi.eu (14.0.1.0.TKFMIXM) and touchscreen works alright...

EDIT: This OrangeFox R11.1_3 Unofficial recovery works fine on Focaltech devices (https://github.com/basamaryan/android_device_xiaomi_sweet-TWRP/releases/) -- to date, it's the only custom recovery that does....
[Redmi Note 10 Pro] Dreedi:
Yes the official Roms as well as Xiaomi.eu works but not all customs roms work with the touch screen.

If you flash boot.img and dtbo.img the touch screen works with the custom roms but there are new problems :

- No Sound

- No Camera

- ...
[Redmi Note 10 Pro] Fostel:
Just to let you know, the two of the Xiaomi Redmi Note 10 Pro (sweet) 6GB RAM 128GB ROM that I ordered in April 2023 from mi.com/uk both came with a working goodix_ts touchscreen, ln8000 charging board and Samsung K6 38 display. Mi UK had them on sale for a few days, so I got one at 159 with additional coupons.

Now. Unlock, flash, root.
[Redmi Note 10 Pro] hy00i:
this thread is dead?
[Redmi Note 10 Pro] Mayuna:
Hopefully not. It would be a real shame if we would not be able to support fts_ts since newer models do have it.
[Redmi Note 10 Pro] alcadon:
hi got same pb with redmi 9...

inputs are:

mtk-kpd

fpc_irq

accdet

nvtcapacitive touchscreen

uiinput-fpc

i thought abt a solution but i dont know if this works with recovery...

use a pc app to have the functions on screen as a distant control on pc
[Redmi Note 10 Pro] rumhojake:
I also encountered same problem. No touch response in custom recovery either twrp or orangefox.

Initially I installed orangefox recovery, it was working well till i installed Pixel Experience Rom with Pixel Experience Recovery. Pixel Experienced Recovrery Replaced my earlier installed orange fox recovery and now when i tried to install again - no touch response encountered. I tried numerous time but failed and then even i tried to installed STock miui global rom but no result at all.

finally I accepted this issue and moved to Pixel experience recovery and installed EvolutionX android 13 AOSP based custom ROM. Touch of Pixel Experience Recovery is working fine with limited option as recovery but worked done for custom recovery
[Redmi Note 10 Pro] fobtob387:
Touchscreen issues with FTS has been fixed with custom recoveries, kernels and ROMs. The RN10P Telegram group has all the info needed.
[Redmi Note 10 Pro] hy00i:
ok .. thank you... (just an average RN10PRO user) will try this when I got home 👍 been months since waiting for someone to help tweaking on the custom recoveries.
[Redmi Note 10 Pro] rozsalyib:
On Redmi Note 9 I replaced the LCD Digital Display Digitizer Assembly with a brand new one that I got from aliexpress. Currently on MIUI image V13.0.2.0.SJOMIXM_20221013 and my touch screen doesn't work. Before I was on custom ROM. I attached the Input page from Device Info HW. Please let me know what else I can try to regain the touchscreen. Could be a hardware issue since I don't see in the list anything that ends with _ts ? I used a logitech mouse to navigate to make this screenshot.
[Redmi Note 10 Pro] Sheist!:
Is this one group on Telegram? Anything similarly posted on XDA with a developer approval here? I'd like to see what actually exists since we do not yet have a kernel with Xiaomi code (for FTS issues) on XDA that has been tested and is ready to go.
[Redmi Note 10 Pro] fobtob387:
Most community progress is on Telegram, XDA is basically dead in comparison unfortunately.
[Redmi Note 10 Pro] rozsalyib:
Thanks. I posted to Telegram: https://t.me/HelioG85_Unified/795947
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
Hi guys,

I really love RR and since my wife still has her Galaxy S8 and since there seems to be no one else who is willing to maintain the latest Resurrection Remix ROM for the Samsung Galaxy S8 for Android Q, I offer you this unofficial version.

-/\-/\-/\-/\-/\-/\-/\-/\-/\-

Note:

By downloading this ROM you take full responsibility of all consequences by your own!

I'm not responsible if you brick your device or do any other damage.

-\/-\/-\/-\/-\/-\/-\/-\/-\/-​

Download and changelog for dreamlte, dream2lte and greatlte:

https://freeze.ws/RR
​

-/\-/\-/\-/\-/\-/\-/\-/\-/\-

Please don't ask me for support how to flash!

-\/-\/-\/-\/-\/-\/-\/-\/-\/-

Kernel Source: https://github.com/exynos8895/android_kernel_samsung_universal8895/tree/lineage-17.1

Resurrection Remix Source: https://github.com/ResurrectionRemix

-/\-/\-/\-/\-/\-/\-/\-/\-/\-​

There are three changes I've made:

- The default networkTransitionTimeout is decreased from 60 to 30 seconds.

- The bluetooth icon in the status bar is visible as soon as bluetooth is enabled (and not only if a bluetooth device is connected).

- The battery LED color can be set individually for the range 90 to 99% (so you have <90% charging, 90% to 99% nearly full and 100% full).

Everything else is default RR!

-\/-\/-\/-\/-\/-\/-\/-\/-\/-​

These are the device/vendor sources I use for the build:

https://github.com/exynos8895/android_device_samsung_dreamlte

https://github.com/exynos8895/android_device_samsung_dream2lte

https://github.com/exynos8895/android_device_samsung_greatlte

https://github.com/exynos8895/android_device_samsung_universal8895-common

https://github.com/exynos8895/android_vendor_samsung_dreamlte

https://github.com/exynos8895/android_vendor_samsung_dream2lte

https://github.com/exynos8895/android_vendor_samsung_greatlte

https://github.com/exynos8895/android_vendor_samsung_universal8895-common

-/\-/\-/\-/\-/\-/\-/\-/\-/\-​

Big thanks to the LineageOS team, to mainey, to Stricted and especially to all the RR developers.

Thank you for this amazing ROM!!

-\/-\/-\/-\/-\/-\/-\/-\/-\/-

Feel free to donate, if you want to :)

​
[Samsung Galaxy S8 & S8+ Cross Device Development] ylmz134:
Do you have a screenshot and how is the game performance?
[Samsung Galaxy S8 & S8+ Cross Device Development] ylmz134:
I like to play games and I use hadesrom, it is very fluent and successful, I will test and share this rom. There is volte support on the rom's own page, but this port also works on the rom, has anyone tried it?
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
Please have a look onto the official page of RR:

Resurrection Remix OS | Get Resurrected - Resurrection Remix OS

#GetResurrected The Latest Resurrection Remix OS 8.6 Update “Based On Android 10” Has Been Released. We work to make your android experience elegant. Handpicked features beautifully packed in one OS. Screenshots Personalizations Don’t get lost in the plethora of customization options. Advanced...

resurrectionremix.com

I have no idea about the game performance, but I would say this depends only on the kernel you are using. Of course you can also flash other kernels.
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
Also compiled the ROM for S8+ and N8.

See the link in the starting post for download.

Please note: I don't have a S8+ nor a N8, so I'm not able to test it!
[Samsung Galaxy S8 & S8+ Cross Device Development] Refayatul:
Will try it tomorrow on my s8+. And report back
[Samsung Galaxy S8 & S8+ Cross Device Development] Refayatul:
Currently running your build. Thanks you for your work...

I have found two problems. One is s8/+ has a on sceen button. Which we can press to turn to device on. This feature works in all the roms i have use. It even works in recovery. But not working in this device. 2. Pressing Power button+ volume down doesn't take screenshots... My usb port is kind of broken. Thats why i am unable to provide adb logs. But if you suggest any apps that can take good logs using root. Then i can provide logs using that app
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
Thank you for your feedback.

Said to hear that. On my wife's S8 all this works fine. So this is really strange.

Normally I'm using https://nolanlawson.com/apps/#catlog for the logs.

Maybe you could try another kernel?
[Samsung Galaxy S8 & S8+ Cross Device Development] Refayatul:
Since you are new to s8+ development. Give this rz kernel a try. When all of us were using a10/11 . This was the kernel that every dev would recommend us to use.
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
Thanks. I tried to compile the ROM with the kernel source from https://github.com/diepquynh/android_kernel_samsung_universal8895.

Unfortunately it seems that this kernel requires a newer version of gcc and to be honest I don't know how to implement this in my build process.

So at the moment the only possibility I see is to flash the kernel manually after flashing the ROM.
[Samsung Galaxy S8 & S8+ Cross Device Development] farish_xda:
Great ROM ... I have been using RR since a long time .... if could you please update the security patch as well as the vendor security patch for dreamlte ... that would be awesome...
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
Thank you. The security patch level is currently Oct 2022. Maybe I can update to Dec this weekend.

But I have to say: The code base got pretty old in the meantime and so the number of patches which can't be included, because the code is totally different today, increases. So I'm not able to implement all fixes.

And I have absolutely no idea about vendor security patches. Where would I get these?
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
++ UPDATE ++

download: https://freeze.ws/RR

security string: 2022-12-05

CVE-2022-20472
CVE-2022-20473
CVE-2022-20470
CVE-2022-20474
CVE-2022-20485
CVE-2022-20486
CVE-2022-20491
CVE-2021-0934
CVE-2022-20449
CVE-2022-20476
CVE-2022-20500
CVE-2022-20144
CVE-2022-20478
CVE-2022-20479
CVE-2022-20480
CVE-2022-20484
CVE-2022-20487
CVE-2022-20488
CVE-2022-20495
CVE-2022-20501
CVE-2022-20466

not implemented:
CVE-2022-20124
CVE-2022-20442
CVE-2022-20611
CVE-2022-20411
CVE-2022-20498
CVE-2022-20469
CVE-2022-20144
CVE-2022-20483
CVE-2022-20468
CVE-2022-23960
[Samsung Galaxy S8 & S8+ Cross Device Development] farish_xda:
Home button press screen wakeup is not working ....
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
Have you already tried RZ kernel as recommended by Refayatul?

https://xdaforums.com/t/rom-s8-s8-n8-resurrection-remix-8-7-q-unofficial.4528715/post-87852797
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
Tried it now by my own.

RZ kernel doesn't work at all for me.

RAD kernel didn't show any improvement concerning the problem with the screen wakeup.

So it seems to be something related to the ROM itself. But I have no idea..

This ROM has the same base I'm using for my S9 and there it works without problems.

At the moment I'm not sure if it makes sense to develop this any further.

With the latest release I have problems with Magisk, which didn't reinstalled automatically and also Google Apps had some problems without reinstalling. Strange.....
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
I repaired the broken wakeup button. Reason was the missing sec_touchscreen.kl in /system/usr/keylayout which maps the touch key to KEY_WAKUEP.

Download: https://freeze.ws/RR
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
I've fixed the problem that Magisk, OpenGapps and so on were not reinstalled automatically after dirty flash.

If you installed the apps properly (for Magisk patching the boot img is not enough, you have to do another direct install from the App!), the reinstallation should work now automatically if you are dirty flashing a new version.

Download: https://freeze.ws/RR
[Samsung Galaxy S8 & S8+ Cross Device Development] farish_xda:
great news .... let me download the rom and try it again ...
[Samsung Galaxy S8 & S8+ Cross Device Development] farish_xda:
Working perfectly ....... good job brother
[Samsung Galaxy S8 & S8+ Cross Device Development] farish_xda:
Tested the ROM thoroughly ... root, sensors, signature spoofing, settings etc ... found no issues yet ... very stable ....
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
### UPDATE ###

Fixed bug with screen casting (there were some missing libraries so that the submix audio device didn't work).

Changed p2p_disabled in wpa_supplicant_overlay.conf to 0 to get rid of continous error messages in logcat.

-> https://freeze.ws/RR
[Samsung Galaxy S8 & S8+ Cross Device Development] afrds:
Good morning, I have installed in my sm g955f and it does not work, the screen freezes, it does not allow unlocking the sim
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
Thank you for the feedback. Sad to hear that. Do other LOS (based) ROMs work for you?
[Samsung Galaxy S8 & S8+ Cross Device Development] afrds:
I have tried

Lineage OS 19.1 (Android 12L)

this works very well

too

LineageOS 20 (Android 13) this won't connect my smartwatch

and the one i currently have

ROM][11][OFFICIAL] Havoc OS v4.11

and those based on

PixelExperience

more of the same android 13 still does not connect with the smart watches thanks for the inconvenience
[Samsung Galaxy S8 & S8+ Cross Device Development] afrds:
I also want to say thank you very much to all of you who make it possible for our phones not to become obsolete
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
Okay, thank you.

At the moment I have no idea why it's not working for you 🤷
[Samsung Galaxy S8 & S8+ Cross Device Development] afrds:
I don't know if it helps you what happens when you install the screen freezes, it doesn't allow you to unlock the sim

and there is no way to turn it off just like that

press and hold Power + Volume Down button for 7 seconds

and then immediately press Vol Up + Bixby + Power to reboot to TWRP
[Samsung Galaxy S8 & S8+ Cross Device Development] Aidarintrong:
Hello. AOD not work !😭😭😭 Note 8 greatlte
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
You mean there is no option to enable it, right?

/e: Fixed it, update is coming soon.
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
### UPDATE ###

- Fixed not working main phone speaker (due to previously added wrong libraries).

- Fixed missing option for always on display.

Download: https://freeze.ws/RR
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
### UPDATE ###

security fixes 2023-01-05

download: https://freeze.ws/RR

implemented:
CVE-2022-20456 CVE-2022-20489 CVE-2022-20490
CVE-2022-20492 CVE-2022-20493 CVE-2023-20918
CVE-2023-20920 CVE-2023-20921 CVE-2022-20494
CVE-2023-20908 CVE-2023-20905 CVE-2023-20913
CVE-2023-20915 CVE-2022-22088 CVE-2022-33255

not implemented:
CVE-2022-20461 CVE-2022-42719 CVE-2022-42720
CVE-2022-42721 CVE-2022-2959 CVE-2022-41674
CVE-2023-20928
[Samsung Galaxy S8 & S8+ Cross Device Development] hum-man:
Beautiful ROM, thanks. Any suggestions to get network running? No IMEI issue, SIM card is detected, carriers are listed but no connection at all. Thanks again
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
Are you talking about data connection?

Sounds like you have to add the APN under Settings, Network, Mobile, APNs.
[Samsung Galaxy S8 & S8+ Cross Device Development] hum-man:
no

No APN is set, but calls, SMS, data, USSID codes no chance. The problem exists with all custom ROMs that have been installed (lightheart 1.0,, LineageOS 20, RR 8.7) . On stock DTB and on other devices no such issues with the same SIM card.
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
Maybe you could try another baseband.

Also read something about clearing EFS partition, but I'm not sure if this is good. You should anyway make backups before changing anything.
[Samsung Galaxy S8 & S8+ Cross Device Development] hum-man:
because of the issues in the past, I just test things with the basic install, so no backup needed, at least of data. Just rebooted a few minutes ago, without any changes in EFS and basband, the SIM got network connection for a few minutes, but than it stopped again. With manual carrier selection, the connection seems to be more stable so far.

Which version of Magisk do you recommend? With Magisk 19.3 the device boot looped. With the RR recommendet Magisk-v17.1-SoLdieR9312.zip, leads to "Unable to repack boot image". Or use a different root option?
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
Before clearing EFS I would definitely make a backup. Really don't know what might happen.

I also would backup baseband.

Just had a look, my wife's S8 has baseband G950FXXU2CRF1.

Works perfect, at least in Germany.

Concerning Magisk she's using 25201, I guess canary version.

As far as I remember, I made a backup of the boot image using TWRP, repacked it using Magisk and then flashed it using TWRP again.
[Samsung Galaxy S8 & S8+ Cross Device Development] hum-man:
ok, got root with Magisk 22.1 canary. Wifi and carrrier network get connection, but disengage after a few minutes. So no solution to use this ROM as a daily driver so far. Any further suggestions are welcome.
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
It would be good to have a catlog from the moment when the network disconnects.
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
Hey guys. I somehow broke my code base.

At the moment I don't know if there is any chance for this project to proceed.

Maybe I can restart from a backup, we'll see.
[Samsung Galaxy S8 & S8+ Cross Device Development] Unicron.mafia:
could u find android 13 with smartwatch conncet option?

i have this issue and saddly have to use older androids
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
I was able to recover the codebase.

So here is the update to 2023-02-05.

In March there were no implementable security updates for Android 10.

Download: https://freeze.ws/RR

Fixed wakeup soft button not working in AOD.

Bumped security string to 2023-02-05

CVE-2023-20943
CVE-2023-20944
CVE-2022-43680
CVE-2023-20945
CVE-2023-20932
CVE-2022-39842
CVE-2022-0850

not implemented:
CVE-2023-20933
CVE-2022-20481
CVE-2022-20455
CVE-2022-39189
CVE-2022-41222
CVE-2023-20937
CVE-2023-20938
[Samsung Galaxy S8 & S8+ Cross Device Development] Slooer:
Thanks 🥰
[Samsung Galaxy S8 & S8+ Cross Device Development] farish_xda:
Geart news ... n thanks
[Samsung Galaxy S8 & S8+ Cross Device Development] Aidarintrong:
Awesome rom. Thank you mr. Freeze !
[Samsung Galaxy S8 & S8+ Cross Device Development] hum-man:
Sorry for the long delay. Any suggestions to extract a useful cat log without a bunch of useless information to read through? As far es I could find out, carrier connections only work close to a mobile network tower. At higher distances and lower signal levels the phone disconnects completely. Would it be a problem to get a backup of the base band of your wifes S8?

Some apps like blitzer.de don't work properly. The notification asks to turn of activity log in the developer options, but there is no feature named this way. Any suggestions for this problem without the complete turn off of the developer options?

Thanks a lot
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
Just stop logging as soon as the connection breaks down.

I made a backup of the baseband of my wifes S8 using TWRP 3.3.1-0, download it here: https://freeze.ws/RR/archive (modem.emmc.win)

Can you please send a screenshot / link?

Maybe you have to look for this setting in the app itself?
[Samsung Galaxy S8 & S8+ Cross Device Development] farish_xda:
H

Hi ... When is the next update expected ?
[Samsung Galaxy S8 & S8+ Cross Device Development] Freeze24:
Hi, there are no more security fixes for Android 10. Thus there are no updates.