Hello guys, this is my first guide here. So as the title says, I will show you how to install Lineage OS on your Redmi Note 3 device (kenzo).
So before following the guide, your device should have a unlocked bootloader and TWRP recovery.
I will also tell you how to fix in calls audio issue if you are facing it after installing Lineage OS 14.1
So let's begin.
First download the rom (refer to the official thread).
Download Cm14.1 firmware for kenzo (you can find it in the same rom thread)
Download Gapps (any package like micro or nano)
Procedure:-
1- Boot to TWRP recovery.
2- Go to wipe menu. Wipe system, data, dalvik cache and cache.
3- Now go to mount, and mount cust and persist.
4- Go to install. Select the firmware zip file you had downloaded. Install it. (This fixes in call audio problem)
5- After installing it you can unmount cust and persist from the mount menu.
6- After it flash the official Lineage OS rom which you had downloaded. (Install menu, zip)
7- After rom is flashed, flash Gapps package. (Install menu, zip)
8- After flashing Gapps, go to wipe and wipe cache, dalvik cache.
9- Reboot your device
10-Enjoy!
First Reboot will take a while so don't panic... Download Google camera if you want a more stable camera (since stock is quite buggy).. Also you can use Umang's Flashlight fix for the buggy Flashlight button.
Just in case you want to root the device, just download root add-on (found in official thread)
Enjoy the experience.. ?
xzy99 said:
Hello guys, this is my first guide here. So as the title says, I will show you how to install Lineage OS on your Redmi Note 3 device (kenzo).
So before following the guide, your device should have a unlocked bootloader and TWRP recovery.
I will also tell you how to fix in calls audio issue if you are facing it after installing Lineage OS 14.1
So let's begin.
First download the rom (refer to the official thread).
Download Cm14.1 firmware for kenzo (you can find it in the same rom thread)
Download Gapps (any package like micro or nano)
Procedure:-
1- Boot to TWRP recovery.
2- Go to wipe menu. Wipe system, data, dalvik cache and cache.
3- Now go to mount, and mount cust and persist.
4- Go to install. Select the firmware zip file you had downloaded. Install it. (This fixes in call audio problem)
5- After installing it you can unmount cust and persist from the mount menu.
6- After it flash the official Lineage OS rom which you had downloaded. (Install menu, zip)
7- After rom is flashed, flash Gapps package. (Install menu, zip)
8- After flashing Gapps, go to wipe and wipe cache, dalvik cache.
9- Reboot your device
10-Enjoy!
First Reboot will take a while so don't panic... Download Google camera if you want a more stable camera (since stock is quite buggy).. Also you can use Umang's Flashlight fix for the buggy Flashlight button.
Just in case you want to root the device, just download root add-on (found in official thread)
Enjoy the experience..
Click to expand...
Click to collapse
it this a joke? this looks like a chinese copy of a guide posted 1 week ago and is only 2 posts under this:
https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
what is your intention?
@massan1 I hope you have eyes through which you can read properly. No offence brother. Well, I didn't copy it. Plus that guide is made for those who have locked bootloader. Second, I am posting this for those who want to clean install Lineage OS with the call audio fix. So, if you believe I have copied it , just keep believing it.
Keep burning.. I'll get ice packs for you. Thanks.
I was on cm 13 before flashing lineage OS 14.1..Now the issue iam facing is that while making calls without headphones the both myself and other person won't hear a thing. On reverting back to cm 13 everything works fine. Currently on nightly 07.02.2107
r28 said:
I was on cm 13 before flashing lineage OS 14.1..Now the issue iam facing is that while making calls without headphones the both myself and other person won't hear a thing. On reverting back to cm 13 everything works fine. Currently on nightly 07.02.2107
Click to expand...
Click to collapse
just flash upgraded firmware or change build.prop:
https://forum.xda-developers.com/re...stall-lineage-os-locked-t3546154/post70826457
Raaj52 said:
This is not a build.prop issue!! In order to work with the old firmware (patched one) you have to make fluence to none, this is done when you use patched VoLTE. If you make fluence to none the latest MM firmwares won't give sound in call, many are getting no sound because they are using the old patched firmware. Since the native VoLTE is fixed no need of the old firmware and you don't need to change fluence to none. Just flash the latest firmware and you are good to go.
Still doubt? OK then I need to tell you one more thing, The first patch for VoLTE for MIUI MM was made by me (you can check that in MIUI Global forum) and sudeep made a firmware.zip with my NON-HLOS.bin and I can see that the same is copied in the firmware.zip, in order to get fluence working in the patched firmware it should have used with the correct adspso.bin.
Many are thinking that changing firmware is useless but in reality it comes with lot of stability fixes, so I recommend everyone to update your firmware to the latest one instead of all this build.prop editing craps.
What is the problem if I edit build.prop? --> You have to edit your build.prop whenever you flash a ROM, you can't avoid it unless you flash the latest firmware.
Why I am so confident? --> Because I know what is firmware and How does it work!
If you have "no sound in calls" issue even after you change the firmware I recommend a clean mi flash tool flashing with the latest MIUI ROM (because it will fix all your partition related stuffs, instability issues)
@abhishek987 @akhilnarang could you please add the "solution for no sound in calls is to flash the latest firmware" in your first post?
Click to expand...
Click to collapse
GUIDE SECTIONS QUICK LINKS
#1 - MIUI ROM, Types of MIUI ROM
#2 - TWRP, Types of TWRP, Flashing TWRP
#3 - Unlock, Root, Flashing via TWRP
#4 - Custom ROM, Types of custom ROMs
MIUI ROM
MIUI (pronounced as Me-You-I) is Xiaomi's custom built firmware like Samsung's OneUI, HTC's SenseUI, OnePlus's OxygenOS which is built on top of Android's AOSP base with its own modifications and features. At first glance it resembles like a hybrid between Google's Material Design and Apple's iOS. But unlike Stock Android or iOS, MIUI is very intuitive, feature rich and has multiple tweaking options. MIUI is updated regularly depending on the development branch. Xiaomi gathers reports, feedbacks and suggestions from the community, addresses the bug-fixes and integrates new features upon request. Most of Xiaomi devices are regularly patched with security updates every 2-3 months. The flagship "Mi" series like Mi9 receive quicker Android version updates than their budget "Redmi" series like Redmi 7, Redmi Note 7 Pro etc.
TYPES OF MIUI ROM
There are 2 development branches of MIUI ROMs for all Xiaomi devices.
A) Stable Builds
It is updated on a monthly basis or longer
New features are added slowly after testing
Higher system stability and less bugs than Beta ROMs
It has a four digit numbering scheme (X.X.X.X)
For eg. 8.X.X.X is MIUI8 Stable Build
Stable builds come in 2 variants
1. MIUI China Stable ROM
This ROM is pre-installed on all Xiaomi devices sold in China.
It is made for the Chinese market & contains Chinese MIUI apps.
Google Apps are absent. You can install them manually.
It supports Chinese & English languages.
2. MIUI Global Stable ROM
This ROM is pre-installed on all Xiaomi devices sold outside China.
It is made for the International market & contains English MIUI apps.
Google apps are pre-installed by default.
It supports 50+ languages.
B) Beta Builds
It is updated on a weekly/bi-weekly basis or longer.
New features are added quickly for testing.
Lower system stability and more bugs than Stable builds.
It has a three digit numbering scheme (X.X.X)
For eg. 6.11.21 is MIUI8 Beta build for 21th Nov, 2016.
This ROM is not pre-installed on any Xiaomi device.
You can install Beta build over Stable build manually.
Beta/Developer builds come in 2 variants.
1. MIUI China Beta ROM
It is made for the Chinese market & contains Chinese MIUI apps.
Google Apps are absent. You can install them manually.
It supports Chinese & English language.
2. MIUI Global Beta ROM It is made for the International market & contains English MIUI apps.
Google apps are pre-installed by default.
Supports more than 50+ languages.
TWRP
Team Win Recovery Project is a custom recovery which is flashed over the stock recovery as it gives user more options such as flashing custom ROMs, kernels & scripts, take full system backups, restore backups, root etc.
TYPES OF TWRP
1. TWRP by iscle: https://forum.xda-developers.com/mi-max-2/development/recovery-twrp-3-1-1-0-touch-recovery-t3652762
Based on Stock TWRP 3.1.1-0 with no modifications.
Ported from Redmi Note 4 (mido)
English language as default
Need to flash dm-verity zip immediately after flashing this TWRP, else your phone wont boot.
2. TWRP by xuefer: https://forum.xda-developers.com/mi-max-2/development/twrp-max2-oxygen-t3634437
Built using LineageOS 14.1 source
Built and tweaked for Mi Max 2 (oxygen)
Decryption support added for /data
Faster transfer using adb push
Extra fonts added
FLASHING TWRP
Unlock bootloader here: https://forum.xda-developers.com/mi-max-2/how-to/guide-unlocking-bootloader-mi-max-2-t3641257
Install "Minimal ADB+Fastboot Drivers": https://forum.xda-developers.com/showthread.php?t=2317790
Download TWRP file and copy the file in the C:\Program Files (x86)\Minimal ADB and Fastboot folder
Download dm-verity disabler and copy the file in your phone: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Switch off phone. Hold Power + Volume Down to boot into fastboot mode. Connect it to PC.
Inside the folder where TWRP file is present, open command prompt window.
Type "fastboot devices". Your phone will get detected with serial number.
Type "fastboot flash recovery <recovery_name.img>". TWRP will get flashed on your device.
E.g. "fastboot flash recovery twrp_3.1.1-0.img".
Type "fastboot boot <recovery_name.img>". You will boot into TWRP. Disconnect phone from PC.
E.g. "fastboot boot twrp_3.1.1-0.img".
On the screen, swipe to allow modifications and select your language. Uncheck "Keep system read-only"
Select Install and then choose the dm-verity disabler zip and swipe to flash.
Select Backup and check all partitions. Swipe to backup. The backup will be stored in "TWRP" folder
Select Reboot and then system. You will be asked if you want to disable the stock recovery. Swipe to disable.
You will boot into MIUI with TWRP installed.
TWRP ZIPs
These zips are meant to be flashed with TWRP with a specific order. Before flashing any zip make sure you have taken full backup of your device partitions using TWRP.
1. no-verity-opt-encrypt: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Also called as dm-verity disabler/lazy flasher
"dm-verity" is a feature in the MIUI kernel which checks and prevents the phone from booting normally if you modify the phone. (e.g. flash TWRP)
To prevent that, you need to flash the dm-verity disabler zip which removes dm-verity check and also decrypts the /data partition so that you can boot into MIUI normally.
Else you can flash a custom ROM immediately after flashing TWRP which removes the MIUI system and kernel
2. Xiaomi.EU ROM Patch: https://forum.xda-developers.com/mi-max-2/development/xiaomi-eu-rom-patches-dpi-change-t3656296
You need to install Xiaomi.EU ROM before installing these zips via TWRP.
MIUI to Google Apps: Replaces default MIUI apps with Google apps.
Google Now/Pixel Launcher: Replaces stock MIUI launcher and enables Google Assistant via build.prop tweak.
DPI changer: Change values from stock 440 (low res, bigger) to 325 (high res, smaller).
3. Hardware Key Disabler : https://forum.xda-developers.com/mi-max-2/themes/mod-disable-hardware-keys-lineageos-rom-t3696108
This mod enables on screen navigation bar and disables the hardware keys
You can revert back to stock configuration by flashing "enable_HWkeys.zip"
FLASHING VIA TWRP
Some important terms to remember:
Formatting data: Factory resets the phone, will erase internal storage, will remove encryption
Wiping data: Factory resets the phone, will not erase internal storage, will not remove encryption
Clean flash: Flashing a new ROM or an updated version of the same ROM by wiping or formatting data of current ROM in TWRP. Cache & dalvik is automatically wiped in TWRP.
Dirty flash: Flashing an updated version of the same ROM without wiping or formatting data of current ROM in TWRP. Cache & dalvik wipe is recommended in TWRP.
Treble TWRP: Custom TWRP which uses existing /cust partition and formats it into /vendor partition which is needed for non-MIUI Oreo and Pie ROMs where Treble is used.
Notes:
Always read the entire post & comments of the custom ROM page before asking any questions, chances are your query has already been answered.
You do not need to wipe /system partition manually, it its automatically wiped when a ROM is flashed by the updater-script inside the ROM zip. General rule of thumb is always clean flash any ROM, unless mentioned by the ROM developer or maintainer that dirty flashing is okay.
Requirements:
Unlocked bootloader with TWRP installed
Phone partition backup using TWRP
All data backup from internal storage (sms, contacts, files etc.)
Official MIUI ROM encrypts /data partition, you will need to Wipe > Format Data to decrypt it completely else need to flash dm-verity disabler zip or Magisk zip.
1. Rooting MIUI / non-MIUI ROM
Boot into TWRP (Power+Volume Up)
Install > Magisk zip
Reboot > System
2. Flashing official MIUI recovery ROM
Boot into TWRP
Wipe > Format data (if storage is encrypted)
Reboot > Recovery
Install > MIUI ROM zip + Magisk Zip
Reboot > System
3. Flashing custom MIUI ROM (Xiaomi.EU / RevOS / Mi Globe)
Boot into TWRP
Wipe > Format data (if storage is encrypted)
Reboot > Recovery
Wipe > Factory reset
Install > Custom MIUI ROM zip
Reboot > System
4. Flashing LineageOS/AOSP ROMs (Non-Treble)
Boot into TWRP
Wipe > Format data and Reboot > Recovery (if storage is encrypted)
Wipe > Factory reset
Install > Firmware + ROM Zip + Google Apps Zip
Reboot > System
5. Flashing LineageOS/AOSP ROMs (Treble)
Boot into Treble TWRP
Wipe > Format data (if storage is encrypted)
Reboot > Recovery
Wipe > Factory reset
Install > Firmware + ROM Zip + Google Apps Zip
Reboot > System
TYPES OF CUSTOM ROMs
There are mainly two types of custom ROMs for any Android device. You need to flash them on your phone using custom recovery such as TWRP.
1. Stock based ROMs
They are based on the factory ROM which came pre-installed on your device. In case of Xiaomi devices, developers take the stock China Stable/Beta MIUI ROMs as base, perform modifications and tweaking and then re-pack it. Examples of stock based MIUI ROMs.
Xiaomi.EU: https://xiaomi.eu/
MIUI Pro: https://miuipro.by/
Mi Globe: http://mi-globe.com/
Epic ROM: http://www.epicrom.pro/
2. Custom based ROMs
They are typically based on either AOSP or LineageOS code. They can either be ported from similar devices or built using the kernel source code of a particular device. Xiaomi has not yet released kernel source code for Mi Max 2. Kernel source codes are needed for relatively stable and bug-free experience on custom ROMs. Examples of some popular custom ROMs
A) AOSP based ROMs
AOSPExtended: https://www.aospextended.com/
Nexus Experience: http://www.nxrom.us/
SlimRoms: https://slimroms.org/
B) LineageOS based ROMs
LineageOS: https://lineageos.org/
Resurrection Remix: http://www.resurrectionremix.com/
XenonHD: http://www.xenonhd.com/
Reserved #4
Reserved #5
Thanks for wonderful explanation and for content too
Hi,
I flashed TWRP from PC using above procedure & tried to install no-verity-opt-encrypt (version 5.1.zip).
I got below error while installing :
Error: unpacking ramdisk failed
Phone booted normally & TWRP is not there.
How to fix this issue?
I know these questions are sometimes annoying, but for someone who hasn't been following Android development since Android 4.4.4, I'm a little overwhelmed by all this information. What does the "Oxygen" mean? Is it just a certain model of the Mi Max 2? I see all ROMs say Oxygen but none explain what it means. If it's a model of the Max 2, how can I know if the version I have is Oxygen?
Thanks and sorry if it's a dumb question
It's a code name for Max 2, so you don't mistakenly flash the wrong ROM, if it says Oxygen, than you're sure it's for your model, not for i.e. Mi Max...
Sent from my Mi Max 2 using Tapatalk
Hello,
I have a Mimax 2 bootloader unlocked, rooted, SuperSU, twrp 3.1.0-0 (cofface) installed. I installed, after some difficulties, the rom xiaomi.eu 7.12.28. When I'm in recovery, after the flash I sometimes have a red line that says "... no-verity-opt-encrypt ..." blah blah. But the phone boot normally, everything works fine. Do I have to install lazyflasher-no-verity-opt-encrypt or can I do without it?
thank you and sorry for my bad english
Hi, I have unlocked BL and installed Developer ROM 7.12.28. for a few weeks now. Can I install latest 8.1.4 developer ROM with TWRP without wiping cache/dalvik and will I keep my data/apps that way?
Thanks.
Sent from my Mi Max 2 using Tapatalk
@frulex, I installed the 8.1.4 (via updater) after using the 7.12.28, without any problem. That you erase the cache where not, you will not lose the data of your apps
What was the size of that update file you installed? I first got notification of 8.1.4 update and it said it's something like 95 MB file size. Tried to install it twice via updater, it starts updating, boots to TWRP and ends with error without installing. After reboot notification changed and now it offers update of full 1.5 GB 8.1.4 version ROM. I didn't have time to download and try that but I wonder will that also end in error and that's why I ask about downloading .zip and flashing through TWRP.
Sent from my Mi Max 2 using Tapatalk
These are the roms I used, as you see 8.1.4 weighs 1.2 Go
edit: I had uploaded an image of the explorer but it does not appear! (decidedly i'm struggling with this forum, lol)
Not many roms for this phone..it sux..I regret exchanging it with my oneplus 3..
How many ROMs have you expected in 3 days since kernel source has been released?
Sent from my Mi Max 2 using Tapatalk
good tutorial
thanks to you @SharkcpN . this is such a clearly, easily tutorial "How to Flash TWRP" for newbie like me..
I tried and succeed with no error at all.. once again, thanks for your good job :good:
Hi there! Thanks for the excellent thread and collection of links. I started here and found a setting on this phone's NVRAM that I have not seen mentioned anywhere else, and you will need it for LTE unlocking.
Below are the exact steps, many taken from this guide, that I used to go from a phone with an unlocked bootloader to flipping the LTE B2 and LTE B4 bits on. After I did it and rebooted, I suddenly had a working LTE connection!
I cannot yet PROVE that this actually enabled the bands, but it hasn't hurt anything. I will test for that in a couple days, because the only dumb thing I did was afterwards, when I accidentally re-locked the bootloader by not paying attention to what I was doing. If you use the MiFlash program to install a ROM, don't forget to change the setting in the lower right corner!
Notes for those wishing to use this as a guide:
I don't think you can brick the phone completely playing with just these settings, but you should be prepared to restore everything. Take backups where I mention them, and if you need the device working, you should have a current MIUI fastboot flashable image, available from the official website, on hand.
This is LTE only and there are different settings for GSM that work the same way.
The steps are numbered, but you should also understand mostly what they do.
You may ignore the VM part and just boot your normal Win7 with driver signature checking DISABLED (F8 on boot). I use Linux and I'm security-conscious about downloading programs that I can't verify, so I'm using a VM.
There is a dialpad option for opening the diag port (if you have root), but it did not work for me, so I have provided a method that I know works and it clears itself upon reboot
QXDM's NV browser has a checkbox for "DUAL SIM". You don't need to check it for this process, you won't lose SIM2.
Downloads section:
(REQUIRED) Most are in the links provided by OP:
MiFlash (official one)
QPST 2.7.460
QXDM 3.12.714
Minimal adb and fastboot
no-verity-opt-encrypt-6.0.zip
twrp-3.2.1-0-oxygen.zip
SuperSU-v2.82-201705271822.zip
(OPTIONAL, needed if you mess up. I chose to have it ready to go.):
From MIUI official site, go to the ROMs for the Max 2. The one on the download button here is NOT what you want.
Select Flashing guide, then on on the left hand side select FastBoot.
Download the image for your device. I have a copy of oxygen_global_images_V9.0.3.0.NDDMIEI_20171209.0000.00_7.1_global_298fd5f49c.tgz
SETUP SECTION (install tools and root phone):
Enable developer mode and USB debugging on phone
Boot into a Windows VM, pressing F8 to go into unsigned drivers mode
Install MiFlash, just to get the drivers
Install QPST and QXDM for later
Install adb and fastboot
Pass USB port through to VM and check adb is working by twice typing
Code:
adb devices
Shutdown phone and remove SD card from phone.
Add no-verity-opt-encrypt-6.0.zip and SuperSU-v2.82-201705271822.zip to SD card
Put SD card back in phone
Reboot phone into fastboot mode using PWR & VOL-, and re-pass to VM if needed
From cmd terminal in adb folder,
Code:
fastboot flash recovery twrp-3.2.1-0-oxygen.img
Code:
fastboot boot twrp-3.2.1-0-oxygen.img
Once TWRP comes up, install no-verity-opt-encrypt-6.0.zip
(OPTIONAL) Make a backup. I didn't because I don't want the ROM that's on there anyway.
Reboot and ensure MIUI loads
Shutdown phone and reboot into TWRP using PWR & VOL+
Install SuperSU as a system app
Reboot into MIUI
Access and edit the NVRAM:
Connect the device back to the computer, pass to VM if necessary
From your terminal in the adb folder,
Code:
adb devices
Grant debug permission on the device, if it asks again
Code:
adb shell
Code:
$su
Grant permission in superSU popup
Code:
#setprop sys.usb.config diag,adb
When the device reconnects, re-pass to VM if needed, and it may install another driver
Open QPST Configuration and make sure the device's port is enabled.
At the top, go to "start clients" and open "software download"
In the "Backup" tab, choose a location to save your file and hit Start, just in case you do break something
Once finished, close "software download" but leave QPST Configuration running
Open QXDM Professional
Under Options->Communications, make sure your phone is set "active" then set "target port" to the port it's on, then press OK
Go to NV Browser in the dropdown on the upper left.
Scroll down to 06828 :"nv_lte_bc_config_type.lte_bc_config"
Press READ and save this value somewhere in case you forget which bits you set! Mine was: 2061584302293
It's little-endian, and I wanted to flip bits from 0 to 1 to enable bands {2} and {4}, so I added 2^({2}-1)+2^({4}-1) = 10 to get a value of 2061584302303
Enter your new value in the "value" field and press "write"
Now, scroll down to the corresponding LTE prefs value at 65633
Read again. This should be the same number you had before, in hexadecimal format. Mine was 0x1E0000000D5, so to add B2 and B4 (Combined value 0xA), I changed it to 0x1E0000000DF
Again, enter your new value in the "value" field and press "write"
I doubt this requires any sort of "safe shutdown," but I hit "offline" then closed QXDM, then closed QPST, then rebooted the phone.
For a quick test, you can set network preferences to "LTE ONLY" by going to the dialpad and hitting *#*#INFO#*#*, then selecting your SIM card and using the dropdown in there. Mine was preferring HSPAP because the signal was stronger, even though the data was blocked.
Further testing I want to do when I get the bootloader unlocked again:
Use an app that shows what bands are in use to prove I'm on B2 or B4
Try disabling bands I will never use that have similar frequencies to the bands I want to see if signal improves
TWRP ZIPs
These zips are meant to be flashed with TWRP with a specific order. Before flashing any zip make sure you have taken full backup of your device partitions using TWRP.
1. no-verity-opt-encrypt: https://build.nethunter.com/android-...y-opt-encrypt/
Also called as dm-verity disabler/lazy flasher
"dm-verity" is a feature in the MIUI kernel which checks and prevents the phone from booting normally if you modify the phone. (e.g. flash TWRP)
To prevent that, you need to flash the dm-verity disabler zip which removes dm-verity check and also decrypts the /data partition so that you can boot into MIUI normally.
Else you can flash a custom ROM immediately after flashing TWRP which removes the MIUI system and kernel
2. Xiaomi.EU ROM Patch: https://forum.xda-developers.com/mi-...hange-t3656296
You need to install Xiaomi.EU ROM before installing these zips via TWRP.
MIUI to Google Apps: Replaces default MIUI apps with Google apps.
Google Now/Pixel Launcher: Replaces stock MIUI launcher and enables Google Assistant via build.prop tweak.
DPI changer: Change values from stock 440 (low res, bigger) to 325 (high res, smaller).
What does It mean??
Hi guys, I have been testing the GSI AOSP ROM (from @phhusson) on our CC9e and works well most of the functions (maybe is not for daily driver but you can test and decide), except for :
-the FP sensor doesn't work
- the camera preinstalled not adjust to interface and the quality is bad (install gcam instead)
- Maybe other things
For those who want to test the AOSP Q sensation try the next steps:
You need a unlocked bootloader a TWRP working on your device and maybe some knowledge on how TWRP works.
1- Install the latest android 10 xioami.eu rom for cc9e (in order to get the vendor of android 10).
2- Download the latest AOSP 10 gsi system image (thanks to @phhusson ), extract it to get the .img file, copy it to internal memory or a otg device, then back to twrp.
2- Enter to wipe option on twrp, and slide to wipe data and cache partition, then go to install option and flash the .img file in the system partition.
3- Once it is installed just reboot to system and test the sensation of an AOSP rom
fer15 said:
Hi guys, I have been testing the GSI AOSP ROM (from @phhusson) on our CC9e and works well most of the functions (maybe is not for daily driver but you can test and decide), except for :
-the FP sensor doesn't work
- the camera preinstalled not adjust to interface and the quality is bad (install gcam instead)
- Maybe other things
For those who want to test the AOSP Q sensation try the next steps:
You need a unlocked bootloader a TWRP working on your device and maybe some knowledge on how TWRP works.
1- Install the latest android 10 xioami.eu rom for cc9e (in order to get the vendor of android 10).
2- Download the latest AOSP 10 gsi system image (thanks to @phhusson ), extract it to get the .img file, copy it to internal memory or a otg device, then back to twrp.
2- Enter to wipe option on twrp, and slide to wipe data and cache partition, then go to install option and flash the .img file in the system partition.
3- Once it is installed just reboot to system and test the sensation of an AOSP rom
Click to expand...
Click to collapse
Very nice.Thank you much more.
• Introduction
Samsung Galaxy J4 is a phone based on Exynos 7570 with 720x1280 resolution, ARM Mali T720 GPU, Cortex A53 Quad-core CPU. This phone released in 2018 with Android 8 shipped out-of-box, and available OS update until Android 10.
But, since it already 2 years (in 2020) from launched, this phone only have developer that can be counted on one hand. There is no custom rom for this device, and custom kernel only 1 or 2 or 3 (I'm building this kernel right now, but I'll release it when I have enough post count )
The good news is, this device is Treble supported! So we can install most of available GSI, even without any vendor or kernel required.
• Stock ROM vs GSI
What's the different? In my opinion, very much! As we know, GSI is based on AOSP, which is pure android, and almost no bloatware. And, for other GSI, like Havoc or Lineage or any GSI like that, have cool theme and animation. Why not giving a try?
• Warning
Although this is cool, but, remember this is GSI, bugs are widely open. Bugs I found are in below.
Second thing, your warranty is void! This is sure, you unlock bootloader, Install TWRP, even install GSI, that surely will trip knox and voiding warranty.
And, last one, backup ALL of your data. This process will wipe your data partition.
• Bugs
As far as I use Havoc-OS GSI 3.7 Android 10, I feel these bugs:
1. Camera Streching, use Open Camera
2. Video recording, use Open Camera too
3. Camera in Whats'App
4. I forgot
If you feel other bugs, please write it in below.
• Steps
Since currently this phone have Android 9 Android 10 update, the steps will be different. Dont worry, I'll write all the steps
From Android 9 stock :
1. Download TWRP 3.2 and 3.4
2. Copy to your PC
3. You must have Odin
4. Download GSI image A64 A-ONLY / ARM32_BINDER64 and put it in your Micro SD card or USB (for OTG)
5. Download Gapps (optional if you want google apps installed) nano / pico ARM-10.0
6. Download Magisk if you want root
7. Dont forget to copy downloaded zip file to Micro SD Card or USB (For OTG)
8. Flash TWRP 3.2 via odin, then reboot recovery
9. Wipe - format data - yes
10. Wipe - advanced wipe - choose system, data, internal, cache / dalvik cache
11. Install - install image - choose gsi image you downloaded - choose system image
12. reboot recovery
13. mount - system
14. wipe - advanced wipe - choose system - repair filesystem - resize
15. install - install gapps zip
16. reboot download
17. flash TWRP 3.4
18. reboot recovery
19. flash magisk (optional)
20. flash zygotefix
21. reboot and complete setup
From Android 10 stock :
1. Download TWRP 3.2 or OrangeFox
2. Download any a64 A/B (arm32_binder 64) xz decompress it* and put it in your Micro SD card or USB (for OTG) or internal memory
3. extract it with any extractor app
5. Download Gapps (optional if you want google apps installed, some have it included)
6. Reboot recovery
7. wipe. advance wipe. system, data, dalvick cache.
8. Flash the extracted GSI
9. Flash Gapps if they are not included
10. Flash magisk (optional)
11. Reboot system
And Done!
If you have anything you ask, feel free to join our Telegram group : t.me/SamsungGalaxyJ4
Or PM me in Telegram : t.me/hendramanudinata
Cheers!
As you all may know, CorvusOS is one of the most popular custom ROM At the moment, and the developers known as "Tipz Team Builds" Have made it compatible for J7 Prime!
(IMPORTANT!!, There are currently lots of bugs in CorvusOs, so i recommend waiting for a stable release, if you wanna install it then im not responsible for any damages done to your phone, i warned you!)
(Please as always take a nandroid backup of your phone as with any other custom rom installation!)
Credits :
Tipz Team Builds original thread : https://forum.xda-developers.com/t/gsi-beta-11-phh-corvusos-v16-8-avalon.4212765/
Downloads :
Treblue : https://www.mediafire.com/file/xskqacpul8glpfx/Treblue_v2.0.zip/file
NikGAPPS : https://www.mediafire.com/file/fk3xv8xr8i2bxrt/NikGapps-basic-arm64-11-20201231-signed.zip/file
CorvusOS : https://sourceforge.net/projects/ti...e-25082021-Beta-Official-0000.img.xz/download
Installation :
*I cannot stress this enough, Please always take a nandroid backup of your phone when installing a custom rom!*
1. Download all of the above
2. Boot into custom recovery
3. Wipe : Cache, Dalvik Cache, Data, System, Vendor *DO NOT WIPE INTERNAL STORAGE*
4. Extract the CorvusOs*version*.img.xz as .xz
5. Flash the extracted CorvusOs as system image
6. After flashing CorvusOs, Mount System and vendor, *If you can't mount it, Reboot into recovery again*, After mounting Flash Treblue
7. After flashing treblue Flash NikGAPPS
8. Wait for it to finish
9. To confirm it works reboot into recovery and look at terminal, it should say something like "Custom ROM (TREBLE) CorvusOs"
10. Now reboot into system and enjoy!!
After installation it should reboot a few times, let it rest for 5-10 minutes
Credits are given above, please give me suggestions on how to improve my guide!
Also, if you are gonna update to the latest version, do not download ones with "gapps" in their name, also the file must have either vndklite or nonlite on the file, so it looks something like this
CorvusOs-*version*-treble-arm64-vndklite/nonlite-*DATE OF RELEASE*-Beta/Stable-Official-0000.img.xz