Before anyone gets the idea and goes to the trouble of building a custom ROM - install a /e/GSI for a quick sense of achievement.
The bootloader of the Xiaomi Redmi 9AT (dandelion), originally shipped with Android 10, Android 11 also already available, needs to be officially unlocked via a Xiaomi account first. The waiting periods imposed by Xiaomi on the user vary depending on the model.
It should be taken into account that the system works with the partitioning system, a so-called Super Partiton | Dynamic Partition, in which the otherwise usual /system and /vendor and /product partitions are combined.
The Redmi ‘9A’ has the architecture A64-AB (also may be called arm32-binder64-ab) starting from Android 10. For safety’s sake, check with Treble Info App whether this also applies to the Xiaomi Redmi ‘9AT’.
Thanks a lot for your answer. I’m not used to flashing. Well, years ago I’ve installed Cyanogen and LineageOS with step by step instructions, and my actual /e/ was bought with system included here.
But I need some help.
I suppose that you mean to be used with another phone company. Then the phone sholud be yet unlocked.
Any differences between both or recommendation?
Don’t know if it can affect the use of phone with /e/.
Just unboxed it and install Treble Info.
It said I need system-arm32_binder64-ab.img.xz image.
It it’s the one called system-arm-ab.img.xz here?
Hi @Colegota, I take it from your questions that not only “some help” is needed. By no means do I want to offend or verbally hurt you, but your question tell me that there is a lack of elementary basic knowledge.
Unlocking the bootloader of a Xiaomi Redmi 9AT is a more complex matter than the simple OEM unlock of the Samsung S7. The ‘FastbootD’ mode is elementarily important for flashing into a Super Partition | Dynamic Partition. Also the difference of the different ‘system images’ must be known.
The /e/ documentation Flash the system image isn’t sufficient to install an e/e/OS GSI on a Xiaomi Redmi 9AT. The smallest operator errors can trigger a bootloop when the system is rebooted, or in the worst case, massively lock up your system.
Please do your research first to minimize possible flash risks. Until then, I advise you not to install the /e/OS GSI I suggested. Thank you for reading.
Maybe i’s good an introduction.
I’m using ungoogled systems since CyanogenMod in a Galaxy S (without number).
Now, I need a second phone for work, because I need to install some privative apps, including one by Microsoft, and I don’t want that those apps have any access to other information inside the phone.
So I try to install a new system with /e/, if possible, and a different SIM card in other terminal. Then a friend gives me this Redmi that he don’t use, totally unboxed.
I want to check first if it’s possible to install /e/ there and if I can do it. It seems yes. I’m searching and found some useful links for the help I need and lacks here. I’ll post this links later.
By now, I need to unlock the Xiaomi bootloader, but it requires a Xiaomi account that it’s related to the SIM card/phone number and I have to go a shop to buy a new one.
I’m also interested in learning to build /e/OS custom ROMs. I can’t get by with the instructions available in the /e/forum. If the information you found is suitable for a beginner as you say, then please link to those guides. Maybe we can learn together and profit from each other?
I liked what /e/ is trying to achieve and it will be on the top list of my OASP ROMs to build.
I’m currently “trying” to create a device tree that is able of build an AOSP ROM with user build type (production build). I say “trying” because I’m struggling hard with the server part and that’s the reason I haven’t achieve my goal so far.
If anyone can help him, then probably he can help us.
Sure, but I’m confused with the information given by the app and the names at /e/ GSI.
At the app, as required image, it saids: Your device requires an image fle called system-arm32_binder64-ab.img.xz
But in Arquitecture saids: your device it’s arm32 but uses binder of 64 bits. It usually means that your device support 64 bits but your software not. In this case use images called ‘binder64’ or ‘a64’.
I supposed that arm in /e/ means 32 bit hardware, not software.
So, the sentence In this case use images called ‘binder64’ or ‘a64’, seems to refer to system-a64-ab.img.xz, but the one ‘Your device requires an image fle called system-arm32_binder64-ab.img.xz’ it’s more relate to system-arm-ab.img.xz.
I’m currently trying to build an unofficial build of /e/ os for this phone. I flashed it and it stucks on the e os boot animation. Not giving up, I’ll try new things during the week because I’m on holidays. I’ll post here for more information
Hi guys ! Today, I tried to build eOS multiple times and it seems that eOS is too large for the system partition of our device because I get this error at 99%:
Out of space? Out of inodes? The tree size of /home/mael/e/out/soong/.temp/tmptvSaWD is 1546927104 bytes (1475 MB), with reserved sp
ace of 0 bytes (0 MB).
The max image size for filesystem files is 1467244544 bytes (1399 MB), out of a total partition size of 1490853888 bytes (1421 MB).
20:33:26 ninja failed with: exit status 1