I don't think so
I am not sure about their compatibility, but anyway, MIUI uses dandelion codename for the both.If Dandelion and DandelionC3L2 are not compatible, why they are in same section? Lol.
Allright.I am not sure about their compatibility, but anyway, MIUI uses dandelion codename for the both.
No. MIUI uses DANDELIONC3L2 for Redmi 10A and not for Redmi 9A.I am not sure about their compatibility, but anyway, MIUI uses dandelion codename for the both.
Check the updater script of any of their ROMs / Firmware, you will see that both are dandelion.No. MIUI uses DANDELIONC3L2 for Redmi 10A and not for Redmi 9A.
DANDELION and DANDELIONC3L2 are NOT compatible.
So, doesn't make sense for keeping them in same section.
NO.Check the updater script of any of their ROMs / Firmware, you will see that both are dandelion.
Some people is saying Redmi9A and Redmi10A can share their ROMs.
I clearly stated that you can see the codename in the updater-script, here's the lines I meant in case you didn't manage to check:Check the updater script of any of their ROMs / Firmware, you will see that both are dandelion.
getprop("ro.product.device") == "dandelion" || abort("E3004: This package is for \"dandelion\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: Redmi/dandelion_cn/dandelion:11/RP1A.200720.011/V12.5.7.0.RCZCNXM:user/release-keys");
getprop("ro.product.device") == "dandelion" || abort("E3004: This package is for \"dandelion\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: Redmi/dandelion_global2/dandelion:11/RP1A.200720.011/V12.5.1.0.RCZTWXM:user/release-keys");
getprop("ro.product.device") == "dandelion" || abort("E3004: This package is for \"dandelion\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: Redmi/dandelion_global2/dandelion:11/RP1A.200720.011/V12.5.5.0.RCZMIXM:user/release-keys");
I didn't say they are compatible, did I?NO.
You and your script are wrong.
Codename for Redmi10a is not Dandelion, but Dandelion_C3L2.
I am not a grammar teacher, but I know perfectly that Dandelion != Dandelion_C3L2, otherwise the expression would not have "C3L2" to differentiate.
When I asked if Dandelion and Dandelion_C3L2 are compatible, you replied "I don't think so."
Now, I'm saying, "Dandelion and Dandelion_C3L2 are NOT compatible."
I don't think this, I'm sure of this.
I took the test for myself, and I didn't ask anyone to tell me the result.
Due to your misconception and your script, this error can cause catastrophic losses to users trying to install the ROM on the wrong device.
As soon as I installed the ROM for the Dandion_C3L2, the device crashed before the boot starts and the USERDATA WAS FULLY LOST.
If they are "same" why USERDATA WAS FULLY LOST ????
Please, moderators, do something! @shadowstep @Oswald Boelcke
As I said, I don't think they are NOT compatible, I'm totally sure.
Sure thing, I haven't told anyone to do so, and I have updated the first post to elaborate which files are for 9A and which are for 10A.Some people is saying Redmi9A and Redmi10A can share their ROMs.
But, they can NOT.
Everybody should avoid flashing the wrong ROM to your devices.
If you have a Redmi9A, flash DANDELION rom only !!!!
If you have a Redmi10A, flash DANDELION_C3L2 rom only !!!!
If you mix them, you will have catastrophic losses as the FULL USERDATA !!!!
KEEP ATTENTION AND USE YOUR BRAIN !
What matters if it does not work on different device?I clearly stated that you can see the codename in the updater-script, here's the lines I meant in case you didn't manage to check:
China ROM:
Code:getprop("ro.product.device") == "dandelion" || abort("E3004: This package is for \"dandelion\" devices; this is a \"" + getprop("ro.product.device") + "\"."); ui_print("Target: Redmi/dandelion_cn/dandelion:11/RP1A.200720.011/V12.5.7.0.RCZCNXM:user/release-keys");
TW ROM:
Code:getprop("ro.product.device") == "dandelion" || abort("E3004: This package is for \"dandelion\" devices; this is a \"" + getprop("ro.product.device") + "\"."); ui_print("Target: Redmi/dandelion_global2/dandelion:11/RP1A.200720.011/V12.5.1.0.RCZTWXM:user/release-keys");
Global ROM:
Code:getprop("ro.product.device") == "dandelion" || abort("E3004: This package is for \"dandelion\" devices; this is a \"" + getprop("ro.product.device") + "\"."); ui_print("Target: Redmi/dandelion_global2/dandelion:11/RP1A.200720.011/V12.5.5.0.RCZMIXM:user/release-keys");
I didn't say they are compatible, did I?
You asked, and I replied, "I am not sure"
My script is not wrong, because as you clearly see, both devices uses dandelion in updater-script assertion.
Sure thing, I haven't told anyone to do so, and I have updated the first post to elaborate which files are for 9A and which are for 10A.
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/