Code:
/*
* Your warranty is now void lol.
*
* 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 tutorial
* 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.
*/
You will need:
1. LineageOS 16 from this link:
[ROM][9.0.0][UNOFFICIAL] [redmi 8/olive LineageOS 16.0
my name is mohamed first of all sry am not good in making threads :D today am going to share my device tree from scratch including The Rom for lineage-16 am doing my best to get this phone stable as i could if you like my work send me thanks...
forum.xda-developers.com
2. LOLZ kernel from this link:
[KERNEL][4.9.229] LOLZ V10 [olive] [01/07/2020]
/* * Your warranty is now void lmao. * * 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...
forum.xda-developers.com
3. TWRP (Not gonna show you where to get this, if you are on this forum you probably should have it.
4. And any GSI rom that is arm64 and uses the AB partition scheme.
And a basic sense of how rom flashing works
If you flash any GSI normally you will experience bugs such as Bluetooth audio not working and sensors not working.
Thats why I realized i could write the system partition from a GSI onto the lineageOS system partition, which is fully functional.
Result is a working GSI with all features (Not including voLTE, its useless).
I used Havoc OS android 11 GSI for this tutorial:
1. Wipe every partition on your phone, so thats Vendor System Data Cache and Internal storage.
2. Use a SD card or MTP over these files:
LineageOS 16.0 zip
LOLZ kernel zip
Magisk
And the GSI, but I personally MTP this at the last step.
And GAPPS for the GSI, if it doesnt have them built in.
3. Flash the lineageOS zip.
4. After its done flash magisk.
5. And last flash LOLZ kernel.
6. Reboot your device and wait for lineage to boot, once its done set it up until you are in the Pixel Launcher.
7. Reboot back into TWRP or any custom recovery.
8. Now if you haven't already MTP over the GSI and Gapps (if needed).
9. Flash the System partition from the GSI, DO NOT FORMAT ANY PARTITIONS UNTIL YOU DO THIS.
10. Resize the system partition if needed.
11. Install GAPPS.
And last but not least, step 12!
Format data!
Reboot into system and the rom should start booting. After its booted you are gonna set it up normally like you would any other rom. But this time the GSI has features like bluetooth, Gyroscope working and Automatic Brightness (a big issue on any GSI on this phone).
I hope you enjoyed using my tutorial
Forgot to mention that magisk WONT WORK on roms that use android 11!!
Its a limitation of android 11 and i cannot fix this.
Seems promising. Would try on weekend and cast vote.
Thanks for you efforts for community.
Realized once again that you dont even need to boot, just flash the lineageOS rom, then the GSI on top.
thank you very much its working the problem i always encounter is my bluetooth but now its working fine sorry for my bad english BTW i use havoc <3
I was in stock firmware 12.0.1 and I did the following.
1) Formated system, data, vendor and internal storage in twrp.
2) Flashed lineage 16
3) Flashed Magisk 20.4
4) Flashed loz kernel.
5) Reboot
Phone did not boot and was back to twrp. Tried twice and got the same result.
Do I need to flash other files like vbmeta, certification patch or permissive etc to make it work?
thanks, in the evening I will check and tell exactly what works and what does not work, probably all GSIs are giving me some problems (problem with brightness or bluetooth headphones)
Thank you for this guide. I installed havoc os 4.1 using this exact method wiped everything formated data flashed lineage and lolz kernel formated data , I flashed havoc on top without booting into lineage formated data again and voala everything is working smoothly as of now. I am curious tho why do we need to flash lolz is it necessary?
Thank you for this guide. I installed havoc os 4.1 using this exact method wiped every partition (I didn't wiped the USB OTG partition )formated data flashed lineage and lolz kernel formated data , I flashed havoc on top without booting into lineage formated data again and voala everything is working smoothly as of now. I am curious tho why do we need to flash lolz is it necessary?
Dragonnuu said:
Thank you for this guide. I installed havoc os 4.1 using this exact method wiped every partition (I didn't wiped the USB OTG partition )formated data flashed lineage and lolz kernel formated data , I flashed havoc on top without booting into lineage formated data again and voala everything is working smoothly as of now. I am curious tho why do we need to flash lolz is it necessary?
Click to expand...
Click to collapse
We need LOLZ because the lineage kernel gets carried over and its broken (Try booting lineage clear, you wont get far)
mwaseem851 said:
I was in stock firmware 12.0.1 and I did the following.
1) Formated system, data, vendor and internal storage in twrp.
2) Flashed lineage 16
3) Flashed Magisk 20.4
4) Flashed loz kernel.
5) Reboot
Phone did not boot and was back to twrp. Tried twice and got the same result.
Do I need to flash other files like vbmeta, certification patch or permissive etc to make it work?
Click to expand...
Click to collapse
Sorry for the late response, did you format data after installing?
Or did you even flash the GSI?
If so you might actually need the new vbmeta, if you do respond to this and i'll send it to you.
I have done lots of experimentation since last post and finally settled with Havoc OS 3.12 (all android 11 roms are still buggy).
Thanks.
boofiboi said:
Sorry for the late response, did you format data after installing?
Or did you even flash the GSI?
If so you might actually need the new vbmeta, if you do respond to this and i'll send it to you.
Click to expand...
Click to collapse
boofiboi said:
Code:
/*
* Your warranty is now void lol.
*
* 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 tutorial
* 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.
*/
You will need:
1. LineageOS 16 from this link:
[ROM][9.0.0][UNOFFICIAL] [redmi 8/olive LineageOS 16.0
my name is mohamed first of all sry am not good in making threads :D today am going to share my device tree from scratch including The Rom for lineage-16 am doing my best to get this phone stable as i could if you like my work send me thanks...
forum.xda-developers.com
2. LOLZ kernel from this link:
[KERNEL][4.9.229] LOLZ V10 [olive] [01/07/2020]
/* * Your warranty is now void lmao. * * 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...
forum.xda-developers.com
3. TWRP (Not gonna show you where to get this, if you are on this forum you probably should have it.
4. And any GSI rom that is arm64 and uses the AB partition scheme.
And a basic sense of how rom flashing works
If you flash any GSI normally you will experience bugs such as Bluetooth audio not working and sensors not working.
Thats why I realized i could write the system partition from a GSI onto the lineageOS system partition, which is fully functional.
Result is a working GSI with all features (Not including voLTE, its useless).
I used Havoc OS android 11 GSI for this tutorial:
1. Wipe every partition on your phone, so thats Vendor System Data Cache and Internal storage.
2. Use a SD card or MTP over these files:
LineageOS 16.0 zip
LOLZ kernel zip
Magisk
And the GSI, but I personally MTP this at the last step.
And GAPPS for the GSI, if it doesnt have them built in.
3. Flash the lineageOS zip.
4. After its done flash magisk.
5. And last flash LOLZ kernel.
6. Reboot your device and wait for lineage to boot, once its done set it up until you are in the Pixel Launcher.
7. Reboot back into TWRP or any custom recovery.
8. Now if you haven't already MTP over the GSI and Gapps (if needed).
9. Flash the System partition from the GSI, DO NOT FORMAT ANY PARTITIONS UNTIL YOU DO THIS.
10. Resize the system partition if needed.
11. Install GAPPS.
And last but not least, step 12!
Format data!
Reboot into system and the rom should start booting. After its booted you are gonna set it up normally like you would any other rom. But this time the GSI has features like bluetooth, Gyroscope working and Automatic Brightness (a big issue on any GSI on this phone).
I hope you enjoyed using my tutorial
Click to expand...
Click to collapse
Can you flash the AOSP beta GSIs from released on the Android website? For example the Android 12 Beta GSI?
I tried installing Android 12 on Redmi 8 but it did something perplexing.
TWRP said no OS was installed. Rebooting had the phone boot back into TWRP. I tried installing through both fastboot and TWRP. Installations were successful tho.
Related
loaded this on my old phone, seems to work
https://drive.google.com/open?id=0B0...jNKZW1WQ3ExOWs
^ edited to include link
-- see below for update --
Bluetooth isn't working. The message bluetooth share stopped working appears as soon as I switch the toggle. Just letting you know. Great work with this build, I was able to make calls and send messages over lte on AT&T. Really great so far
fixed bluetooth: https://drive.google.com/open?id=0B08utbHfUyw6MjNKZW1WQ3ExOWs
source of fix:
https://github.com/LegacyHuawei/and...mmit/e1564746378cfe5e7b30bec65e626c3edebebacc
Thanks, that fixed Bluetooth, also mtp notified me that it stopped working the moment I make my sd marked as portable storage, I'll check if that occurs again when I try to transfer from my PC. No other problems so far
Update - otg and mtp working fine
source?
Thanks muchly for doing this. Is the source that you used to build the zipfile available someplace I could download it?
plasticchris said:
loaded this on my old phone, seems to work
https://drive.google.com/open?id=0B0...jNKZW1WQ3ExOWs
Click to expand...
Click to collapse
File no longer available?
Demasiados bugs el inestabilidad reinicios a cada rato
The VoIP doesn't seem to work. I tried the stock stack and Fongo. On connecting a call the I can hear the other side, but my voice is muffled/crackly and very very quiet. If I switch to the external speaker everything works but switching back causes the same problem. To me it seems like a sound routing problem.
protectivedad said:
The VoIP doesn't seem to work. I tried the stock stack and Fongo. On connecting a call the I can hear the other side, but my voice is muffled/crackly and very very quiet. If I switch to the external speaker everything works but switching back causes the same problem. To me it seems like a sound routing problem.
Click to expand...
Click to collapse
I had the same problem.
You need change those parametrs at build.prop:
use.dedicated.device.for.voip=true.
use.voice.path.for.pcm.voip=true.
change those parameters to "false"
At CianogenMod12.1(at this firmware Voip work fine), this parametrs are missing, maybe need simply deleting at Lineage 14.1. Today I use my smartphone whith those changes, problem resolved.
krv163 said:
I had the same problem.
You need change those parametrs at build.prop:
use.dedicated.device.for.voip=true.
use.voice.path.for.pcm.voip=true.
change those parameters to "false"
At CianogenMod12.1(at this firmware Voip work fine), this parametrs are missing, maybe need simply deleting at Lineage 14.1. Today I use my smartphone whith those changes, problem resolved.
Click to expand...
Click to collapse
Worked like a charm. Too bad the phone has started having a battery charge issues. I had it dismantled for the last three weeks. Reassembled to test. I will have to keep those settings in mind for other VoIP android phones.
Could you post the link of your device tree, kernel, vendor and any other repos that you used?
krv163 said:
I had the same problem.
You need change those parametrs at build.prop:
use.dedicated.device.for.voip=true.
use.voice.path.for.pcm.voip=true.
change those parameters to "false"
At CianogenMod12.1(at this firmware Voip work fine), this parametrs are missing, maybe need simply deleting at Lineage 14.1. Today I use my smartphone whith those changes, problem resolved.
Click to expand...
Click to collapse
What recovery you used?
Lineage-14.1-20200227-UNOFFICIAL-mb886
Lineage14.1 unoficial and TWRP 3.3.1-0 for the Atrix HD. It as only been tested on a Razr M. I will make an official thread in the development section if there's enough interest.
I am not responsible for bricked devices, loss of data, dead SD cards,
* loss of hair, 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 us for messing up your device, everyone will laugh at
* you and I will deny any wrong doing or responsibility.
Procedure
NB: You must format your Data and Cache partitions as F2FS
Download the latest PICO or NANO GApps from OpenGapps
Backup your internal SD Card, off of the device eg USD or Hard Disk
Boot to TWRP
Make a nandroid backup, and ensure this backup is not on the device itself
Format your data partition and cache partition to F2FS (do NOT post for instructions
on how to do this on this thread!)
**Note: Touch still not working properly so you MUST use a mouse.
Wipe Cache , System & Dalvik-Cache
Flash the ROM Zip
Flash Gapps ARM -> 7.1
Wipe cache and dalvic
Done - Reboot to [System]
Wait...
Not Working:
You tell me
Rom: https://www.androidfilehost.com/?fid=4349826312261733183
MD5sum: https://www.androidfilehost.com/?fid=4349826312261733184
Recovery: Here
***Don't forget a mouse***
All work is done here: https://github.com/Wheels564
Screenshot https://www.androidfilehost.com/?fid=4349826312261715435
Edit: Added recovery download to OP
Wheels564 said:
Here is a test version of lineage14.1 unnoficial and TWRP 3.1.1-0 for the Atrix HD. It as only been tested on a Razr M. I do not have enough posts to make a new thread so I'm adding it here.
I am not responsible for bricked devices, loss of data, dead SD cards,
* loss of hair, 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 us for messing up your device, everyone will laugh at
* you and I will deny any wrong doing or responsibility.
Procedure
NB: You must format your Data and Cache partitions as F2FS
Download the latest PICO or NANO GApps from OpenGapps
Backup your internal SD Card, off of the device eg USD or Hard Disk
Boot to TWRP
Make a nandroid backup, and ensure this backup is not on the device itself
Format your data partition and cache partition to F2FS (do NOT post for instructions on how
to do this on this thread!)
Wipe Cache , System & Dalvik-Cache
Flash the ROM Zip
Flash Gapps ARM -> 7.1
Wipe cache and dalvic
Done - Reboot to [System]
Wait...
Rom: https://www.androidfilehost.com/?fid=4349826312261715411
MD5 sum: https://www.androidfilehost.com/?fid=4349826312261715412
Recovery: https://www.androidfilehost.com/?fid=4349826312261715413
All work is done here: https://github.com/Wheels564
Screenshot https://www.androidfilehost.com/?fid=4349826312261715435
Click to expand...
Click to collapse
does not work on atrix hd. touch doesnt work.
---------- Post added at 11:35 PM ---------- Previous post was at 11:32 PM ----------
jerryspring said:
does not work on atrix hd. touch doesnt work.
Click to expand...
Click to collapse
on other roms that i have flashed that required to format to f2fs i successfully flashed with 6059 philz f2fs recovery without changing that options.. wouldnt your rom flash on that recovery as well?
jerryspring said:
does not work on atrix hd. touch doesnt work.
---------- Post added at 11:35 PM ---------- Previous post was at 11:32 PM ----------
on other roms that i have flashed that required to format to f2fs i successfully flashed with 6059 philz f2fs recovery without changing that options.. wouldnt your rom flash on that recovery as well?
Click to expand...
Click to collapse
I'll see if I can build one with the old touch driver. Touch worked fine on the Razr M both in recovery and rom. My Razr HD had the old touch driver but works fine with the new one.
The old Philz recovery probably won't support android 7.1. I'll see what I can do with it when I get time.
Wheels564 said:
I'll see if I can build one with the old touch driver. Touch worked fine on the Razr M both in recovery and rom. My Razr HD had the old touch driver but works fine with the new one.
The old Philz recovery probably won't support android 7.1. I'll see what I can do with it when I get time.
Click to expand...
Click to collapse
Yeah. Got status 7 using philz f2fs recovery
TWRP and Lineage
New builds up:
Read op for info on rom and twrp.
lineage-14.1-20200227-UNOFFICIAL
New build up
lineage-14.1-20200227-UNOFFICIAL-mb886
Changelog
Bluetooth fixed
Rom: https://www.androidfilehost.com/?fid=4349826312261733183
MD5sum: https://www.androidfilehost.com/?fid=4349826312261733184
Don't forget to read the op about TWRP https://forum.xda-developers.com/showpost.php?p=81672185&postcount=15
Code:
/*
* 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.
*/
Requirements:
# treblized vendor (P or O)
How to install:-
1. Enable Developer options in Settings app
2. Check Enable OEM Unlocking
3. Reboot to fastboot mode
4. Unlock your bootloader
5. Install TWRP-fastboot only through fastboot boot command (Extract the .img file from the zip)
6. Flash CosmicDan's TWRP Installer through your current TWRP. Credits to @CosmicDan for his TWRP and @mohancm for official TWRP sources.
7. Reboot to TWRP recovery
8. Go to WIPE then ADVANCED then click FORMAT data. This will remove Encryption on your device and allows you to set new passwords when installing the GSI. Note that this will format your internal storage.
9. Treblelize through TWRP Tissot Manager (Go to advanced, click Tissot Manager and choose the repartition userdata option. Select singleboot option then click repartition)
10. Flash Boot image
11. Flash Pie Vendor ( VENDOR_A1_PIE-NFE_20181011 ) by Adb sideload
12. Install System Image (Q_AB_v0.3.img.7z)
13. Flash permissiver_v2.zip or make your boot partition selinux permissive
14. Flash FixZygote.zip
15. Reboot To system
16. Special thanks to @erfanoabdi for porting the Q A/B GSI.
Bugs:-
1. Volte Fully Broken
2. Camera Not Working
3. Wifi Broken ( Connection seems but not connected)
Duplicate thread closed.
Please use this one instead.
Funk Wizard
Forum Moderator
Introduction
Pixel Experience is an AOSP based ROM, with all pixel goodies.
Disclaimer
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 blame me in any way for what happens to your device, I will laugh at you. BOOM! goes the dynamite ?
How to Flash
Clean
1. Install The Latest TWRP
2. Wipe -> Advanced Wipe -> Wipe System + Cache + Dalvik's/Art cache + Internal Storage (optional)
3. Install the Rom Package
4. Reboot
Dirty
1. Install the Rom Package
2. Wipe Cache+Dalvik's/Art cache
3. Reboot
Note
No need to flash Gapps, already included. Don't wipe vendor partition. Use Redwolf non-treble recovery.
Links
MEGA Repository
https://mega.nz/#F!INZgnAZI!9fuWhfCuazOO5YPBjxGlmA
Firmwares
https://forum.xda-developers.com/xia...mi-4x-t3856430
Google Camera
https://www.celsoazevedo.com/files/a...arthur/#apk506
Redwolf Custom Recovery
https://forum.xda-developers.com/xi...ent/unofficial-redwolf-recovery-t3776738/amp/
Build Author/Maintainer: Silent27
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Otg works
- Flash Rom works
- F2FS support
- Fastboot boot command support
Not working:
- Fastbootd
- Adb sideload
- Backup restore and image flash (system-vendor-product)
- Android 11 fully support
Download:
TWRP 3.4.0-14 Unofficial by mauronofrio
TWRP 3.4.0-12 Unofficial by mauronofrio
TWRP 3.4.0-10 Unofficial by mauronofrio
To Flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually or using a fastboot command.
Code:
fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img
or
Code:
fastboot oem reboot-recovery
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/Teamwin/android_bootable_recovery
https://github.com/mauronofrio/android_device_xiaomi_phoenix
https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
- Thanks to @merothh for the hard testing and other support
- Thanks to @bigbiff and @Captain_Throwback for the hard work on this android 10 TWRP
Thanks to all testers on the Telegram Group
Created 2020-09-16
Nice work the first build...
Thanks and waiting for 2nd build.....
mauronofrio said:
- Backup restore and image flash (system-vendor-product)
Click to expand...
Click to collapse
But does backup & restore for the data partition work?
Nice work!!!
Ya_SG said:
But does backup & restore for the data partition work?
Click to expand...
Click to collapse
it is in non working list
Nice. May I ask does Format data works reliably yet? (mean after Format data and flash rom, the phone won't automatically encrypt)
Never_Sm1le said:
Nice. May I ask does Format data works reliably yet? (mean after Format data and flash rom, the phone won't automatically encrypt)
Click to expand...
Click to collapse
Yes works
Finally!
Now I don't have to be afraid the phone will brick because of unknown sourced twrp from chinese.
Martensite said:
Finally!
Now I don't have to be afraid the phone will brick because of unknown sourced twrp from chinese.
Click to expand...
Click to collapse
I'm using the chinese one for months and it does not have any issues.
Until this has stable status or official status I'm more afraid of flashing this one
It's always asking for the password. Even though i did format data using that chinese twrp, when i flash this, it asks for password again.
TWRP 3.4.0-14 for Xiaomi Poco X2 (phoenix-phoenixin):
- Fixed decryption request also when the device is not encrypted.
TWRP 3.4.0-14 Unofficial by mauronofrio
mauronofrio said:
TWRP 3.4.0-14 for Xiaomi Poco X2 (phoenix-phoenixin):
- Fixed decryption request also when the device is not encrypted.
So the remaining issues still exist?
Thanks btw for new build
Click to expand...
Click to collapse
internal storage not showing in pc from this latest build. cannot copy rom zips to internal
This TWRP is worked on my Redmi k30 Phoenix. I have tried 'recovery-TWRP-3.4.0B-0209-REDMI_K30-CN-wzsx150', but failed boot twrp.
Thank u so much 'Dev', Please continue releasing newer version <3
arifn82 said:
internal storage not showing in pc from this latest build. cannot copy rom zips to internal
Click to expand...
Click to collapse
reboot again in TWRP, connect USB cable to pc. now u can see internal storage
How can i make the twrp permanent ?
Userbaban said:
How can i make the twrp permanent ?
Click to expand...
Click to collapse
Don't Flash stock ROM/ official ROM .
'boot ' fastboot command in lastest platform-tools won't work in that way.It assume the file is a KERNEL,not a whole boot image.This will only make device go blackscreen.Check the binaries' help before run this command!
I found a problem.
If I use WIPE to format internal storage in TWRP and still can't mount internal storage after rebooting recovery.
It will not be possible to copy ROM files properly.
If you restart the system, re-entering TWRP after a successful system boot will restore the system to normal.
I wonder if it can be fixed?
ask Decrypt password everytime I reboot to twrp.
Help!
Give a man a fish, feed him for a day. Teach a man to fish, feed him for life.
Click to expand...
Click to collapse
YOUR WARRANTY IS VOID IF YOU CONTINUE
A noob friendly guide on how to get the most out of your phone. The Xiaomi Redmi 8 has been touted as one of the most sold phone during the release alongside the Note 8. As of mid 2021, there have been a rise of actively developed kernels, recoveries, and finally custom ROMs. There were only a select few before, and may be dormant now. While the Xiaomi.eu custom may be enough for some, others may want a more different approach.
DRIVER
Windows
Generic "Universal ADB Fastboot" drivers are multipurpose drivers that support a wide range of device drivers using ADB and Fastboot. It may be a better idea to also install Xiaomi specific drivers if you also want to enable "USB Mode" as well.
Required drivers may be installed automatically via "Device Manager", selecting the device, then updating the driver. Windows 10 automatically installs required drivers for ADB, and USB Mode drivers on first connection.
Linux
Most mainstream distributions have them in their official repository. Searching for "android driver" usually includes ADB/Fastboot. USB Mode drivers can also be found by searching for "mtp" which usually has FUSE support builtin to the Linux kernel.
FIRMWARE
The official site for Xiaomi firmware usually only shows the latest drivers, and is hard to find more specific versions. The unofficial site does also include many archive versions. Although it is not required, it is more recommended to use what your phone shipped with. For example, my phone (global indo) came with PCNIDXM 11.0.2.0, and I will use the last A9 11.0.7.0 release. I prefer using the latest release, as A10 does not have the last release status yet, I chose to stay with A9. You may try upgrading your OS to A10 (A11 might also be released for our phone), but beware of "Android Anti Rollback" and always use an upgraded/higher firmware.
As it turns out, many members in the group have said that ARB is not active on our devices. It may be wise to stick with your region firmware and not another region to ensure compatibility.
BOOTLOADER
ALL DATA WILL BE ERASED. If you need to take backups, do it before starting. Copying backups to another device (phone or PC) is more reliable than an external SD card.
Requirements
3 days account age
7 days of usage
Enable "Developer Option"
Settings > About Phone > Build Number > Tap 7 times
Settings > Additional Settings > Developer Option
Enable both "USB Debugging" and "OEM Unlock"
Mi Account link
Xiaomi Unlock https://en.miui.com/unlock
Xiaomi Cloud https://i.mi.com
Find your device, it may help as the unlock tool has been buggy
Launch the unlock tool with admin rights
(optional) upgrade both the app and driver via the menu icon
Follow the instructions
You may require both SMS and data quota available in SIM 1 (the middle slot)
Turn off your phone, then turn it on with POWER + VOLUMN DOWN to boot into Fastboot mode
Start the unlock
A successful unlock shows an "(unlock icon) Unlocked" upon booting before the boot animation. It may show an unsuccessful unlock, but once your phone reboots, it may turn out to be unlocked. Your phone will reset to factory defaults.
FLASHING
It is not required to add ADB tools under your system's path. It does make future usage easier, and you also learn how to use computers, and is beneficial in the long run. Binaries and libraries are linked together. Simply copying the platform tools folder to another place, or vice versa, and launching the tools should be safe.
FIRMWARE FASTBOOT
Flashing an entire firmware is more safely done while in Fastboot mode. While there are also recovery archives, they do not include the entire partition library for a full clean install. There is also a risk of hitting an ARB http://xda-developers.com/xiaomi-anti-rollback-protection-brick-phone. There are GUI tools available, but they are very prone to bugs, and may not work well compared to simple CLI. Fastboot images also include "flash_all..." for both Windows (.bat) and Linux (.sh). To ensure better results, make sure the extracted path is short and has no unique characters (such as spaces) in the names. On Windows, it is preferable to use "Command Prompt" instead of "Powershell" as the latter is not as stable. Running the preferred terminal as admin/root is also a favorable.
Most users require an unofficial "vbmeta" patch to bypass "Android Verified Boot" for more advanced usage. The attached vbmeta bypasses builtin blocking.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
RECOVERY TWRP
TWRP is a general purpose recovery without too many features. It is much better than every stock recovery, but may have less features than the newer recovery projects. As a starting point, many other recoveries require having at least a custom recovery installed. While it is possible to Fastboot install other recoveries by extracting the archive, flashing the image, then copying over the default configs. This should not be relied upon as there may be additional scripts that are required to safely install other custom recoveries.
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
Click to expand...
Click to collapse
The official documentation for Fastboot states that not every phone supports 'fastboot reboot MODE', our phone does. We can safely append recovery to reboot into recovery mode from Fastboot, and expect it to work without rapidly trying to enter recovery mode via hardware buttons.
fastboot reboot recovery
ROOT MAGISK
It is recommended to backup the boot partition with TWRP. If you are using a custom ROM, a boot.img is inside the archive.
It is safe to flash magisk directly using TWRP. We should download the APK, rename it to ZIP, reboot to recovery and install, once it is done installing, rename it again to APK, boot to system and install it normally. Since our device qualifies as an exception, the boot partition is flashed instead of the recovery when reading the installation guide.
KERNEL
Other than the LOLZ kernel available here, there are a few additional kernels available in the Telegram chat group. I will try to provide more information later.
GAPPS
Like it or not, Google is here to stay. With so many GAPPs variants (respective packages, and addons), which should we choose? There might not be a correct answer as they are always evolving. The only thing most users MUST care about, is whether or not their recent changelog may include major stability issues such as 'fixed bootloop' and decide for themselves.
Most of the time, it should be more preferred to choose the core installer, then manually installing from there, YOUR required additional GAPPs (either via addons or the store). Fewer cars do mean fewer pileups, and not having too many apps installed will also cause less headaches.
ROM
The meat of the guide, and what most people seek when searching around the XDA. There are two main groups of ROMs, Generic System Image (GSI), and full custom ROMs specifically built for a device. Many devices may share common drivers with each other, such as the Redmi 8 series and the 8A. While not going too in-depth on a particular selection, one should take note and at least read through the installation instructions. Typically on modern A11 ROMs, most follow similar steps as followed;
reboot recovery
format data
reboot recovery
wipe cache, dalvik, data, system (sometimes vendor and internal)
reboot recovery
install archives
some may have a different step which are required for it to install. If one were to follow another guide for another phone, and ask for support on your phone's ROM thread, welp.
GSI builds have been around since A9 with treble support, and might have been a great idea. It allows users to try out a ROM not available within their reach, or try a completely new system such as UBports. It works much like a PC OS installer, but with PC experience, most users are required to finish their installation with needed tweaks. Additional drivers, security patches, custom user services and so on are the many examples that can easily be installed with minimal PC experience. Phones also require device specific tweaks to get the most out of GSIs and may vastly differ from each other. I am not against GSIs in general, but do hope for major breakthroughs in the development.
OFFICIAL adb/fastboot
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
OFFICIAL driver
https://mi.com/c/driver
OFFICIAL mi unlock
https://c.mi.com/thread-2262302-1-0.html
OFFICIAL twrp
Xiaomi Redmi 8
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
OFFICIAL magisk
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
MOD EDIT: Telegram link removed, please read the STICKY!
UNOFFICIAL firmware
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
UNOFFICIAL tool
GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot - GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
github.com
UNOFFICIAL vbmeta
attached below
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reserved - misc tips and tricks
While this guide was written with the Redmi 8 in mind and body, in can be put into good use on other phones as well.
MAGISK
With the current development of Magisk, it may be wise to wait on a new development path. Currently, there are reports of Magisk still working for some, but not for the vast majority of others. There are many workarounds, but as stated, will have varying success.
RELOCK BOOTLOADER
A forewarning for those that decide to relock their bootloader, there are people with destroyed systems after relocking. It is fully recommended to first full fastboot flash a stock firmware before attempting to relock. Simply unlocking again can successfully reboot the device, hinting there is a bug within Xiaomi. Some others have been unlucky and can cause EDL mode where only official service centers can unlock.
Others have also tested out many methods to workaround issues like these, and are having doubts as to how modern businesses are run.
MIGRATE
Migrate is a specially built backup/restore tool that makes moving from one ROM to another easily as the name suggests. It allows us to perform batch backups of apps, data, and/or permissions into a flashable recovery archive. Then finally completing the installation once we have fully installed the ROM by selectively restoring all/none of what has been backed up. It is possible to restore without TWRP, but using TWRP is recommended as it is more direct and user friendly.
Most of the time, it should be technically safe to migrate from OS versions since it only backup/restore user apps, one should take note of different min/max version specified in apps. A quick workaround is to find a trustworthy mirror, and download an universal app. At first launch, it is also recommended to do a quick test run by backing up an app, then restoring it by recovery.
backup app|data|perm
full install a ROM, GAPPS, magisk
boot system to complete the magisk installation
reboot recovery and flash the archive
boot system and complete the installation
The last reboot is not required, and can be manually cleaned up.
reserved - redmi 8 custom list
This is not a complete list of all available ROMs. I have purposely left ROMs unannounced in the XDA, GSIs, and dorment releases out. If one were curious, you could search for many more available, about twice the amount listed here. There may be a good reason they are not announced to the public, and we must use them with caution.
FIRMWARE
[Firmware] Xiaomi Redmi 8 [olive] [Auto updated daily!]
All Xiaomi custom ROMs users complain from a single problem, which is the firmware updates. As there are many devices with no one to provide the newest firmware update every single release, and developers who provide updates to devices may forget...
forum.xda-developers.com
ROM
MIUI BASED
[ROM][Stable] MIUI 11 xiaomi.eu
11.0.8.0 https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv11/xiaomi.eu_multi_HM8_V11.0.8.0.PCNCNXM_v11-9.zip/download https://androidfilehost.com/?fid=4349826312261737251 11.0.7.0...
forum.xda-developers.com
[ROM] [GUIDE] HOW TO INSTALL XIAOMI.EU MIUI 12.0.3 (WITH ALL FEATURES OF 12.5) ANDROID 10 ON REDMI 8
Hi, here's my guide on how install Xiaomi.eu MIUI 12.5 (A10) with all features of MIUI 12.5 on Redmi 8 What work - All functions of the phone What doesn't work - Nothing Note 1: If you fing bugs tell me in comments, maybe I could help you (I'm...
forum.xda-developers.com
MIUI ROM Builder - Create your own MIUI Custom-ROM! - mi-globe.com
Download your MIUI ROM just as you like it! Select from more than 20 modifications and build your very own Xiaomi MIUI custom firmware!
mi-globe.com
FULL CUSTOM
[ROM][LOS][11.0][OFFICIAL][olive] crDroid v7.12 for Redmi 8
*** Disclaimer I am not responsible for any damage you made to your device You have been warned crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features...
forum.xda-developers.com
[ROM][11.0][OFFICIAL][olives] Project Sakura v5.2 for Redmi 8/8A/8A Dual (unified)
Project Sakura is a custom ROM based on Lineage OS, It tries to remain true to it while also providing some more functionality and UI changes. Its sole purpose is to provide a platform which is powered by Lineage and is more customisable than...
forum.xda-developers.com
[ROM][11.0][olives][UNOFFICIAL] RevengeOS 4.1 for Redmi 8/8A/8A Dual [23/08/21]
RevengeOS is an operating system based on Android Open Source Project, built with a unique look and performance in mind. It's daily usage ready, lightweight and elegant. /* * Your warranty is now void. * * We're not responsible for bricked...
forum.xda-developers.com
[ROM][11.0][UNOFFICIAL][olives] Stag OS 11.0.R4.1 for Redmi 8/8A/8A Dual (unified)
Credits where they are Due: Google(No explanation needed n this regards) Lineage(For starting of the custom rom war) KCUF Rom(For acting as base) Omni Rom, Slim Rom, DirtyUnicorns, AospExtended and every other project whose contributions lead to...
forum.xda-developers.com
[ROM][AOSP][11.0][OFFICIAL][olive] dotOS v5.2.1 for Redmi 8
" #DroidOnTime " ROM Version: 5.2.1 Device: olive Maintainer: deadlylxrd Build Status: OFFICIAL * Your warranty is now void. * We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels...
forum.xda-developers.com
[ROM][11.0_r40][UNOFFICIAL][STABLE] ShapeShiftOS 2.7 // Solosis for unified Redmi 8/8A/8A Dual [olives]
/* * 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...
forum.xda-developers.com
[ROM][AOSP][11.0][OFFICIAL][olive] Havoc OS v4.8 for Redmi 8
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that provide a smooth premium experience. Just flash and enjoy...
forum.xda-developers.com
[ROM][11.0][OFFICIAL][olives] Komodo OS 3.2.1 for Redmi 8/8A/8A Dual (unified)
Komodo OS ROM for Xiaomi Redmi 8/8A/8A Dual (olives) * Your warranty is now void. * We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels. * You do it at your own risk and take the...
forum.xda-developers.com
[ROM][11.0][OFFICIAL][olives] LegionOS 3.13 for Redmi 8/8A/8A Dual (unified)
* Your warranty is now void. * We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels. * You do it at your own risk and take the responsibility upon yourself and you are not to blame us or...
forum.xda-developers.com
[ROM][11.0][UNOFFICIAL][olives] XTENDED XR-v9.0 for Redmi 8/8A/8A Dual (unified)
Disclaimer * We're not responsible for bricked devices, dead SD card or anything happens with your device * Flash on your own risk/knowledge...
forum.xda-developers.com
[ROM][11.0][UNOFFICIAL][olives] BaikalOS 11.1 for Redmi 8/8A/8A Dual (unified)
BaikalOS BaikalOS Project Until Android 10 the ROM been based on GZOSP. From 10.0 we changed our base to AICP. If there are any bugs, either we will sort them out, if it concerns our code base. This ROM isn't AICP supported, so there is no need...
forum.xda-developers.com
[ROM][11] Lineage Fan Edition v11.69 [ISOBAR][OLIVES]
Lineage OS Fan Edition for Xiaomi Redmi 8/8A/8A Dual (olives) * Your warranty is now void. * We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels. * You do it at your own risk and take...
forum.xda-developers.com
[ROM][11.0][UNOFFICIAL][LineageOS 18.1] for Redmi 8(olive)
would like to share my device tree from scratch from 0 to hero for redmi 8 olive i left developing that phone for a while 2day sharing my device tree for lineage 18.1 along with the rom . rom based on latest miui vendor prebuilt Your warranty...
forum.xda-developers.com
[ROM][11.0][OFFICIAL][olives] AncientOS 5.7 for Redmi 8/8A/8A Dual (unified)
/* * 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...
forum.xda-developers.com
https://forum.xda-developers.com/t/...-olives-pixel-experience-for-redmi-8.4366771/
GAPPS
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
FlameGApps
BiTGApps
Custom Google Apps Project
bitgapps.github.io
NikGApps - Custom Google Apps Package!
NikGapps Website
nikgapps.com
RECOVERY
Download TWRP for olive
Download TWRP Open Recovery for olive
dl.twrp.me
Xiaomi Redmi 8 (olive) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Redmi 8 (olive)
orangefox.download
RECD to use the latest beta 11.1 (1 aug 21)
[RECOVERY][UNOFFICIAL][olive] PitchBlack Recovery v3.1.0 for Redmi 8
/* * Disclaimer * * Your warranty is now void. * * We're 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...
forum.xda-developers.com
[RECOVERY] [OLIVE] Sky Hawk Recovery Project v2.2 [07-03-2020]
#include /* * Your warranty is... still valid? * * 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...
forum.xda-developers.com
KERNEL
[KERNEL][4.9.337] LOLZ V21 [olive/olivelite/olivewood/pine] [14/01/2023]
/* * Your warranty is now void lmao. * * 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...
forum.xda-developers.com
[KERNEL][SDM439][4.9.282] Moonlight Kernel v1.2
Moonlight Kernel for Xiaomi SDM439 a new era for your smartphone /* * 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...
forum.xda-developers.com
Redmi 8 development is seeing a huge spike recently with many available full customs, and some more unpublished here. There is also a group that is working on an alternative operating system, aiming to bring Linux (I usually exclude the 'GNU/' part) here. On top of that, there may be future attempts to not only bring UBports/Ubuntu Touch, but a few more arm64 ports
With the release of Android 13, many ROM devs are switching to an RDP (retrofit dynamic partition) scheme to allow A13 to install on our phones. These new ROMs require a modded recovery not currently released on official sites, nor in this subforum. To find these RDP type recoveries, see my signature that mentions a TG (Telegram) group.
The group is the main driving force, and sadly many of them are not an active part of this forum.
For those wondering, the MI439 release tag includes Olives (both lite and wood) and with the Redmi 7A. With RDP schemes currently the norm with ROM devs for our phones, it may be worth joining the TG to avoid installation missteps.
Impressive. Thank you
fonzacus said:
GSI builds
Click to expand...
Click to collapse
Can you explain what are they?
fonzacus said:
try a completely new system such as UBports
Click to expand...
Click to collapse
Is it really possible to have Ubuntu mobile on ginkgo ? That would be interesting.
Besides, I'm didn't find how to downgrade from A12 or 11 to A10 here.
GSI = generic system images. something like PC OSs. they can be installed on all hardware. but we 1st must know what our devices need (like a specific vendor partition)
this is mainly chatting about olives, dont know about ginkgo
for olives only, all you have to do is flash what android version you want to down|upgrade as you want
Jarod5001 said:
Impressive. Thank you
Can you explain what are they?
Is it really possible to have Ubuntu mobile on ginkgo ? That would be interesting.
Besides, I'm didn't find how to downgrade from A12 or 11 to A10 here.
Click to expand...
Click to collapse
fonzacus said:
this is mainly chatting about olives
Click to expand...
Click to collapse
My bad . I was doing a lot of searching and didn't realize that the thread was about redmi 8 and not redmi note 8. Sorry.
Thanks for explaining
fonzacus said:
With the release of Android 13, many ROM devs are switching to an RDP (retrofit dynamic partition) scheme to allow A13 to install on our phones. These new ROMs require a modded recovery not currently released on official sites, nor in this subforum. To find these RDP type recoveries, see my signature that mentions a TG (Telegram) group.
The group is the main driving force, and sadly many of them are not an active part of this forum.
For those wondering, the MI439 release tag includes Olives (both lite and wood) and with the Redmi 7A. With RDP schemes currently the norm with ROM devs for our phones, it may be worth joining the TG to avoid installation missteps.
Click to expand...
Click to collapse
hello friend, could you provide the group link?