Related
sorry if these are noob questions, however GSI's and custom roms confuse me, and I really don't want to brick my phone on accident
Preface:
I have a rooted moto g6 with an unlocked bootloader that supports project treble. as per getprop ro.treble.enabled running pie 29.55-24 Software channel Retail US
1. Can I flash a GSI on my phone
2. Where is there a good guide on how to flash a gsi
3. Will it factory reset my phone
4, Is there anything I should do beforehand
5. Are there any GSI's I can't flash
(What I think is 1:yes 2:If i knew i wouldn't be here 3:yes 4:backup system images 5: Yes
Thanks
Android Adam said:
sorry if these are noob questions, however GSI's and custom roms confuse me, and I really don't want to brick my phone on accident
Preface:
I have a rooted moto g6 with an unlocked bootloader that supports project treble. as per getprop ro.treble.enabled running pie 29.55-24 Software channel Retail US
1. Can I flash a GSI on my phone
2. Where is there a good guide on how to flash a gsi
3. Will it factory reset my phone
4, Is there anything I should do beforehand
5. Are there any GSI's I can't flash
(What I think is 1:yes 2:If i knew i wouldn't be here 3:yes 4:backup system images 5: Yes
Thanks
Click to expand...
Click to collapse
There are different types of treble devices you know. Only a couple GSI work on the g6.
GSI is a system image, so usually flash with fastboot.
Fastboot flash system system.img
Or in TWRP with the "install image" option.
The G6 does not have a b partition. So only try ones that say "arm A only". Meaning arm, not arm 64, and a - only, not a/b.
There is an entire section of this site devoted to it. Search "Project Treble". Without the quotes obviously
Here you go
https://forum.xda-developers.com/project-treble
Better yet here ya go
Built for the g6.
All GSIs are generic system images, so technically they can Flash on any device that has treble (with the correct CPU architecture and partitioning scheme) but when one gets built for your device most of the bugs have been worked out
madbat99 said:
There are different types of treble devices you know. Only a couple GSI work on the g6.
GSI is a system image, so usually flash with fastboot.
Fastboot flash system system.img
Or in TWRP with the "install image" option.
The G6 does not have a b partition. So only try ones that say "arm A only". Meaning arm, not arm 64, and a - only, not a/b.
There is an entire section of this site devoted to it. Search "Project Treble". Without the quotes obviously
Here you go
https://forum.xda-developers.com/project-treble
Better yet here ya go
Built for the g6.
All GSIs are generic system images, so technically they can Flash on any device that has treble (with the correct CPU architecture and partitioning scheme) but when one gets built for your device most of the bugs have been worked out
Click to expand...
Click to collapse
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Android Adam said:
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Click to expand...
Click to collapse
I would try the one I linked to. It is the most likely to have everything working. Descendant two dot two
The one you're trying to use says it's extremely specific to his device. Majorly buggy for others. Including A only devices.
Android Adam said:
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Click to expand...
Click to collapse
Did you ever manage to get battery to work? Mine doesn't either nor does the USB-C port
Sorry I need help installing the ROM GSi RR I get an error in the text of insufficient space and I get error 70 to someone else happens? And I tried to fix the problem and when I managed to install the gapps the phone did not start someone can help me?
ACM1PT said:
Sorry I need help installing the ROM GSi RR I get an error in the text of insufficient space and I get error 70 to someone else happens? And I tried to fix the problem and when I managed to install the gapps the phone did not start someone can help me?
Click to expand...
Click to collapse
Please link to the rom so I can try to help. describe what you're trying to do
Android Adam said:
Please link to the rom so I can try to help. describe what you're trying to do
Click to expand...
Click to collapse
Could you give me a guide on how to install with gapps? Sorry I have to write in English everything I did my language is Spanish sorry
ACM1PT said:
Could you give me a guide on how to install with gapps? Sorry I have to write in English everything I did my language is Spanish sorry
Click to expand...
Click to collapse
I need to know which rom you are using. Please post a link to it. Is this it https://www.google.com/amp/s/forum....urrection-remix-v7-0-arm64-32-b-t3891636/amp/
Android Adam said:
I need to know which rom you are using. Please post a link to it. Is this it https://www.google.com/amp/s/forum....urrection-remix-v7-0-arm64-32-b-t3891636/amp/
Click to expand...
Click to collapse
Are you using Oreo or pie
Android Adam said:
Are you using Oreo or pie
Click to expand...
Click to collapse
pie bro,
I will try to install again have it happen
ACM1PT said:
pie bro,
I will try to install again have it happen
Click to expand...
Click to collapse
I found the problem. The system partition is too small so GApps always fails. To solve it go to twrp adb push your rom, and flash it. Then go to format then system hit repair then resize and confirm. Of you are flashing a big GApps (Super) do it again. Flash GApps then Magisk (for root) then you're done
Anybody have twrp recovery for redmi note 9 ????
Mbilalkhaan said:
Ksi k pass redmi note 9 ki twrp recovery ha ????
Click to expand...
Click to collapse
Guessing you're asking if there's a custom recovery available for the RN9. Not yet, so far as I know
I've found the stock firmware pretty solid so far - can't see me bothering too root this
@Mbilalkhaan I see that you're new here. Welcome to XDA Developers! I suggest you read the Forum Rules in complete before posting from now on. Please note that as per the forum rules, only English is allowed:
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
Click to expand...
Click to collapse
Request you to please keep this in mind while posting going forward.
Have a nice day!
Regards,
shadowstep
Forum Moderator
interested too in a twrp for RN9 for magisk and stereo mod
Probably gonna be a while. The forum for this phone just opened a couple days ago , plus it has a mediateck processor so gonna be a while
Unofficial twrp?
Has anyone tried this Unofficial TWRP 3.4.1 for Redmi Note 9/Merlin_Global?
unofficialtwrp.com /twrp-3-4-1-root-redmi-note-9/
just remove the space before the forward slash
i must wait 166 hours to unlock my bootloader...after that i will try it. thanks
danger2u said:
i must wait 166 hours to unlock my bootloader...after that i will try it. thanks
Click to expand...
Click to collapse
May I ask, why do you need to wait 166 hours to unlock bootloader? I this about the apply thingy that you need to do before unlocking Xiaomi devices? Because I have read this article that stated "Before some years ago you need to apply and wait 1-15 days for permission! But, now Xiaomi changes its policy. Now you don't need to apply for unlocking your device.Oct 13, 2018"
c.mi.com /thread-1635834-1-1.html#:~:text=Before%20some%20years%20ago%20you,apply%20for%20unlocking%20your%20device.
danger2u said:
i must wait 166 hours to unlock my bootloader...after that i will try it. thanks
Click to expand...
Click to collapse
I see now. Mine's 168 hours. You just need to add your Mi account first then it will tell you to wait 168 hours on the Mi unlock tool. Thanks Mr. danger2u
tested the unofficialtwrp thing today. And now got me bootlooped. seems like the no-verity-opt-encrypt.zip is not working as expected. now im trying to restore the old state.... hope there will be a good way to root this cause i need adaway
Adguard is loads less trouble - fine without root
darthm0e said:
tested the unofficialtwrp thing today. And now got me bootlooped. seems like the no-verity-opt-encrypt.zip is not working as expected. now im trying to restore the old state.... hope there will be a good way to root this cause i need adaway
Click to expand...
Click to collapse
Thanks darthm0e! Hope you keep updating here on your findings BTW, how can we create a custom recovery? I want to know how to.
Adguard doesn't work for all my needs. and its more or less browser based. Anyway i need root for some other stuff too...so.
2nd try i used the Xiaomi Tool V2 (by Francesco Tescari). It loads also the same TWRP image and i also get stucked in the Bootloop.
on tradingshenzhen they explained more or less the same method then unofficialtwrp.com except they use the XiaomiTool V2
and the TWRP i found there is the same.
whats strange is that i only read about Codename Merlin for the Redmi Note 9, but mine reports hisself as MerlinNFC. maybe this is the thing or are they all equipt with NFC? I will try tomorrrow again.
darthm0e said:
Adguard doesn't work for all my needs. and its more or less browser based. Anyway i need root for some other stuff too...so.
2nd try i used the Xiaomi Tool V2 (by Francesco Tescari). It loads also the same TWRP image and i also get stucked in the Bootloop.
on tradingshenzhen they explained more or less the same method then unofficialtwrp.com except they use the XiaomiTool V2
and the TWRP i found there is the same.
whats strange is that i only read about Codename Merlin for the Redmi Note 9, but mine reports hisself as MerlinNFC. maybe this is the thing or are they all equipt with NFC? I will try tomorrrow again.
Click to expand...
Click to collapse
Note 9 phones with model number M2003J15SG have NFC
M2003J15SS don't
(Can check your model number in settings)
Redmi note 9 root
How root redmi note 9???? Any body know about redmi note 9 recovery?????? When recovery coming for redmi note 9??????
Hi guys,
New here and I got this phone a few weeks ago. I tried rooting it via Magisk both by flashing the zip on the unofficial TWRP and by patching the boot.img file, but both methods ended up in bootloop.
So I'd like to know if any of you have informations on this : has a consistent way of rooting this phone been found?
(My question may seem stupid since it only came out a month or so ago, but honestly I don't really have an idea how long it usually takes after a device's release for people to find a way to root it)
Thanks for your answers!
https://forum.xda-developers.com/re.../how-to-unlock-root-redmi-9-9s-9-pro-t4108913
This post worked for me as far as rooting goes.
I also managed to verify the SafetyNet test (with magisk spoofing modules + clearing Play Store/Services data), then installed edXposed just fine too.
But, then I installed some module that got me stuck in a bootloop and had to wipe and start over, and I couldn't pass the SafetyNet check anymore for some reason.
So I wiped again and keeping it unrooted for now, I'll wait for custom ROMs.
Akitake said:
https://forum.xda-developers.com/re.../how-to-unlock-root-redmi-9-9s-9-pro-t4108913
This post worked for me as far as rooting goes.
I also managed to verify the SafetyNet test (with magisk spoofing modules + clearing Play Store/Services data), then installed edXposed just fine too.
But, then I installed some module that got me stuck in a bootloop and had to wipe and start over, and I couldn't pass the SafetyNet check anymore for some reason.
So I wiped again and keeping it unrooted for now, I'll wait for custom ROMs.
Click to expand...
Click to collapse
Could u tell me please how did u install ? I flashed it in magisk but it shows me that it's not installed in the edxposed manager.
@Akitake: That's always nice to see that a particular rooting method of some related Redmi phone works on our Redmi Note 9. :good:
Now, you know for sure that the Redmi Note 9 has a MediaTek G85 processor and Xiaomi devices are notorious for getting very easily bricked. See for example the Custom Rom threads for Redmi Note 8. It is really spooky how some guys end up having their smartphone turn in to a Xiaomi service center - if there is such a center at all in their country. So what's paramount here for us Redmi Note 9 users is that we really, really make sure that we don't arrive at a hopeless situation! That's why I need to ask you some questions to make sure we all are on the same page.
1) What Note 9 do you have? Is it one with NFC or not? Mine, for example, is a M2003J15SG where G denotes the NFC variant.
2) What's the MIUI version you are running? Mine, for example, is 11.0.5.0 (QJOEUXM)
3) You unlocked your phone, right?
4) Did you use any particular tools like a particular fastboot version, for instance?
5) Which version of Magisk did you install?
6) Which version of edXposed did you install?
7) Which Magisk spoofing module did you install? Why that and not another one?
8) What do you mean with "clearing Play Store / services data". Do you mean all Google Play services data?
9) If you arrived at a bootloop, how did you wipe? Did you wipe data/cache/etc? Did you use fastboot or some LR-TWRP or MiFlash? Which version of the tool?
10) Once you reinstalled your original boot.img, did your phone start up normally or were there "hickups"?
Sorry for asking so many questions, but as I said, I want to make a 100% sure that everything goes well.
Thanks for your answers in advance!
Best whishes to you!
- dfahren
Akitake said:
https://forum.xda-developers.com/re.../how-to-unlock-root-redmi-9-9s-9-pro-t4108913
This post worked for me as far as rooting goes.
I also managed to verify the SafetyNet test (with magisk spoofing modules + clearing Play Store/Services data), then installed edXposed just fine too.
But, then I installed some module that got me stuck in a bootloop and had to wipe and start over, and I couldn't pass the SafetyNet check anymore for some reason.
So I wiped again and keeping it unrooted for now, I'll wait for custom ROMs.
Click to expand...
Click to collapse
dfahren said:
@Akitake: That's always nice to see that a particular rooting method of some related Redmi phone works on our Redmi Note 9. :good:
Now, you know for sure that the Redmi Note 9 has a MediaTek G85 processor and Xiaomi devices are notorious for getting very easily bricked. See for example the Custom Rom threads for Redmi Note 8. It is really spooky how some guys end up having their smartphone turn in to a Xiaomi service center - if there is such a center at all in their country. So what's paramount here for us Redmi Note 9 users is that we really, really make sure that we don't arrive at a hopeless situation! That's why I need to ask you some questions to make sure we all are on the same page.
1) What Note 9 do you have? Is it one with NFC or not? Mine, for example, is a M2003J15SG where G denotes the NFC variant.
2) What's the MIUI version you are running? Mine, for example, is 11.0.5.0 (QJOEUXM)
3) You unlocked your phone, right?
4) Did you use any particular tools like a particular fastboot version, for instance?
5) Which version of Magisk did you install?
6) Which version of edXposed did you install?
7) Which Magisk spoofing module did you install? Why that and not another one?
8) What do you mean with "clearing Play Store / services data". Do you mean all Google Play services data?
9) If you arrived at a bootloop, how did you wipe? Did you wipe data/cache/etc? Did you use fastboot or some LR-TWRP or MiFlash? Which version of the tool?
10) Once you reinstalled your original boot.img, did your phone start up normally or were there "hickups"?
Sorry for asking so many questions, but as I said, I want to make a 100% sure that everything goes well.
Thanks for your answers in advance!
Best whishes to you!
- dfahren
Click to expand...
Click to collapse
1) It's the lower end version, with 64GB internal storage, Redmi Note 9 (merlin)
2) Latest at time of writing, shouldn't matter but yes, 11.0.5.0, we're also going to get MIUI 12 soon-ish as it's already released in China.
3) Yes with miunlock (Official tool)
4) I just always use the ADB and Fastboot versions provided with MiUnlock (same folder, open CMD inside it then you can use adb and fastboot)
5) Latest? 20.4
6) I installed EdExposed manager from XDA Labs and simply installed it that way, so, latest
7) One of them is like Magisk Props something, the other is lib something which seemed to help for DRM content (netflix etc)
8) Once I installed the Magisk modules for spoofing, I restarted, then cleared the Google Play Store & Play Store services data (In Settings>Apps>Manage Data> Clear all Data), restarted again.
9) I didn't bootloop ever. And even if you do, it's to either use fastboot (power + vol down) and flash the official rom back with MiFlash.
10) Nah it was completely normal.
Links:
- Official Roms for Redmi note 9: https://c.mi.com/oc/miuidownload/detail?device=1900378
- Re-flash stock rom via recovery (power + vol up): https://c.mi.com/oc/miuidownload/detail?guide=1
- Re-flash stock rom via fastboot (power + vol down): https://c.mi.com/oc/miuidownload/detail?guide=2
Their links to roms in that guide are dead, you can get them here though: https://xiaomifirmwareupdater.com/miui/merlin/
Just make sure the ROM you download is of the right type (recovery for recovery method, fastboot for fastboot+miflash method) before downloading.
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
I came to this just by occasion while trying different things with the phone.
Please keep in mind that there were 4 testers, but only 2 successful installations have been reported. Please consider participating in testing
So, the instruction itself:
Download the latest china fastboot ROM
Download your preferred, but one of the latest Recovery global ROM (I recommend Taiwan)
From recovery archive, with the help of payload-dumper-go extract vendor partition:payload-dumper-go -p vendor payload_bin_or_recovery_rom
Flash China ROM, then reboot to fastbootd: fastboot reboot fastboot
Flash vendor: fastboot flash vendor vendor.img
Flash patched vbmeta (you can find it yourself)
Now the system should boot just fine (dm-verity still may occur, but that's not critical)
How to OTA:
After the system prompts you for reboot, reboot into fastbootd: adb reboot fastboot and flash your vendor again, then flash pathced vbmeta
Problems:
On POCO, POCO launcher is being installed and it doesn't work. The fix is down this post
No Google services included, flash WeebGApps in Magisk. SafetyNet attestation WON'T WORK! AT ALL!
Everything else is working just fine (Camera, NFC, 5G)
POCO fix:
First of all, you have to enable USB debugging and installing apps via usb. Because the launcher is "blinking", you will have to get to developer options via quick settings. It might not work, so firstly get to any application from notification or quick settings button.
Once you've done that, install magisk via adb:adb install magisk.apk
Now you have to open it: adb shell monkey -p magisk.package.name (look for it in settings) -v 1
Patch boot image with magisk as usual and flash it
Open magisk again with the same method. Or flash via PC: adb push module.zip your/desired/location; adb shell; su; magisk --install-module module.zip
Flash P2Mi.zip
Reboot and enjoy
Hi, could you please kindly provide a url link to the Chinese roms?
Thanks.
wenyendev said:
Hi, could you please kindly provide a url link to the Chinese roms?
Thanks.
Click to expand...
Click to collapse
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
btw, 4 testers have tested this method. And there were only 2 sucessful attempts, and 2 unsuccesful
Great post, i was waiting this guide for a long time!
My suggestion is 8ndonesian vendor and microg gapps. I will try asap
A question: u have tryed without flash a global vendor?
KastenTop said:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
btw, 4 testers have tested this method. And there were only 2 sucessful attempts, and 2 unsuccesful
Click to expand...
Click to collapse
Thanks for the link.
I suppose you mean "Global phone models" by the Android devices other than Xiaomi & Redmi?
Have you tried flashing MIUI roms downloaded from the official site (https://www.miui.com/download.html) straight to Global phone models? And how was that?
wetito said:
have tryed without flash a global vendor?
Click to expand...
Click to collapse
Yep. If so, it just reboots into recovery saying that NV data is corrupted
wenyendev said:
"Global phone models"
Click to expand...
Click to collapse
The funny thing is that any other Xiaomi device just boots normally and only we are unique. And as for this phone it's got 2 versions: camellia (for china), and camellian (global)
KastenTop said:
The funny thing is that any other Xiaomi device just boots normally and only we are unique. And as for this phone it's got 2 versions: camellia (for china), and camellian (global)
Click to expand...
Click to collapse
So for the same model, for example, Redmi Note 10, Xiaomi developed a version (named "camellia") to sell in mainland China, and another (named "Camellian") for oversea market?
wenyendev said:
So for the same model, for example, Redmi Note 10, Xiaomi developed a version (named "camellia") to sell in mainland China, and another (named "Camellian") for oversea market?
Click to expand...
Click to collapse
Yes
KastenTop said:
Yes
Click to expand...
Click to collapse
Ok, I see.
So am I right in saying that Chinese roms (on the official website listed here https://www.miui.com/download.html) customized for domestic model (ex. Camellia) cannot be installed on Global model (ex. Camellian)?
wenyendev said:
Ok, I see.
So am I right in sayting that Chinese roms (on the official website listed here https://www.miui.com/download.html) customized for domestic model (ex. Camellia) cannot be installed on Global model (ex. Camellian)?
Click to expand...
Click to collapse
Yes. And it looks like the reason is vendor partition. I can't tell exactly what makes it crash with Chinese vendor
KastenTop said:
Yes. And it looks like the reason is vendor partition. I can't tell exactly what makes it crash with Chinese vendor
Click to expand...
Click to collapse
I understand now.
Why not simply install a Global miui for Camellian (https://new.c.mi.com/global/miuidownload/detail/device/1900390), rather than use a Chinese Rom customized for Camellia on Camellian?
wenyendev said:
I understand now.
Why not simply install a Global miui for Camellian (https://new.c.mi.com/global/miuidownload/detail/device/1900390), rather than use a Chinese Rom customized for Camellia on Camellian?
Click to expand...
Click to collapse
More beautiful and faster
KastenTop said:
More beautiful and faster
Click to expand...
Click to collapse
Ok. Btw, how do you get to know if the version of Redmi Note 10 is Camellia or Camellian?
wenyendev said:
Ok. Btw, how do you get to know if the version of Redmi Note 10 is Camellia or Camellian?
Click to expand...
Click to collapse
Build prop
i could flash both latest MIUI 13 dev (13.0.3.1.13) and stable (V13.0.8.0.SKSCNXM) without doing anything from your thread
cams and nfc (didnt try 5G since i dont have coverage) work well
im not sure if for older MIUI versions you can just flash it without requiring any steps from the post
(dev miui, always uses blue miui logo)
so i suppose flashing system.img china over could work?
1lopes said:
i could flash both latest MIUI 13 dev (13.0.3.1.13) and stable (V13.0.8.0.SKSCNXM) without doing anything from your thread
cams and nfc (didnt try 5G since i dont have coverage) work well
im not sure if for older MIUI versions you can just flash it without requiring any steps from the postView attachment 5787399
(dev miui, always uses blue miui logo)
Click to expand...
Click to collapse
thanks for your feedback. i was quite sure that miui cn version can be installed without any bootloop, and you have confirmed
wetito said:
so i suppose flashing system.img china over could work?
thanks for your feedback. i was quite sure that miui cn version can be installed without any bootloop, and you have confirmed
Click to expand...
Click to collapse
I actually just flashed it via mi flash both versions just fine
1lopes said:
I actually just flashed it via mi flash both versions just fine
Click to expand...
Click to collapse
Are you sure you got camlliaN, and not just camellia?
It's really interesting topic. In my case if I do not flash vendor I get rebooted into Recovery saying NVData is corrupted. For the other guy it didn't even boot, throws to fastboot
KastenTop said:
Are you sure you got camlliaN, and not just camellia?
Click to expand...
Click to collapse
It is camellian, I bought it fresh new, if u want to see I can send some images (but if im sure MIUI CN changes the model to Chinese but im not sure about the hardware)
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.