[Redmi Note 4 MTK (Nikel)] Epic ROM 7.6.10 Released! (By EPIC Team) - Xiaomi Redmi Note 4 [Mediatek] ROMs, Kernels, Reco

[Redmi Note 4 MTK (Nikel)] Epic ROM 7.6.10 Released! (By EPIC Team) - Xiaomi Redmi Note 4 [Mediatek] ROMs, Kernels, Reco

Greetings MIUI-ers!!!
Jamflux, Pocarropa, and MrRaines (MrTomatico here on en.miui), creators of Épic ROM, we are glad to present Épic ROM for Xiaomi Redmi Note 4, who was born thanks to the hard work of these guys. Epic ROM is a Custom ROM based on MIUI, but with some mods and improvements that you can see below on features chapter.
The focus of this ROM is improve MIUI official stock on many devices making many mods and improve Xiaomi sellers to get a bigger MIUI-ers family! This is not MIUI DEVICE TEAM Rom, this is an EPIC TEAM ROM who was born on HTCMANIA (spanish forum) one year ago! .
MIUI DEVICE TEAM is making an amazing work with other issues, and two of them will add to EPIC TEAM to bring to you EPIC. Thanks guys for your hard work!!! And thanks to all Xiaomi members and en.miui Smods/Admins/Mods: Thank you for all your support and help!
Epic ROM also will available on:
Mi MIX [Lithium] -> MrRaines (MrTomatico) NOW AVAILABLE
Mi MAX [Hydrogen] -> Albertkuba (coming soon)
Redmi Note 3 [Hennessy] -> ByAdversary NOW AVAILABLE
Redmi Note 3 Pro [Kenzo] -> Jamflux and Pocarropa NOW AVAILABLE
Redmi 3 [Ido] -> xXxlol456789xXx (Coming soon)
Redmi Note 4 [Nikel] -> coolmihir NOW AVAILABLE
**IMPORTANT ADVISE : Install at your own risk on your device. We are not responsible of any damage on your device. Read carefully instructions before install.
Requirements:
-Xiaomi Redmi Note 4
-Unlocked Bootloader (official unlock to prevent issues)
-Custom Recovery (TWRP ZCX Recovery is highly recommended)
-Make a full Backup before flashing using TWRP Recovery (System, Data, Cache, and EFS).
-Read all thread before proceed
-Love for technology and most important: Love for Xiaomi!
Features 10-Jun-2017
Based on Latest 7.6.10 build (Xiaomi.eu build)
Multilanguage
Gapps Pico pre-installed (Google Play Store and Google Services... you can choose what Google app's are you going to install later )
Épic OTA Service Added on Settings
Epic Mods on OTA app
Music App Improved
Icons on Settings
Root SuperSU updated and adapted to RN4
Init.d support
Busybox pre-installed
Kernel tweaks (very little changes on boot.img)
MIUI Launcher improvements
Camera MODs (better image quality)
Adway integrated on system (you can see also on Settings)
All Chinese app's and Google app's (bloatware) removed
Advanced Reboot Menú (PowerMenu improved)
DolbyAtmos Updated to latest version
Fingeprint Lock (Not Enabled by default)
Supports Xposed but Xposed is not pre-installed (I am not going to pre-install Xposed on this ROM to prevent System Issues, but I bring you the posibility of installing it, thanks to init.d, root, and busybox... use Xposed at your own risk).
Few New Icons Added
Some Nice Wallpapers added
Setings > About Phone > Epic ROM Pic Changed [Screenshot Below]
RAM Improved [On an average 1.9GB or 1.8 GB is available]
More Languages and Spanish Updated (thanks to @JamFlux)
Assistant Touch Updated Like Epic Team Style
Animations on SystemUI (lockscreen). Thanks to Xiaomi EU.
Epic Bootanimation
Updater-Script improved thanks to @pocarropa
Increased Battery Performance
Better Battery and Performance/RAM management thanks to few more code lines from Epic Team & Xiaomi Eu
I have removed the SIM Signal Icon to the left and Center Clock Mod by Default. I will add it to the Epic OTA app Soon.
If you want them Download and flash it via the Recovery from here.
Flash it only on Epic ROM.
Languages Supported:
All European Languages from Xiaomi.eu (Thanks Guys)
How to install
Download ZIP from below.
Reboot to recovery (Press Power + Volume up)
Make a full backup of your current ROM and copy it to your computer to prevent issues.
Wipe: Dalvik, Cache, Data, System.
Install ZIP Rom.
**IMPORTANT ADVISE: Sometines TWRP have issues installing .zip and you might get Error 7. If this happens, please reinstall the ROM. In the second try, TWRP will install without problem. If you still having the issue, download the ROM again (sometimes servers download a corrupt .zip file...).
**IMPORTANT ADVISE 2: On first boot, you will get one bootloop, THAT'S NORMAL, this is caused by ROOT installation. Please, do not interrupt process and look how your device turns ON in 10-15 minutes. Next time you reboot or Power on your device, it will turn ON like always .
Reboot system and wait 10 minutes until your device loads the system (only first time)
Configure your Google Account and Mi Cloud like always
Enjoy.
Download Center
7.6.10 Epic Build out!
Download: EpicROM_7.6.10_Multilanguage_RedmiNote4_coolmihir.zip
Current Status: Tested and should be stable, install at your own risk!
If already using Epic ROM
Go to Settings > OTA & Mods. OTA is now available.
Download and flash it via the recovery. After flashing, just wipe the dalvik cache. The update will not format your phone and you will not,lose any app data. Don't worry
Those who are having bootlooping issue can reciprocate the following steps:-
Flash any Xiaomi Official Fastboot ROM (Stable or Dev) via MiFlash tool. Choose Clean_all. Now flash TWRP and wipe everything. Flas the above ROM and Reboot. If it then also bootloopes then flash this after flashing the ROM.
PLEASE, SUPPORT THIS PROJECT DONATING TO SOME NGO WHO ARE HELPING NOW SOME COUNTRIES ON AFRICA TO GET WATER OR FOOD AND MEDICINES... WE DON'T WANT ANY MONEY FOR THIS, BUT YOU CAN HELP A LOT OF PEOPLE WITH A LITTLE DONATION...
Thanks to:
Xiaomi (and Xiaomi official developers for bring to us this amazing OS)
Google
Xiaomi Eu Team
MultiROM Team
Epic Team Members @JamFlux, @pocarropa, ByAdvesary, Albertkuba, @xxxlol456789xXx, @coolmihir, @mrtomatico (MrRaines))
All MIUI DEVICE TEAM
All Admins/Mods/SMods from En.MIUI
HTCMan

ROM OS Version: 2.3.x Gingerbread
Click to expand...
Click to collapse
Something's wrong here

Thanks and help me
Hi coolmihir thanks for your work for this rom. I just try it. But I have little problem that I can't add or remove my fingerprint. Also I can't change my password for lock screen. It always back to Settings. Could you help me?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Can you build an rom with magisk v13? Its working good...

yasars said:
Can you build an rom with magisk v13? Its working good...
Click to expand...
Click to collapse
Will do the next build!!

JohnMelson said:
Something's wrong here
Click to expand...
Click to collapse
Corrected

fazrinashari said:
Hi coolmihir thanks for your work for this rom. I just try it. But I have little problem that I can't add or remove my fingerprint. Also I can't change my password for lock screen. It always back to Settings. Could you help me?
Click to expand...
Click to collapse
Works fine for me!! Click on view summary when it fc and upload the ss here.

fazrinashari said:
Hi coolmihir thanks for your work for this rom. I just try it. But I have little problem that I can't add or remove my fingerprint. Also I can't change my password for lock screen. It always back to Settings. Could you help me?
Click to expand...
Click to collapse
Same for me please fix it, it is a very good rom

xtreme97 said:
Same for me please fix it, it is a very good rom
Click to expand...
Click to collapse
Works fine on my phone.

