Related
Hi guys, I have an SM-N960F dual sim exynos Note 9 and i have recently discovered this whole other element of ROM flashing known as project treble ROMs. I tried to flash a few different ones and i could only get one to work and the rest all just either bootlooped or stayed on the initial splashscreen. I was wondering if anybody could shed some light on them a bit for me and perhaps knew exactly the best way to flash them, and what firmware is best to start on beforehand etc? I found the whole thing EXTREMELY confusing especially with venfor images and kernel images etc...
Thank you for any input/help!
We can't really use the term Project Treble when talking about Samsung phones. Technically it is implemented, but Samsung being Samsung, it's quite a non-standard implementation and not really compatible with anything else.
oddbehreif said:
We can't really use the term Project Treble when talking about Samsung phones. Technically it is implemented, but Samsung being Samsung, it's quite a non-standard implementation and not really compatible with anything else.
Click to expand...
Click to collapse
Ive flashed a few of them onto my phone but it seems to be a bit of hit and miss as to whether they boot up or not. The ones that do have been good in terms of the size and speed etc, I even flashed a generic copy of OneUI which worked well.
I am on Pie base using the Dr.Ketan rom, so I tried a few GSIs which are supposed to be compatible with Pie base. I took them from here.
The way I flash them is:
1. Factory reset from TWRP
2. Flash the GSI as system image
3. Flash stock kernel otherwise you will be stuck on boot logo or you will get into bootloop. To flash the stock kernel I just use Dr.Ketan's rom, because the UI upon flashing allows you to choose and flash stock kernel and skip everything else.
(They mention that we should flash Permissiver also, but it gives error so I can't flash it)
So those GSIs boot up, but they are barely usable. The "System is finishing update" and "System setup will start soon" are stuck for me and never finish. Also for example in the PixelExperience9 from this collection I was not even able to add my Google account because of the system auto-closing almost all system apps that I try to open.
It might be that these things should be done in a different way, but this is my experience for now. So..... back to Dr.Ketan ROM. I was really hoping to get the MIUI GSI as daily, but it seems impossible to me.
EDIT: Lol I realised we are the same people talking on the other thread also, so you gave me the link to the treble collection.
Hi folks,
I'm currently on Android 9 Stock on my Note 9 Exynos.
My phone is ready to update to Android 10. However, I wanted to take the chance and finally root my Note using TWRP and Magisk.
But since I'm using a Galaxy Watch to count my steps and Secure Folder is important to me too, I have a few questions.
Please reply even if you can answer only one question. Thanks.
If opening my bootloader and flashing TWRP, KNOX will be tripped. Can this be bypassed by a specific Samsung ROM, Kernel oder Magisk module in general?
Can my Samsung Galaxy Watch still be paired with my phone after flashing TWRP and Magisk? (this question excludes S-Health related things but includes the pairing in general + notifications on the watch)
If the answer to 1. is no, how can I still use S-Health? Is this still working and is it the only way?
If the answer to 1. is no, how can I still use Secure folder? Smali Patcher seems to list Secure Folder usage as one of their features so I guess this is my (only) way to go?
Is it better to proceed with the official update to Android 10 and do all the flashing/rooting afterwards or to flash TWRP now and directly flash a good Samsung Android 10 rom from this forum?
Even if the answer to 1. is no, are there still any Samsung roms (I want/need most Samsung features including S-Pen so I won't flash LineAge) and/or Kernels that you can highly recommend?
TarikVaineTree said:
Hi folks,
I'm currently on Android 9 Stock on my Note 9 Exynos.
My phone is ready to update to Android 10. However, I wanted to take the chance and finally root my Note using TWRP and Magisk.
But since I'm using a Galaxy Watch to count my steps and Secure Folder is important to me too, I have a few questions.
Please reply even if you can answer only one question. Thanks.
If opening my bootloader and flashing TWRP, KNOX will be tripped. Can this be bypassed by a specific Samsung ROM, Kernel oder Magisk module in general?
Can my Samsung Galaxy Watch still be paired with my phone after flashing TWRP and Magisk? (this question excludes S-Health related things but includes the pairing in general + notifications on the watch)
If the answer to 1. is no, how can I still use S-Health? Is this still working and is it the only way?
If the answer to 1. is no, how can I still use Secure folder? Smali Patcher seems to list Secure Folder usage as one of their features so I guess this is my (only) way to go?
Is it better to proceed with the official update to Android 10 and do all the flashing/rooting afterwards or to flash TWRP now and directly flash a good Samsung Android 10 rom from this forum?
Even if the answer to 1. is no, are there still any Samsung roms (I want/need most Samsung features including S-Pen so I won't flash LineAge) and/or Kernels that you can highly recommend?
Click to expand...
Click to collapse
1. No
2. Yes. Even samsungpay works but from the watch only in android 9. Not sure 10.
3. Samsung health work. Not sure what was the workaround but it is ready baked in the rom
4. Secure folder work. Not sure what was the workaround but it is ready baked in the rom
5. No difference in rooting between 9 & 10. But you need android10 bootloader to boot up android 10 rom. So if you root at Pie, need to flash bootloader seperately.
6. All oneui custom roms have working spen. Not knox related. I don't know about kernel. I'm just using the one with the rom. You will have to search which is the best for your phone and usage.
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
Hiya folks,
I've been playing around with trying to get GSI ROMs to work on this old Mi3W.
I was specifically keen on LeOS but I was under the impression that ANY GSI for 32bit is universally compatible and should work, right?
I (successfully) followed the repartitioning instructions here (and referred to here also) to supposedly make the Mi3W GSI "compatible".
MIUI 10 EU ROM boots fine, is smooth and polished, but NOT privacy friendly..
I'm a longtime user of lineageOS and other custom ROMs mostly in the interest of less invasion of privacy.
I've gone through several lists of GSI ROMs looking for 32bit / arm and degoogled / microg and downloaded what I found.
Unfortunately, I seem to have missed something because none of them boot.
The phone shows "MI" a couple of times and then just boots to TWRP recovery each time.
Either I'm doing something wrong, or these ROMs really cannot / are not meant to boot on this phone.
How do I tshoot this? A little help please? There seem to be a lot of links to telegram groups, what is up with that?
go0 said:
Hiya folks,
I've been playing around with trying to get GSI ROMs to work on this old Mi3W.
I was specifically keen on LeOS but I was under the impression that ANY GSI for 32bit is universally compatible and should work, right?
I (successfully) followed the repartitioning instructions here (and referred to here also) to supposedly make the Mi3W GSI "compatible".
MIUI 10 EU ROM boots fine, is smooth and polished, but NOT privacy friendly..
I'm a longtime user of lineageOS and other custom ROMs mostly in the interest of less invasion of privacy.
I've gone through several lists of GSI ROMs looking for 32bit / arm and degoogled / microg and downloaded what I found.
Unfortunately, I seem to have missed something because none of them boot.
The phone shows "MI" a couple of times and then just boots to TWRP recovery each time.
Either I'm doing something wrong, or these ROMs really cannot / are not meant to boot on this phone.
How do I tshoot this? A little help please? There seem to be a lot of links to telegram groups, what is up with that?
Click to expand...
Click to collapse
Hi @go0,
If you can still access to fastboot mode, I would suggest you try
- fastboot erase cache.
If it doesn't work,
- fastboot erase system;
- fastboot erase userdata.
If you still can, remember back up your data before executing these commands above.
Have you ever tried GSI before and did they work well on your device?
oops
Hello Guys!
I'm thinking to install GSI ROM on my Redmi note 12 pro 5G. I have some experience with custom ROM flashing in TWRP. As far as I know there's no TWRP recovery available for my phone!
Can I flash GSI ROM with Fastboot mode in my device?
If you have experience or some guide for me to Flash GSI, please could you tell me?
And I don't familiar with those terms in GSI ROM name so I'm afraid that I would brick my device or some would go wrong.
I'm planning to flash AOSP 12.1 v416 by PHH or Android 13 Project Elixir.
Redmi note 12 pro should be similar close to Note 10, an A/B device with dynamics partitions
Read here, just find the appropriate GSI image and everything else specific for Note 12 pro
[GSI][PHH][13] Guide & Support [Mojito][Sunny]
Why should I use a GSI ? Mojito already have custom ROMs ¯\_(ツ)_/¯ Yes. But this thread exists due to the following reasons: You don't wanna fear about devs stop shipping updates. You don't wanna re-flash your custom recovery / kernel after each...
forum.xda-developers.com
x3r0.13urn said:
Redmi note 12 pro should be similar close to Note 10, an A/B device with dynamics partitions
Read here, just find the appropriate GSI image and everything else specific for Note 12 pro
[GSI][PHH][13] Guide & Support [Mojito][Sunny]
Why should I use a GSI ? Mojito already have custom ROMs ¯\_(ツ)_/¯ Yes. But this thread exists due to the following reasons: You don't wanna fear about devs stop shipping updates. You don't wanna re-flash your custom recovery / kernel after each...
forum.xda-developers.com
Click to expand...
Click to collapse
i think there is no twrp for this device yet but i think it is fine to just flash gsi.
keithsze001 said:
i think there is no twrp for this device yet but i think it is fine to just flash gsi.
Click to expand...
Click to collapse
True, you won't need twrp or any recovery at all to flash gsi.
Step to flash twrp/recovery is optional if you want to get rooted because fastboot doesn't have sideload function. Unless you go for KernelSU, it's a different topic.
Nowadays twrp function starts to decease, unless you need to dump/backup partition without root. I use included recovery from rom for A/B dynamic device
Thanks for the info, I haven't flashed GSI yet. does anyone know any working well rom or recommend ROM for Ruby except MIUI. I will leave my experience after I flashed GSI.Hope some rom for this device will come out!
Xenolast said:
Thanks for the info, I haven't flashed GSI yet. does anyone know any working well rom or recommend ROM for Ruby except MIUI. I will leave my experience after I flashed GSI.Hope some rom for this device will come out!
Click to expand...
Click to collapse
I am looking forward to hear your experience on gsi !
Please let us know if you find any particular stable rom for this device.
piyush_duggal said:
Please let us know if you find any particular stable rom for this device.
Click to expand...
Click to collapse
I bet if the buyers smart enough, they'll mostly will pass buying this. The price is closer to almost a mint second hand of Poco F4, offering almost better in everything except for maybe the main sensor (ov64b vs. imx766). And here we are Poco F4 has already a headstart in custom rom community.
And if you're willing to let go the OIS, Poco F3 isn't that bad either, price nowadays should be the same, its only disadvantages are slower charging and again, main sensor (imx586 vs imx766).
And the last, not to mention that Poco F5 is just around the corner... That should put some coffin nails to Redmi note 12 Pro.
x3r0.13urn said:
I bet if the buyers smart enough, they'll mostly will pass buying this. The price is closer to almost a mint second hand of Poco F4, offering almost better in everything except for maybe the main sensor (ov64b vs. imx766). And here we are Poco F4 has already a headstart in custom rom community.
And if you're willing to let go the OIS, Poco F3 isn't that bad either, price nowadays should be the same, its only disadvantages are slower charging and again, main sensor (imx586 vs imx766).
And the last, not to mention that Poco F5 is just around the corner... That should put some coffin nails to Redmi note 12 Pro.
Click to expand...
Click to collapse
the phone is just released, how could you put the nail? we haven't seen any development for this phone yet.
try Pixel Experience GSI: https://github.com/ponces/treble_build_pe/releases
groovepeppy said:
the phone is just released, how could you put the nail? we haven't seen any development for this phone yet.
Click to expand...
Click to collapse
What I said was: if you're looking for a particular good phone with a good custom roms support, and if you want it now, or very quickly from now, Poco F4 is already here, and its price is very close to Note 12 Pro with same feature and even more potent SoC. And if custom roms in Poco F4 aren't adequate, there's also Poco F3, its community is more active than F4, new one old stock F3 should be priced similar to Note 12 Pro, only if you're willing to loose the fast 67w charger and OIS in Note 12 Pro.
But if you still want Note 12 Pro with custom rom... Well, that's up to you. I didn't say it wouldn't see any custom rom, it just... looks less interesting than the others two.
Redmi Note 8 Pro is the most active for MTK device as far as I know, and for more two years consecutive after its release, it was ridden by a lot of issues. It was ironed out very lately, just after A12 out, and sadly most people has already moved out. Another one was Redmi Note 9 and Redmi 9, merlin and lancelot, again, most their roms stay on A11 firmware because latest A12 firmware gives a lot of headache. I've seen some development on Note 10s (evoX) and Poco M4 Pro (ported roms?), which those are MTK, but again, they're very slow and they had been released earlier than Note 12 Pro, but to be honest, those devices didn't bring the same attractive to Note 12 Pro.
If those aren't providing enough for arguments... Its closest rival is their own Poco X5 Pro, which again uses more common and widespread soc in custom rom community, the SD 778g, which it has some development on similar device such Mi 11 Lite 5g. Xiaomi 12 Lite also uses SD 778g, still hasn't seen any development yet.
tl;dr: there are many xiaomi devices, even the "flagship" Xiaomi 12 or Xiaomi 12 Pro, has yet seen any custom roms. I'd say: stick to existing community or any "its looks more guaranteed to be supported by community" devices rather than hoping this one would have one in the future.
x3r0.13urn said:
What I said was: if you're looking for a particular good phone with a good custom roms support, and if you want it now, or very quickly from now, Poco F4 is already here, and its price is very close to Note 12 Pro with same feature and even more potent SoC. And if custom roms in Poco F4 aren't adequate, there's also Poco F3, its community is more active than F4, new one old stock F3 should be priced similar to Note 12 Pro, only if you're willing to loose the fast 67w charger and OIS in Note 12 Pro.
But if you still want Note 12 Pro with custom rom... Well, that's up to you. I didn't say it wouldn't see any custom rom, it just... looks less interesting than the others two.
Redmi Note 8 Pro is the most active for MTK device as far as I know, and for more two years consecutive after its release, it was ridden by a lot of issues. It was ironed out very lately, just after A12 out, and sadly most people has already moved out. Another one was Redmi Note 9 and Redmi 9, merlin and lancelot, again, most their roms stay on A11 firmware because latest A12 firmware gives a lot of headache. I've seen some development on Note 10s (evoX) and Poco M4 Pro (ported roms?), which those are MTK, but again, they're very slow and they had been released earlier than Note 12 Pro, but to be honest, those devices didn't bring the same attractive to Note 12 Pro.
If those aren't providing enough for arguments... Its closest rival is their own Poco X5 Pro, which again uses more common and widespread soc in custom rom community, the SD 778g, which it has some development on similar device such Mi 11 Lite 5g. Xiaomi 12 Lite also uses SD 778g, still hasn't seen any development yet.
tl;dr: there are many xiaomi devices, even the "flagship" Xiaomi 12 or Xiaomi 12 Pro, has yet seen any custom roms. I'd say: stick to existing community or any "its looks more guaranteed to be supported by community" devices rather than hoping this one would have one in the future.
Click to expand...
Click to collapse
You got the point, you are right. MTK are very slow in development.
I've flashed 2 GSI ROM (Acient OS, Project Elixir) today.
For somehow, I can't flash vbmeta because it made phone to bootloop when I tried to go fastboot on cmd. Project Elixir is lastest version and it have this strange bug that can't connect to internet via wifi even with VPN and DNS Change. Everything is working fine.
But those two ROM have same issue sharing that's brightness can't be decrease or increase and Screen is flickering in every 5 sec or so.
I didnt test camera with GCam since I've to prepare for my work trip. I may write more later about them.
Xenolast said:
I've flashed 2 GSI ROM (Acient OS, Project Elixir) today.
For somehow, I can't flash vbmeta because it made phone to bootloop when I tried to go fastboot on cmd. Project Elixir is lastest version and it have this strange bug that can't connect to internet via wifi even with VPN and DNS Change. Everything is working fine.
But those two ROM have same issue sharing that's brightness can't be decrease or increase and Screen is flickering in every 5 sec or so.
I didnt test camera with GCam since I've to prepare for my work trip. I may write more later about them.
Click to expand...
Click to collapse
Do you succeed to flash Elixir?? if yes can you share your exact way of flashing...I have bootloop on MI logo..I flashed at least 15 times with different setup without success..thanks
Xenolast said:
I've flashed 2 GSI ROM (Acient OS, Project Elixir) today.
For somehow, I can't flash vbmeta because it made phone to bootloop when I tried to go fastboot on cmd. Project Elixir is lastest version and it have this strange bug that can't connect to internet via wifi even with VPN and DNS Change. Everything is working fine.
But those two ROM have same issue sharing that's brightness can't be decrease or increase and Screen is flickering in every 5 sec or so.
I didnt test camera with GCam since I've to prepare for my work trip. I may write more later about them.
Click to expand...
Click to collapse
Please try this, maybe it's a mediatek related GSI issue https://forum.xda-developers.com/t/gsi-13-lineageos-20-light.4509315/post-87620773
it seems that MIUI 14 cause big problems to flash GSI.. A downgrade to MIUI 13 can solve it
rayman95 said:
it seems that MIUI 14 cause big problems to flash GSI.. A downgrade to MIUI 13 can solve it
Click to expand...
Click to collapse
I did flash with MIUI 14 and successfully.
I erase user data,system,cache and A/B partition too.
I would use them if I have time to solve all the problem for myself and I think it's usable as daily rom.
The only problem I face is I can't flash vbmeta and it cause me bootloop to fastboot.
And important things is if you are in fastboot mode, phone screen show as FASTBOOTD
if not you are still in bootloader.
I use
Fastboot getvar is-userspace
Before
Fastboot boot fastboot
Xenolast said:
I did flash with MIUI 14 and successfully.
I erase user data,system,cache and A/B partition too.
I would use them if I have time to solve all the problem for myself and I think it's usable as daily rom.
The only problem I face is I can't flash vbmeta and it cause me bootloop to fastboot.
And important things is if you are in fastboot mode, phone screen show as FASTBOOTD
if not you are still in bootloader.
I use
Fastboot getvar is-userspace
Before
Fastboot boot fastboot
Click to expand...
Click to collapse
Can you share your exact way to flash please. I don't want to erase one more time my device....for nothing and flash again miui...thanks
Xenolast said:
I did flash with MIUI 14 and successfully.
I erase user data,system,cache and A/B partition too.
I would use them if I have time to solve all the problem for myself and I think it's usable as daily rom.
The only problem I face is I can't flash vbmeta and it cause me bootloop to fastboot.
And important things is if you are in fastboot mode, phone screen show as FASTBOOTD
if not you are still in bootloader.
I use
Fastboot getvar is-userspace
Before
Fastboot boot fastboot
Click to expand...
Click to collapse
That doesn't sound as a working solution.
Your are writing .... If I have time to solve all the problem for myself ....
So what does that mean ?
And .....
I erase user data,system,cache and A/B partition too......
is also stupid. In a and b slots are the boot, vbmeta, system_vbmeta. So if you erased a and b slots, it can't boot without boot partition.
rayman95 said:
Can you share your exact way to flash please. I don't want to erase one more time my device....for nothing and flash again miui...thanks
Click to expand...
Click to collapse
I'm back from my trip and I will comment here my process and screenshots. I'm redownloading all tools and rom to my pc.
I'm one of the end user and I'm sorry if I confused you all with unclear method but I will try to describe every step I did.
I'm finding solution for screen flickering, auto brightness issue and no internet connection error.