Database Develop

TWRP for Andoird 11

X1 ii andoird 11 has come up for sometime, is there a Twrp for A11 that can backup and restore phone?
Recently just updated from A10 to A11 58.1.A.5.55 rooted, hope to backup & restore with Twrp.

Sadly, I don't think there is any working custom recovery for this phone on Android 11. I think our best hope is orange fox. See https://forum.xda-developers.com/t/...fox-recovery-project-for-xperia-1-ii.4224247/

Gunseng said:
Sadly, I don't think there is any working custom recovery for this phone on Android 11. I think our past hope is orange fox. See https://forum.xda-developers.com/t/...fox-recovery-project-for-xperia-1-ii.4224247/
Click to expand...
Click to collapse
Yes, for the time being, orangefox recovery is what I use(NG for backup &restore). Hope to have full backup & restore function.
Thanks to @shinyquagsire23
[RECOVERY][UNOFFICIAL] TWRP 3.5.2 for Xperia 1 II
Disclaimer Builds are provided AS-IS without warranty or repair. I am not responsible if you brick your device. About I was using the existing TWRP build that's been floating around and noticed it had a few issues, so I made a device repo and...
forum.xda-developers.com
works great!!!

Not long ago, I just came across this post. But I haven't had time to test it yet. https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-2-for-xperia-1-ii.4279601/

Legit Nokia 7 Plus Bootloader Unlock?

Hi,
I just happened to google how to unlock Nokia 7 Plus' bootloader again and stumbled upon this site:
[Guide] How to unlock the bootloader on Nokia Android Phones for free
Detailed guide to help you unlock the bootloader of your Nokia Android device. You can unlock bootloader on many Nokia smartphones, including Nokia 7 Plus, Nokia 8, Nokia 8 Sirocco, Nokia 8.1, Nokia 7, Nokia 6, Nokia 6.1, Nokia 5, Nokia 2, Nokia 2.1. etc.
www.techmesto.com
It was updated today with a free way to generate bootloader unlock keys for Nokia 7 Plus apparently. Now I can't test this myself at the moment (in a week at earliest), but do you think this is legit?
At least I can generate a code apparently, so this part is actually free.

Hello,
has anyone tried this unlocker, because I'd like to use it, but since I use my nokia 7 plus as my primary phone I'd like to have some confirmations before using it

I use my Nokia 7 Plus as primary phone as well, but I guess I'll just risk it
However, I can't promise anything here. Hopefully I will get around to it within the coming week.

I tried it yesterday and it work flawlessly.
Just follow the steps on the page, I had no issues unlocking the bootloader.
That being said, I nearly bricked my device when trying to flash Lineage OS onto it (because all TWRP and Lineage OS step by step guides seem to be out of date?), but this guide helped me get back to stock: https://forum.xda-developers.com/t/...m-flash-tool-nokia-7-plus-b2n_sprout.4023961/
Might keep it handy if you are like me

Znert said:
I tried it yesterday and it work flawlessly.
Just follow the steps on the page, I had no issues unlocking the bootloader.
That being said, I nearly bricked my device when trying to flash Lineage OS onto it (because all TWRP and Lineage OS step by step guides seem to be out of date?), but this guide helped me get back to stock: https://forum.xda-developers.com/t/...m-flash-tool-nokia-7-plus-b2n_sprout.4023961/
Might keep it handy if you are like me
Click to expand...
Click to collapse
Thanks for the useful infos.
I suppose I will unlock my phone in the upcomming months but right now I just factory resetted it and it's working almost nicely.
I really want to unlock and flash a custom rom on my phone, because the stock rom it's buggy and tends to have some performance issues, but right now if I mess with it I can't afford to change the phone so I guess I'll have to wait.