Hello. I got some problem here. When I installed the ROM there was no notification that show the installation complete and succesfully. It just suddenly going back to the TWRP homepage. Then I try to wipe the dalvik cache from "WIPE" tab, the I reboot the system. But it was stuck in th booting (the white line loading). I have waiting for 2 hours but it still stucked. Can u help me with this? Thank you

yahyagta said:
Hello. I got some problem here. When I installed the ROM there was no notification that show the installation complete and succesfully. It just suddenly going back to the TWRP homepage. Then I try to wipe the dalvik cache from "WIPE" tab, the I reboot the system. But it was stuck in th booting (the white line loading). I have waiting for 2 hours but it still stucked. Can u help me with this? Thank you
Click to expand...
Click to collapse
same case with me

Works great, but unable to change lockscreen password or add fingerprint without it crashing.

yahyagta said:
Hello. I got some problem here. When I installed the ROM there was no notification that show the installation complete and succesfully. It just suddenly going back to the TWRP homepage. Then I try to wipe the dalvik cache from "WIPE" tab, the I reboot the system. But it was stuck in th booting (the white line loading). I have waiting for 2 hours but it still stucked. Can u help me with this? Thank you
Click to expand...
Click to collapse
Flash the Official ROM via Mi Flash tool clean all and them ash twrp again. Wipe everything and install the ROM again.

Are the battery issues faced by multi rom users fixed in this rom?
---------- Post added at 08:40 AM ---------- Previous post was at 08:09 AM ----------
Are the battery issues faced by multi rom users fixed in this rom?

coolmihir said:
Works fine for me!! Click on view summary when it fc and upload the ss here.
Click to expand...
Click to collapse
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.ConfirmLockPassword$InternalActivity}: android.view.InflateException: Binary XML file line #11: Binary XML file line #11: Error inflating class com.android.internal.widget.PasswordEntryKeyboardView
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java)
at android.app.ActivityThread.access$1000(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
at android.os.Handler.dispatchMessage(Handler.java)
at android.os.Looper.loop(Looper.java)
at android.app.ActivityThread.main(ActivityThread.java)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
Caused by: android.view.InflateException: Binary XML file line #11: Binary XML file line #11: Error inflating class com.android.internal.widget.PasswordEntryKeyboardView
at android.view.LayoutInflater.inflate(LayoutInflater.java)
at android.view.LayoutInflater.inflate(LayoutInflater.java)
at android.view.LayoutInflater.inflate(LayoutInflater.java)
at com.android.settings.ConfirmLockPassword$ConfirmLockPasswordFragment.b(ConfirmLockPassword.java)
at com.android.settings.BaseConfirmLockFragment.onCreateView(BaseConfirmLockFragment.java)
at android.app.Fragment.performCreateView(Fragment.java)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java)
at android.app.FragmentManagerImpl.dispatchActivityCreated(FragmentManager.java)
at android.app.FragmentController.dispatchActivityCreated(FragmentController.java)
at android.app.Activity.performCreateCommon(Activity.java)
at android.app.Activity.performCreate(Activity.java)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java)
... 10 more
Caused by: android.view.InflateException: Binary XML file line #11: Error inflating class com.android.internal.widget.PasswordEntryKeyboardView
at android.view.LayoutInflater.createView(LayoutInflater.java)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java)
at android.view.LayoutInflater.rInflate(LayoutInflater.java)
at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java)
at android.view.LayoutInflater.rInflate(LayoutInflater.java)
at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java)
... 24 more
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Constructor.newInstance(Native Method)
... 31 more
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.graphics.drawable.Drawable.getPadding(android.graphics.Rect)' on a null object reference
at android.inputmethodservice.KeyboardView.<init>(KeyboardView.java)
at com.android.internal.widget.PasswordEntryKeyboardView.<init>(PasswordEntryKeyboardView.java)
at com.android.internal.widget.PasswordEntryKeyboardView.<init>(PasswordEntryKeyboardView.java)
at com.android.internal.widget.PasswordEntryKeyboardView.<init>(PasswordEntryKeyboardView.java)
... 32 more
Here is the lock for FC

No matter what I do, the ROM just doesn't want to boot, it stays stuck at the first Mi Logo no matter how much I wait, tried flashing it multiple times, re-downloaded the ROM file, updated TWRP, nothing works.

Can i flash this to my redmi note 4x 4/64?

Silvers91 said:
No matter what I do, the ROM just doesn't want to boot, it stays stuck at the first Mi Logo no matter how much I wait, tried flashing it multiple times, re-downloaded the ROM file, updated TWRP, nothing works.
Click to expand...
Click to collapse
i got this also, did you figure it out?

retarded1 said:
i got this also, did you figure it out?
Click to expand...
Click to collapse
Me too, but I fix it by install miuipro first
Once start, reboot and install this ROM, works fine
Anyway, is this ROM Magisk support? I try to install but it seems SuperSU break it. And also, I can't uninstall SuperSU from the app setting

retarded1 said:
i got this also, did you figure it out?
Click to expand...
Click to collapse
The dev answered me on Mi forum and this is what he said:
"Flash the fastboot ROM using MiFlash tool choose clean_all and flash the ROM again via TWRP."
Can't try it now though, try and see if it works. At your own risk of course.

Related

[EXPERIMENTAL][TESTING][29-3-17] MultiRom Latest For mido

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For midoSupports all Roms (SHOULD)
NOTE:
Code:
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 Kernel
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.
What is MultiRom?
MultiRom is one-of-a-kind multi-boot mod. It can boot any Android Rom as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiRom can boot from USB drive connected to the device via OTG cable. The main part of MultiRom is a boot manager, which appears every time your device starts and lets you choose ROM to boot. Roms are installed and managed via the modified TWRP recovery. You can use standard ZIP files to install secondary Android Roms, daily prebuilt image files to install Ubuntu Touch and MultiRom even has its own installer system, which can be used to ship other Linux-based systems.
I am not the developer of MultiRom. All Credits for it goes to Tasssadar, the actual developer of it.
Features:
MultiBoot any number of Android Roms
Restore Nandroid Backup as secondary ROM
Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
Boot from USB drive Attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash Stock Rom zips again. Make backups. Always.
TESTED ON ROMS:
Test and Report
SUPPORTED DEVICES:
mido
Please Test it in other Similar SD Variants and Report it Below.
Bugs:
You tell me
SCREENSHOTS:
All Screenshots HERE
INSTALLATION INSTRUCTIONS:
Via The MultiRom Manager App:This is the easiest way to install everything MultiRom needs... Just follow the Below Instructions:
Install the app (Links Below)
Select MultiRom and Recovery on the Install/Update card.
Press "Install" on the Install/Update card to start the installation.
DONE! MULTIROM IS READY TO ROCK!
You current rom will not be erased by the installation.
Download link is in the second post.
Adding ROMs:
Android
Boot into MultiRom Recovery -> select MultiRom -> Add Rom -> Select the Rom's zip file and click Confirm.
Updating/changing ROMs:
1. Primary Rom (Internal)
Flash Rom's zip File as Usual, Do factory reset if needed (it won't erase secondary Roms)
Go to MultiRom in recovery and do Inject curr. boot sector.
2. Secondary Android Roms
If you want to change the Rom, delete it and add new one. To update the Rom, follow these steps:
Go to MultiRom -> List Roms and select the Rom you want to update.
Select "Flash zip" and Flash the Rom's zip File.
Explanation of recovery menus:
Main menu
- Add Rom - Add Rom to Boot
- List Roms - List Installed Roms and Manage Them
- Inject boot.img File - When you Download something, for example a Kernel, which is Distributed as a Whole boot.img (eg. Qassam Kernel), you have to use this option on it, otherwise you would lose MultiRom.
- Inject curr. boot sector - Use this option if MultiRom does not show up on boot, for example after Kernel Installation.
- Settings - Well, SETTINGS!
Manage Rom
- Rename, Delete - No Need to Explain this I Think!
- Flash Zip (Only Android Roms) - Flash zip to the Rom, for example GAPPS
- Add/Replace boot.img - Replaces boot.img used by this Rom, this is more like a Developer Option.
- Re-Patch init - This is available only for Ubuntu. Use it when Ubuntu cannot find the root partition, i.e. after apt-get upgrade which changed the init script.
GitHub Source Codes:
MultiRom Organization for Xiaomi Devicesmido MultiRom Device TreesMultiRom Manager App Source Codes
Current Status:
Test and Report...
CREDITS:
Rishabh Rao (ME) - For Porting MultiRom to kenzo/kate
Tasssadar - For his awesome MultiRom
nkk71 - For his No-KEXEC workaround
Version Information:
Status: Unofficial, IN TESTING, Version 33
ENJOY!:good:
XDA:DevDB Information
MultiRom For mido, Tool/Utility for the Xiaomi Redmi Note 4
Contributors
Rishabh Rao
Source Code: https://github.com/multirom-xiaomi
Version Information
Status: Testing
Current Beta Version: v33
Beta Release Date: 2017-03-29
Created 2017-03-29
Last Updated 2017-03-30

