Related
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
Hey guys,
So recently I tried a few custom roms and noticed that the steps for all roms are slightly diffferent and that confused. Hence decided to try everything available and come to a easiest step by step conclusion:
Steps :
At the time of writing this guide I was on codeworkx universal TWRP running stock OOS 4.7.6 with Magisk 15.2. But the steps would work from any rom to any rom.
1) Flash codeworx universal TWRp from here : https://goo.gl/yXx2sK
2) Boot into twrp and using your pattern/pin decrypt data, yes thats the good part no matter if you are on stable or custom be it android 7.1.1/8.0/8.1 this recovery is able to decrypt all roms.
3) Make a nandroid backup and copy all contents of your internal storage to a pc/ choose the backup method of your choice.
4) Make sure you have at least 50% battery charged.
5) In twrp go to wipe . format data type yes and tick
6) Reboot to recovery
7) Perform a factory reset also wipe internal storage.
8) While in twrp copy the rom and firmware and gapps to your phone
9) Flash first the firmware if needed by the rom, then flash the rom and then gapps and then dm verity zip if needed by the rom. Wipe cache and dalvik. (note if you are flashing a stock rom please flash magisk and then make the first boot otherwise TWRP will be erased)
10) Boot into rom and set it up
11) Flash magisk or supersu if needed.
Heres a step by step video :
Credits :
@Funk Wizard
@codeworkx
xda developers
lineage os
team twrp
oneplus
Please note : Do this at your own risk. I would not be responsible for any damage.
If I have missed any names please PM me I will ensure i add it.
Why all this codeworx TWRP hype all of the sudden? Bluspark has never let me down yet. What is the difference between the two?
It's good if you add DM verity to the list as "if needed" because certain custom ROMs require it.
I'll be looking at this thread at some point in the future. Thanks.
Anyone followed the above and have comments to make ?
after flash any rom black screen and blue LED
any help
So, I searched the internet for a method to flash a CustomROM on the OnePlus 6T. But somehow none of them worked, so I worked on one myself that at least works for me.
There are 2 methods, use Method A if you don't have a custom ROM installed and still use OxygenOS. Use Method B if you are using a custom ROM and want to have another one:
Method A: From OxygenOS to CustomROM
1. boot in twrp
2. in twrp, do a factory reset
3. flash latest oos zip(flashable ota, link will be below)
4. flash twrp installer zip(i recommend mauronofrio´s twrp, link wil be below)
5. check current slot, then reboot in twrp
6. check if slot changed, then do a factory reset
7. flash latest oos zip
8. flash twrp installer zip
9. reboot recovery, and check if slot changed
10. factory reset
11. flash custom rom zip
12. flash twrp installer zip
13. reboot twrp(check current slot)
14. check if slot changed(if yes:it worked, if no:repeat)
15. additional: flash magisk&gapps
then,your rom is ready to use
Method B: From Custom ROM to another Custom ROM
1. reboot to twrp
2. in twrp, do a factory reset
3. then select advanced wipe: wipe system,cache,data. DON’T WIPE VENDOR
4. flash custom rom zip
5. flash twrp installer zip
6. check which slot you´re in
7. reboot twrp
8. if slot changed, everything worked
9. flash gapps and magisk if you want
then, your rom is ready to use
So, I hope I have spared you many problems and wish you much fun with your Devices.
Links:
Mauronofrio TWRP: click here
OxygenOS Stable OTA 10.3.1: click here
DirtryElectro said:
So, I searched the internet for a method to flash a CustomROM on the OnePlus 6T. But somehow none of them worked, so I worked on one myself that at least works for me.
.......
Links:
Mauronofrio TWRP: click here
OxygenOS Stable OTA 10.3.1: click here
Very important note: Download the FULL OTA, not the local-upgrade OTA!
Click to expand...
Click to collapse
Some of those steps are unnecessary. Like doing a Factory Reset each time you boot to TWRP as that will mess up your Encryption. And in Method B, you mention to Wipe System. DO NOT UNDER ANY CIRCUMSTANCES WIPE SYSTEM ON THE 6T. IT WILL MESS UP YOUR DEVICE. This is the method I use to flash ROMs.
1. Boot to TWRP
2. Flash the latest version of Stable OOS for your Device and latest TWRP Installer for your Device. -> Reboot to Recovery.
3. Flash the latest version of Stable OOS for your Device and latest TWRP Installer for your Device. -> Reboot to Recovery.
4. Flash ROM + TWRP ,Format Data (Go to Wipe, in the lower right corner Format Data, type in 'YES' and hit Enter) -> Reboot to System
5. After first Boot, You can Reboot to Recovery & Flash Magisk (Optional).
These are for EvolutionX that has Gapps built-in so you don't need to flash Gapps. Otherwise you can Skip the Format Data after ROM flash in Step 4, Reboot to Recovery, Flash Gapps and then Format Data. I use these and they have worked flawlessly for me. Also when switching from one AOSP based ROM to another, it's generally recommended to flash OOS Before.
DarthVader said:
Some of those steps are unnecessary. Like doing a Factory Reset each time you boot to TWRP as that will mess up your Encryption. And in Method B, you mention to Wipe System. DO NOT UNDER ANY CIRCUMSTANCES WIPE SYSTEM ON THE 6T. IT WILL MESS UP YOUR DEVICE. This is the method I use to flash ROMs.
1. Boot to TWRP
2. Flash the latest version of Stable OOS for your Device and latest TWRP Installer for your Device. -> Reboot to Recovery.
3. Flash the latest version of Stable OOS for your Device and latest TWRP Installer for your Device. -> Reboot to Recovery.
4. Flash ROM + TWRP ,Format Data (Go to Wipe, in the lower right corner Format Data, type in 'YES' and hit Enter) -> Reboot to System
5. After first Boot, You can Reboot to Recovery & Flash Magisk (Optional).
These are for EvolutionX that has Gapps built-in so you don't need to flash Gapps. Otherwise you can Skip the Format Data after ROM flash in Step 4, Reboot to Recovery, Flash Gapps and then Format Data. I use these and they have worked flawlessly for me. Also when switching from one AOSP based ROM to another, it's generally recommended to flash OOS Before.
Click to expand...
Click to collapse
these are just the steps which worked for me, but ok
DarthVader said:
Some of those steps are unnecessary. Like doing a Factory Reset each time you boot to TWRP as that will mess up your Encryption. And in Method B, you mention to Wipe System. DO NOT UNDER ANY CIRCUMSTANCES WIPE SYSTEM ON THE 6T. IT WILL MESS UP YOUR DEVICE. This is the method I use to flash ROMs.
1. Boot to TWRP
2. Flash the latest version of Stable OOS for your Device and latest TWRP Installer for your Device. -> Reboot to Recovery.
3. Flash the latest version of Stable OOS for your Device and latest TWRP Installer for your Device. -> Reboot to Recovery.
4. Flash ROM + TWRP ,Format Data (Go to Wipe, in the lower right corner Format Data, type in 'YES' and hit Enter) -> Reboot to System
5. After first Boot, You can Reboot to Recovery & Flash Magisk (Optional).
These are for EvolutionX that has Gapps built-in so you don't need to flash Gapps. Otherwise you can Skip the Format Data after ROM flash in Step 4, Reboot to Recovery, Flash Gapps and then Format Data. I use these and they have worked flawlessly for me. Also when switching from one AOSP based ROM to another, it's generally recommended to flash OOS Before.
Click to expand...
Click to collapse
this helped me greatly! following the instructions above had my files corrupt when id factory reset. i dont have an otg usb. so the instructions above kind of troubled me. again, thank you!
Beefybeardedbear said:
this helped me greatly! following the instructions above from OP had my files corrupt when id factory reset. i dont have an otg usb. so the instructions from OP kind of troubled me. again, thank you!
Click to expand...
Click to collapse
Hello together,
after 3 Days of reading and searching and testing solutions, I have to ask you if you can solve my problem.
I can't find the reason by myself, because I'm new with this topic. I want to install a Custom ROM on my Huawei P 8 Lite Alice from 2015, but everytime I flash any Custom ROM which should match, it ends in a bootloop (huawei logo, then logo custom rom, then huawei logo etc....).
My device:
Huawei P8 Lite ALE L21 from 2015 - Alice
Built number before start this "project": ALE-L21C432B634
Android 6
Emui 4.0.3
Bootloader unlocked with code generated by dc-unlocker
No Root
My prefered Custom ROM is Lineage OS 14.1 and I tried to flash it following the steps in this thread:
[url]https://forum.xda-developers.com/p8lite/development/rom-lineageos-14-1-p8-lite-t3824247[/URL]
1. step - Flash TWRP
First Problem was to install the TWRP 3.1.1 linked in this thread:
[url]https://forum.xda-developers.com/p8lite/orig-development/twrp-t3583180[/url][/URL]
To flash the TWRP image with adb caused no problem. When I boot into recovery, TWRP starts, but when I touch anything on the screen (like swipe to unlock) the System boots (With OS installed it boots the OS and without it stucks at huawei logo). Booting again into TWRP is no Problem.
I solved this problem with a TWRP image 3.1.0-1 from this forum:
[url]https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-huawei-p8-lite.2476/huawei-p8lite-neues-inoffizielles-twrp-3-1-0-1-von-surdu_petru-xda.826139.html[/URL]
The thread references on the same XDA thread mentioned above, but it is linked to another version of TWRP image. This Version 3.1.0-1 is working good.
2. step - flash EMUI 4.1
I flashed the EMUI Update B896 with TWRP. In the thread to the Lineage OS 14.1 mentioned above, it is described that you need this update. I used the linked .zip.
Steps:
1. Wipe Data, internal storage, system, Dalvik Cache, Cache (all except micro sd card).
2. Format Data
3. Reboot into TWRP
4. flash .zip from SD card
5. Wipe Davlik Cache and Cache
5. Reboot System
After that :
Android 6
Build number: ALE B896
EMUI: 4.1
The updated ROM works good.
3. Step - Flash Lineage OS 14.1
Steps:
1. Wipe Data, internal storage, system, Dalvik Cache, Cache (all except micro sd card).
2. Format Data
3. Reboot into TWRP
4. flash .zip from SD card
5. Wipe Davlik Cache and Cache
5. Reboot System
Result Boot Loop :victory:
Trouble shooting:
I tried to install different TWRP versions, but only the TWRP 3.1.0-1 works.
I useb adb sideload to flash the Lineage
I flashed the EMUI 4.03. I had before and than Lineage 14.1 (EMUI works, but Lineage doesn't)
I wiped dalvik cache and data, cache after flashing Lineage, to fix the bootloop
I flashed versions of Lineage OS 14.1 from different dates and different download websites
I flashed different Custom ROMS - all the same Problem except Lineage 13.0. Lineage 13.0 boots till it is ready to "preparing" apps and than boots again.
Now I don't know what do do and would be very thankful to get some new ideas to try or perhaps a solution
Thank you! :highfive:
The ROM needs Emui 4.1 B895/B896 update to be installed first
Then unlock bootloader, flash twrp then flash ROM
Thank you for your help. I'll try this. So I have to lock bootloader again first?
No. You flash the update with twrp
Go to step 6 in the first post on this thread
https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
Keran_3066 said:
No. You flash the update with twrp
Go to step 6 in the first post on this thread
https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
Click to expand...
Click to collapse
Maybe I described it not so good in my first post but I think I did it already exactly like that.
1. Unlock bootloader
2. Flash TWRP
3. Flash Emui 4.1 update B896 ( its working on my phone now)
4. Flash TWRP again
5. Flash Custom Rom ( evertime the result is a bootloop)
Or did I overlook anything?
Sorry I didn't read that part where you flashed emui 4.1
Lineage os 14.1 works for me.
Did you try Resurrection Remix OS
https://forum.xda-developers.com/p8lite/development/rom-t3606568
Keran_3066 said:
Sorry I didn't read that part where you flashed emui 4.1
Lineage os 14.1 works for me.
Did you try Resurrection Remix OS
https://forum.xda-developers.com/p8lite/development/rom-t3606568
Click to expand...
Click to collapse
Thank you very much, that you tried to help me Im happy about all suggestions.
Yes I tried RR and Paranoid, but its the same Problem. I'm wondering that the EMUI Roms which are not officially from Huawei work and any custom rom does not. Maybe there is a Problem with the structure of my system but I dont know anything about this stuff and how to find out the reason for my Problem:laugh:
Maybe you know a command for adb or android terminal app to check if everything is ok?
Jaba Wup said:
Maybe you know a command for adb or android terminal app to check if everything is ok?
Click to expand...
Click to collapse
I'm kinda out of ideas
Keran_3066 said:
I'm kinda out of ideas
Click to expand...
Click to collapse
I feel like you:laugh: thanks and have a nice evening:good:
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.