Database Info

[15-3-17] MultiRom For LeEco Le 2 - LeEco Le 2 ROMs, Kernels, Recoveries, & Other Deve

{
"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 LeEco Le 2​Supports all Roms​
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:
All MarshmallowRoms
All Nougat Roms
SUPPORTED DEVICES:
LeEco Le 2 X520
LeEco Le 2 X526
LeEco Le 2 X527
LeEco Le S3 X522
Please Test it in other Le 2 and S3 Similar Devices and Report it Below.
Bugs:
Fingerprint Sensor doesn't work 4/10 Times while Dual Booting
In EUI, 4K Recording doesn't work in Stock Camera App after Installing MultiRom
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 LeEco Devices​Le 2 MultiRom Device Trees​MultiRom Manager App Source Codes​
Current Status:
Everything Works and Everything is Bugfree...
CREDITS:
Rishabh Rao (ME) - For Porting MultiRom to Le 2
Tasssadar - For his awesome MultiRom
nkk71 - For his No-KEXEC workaround
Version Information:
Status: Unofficial, Super Stable, Version 33
ENJOY!:good:
XDA:DevDB Information
MultiRom For LeEco Le 2, Tool/Utility for the LeEco Le 2
Contributors
Rishabh Rao
Source Code: https://github.com/multirom-leeco
Version Information
Status: Stable
Current Stable Version: v33
Stable Release Date: 2017-03-15
Created 2017-01-15
Last Updated 2017-03-23

Download Links:
MultiRom Manager App 2.4-rishabhrao

FAQ
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

Donations are Welcome!!!
YouTube Videos:​

This does not work on the S3 x522. and neither does the other multi-boot tool as it does not support le_s2_na

Guyz I'm on cm13 by sir Codeworkx.. And I'm receiving this error everytime.. .
Do i need to backup my current LOS then flash EUI then multirom and restore LOS backup as a secondary ROM...???

Prathamesh Kapure said:
Guyz I'm on cm13 by sir Codeworkx.. And I'm receiving this error everytime.. .
Do i need to backup my current LOS then flash EUI then multirom and restore LOS backup as a secondary ROM...???
Click to expand...
Click to collapse
Just go to buiod.prop and change device name to s2 enough
Hit thanks if it works

Great work bro
Sent from my Le X520 using XDA-Developers Legacy app

Kr1shna55 said:
Just go to buiod.prop and change device name to s2 enough
Hit thanks if it works
Click to expand...
Click to collapse
Multirom TWRP installed fine but multirom zip ends with error code 7...And after installing MR TWRP everything got smaller in size and my touchpal keyboard messed up....ss attached

Prathamesh Kapure said:
Multirom TWRP installed fine but multirom zip ends with error code 7...And after installing MR TWRP everything got smaller in size and my touchpal keyboard messed up....ss attached
Click to expand...
Click to collapse
Check by changing your dpi bro.. default would be 160.. change it to 400 or above

mdfarazb2 said:
Check by changing your dpi bro.. default would be 160.. change it to 400 or above
Click to expand...
Click to collapse
Okz bro thx I'll surely try....

Installing multirom zip isn't needed
Just inject boot.img from recovery
Also dpi you can change from settings
Sent from my HTC 10 using XDA Labs
---------- Post added at 05:13 AM ---------- Previous post was at 05:12 AM ----------
Prathamesh Kapure said:
Multirom TWRP installed fine but multirom zip ends with error code 7...And after installing MR TWRP everything got smaller in size and my touchpal keyboard messed up....ss attached
Click to expand...
Click to collapse
Check above post
Sent from my HTC 10 using XDA Labs

jhakjhuk1853 said:
Installing multirom zip isn't needed
Just inject boot.img from recovery
Also dpi you can change from settings
Sent from my HTC 10 using XDA Labs
---------- Post added at 05:13 AM ---------- Previous post was at 05:12 AM ----------
Check above post
Click to expand...
Click to collapse
Ty Jignesh bro I'll try that...

Prathamesh Kapure said:
Multirom TWRP installed fine but multirom zip ends with error code 7...And after installing MR TWRP everything got smaller in size and my touchpal keyboard messed up....ss attached
Click to expand...
Click to collapse
Same here!
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
jhakjhuk1853 said:
Installing multirom zip isn't needed
Just inject boot.img from recovery
Also dpi you can change from settings
Sent from my HTC 10 using XDA Labs
---------- Post added at 05:13 AM ---------- Previous post was at 05:12 AM ----------
Check above post
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Device not showing dpi more than 200

I can't install the official 19s from TWRP it ends in error 7 saying it's for le_s2_ww but the device is s2
Eventough I changed the device name in build. Prop I can't install

Kr1shna55 said:
I can't install the official 19s from TWRP it ends in error 7 saying it's for le_s2_ww but the device is s2
Eventough I changed the device name in build. Prop I can't install
Click to expand...
Click to collapse
Change first line of stock firmware zip's updater script
Not ur build.prop
TWRP doesn't care about your build.prop
This problem happens bcz all newer twrps are made for custom roms lile lineage as lineage uses device name s2 and no le_s2_ww to maintain consistency...
So stock will have problems if updater script not modified properly
Sent from my LeEco Le 2 using XDA Labs

britdude said:
This does not work on the S3 x522. and neither does the other multi-boot tool as it does not support le_s2_na
Click to expand...
Click to collapse
Change ur build.prop device name to s2
And it ll alll work just fine
Also tell me s3's ro.product.device name in the stock rom
I ll add support for it right away
Sent from my LeEco Le 2 using XDA Labs

Prathamesh Kapure said:
Multirom TWRP installed fine but multirom zip ends with error code 7...And after installing MR TWRP everything got smaller in size and my touchpal keyboard messed up....ss attached
Click to expand...
Click to collapse
Don't install MultiRom manually
Use the app to install BOTH THE RECOVERY AND THE MULTIROM ZIP TOGETHER
Sent from my LeEco Le 2 using XDA Labs

jhakjhuk1853 said:
Installing multirom zip isn't needed
Just inject boot.img from recovery
Also dpi you can change from settings
Sent from my HTC 10 using XDA Labs
---------- Post added at 05:13 AM ---------- Previous post was at 05:12 AM ----------
Check above post
Click to expand...
Click to collapse
You will never get the BOOT UI in that way
Always install both the MultiRom TWRP Recovery and the MultiRom ZIP TOGETHER
And injecting is sometimes not needed
Depends on the ROM
But actually not needed as we have no kexec implementation
Using App to install is both easier and recommended!
Sent from my LeEco Le 2 using XDA Labs

Rishabh Rao said:
Change ur build.prop device name to s2
And it ll alll work just fine
Also tell me s3's ro.product.device name in the stock rom
I ll add support for it right away
Click to expand...
Click to collapse
S3's ro.product.device is le_s2_na

Related

{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Xperia Z1 Compact. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that 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. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. 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 factory images again. Make backups. Always.​
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.​
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM (multirom-vXX-DDMMYY-amami.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom-amami.img) - download the IMG file from second post and use fastboot to flash it.
Patched kernel - You can use either the stock one in second post or third-party kernels which include the patch, you can see list in the second post. Download the IMG file and flash it via fastboot.
You current rom will not be erased by the installation.
Download links are in the second post.​
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of a ROM after first boot (with dalvik cache generated and connected to google account) takes more or less 700MB of space.​
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive (if USB drive partitions are not showed, disconnect USB drive and try again). You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
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 Advanced -> 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 ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/XperiaMultiROM/multirom (branch master)
Modified TWRP - https://github.com/XperiaMultiROM/android_bootable_recovery (branch master)
Kexec-hardboot patch for stock Sony kernel- https://github.com/Garcia98/kernel-amami/commit/4185df7caf40ac5aa6c7fc81d4098de58f9af19f
Touch patch for MultiROM menu- https://github.com/CyanogenMod/andr...mmit/907103b43eed80bd2bef89beb957d4052311ae67​
XDA:DevDB Information
MultiROM for Xperia Z1 Compact, Tool/Utility for the Sony Xperia Z1 Compact
Contributors
Garcia98
Version Information
Status: No Longer Updated
Created 2015-01-17
Last Updated 2016-06-10

Downloads
1. Main downloads
MultiROM: MultiROM-v30x-170115-UNOFFICIAL-amami.zip
Modified recovery (based on TWRP): TWRP_multirom-amami_20150201-00.img
MultiROM Manager Android app: Google Play or link to APK
Kernel w/ kexec-hardboot patch (Stock 4.4.4 - .157): stock-kexec-boot.img
Kernel w/ kexec-hardboot patch (Stock Lollipop): http://forum.xda-developers.com/showpost.php?p=61802911&postcount=119
Kernel w/ kexec-hardboot patch (CyanogenMod 12): kernel.zip
You need to have kernel with kexec-hardboot patch only in your primary ROM!​
2. third-party kernels with kexec-hardboot patch
* Validus LP kernel
* Resurrection Remix LP kernel
Nicely ask your kernel developer to merge kexec-hardboot patch.​
3. Uninstaller
MultiROM uninstaller: MultiROM_uninstaller.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.​
Changelog
Code:
MultiROM v30x
=====================
* Initial release
Recoveries:
Code:
01/02/2015
==========
* Disabled screen timeout.
* Added filesystems tools.
* Latest TWRP updates and changes.
21/01/2015
==========
* Fixed the installation of block images OTAs through MultiROM.
* Latest TWRP updates and changes.
17/01/2015
=====================
* Initial amami release

FAQ and other notes
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.​
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.​
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive./external SD card. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.​
Can I have different versions of Android working alongside
Yes.​
MultiROM recovery says it's 2.8.4. Why isn't it updated to 2.8.4.*highernumber*?
It is, it just shows wrong version.​
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.​

Finally, I've been waiting for this for a long time :victory:
Thanks for bringing this great mode to our device, gonna try it soon.
Regards,
Omar.

MultiROM Manager Android app
MultiROM Manager Android app is showing : this is unsupported device (amami) even with the latest version

LIONS1 said:
MultiROM Manager Android app is showing : this is unsupported device (amami) even with the latest version
Click to expand...
Click to collapse
The pull request in the source of the app for adding support for Z1 Compact is opened, just wait a few days until it is merged and the app updated
Sent from my D5503 using XDA Free mobile app

I am using stock as primary rom
And resurrection remix as secondary and i am getting error trying to boot resurrection remix rom,
I attached log.
Thanks

Rempty said:
I am using stock as primary rom
And resurrection remix as secondary and i am getting error trying to boot resurrection remix rom,
I attached log.
Thanks
Click to expand...
Click to collapse
Resurrection Remix on LP uses block images, so that's why it throws that error, but I have already talked with Omar and I think he will disable them for next release, fixing this issue

I'm using official CM12 nightly as primary rom and I tried to install CM11 ROM as secondary, but it failed (kexec-hardboot failure). And I have flashed the stock-kexec-boot.img from fastboot, but it caused bootloop. I think it is the .dat files problem. Although if I will flash the Validus ROM I wouldn't have working camera, because camera fix by xkonni will be overwrited by kexec kernel.

Once again congrats, and nice thread btw

Casserole said:
I'm using official CM12 nightly as primary rom and I tried to install CM11 ROM as secondary, but it failed (kexec-hardboot failure). And I have flashed the stock-kexec-boot.img from fastboot, but it caused bootloop. I think it is the .dat files problem. Although if I will flash the Validus ROM I wouldn't have working camera, because camera fix by xkonni will be overwrited by kexec kernel.
Click to expand...
Click to collapse
Wait for a custom kernel for CM12 (maybe Omar's GreatDevs kernel) with kexec support in Lollipop, as I don't think that CM12 will add kexec support by default due to its security issues, BTW .dat is just a problem for secondary ROMs not for host ROMs
Also stock-kexec-boot.img is just for stock ROMs (by Sony), flashing it in another ROM will cause a bootloop

I am not sure if I understand it correctly. But is it possible to use this on stock rom as primary and CM12 as secondary?

amnher said:
I am not sure if I understand it correctly. But is it possible to use this on stock rom as primary and CM12 as secondary?
Click to expand...
Click to collapse
Well, CM12 as secondary not yet, but yes other LP ROMs which doesn't have .dat files in the zip, like Validus
Sent from my D5503 using XDA Free mobile app

I am using the new Resurrection Remix build (without block image OTAs) as secondary and now work flawesly
Question
To install a rom to ext sdcard, need to create a ext4 partition?

Compiled kexec patched kernel to CM12
Checked, internal ROM - cm12, second - cm11. All works fine
This boot.img with TWRP 2.8.4.0 and worked vol keys for entering when you are booting
UPD:
Fix zip archive, zipping on Linux and it was gzip archive, sorry.

Rempty said:
I am using the new Resurrection Remix build (without block image OTAs) as secondary and now work flawesly
Question
To install a rom to ext sdcard, need to create a ext4 partition?
Click to expand...
Click to collapse
No, they are created automatically
russel5 said:
Compiled kexec patched kernel to CM12
Checked, internal ROM - cm12, second - cm11. All works fine
This boot.img with TWRP 2.8.4.0 and worked vol keys for entering when you are booting
Click to expand...
Click to collapse
Thank you, I'll attach it at second post as soon as possible
Sent from my D5503 using XDA Free mobile app

russel5 said:
Compiled kexec patched kernel to CM12
Checked, internal ROM - cm12, second - cm11. All works fine
This boot.img with TWRP 2.8.4.0 and worked vol keys for entering when you are booting
Click to expand...
Click to collapse
your zip seems to be broken (cannot unzip). downloaded various times.

paulle said:
your zip seems to be broken (cannot unzip). downloaded various times.
Click to expand...
Click to collapse
fix, check

russel5 said:
fix, check
Click to expand...
Click to collapse
Added to Downloads in second post

russel5 said:
fix, check
Click to expand...
Click to collapse
yes, now I get it unzipped. Thank you..

/include/disclaimer or warning.h
/*
* Your warranty is not void as I Think!!
*
* 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 Port
* 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, Hard, a Lot $ Lot
* But I will always be here to HELP! You...
*/
yO Guys..
To Support the Project PM me but if you are not a Developer than Press Thumps Up! :good: Button for Encouraging..:good::fingers-crossed:
I @yoAeroA00 and @m11kkaa has spended two Days to Successfully Port it to Nokia X2 so you better try it out...
If you wan't any feature to be added in EFIDroid than you are specially welcomed:good:​
XDA:DevDB Information
EFIDroid for Nokia X2, Tool/Utility for the Nokia X2
Contributors
yoAeroA00, m11kkaa, Nokia X2 Users and Fan's...
Source Code: https://github.com/efidroid/device/tree/nokia/ara
Version Information
Status: Stable
Created 2017-01-14
Last Updated 2017-01-21

Let's Continue
Table of Contents
1> About EFIDroid
2> How to install EFIDroid on any Supported Device
3> Configuring new ROMs from the APP before Installation
4> Adding a System to the newly created ROM Slot
5> MultiBooting into your newly created ROM
6> FAQ
About EFIDroid
As @m11kkaa said EFIDroid is a easy to use, powerful 2ndstage-bootloader based on EDKII(UEFI).
It can be installed one-click with the EFIDroidManager App. You can Add/RemoveEdit Multiboot ROM's.
There's no special support needed by ROM's or RecoveryTools(no kexec etc).
And I think @yoAeroA00 EFIDroid is a relatively new Multiboot solution for Snapdragon SOC based mobile devices which is based on the EFI implementation by Intel (EDK2).
In last few month's 90% of the Developers has just drop out for no Reasons. Without these drop-out's it could gain a Huge Success.
For more information , please visit to the Github WIKI and for support, please visit EFIDroid Slack. @m11kkaa and I @yoAeroA00 will always be on Slack Community to Help you Porting it to your Devices or Help you a little bit.:silly:
How to install EFIDroid on any Supported Device
> You can Download EFIDroid Manager App from Google Play.
> After installing EFIDroid Manager App Go to Install/Update..
> Then Click Install:
{
"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"
}
> It should be Successfully Installed!
Configuring new ROMs from the APP before Installation
Note: You need to configure the system before installing any new ROM for Multibooting.
> Before you do any of this you should have a ROM .zip file Handy on your SD card (/storage/sdcard1/ and !!NOT!! /sdcard!).
> To Add a ROM Slot got to "Operating Systems" List and click on the FAB (Floating Action Button)..
> Choose an ICON for your new ROM Slot..:good:
> Choose in the screen /data/media/0/multiboot or any other on screen places as a location for your ROM Slot.
> Enter a name and description for your ROM.
> You can leave the partitions as they are (Schema LoopSystem + BindOther) or modify their names or sizes.
> If you need your own custom replacements than configure them as per your needs in the Replacement Tab.
> Press the tick in the top right corner if you have finished setting up things.
> Now you can see that your newly created ROM Slot is in the "Operating Systems" list.
> Then Reboot to See the EFIDroid's Magic!:silly:
Adding a System to the newly created ROM Slot
Note: Once you are in the UEFI, you can navigate around with Volume Down to go Down, Volume Up to go Up and the Power Button to confirm your Selection.
> To flash a ROM select the empty slot, select TWRP (Internal) and then press Power Button.
> Next select your newly created ROM Slot.
> You will be now landed in TWRP and be greeted with a warning about keeping the System Partition ReadOnly. Swipe the Slider at the bottom to Acknowledge it.
> I will highly Recommend you to format all the Partitions(System, Data, Cache) to EXT4 or any file System before you Continue to Install any ROM..
> Click Install, select the Micro SDcard at the Storage tab and then navigate to the directory where your ROM .zip is placed.
> Select your ROM .zip file ****!-ROM.zip.
> Disable the Zip file signature verification and slide the Confirmation Bar.
> If Everything is good then you can Reboot!
MultiBooting into your newly created ROM
> Select your new ROM and press the Power Button. Do not be put off because of the long “Booting <ROMName>” screen as your ROM will open & play the boot animation very late (Unfortunately for only the First time).
> Aaaand Finally we are in the New ROM!
FAQ
Note: If you have any questions, please ask in the This Forum thread or PM me
Q.1> This is a UEFI port, can we port Windows?
> Not, till Yet but with your support we can easily Port it.
Q.2> Can I still use fastboot after installing this?
> If you flash to the boot/recovery partitions, UEFI will be overwritten.(dd in Android/Recovery instead) all other partitions will work as usual.
Q.3> I FOUND A BUG, what should I do now?
>Report it on Github. If there already is an issue for your bug and you don't have anything useful to add, just hit the thumbs-up button. This way I know how many people are affected and can adjust my priority list. I will not keep track of all bugs reported in posts of this thread. If you want a bug to get fixed, report it on Github.
​[email protected]​

yUP Two...
:fingers-crossed::good:

Why you not start your new project to fixing ril and camera on cm13 and los 14 by your hacking mind

netradip said:
Why you not start your new project to fixing ril and camera on cm13 and los 14 by your hacking mind
Click to expand...
Click to collapse
he's not ROM builder but kernel builder :laugh:

yoAeroA00 said:
yO Guys..
Currently Testing..
To Support the Project PM me but if you are not a Developer than Press Thanks! Button for Encouraging..:good::fingers-crossed:​
XDA:DevDB Information
EFIDroid for Nokia X2, Tool/Utility for the Nokia X2
Contributors
yoAeroA00, yoAeroA00, Nokia X2 Users and Fan's...
Source Code: http://Coming Soon...
Version Information
Status: Testing
Created 2017-01-14
Last Updated 2017-01-14
Click to expand...
Click to collapse
Could you please fix bugs on the new Lineage OS ?

Multi rom on 2,2gb is bad idea

thinhx2 said:
Multi rom on 2,2gb is bad idea
Click to expand...
Click to collapse
It is not multi ROM Bro. It is Grub bootloader through which I can even boot from a system image file stored in a folder on sdcard... And even boot Linux on the Mobile(Need's to be Ported First!)....
If anyone wan't to help me than PM me so that we can give it a start...

KenX2 said:
Could you please fix bugs on the new Lineage OS ?
Click to expand...
Click to collapse
Yes, but only those bugs related to kernel...

How to you add config of X2 to EFIDroid?

i'm building efidroid
source: https://github.com/thinhx2/device @yoAeroA00
I need you phone to take file,i build done lk.img but i need 1 nokia x2 to read file

thinhx2 said:
i'm building efidroid
source: https://github.com/thinhx2/device @yoAeroA00
I need you phone to take file,i build done lk.img but i need 1 nokia x2 to read file
Click to expand...
Click to collapse
No need Bro I have successfully made EFIDroid for Nokia X2...

after install this my sdcard not detected on twrp and stock ROM. But sdcard read on cm12, i have change my sdcard still got this problem. On stock rom i have clean flash trough NCS.

frnsl3 said:
after install this my sdcard not detected on twrp and stock ROM. But sdcard read on cm12, i have change my sdcard still got this problem. On stock rom i have clean flash trough NCS.
Click to expand...
Click to collapse
Hmm you have followed wrong steps while installing EFIDroid..
Uninstall it and see if your problem still persists..[emoji44] [emoji6]
Sent from my ara using XDA-Developers Legacy app

yoAeroA00 said:
Hmm you have followed wrong steps while installing EFIDroid..
Uninstall it and see if your problem still persists..[emoji44] [emoji6]
Sent from my ara using XDA-Developers Legacy app
Click to expand...
Click to collapse
My SD card could be detected in TWRP and CM12, but it's mounted Read-Only, I can not add any file or remove any file.
I tried to connect it to my PC and format it or use the " Check " inside tool then It's had worked correctly but the problem happens again when I reboot my phone
How can I fix this ?

yoAeroA00 said:
Hmm you have followed wrong steps while installing EFIDroid..
Uninstall it and see if your problem still persists..[emoji44] [emoji6]
Sent from my ara using XDA-Developers Legacy app
Click to expand...
Click to collapse
all i need is just repartition my sdcard bro :silly::silly:, just install efidroid its get partition error. now working as usual :victory:

@yoAeroA00 can you share direct image file, and "how to install manually" steps for advanced users like me?
---------- Post added at 11:15 AM ---------- Previous post was at 10:58 AM ----------
symbuzzer said:
@yoAeroA00 can you share direct image file, and "how to install manually" steps for advanced users like me?
Click to expand...
Click to collapse
"https://github.com/efidroid/files/releases/download/builds/otapackage-20170120-nokia_ara.zip"
files already found. can you help with manual installation steps?

symbuzzer said:
@yoAeroA00 can you share direct image file, and "how to install manually" steps for advanced users like me?
---------- Post added at 11:15 AM ---------- Previous post was at 10:58 AM ----------
"https://github.com/efidroid/files/releases/download/builds/otapackage-20170120-nokia_ara.zip"
files already found. can you help with manual installation steps?
Click to expand...
Click to collapse
got to https://slack-redir.net/link?url=ht...ndroid/software-hacking/efidroid-t3447466&v=3

yoAeroA00 said:
got to https://slack-redir.net/link?url=ht...ndroid/software-hacking/efidroid-t3447466&v=3
Click to expand...
Click to collapse
No, I didnt mean that.
- I flashed lk.img via fastboot flash boot lk.img
- I can reach efidroid's menu
- But I can't add installed rom and twrp recovery from there
(I can't use efidroid's android app, because of my data partition is encrypted - it show's not supported message when I click install button)
So is there any advanced way to add my rom and recovery manually, like editing a xml based config file etc?

symbuzzer said:
No, I didnt mean that.
- I flashed lk.img via fastboot flash boot lk.img
- I can reach efidroid's menu
- But I can't add installed rom and twrp recovery from there
(I can't use efidroid's android app, because of my data partition is encrypted - it show's not supported message when I click install button)
So is there any advanced way to add my rom and recovery manually, like editing a xml based config file etc?
Click to expand...
Click to collapse
Ohh... You should flash uefi_boot.img not lk.img and currently EFIDroid is in development so you can only add ROMs by using it's app and soon I will write a tutorial on how to install ROMs on EFIDroid...using app[emoji6]
Sent from my ara using XDA-Developers Legacy app

{
"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 mido​Supports 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 Devices​mido MultiRom Device Trees​MultiRom 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.

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo.
Important info:
ROM OS Version: 7.1.2 Nougat
ROM Kernel: Linux 3.4
- Note: Warning! You are the only responsible of your actions, and especially of your use of your phone. Neither I, neither XDA, are responsible of your handling with your phone.
- Note: You must have unlock your bootloader on sony's page
- Note: You need to use the stock bootloader. If you switched to the Open Device Bootloader (D2203), please flash again the old bootloader. Here you have FTF file: (https://drive.google.com/file/d/0B07I-JdP5dQzSWs3SW1uYXVsWjg/view?usp=sharing). If you don’t remember the process, you can check it on Google.
Working
All
Almost working
Cameras are not fully working. You can take panorama pictures but no videos nor photos (with Snap app). In some other apps you can take them sometimes. In cameringo for example you can take everything. Fixed on V4!
Known issues
WiFi MAC address is a default address because TA is not being read yet. We are working to fix it. This only makes that some WiFi networks does not allow your phone to connect because another device with the same address is connected, but this is not usual so you shouldn't have problems with that. Fixed on V4!
Audio bugs:
Songs may pause randomly after some time and continue after some secs.
Some games might have a laggy audio problem (Pokémon Go for example).
Download
You have to download the latest version of boot.img, recovery.img and system.img or flashable zip from this link https://drive.google.com/drive/folders/0B07I-JdP5dQzM1FRbXY4bGt4VzQ?usp=sharing
For Google apps (Play Store, Google account...) go to http://opengapps.org/, choose Arm for Android 7.1 and select any variant you want. We recommend Pico variant as is the smalles one (you can choose stock if you want Pixel launcher).
Install
You need to install adb and fastboot. If you don’t know how to do that, click on the link down below.
https://forum.xda-developers.com/showthread.php?t=2588979
Then, in your file explorer, go to « This computer » and search for the file « adb ».
Next, put files in the folder « adb ». Hold shift and click (right click). Then click on « open terminal » or do « cd » (you need to find the location of your file « adb »).
Boot your phone in Bootloader/fastboot (this is the exact same thing but with different names depending on how you call it).
Before all, you have to start cleaning the device so do a wipe then:
In the terminal, type the command « fastboot devices »
You should see something like this for example :
Code:
CVH7N15B11004115 fastboot
If it isnt’t the case
go to Device Manager
Find your phone
Click on properties
Update the driver for your phone
Choose « Bootloader interface » and retry the command « fastboot device »
Now, you’ve done a big part of the work! You only have to type the following commands.
Commands
Code:
1. fastboot flash boot "name of boot".img
2. (Starting from V4 - 2020-01-23) fastboot flash FOTAKernel "name of recovery".img
[COLOR="SeaGreen"]3. Boot TWRP with Vol - and flash LineageOS zip[/COLOR]
[B][COLOR="Red"]IMPORTANT:[/COLOR] Only if Magisk was automatically installed after flashing LineageOS zip and after the first reboot the ROM is not booting:[/B] [COLOR="SeaGreen"]Flash again any boot.img with fastboot or TWRP (using "Install image" option)[/COLOR]
[COLOR="red"][STRIKE]fastboot –S 256M flash system "name of system".img[/STRIKE] (that was for v1 && v2 )[/COLOR]
You will boot into your new ROM.
IMPORTANT!
If your Xperia E3 model is D2202 or D2212 (3G-only single and dual SIM variants) you may need to flash an additional firmware zip in order to get SIM card working if it does not work after the first boot. Here you have the link:
https://drive.google.com/drive/folders/0B07I-JdP5dQzRG83U2d2aXBmUWM?usp=sharing
Note that there is a zip for each variant, but this is only to avoid confusion. Both are the same zip and you can flash any of them.
Extras
Now all you have to do is to flash the GAPPs in the recovery.
For Magisk go to https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
and download Magisk app and zip (ONLY FOR VERSIONS BEFORE V4: using the boot named Magisk) and its corresponding Magisk version.
Contributors
@rmnhg Ramón Hernández
@infus38 Thomas
@Konstantinosj77
@galaxyfreak
@adfad666
@vinay
@jerpelea
@Ｄｈｒｕｖ
@jpzex
@Nicklas Van Dam
@madcodez
Changelog
- note only last change will be post ( change log for v1 and v2 was remove )
New release 14/02/20 v4.1
Fixed a sensors bug introduced on V4. Now sensors should work as before.
New release 23/01/20 v4
Recovery is now independent from Boot partition! Now you should flash recovery image to FOTAKernel using fastboot or to "recovery" partition using TWRP. With this measure you can flash any Magisk version without waiting us to update boot.img.
Camera fully working now! Torch also works. The only thing you can't do is to enable Noise Reduction on Snap as it is not supported on Stock ROM
Bluetooth and WiFi addresses are now fine. They should be the same as the stock ones.
Compass may work better.
New release 06/01/18 v3
Tethering works now (in WiFi, BT and USB)
NFC works perfectly now
Now no user needs to flash additional firmware blobs This is not always working.
Camera working partially (I recommend you taking photos with panoramic mode and videos with other apps, like Instagram)
TWRP 3.2.1
Magisk v15.2 is now supported
Sony's framework is preinstalled, you are able to download Sony's Apps from Google Play
Safety net passed using Magisk+Magisk Hide
XDA:DevDB Information
LINEAGE-OS OMSv7, ROM for the Sony Xperia E3
Contributors
infus38, rmnhg
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: V4.1
Stable Release Date: 2020-02-14
Created 2018-03-23
Last Updated 2020-02-14

Screenshots, do you have? And steal in development?

eladiocesar said:
Screenshots, do you have? And steal in development?
Click to expand...
Click to collapse
Yes i have screenshots i can not now post them the rom work and is very stable you Can try

When I give the 2nd command, a list of commands shows up. What to do?
Edit: Resolved by @infus38 Thomas

First Of all Thanx Everyone Who Has Contributed in the making of this ROM i m glad that Dev Has not left the Users Of E3 in the dark.
So,I hv a Xperia E3 D2203 18.5.0.C.19 Currently i m on Cyanogen 11 ROM UNOFFICIAL.
I hv some questions regarding this ROM-
1-Does this ROM hv any Recovery Installed?
2-This ROM does not hv root access so if i want root cn i flash the SuperSU Zip 2.79?
3-Will u make a flashable Zip Package Of via Recovery for this ROM?
4-Do i need to perform a Wipe Data/Factory Reset in Recovery before flashing this ROM?
5-Are there any Special Features In this ROM?
6-Which Gapps Should i Flash with this ROM?
7-Does This ROM support Substrantum Theme Manager?
I think that's It.
Thanx In Advance.:fingers-crossed::fingers-crossed:

..

device dosn't boot only boot animation are show(D2202) please help.
edit-solved

priyesh9 said:
device dosn't boot only boot animation are show(D2202) please help .
Click to expand...
Click to collapse
We tested on each variant this rom without problem, you can quote me exactly what you did in private message pleas
I will take care of your problem do not worry
Edit now solved

UPDATE: now you have boot.img with latest TWRP included

Edit-Solved

Ali Haide 001 said:
First Of all Thanx Everyone Who Has Contributed in the making of this ROM i m glad that Dev Has not left the Users Of E3 in the dark.
So,I hv a Xperia E3 D2203 18.5.0.C.19 Currently i m on Cyanogen 11 ROM UNOFFICIAL.
I hv some questions regarding this ROM-
1-Does this ROM hv any Recovery Installed?
2-This ROM does not hv root access so if i want root cn i flash the SuperSU Zip 2.79?
3-Will u make a flashable Zip Package Of via Recovery for this ROM?
4-Do i need to perform a Wipe Data/Factory Reset in Recovery before flashing this ROM?
5-Are there any Special Features In this ROM?
6-Which Gapps Should i Flash with this ROM?
7-Does This ROM support Substrantum Theme Manager?
I think that's It.
Thanx In Advance.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
1=For now no we have some problem,But later yes(edit The recovery has just been officially run from 18pm French time , You need to download the boot.img again to get the recovery if you have to download before )
2=Yes this ROM can be root now :flash this in recovery http://tiny.cc/latestmagisk and install apk http://tiny.cc/latestmanager
3=just with the bootloaderfor now you can flash the rom , not with the recovery (you will be able to read the topic all the same I gave myself trouble) ,for now 2 .img same aosp but follow the topic , soon the rom will be just a .zip we worked on
4=Yes you must all whyp but your sd card is not neccesaire of format
5=yes just lineage os
6=you can choos this for gapps http://opengapps.org/ choos arm 7.1 pico and flash in recovery (you can choos stock if you want pixel luncher)
7=This rom supports the substratum legacy theme soon the support of full omsv7
Thank you for your comment,If you have any other question you can ask them

infus38 said:
1=For now no we have some problem,But later yes(edit The recovery has just been officially run from 18pm French time , You need to download the boot.img again to get the recovery if you have to download before )
2=Yes this ROM can be root now :flash this in recovery http://tiny.cc/latestmagisk and install apk http://tiny.cc/latestmanager (If this does not work, wait for the next version of the boot.img it will have to include the root with magisk)
3=just with the bootloaderfor now you can flash the rom , not with the recovery (you will be able to read the topic all the same I gave myself trouble) ,for now 2 .img same aosp but follow the topic , soon the rom will be just a .zip we worked on
4=Yes you must all whyp but your sd card is not neccesaire of format
5=yes just lineage os
6=you can choos this for gapps https://www.androidfilehost.com/?w=files&flid=171931&sort_by=date&sort_dir=DESC
7=This rom supports the substratum legacy theme soon the support of full omsv7
Thank you for your comment,If you have any other question you can ask them
Click to expand...
Click to collapse
Two Question-
1-IS this Rom Support Substratum theme Manager at this Current Stage?
2-Can I flash Those SuperSU Addons Which Are Given On The Official Page Of LineageOS?
Thanks For Ur Help.:fingers-crossed::fingers-crossed:

Ali Haide 001 said:
Two Question-
1-IS this Rom Support Substratum theme Manager at this Current Stage?
2-Can I flash Those SuperSU Addons Which Are Given On The Official Page Of LineageOS?
Thanks For Ur Help.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
1=This rom for now supports partially the substratum( just leagcy) but soon full omsv7 suport
2=for now the boot.img is in the process of modification because any method of root does not work, but in the next verssion the root will be included with magisk su (edit now at the time in french 19 pm new boot with root on cloud you can donwload :laugh: thanks @rmnhg )

rmnhg said:
UPDATE: now you have boot.img with latest TWRP included
Click to expand...
Click to collapse
Thank You Bro, Now We Hv TWRP Included :fingers-crossed::fingers-crossed::fingers-crossed:
Already Pressed The Thanks Button.
One Thing -
1-What Is The Version Of TWRP?
---------- Post added at 06:14 PM ---------- Previous post was at 06:08 PM ----------
infus38 said:
1=This rom for now supports partially the substratum( just leagcy) but soon full omsv7 suport
2=for now the boot.img is in the process of modification because any method of root does not work, but in the next verssion the root will be included with magisk su (edit now at the time in french 19 pm new boot with root on cloud you can donwload :laugh: thanks @rmnhg )
Click to expand...
Click to collapse
So, Now I don't Need To Flash The Files (For Root Access) Which You Hv Given Me Before
Thanx In Advance.
Downloading Now.

Ali Haide 001 said:
Thank You Bro, Now We Hv TWRP Included :fingers-crossed::fingers-crossed::fingers-crossed:
Already Pressed The Thanks Button.
One Thing -
1-What Is The Version Of TWRP?
---------- Post added at 06:14 PM ---------- Previous post was at 06:08 PM ----------
So, Now I don't Need To Flash The Files (For Root Access) Which You Hv Given Me Before
Thanx In Advance.
Downloading Now.
Click to expand...
Click to collapse
Yes just flahs lates boot_twrp_root.img ??

Ali Haide 001 said:
Thank You Bro, Now We Hv TWRP Included :fingers-crossed::fingers-crossed::fingers-crossed:
Already Pressed The Thanks Button.
One Thing -
1-What Is The Version Of TWRP?
Click to expand...
Click to collapse
You're welcome ?. TWRP is in it's latest version (3.1.1). Material design and multi language.

infus38 said:
We tested on each variant this rom without problem, you can quote me exactly what you did in private message pleas
I will take care of your problem do not worry
Click to expand...
Click to collapse
edit -solved

I was able to flash this ROM. I followed the instructions stated above but my d2203 was just stock at the LOS boot logo. I don't know what I did wrong. I came from stock KitKat rom before I flashed this. If that helps. HELP PLS! I really wanna try this ROM so badly
thanks @infus38 Thomas for helping me solve the problem

Screenshots
Note I'm using custom launcher and custom theme (flux substratum theme)
My review:- I'm using this ROM from 4 days and this ROM is totally awesome. Since I don't use Camera of this device that much I love this ROM.

infus38 said:
Yes just flahs lates boot_twrp_root.img
Click to expand...
Click to collapse
Hey,One More Thing-
1-Do I Need To Flash This ROM above Stock ROM Or It Does Not Matter Cause I Am On CM 11 Unofficial Flamingo?
---------- Post added at 09:55 AM ---------- Previous post was at 09:52 AM ----------
Ｄｈｒｕｖ said:
Screenshots
Note I'm using custom launcher and custom theme (flux substratum theme)
My review:- I'm using this ROM from 4 days and this ROM is totally awesome. Since I don't use Camera of this device that much I love this ROM.
Click to expand...
Click to collapse
So,You Have Flashed This ROM.
How Is The Battery Life?
Can You tell Me What are The Features In This ROM (By Features I mean The Features Which are in cm Roms Like Center Clock,Privacy Guard,Performance Profile,Etc)?
Is Substratum Theme Manager Working Fine?
Thanks In Advance.

{
"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"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.4.0
PitchBlack version: 3.0.0
For device: excalibur
Maintainer/Authors build: @TheMalachite
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/TheMalachite/android_device_xiaomi_excalibur
Kernel: Prebuilt kernel from MIUI V11.0.2.0.QJXINXM
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Device Changelog
Code:
2020-07-30
- Initial unofficial release
PBRP Changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Downloads
Flashable zip
https://drive.google.com/file/d/18MzNCTExOWLiu9ZUD3A7SXlD4QY2grrZ/view?usp=drivesdk
XDA:DevDB Information
PitchBlack Recovery Project, Tool/Utility for the Redmi Note 9 Pro Max
Contributors
TheMalachite, Reza Adi, Shovon, Manjot Sidhu, Mohd Faraz, Sagar
Version Information
Status: Stable
Current Stable Version: 3.0.0
Stable Release Date: 2020-07-30
Created 2020-07-30
Last Updated 2020-07-30

Bugs: You tell me

Reserved #2

thank you sir..... for providing this recovery and opportunity to test your initial relese

Good but when other custom rom for redmi note 9 pro max

[email protected]@ said:
Good but when other custom rom for redmi note 9 pro max
Click to expand...
Click to collapse
When their will be dev who wanna build custom rom for it

Flashed it via fastboot from Platform Tools folder. Rebooted into recovery mode. And Pitch Black was installed successfully. Then transferred the pitchblack zip folder to sd card. And installed it through pitchblack. Rebooted to system.
After the system reboot, again switched off phone and entered recovery mode, only to find that the pitchblack was overwritten by system recovery.
tried wiping data second time, after installing pitchblack. Again it was overwritten by system recovery.
Do I need to do any additional steps within pitchblack, before rebooting to system?
Or install any ROM?
My final aim is to install LineageOS, which currently isn't available for this devise..
Any help is greatly appreciated...

Vijo123 said:
Flashed it via fastboot from Platform Tools folder. Rebooted into recovery mode. And Pitch Black was installed successfully. Then transferred the pitchblack zip folder to sd card. And installed it through pitchblack. Rebooted to system.
After the system reboot, again switched off phone and entered recovery mode, only to find that the pitchblack was overwritten by system recovery.
tried wiping data second time, after installing pitchblack. Again it was overwritten by system recovery.
Do I need to do any additional steps within pitchblack, before rebooting to system?
Or install any ROM?
My final aim is to install LineageOS, which currently isn't available for this devise..
Any help is greatly appreciated...
Click to expand...
Click to collapse
I am waiting for my bootloader time 133 hours provided by MI. I will flash and provide feedback on 13 August.

kannss said:
I am waiting for my bootloader time 133 hours provided by MI. I will flash and provide feedback on 13 August.
Click to expand...
Click to collapse
Ok. Never go back to 'Mi Unlock Status' under Developer Options to add ur device again...
I did that mistake and my wait time got reset to give me new wait time.
Also don't log out of Mi account or play with 'Find Device' settings.
U may know already. But im just saying..
If u face any driver related issues, then in the Mi Unlock Tool itself, they have provided a way to install it, if u check their settings...
Good Luck

Vijo123 said:
Flashed it via fastboot from Platform Tools folder. Rebooted into recovery mode. And Pitch Black was installed successfully. Then transferred the pitchblack zip folder to sd card. And installed it through pitchblack. Rebooted to system.
After the system reboot, again switched off phone and entered recovery mode, only to find that the pitchblack was overwritten by system recovery.
tried wiping data second time, after installing pitchblack. Again it was overwritten by system recovery.
Do I need to do any additional steps within pitchblack, before rebooting to system?
Or install any ROM?
My final aim is to install LineageOS, which currently isn't available for this devise..
Any help is greatly appreciated...
Click to expand...
Click to collapse
Enable DM VERITY

MaheshTechnicals said:
Enable DM VERITY
Click to expand...
Click to collapse
Will it keep PB Recovery form overwritten?
Because, ppl try to disable DM verity, so im asking.
Also, I managed to root my Pro Max using Magisk manager. But a lack of custom recovery always hurts.
So how do i Enable DM verity now?

I'm on rooted (magisk), device with xposed installed and working BUT stock recovery. waiting for you to successfully stick the tarp and I'll follow. Kindly keep updating results and steps tried by you.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
Vijo123 said:
Will it keep PB Recovery form overwritten?
Because, ppl try to disable DM verity, so im asking.
Also, I managed to root my Pro Max using Magisk manager. But a lack of custom recovery always hurts.
So how do i Enable DM verity now?
Click to expand...
Click to collapse
I'm on rooted (magisk), device with xposed installed and working BUT stock recovery. waiting for you to successfully stick the tarp and I'll follow. Kindly keep updating results and steps tried by you.

I'm currently using SD Maid app (Pro version) to remove all unnecessary bloatwares. Works like a charm.
And IMO, also works better than Termux or any other debloater. Although debloating is just one of the function of termux, but if u r using it just to debloat, then better go for SD Maid ?

UPDATE : i installed as per instructions for installation from PC, first recovery.img and then flashed whole zip. Worked great. after rebooting device twice manually,, recovery sticks,, and its a great one. excellent work done.
just one question, what does magisk manager installation in recovery do ? (Specials>tools>magisk manager)

coolvipcandy said:
UPDATE : i installed as per instructions for installation from PC, first recovery.img and then flashed whole zip. Worked great. after rebooting device twice manually,, recovery sticks,, and its a great one. excellent work done.
just one question, what does magisk manager installation in recovery do ? (Specials>tools>magisk manager)
Click to expand...
Click to collapse
Did u wipe data or dalvik etc. Because mine got overwritten by system recovery.
Can u please tell how did u do, STEP BY STEP?
Maybe my adb fastboot tools were outdated??

Vijo123 said:
Will it keep PB Recovery form overwritten?
Because, ppl try to disable DM verity, so im asking.
Also, I managed to root my Pro Max using Magisk manager. But a lack of custom recovery always hurts.
So how do i Enable DM verity now?
Click to expand...
Click to collapse
Vijo123 said:
Did u wipe data or dalvik etc. Because mine got overwritten by system recovery.
Can u please tell how did u do, STEP BY STEP?
Maybe my adb fastboot tools were outdated??
Click to expand...
Click to collapse
i did as mentioned in first post,, as i was already root, i first flashed recovery.img and then from recovery, flashed the whole zip archive. thats all.
then.booted to system,, again booted manually to recovery and it was there,, and checked twice again, recovery was there.
---------- Post added at 05:25 AM ---------- Previous post was at 05:24 AM ----------
i didnt mess with dm verity,,

Working fine in my device. Successfully rooted and installed Edxposed. Everything working fine.

how to wipe "system" partition, there's no option for that ??
wipe > Advance > ???

Format data option
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
Do not install inbuilt magisk from this recovery. It gives bootloop, download from github or xda and flash zip manually

Stuck on fastboot mode
PLEASE HELP
i installed twrp recovery in my redmi note 9 pro max and install magisk , now my device is stuck on fastboot.
---------- Post added at 05:22 AM ---------- Previous post was at 05:18 AM ----------
kannss said:
Working fine in my device. Successfully rooted and installed Edxposed. Everything working fine.
Click to expand...
Click to collapse
bro when i installed i got stuck in fastboot
what should i do now ...? should i install custom rom or not