Download Links:
MultiRom Manager App 2.4-rishabhrao

1. Can I flash any Other Kernel?
- YES! You CAN flash ANY Kernel!!!
2. Can I Flash Roms to USB-OTG? How?
- Yes, You CAN Flash Roms to USB-OTG.
Follow these steps to do so:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on Add Rom.
4. Select the correct Location and Flash it...
Note: Flashing on a USB-OTG takes some Time, so be patient & Don't Worry!
3.Where to Find Roms Installed in my USB-OTG Drive? How to Boot into Them?
- After Flashing the Rom you will be Booted into the MultiRom Boot Menu.
All your Roms Flashed on the Internal Memory will be in Internal Tab.
All Others will be in the External Tab.
4. How to Rename/Remove/Delete/Wipe Dalvik Cache or Flash any Other zips to an Existing Rom?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the Rom which you want to Remove/Add zips.
You will find all the options you need there!
5. "Unable to Flash, I am getting Errors" / "Executing Updater Script Failed" / "Rom is not Booting". ANY HELP???
- Please Provide Logs. It will be located in /sdcard/multirom/error.txt OR if that's not present here: /proc/last_kmsg
It would be Great if you can Provide Some Screenshots.
Press Volume Down + Power Buttons Together to take Screenshots.
6. How to Disable Auto Boot / Change Rom Name / Hide Roms / Change Brightness of MultiRom Boot Menu?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the 3 Dots on the Top Right of the Screen.
4. Select Settings.
You will find all the Customizations of the MultiRom Boot Menu you need there!
7. What is the No-Kexec Workaround?
- The No-Kexec Workaround by @nkk71 allows you to use MultiROM without having to flash a Kexec Enabled Kernel.
Please read More about No-Kexec Workaround from the author words only (to avoid duplicity and to get the latest information), thanks to @nkk71 once again!
http://forum.xda-developers.com/showpost.php?p=68738134&postcount=4

Guys please test this in your mido and Please tell me how it works

How about the recovery? witch one we can use?

Question 1: what is to difference between multirom and dual boot?
Question 2: can I use miui as secondary ROM with aospe as first Rom?
Question 3: when will dual boot be available for rn4?

XMoDuLeSx said:
How about the recovery? witch one we can use?
Click to expand...
Click to collapse
It has it's own modified TWRP recovery
Sent from my LeEco Le 2 using XDA Labs

dragneelfps said:
Question 1: what is to difference between multirom and dual boot?
Question 2: can I use miui as secondary ROM with aospe as first Rom?
Question 3: when will dual boot be available for rn4?
Click to expand...
Click to collapse
1. MultiRom is a complete Multi Booting tool which has it's own Recovery, boot ui, etc.
2. Yeah i think so... You can.
3. Mido is rn4 only r8!
Also note that this is still in testing so please forgive me if you face any bugs. But it will be stable soon...
Sent from my LeEco Le 2 using XDA Labs

flashed miui 7.2.23 as second rom ..(aospe as first rom).
I open the app and try to boot into miui..it says No-Kexec kernel found and reboots to recovery.
---------- Post added at 01:50 PM ---------- Previous post was at 01:18 PM ----------
Now tried LOS as second rom. Couldnt even boot in my first rom. So deleted the second rom. Still couldnt boot in the first rom. (screen goes off after mi boot logo). Now restored the first rom nandroid backup. Working now.(first rom only).

dragneelfps said:
flashed miui 7.2.23 as second rom ..(aospe as first rom).
I open the app and try to boot into miui..it says No-Kexec kernel found and reboots to recovery.
---------- Post added at 01:50 PM ---------- Previous post was at 01:18 PM ----------
Now tried LOS as second rom. Couldnt even boot in my first rom. So deleted the second rom. Still couldnt boot in the first rom. (screen goes off after mi boot logo). Now restored the first rom nandroid backup. Working now.(first rom only).
Click to expand...
Click to collapse
I did the same thing and I'm having the same problem...
Only that I tried xenon HD instead of aospe

leo_pard2331 said:
I did the same thing and I'm having the same problem...
Only that I tried xenon HD instead of aospe
Click to expand...
Click to collapse
Let's see . op will fix the bug probably.

dragneelfps said:
Let's see . op will fix the bug probably.
Click to expand...
Click to collapse
I wiped everything and restored the backup and now I'm unable to install the multi rom

dragneelfps said:
flashed miui 7.2.23 as second rom ..(aospe as first rom).
I open the app and try to boot into miui..it says No-Kexec kernel found and reboots to recovery.
---------- Post added at 01:50 PM ---------- Previous post was at 01:18 PM ----------
Now tried LOS as second rom. Couldnt even boot in my first rom. So deleted the second rom. Still couldnt boot in the first rom. (screen goes off after mi boot logo). Now restored the first rom nandroid backup. Working now.(first rom only).
Click to expand...
Click to collapse
Hey u mentioned the screen goes off after mi boot logo
How much time did you wait after that happens?
Sent from my LeEco Le 2 using XDA Labs

leo_pard2331 said:
I wiped everything and restored the backup and now I'm unable to install the multi rom
Click to expand...
Click to collapse
What is happening when you try to install it?
Sent from my LeEco Le 2 using XDA Labs

dragneelfps said:
Let's see . op will fix the bug probably.
Click to expand...
Click to collapse
Definitely i will
Sent from my LeEco Le 2 using XDA Labs

Rishabh Rao said:
Hey u mentioned the screen goes off after mi boot logo
How much time did you wait after that happens?
Sent from my LeEco Le 2 using XDA Labs
Click to expand...
Click to collapse
actually 10-20 sec

Hey sir, Did u test this before posting in here? Do u own a mido? Just curious lol

Sarthak Narang said:
Hey sir, Did u test this before posting in here? Do u own a mido? Just curious lol
Click to expand...
Click to collapse
+1

Sarthak Narang said:
Hey sir, Did u test this before posting in here? Do u own a mido? Just curious lol
Click to expand...
Click to collapse
Hello Sarthak Sir
No i do not own a mido.
I approached in some TG, WhatsApp groups after i made this to get someone to test. But everyone got me to post it here
So i just posted it with the BIG Heading "TESTING".
Also just because I don't have this device, please don't think i will not fix this MultiRom.
I will work day and night to fix this lol:silly::fingers-crossed:
Now some guys at some TG group confirmed to me the following points:
1. MultiRom works through the app to dual boot.
2. Boot UI is messed up and needs fix. (Trying out different Pixel Formats now)
3. The Lockscreen and FP Bug exists just like some other devices like kenzo, s2, x2, etc. (Temporary fix: Disable your FP and Pattern before Installing any new Rom)
Now looking out for more testing and propably this thing will be ready to rock in a few days.
Sent from my LeEco Le 2 using XDA Labs
Edit: Just also added EXPERIMENTAL in the Title to show that this is just in the Alpha Stage till now

