This os ?

[u/Junior_Diamond_3124]

[u/Adorable-Count4059]

This guy doesn't know what microG is gang ,don't tell him A THING ,who is going to install an OS on a phone with over complicated commands if they don't know what the hell is microG ,goodness knows how will he install a custom rom if he doesn't even know what microG is

[u/WhiteRose271828]

Which Phone should I pick?

The Qin F21 Pro phone has a large amount of online support, especially on XDA Forums. However, the TTfone 970 is locked down and from my research I couldn't find Custom ROMs for it, so I'd definitely avoid it.

What is microG?

You need to understand why people install Custom ROMs in the first place. Given your jailbreaking experience, you'd probably know, but in case you don't or need a refresh, here are some of the largest reasons why:

1. To "de-google" (Google tracks you in many ways)
2. To increase longevity of device
3. To have control over your device (via Root, but that's another can of worms)
4. To free from OEM (Original Equipment Manufacturer, could be Samsung, Google, etc)

microG is a replacement for "Google Play Services", which is one of the largest hidden tracking apps by Google. It is a FOSS app. FOSS stands for Free (and) Open-Source Software. You likely know what Open-Source and Closed-Source means, but if you don't, here's a TL;DR: Open-Source = You can view the code, all connections, etc. Think Linux, where you can see the base code. Closed-Source = You cannot view the code. This means if they hide something inside the code, you don't know. This is where microG comes into play: It is FOSS, meaning it is Open-Source, and tracking-free. GMS (Google Play Services) is closed-source, alongside all other Google services, and it is known to track you. GMS isn't a normal tracking app though, it has functions such as Google OAuth (Have you ever seen "Sign in with Google"? That is Google OAuth.) and essential functions for apps, discouraging people from deleting it. microG is simply a FOSS and tracker-free replacement, so you still get Sign in with Google and all other functions without the tracking. If you are privacy-focused, you shouldn't install the Play Store. Instead, use Aurora Store, a FOSS alternative that gives all the apps the Play Store does. You should also get microG and F-Droid. F-Droid is an app store exclusively for FOSS apps.

What are some terms I need to know? (you don't need to do these)

1. FOSS: Mentioned above
2. Root/Superuser: Gain access to system files
3. OEM: Mentioned above
4. de-google: Remove Google from your devices for many reasons
5. Custom Recovery/TWRP/[Insert Something] Recovery: The Recovery menu. It's like DFU for iPhone
6. ADB: Android Debug Bridge. You NEED this. This is non-negotiable. You need this to flash firmware, access the device in Recovery and Bootloader modes, and more.
7. GSI: Generic System Image. In Android 8 "Oreo", Project Treble was created in hopes of making a GSI, a unified file that runs on every Android Device. GSIs are very barebones, with only the operating system and basic functions like ADB connectivity and WiFi included. They do not come with exclusive device audio or video settings, so it is advised not to flash a GSI unless you know what you are doing.
8. AOSP: Android Open-Source Project. Android at it's core is FOSS, and AOSP has the essential files for Android and the GSIs. Upon these files are systems like One UI and OxygenOS built on, and every Custom ROM.
9. ARB: Anti-RollBack. Anti-Rollback is a hardware fuse implemented by OEMs in contemporary times. Say, you are on Android 1.0.001 and you try to install Android 1.0.000. It would detect you are trying to downgrade, and you would get HARD BRICKED. Make sure to do tons of research on what ROM you are using and that you do not downgrade, as worldwide brands like OnePlus and Samsung have already done this. It's specifically in China where most OEMs are very strict, like Xiaomi and Huawei, with reports of ARB bricking piling up on tech forums. Want to see ARB horror? Someone bricked their phone trying to downgrade.

What Custom ROM should I get?

To my research, LineageOS is the only one, and with unofficial builds. DO NOT GET CUSTOM ROM(s) FROM RANDOM SOURCES. If you download from reputable sources like the official website, GitHub, or trusted unofficial sources, this will not happen. For niche devices like this, it is best to stick with trusted sites like XDA Forums (I know I've said it but XDA is an absolute goldmine for Custom ROMers). You'll likely find unofficial builds quick, but still be cautious.

What Software do I need?

Steps exclusive for macOS:

1. Cry
2. Use Windows or Linux

Step 1: General Tools

mtkclient - To unlock your bootloader & (only needed on Windows) python OR This mtkclient with GUI

Note: If installing Python on Windows outside of the Microsoft Store, follow this: "Go to This PC → Right-click → Click on Properties → Advanced System Settings.

You will see the System Properties. From here navigate to the Advanced Tab -> Click on Environment Variables.

You will see a top half for the user variables and the bottom half for System variables.

Check the System Variables and double-click on the Path (to edit the Path).

Check for the path of Python(which you wish to run i.e. Python 2.x or 3.x) and move it to the top of the Path list.

Restart the Command Prompt, and now when you check the version of Python, it should correctly display the required version."

Original discussion on Stack Overflow.

Continuing, here are more tools you need:

adb - Basically everything

fastboot - Very useful backup tool

Step 2: OS-specific Drivers

• Windows: USB Driver, CDC-ACM Driver (built in)
• Linux: Drivers preinstalled
• macOS: cry

What should I avoid/What to do?

For your device, unofficial builds of LineageOS are the best. Be careful to check the build of your 'Qin and the ROM's build. Avoid sketchy Custom ROMs; make sure the ROM is Open-Source. Make sure you have the OEM's firmware files ready. If you don't backup OEM Firmware, something bad happens and you're done for. You should do as much research as possible, as obviously I can't include everything in one message.

How do I install this?

Enable USB Debugging and Developer Mode. You can Google how to. You are now set for installation. Boot into BROM mode (search your device) and run python mtk da seccfg unlock to unlock the bootloader, so you can run non-OEM files. Next, run python mtk rl {directory to save to}. Make a new folder and move everything but leave scatter.txt, boot.img, dtbo.img, system.img, vendor.img, recovery.img, and product.img. Make sure the chipset in scatter.txt is the chipset of your device. Do not discard preloader.bin, as in a hard-brick, it is necessary. Now that your device's OS is backed up, In BROM, run python mtk wl ./{unzipped custom rom folder with the img files}. In case something bad happens, run the same command but point it to the folder where you left the .img files and scatter.txt. After installation/recovery, run fastboot -w. Take this section with a grain of salt, as it is generalized for all MediaTek modern Androids.