Znert said:
I tried it yesterday and it work flawlessly.
Just follow the steps on the page, I had no issues unlocking the bootloader.
That being said, I nearly bricked my device when trying to flash Lineage OS onto it (because all TWRP and Lineage OS step by step guides seem to be out of date?), but this guide helped me get back to stock: https://forum.xda-developers.com/t/...m-flash-tool-nokia-7-plus-b2n_sprout.4023961/
Might keep it handy if you are like me
Click to expand...
Click to collapse
Do you have any tips on flashing TWRP? Thanks!
I have unlocked bootloader, tried to install TWRP from https://twrp.me/nokia/nokia7plus.html
fastboot flash recovery twrp.img
Output:
target reported max download size of 402653184 bytes
sending 'recovery' (42644 KB)...
OKAY [ 1.274s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.298s

GenericAsianGuy said:
Do you have any tips on flashing TWRP? Thanks!
Click to expand...
Click to collapse
Yeah, the tutorials seem to be a little outdated...
In general, follow this guide here (its from the same person that created the official twrp.me site I believe):
[CLOSED][OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7 Plus | Onyx |
Note - Iam Not Responsible for bricked devices About Team win recovery project TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who...
forum.xda-developers.com
I wasn't sure if I have a OOB or POB device, but I haven't had any issues using both (currently using OOB since I'm pretty sure my Nokia 7 Plus is that old )
Secondly, what the instruction somehow failed to mention is how to get the install.zip. It is on their sourceforge page in a subfolder:
B2N_sprout - Browse /TWRP-TEN/OOB at SourceForge.net
sourceforge.net
This is for the OOB variant, you can replace OOB at the end with POB to get the other files
You can verify, that I'm sending you the right link by following the links from the forum post to download the image to boot from. For example:
https://sourceforge.net/projects/b2n-sprout/files/TWRP-TEN/POB/twrp-3.4.0-0-B2N_sprout-POB-10.0-20200829.img/download
Now you can just remove the "twrp-3.4.0-0-B2N_sprout-POB-10.0-20200829.img/download" part of the URL and you get to the folder where all the other images are located. Download the latest "twrp-installer-*.zip" for your device and install it.

Znert said:
Yeah, the tutorials seem to be a little outdated...
In general, follow this guide here (its from the same person that created the official twrp.me site I believe):
[CLOSED][OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7 Plus | Onyx |
Note - Iam Not Responsible for bricked devices About Team win recovery project TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who...
forum.xda-developers.com
I wasn't sure if I have a OOB or POB device, but I haven't had any issues using both (currently using OOB since I'm pretty sure my Nokia 7 Plus is that old )
Secondly, what the instruction somehow failed to mention is how to get the install.zip. It is on their sourceforge page in a subfolder:
B2N_sprout - Browse /TWRP-TEN/OOB at SourceForge.net
sourceforge.net
This is for the OOB variant, you can replace OOB at the end with POB to get the other files
You can verify, that I'm sending you the right link by following the links from the forum post to download the image to boot from. For example:
https://sourceforge.net/projects/b2n-sprout/files/TWRP-TEN/POB/twrp-3.4.0-0-B2N_sprout-POB-10.0-20200829.img/download
Now you can just remove the "twrp-3.4.0-0-B2N_sprout-POB-10.0-20200829.img/download" part of the URL and you get to the folder where all the other images are located. Download the latest "twrp-installer-*.zip" for your device and install it.
Click to expand...
Click to collapse
This is great, thank you so much! I can also boot from both OOB and POB, will try this out later today
EDIT: worked like a charm. Thanks again!

Great! Glad I could help!

Hi @Znert, did you use TWRP for Android 10 or Android 11?
Another question: can I unlock the bootloader of a Nokia 7+ on Android 10?
Thank you again.

Radder124 said:
Hi @Znert, did you use TWRP for Android 10 or Android 11?
Another question: can I unlock the bootloader of a Nokia 7+ on Android 10?
Thank you again.
Click to expand...
Click to collapse
I use the Android 10 version, but I'm not sure what the difference is anyways (it's a bootloader, shouldn't that be OS independent?)
Regarding your second question, yes, I unlocked my bootloader with the latest official stock ROM (so Android 10).

Yes that's what I thought also... Maybe we need to use the Android 11 version to install a Android 11 ROM.
Now I see there is a new version of TWRP 3.5.2 on the official website.

Znert said:
I tried it yesterday and it work flawlessly.
Just follow the steps on the page, I had no issues unlocking the bootloader.
That being said, I nearly bricked my device when trying to flash Lineage OS onto it (because all TWRP and Lineage OS step by step guides seem to be out of date?), but this guide helped me get back to stock: https://forum.xda-developers.com/t/...m-flash-tool-nokia-7-plus-b2n_sprout.4023961/
Might keep it handy if you are like me
Click to expand...
Click to collapse
Can you tell me, has unlocking bootloader deleted your apps and data?
In my experience with every older fone, it does format it, but i wanna make sure.
Thanks in advance!

ghost baby said:
Can you tell me, has unlocking bootloader deleted your apps and data?
In my experience with every older fone, it does format it, but i wanna make sure.
Thanks in advance!
Click to expand...
Click to collapse
Yes, unlocking the bootloader will wipe your phone. As far as I know, this is true for all Android phones.

Deleted

Question Redmi 9T with NVT-ts touch screen unresponsive with custom ROMs

Hello.
I have been trying to get a custom rom flashed on my Redmi 9T the past two days.
The problem I am facing is that the touch screen is not responsive with the flashed ROMs that I have tried.
ROMs I have tried:
PixelPlusUI_3.9_juice-11.0-20210912-1736-OFFICIAL
LegionOS-v3.13-juice-20210922-OFFICIAL-GAPPS
Arrow-v11.0-juice-COMMUNITY-20210809-GAPPS
crDroidAndroid-11.0-20210927-juice-v7.10
What did make the touch screen work was to flash "boot.img" from one of the android 11 builds of MIUI such as "xiaomi.eu_multi_HMNote94G_HM9T_POCOM3_21.9.8_v12-11" or "xiaomi.eu_multi_HMNote94G_HM9T_POCO_M3_21.5.27_v12-11" after flashing the custom ROM, but this resulted in "Sytem UI" crashing and wifi not working. There were probably other things that didn't work but I can't have a phone without WiFi so this was not a solution for me.
After looking into what "boot.img" contains, it seems like it contains the kernel and other important system related components.I then tried to flash the following kernels over a new install of the custom ROMs "crDroid" and "PixelPlusUI 3.9":
StormBreaker-lime-r3-0909-0545
CartelProject-lime-BETA-20210915-07
Optimus_Drunk_Citrus_v11.1
But they did not help with getting the touch screen to work.
I also tried a combination of a "boot.img" from an offical android 11 EU MIUI ROM and these three kernels in the hope that I would keep the touch screen fix from "boot.img" and get wifi from the kernels, however every time the kernel was flashed the touch screen stopped working.
This leads me to believe the kernel itself makes the touch screen not work, and other things from the "boot.img" make the WiFi stop working.
So I have a few questions I hope someone can answer:
When do you think Xiaomi will release the source-code for the android 11 kernels that they use in their new MIUI ROMs? As I don't know their release cycles.
When will the firmware for the NVT-ts touchscreen version of Redmi 9T be added to custom kernels?
Is there a way for me to extract the Android 11 MIUI kernel from "boot.img" and flash ONLY that, if that fixes my touchscreen and does not break my WiFi? (If this is legal/allowed/possible)
I don't know anything about android development so if I am wrong please correct me.
Thank you in advance.

1.Download an official firmware, boot your device into your Fastboot Mode with Power+Volume Down Button connect your device to your pc and launch the flash_all.bat
When the flash is completed go to the Stock Recovery with Power Button+Volume Up Button, clean the data and wait your device to boot. When your device booted setting it up and enable USB Debugging from the Developer Tools.
2. Now boot your device to Fastboot Mode using Power Button+Volume Down and try to Flash TWRP or OrangeFOX.
3. Boot your device into Recovery using Power Button+Volume Up
4. Now make a CLEAN FLASH:
Format Data
Flash latest MIUI Weekly
Flash ROM zip
Flash Gapps (for Vanilla build)
Format Data
Reboot System,
Enjoy!
MIUI Weekly Firmware (Lime):​Download​
Fastboot Firmware tgz:​Download​

Atanassoww said:
1.Download an official firmware, boot your device into your Fastboot Mode with Power+Volume Down Button connect your device to your pc and launch the flash_all.bat
When the flash is completed go to the Stock Recovery with Power Button+Volume Up Button, clean the data and wait your device to boot. When your device booted setting it up and enable USB Debugging from the Developer Tools.
2. Now boot your device to Fastboot Mode using Power Button+Volume Down and try to Flash TWRP or OrangeFOX.
3. Boot your device into Recovery using Power Button+Volume Up
4. Now make a CLEAN FLASH:
Format Data
Flash latest MIUI Weekly
Flash ROM zip
Flash Gapps (for Vanilla build)
Format Data
Reboot System,
Enjoy!
MIUI Weekly Firmware (Lime):​Download​
Fastboot Firmware tgz:​Download​
Click to expand...
Click to collapse
Thank you for the reply.
However I believe that this is what I did do when I set up the phone with the ROMs.
I still tried to do it exactly as you explained, however this did not work.
I got into a bootloop after flashing firmware through fastboot, even if I cleaned the data using recovery. I tried the Recovery version of the firmware and this worked fine so after that I followed your tutorial just as you described.
This still didn't work, when booted into the Custom ROM the touch screen was still not working at all.
In the meanwhile I found this blog-post:
lemon – Encik Kunci
Posts about lemon written by Encik Kunci
encikkunci.wordpress.com
Where he states and I quote: "Phones with nt36672d display isn’t supported yet." this was posted August 11, 2021.
I don't know who he is or how he knows that.
I am pretty sure it's a kernel problem or firmware or something, regarding the screen being NVT-ts and probably the "nt36672d" variant.
This makes me very sad.

Its indeed an kernel issue, there's ( at least) two screen revisions from two different vendors

coffeemakerexpress said:
Thank you for the reply.
However I believe that this is what I did do when I set up the phone with the ROMs.
I still tried to do it exactly as you explained, however this did not work.
I got into a bootloop after flashing firmware through fastboot, even if I cleaned the data using recovery. I tried the Recovery version of the firmware and this worked fine so after that I followed your tutorial just as you described.
This still didn't work, when booted into the Custom ROM the touch screen was still not working at all.
In the meanwhile I found this blog-post:
lemon – Encik Kunci
Posts about lemon written by Encik Kunci
encikkunci.wordpress.com
Where he states and I quote: "Phones with nt36672d display isn’t supported yet." this was posted August 11, 2021.
I don't know who he is or how he knows that.
I am pretty sure it's a kernel problem or firmware or something, regarding the screen being NVT-ts and probably the "nt36672d" variant.
This makes me very sad.
Click to expand...
Click to collapse
I found this in 4pda:
Quote a reply: Yes, I had the same thing. By the way, if we are talking about OrangeFox recovery, which did not start at all, then it was necessary to use a newer version, I found a link to a google drive on the xda forum, it did not start there.
And on the touch, I also tried 2 custom firmware on them, everything started, but the touch did not work in principle. Only on off or lightweight everyone and on xiaomi.eu worked. I suppose the same case, but I can refine it when the phone is sent back.
ps: Due to freezes and rebots - in the service they changed the motherboard in the end, I'm waiting for the parcel now.

superdragonpt said:
Its indeed an kernel issue, there's ( at least) two screen revisions from two different vendors
Click to expand...
Click to collapse
I see, so my assumption was correct. Thank you for clarifying.
Do you know how often Xiaomi (or if they will at all) release firmware/kernel source codes, and do you know if custom kernel makers/Custom ROM makers, will actually update their kernels/ROMs to use this in the future?
And is there a way/place for me to keep updated on if Xiaomi releases the needed firmware/sourcecode for this display, so that I can ask ROM makers/Kernel makers nicely to add the firmware, assuming they don't know about this issue?
Atanassoww said:
I found this in 4pda:
Quote a reply: Yes, I had the same thing. By the way, if we are talking about OrangeFox recovery, which did not start at all, then it was necessary to use a newer version, I found a link to a google drive on the xda forum, it did not start there.
And on the touch, I also tried 2 custom firmware on them, everything started, but the touch did not work in principle. Only on off or lightweight everyone and on xiaomi.eu worked. I suppose the same case, but I can refine it when the phone is sent back.
ps: Due to freezes and rebots - in the service they changed the motherboard in the end, I'm waiting for the parcel now.
Click to expand...
Click to collapse
So you have the same problem? I'm not sure I understand what you mean here, aside from the touchscreen not working for you either due to this weird display model.

coffeemakerexpress said:
I see, so my assumption was correct. Thank you for clarifying.
Do you know how often Xiaomi (or if they will at all) release firmware/kernel source codes, and do you know if custom kernel makers/Custom ROM makers, will actually update their kernels/ROMs to use this in the future?
And is there a way/place for me to keep updated on if Xiaomi releases the needed firmware/sourcecode for this display, so that I can ask ROM makers/Kernel makers nicely to add the firmware, assuming they don't know about this issue?
So you have the same problem? I'm not sure I understand what you mean here, aside from the touchscreen not working for you either due to this weird display model.
Click to expand...
Click to collapse
Yes or is not Supported right now..

This is just a small update with a possible fix that I haven't tried yet because I'm tired of flashing ROMs all day, I will try it later if I get the motivation to do so. I post this because someone else might have the energy to test this themselves. If I test this I will update this post with an edit or bump this thread.
I Found on a forum called 4PDA where a user by the name "Void_dp" talks about a Xiaomi Redmi 9T with a nt36672d display. The forum is in Russian, but use a translator if you are interested. It is the post this url links to:
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки - 4PDA
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки
4pda.to
I do not know if the website itself or this user is trustworthy or correct, so try this with caution and I am not responsible for anything you decide to do or happens to you or your computer, or phone.
In short he explains that crDroid 7.9 (7.10 is the current version, and is the one I tried) use a different kernel than the Stormbreaker kernel than crDroid 7.10 uses.
He says if you have crDroid 7.10 installed you have to format data before trying this.
1. Download crDroid 7.9 and crDroid 7.10
2. Get the "boot.img" from the crDroid 7.9 rom and extract it
3. Open the zip file for crDroid 7.10 (do not extract anything) and replace the "boot.img" (7.10 version) with the one you just extracted (7.9 version)
4. Do a clean flash with this modified ROM you just made.
That is all he said, but if it doesn't work my first thought is to try the original crDroid 7.9 rom, if you don't care about running the latest update. This is probably not smart in relation to security patches and stuff like that. I take no responsibility for whatever happens.
Additional information:
I checked the Changelog for the crDroid roms, and they changed the kernel from "Optimus Drunk kernel 11.0" to "Stormbreaker" when they upgraded their ROMs version from 7.9 to 7.10.
I tried using the "Optimus Drunk kernel 11.1" kernel in my trial and error with the ROMs without luck, so I will try to flash some roms together with the "Optimus Drunk kernel 11.0" if I can find it.
Link to crDroid ROM for Redmi 9t:
crDroid.net - Download crDroid for supported devices
official crDroid ROM website
crdroid.net

coffeemakerexpress said:
This is just a small update with a possible fix that I haven't tried yet because I'm tired of flashing ROMs all day, I will try it later if I get the motivation to do so. I post this because someone else might have the energy to test this themselves. If I test this I will update this post with an edit or bump this thread.
I Found on a forum called 4PDA where a user by the name "Void_dp" talks about a Xiaomi Redmi 9T with a nt36672d display. The forum is in Russian, but use a translator if you are interested. It is the post this url links to:
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки - 4PDA
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки
4pda.to
I do not know if the website itself or this user is trustworthy or correct, so try this with caution and I am not responsible for anything you decide to do or happens to you or your computer, or phone.
In short he explains that crDroid 7.9 (7.10 is the current version, and is the one I tried) use a different kernel than the Stormbreaker kernel than crDroid 7.10 uses.
He says if you have crDroid 7.10 installed you have to format data before trying this.
1. Download crDroid 7.9 and crDroid 7.10
2. Get the "boot.img" from the crDroid 7.9 rom and extract it
3. Open the zip file for crDroid 7.10 (do not extract anything) and replace the "boot.img" (7.10 version) with the one you just extracted (7.9 version)
4. Do a clean flash with this modified ROM you just made.
That is all he said, but if it doesn't work my first thought is to try the original crDroid 7.9 rom, if you don't care about running the latest update. This is probably not smart in relation to security patches and stuff like that. I take no responsibility for whatever happens.
Additional information:
I checked the Changelog for the crDroid roms, and they changed the kernel from "Optimus Drunk kernel 11.0" to "Stormbreaker" when they upgraded their ROMs version from 7.9 to 7.10.
I tried using the "Optimus Drunk kernel 11.1" kernel in my trial and error with the ROMs without luck, so I will try to flash some roms together with the "Optimus Drunk kernel 11.0" if I can find it.
Link to crDroid ROM for Redmi 9t:
crDroid.net - Download crDroid for supported devices
official crDroid ROM website
crdroid.net
Click to expand...
Click to collapse
I DIDN't work for me, I got a bootloop, maybe it will work for u

hamid_dabouz said:
I DIDN't work for me, I got a bootloop, maybe it will work for u
Click to expand...
Click to collapse
Thats sad to hear, this phone is a nightmare. I haven't tried this yet, maybe I will try this weekend.
I'm wondering though, did you FORMAT data after flashing?
By bootloop, which of these do you mean:
That it never enters the "loading phase" of the OS (Android/rom splash screen)
That it gets stuck and restarts in the "loading phase" of the OS (Android/rom splash screen)
That it just kicks you to recovery/fastboot over and over again, without showing the OS loading screen
Or something else?

coffeemakerexpress said:
Thats sad to hear, this phone is a nightmare. I haven't tried this yet, maybe I will try this weekend.
I'm wondering though, did you FORMAT data after flashing?
By bootloop, which of these do you mean:
That it never enters the "loading phase" of the OS (Android/rom splash screen)
That it gets stuck and restarts in the "loading phase" of the OS (Android/rom splash screen)
That it just kicks you to recovery/fastboot over and over again, without showing the OS loading screen
Or something else?
Click to expand...
Click to collapse
Ohh Jeesus...

OK I just got my t9, and started the BL unlock, unfortunately I still need to wait ~ 1 week.
So I can't do testing at the moment
My unit has this very same touch screen, so seems I will likely have this same issue in the future.
I took a look at the kernel source provided by Xiaomi ( android 10 only)
And this touch variant isn't there in the defconfig
since the same kernel is used by 4 devices ( including t9, poco m3,etc )
I took the opportunity to check the few custom kernels that already exist for poco M3, and you guys should definitely try the poco m3 " stormbreaker" kernel, since it includes more TP drivers and the correct loading of both Novatek's TP drivers firmware
Cheers

superdragonpt said:
OK I just got my t9, and started the BL unlock, unfortunately I still need to wait ~ 1 week.
So I can't do testing at the moment
My unit has this very same touch screen, so seems I will likely have this same issue in the future.
I took a look at the kernel source provided by Xiaomi ( android 10 only)
And this touch variant isn't there in the defconfig
since the same kernel is used by 4 devices ( including t9, poco m3,etc )
I took the opportunity to check the few custom kernels that already exist for poco M3, and you guys should definitely try the poco m3 " stormbreaker" kernel, since it includes more TP drivers and the correct loading of both Novatek's TP drivers firmware
Cheers
Click to expand...
Click to collapse
Thank you for respond, But i already flashed Two versions of " stormbreaker"kernel one of them worked but the touch is going insane, if you clicked on somewhere on the screen it will respond in other place of the screen ( i hope you understand what i'm saying)

hamid_dabouz said:
Thank you for respond, But i already flashed Two versions of " stormbreaker"kernel one of them worked but the touch is going insane, if you clicked on somewhere on the screen it will respond in other place of the screen ( i hope you understand what i'm saying)
Click to expand...
Click to collapse
Oh i see...
Well since the weekly MIUI EU a11 ROMs seems to work alright ( as per the users feedback) , perhaps this can be easily fixed.
Just a matter of extracting from those android 11 kernel the DTB, and convert dtb to dts and the touch firmware loading binary and fix the kernel entries.
Assuming that the tp driver is the same or similar, and the issue is just the firmware blob and DTS
Let's see
Cheers

Atanassoww said:
Ohh Jeesus...
Click to expand...
Click to collapse
Why that reaction? I am here to learn and try to solve my problem, if you have any advice please elaborate on why what I said was wrong or dumb so I won't make the same mistake again.
superdragonpt said:
OK I just got my t9, and started the BL unlock, unfortunately I still need to wait ~ 1 week.
So I can't do testing at the moment
My unit has this very same touch screen, so seems I will likely have this same issue in the future.
I took a look at the kernel source provided by Xiaomi ( android 10 only)
And this touch variant isn't there in the defconfig
since the same kernel is used by 4 devices ( including t9, poco m3,etc )
I took the opportunity to check the few custom kernels that already exist for poco M3, and you guys should definitely try the poco m3 " stormbreaker" kernel, since it includes more TP drivers and the correct loading of both Novatek's TP drivers firmware
Cheers
Click to expand...
Click to collapse
I will maybe try the Stormbreaker kernel for Poco M3 this weekend as well then to check it out.
superdragonpt said:
Oh i see...
Well since the weekly MIUI EU a11 ROMs seems to work alright ( as per the users feedback) , perhaps this can be easily fixed.
Just a matter of extracting from those android 11 kernel the DTB, and convert dtb to dts and the touch firmware loading binary and fix the kernel entries.
Assuming that the tp driver is the same or similar, and the issue is just the firmware blob and DTS
Let's see
Cheers
Click to expand...
Click to collapse
Thank you for this informative answer, do I take it as this is something you will look into? If I can help by using adb or something, to get information from my phone just tell me what to do.

superdragonpt said:
Oh i see...
Well since the weekly MIUI EU a11 ROMs seems to work alright ( as per the users feedback) , perhaps this can be easily fixed.
Just a matter of extracting from those android 11 kernel the DTB, and convert dtb to dts and the touch firmware loading binary and fix the kernel entries.
Assuming that the tp driver is the same or similar, and the issue is just the firmware blob and DTS
Let's see
Cheers
Click to expand...
Click to collapse
Is this the extract you were talking about? It has the firmware for the touchscreens and everything for android 11. but it is for the Chinese version, so I don't know if that matters.
redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
qssi-user 11 RKQ1.201004.002 V12.0.3.0.RJQCNXM release-keys - redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
github.com
I don't know if this is relevant but I thought I would share it since I found it. Someone smarter than me can maybe use it to make the touchscreen work.

I fix dt2w on Xtended custom rom. Replace kernel and flash Magisk extension. I don.t try others roms....

coffeemakerexpress said:
Is this the extract you were talking about? It has the firmware for the touchscreens and everything for android 11. but it is for the Chinese version, so I don't know if that matters.
redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
qssi-user 11 RKQ1.201004.002 V12.0.3.0.RJQCNXM release-keys - redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
github.com
I don't know if this is relevant but I thought I would share it since I found it. Someone smarter than me can maybe use it to make the touchscreen work.
Click to expand...
Click to collapse
coffeemakerexpress said:
Hello.
I have been trying to get a custom rom flashed on my Redmi 9T the past two days.
The problem I am facing is that the touch screen is not responsive with the flashed ROMs that I have tried.
ROMs I have tried:
PixelPlusUI_3.9_juice-11.0-20210912-1736-OFFICIAL
LegionOS-v3.13-juice-20210922-OFFICIAL-GAPPS
Arrow-v11.0-juice-COMMUNITY-20210809-GAPPS
crDroidAndroid-11.0-20210927-juice-v7.10
What did make the touch screen work was to flash "boot.img" from one of the android 11 builds of MIUI such as "xiaomi.eu_multi_HMNote94G_HM9T_POCOM3_21.9.8_v12-11" or "xiaomi.eu_multi_HMNote94G_HM9T_POCO_M3_21.5.27_v12-11" after flashing the custom ROM, but this resulted in "Sytem UI" crashing and wifi not working. There were probably other things that didn't work but I can't have a phone without WiFi so this was not a solution for me.
After looking into what "boot.img" contains, it seems like it contains the kernel and other important system related components.I then tried to flash the following kernels over a new install of the custom ROMs "crDroid" and "PixelPlusUI 3.9":
StormBreaker-lime-r3-0909-0545
CartelProject-lime-BETA-20210915-07
Optimus_Drunk_Citrus_v11.1
But they did not help with getting the touch screen to work.
I also tried a combination of a "boot.img" from an offical android 11 EU MIUI ROM and these three kernels in the hope that I would keep the touch screen fix from "boot.img" and get wifi from the kernels, however every time the kernel was flashed the touch screen stopped working.
This leads me to believe the kernel itself makes the touch screen not work, and other things from the "boot.img" make the WiFi stop working.
So I have a few questions I hope someone can answer:
When do you think Xiaomi will release the source-code for the android 11 kernels that they use in their new MIUI ROMs? As I don't know their release cycles.
When will the firmware for the NVT-ts touchscreen version of Redmi 9T be added to custom kernels?
Is there a way for me to extract the Android 11 MIUI kernel from "boot.img" and flash ONLY that, if that fixes my touchscreen and does not break my WiFi? (If this is legal/allowed/possible)
I don't know anything about android development so if I am wrong please correct me.
Thank you in advance.
Click to expand...
Click to collapse
Atanassoww said:
1.Download an official firmware, boot your device into your Fastboot Mode with Power+Volume Down Button connect your device to your pc and launch the flash_all.bat
When the flash is completed go to the Stock Recovery with Power Button+Volume Up Button, clean the data and wait your device to boot. When your device booted setting it up and enable USB Debugging from the Developer Tools.
2. Now boot your device to Fastboot Mode using Power Button+Volume Down and try to Flash TWRP or OrangeFOX.
3. Boot your device into Recovery using Power Button+Volume Up
4. Now make a CLEAN FLASH:
Format Data
Flash latest MIUI Weekly
Flash ROM zip
Flash Gapps (for Vanilla build)
Format Data
Reboot System,
Enjoy!
MIUI Weekly Firmware (Lime):​Download​
Fastboot Firmware tgz:​Downl​
Click to expand...
Click to collapse

bogteo said:
I fix dt2w on Xtended custom rom. Replace kernel and flash Magisk extension. I don.t try others roms....
Click to expand...
Click to collapse
Please can you explain more ?

I tried with crdroid 7.9 without success. still cannot use the touchscreen
m210j19sy I began with global miui rom

Question Miui 14 root

Is there already a way to root on android 13 for redmi note 10 pro? Twrp? I can't find anything so far, maybe someone knows something?

kawala8888 said:
Is there already a way to root on android 13 for redmi note 10 pro? Twrp? I can't find anything so far, maybe someone knows something?
Click to expand...
Click to collapse
Same as on Android 12. That was the one with the issue decrypting in custom recovery.

Can't you just fix boot.img with Magisk and then fastboot flash it?

hyperboarean said:
Can't you just fix boot.img with Magisk and then fastboot flash it?
Click to expand...
Click to collapse
Yep.

so, i bought my new redmi note 10 pro yesterday.
its on android 12, miui 13. and it asks me to upgrade.
i havent upgraded yet, thinking maybe rooting it with twrp and all, would be difficult.
Should i keep the current version and root it. or am i ok to upgrade it and then rooting it?
seeing this thread, it seems like im ok with upgrading and rooting. but want to make sure.

Clawsman said:
so, i bought my new redmi note 10 pro yesterday.
its on android 12, miui 13. and it asks me to upgrade.
i havent upgraded yet, thinking maybe rooting it with twrp and all, would be difficult.
Should i keep the current version and root it. or am i ok to upgrade it and then rooting it?
seeing this thread, it seems like im ok with upgrading and rooting. but want to make sure.
Click to expand...
Click to collapse
Wait the days until you are unlocked, in case something borks during that procedure.

thank you for replying.
well, i couldn't wait, considering the new update is lighter and better. so i just updated it and everything went smooth. What is the best way of rooting it? i mean, should i go with or without the twrp. any bugs with the twrp. or is there any better recovery to flash.

Clawsman said:
thank you for replying.
well, i couldn't wait, considering the new update is lighter and better. so i just updated it and everything went smooth. What is the best way of rooting it? i mean, should i go with or without the twrp. any bugs with the twrp. or is there any better recovery to flash.
Click to expand...
Click to collapse
I'd just fix boot.img with Magisk to root. TWRP is mostly just for flashing different roms, and our phones use 2 different touch screens, so your might not even work in TWRT.

hyperboarean said:
I'd just fix boot.img with Magisk to root. TWRP is mostly just for flashing different roms, and our phones use 2 different touch screens, so your might not even work in TWRT.
Click to expand...
Click to collapse
I have been using TWRP on every device i have rooted. i just love the TWRP recovery. because, as you said, it allows me to flash different kind of roms and it allows me to backup my current rom.
i am probably not going to flash any custom roms on this device, but i would like to have the opportunity to backup my current rom for flashing it later on if needed.
Will i be able to do this with the fixed boot.img and Magisk?

Clawsman said:
I have been using TWRP on every device i have rooted. i just love the TWRP recovery. because, as you said, it allows me to flash different kind of roms and it allows me to backup my current rom.
i am probably not going to flash any custom roms on this device, but i would like to have the opportunity to backup my current rom for flashing it later on if needed.
Will i be able to do this with the fixed boot.img and Magisk?
Click to expand...
Click to collapse
Magisk is just for root and different modules (like viper4android). You need TWRP to backup rom, but as I said touch might not work for you, check the TWRP touch not working posts.

hyperboarean said:
Magisk is just for root and different modules (like viper4android). You need TWRP to backup rom, but as I said touch might not work for you, check the TWRP touch not working posts.
Click to expand...
Click to collapse
well, it seems "not worth it". until an official TWRP is released.
And if i decide flash boot.img/Magisk or TWRP, mtk will restore my device back to its locked/stocked state?

Question Does TWRP work with latest firmware?

I've gone back and forth between stock OneUI and GSIs. Recently, I returned to stock but am looking to go back to GSIs again.
When I last went back to stock, I used the latest firmware, WD2. My question is - does the latest version of TWRP for our device work properly with WD2?
As the latest TWRP version is WA3 I'm wondering if there are some compatibility issues such as non working touch screen that I'd like to be aware of before doing this process again.

kevinco1 said:
I've gone back and forth between stock OneUI and GSIs. Recently, I returned to stock but am looking to go back to GSIs again.
When I last went back to stock, I used the latest firmware, WD2. My question is - does the latest version of TWRP for our device work properly with WD2?
As the latest TWRP version is WA3 I'm wondering if there are some compatibility issues such as non working touch screen that I'd like to be aware of before doing this process again.
Click to expand...
Click to collapse
If you read the posts, you'll find I already answered that question.

lewmur said:
If you read the posts, you'll find I already answered that question.
Click to expand...
Click to collapse
Care to at least give a hint of what thread that's in?
Don't see anything in the TWRP one itself and the other threads are all unorganized conversations about TWRP, GSIs and system partitions

kevinco1 said:
Care to at least give a hint of what thread that's in?
Don't see anything in the TWRP one itself and the other threads are all unorganized conversations about TWRP, GSIs and system partitions
Click to expand...
Click to collapse
I've updated to CWD2, rooted and then flashed TWRP and LOS 20 GSI just to make sure it could be done. But I'm not going to re-post all the steps I took to do it. Yes, they are in separate threads because rooting, flashing TWRP and flashing GSI, are separate topics.

lewmur said:
I've updated to CWD2, rooted and then flashed TWRP and LOS 20 GSI just to make sure it could be done. But I'm not going to re-post all the steps I took to do it. Yes, they are in separate threads because rooting, flashing TWRP and flashing GSI, are separate topics.
Click to expand...
Click to collapse
I don't need any instructions or further guidance on how to install TWRP as I've done it a number of times.
The only question I asked was if it worked, most notably touch as that may not always be functional when using a version of TWRP which is not the same as the firmware. A simple yes or no was the only thing I was seeking, nothing additional.
Once the newest version of LOS 20 has been released which has our Unisoc fix included, I'll find out myself once I go through this process again