Rishabh Rao said:
Hello Sarthak Sir
No i do not own a mido.
I approached in some TG, WhatsApp groups after i made this to get someone to test. But everyone got me to post it here
So i just posted it with the BIG Heading "TESTING".
Also just because I don't have this device, please don't think i will not fix this MultiRom.
I will work day and night to fix this lol:silly::fingers-crossed:
Now some guys at some TG group confirmed to me the following points:
1. MultiRom works through the app to dual boot.
2. Boot UI is messed up and needs fix. (Trying out different Pixel Formats now)
3. The Lockscreen and FP Bug exists just like some other devices like kenzo, s2, x2, etc. (Temporary fix: Disable your FP and Pattern before Installing any new Rom)
Now looking out for more testing and propably this thing will be ready to rock in a few days.
Sent from my LeEco Le 2 using XDA Labs
Edit: Just also added EXPERIMENTAL in the Title to show that this is just in the Alpha Stage till now
Click to expand...
Click to collapse
Looking forward to it.

[ROM][SiriuZ V3.0][GT] EMUI 8.0 P20 Lite by Catuva21

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
V 3.0 - EMUI 8.0DONOT COPY MY WORK, Ask for Permissions
Code:
- I am not responsible for the damage of your cell phone if you do not correctly perform the steps
- loser warranty
- if you are not sure better not to touch and leave this page
COMPATIBLE WITH
with all versions, P20 lite, remember to know your original compilation if at any time you want to return to stock for example ANE-LX3C25 with this data you can return to stock.
This version is based on the official modification of EMUI, activating functions that are in the high-end versions, adding some modifications for their better performance.
REQUIREMENTS:
- EMUI 8.0.0
- Activate the OEM unlocking, which is in adjustment / developer options and leave it so forever to avoid conflict.
- unlock the bootloader.
- install the recovery that I will leave, automated from windows-linux
Guard the rom in an external memory.
Turn off the cell phone press the plus and power buttons until you have the TWRP window
Press WIPE
Press FORMAT DATA
Write the word "yes" without quotes and accept, just do the work
Press BACK to go back several times to the main window.
Press WIPE, then ADVANCE WIPE
Verify that the partition DATA this in the f2fs extension
Mark: Dalvik, cache, data, internal storage, system
IMPORTANT !: do not mark "micro sdcard".
Once you have marked, slide the "swipe to wipe" arrow to clear it.
Go back to the main sale, press INSTALL
Press SELECT STORAGE
Switch to Micro SDCard to find the rom.
Look for the MORFUZ rom and flash
At the end of the installation press "wipe davilk-cache", wait for it to finish.
Reboot system.
Congratulations now will start the rom MORFUZ
It seems that Huawei modified the modem partition in the September-October patch and the MORFUZ kernel does not work incoming and outgoing calls.
-IMPORTANTonly install this module from the root Magisk options if incoming and outgoing calls do not work.
https://mega.nz/#!F7oXzSRZ!8uuSCIx4UTbuWkTEYoFmTXTCwvIr6Reuc1vyq6OIhw0
Rom Siriuz
https://mega.nz/#!tYBjTQhC!yPbPXkazpQUy7bzLdm33rEapihBB8iVmSGlGxy1RweI
TWRP Mod by catuva21 - VERSION 2
unzip, the file is automatic
https://mega.nz/#!uD4FlCqL!ERBzP4ZWa2sR8f_wnn15F_cOFCdYVKgfYETjiehQkkQ
TELEGRAM GROUP
https://t.me/joinchat/ERAhfQ8kyF6_iH5nMun5dg
Contributors:
CATUVA21
Credits:
- Openkirin Recovery TWRP
- Alexxx1
- Chisetdel31260
ROM OS Version: ANE-L
ROM Kernel: Stock
ROM Firmware Required: EMUI 8.0.0
Version Information:
Status: Stable
Created on: 2018-06-30
Last Updated on: 2018-09-10

DESCRIPTION ROM SIRIUZDETAILS OF THE ROM
SIRIUZ 3.0
- Base firmware P20 lite (security patch for September).
- Custom kernel MorfuZ now works wifi and bluetooth.
- Huawei ID integrated and running.
- New bootanimation.
- New bootlogo.
- Percentage activated from start, for other models.
- Activated the font change in themes.
- New topics.
- 7 themes to change the font customization.
- Yorreciones de camara.
- Youtube advance updated.
- Adaway ad blocker.
- VolTe Activated.
- Magisk 17.1
SIRIUZ 2.6
- P20 lite base firmware (August security patch).
- MorfuzKernel 2.1 selinux Permissive.
- Turbo GPU.
- Added support init.d.
- Added busybox.
- Huawei ID back.
- Boot profile for the Darknnes-Blu_Active kernel within init.d improves performance.
- Change of the MTweaks auditor kernel application.
- Added Lent AR fun camera function.
- Magisk 16.7.
- Increase bitrate of photos and video, improve quality.
- Application of return mail.
- Youtube Mod Updated.
- New Gboard keyboard.
SIRIUZ 2.4
-Base firmware P20 lite(security patch jun).
-Activated Dual Speaker.
-Added DolbyAtmos in Music.
-New Boot logo.
-Added custom watermark for the P20 lite.
-Now without patches.
-Installation mode AROMA-INSTALLER.
-Music: stock or crack.
-Camera: stock, Mate10Pro or P20Pro.
-Root: Magisk or Supersu.
-Navbar, Use the fingerprint sensor as a navigation bar.
-Solid explorer, Kernel Auditor, Quick Reboot.
-MxPlayer.
-Sony Music.
-Eliminated the data space.
-Deodexed (improves optimization).
-Improvements in the quality of photos, video and sound..
-It eliminated unnecessary google applications.
-Added Call Recorder.
-Added Youtube Mod (function in the background).
-Activated multi-user X5.
-Keyboard change, google.
-Reduction of size of icons.
-Activated glove mode.
-Mtu 1500.
-Explored files improved.
-Added main screen design 5x5,5x6,6x5.
-Added more applications of social networks of Twin cloning.
. * facebook, faceboot lite
. * messenger, messenger lite
. * whatsapp, whatsapp mod
. * instagram
. * snapchat
. * telegram
. * twitter
. * mega
. * creativefrends
. * microsoft office

r2

when i go to security options settings app crashes
cant setup fingerprint id
oh now it works after playing with the instalation settings

I got an error during installation and start bootlooping, latter with more time I'll try again.
Thanks to share your work with us.

Error finishing the installation:
set_perm: some changes failed
Other problems:
-Does not detect micro sd
-You can not configure a screen lock method (settings close when you try to enter that section)
-Developer options can not be activated (the settings are closed when you press compile)
Those problems are what happened to me, I followed the installation instructions exactly as it says in the post

same problem with me

brandox0 said:
Error finishing the installation:
set_perm: some changes failed
Other problems:
-Does not detect micro sd
-You can not configure a screen lock method (settings close when you try to enter that section)
-Developer options can not be activated (the settings are closed when you press compile)
Those problems are what happened to me, I followed the installation instructions exactly as it says in the post
Click to expand...
Click to collapse
The rom is working or not?

