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. 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
Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install + one optional (deprecated) :
MultiROM (multirom-YYYYMMDD-v33x-device.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (multirom-YYYYMMDD-recovery-fota-device.zip) - download the ZIP file from second post and use a recovery
to flash it into the FOTA partition (see TWRP 3 thread for more informations).
DEPRECATED: Patched kernel - You can use those kernels on most Marshmallow and Lollipop based primary ROMs to add kexec boot support.
Be aware that those patchers will be updated when possible after kernel sources updates
Kexec support no longer required thanks to the no-kexec workaround by nkk71.
For convenience reasons, I enabled the workaround by default if kexec is not found.
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.
Recommended values are :
Cache : Keep default value
Data : Minimum 4000
System : 1000 is enough for most installs
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. 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 don't know how/don't know where to find out how, you probably should not try installing MultiROM.
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, so installation of Android to 4Gb image on a pretty fast USB drive takes about 20 minutes maximum.
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.
OPTIONAL: Reflash the kernel patcher to add kexec support
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.
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 for example kernel, which is distrubuted as whole boot.img (eg. franco 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 - I believe these are obvious
- 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 developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
MultiROM - https://github.com/AdrianDC/multirom_core (branch master)
Modified TWRP - https://github.com/multirom-dev/Team-Win-Recovery-Project (branch master)
Device Tree - https://github.com/XperiaMultiROM/android_device_sony_huashan (branch master)
MultiROM available for Huashan also thanks to :- [MENTION]Tasssadar[/MENTION]
- The XperiaMultiROM team
- The MultiROM HTC team
- [MENTION]Arvind7352[/MENTION]
- [MENTION]nkk71[/MENTION]
XDA:DevDB Information
MultiROM for Xperia SP, Tool/Utility for the Sony Xperia SP
Contributors
Adrian DC
Source Code: http://forum.xda-developers.com/google-nexus-5/orig-development/mod-multirom-v24-t2571011
Version Information
Status: Stable
Created 2016-04-03
Last Updated 2017-06-07
Reserved
Downloads
1. Main downloads
Xperia SP (Huashan): https://mega.nz/#F!mpMATaJa!gGshpOwYueKdK0bu6YSNUg
MultiROM: multirom-2017MMDD-v33x-device.zip
Modified recovery (based on TWRP 3): multirom-2017MMDD-recovery-fota-device.zip
OPTIONAL: Kernel w/ kexec-hardboot patch (msm8960t Marshmallow based): kernel-2016MMDD-device.zip
If used, kernel with kexec-hardboot patched needs to be only in your primary ROM!
No longer required thanks to the no-kexec workaround.
OPTIONAL: MultiROM installed as a secondary "ROM": multirom-2016MMDD-recovery-secondary-device.zip
Mostly meant to be used for Stock ROMs users and devs. Only use as secondary ROM to flash.
2. Third-party kernels with kexec-hardboot patch
* None, and do not use any that would have it until the kernel is ready
Nicely ask your kernel developer to merge kexec-hardboot patch.
3. Uninstaller
MultiROM uninstaller: Unavailable due to the already considerable SONY ELF format port
Reflash a ROM or a boot.img without injection (or the v33x zip) to remove MultiROM bootimage from your device.
Then delete the "multirom..." folders from internal & external storages.
If you don't want MultiROM menus in recovery, re-flash a normal TWRP, but it is not needed,
those menus don't do anything if MultiROM is not installed.
How to install for the first time
Flash the 2 MultiROM zips as explained
Reboot to the FOTA Recovery (Volume +)
In MultiROM TWRP, Add a ROM, set everything properly
Wait for the ROM to be installed (can take a while)
In MultiROM screen, choose the ROM location
For the concerned ROM, "Flash zip" for wished zips (GApps, SuperSU, Addons...)
Reboot the phone
Changelog
Code:
MultiROM v33x - TWRP 3.2.1 - 21/01/2018
=========================================
* Merged TWRP 3.2.1 updates into MultiROM TWRP
* Improvements for Android 8.1 support
* Improvements [URL="https://www.xda-developers.com/rest-in-peace-xda-recognized-developer-nkk71-has-passed-away/"]made with nkk71, RIP[/URL] >> [URL=https://www.xda-developers.com/rest-in-peace-xda-recognized-developer-nkk71-has-passed-away/#comment-3719128510]Comment[/URL]
MultiROM v33x - TWRP 3.1.1 - 01/11/2017
=========================================
* Improvements for Android 8.0 support
* Improvements for SDCardFS support
* Improvements from secondary ROMs handling
* Changes on the boot UI's Android ROM icons
MultiROM v33x - TWRP 3.1.1 - 07/06/2017
=========================================
* New implementation to handle external boot
on Ext4 / F2FS MicroSD or USB Drive in order
to allow access to the external storage for media,
through the storage 'external_multirom' path
MultiROM v33x - TWRP 3.1.1 - 17/05/2017
=========================================
* Include all recent improvements from TWRP 3.1.1
MultiROM v33x - TWRP 3.1.0 - 03/05/2017
=========================================
* Upstream updates from recovery and sources
* Fix for the offline charger detection mode
MultiROM v33x - TWRP 3.1.0 - 12/03/2017
=========================================
* Include all recent improvements from TWRP 3.1.0
MultiROM v33x - TWRP 3.0.3 - 05/03/2017
=========================================
* Built in a clean new tree of Android 7.1.1 (replaces 6.0)
* Multiple fixes to support 7.1 changes
* Include all recent improvements from TWRP 3.0.3
* Fix the 7.1 busybox cpio corruption, needed for MultiROM
MultiROM v33x - 18/12/2016
======================================
* Minor improvements of MultiROM
* Improved versioning with header showing build date
* libbootimg changes from my recent updates
MultiROM v33x - 17/10/2016
======================================
* Improve autobooting to external ROM (MicroSD / USB)
MultiROM v33x - 18/09/2016 - 24/09/2016
======================================
* Updated to no-kexec workaround v4 by nkk71
* Autoboot accessible for external / MicroSD
MultiROM v33x - 16/08/2016
======================================
* Add support for the new ramdisk structure with init.real
MultiROM v33x - 14/06/2016 - 15/07/2016
======================================
* Support for hardware keys (Volume +/- & Power)
MultiROM v33x - 06/06/2016
======================================
* Support for Stock SONY ROMs added
MultiROM v33x - 23/05/2016
======================================
* MultiROM UI dimensions completely fixed
* Access to MultiROM color themes and Shutdown
MultiROM v33x - 11/05/2016
======================================
* Support for no-kexec workaround to boot ROMs
MultiROM v33x - 15/04/2016 - 09/05/2016
======================================
* Improved UI with unified Internal / External ROMs in one tab
MultiROM v33x - 03/04/2016
======================================
* Initial release with full SONY ELF port and dual ramdisk support
Kernel patchers :
Code:
23/04/2016 - 06/06/2016
==========================
* Updated to latest sources, standalone kernel without modules
* Deprecated, releases abandoned.
06/04/2016 - 15/04/2016
==========================
* Updated to latest CM-13.0 & CM-12.1 stable kernel status
03/04/2016
==========================
* Initial huashan release, unstable kernel for the moment
Recent ROMs tested so far :
Code:
LineageOS 14.1 : OK (Primary & Second)
AOSP 7.1 : OK (Primary & Second)
AOSP 7.0 : OK (Primary & Second)
CyanogenMod 12.1 : OK (Primary & Second)
CyanogenMod 13.0 : OK (Primary & Second)
CyanogenMod 14.1 : OK (Primary & Second)
AICP Marshmallow : OK (Primary & Second)
AOSP-CAF Marshmallow : OK (Primary & Second)
AOSP-OMS Marshmallow : OK (Primary & Second)
AOSP-RRO Marshmallow : OK (Primary & Second)
Sony 4.3 based ROMs : Normally OK (Primary & Second)
eXistenZ Ultra 4.0.0 : OK (Primary & Second)
Warning : If using old ROMs as secondary, primary ROM
should not have F2FS filesystems for Data and Cache
Other ROMs : To confirm & report here
Reserved
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.
Why is my USB connection to computer not detected ?
Uncheck the "Enable ADB" option in MultiROM Settings.
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.
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.
The installation fails with "trampoline not found -1"
Often the issue appears because the ROM zip has a nested zip for rooting methods.
Best solution is to remove the root zip from the ROM and flash it separately later.
Something wrong happened, I lost something or it's really laggy
You have been warned about making backups & the fact this is more experimental than stable.
You alone will be responsible for loosing data or having an usable ROM when you really needed it.
Everyone in this thread will try to help you, but we can't do backups of your data ourselves.
Thanks for your understanding, remember to read the previous comments and please try to help each other.
Current local manifest of the MultiROM build
Code:
<!-- https://github.com/AdrianDC/multirom_development_sony -->
And no, this is not an april fools joke.
Clicking on that link for patched kernel, opens a google search page which shows links for AK kernel, is that what we're supposed to use??
STUPID QUESTION. NEVERMIND.
Whaaat ?
What the F#?+ !
Thank you thank you thank you.
Thats all i say !
WTF?! OMG! Thank you so much adrian!
Adrian >> Harry Potter
Sent from my Xperia SP using XDA-Developers mobile app
For People Using this MOD:-
Follow the Instructions carefully and try reporting which ROMs work with it. This would reduce Adrian's effort to list bootable ROMs. Hope almost all of the ROMs boot.
Congrats @Adrian DC :laugh: :highfive:
Thanks to AdrianDc
I've installed the cm-13.0-20160329 beside my AICP 10 (Lollipop).
Great! Please try to fix for .207
P.S. Remains only wait DT2W from you
-Mr.freeze- said:
Great! Please try to fix for .207
P.S. Remains only wait DT2W from you
Click to expand...
Click to collapse
Dont rush him or he'll personally send a assaniation pigeon from the other side of the world to your home
Primary: CM12.1 unofficial works great
CM13 Works great too
CM11 bugyusz didn't boot (because it use stock kernel)
AICP Works great
Sent from my Xperia SP
Furrydaus said:
Dont rush him
Click to expand...
Click to collapse
I'm not hurry him. This can be called wishes)
I installed cm13 and then wanted to flash AICP10 by twrp 3.0.1 r6, but encountered these errors (see the attached pix please)
desalt said:
I installed cm13 and then wanted to flash AICP10 by twrp 3.0.1 r6, but encountered these errors (see the attached pix please)
Click to expand...
Click to collapse
The rom is successfully installed. Nothing to worry about. I had also some days ago that error but the roms booted without a problem.
Sent from my A0001 using Tapatalk
darjwx said:
The rom is successfully installed. Nothing to worry about. I had also some days ago that error but the roms booted without a problem.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
tanx, but the Multirom menu doesn't appear and I have no choice to select AICP, moreover in the recovery there isn't any secondary ROM.
would you please see the following attached pix? do you see anything wrong?
the first one, says something (in mount menu) after failure in flashing the second rom.
and from the 2nd one, I guess my SD card is locked.
.
desalt said:
would you please see the following attached pix? do you see anything wrong?
Click to expand...
Click to collapse
First : Accept & set it to never ask again, it's ok.
Second : No. All storage devices are "block" based, doesn't mean anything related to the MicroSD being locked.
About old ROMs : No yet support nor known to work one day,
I'll get back to it soon enough but nothing sure yet.
Finally about latest CM12.1 / CM13 Beta releases : The newest MultiROM kernel patcher
can freely be used to test both ROMs as it has been updated to the same state.
I installed the proper Gapps for both cm12 and cm 13 without any problem when they were single Roms on my phone. but when I try to install each of them beside the other one as a secondary Rom , face to an error and installation process fails.
[ROM][UNOFFICIAL][6.0.1][E6653/E6603] CyanogenMod 13 for the Sony Xperia Z5 [ALPHA]
{
"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"
}
CyanogenMod 13 for the Sony Xperia Z5 E6653 and E6603
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase
performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be
used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps).
CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Before you start
This ROM is only for the E6653 and the E6603
Code:
*
* Your warranty may be voided !
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
Special Thanks
@CTXz for getting the ball rolling on CyanogenMod for Z5 series and stemming the lion's share to get this working
@oshmoun for providing fixes ASAP
@AndroPlus for providing a great kernel that works with many recoveries
@moonbutt74 for reminding me that smashing your device can provide a solution
@sub77 for teaching me how to work with QCOM (I was on exynos before)
@Joeisgood99 for providing a solid working TWRP-3.0.0.0 build until we had our own
@bazhip for providing a well working twrp 2.8.7.0 for restoring until we had our own
@alphatact1cs has a great overview on lots of topics for the Z5 device family
@auras76 for his great Custom ROM
@infected_ for his experience
Thanks to @mpro420 for help to get Viper4Android working !
Thanks to @jimRnor for Project DiVA SoundMod !
The Sonyxperiadev team for releasing their sources to the public
SonyAOSP team
SonyCM team
Sony Xperia (community) devs
And ofcourse the entire CyanogenMod team!
(Known) Issues
Video Recording
Bluetooth (keeps restarting) (might be fixed, needs feedback + testing)
Camera Colors (can be circumvented by using specific apps CameraNext Mod )
Camera Focus & Sharpness (driver issue, probably since it uses Xperia Z (original) drivers but different lenses ?)
Camera lowlight pictures (might improve with release of Sony's "Experimental AOSP Camera" for the Z5 series, porting of other Framework + Stock Cam app; partially needs DRM magic)
Camera Focus (even with VCM2 actuator changes focus is still kind of murky)
Fingerprint sensor (might work depending on build date of ROM)
Lag after booting up device (Will resolve: lock screen after boot and waiting a few seconds)
Long bootup times & less smoothness with "stock" (prebuilt) kernel
What can not be fixed, changed - aka WONTFIX - NOTOURPROBLEM
There might be potential speed issues with Class 10+ microSD cards not properly being "tuned", in that case switch to slower cards or RMA it which should hopefully solve it. There is a possibility to force slower speeds on cards but that is not really the optimal solution with ultra speed cards and needs further investigation. Samsung (EVO/EVO+) cards, Transcend cards and a few others UHS-I(+) and faster are affected.
What has been Fixed
Horizontal color lines and color glitches during bootup
Gapps
Sudden Lag after some time
NFC
Odd calling numbers
In-call mic
Sound on calls
Camera button
Microphone
Thermal regulation
Red flashy frames
RIL (SIM detection)
Dex pre-optimization
Camera
Sensors
Crash after locking device
microSD access
Flash light / Torch
Full brightness (should be fully working)
Gapps (permissions issues) [occurs occasionally and should be circumvented by full-wipe approach (incl. internal storage)
Hang/Loop during boot stage (should be circumvented by full-wipe approach (incl. internal storage)) (use Custom Kernel, under investigation)
High battery drain [~ 10%-20% per hour] when dirty-flashing system (fastboot -S 256M flash system system.img), make sure to have data backed up, then format /data ; OTA updates should be fine though [need feedback] ); causes are: dirty flashing, certain apps, ROM issues, etc.
Guides/Instructions
Unlocking Bootloader
Warning! The following procedure may void your warranty and will wipe EVERYTHING
Visit Sonys Official Bootloader Unlock guide (Details to all the risks you are taking are located on their site)
After Unlocking your bootloader you can proceed with the next steps
Steps on how to Fastboot, Flashmode, Recovery, Emergency/Force Poweroff
@alphatact1cs has a great overview on lots of topics for the Z5 device family
over at [GUIDE] Sony Xperia Z5 - UNLOCK / ROOT / TWEAKS - OS 5.1.1 / 6.0
There go to the [GUIDE] StockROM section , open it up and under #GENERAL you'll find everything you need to know.
Setting up fastboot and how to use it
For windows users
Please checkout this guide on how to use fastboot on windows
If you prefer to keep a low footprint instead of installing the whole Android SDK, take a look at its thread
[TOOL]Minimal ADB and Fastboot [8-28-15]
For Linux users
Installation
Debian based distros (Debian, Ubuntu etc.)
Open a terminal and enter the following :
Code:
sudo apt-get update && sudo apt-get install android-tools*
Confirm the installation by either hitting enter or typing y
Gentoo based Distros (Gentoo, Funtoo, Sabayon, Scientific Linux)
Once you're in a terminal, enter the following:
Code:
emerge dev-util/android-sdk-update-manager
Other distros (Arch, Fedora, Open Suse etc.)
Please find the apropriate packages to install android fastboot tools for your distro
How to use
Open a terminal in the location your .img file is located or cd into that directory like this:
Code:
cd <path to your directory that contains the .img files>
Replace <path to your directory that contains the .img files> with your actuall path
To boot temporarely into a .img (ex recovery) use the following command (replace <your.img> with your .img file) :
Code:
fastboot boot <yourfile>.img
To flash a kernel image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash boot <your.img>
To flash a recovery image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash recovery <your.img>
To exit fastboot enter :
Code:
fastboot reboot
How to install CM 13
Above all - do a Backup of ALL your data
When I write ALL I mean ALL (this includes the data on your micro SD card,
don't come whining to me if you lose your wedding photos/videos, kids' photos/videos or other important stuff !
For optimal experience I'd recommend my built custom kernel (quicker boot times, higher reliability, more tweakability)
General, in-depth instructions
Download one of the newer Z5 AndroPlusKernels v20+ by @AndroPlus from his official website (Scroll down and select Z5, then on AndroidFileHost search for Z5_AndroPlusKernel_Permissive_v2 (v20 - v23) and download it)
Extract the flashable zip-file e.g. Z5_AndroPlusKernel_Permissive_v23.zip
Download our TWRP 3.0.1-0 build for the Z5)
Download the appropriate gapps from below (Can be downloaded on your device)
Download the CM 13 Zip for the Z5 from below (Can be downloaded on your device)
Move the GAPPS zip and the CM 13 to your Z5 if you haven't downloaded them on your device
Power Off your Z5 and wait about 10-15 seconds to make sure it's off
To enter fastboot mode hold VOL UP and while holding VOL UP connect your device to your pc via cable
When the notification LED has turned blue you are in fastboot mode
On your PC flash the boot.img that has been extracted from the Z5_AndroPlusKernel_Permissive_v23.zip using fastboot (
Code:
fastboot flash boot boot.img
)
Now flash twrp-3.0.1-0-E6653-20160403.img by using fastboot (
Code:
fastboot flash recovery twrp-3.0.1-0-E6653-20160403.img
)
Once both of those images have been flashed you can reboot the device like so:
Code:
fastboot reboot
Quickly pull the usb cable from the computer (you can leave the other end in the phone's port)
When booting up wait for the notification light to turn yellow at the Sony logo
Once it has turned yellow, you will enter TWRP by pressing VOL UP (or VOL DOWN - up works more reliably)
If you've missed the step above, reboot your device and try the step above again
Alternatively you can force turn off the device via: Power Button + Volume Up , then turn it on again via Power Button
If TWRP asks you to enable read and write, swipe to continue
Go to settings and lower the max brightness to the minimum or one of the lower levels to preserve energy
In TWRP make a full backup to the microSD in case you want to revert back to stock.
After it has finished, in this case Reboot -> System.
Copy over the TWRP folder from the external microSD to your computer (reason: you might not have access to your external SD or have to reformat it
Thank Microsoft, Sony, etc. for that: "Stock" ROM uses texfat , AOSP, CM, etc. uses exfat, ext4, ntfs
The files on the microSD might get corrupted (filesystem problem) or the microSD going crazy (I already had both cases)
Now Power on your phone and follow the steps again to get into TWRP
Swipe to continue (?)
select Wipe > Advanced Wipe
Now ONLY tick Dalvik/ART cache, System, Cache and Data
WARNING! THE NEXT STEP WILL WIPE YOUR SYSTEM AND DATA, MEANING YOU WILL DELETE YOUR STOCK SONY SYSTEM AND ALL YOUR APPS
(You already DID a Backup of your files so nothing to worry about)
Once you've ticked the correct boxes, swipe to wipe
Once the wipe is complete, return to the main menu and select Install
Locate and select your CM 13 Zip
Select "Add more Zips" and add your GAPPS package and finally swipe to install
Once the installation succeeded you can select "Reboot System"
Wait for CM 13 to boot up (Can take several minutes)
Enjoy CM13
OPTIONAL: You can remove your TWRP backup that is located in the TWRP folder if you feel like you will no longer need it
How to ROOT
In CM 13, enable the developer options
Select Root access
Select Apps Only (Or Apps and ADB if you use ADB)
Done
How to disable the Thermal Manager
Before we start I want to set a few questions and warnings. Disabling the thermal manager will cause you device to run slightly hotter, do this at your own risk.
Let's start out with why you would want to disable the thermal manager. At this point it's not recommended to disable the thermal manager as it has been fixed. However some people still want the max performance out of their device. The average heat without the thermal manager will be roughly the same, if not less compared to the stock ROM with it's thermal manager enabled.
So why is the thermal manager even included if it the device runs mostly fine without it. As most of you already know, the Snapdragon 810 (MSM8994) has overheating problems. The first CM boot after flash is responsible for optimizing apps and android and can become extremely resource hungry at that point. Due to that, the device can heat tremendously! Not only can that cause a panic reboot but it can also damage your device in rare cases. To avoid that issue a thermal manager shrinks down process and slowers the boot animation (That's why the CM logo may lag at first boot).
Enough said, let's get going..
To disable the thermal manager you must do the following :
First enable root access (See "How to ROOT" guide)
Open the CM file manager
Go to settings > General Settings > Access Mode
Select root acess mode
Go back to the file manager
Swipe from left to right or press the menu button in the upper left corner
Select Root folder
Open the folder/directory called etc
Delete thermanger.xml
Reboot
Done
How return back to stock via TWRP backup
Reboot your device
Wait for the notification light to turn purple at the Sony logo
Once it has turned purple, you will enter TWRP by pressing VOL UP or VOL DOWN
If you've missed the step above reboot and try again
If TWRP will ask you to enable read and write, swipe to continue
In TWRP select restore and select your backup, then swipe to restore
Once the restore is done you can select "Reboot System"
If your device hangs at the Sony wave boot animation, force shut down and power your device up again.
Downloads
Latest recommended CyanogenMod release for the Sony Xperia Z5 E6653/E6603 :
6.0.1_13.0-20160626-UNOFFICIAL-sumire_r46_alternate
Latest recommended Kernel for the CM release for the Sony Xperia Z5 E6653/E6603 :
6.0.1_13.0-20160626-UNOFFICIAL-sumire_r46_alternate
All my releases can be found here on : Android File Host
TWRP for CM/AOSP-based ROMs:
[TWRP][E6653/E6603/E6633/E6683] 3.0.2 , for CM/AOSP ROMs
Gapps (Select ARM64 > 6.0) :
Open Gapps
[GAPPS][6.0/5.1/5.0][arm/arm64] Official Slim GApps ( recommended )
XPosed for Android:
[OFFICIAL] Xposed for Lollipop/Marshmallow (Installer in Thread)
XPosed Releases
SuperSU in SystemMode:
SuperSU in System-Mode [v2.65-STABLE] [v2.68-BETA] [v2.70-WIP/BETA-RC]
Sound MODs:
[Sound Mod ][Project DiVA][6.0 MM_Z5 series] KitaKami sound mod Prototype 01 (any effect ?)
A.R.I.S.E. Sound Systems - Auditory Research in Sound Enhancement - Exodus RC8.3 (works (RC8.3))
[SOUNDMOD][JB/KK/LP/MM]Project Yume Final, You are the Legend (needs testing)
[SUPER MOD][4.4+/6.0/N][ v7.5.2 ] XTREMEMusic™ THE SOUND THAT YOU'VE NEVER HEARD! (NOT working (7.4), needs testing of 7.5*
[Audio Mod] eXtremeBeats Aural Maximizer (needs testing)
[APP]Material ViPER4Android 2.4.0.1[Light/Dark][LP/MM]
mpro420 said:
1.)zip file install via twrp.
2.)reboot to system.
3.)enable v4a "write to sdcard" permission in setting/apps/viper4android/permission.
4.)open v4a and gain root permission.
5.)install driver for v4a.
6.)reboot system.
7.)[emoji39]
Click to expand...
Click to collapse
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Requests for other devices
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions or requests usually by the same user
Requests that are out of CM's framework (Ex. Adding Sony Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Source Code
All Source Code can be obtained from:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
Kernel Source code can be obtained from : zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
We gladly accept any developers that are willing to contribute to this project! Please PM @CTXz if you are interested in joining this project!
Build from Source
http://forum.xda-developers.com/xperia-z5/general/guide-build-cm13-source-z5-z5c-z5p-t3357040
Screen Shots (Z5 compact)
XDA:DevDB Information
CyanogenMod 13 for the Sony Xperia Z5 E6653 and E6603, ROM for the Sony Xperia Z5
Contributors
CTXz, Moonbutt74 , zacharias.maladroit , oshmoun , infected_
Source Code:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: 6.0 Recommended
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-04-11
Last Updated 2016-06-28
Changelog
Code:
2016/05/06
[LIST]
[*]Dual SIM support (ROM) [COLOR="Red"][B][WIP][/B][/COLOR]
[*]Dual SIM support (Kernel) [COLOR="Red"][B][WIP][/B][/COLOR]
[*]smoother brightness (automatic & manual), lower default and manual brightness
[*]weather provider support (CM)
[*]thermal manager improvements (CM)
[*]potential stability-fixes (CM)
[*]brightness dimming disabled (once temperature raises)
[*]VCM2 camera actuator (presumably working focus) == feature complete camera [LED torch still needs work]
[*]adb enabled from the start (diagnostics at this early ROM stage)
[*]upstream ROM + Kernel changes
[*]
[*] Sim-specific change: add DSDS (dual sim) detection script that starts second ril-daemon
[*]
[*] Custom Kernel changes:
[*] Intelliplug + Intellithermal by default [[B][COLOR="Red"]stability testing[/COLOR][/B]]
[*] added Quick Wakeup, PowerSuspend,
[*] added AdrenoIdler
[*] CPU and general Kernel optimized compiler flags
[*] re-enabled efficient WorkQueue [[B][COLOR="Red"]stability testing[/COLOR][/B]]
[*] re-enabled nop idle governor for CPUIDLE driver [[B][COLOR="Red"]stability testing[/COLOR][/B]]
[*]
[/LIST]
2016/04/19
- LiveDisplay (CM upstream) should work more reliably and should not cause instabilities and (boot)loops anymore
- torch should work now (ROM)
- changes, improvement to Bootup (Kernel side) - should make prebuilt kernel more reliable
2016/04/17 [suzuran]
- Fixed Brightness
- Fixed Torch
- Fixed Double Tap 2 Wake
- Added CPU core optimization
- Added USB gadget support
- Synced with the latest CM sources
-----------------------------------------------
* For devs
- Added Kitakami patcher to manifests
2016/04/15
- Full brightness range + maximum brightness (ROM + Kernel)
- KCAL support (Kernel)
- alucard, elementalX, zzmoove governors (Kernel)
- upstream sync (Kernel), perhaps better, more reliable WiFi
- more battery efficiency during video playback (Kernel), [needs testing, lags ?]
- adreno (GPU) governor, lower default frequency (Kernel), perhaps lower battery consumption, [needs testing, lags ?]
- vibrator intensity control (Kernel) [needs testing]
- some more battery efficiency tweaks (Kernel)
- NTFS, exFAT filesystem support (for microSD) (Kernel)
- tweaks and reliability improvements (Kernel)
- Driver wakelock control (Kernel)
- NEON/FPU compiler optimizations (Kernel)
- improved Hotplug reliability and stability (Kernel)
2016/04/12 [suzuran]
- Fixed sdcard recognition
- Updated binaries to v4
- Released CM build guide
- Synced with newest sources
2016/04/11
- CM 13 For the Z5 E6653 Released
2016/04/10
- CM 13 For the Z5 Premium E6853 Released
2016/04/05
- Fixed GApps
- Partially fixed Bluetooth
- Synced to latest CM sources
2016/03/27
- Fix thermal manager lag
- Fix NFC
- Updated kernel configs
- Added ffmpeg codecs support
- Synced with newest CM sources
-------------------------------------------
* For devs
- Cleaned up suzuran and satsuki tree
- > Moved common media configs to kitakami common tree
- > Moved acdb files to vendor tree
2016/03/24
- Fix In-call Mic
- Add support for the E5803
- Add option to boot into recovery (On purple LED at Sony logo press VOL UP or VOL DOWN to enter recovery)
- Update Thermal manager
- Merge latest AOSP kernel commits
- Sync to newest CM source
2016/03/22
- Fix microphone
- Add settings for camera button
- Add settings for volume rockers
- Fix sound on calls
2016/03/20 - RIP TonyStark, you were a great moderator and we'll all miss you.
- Added Thermal regulation to avoid overheating problems
- Fixed Red flashy frames
- Fixed RIL (SIM detection)
- Fixed Dex pre-optimization
- Fixed Camera
- Fixed Sensors
- Fixed Crash after locking device
2016/03/18 - CM 13 For the Z5 Compact E5823 Released
Reserved 02
Reserved 03
(and another one)
You know the drill:
the most important part is the phone functionality (well, it's a smartphone ),
please test that after you've done the initial set-up and tell, whether it works
Finally get there....
Great job man!
Hope there will be dual sim support asap.
Nice jobe, I'll wait for a more stable version to test it
keep up the good work
best regards.
Well done again to Sony Kitakami Developer Organization!
Sooooo much time and effort represented in those CM13 github projects. Total Respect.
Nuf said.
JerryLaiHMmmmmm said:
Finally get there....
Great job man!
Hope there will be dual sim support asap.
Click to expand...
Click to collapse
I've taken a look but haven't figured out yet on how to make it work,
if there are any developers out there with DSDS (dual sim) devices, interested on getting this working and read this - please take a look at it
Thanks !
korom42 said:
Nice jobe, I'll wait for a more stable version to test it
keep up the good work
best regards.
Click to expand...
Click to collapse
Okay
Thanks
Joeisgood99 said:
Well done again to Sony Kitakami Developer Organization!
Sooooo much time and effort represented in those CM13 github projects. Total Respect.
Nuf said.
Click to expand...
Click to collapse
Thanks ! <3
Will you be making a guide on building this rom from source? And of course, thank you for all your hard work we all greatly appreciate it.
Uclydde said:
Will you be making a guide on building this rom from source? And of course, thank you for all your hard work we all greatly appreciate it.
Click to expand...
Click to collapse
Very soon mate
Uclydde said:
Will you be making a guide on building this rom from source? And of course, thank you for all your hard work we all greatly appreciate it.
Click to expand...
Click to collapse
Build from Source
The guide on how to build your own Z5 ROM will be posted once we feel like this ROM is ready enough
Click to expand...
Click to collapse
Take a look at the source and the repos, the guides are out there ...
... you got a PM
CTXz said:
Very soon mate
Click to expand...
Click to collapse
beat me to it
zacharias.maladroit said:
[ROM][UNOFFICIAL][6.0.1][E6653/E6603] CyanogenMod 13 for the Sony Xperia Z5 [ALPHA]
if you loose your wedding photos/videos,
Click to expand...
Click to collapse
If it's "loose", put some glue on it!
lol
m3ta said:
If it's "loose", put some glue on it!
lol
Click to expand...
Click to collapse
lol - I get those mixed up quite a bit, sometimes due to typos, too
Status Update:
Uploaded new img files and a flashable zip-file for TWRP (haven't tried it out myself, currently evaluating Resurrection Remix)
Sorry for the inconvenience so far
Give it a try, if you dare
Okay, so I followed the steps for "General installation", and the rom is surprisingly smooth. The only issue I've noticed that isn't addressed in the original post is that vibration intensity is WAY higher than in the stock rom. Like it's actually pretty loud. I know it's a minor issue compared to some of the other things, but I'm just throwing that out there. I'll point out anything else I find.
Absolute legend! Thanks man. I'll get to testing once i get home off this drilling rig
Uclydde said:
Okay, so I followed the steps for "General installation", and the rom is surprisingly smooth. The only issue I've noticed that isn't addressed in the original post is that vibration intensity is WAY higher than in the stock rom. Like it's actually pretty loud. I know it's a minor issue compared to some of the other things, but I'm just throwing that out there. I'll point out anything else I find.
Click to expand...
Click to collapse
Thanks for testing
Actually it already was higher on AOSP, if recall correctly, but I'll ask the other devs if they noticed something out of the ordinary
Thanks
atanu89 said:
Absolute legend! Thanks man. I'll get to testing once i get home off this drilling rig
Click to expand...
Click to collapse
Thanks
Thanks for this great rom, the only problem i encounter is that my phone keeps stuck in first startup (cyanogenmod logo) and that keeps going i force my phone to switch off after 45 minutes, is there something i do wrong i followed the in depth guide
Sovjet-Command said:
Thanks for this great rom, the only problem i encounter is that my phone keeps stuck in first startup (cyanogenmod logo) and that keeps going i force my phone to switch off after 45 minutes, is there something i do wrong i followed the in depth guide
Click to expand...
Click to collapse
That partially is caused by the "stock" built kernel,
you can see whether is improved by flashing my custom kernel.
One observation (according to @moonbutt74 afaik) led to the conclusion that the upstream (from sonyxperiadev) setting of coherent_pool=8M doesn't match with Sony's ("Stock ROM") setting of coherent_pool=2M,
and does no good for startup time (and reliability ?).
Another factor (like in most AOSP-based ROMs, Kernels) is that the kernel was built with a less tuned toolchain (gcc),
can't directly explain though why does leads to exactly that behavior.
Tl;dr:
Give the custom kernel a try - the "stock" kernel should work but for some reason sometimes it does not
custom has exfat + ntfs support to make microSDs work reliably and other things
Thanks
Thread template from CosmicDan's thread.
About
This is a TWRP Installer ZIP and bootable IMG with extra capability such as Treble-izing and other power-user tools with integrated TWRP-powered submenus that CosmicDan originally called Tissot Manager.
Few months ago, CosmicDan officially decided to leave Tissot development, and his twrp was stuck on 3.2.3. So I decided to update that to 3.3 and convert all the aroma stuff into TWRP-powered menus etc, in order to preserve better future compatibility.
HIGHLY recommended reading and guide for everyone new to Treble - [TREBLE][GUIDE] From Stock to Treble - everything you need to know! by CosmicDan. It also has some general protips hidden within there, for example the seamless/slot system interactions and nuances, so it's worth reading for anyone who wants to be a master of the Android flashing domain
Features:
TWRP fully Treble-ready based on 3.3.1-0;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
Full USB-OTG support;
Full MTP support;
Optional TWRP Survival function, that works both in hotboot and real recovery;
Optional Active slot install method, selectable right before the zip flash;
Option to ignore Payload<>Recovery certificate failures (fix for newer LOS-based ROMs);
Added a Tissot Manager list item under Advanced Menu, totally built-into TWRP itself that allows you to do:
Has the option to shrink Userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
Treble-izing will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Adds a "Patches" section with the following current options:
Patch kernel from Enforcing to Permissive and vice versa
More features coming!
All of this info is detailed inside the Tissot Manager GUI.
See screenshots in post 2.
Since this is an early version (still stable), some original features from 3.2.3 are still not available. I'll do my best to constantly add new functions when possible!
Instructions
Optionally boot the boot-recovery.img to get a temporary TWRP if you don't have it installed, unzipped from TWRP-3.3-withTM-BOOT.zip
Code:
fastboot boot boot-recovery.img
Warning - do not EVER flash this img - hotboot it only.
Flash the TWRP Installer. Any slot, any ROM, any existing Recovery - it doesn't matter - it will be installed to both slot kernels.
Reboot Recovery
Optional - Use the "Advanced > Tissot Manager" option for repartition options and other advanced ROM patches, this time built-in TWRP itself for better compatibility with future versions.
About TWRP survival
Starting from 1.0, TWRP Survival will be able both in hotboot mode 'n real recovery mode. Just tick the checkbox 'n flash!
Download
All downloads (and source code) always at:
https://github.com/Giovix92/twrp_device_xiaomi_tissot/releases
Additional sources not able to be listed in DevBB:
Modified update_engine: https://github.com/Giovix92/android_system_update_engine
What's next?
See [TREBLE][GUIDE] From Stock to Treble - everything you need to know! by CosmicDan for detailed instructions and learning on how to Treble like a pro.
FAQ
Q) After I flash TWRP, I get kicked into a Recovery loop when trying to boot the ROM!
A) This is probably because you have a kernel that does not disable dm-verity. To fix this, flash Magisk.
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes! In fact, this is the easiest way for using stock ROM on Treble repartition. May also require a custom kernel with dm-verity disabled (see Questions above regarding fastboot kick and recovery loop).
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM. This may occur while flashing in the active slot.
Q) What "Inject TWRP after install" option does?
A) It's TWRP Survival. If you check that checkbox, then after the installation of your zip file the TWRP will automatically reinstall TWRP into your slot.
Bugs Report
If any bug/problem may occur, feel free to report it here! Explain the problem and attach the recovery log. You can get it by going to Advanced - Copy Log and sliding. Kernel log isn't necessary.
If, for some strange reasons, you are unable to get into that menu', connect your phone to PC, open up CMD (aka command prompt) and type:
Code:
adb pull /tmp/recovery.log
Credits and Thanks
- @CosmicDan for tips, helps and his amazing work on TWRP 3.2.3, which I've taken many things from
- @nicknitewolf for his DT
- @chondoe for always being present in testing and reporting bugs/good news
- @flex1911 for DT stuff
- @mauronofrio for inject twrp function
XDA:DevDB Information
TWRP 3.3.1-0 with Tissot Manager, ROM for the Xiaomi Mi A1
Contributors
Giovix92
Source Code: [url]https://github.com/Giovix92/device_xiaomi_tissot[/URL]
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-10-01
Created 2019-10-01
Last Updated 2019-10-01
Reserved
Changelog:
**10-11-2019**
- Fixed error 28 and 13, this led to some issues while doing a clean installation.
- Restored active slot install functionality, now it's fully working.
**18-10-2019**
Version: 2.0 (MAJOR UPDATE)
- Fixed all kind of problems while flashing:
- Error 51, 15, 31, 17, 35 (postinstall)
- Unability to make a clean flash
- Removed changelog section from Tissot Manager
- Added ADB God Mode
- Added missing binary, required in order to let selinux changer work properly
- Now the 2 new checkboxes won't stay checked anymore after any zip install
- Added system remount to r/w after zip flash in order to flash multiple zips in the same recovery session (like ROM + magisk + gapps and then reboot)
- Fixed linker problem that was causing some options in Tissot Manager to fail
- Smoother experience
Older changelogs:
**01-10-2019**
Version: 1.0
- Initial release with Tissot Manager, now powered by TWRP
- Optional TWRP Survival
- Ability to install into same slot
- Ability to repartititon to Treble and vice versa
- More features coming!
Reserved
Great work.
Sent from my Mi A1 using Tapatalk
Thanks ??
Nice. Bro you carried legacy ?
nice work waiting for shrp version of this ??
Noice :good:
Sent from my Mi A1 using XDA Labs
This is an update of TWRP Comic Dan?
manchirua said:
This is an update of TWRP Comic Dan?
Click to expand...
Click to collapse
Read op
Any way to flash it using cosmic dan's twrp? I don't have any pc now
Anikur Rahman said:
Any way to flash it using cosmic dan's twrp? I don't have any pc now
Click to expand...
Click to collapse
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Great job dude ?
Awesome work!
Thank you so much for this.
@Giovix92
Great Job.
Is there a way to show the current slot status like in CosmicDan's ?
sdeft said:
@Giovix92
Great Job.
Is there a way to show the current slot status like in CosmicDan's ?
Click to expand...
Click to collapse
You can check current slot from reboot menú.
Where is the survival checkbox??
What is this "inject twrp" does ?
oskrprez said:
Where is the survival checkbox??
Click to expand...
Click to collapse
Anikur Rahman said:
What is this "inject twrp" does ?
Click to expand...
Click to collapse
That's the TWRP survival option
Unipo said:
That's the TWRP survival option
Click to expand...
Click to collapse
So, Isn't it automatically reinstalled like Comic Dan's version?
Introduction
PitchBlack Recovery Project is Open Source organization founded on 28th March 2018 collectively by the developers from different countries with an aim to provide the world’s most advanced recovery with better customization’s, themes and features.
Based on TWRP v3.4.0
PitchBlack version: v3.0.0
For Device: Sagit
Changelog v3.0.0:
HTML:
- Bringup 3.0
- Source side changes
- Fully Redesigned UI
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- Flashlight toggle on Lockscreen
- Etc.
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
Click to expand...
Click to collapse
From Fastboot
Extract the Downoaded zip file
Grab the recovery.img from extracted folder
Reboot device in fastboot
Run "fastboot flash recovery recovery.img" from fastboot
Boot into recovery
Click to expand...
Click to collapse
Downloads
Flashable zip
PBRP-sagit-3.0.0-20200728-2256-UNOFFICIAL.zip
Post Installation Instructions
BACKUP YOUR Boot.img BEFORE DOING THIS
Thx
XDA:DevDB Information
PitchBlack Recovery Project, Tool/Utility for the Xiaomi Mi 6
Contributors
trisfaizal, trisfaizal, Reza Adi, Shovon, Manjot Sidhu, Mohd Faraz, Sagar
Version Information
Status: Stable
Current Stable Version: 3.0.0
Stable Release Date: 2020-07-29
Created 2020-07-29
Last Updated 2020-07-29
Reserved
Nice to see new recovery builded on newer version of twrp.
Some little bugs:
- flash light not working (using vol up button and from recovery lockscreen)
- option free sd mb showing info on top of status bar clock
- in polish language some letters not displaying correctly
- button select language on decryption screen and read only screen not working
- on read only screen slider label (mount to modification) not fit in screen
Main function working fine like installing zips, mounting system, decryption, rebooting.
Eselter said:
Nice to see new recovery builded on newer version of twrp.
Some little bugs:
- flash light not working (using vol up button and from recovery lockscreen)
- option free sd mb showing info on top of status bar clock
- in polish language some letters not displaying correctly
- button select language on decryption screen and read only screen not working
- on read only screen slider label (mount to modification) not fit in screen
Main function working fine like installing zips, mounting system, decryption, rebooting.
Click to expand...
Click to collapse
Thx for report, i hope can fix in next build
Any chance for update?
{
"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: E7746
Maintainer/Authors build:@raza231198,
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: Soon™
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
Code:
fastboot flash recovery recovery.img
Flash vbmeta
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Boot into PBRP by
Code:
fastboot boot recovery.img
or
Code:
fastboot oem reboot-recovery
Copy the zip to internal storage
Flash it
Enjoy
Changelog
PBRP Side 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.
Device Side Changelog
Code:
Initial Build
Bugs
-
Code:
adb reboot recovery
or
Code:
reboot recovery
don't use it
Downloads
Flashable zip
Micromax IN Note 1 | E7746 - PitchBlack Recovery Project
PBRP Version: 3.0.0 Maintainer: PBRP Team
pitchblackrecovery.com
Telegram Group: Click Here To Join
Telegram Channel: Click Here To Join
Project Type: Tool/Utility
Project Name: PitchBlack Recovery Project
Additional Contributors: Reza Adi, Shovon, Manjot Sidhu, Mohd Faraz, Sagar
Project status: Stable
Stable Version: 3.0.0
Good job bro
Thanx for this bro
Wow, at least a step towards a custom rom for mediatek phones..
has anyone tried this on micromax in 1? Or if someone has a recovery for it?
shah.meet6338 said:
has anyone tried this on micromax in 1? Or if someone has a recovery for it?
Click to expand...
Click to collapse
Yeah!! I've tired and works Fine
ashish.rasaily said:
Yeah!! I've tired and works Fine
Click to expand...
Click to collapse
Where is the vbmeta.img file?
We
shah.meet6338 said:
Where is the vbmeta.
Click to expand...
Click to collapse
shah.meet6338 said:
Where is the vbmeta.img file?
Click to expand...
Click to collapse
We don't need vbmeta file we only needed recovery.img file...
Thank you for the recovery. While the recovery is for Micromax in note 1 , i tried it on Micromax in 1 and it works successfully.
I ran into an issue where even after flashing the recovery, the phone was booting into stock recovery. But as it turns out i only had to press down volume down+ power key to boot into PBRP.
Also rooted the device by flashing magisk zip and installing magisk managaer app.
shah.meet6338 said:
Thank you for the recovery. While the recovery is for Micromax in note 1 , i tried it on Micromax in 1 and it works successfully.
I ran into an issue where even after flashing the recovery, the phone was booting into stock recovery. But as it turns out i only had to press down volume down+ power key to boot into PBRP.
Also rooted the device by flashing magisk zip and installing magisk managaer app.
Click to expand...
Click to collapse
Does magisk works fine @shah.meet6338 ? How do you do coz i face the bootloop problem after flash magisk?
ashish.rasaily said:
Does magisk works fine @shah.meet6338 ? How do you do coz i face the bootloop problem after flash magisk?
Click to expand...
Click to collapse
Yes. Magisk works just fine for me. But i didn't use the magisk zip that was provided with the recovery. I downloaded the magisk zip and flashed it through the recovery and installed the app afterwards ( i might have installed the app first though, i am not sure).
Have you taken backup through the recovery? I ran into bootloop issue after i flashed a custom rom but i had the backup so just restored it.
I am trying to flash a custom rom through PBRP but i am not sure which partition i should select when flashing?
The partition list shows
nvram,uboot,boot,recovery,logo,tee1,tee2,super(product,vendor,system)
i think i should flash the rom to system partition but the system partition doesn't show separately on the list.
RazaDroid said:
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: E7746
Maintainer/Authors build:@raza231198,
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: Soon™
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
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
Code:
fastboot flash recovery recovery.img
Flash vbmeta
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Boot into PBRP by
Code:
fastboot boot recovery.img
or
Code:
fastboot oem reboot-recovery
Copy the zip to internal storage
Flash it
Enjoy
Changelog
PBRP Side 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.
Device Side Changelog
Code:
Initial Build
Bugs
-
Code:
adb reboot recovery
or
Code:
reboot recovery
don't use it
Downloads
Flashable zip
Micromax IN Note 1 | E7746 - PitchBlack Recovery Project
PBRP Version: 3.0.0 Maintainer: PBRP Team
pitchblackrecovery.com
Telegram Group: Click Here To Join
Telegram Channel: Click Here To Join
Project Type: Tool/Utility
Project Name: PitchBlack Recovery Project
Additional Contributors: Reza Adi, Shovon, Manjot Sidhu, Mohd Faraz, Sagar
Project status: Stable
Stable Version: 3.0.0
Click to expand...
Click to collapse
But first of all tell us how can we unlock its bootloader.
hasnainali2404 said:
But first of all tell us how can we unlock its bootloader.
Click to expand...
Click to collapse
Enable Debugging and OEM unlock option in developer options.
Connect to pc install drivers and fastboot binaries
And run command in shell
Code:
fastboot flashing unlcok
RazaDroid said:
Enable Debugging and OEM unlock option in developer options.
Connect to pc install drivers and fastboot binaries
And run command in shell
Code:
fastboot flashing unlcok
Click to expand...
Click to collapse
Is that so easy.
RazaDroid said:
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: E7746
Maintainer/Authors build:@raza231198,
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: Soon™
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
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
Code:
fastboot flash recovery recovery.img
Flash vbmeta
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Boot into PBRP by
Code:
fastboot boot recovery.img
or
Code:
fastboot oem reboot-recovery
Copy the zip to internal storage
Flash it
Enjoy
Changelog
PBRP Side 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.
Device Side Changelog
Code:
Initial Build
Bugs
-
Code:
adb reboot recovery
or
Code:
reboot recovery
don't use it
Downloads
Flashable zip
Micromax IN Note 1 | E7746 - PitchBlack Recovery Project
PBRP Version: 3.0.0 Maintainer: PBRP Team
pitchblackrecovery.com
Telegram Group: Click Here To Join
Telegram Channel: Click Here To Join
Project Type: Tool/Utility
Project Name: PitchBlack Recovery Project
Additional Contributors: Reza Adi, Shovon, Manjot Sidhu, Mohd Faraz, Sagar
Project status: Stable
Stable Version: 3.0.0
Click to expand...
Click to collapse
I installed PBRP TWRP ...
..OTA.
I got notification that update is available. It wont install via TWRP.
How do I install OTA. wrt THis guide .... this phone does not seem to fit ( this isn't A/B phone type A phone. Change log says it can handle MIUI A/B and AB OTA update but this is A ) . WHat do I do ? restore stock recovery and boot and then restore TWRP and boot.patch.img ? Any clue ?
RazaDroid said:
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: E7746
Maintainer/Authors build:@raza231198,
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: Soon™
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
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
Code:
fastboot flash recovery recovery.img
Flash vbmeta
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Boot into PBRP by
Code:
fastboot boot recovery.img
or
Code:
fastboot oem reboot-recovery
Copy the zip to internal storage
Flash it
Enjoy
Changelog
PBRP Side 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.
Device Side Changelog
Code:
Initial Build
Bugs
-
Code:
adb reboot recovery
or
Code:
reboot recovery
don't use it
Downloads
Flashable zip
Micromax IN Note 1 | E7746 - PitchBlack Recovery Project
PBRP Version: 3.0.0 Maintainer: PBRP Team
pitchblackrecovery.com
Telegram Group: Click Here To Join
Telegram Channel: Click Here To Join
Project Type: Tool/Utility
Project Name: PitchBlack Recovery Project
Additional Contributors: Reza Adi, Shovon, Manjot Sidhu, Mohd Faraz, Sagar
Project status: Stable
Stable Version: 3.0.0
Click to expand...
Click to collapse
Make one compatible with Android 12