thanks for the rom!
followed the install instructions except i didn't install the TWRP321_OREO_P20LITE.rar because i previously installed it following these instructions.
chose to install the custom kernel and SuperSU. not sure right now what else. i will write it down when i try the next build.
i encountered the following issues:
-error finishing the installation: set_perm: some changes failed during flashing (could this be because i didn't install your modded TWRP?)
-unable to set the lockscreen options
-unable to set up fingerprintid
-settings crashes when attempting to enable dev options
-sd card isn't detected within the fw
once i saw the sdcard isn't detected, i tried to recover from my latest backup but TWRP wasn't able because /system was only mounted as read-only (could this be as well because i didn't install your modded TWRP?).
ended up having to reflash stock from erecovery, rerooting and reinstalling TWRP in order to restore from my last backup (maybe i did something wrong?).
after reading the features list, i personally would use it as my main rom. i'd love to see it with viper4android included and with an all dark theme though but that's just me.
thanks for your work! looking forward to more!

luigi997 said:
The rom is working or not?
Click to expand...
Click to collapse
Well, if you eliminate the fact that the fingerprint reader or any other screen lock method does not work, you can not use the micro sd and the developer options are not available. So yes, the rom works.
You can try to urge it, maybe you're lucky and do not have mistakes.

brandox0 said:
Well, if you eliminate the fact that the fingerprint reader or any other screen lock method does not work, you can not use the micro sd and the developer options are not available. So yes, the rom works.
You can try to urge it, maybe you're lucky and do not have mistakes.
Click to expand...
Click to collapse
If i try to uninstall an app, the system reboot.
I've installed the modded kernel

Anyone with no issues? Can be used as a daily driver?
Please report back testers ^_^

[email protected] said:
Anyone with no issues? Can be used as a daily driver?
Please report back testers ^_^
Click to expand...
Click to collapse
Nope, so far I haven't seen anyone reporting positively. No fingerprintid and no security features makes the rom pretty much unusable as far as I've tested and seen on the thread. I'm awaiting to see how this develops..

Success
This rom is working prefectly.. i have keep on trying to re install the rom.I always follow the exact instruction, and i have found out. You will have a set_perm: some changes failed. IF you mark check the navbar, and status bar while in aroma installer.. I have able to use everything. Ill try to make a screenshot of it.

riorabel12 said:
This rom is working prefectly.. i have keep on trying to re install the rom.I always follow the exact instruction, and i have found out. You will have a set_perm: some changes failed. IF you mark check the navbar, and status bar while in aroma installer.. I have able to use everything. Ill try to make a screenshot of it.
Click to expand...
Click to collapse
Awesome! I'll try again!
Did you flash the recovery included in the post?
What do you mean with "If you mark check the navbar, and status bar while in aroma installer"?
Thanks for the feedback!

madalone said:
Awesome! I'll try again!
Did you flash the recovery included in the post?
What do you mean with "If you mark check the navbar, and status bar while in aroma installer"?
Thanks for the feedback!
Click to expand...
Click to collapse
YES. I HAVE FLASH THE RECOVERY. AND WHEN YOU FIRST DO THAT... AND YOU SHOULD PUT THE ROM INTO YOUR SD CARD..
YES, IF YOU MARK CHECK THE NAVBAR ANF STATSBAR. WHILE CHOOSING YOUR DESIRED APPS. YOU WILL SEE THAT IN THE VERY LAST PAGE OF THE AROMA INSTALLER. WHERE YOU HAVE THE OPTIONS. NAVBAR STATSBAR, SOLID EXPLORER, KERNEL AUDIATOR, AND the QUICK REBOOT. SO JUST MARK CHECK THE SOLID EXPLORER,KERNELAUDITOR,AND QUICK REBOOT..
SO TRY IT NOW. AND GIVE ME SOME FEEDBACK IF IT WORKS IN YOU. ALSO KINDLY TRY TO DO A SCREENSHOT. I DONT HAVE OTHER PHONE TO TAKE A SHOT ON IT. KUDOS THANKS

ok so i flashed the provided recovery and the rom following the instructions with the following options in aroma installer:
Kernel: Morfu2kernel
Root: SuperSU
Camera: P20 Pro
Music: Stock
Kernel Auditor
Quick Reboot
the installation went through except bootimage patcher failed at decompressing ramdisk (failure, aborting).
edit1: after a cache wipe, i rebooted the phone. the phone boots but no root.
tried to flash SuperSU through TWRP but failed.
wiped data/cache/dalvik/system & reflashed rom with Stock kernel & Magisk no bootimage patcher errors. after a cache wipe, rebooted & phone has root :victory:
brandox0 said:
I also want to try again, but I'm still not sure.
So far, how is the rom working? Is there a fault signal mentioned above?
Click to expand...
Click to collapse
so far i'm still getting all my apps installed. i'll letcha know how i get on with it.
edit2: as i am stubborn, i reflashed the rom with the custom kernel and Magisk. root is on and the phone seems to run smoothly.

madalone said:
ok so i flashed the provided recovery and the rom following the instructions with the following options in aroma installer:
Kernel: Morfu2kernel
Root: SuperSU
Camera: P20 Pro
Music: Stock
Kernel Auditor
Quick Reboot
the installation went through except bootimage patcher failed at decompressing ramdisk (failure, aborting). is that the kernel failing to install?
after a cache wipe, i rebooted the phone. the phone boots as expected.
Click to expand...
Click to collapse
I also want to try again, but I'm still not sure.
So far, how is the rom working? Is there a fault signal mentioned above?

madalone said:
ok so i flashed the provided recovery and the rom following the instructions with the following options in aroma installer:
Kernel: Morfu2kernel
Root: SuperSU
Camera: P20 Pro
Music: Stock
Kernel Auditor
Quick Reboot
the installation went through except bootimage patcher failed at decompressing ramdisk (failure, aborting).
edit1: after a cache wipe, i rebooted the phone. the phone boots but no root.
tried to flash SuperSU through TWRP but failed.
wiped data/cache/dalvik/system & reflashed rom with Stock kernel & Magisk no bootimage patcher errors. after a cache wipe, rebooted & phone has root :victory:
so far i'm still getting all my apps installed. i'll letcha know how i get on with it.
Click to expand...
Click to collapse
I worked perfectly, the only problem is that mobile became very slow.

rapza4 said:
I worked perfectly, the only problem is that mobile became very slow.
Click to expand...
Click to collapse
i had that plus overheating but after what i did in edit2 it was gone and the phone runs smoothly.
on another note: is it possible to make this rom have init.d support somehow? it'd be cool for stuff like Liveboot..

[ROM] LITE OS 6.0 v2 for realme 2 pro [STABLE][CUSTOM STOCK ROM]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
★LITE OS 6.0 V2
(Based on stock os)
Stable and can be used as daily driver
Watch video for review and install-
https://youtu.be/q3L25WblKLM
Rom features-
✪Prerooted
✪Odexed this time
✪Debloated
✪Busy Box
✪Qn Engine
✪Some of The Major Init.d tweaks......
✪Zero FC.(If You Follow my guidelines)
✪Nano
✪High Touch Sensitivity (Driver Moded)
✪Swap enabled (upon request)
✪Ram Optimization
✪Loop Smoothness Tweak
✪SD card Read Write Speed Optimization
✪Sqlite Optimization
✪Net Speed & DNS Tweaks
✪Darky Zip-align
✪Build Prop Tweaks
✪Battery Saving script
✪Decrypted
✪Liquid UI
✪Kernal optimization
✪Gpu driver refined
✪Unecessary resources removed inside app and system for better optimization
✪And more if u explore ~_~
Donators -
Dr_lokman_sir
Anurag singh
Syam velchuri
Donate to apperciate and support :
7804011237 (Google pay/tez)
7804011237 (Paytm)
7804011237 (Phonepe)
[email protected] (UPI ID)
PAYPAL : www.paypal.me/mks7s
Source used for build -Stock kernel and stock rom
Downloads -
(Make complete backup first , and scroll down more and read F.A.Q too for your general questions )
✪LITE V2 ROM LINK
✪LITE APPS LINK
Instructions -
1.Download ROM
2.Place rom in internal memory
3.Wipe everything except internal and memory card
4.Flash and reboot
5.Install missing package from r2x2 recovery
6.done. if you can't understand my instructions then watch video tutorial
Missing packages (install only if you need !) -
(Scroll down and read F.A.Q for installation)
✪Assitive touch - LINK
✪Clone apps - LINK
✪Gesture U.I - LINK
✪Night shield - LINK
✪Oppo gallery - LINK
✪Long screenshot & other - LINK
✪U.I Sound - LINK
✪Oppo backup & restore - LINK
✪Call recording - LINK
Reproduction,remodification and use of any components of this rom in other rom/mod is not allowed

F.A.Q -
1.Is there any bug?
Ans - no ,if you found one please let me know
2.How to install missing packages ? proper way
Ans - install along with rom when you freshly install rom and
1.mount system first from recovery
2.then install missing packages and reboot system .
3.Having problems to get root rights for titanium backup and other ?
Ans - flash LINK zip again ! And uninstall magisk app and install app manually by extracting LITE APPS zip
4.quick pic and magisk not opening ?
Ans - extract LITE APPS zip and install it manually
5.Im having transparent lockscreen problem ?
Ans - just set any wallpaper it will get fixed or use color os theme store to fix it by changing theme
6.Im missing some apps from lite os , is there any way to get them ?
Ans - yes comment down below , i'll upload for u okay (will take time)
7.My phone is encrypted , should i flash this rom ?
Ans - decrypt from here {Mod edit} although rom is decrypted already if u try to install this on your encrypted phone then you'll need to format data
8.Are other zip required to wipe anything ?
Ans - No just flash by recovery and reboot okay
9.Im on color os 5 and gsi , can i flash this directly ?
Ans - No , first upgrade from this link - {Mod edit} U must be on color os 6 already inorder to flash this ROM
10.how do i fix this red root notification bar ?
Ans - follow this to remove root notification bar {Mod edit} and if u don't like xposed then use system ui tuner from playstore
11.Im facing strange problems ? which happens to no one !
Ans - you'll be ignored because you are'nt following what i said above and in video too !

Honest user review -
Q.1 How's performance ?
Ans -
Q.2 How's ram management ?
Ans -

Just finished downloading... Have been waiting for this

BUG (?): If you have a lockscreen enabled, and then if you backup this ROM and the Data partition using R2X2 Recovery and then restore it, the phone will refuse to accept your passcode and deny access. Even if you reset the passcode, you'll never be able to unlock the lockscreen. Remove your lockscreen passcode before backup, otherwise you'll be permanently locked out of your own data.
---------- Post added at 04:01 PM ---------- Previous post was at 03:54 PM ----------
Also, after 3 clean installations, I can confirm that the root warning notification fix does not work on this ROM by the given method. Could not flash the Riru zip.
Update: The notification fix works. I had to flash Magisk 17.1 seperately. But somehow, R2X2 Recovery kept losing grasp of /system, so the flash kept failing. I had to unmount and remount /system manually before flashing Magisk. If you face the same problem, try this.

CerinCorbierre said:
BUG a.... IMPORTANT NOTE for users: ........n. ...., o.....
---------- Post added at 04:01 PM ---------- Previous post was at 03:54 PM ----------
.....
Click to expand...
Click to collapse
Ofcourse if you try backup any rom with locked password , it will have password after restore for sure !!!! don't u know ????
Just reset the data or don't create backup of data
I don't get it why you highlighting such things with red words without having proper knowledge about it
And about red root notification , reset data again and flash magisk as mentioned in post and flash riru and ed exposed , it will work for sure
As its working for me and 99% people out there in my group !

Bro, why are you sending so many exclamation marks? I'm not shouting. Chill, man.
anabhi said:
Ofcourse if you try backup any rom with locked password , it will have password after restore for sure !!!! don't u know ????
Just reset the data or don't create backup of data
I don't get it why you highlighting such things with red words without having proper knowledge about it
Click to expand...
Click to collapse
I do. It's just that in case of my previous phones, they accepted the correct password after restoration. ColorOS/LiteOS does not accept the password. Maybe this problem is unique to ColorOS. You know better than I do, obviously.
anabhi said:
And about red root notification , reset data again and flash magisk as mentioned in post and flash riru and ed exposed , it will work for sure
As its working for me and 99% people out there in my group !
Click to expand...
Click to collapse
I wiped data and flashed LITE APPS.zip again, 3 times. Didn't work.
Should I erase internal storage, too? I'll try it if you tell me to.
I also tried flashing Magisk 17.1 seperately, but it fails to mount /system in recovery.

anabhi said:
And about red root notification , reset data again and flash magisk as mentioned in post and flash riru and ed exposed , it will work for sure
As its working for me and 99% people out there in my group !
Click to expand...
Click to collapse
Update: I've finally solved the problem. Thanks for your patience and attempts to help. But even though I reset my data 5 times and tried, it didn't work.
I did something else.
I tried to flash Magisk seperately, like you said. It kept failing because R2X2 Recovery kept saying "! Cannot mount /system".
I had already wiped the system and reinstalled LiteOS twice. Didn't help. Same problem.
So, a while ago, I manually unmounted and remounted /system in R2X2 Recovery 3-4 times. Then I tried flashing the Magisk zip, it worked. I didn't need to reset data.
After rebooting, I had to I was finally able to flash the Riru module in Magisk and follow your method.
Maybe R2X2 Recovery has a small bug? I had to manually unmount and remount system to get things working.
Anyway, thanks for all these amazing works, man. The red notification is finally gone.

Im already chill bro but you shouldn't send any confirmation that its not working on my rom , even though it works alright that's what im trying to tell you
Im happy your issue gotta solved enjoy .

So far I've 2 problems with the Magisk.
# Magisk that comes with the installation (LITE APPS) doesn't successfully install Riru module and that's why the red blinking is still there.
# If I flash latest Magisk (19.2/3), it is able to install riru and other modules successfully but the Magisk is installed as "Core Only Mode" and you can never change that. That mode disables the modules and there comes the blinking issue.
I've tried to solve this multiple times and in many ways (re-flash,mounting etc.) but failed. What should I do now ?

Sayed Anan said:
So far I've 2 problems with the Magisk.
................... What should I do now ?
Click to expand...
Click to collapse
Read question 3 from f.a.q and module working fine on 17.1 and why u updating to 19.1 when Its not supported on our device
Install below zip by recovery
https://www.androidfilehost.com/?fid=6006931924117891637
Then extract lite apps zip and install magisk app normally

Thanks for the rom and solution of the red blinking.
Keep up the great works. Peace.

anabhi said:
thanks for lite os v2...keep it up..:good:
Click to expand...
Click to collapse

U welcome sayed and meraj

Need Vendor zip
Bro, apps fc and battery backup decreased. (sot- 6 hourz). Plz provide vendor img.. Want to reflash lite os.

indra94 said:
Bro, apps fc and battery backup decreased. (sot- 6 hourz). Plz provide vendor img.. Want to reflash lite os.
Click to expand...
Click to collapse
Bro just reflash rom zip again without wiping anything
Vendor.img is already there in lite os rom if u wanted to flash separately
Which apps force closing btw ?

Bugs Maybe ?
# When I use USB Tethering, sometimes (I've noticed 3 times, not everytime) my phone's apps are automatically closed and then after 2/3 seconds, showing a black screen, it comes back to normal (like it was forced closed).
# The second is that my notification bar is not showing last 3 icons from 2nd row.

Any suggestions ? Thanks.

Sayed Anan said:
# When I use USB Tethering, sometimes (I've noticed 3 times, not everytime) my phone's apps are automatically closed and then after 2/3 seconds, showing a black screen, it comes back to normal (like it was forced closed).
# The second is that my notification bar is not showing last 3 icons from 2nd row.
View attachment 4783982
Any suggestions ? Thanks.
Click to expand...
Click to collapse
About force close , i'll look
And your notification panel facing problem because of system ui tuner , reset system ui tuner preset and reboot

How to enable full Google Assistant in LiteOS v2? "Ok Google" isn't working. Can't launch Google Assistant buy long-tapping the Home button either.

Does magisk HIDE works....pl let me know as I use many banking apps ...

[Recovery] TWRP (vela) - Official 3.3.1-0 (final)

Hi.
First of all, thank you so much for all the time and effort you have put in to make this recovery for all of us.
Second, The url is bad I get a 404 error.
I would appreciate it if you could resend the correct link.

yotamy said:
Hi.
First of all, thank you so much for all the time and effort you have put in to make this recovery for all of us.
Second, The url is bad I get a 404 error.
I would appreciate it if you could resend the correct link.
Click to expand...
Click to collapse
It's working now. Thanks

I think it works
gringo80 said:
It's working now. Thanks
Click to expand...
Click to collapse
I did all your that you have instructed.
All my data was deleted, due to format data in twrp.
i will continue to test it and let you know.
@gringo80 , what will it take for you to create a global rom for this device?

yotamy said:
I did all your that you have instructed.
All my data was deleted, due to format data in twrp.
i will continue to test it and let you know.
@gringo80 , what will it take for you to create a global rom for this device?
Click to expand...
Click to collapse
i need time. may be next week !
btw, i'm working on a GSI patch. Some issues need to be fixed. I'm focusing myself now on this !

thanks. Some QA
gringo80 said:
i need time. may be next week !
btw, i'm working on a GSI patch. Some issues need to be fixed. I'm focusing myself now on this !
Click to expand...
Click to collapse
@gringo80 , you are the best!
you made me so happy.
you dont have to apologize or to explain yourself regarding the ROM . you are great
if you can send me a link to tutorial for creating a rom i will start the learning process
after examining the recovery:
1. it works! it identifies vela official rom
2. can not create twrp backup.
there is an error message after the attempt to backup DATA.
"create tar fork() process ended with error: 255" (attached recovery log and screenshot)
3. when choosing to install from internal storage, I get a list of unidentified folders
when you go up one level, everything is ok with the folders names (attached screenshot)
this is a minor bug
4. when changing things in settings, like "reversed navbar layout"
after reboot the values are changing to the original values. they are not saved.
this is a minor bug
Yotam

yotamy said:
@gringo80 , you are the best!
you made me so happy.
you dont have to apologize or to explain yourself regarding the ROM . you are great
if you can send me a link to tutorial for creating a rom i will start the learning process
after examining the recovery:
1. it works! it identifies vela official rom
2. can not create twrp backup.
there is an error message after the attempt to backup DATA.
"create tar fork() process ended with error: 255" (attached recovery log and screenshot)
3. when choosing to install from internal storage, I get a list of unidentified folders
when you go up one level, everything is ok with the folders names (attached screenshot)
this is a minor bug
4. when changing things in settings, like "reversed navbar layout"
after reboot the values are changing to the original values. they are not saved.
this is a minor bug
Yotam
Click to expand...
Click to collapse
this is not a bug. you have to format data after installing twrp.
from twrp homescreen, go to :
Wipe > Format Data (on the right) > type yes from the keyboard
TWRP don't support backup/ restore from encrypted files/folders. You must decrypt by formatting data !
Reboot to system. Install and config your rom then go TWRP to make backup !
Always put your roms and zip on the External SD Card... or sideload them by adb cmd from your windows PC !

Flash fstab.zip (OP) to avoid the encryption again by your MIUI rom !

sorry. i dont understand
gringo80 said:
Flash fstab.zip (OP) to avoid the encryption again by your MIUI rom !
Click to expand...
Click to collapse
fstab = file system table?
where do i find it?
flash it how? via twrp or fastboot?

yotamy said:
fstab = file system table?
where do i find it?
flash it how? via twrp or fastboot?
Click to expand...
Click to collapse
lol
it's inside the zip. go to my mediafire link. you will find everything
yes you flash it on twrp

i cannot thank you enough
thanks again

New Update (TWRP auto-decrypt)
yotamy said:
i cannot thank you enough
thanks again
Click to expand...
Click to collapse
Please update you TWRP ! (Highly recommended). Read OP carefully !
Thanks
:good:

You are the best.
I hope this will fix the issue I have with the fingerprint scanner. It's not working well since the twrp

yotamy said:
You are the best.
I hope this will fix the issue I have with the fingerprint scanner. It's not working well since the twrp
Click to expand...
Click to collapse
Yes, the fingerprint and the lockscreen pattern.
Follow the instruction on the OP !

Are the font files related to this twrp?
There are 2 font files in the link

yotamy said:
There are 2 font files in the link
Click to expand...
Click to collapse
NO, for the roms !

Speaking of roms.....

yotamy said:
Click to expand...
Click to collapse
work in progress

now its working good
gringo80 said:
work in progress
Click to expand...
Click to collapse
@gringo80 ,
the recovery works better now and recognizes fingerprint and lockscreen pattern
1. do you know why this twrp does not save my request to reverse navbar?
after each reboot it returns to the original values
2. in the rom, do you know how I can add 3 way reboot or advanced reboot?
in the china rom, under developer options, I dont have this option like in xiaomi.eu rom.
Thanks again @gringo80 for all the time and effort you put in
Yotam

yotamy said:
@gringo80 ,
the recovery works better now and recognizes fingerprint and lockscreen pattern
1. do you know why this twrp does not save my request to reverse navbar?
after each reboot it returns to the original values
2. in the rom, do you know how I can add 3 way reboot or advanced reboot?
in the china rom, under developer options, I dont have this option like in xiaomi.eu rom.
Thanks again @gringo80 for all the time and effort you put in
Yotam
Click to expand...
Click to collapse
Don't delete TWRP folder on your internal storage, to keep your TWRP settings.
3 way reboot is framework related. Sorry i don't support MIUI for now because i'm busy with GSI. Try to download "Simple Reboot" from the playstore.

[ROM] [OFFICIAL][A12][GApps] BlissRoms 15.x [guacamole]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Bliss is pleased to present to you
BlissRoms based on Android 12
Bliss ROMs comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.
Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customizations across all platforms you run Bliss on.
BlissROM Download
Latest TWRP recovery Download
Installing from Android 11 Rom's.
Code:
-Make sure you are on the latest OOS 11
- Dump the BlissROM zipfile through payload_dumper
- flash the partition images with the following commands
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
- Reboot and #StayBlissful
Code:
- If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you and our team quite some time.
- Download the Matlog app from the Play Store.
- Clear all previous logs and take the exact steps to produce the error you are receiving.
- As soon as you receive the error (probably a force close), go straight into Matlog and stop the log recording.
- Copy and paste the entire log either to Dogbin
- Save the log, and copy and paste the link into the forum with a brief description of the error.
BlissRoms Github
BlissRoms Gerrit
BlissRoms Device Sources
BlissRoms Kernel Source
BlissRoms Website
Bliss Blog
BlissRoms Facebook
BlissRoms Twitter
BlissRoms Instagram
BlissRoms Telegram Group
BlissRoms Announcements Telegram Channel
Bliss Wiki
If someone wants to donate, please do so via this PayPal link
Code:
[COLOR=DeepSkyBlue][B]
@Jackeagle
@electrikjesus
@Rohanpurohit
@rwaterspf1
@ideaman924
@Makaveli_da_dev
@ElfinJNoty
@BitOBSessiOn
@customworx
@nilac
@sixohtew
@aclegg2011
@Roger.T
@T.M.Wrath
@kanttii
@rev3nt3ch
@techfreak243
@SuperDroidBond
@USA_RedDragon
@bcrichster
@deadmanxXD
@krittin98
@BlackScorpion
@techexhibeo
@droidbot
@siphonay
@pacer456
@nitin1438
@theGeekyLad
@kunalshah912
@lordarcadius
@AryanAA
[/B]
[/COLOR]
A huge thanks to Chainfire, CM/LineageOS, Android-x86, Jide, topjohnwu (Magisk) @farmerbb & all the other developers who work hard to keep all the great features coming!
We really appreciate all your knowledge & hard work!
Thank you for using Bliss! And as always: #StayBlissful

Notes:

place holder 2

OTA updated from the previous version and it works fine!
Bluetooth kept crashing but after I cleared data it was just fine.
Android System Intelligence does keep crashing so I just disabled it.
Everything else seems to work just fine.
Bliss Settings -> Animations: is empty. Not sure if this is a bug or just not filled yet due to it being very new.
Oneplus Settings: now lacking refresh settings but I still have the QS tile as I OTAed. It does not work.
Could be a bad install from my part, can you confirm?

Sk1t said:
OTA updated from the previous version and it works fine!
Bluetooth kept crashing but after I cleared data it was just fine.
Android System Intelligence does keep crashing so I just disabled it.
Everything else seems to work just fine.
Bliss Settings -> Animations: is empty. Not sure if this is a bug or just not filled yet due to it being very new.
Oneplus Settings: now lacking refresh settings but I still have the QS tile as I OTAed. It does not work.
Could be a bad install from my part, can you confirm?
Click to expand...
Click to collapse
No bugs these things are just missing this release. All will be added going forward. Although A Clean flash wouldn't hurt. I am on the latest OOS firmware myself.

Awesome bro.. thanks a lot on your efforts .. gonna try right away

Hello,
I want to know if we should follow the installation recommended for version A11 or not.
Thank you

I did the flash as listed in first post but then followed by flash in latest twrp. Only camera is crashing for me. 24 hours in - all seems ok. I rooted with Magisk canary, however cannot seem to get in to twrp after that. Reflashing bliss boot.img & then installing twrp via ramdisk brings it back again - losing root...
Any suggestions to get it all working together?
Sometimes wake with power button is slow. It flashes the desktop background prior to displaying the lockscreen.

jejehtc said:
Hello,
I want to know if we should follow the installation recommended for version A11 or not.
Thank you
Click to expand...
Click to collapse
I'm using the latest twrp and an otg drive.

lev777 said:
I did the flash as listed in first post but then followed by flash in latest twrp. Only camera is crashing for me. 24 hours in - all seems ok. I rooted with Magisk canary, however cannot seem to get in to twrp after that. Reflashing bliss boot.img & then installing twrp via ramdisk brings it back again - losing root...
Any suggestions to get it all working together?
Sometimes wake with power button is slow. It flashes the desktop background prior to displaying the lockscreen.
Click to expand...
Click to collapse
I'm using this for Gcam https://www.celsoazevedo.com/files/android/google-camera/dev-greatness/f/dl11/
Also I am using magisk 23.0 stable without issue.
I hope this helps

After updating from previous version, my phone no longer receives texts. If I use a 3rd party messaging app I can send them, but it doesn't receive. Any ideas as to why?

lev777 said:
I did the flash as listed in first post but then followed by flash in latest twrp. Only camera is crashing for me. 24 hours in - all seems ok. I rooted with Magisk canary, however cannot seem to get in to twrp after that. Reflashing bliss boot.img & then installing twrp via ramdisk brings it back again - losing root...
Any suggestions to get it all working together?
Sometimes wake with power button is slow. It flashes the desktop background prior to displaying the lockscreen.
Click to expand...
Click to collapse
I'm using this for Gcam https://www.celsoazevedo.com/files/android/google-camera/dev-greatness/f/dl11/
Also I am using magisk 23.0 stable without issue.
I hope this helps

MoonlitJolty said:
After updating from previous version, my phone no longer receives texts. If I use a 3rd party messaging app I can send them, but it doesn't receive. Any ideas as to why?
Click to expand...
Click to collapse
Are you on the latest OOS firmware?
Did you do a clean flash?

srgrusso said:
Are you on the latest OOS firmware?
Did you do a clean flash?
Click to expand...
Click to collapse
I upgraded from v14.8 through the update notification. Before that it was a clean flash from latest official ROM

srgrusso said:
I'm using the latest twrp and an otg drive.
Click to expand...
Click to collapse
Gotta say one of the better a12 , just a fyi I tried the payload dumper install but no luck it went to a boot loop, then I saw this post and installed the rom via Nebrassy Twrp and a otg drive rom.zip file install, then a format Incase any one else here is wanting to try it, my order went like this,, your milage may vary ,,
1 boot into bootloader
2 fastboot boot twrp.img ( rename twrp zip to img)
3 . Install twrp by way of radio button in advance, reboot recovery
4 format wipe
5 reboot back to recovery
6 install rom zip file by way of USB C otg
7 wipe/format (probably not nessary but just to be sure)
8 reboot to system and set up
If root is needed
9 I just patched the boot file ( got the boot file from payload dumper) in magisk app and installed the patched file in fastboot
10 fastboot flash boot bootmagisk.img
hth

MoonlitJolty said:
After updating from previous version, my phone no longer receives texts. If I use a 3rd party messaging app I can send them, but it doesn't receive. Any ideas as to why?
Click to expand...
Click to collapse
Had the same problem. Thought a OTA was too good to be true. I check my logcat and it was a SQLite query error because of a failed upgrade from version 67 to 68. I couldn't find a fix even after deleting databases the the path etc.
You will have to do a clean install. Unless someone knows how to fix this. But I spent a solid hour or so using root to delete folder and setting perms. Nothing seem to make it covert the database. After I deleted it even after I set perms (at least I believe to be the correct perms) it will not create a new database.
TL;DR clean flash. Otherwise the SMS database will be "corrupted".
For feature requests:
This ROM lacks a lot of the good stuff the previous version had. OFC this is a very early build. But I would like to see high brightness mode return. The previous A11 version was one of the most feature rich ROMs but this version is bare compared to the former.

Sk1t said:
Had the same problem. Thought a OTA was too good to be true. I check my logcat and it was a SQLite query error because of a failed upgrade from version 67 to 68. I couldn't find a fix even after deleting databases the the path etc.
You will have to do a clean install. Unless someone knows how to fix this. But I spent a solid hour or so using root to delete folder and setting perms. Nothing seem to make it covert the database. After I deleted it even after I set perms (at least I believe to be the correct perms) it will not create a new database.
TL;DR clean flash. Otherwise the SMS database will be "corrupted".
For feature requests:
This ROM lacks a lot of the good stuff the previous version had. OFC this is a very early build. But I would like to see high brightness mode return. The previous A11 version was one of the most feature rich ROMs but this version is bare compared to the former.
Click to expand...
Click to collapse
Interesting hearing what the actual issue was. I actually had a crash happen that caused me to lose some data and decided to do a clean install. I'm fairly certain the crash was my fault because I was messing with root in ways that I barely knew what I was doing.

hammered58 said:
Gotta say one of the better a12 , just a fyi I tried the payload dumper install but no luck it went to a boot loop, then I saw this post and installed the rom via Nebrassy Twrp and a otg drive rom.zip file install, then a format Incase any one else here is wanting to try it, my order went like this,, your milage may vary ,,
1 boot into bootloader
2 fastboot boot twrp.img ( rename twrp zip to img)
3 . Install twrp by way of radio button in advance, reboot recovery
4 format wipe
5 reboot back to recovery
6 install rom zip file by way of USB C otg
7 wipe/format (probably not nessary but just to be sure)
8 reboot to system and set up
If root is needed
9 I just patched the boot file ( got the boot file from payload dumper) in magisk app and installed the patched file in fastboot
10 fastboot flash boot bootmagisk.img
hth
Click to expand...
Click to collapse
Thanks for posting this. Maybe with your permission I can add this to the install instructions in the op.

Does this rom feature Slim recents, or some alternative to the stock recent option?

srgrusso said:
Thanks for posting this. Maybe with your permission I can add this to the install instructions in the op.
Click to expand...
Click to collapse
For what it's worth, these steps from hammered58 are what got be up and running. I had difficulties getting the ROM to boot with flashing the op steps
Thanks srgrusso for a great ROM, and thanks hammered58 for listing what you did.

Database Info

welcome