[MOD] [hydrogen] TWRP 3.1.0 + MultiROM v33 (NO-KEXEC) [UNOFFICIAL] - Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D

[MOD] [hydrogen] TWRP 3.1.0 + MultiROM v33 (NO-KEXEC) [UNOFFICIAL] - Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D

{
"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"
}
Note : Not Tested on Helium hence not supported
Introduction
MultiROM is one-of-a-kind multi-boot mod for Xiaomi Mi Max (Hydrogen). 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. 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, 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.
This is still very experimental!
This has been tested with most popular Rom's of Xiaomi Mi Max (Android MM and N based).
*Please, keep in mind that if you've updated to latest N firmware in your primary ROM, you won't be able to boot MM as secondary any more. If you are on MM firmware then only ROMs built with MM blobs will work, doesn't matter MM or N. If you are on N Firmware then only ROMs built with N blobs will work in MultiROM.
Make backups. Seriously. Please.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive (Not yet implemented)
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 (We do not have Official Support, so this is not an option for us yet)
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 (If you want to use Kexec) - 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, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
Modified recovery - download the IMG file from second post and use fastboot to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the boot.img and flash it in recovery by selecting image flash and flash it to boot parition. This can be avoid using no-kexec workaround in latest MultiROM versions.
MultiROM - download the ZIP file from second post and flash it in recovery.
Your current ROM will not be erased by the installation.
Adding ROMs
Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Once Installation is complete. Go to MultiRom --> List Rom's --> Select the installed secondary Rom --> Remove Boot.img
Done!
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 Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
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)
Flash Kexec-hardboot patched kernel (either the kernel linked in second post or any third party kernel which supports kexec-hardboot (NOT needed when using no-kexec workaround in TWRP -> MultiROM Settings)
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.
Note that swapping roms between internal and external is not supported (yet). Also, after flashing a factory image to the primary system and boot partition, make sure to immediately inject MultiROM before first boot, otherwise the secondary ROMs will be deleted.
Source code
MultiROM - https://github.com/multirom-hydrogen/multirom
Modified TWRP - https://github.com/multirom-hydrogen/Team-Win-Recovery-Project
Kernel w/ kexec-hardboot patch - https://github.com/multirom-hydrogen/kernel_xiaomi_msm8956
Device tree - https://github.com/multirom-hydrogen/android_device_xiaomi_hydrogen
Credits
This work is based on the hard work of @Tassadar (MultiROM), @nkk71 (no-kexec), 500 Internal Server Error, Geoff Levand, webgeek1234, Mike Kasick, Npjohnson, @jackeagle, Hashbang173, and many others. Thank you.
My Team mates @k2wl @Rohan purohit @TechExhibeo @Vatsal. (Thank you very much guys! )
Issues
MIUI is not supported (You should be able to boot MIUI as secondary with latest release if you're still using a MM firmware in your primary ROM).
USB OTG Support is not yet Implemented and will be done in future releases. (It should work in latest releases)
- If you find one that this thread does not know about/hasn't answered (solid rule, read the last three pages of the thread befre reporting an issue), report it on the specific repo in question.
- IF YOU GET LOCKED OUT OF YOUR DEVICE: Don't worry! Your data is fine. Simply boot to TWRP, choose 'Advanced' ==> 'Terminal Command' ==> type "rm -rf /data/system/gatekeeper.*.key" (without the quotes). This is a dirty fix, and should only be used to recover data, not as a permanent solution! After you recover your data, wipe /data (you don't have to wipe Internal Storage), and re-setup the device.
NOTE:
Third party kernel developers if you have merged Kexec-hardboot support kindly PM me linking to your kernel sources with confirmation about the working. So that I can add your kernel here in supported kernel list
Extra Information
I ask that no one build targeting the Xiaomi Mi Max using our source and post it publicly ( distribution is forbidden). Of course, I welcome and ask that anyone who wants to pull request changes in to do so!
XDA:DevDB Information
MultiRom-Xiaomi Mi Max (Hydrogen), Tool/Utility for the Xiaomi Mi Max
Contributors
jackeagle, BitOBSessiOn
Source Code: https://github.com/multirom-hydrogen
Version Information
Status: Stable
Current Stable Version: Stable 1
Stable Release Date: 2016-12-20
Current Beta Version: NO-KEXEC version
Beta Release Date: 2017-01-14
Created 2016-12-20
Last Updated 2017-03-25

Downloads
Downloads (NO-KEXEC)
MR Installer App: Play Store Link
(Still Not Supported for Hydrogen, working on it...)
TWRP 3.1.0 (MultiROM modded): Latest here
MultiROM v33 Installer Flashable ZIP: Latest here
MultiROM Uninstaller Flashable ZIP: multirom_uninstaller.zip

Changelogs
Changelogs
Code:
[COLOR="Blue"]
[SIZE="4"]24/03/2017
- Updated TWRP to 3.1.0 Release
- MultiROM and TWRP Upstream Updates
- [URL="https://forum.xda-developers.com/showpost.php?p=71576938&postcount=40"]More info about release![/URL]
02/03/2017
- Finally fixed Lockscreen security bug fixed
- MultiROM and TWRP Upstream Updates
- [URL="https://forum.xda-developers.com/showpost.php?p=71254611&postcount=24"]More info about release[/URL]
19/01/2017
- MR Upstream Updates merged
- Merged with latest TWRP Changes
- Updated MR TWRP to 3.0.3-1 Release
15/01/2017
- Added MIUI Support (Limited Support kindly read OP and Release notes for further details)
- Updated to Latest MR No Kexec v33
- Updated MR TWRP to 3.0.3 Release
- Fixed USB OTG Support
- Added Minimal Tree
20/12/2016
- Initial Release
[/SIZE][/COLOR]

Great work Jack ! glad to help , we rock

Eagle has arrived?

Great Work Bro.
Thank you for releasing (pain it was to release than to fix bugs) ????
-TechExhibeo

Awesome work buddy.
Really appreciate your efforts and hardwork Sir!
Thank you once again.

It says my device isn't supported I have Mi Max 32gb global My stock ROM is CM 14.1.

jutley said:
It says my device isn't supported I have Mi Max 32gb global My stock ROM is CM 14.1.
Click to expand...
Click to collapse
Follow the installation instructions in OP
Multirom App don't have hydrogen support
-TechExhibeo

Awesome?

is the modded kernel going to work with marshmallow based roms(especially resurrection remix) ?

wingryder said:
is the modded kernel going to work with marshmallow based roms(especially resurrection remix) ?
Click to expand...
Click to collapse
Currently Marshmallow ROMS are not supported
Maybe in future or so
-TechExhibeo

Really appreciate your efforts and hardwork!
Hope Like This You Bring More ROMs for Mi MAX!

TWRP 3.0.3 + MultiROM v33 (NO-KEXEC) Available
Well, after some testing, we can release first NO-KEXEC version for MultiROM v33 and latest modded TWRP 3.0.3 to support it.
You can download latest releases from here.
NO-KEXEC workaround (Big thx to @nkk71 ) is enabled by default so you should be able to boot WITHOUT any kexec-patched kernel as primary ROM.
If you are still using MM firmware on primary ROM you should be able also to boot ANY N, MM based ROM as secondary, included MIUI, but keep in mind that you'll get any issue if your secondary ROM needs N firmware (we can't get everything... ).
This TWRP version should support USB OTG as well and fix some prior bugs found in 3.0.2 version.
Thx to @TechExhibeo and @jackeagle for their support.
Feedback welcome.

BitOBSessiOn said:
Well, after some testing, we can release first NO-KEXEC version for MultiROM v33 and latest modded TWRP 3.0.3 to support it.
You can download latest releases from here.
NO-KEXEC workaround (Big thx to @nkk71 ) is enabled by default so you should be able to boot WITHOUT any kexec-patched kernel as primary ROM.
If you are still using MM firmware in primary ROM you should be able also to boot ANY N, MM based ROM as secondary, included MIUI, but keep in mind that you'll get any issue if your secondary ROM needs N firmware (we can't get everything... ).
This TWRP version should support USB OTG as well and fix some prior bugs found in 3.0.2 version.
Thx to @TechExhibeo and @jackeagle for their support.
Feedback welcome.
Click to expand...
Click to collapse
Good Job Sir.
Note for Users - If you are on MM firmware then only ROMs built with MM blobs will work, doesn't matter MM or N.
If you are on N Firmware then only ROMs built with N blobs will work in MR
You cannot boot different firmware ROMs in MR to boot :v
^ NON-KEXEC Multrirom
Thank you.
-TechExhibeo

TechExhibeo said:
Good Job Sir.
Note for Users - If you are on MM firmware then only ROMs built with MM blobs will work, doesn't matter MM or N.
If you are on N Firmware then only ROMs built with N blobs will work in MR
You cannot boot different firmware ROMs in MR to boot :v
^ NON-KEXEC Multrirom
Thank you.
-TechExhibeo
Click to expand...
Click to collapse
Thx for clarification, OP updated :good:

TWRP 3.0.3-1 + MultiROM v33 (20170118)
Downloads:
TWRP 3.0.3-1 available here.
MultiROM v33 (20170118) available here.
Changelog:
Code:
commit 53f72b7563c6cf358c5088246ad3af0899327df5
Author: bigbiff bigbiff <[email protected]>
Date: Thu Dec 8 21:21:17 2016 -0500
TWRP device version string
For building through jenkins. Export a variable to the shell
so that we don't monkey patch variables.h and keep the git tag
clean in the version string.
Jenkins will export the variable TW_DEVICE_VERSION=n where n > 0.
The makefile will use this variable to show the device string
in twrp startup. For mass production builds, omit the
environment variable to default to 0.
Change-Id: I0d6eb764255d7069c0fb4a378522a009cfe4054f
commit 94e5a23dd2f12c2cfca8beb9dadbde92820b1d55
Merge: 78f6699 7dde36d
Author: nkk71 <[email protected]>
Date: Sat Jan 14 16:13:41 2017 +0200
Merge remote-tracking branch 'upstream/android-7.1' into android-7.1-mrom
commit 7dde36df119a1ed0089b999641b27dc2c2a5280d
Author: sndnvaps <[email protected]>
Date: Tue Oct 4 18:09:37 2016 +0800
updater: link libcrypto_utils_static if it exist
Change-Id: I9bf238a3e29d88850a6cc69f07954949722c35d7
Signed-off-by: sndnvaps <[email protected]>
commit 1c28904749f5d0ae58b113b5b59901f7fc3731f6
Author: D. Andrei Măceș <[email protected]>
Date: Fri Dec 16 16:01:56 2016 -0500
libtar: Use relative path for crypto/ext4crypt include
Don't assume path to be bootable/recovery (i.e., support CM's
RECOVERY_VARIANT).
Change-Id: Ib53cc919c5a9beb3beee71d7227a7c957a24b601
commit 1021edf17ed57f193724a953dd159e7717e9553a
Author: nailyk-fr <[email protected]>
Date: Sun Dec 18 14:32:25 2016 +0100
bootloader_message: Allow TWRP to ignore wipe-data command into misc
* Rebase of https://gerrit.omnirom.org/#/c/20750/ patch-set 3
* Original commit message:
fix: recently a change in AOSP causes a bootloop to TWRP
(and therefore all ROM's based on it)
Reason: AOSP enables use of /misc partition and normally the fstab in
TWRP will not have /misc added. The problem is now when Android writes
a wipe command to /misc it will force TWRP to boot but TWRP will do
nothing - leaving the cmd in /misc. This results in a bootloop to TWRP.
Solution: I added a new var TW_IGNORE_MISC_WIPE_DATA which can be
set to "true" in Boardconfig.mk of a device requiring this which then
ignores /misc commands like it would be when /misc would be just not in
fstab BUT with this change TWRP clears the bit in /misc so a normal boot
can happen.
Besides that if the device do not have an own recovery key combo and
/misc is enabled we want to open TWRP after walking through the factory
reset screen - without actually doing a factory reset.
kudos to nailyk (and DevUt) for the help with the C++ code!
Change-Id: If6fed5872015f1a66304e3edbdb787c507236f69
commit dcd1e440e009b7861f09e2b718ea489bdcea34b5
Author: James Christopher Adduono <[email protected]>
Date: Sun Nov 6 13:17:34 2016 -0500
Support theme width and height offsets
Current use condition is LG V20, where the secondary screen is
actually just a corner chunk of the main screen.
In this case, we need to shift the UI down some pixels in order
to see it all, but just using Y offsets resulted in losing
the rest of the GUI below.
Example in BoardConfig.mk:
# Shift TWRP off the secondary screen
TW_Y_OFFSET := 160
TW_H_OFFSET := -160
Change-Id: I5a06638ba0d05e5b9fd8a6245c630d6ea3394f78
commit b29a5e27c33291f8134ea5f28e84e672a3c25199
Author: D. Andrei Măceș <[email protected]>
Date: Thu Dec 22 06:19:44 2016 -0500
build: Consolidate the crypto_utils presence tests
No point checking filesystem repeatedly/check may change in future
Change-Id: I0413b07b850f785eb5150c6ed18836cc56e94d6f
commit 4767caf1f4cd08cdc7d58476bc017dca17870112
Author: Ethan Yonker <[email protected]>
Date: Wed Jan 11 10:45:04 2017 -0600
Fix compile error on 4.4 tree
Change-Id: Id85fdf0f4dee02f8ee3ae50ec42423c6a154a3eb

BitOBSessiOn said:
Downloads:
TWRP 3.0.3-1 available here.
MultiROM v33 (20170118) available here.
Changelog:
Click to expand...
Click to collapse
Hi , great work! Currently fingerprint/gatekeeper issue is present, to explain in brief ( after adding a secondary ROM , when u boot into primary, u can't unlock the device (deleting /data/system/gatekeeper_pattern/password.key will fix) we need to fix this in mr_hooks.c like here https://github.com/multirom-nexus6p...mmit/2c2bb118fb125888144bb3399aefca961fa77df9
https://github.com/multirom-nexus6p/android_device_huawei_angler/blob/cm-14.1/multirom/mr_hooks.c
Secondly ,
Only tested this with dirty unicorns, aicp as primary, n du as secondary, after selecting secondary in mr menu , it will reach boot animation n reboot again from splash (mi logo) so Ul have to select secondary ROM option again, which then boots fine

Rohan purohit said:
Hi , great work! Currently fingerprint/gatekeeper issue is present, to explain in brief ( after adding a secondary ROM , when u boot into primary, u can't unlock the device (deleting /data/system/gatekeeper_pattern/password.key will fix) we need to fix this in mr_hooks.c like here https://github.com/multirom-nexus6p...mmit/2c2bb118fb125888144bb3399aefca961fa77df9
https://github.com/multirom-nexus6p/android_device_huawei_angler/blob/cm-14.1/multirom/mr_hooks.c
Secondly ,
Only tested this with dirty unicorns, aicp as primary, n du as secondary, after selecting secondary in mr menu , it will reach boot animation n reboot again from splash (mi logo) so Ul have to select secondary ROM option again, which then boots fine
Click to expand...
Click to collapse
Interesting, I will revise. Thx!

yes as described by @Rohan purohit the problem is present ... this problem has beem solved by @nijel8 in his unofficial build waiting for fix

Related

[ROM] [ serrano 3G & LTE ] AICP 12.1 - N7.1.x_rXx | OFFICIAL NIGHTLIES

.
.
.
.
{
"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"
}
AICPAndroid Ice Cold Project
AICP is known by everyone as Ice Cold Project that started on Desire HD and since then evolved into a mature ROM with the BEST community you can find!!!
Until Lollipop, Rom has always been AOKP based. Unfortunately, since AOKP stopped development then (but made a comeback by now), we changed our base to CM when it comes to hardware, drivers and some features. Since CM changed to LineageOS in 2017, our base remain LineageOS (LOS).
If there are any bugs, either we will sort them out or the LOS team, if it concerns their modifications. This rom isn't LOS supported so no need to report errors or bugs to them!!
.
.
.
.
.
In the beginning we would like to thank:
CM team and esp to the great @arco68. Thank You Arne !!!
@f4k for his great work with kernel and the permissions for using it - Thanx Man
maxwen
SlimBean rom team
CarbonRom team
LiquidSmooth rom team
Omni rom team
DU team
Community
@LorD ClockaN
@zipsnet
@n3ocort3x
@semdoc
@eyosen
@alienmind
@Chezbel
@Drgravy
@eboye
.
.
.
We are now paying for servers that build nightlies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!

Latest Stable Release Version 12.1
Download link: goo.gl/mIgmYG
Full Changelog link: goo.gl/mIgmYG
Don't disable Heads-Up. You wont be able to answer phone calls otherwise.
You tell...
The ROM should contain everything you need to enjoy Android Nougat. Only thing that is needed additionally is a root soultion, if you want this! Simply download the latest ROM, GApps, root soultion, flash it, and go!
You are STRONGLY recommended to fully wipe your device before flashing, and if possible avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug. If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience strange behavior.
Addition for installing root on builds after 17/06/14:
CHANGES (READ THIS BEFORE FLASHING!)
YES. AICP is going to build rootless builds.
This change will happen during a short period of time.
I could explain the decision for that,
but that would not be understandable for all users, so i put it this way...
Going rootless means that the ROM will NOT come with any Root or SU built in anymore.
There will be no Magisk - as a buildin root solution - be provided when the user flashes the ROM zip file.
What you will have to do (If you don't do it by now):
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You will have to flash a root solution of your choice (lineage-su addon, SuperSU or Magisk) by yourself after the ROM.
I will link the appropriate solutions here in this post.
REMEMBER:
First flash the ROM, then your desired root solution!
This MUST also be done on every dirty flash to ensure root is not lost!
This MUST be done, when using the OTA app too! Just add the "root" zipfile after the ROM!
What will be noticeable to the user:
~~~~~~~~~~~~~~~~~~~~~~~~~~
1. We had to cut out some features for getting this done. Those are:
a. The SELinux switch in the dev options is gone for now.
This can also be done by other apps, if necessary.
b. The feature to flash another bootanimation from AICP Extras is gone.
You can still use a flashable ZIP from TWRP or Substratum.
c. The builtin logcat feature in AICP Extras will be gone.
Most users did not use it either as it only can store max. 400KB.
We already advised to use Catlog or Syslog Apps (both free on Play store).
Remember that both need root!
d. The builtin "System app remover" will be gone, as it required root to run.
2. You will, of course, not see Magisk Manager in the app folder, of course.
3. Remember that without a root solution some other apps e.g. Kernel Audiutor will also not work.
Whatever you choose. Lineage SU options are in dev options in settings. The others use separate Apps.
Links to tested root solutions (download from the thread):
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Magisk (remember that v12 need the Manager to be flashed separately. v13 will have it buildin the flashable ZIP:
Magisk Official
Magisk beta
SuperSU (Use whatever works for you, stable or beta):
SuperSU stable
SuperSU beta
Lineage SU-addon (check your needed version 14.1 arm or arm64!):
LineageOS su-addons for 14.1
-> the removal zip is available here too.
How to flash:
Again: Don't do it if you don't know it!
TWRP is the recommended custom recovery (and needed for OTA Updates)
1. full wipe
2. flash ROM
3. flash GApps
(The ROM has GApps persistance in between dirty flashes, so you only have to flash them once!)
4. flash root solution of your choice (SuperSU, Magisk or whatever you want)
KERNEL:
AICP for serrano3gxx and serranoltexx was powered with @f4k kernel on MM and now uses LOS stock kernel on N. So expect the best regarding performance, battery life and performance!
IF you want, you can try the Remix Kernel available on XDA. 
PREREQUISITE FOR OTA:
To be able to flash over OTA app, TWRP recovery is needed.
You can still use CWM and OTA app, but only to download zip file and flash it manually from within recovery. The ROM Zip gets saved under AICP_ota folder on your internal SDcard.
Please be sure that you are on the latest TWRP recovery.
For current builds of Nougat (AICP 12.1) please use the versions from here (thx to @ne0zone75):
http://forum.xda-developers.com/showthread.php?t=2678420
AICP supports F2FS for /data & /cache since MM. So enjoy the F2FS smoothness thanx to @f4k !!!!
If you want to contribute to the AICP or want see what is being worked on or merged, feel free to visit our Gerrit Review system (link is at the bottom!!!)
AICP G+ community
kernel github
rom gerrit
You want to see a normal night at the DEV office, click here!!
XDA:DevDB Information
[ROM] [ serrano 3G & LTE ] AICP 12.1 - N7.1.x_rXx | OFFICIAL NIGHTLIES, ROM for the Samsung Galaxy S4 Mini
Contributors
semdoc, wartomato, DarkExistence, Lord CloCKaN
Source Code: http://dwnld.aicp-rom.com/?device=serrano3gxx
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Nightly
Current Stable Version: 12.1
Stable Release Date: 2016-11-04
Created 2015-02-10
Last Updated 2017-08-12

Reserved
How to Convert your Ext SD Card into Semi Portable Storage?
kingwicked said:
I have converted my ext sdcard into semi portable storage as you can see above.
Benifits (8gb adopted storage+21Gb Portable Storage) out of 32GB ext sdcard Class 10
1. i have 8GB (internal)+ 8GB(external) now for apps to move around
2. i can still remove the sdcard and transfer files directly to the sdcard 2nd partition of 21GB from PC
i followed the following guide by Sam Liddicott here is the link.
Code:
http://blog.sam.liddicott.com/2016/02/android-6-semi-adopted-storage.html
if ADB commands dont work from pc . try mounting all partitions from TWRP recovery that worked for me
i am on the latest build of this rom
Click to expand...
Click to collapse

Reserved
Please go and hit Thanx to @ne0zone75 for he's great work !!! That post can be found here: http://forum.xda-developers.com/showthread.php?t=2678420
ne0zone75 said:
What’s new in v3.0.0-0 :
Completely new theme - Much more modern and much nicer looking (by z31s1g)
True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
A huge laundry list of other minor fixes and tweaks
INSTALLATION :
=> Option 1 : your device does not have any custom recovery yet ! Please download the 7zipped .tar.md5 file of your choice below, then flash it through Odin (windows OS).
=> Option 2 : a custom recovery has already been flashed to your device ! Please download the flashable .zip file of your choice below and flash it from recovery as usual.
BIG ORANGE WARNING : if you are coming from regular / PhilZ CWM or legacy TWRP, then please do prefer the Odin way ! Thank you !
TO GT-I9192 users : dedicated recovery images are now available for your device from the downloads section below, just let me know how it goes with them... thank you !
DOWNLOADS :
=> STABLE branch : 1 version per device built for stability, full crypto. support for EXT4 only... EXT4+F2FS <= built along with OmniROM LP ROM tree !
custom TWRP v3.0.0-0 MM enabled for S4 mini (3G variant) | STABLE (2016-02-07) | Odin & recovery flashable
custom TWRP v3.0.0-0 MM enabled for S4 mini (LTE variant) | STABLE (2016-02-07) | Odin & recovery flashable
Click to expand...
Click to collapse

Flashed and no issues so far

Using it for 1 month now, no issue. Best community ever. Doc

Miccia said:
Using it for 1 month now, no issue. Best community ever. Doc
Click to expand...
Click to collapse
Wellcome
Every help with the thread is really appreciated

semdoc said:
Wellcome
Every help with the thread is really appreciated
Click to expand...
Click to collapse
Obviously doc...
U know me with another name ahahahaha, not this one

Thanks

Please can you add some screenshots?

Download is very slow for me, another server download?

Ucar_ said:
Please can you add some screenshots?
Click to expand...
Click to collapse
Check the google+ community

Guys here some screenshoot. Dont look the color and the font ( im using a theme)

Hi,
Flasch perfect for me, no FC. That seems to be a good rom. Wifi OK
Tomorrow I will work with my phone and test it.
See you later.
Nicolas.

Hi,
Does this ROM works for a i9192? or only the i9190-5? thank you!

I could finally download and install on my GT-I9190, the bootanimation is amazing !!! everything is running smoothly, thanks for the support !!!

Miccia said:
Guys here some screenshoot. Dont look the color and the font ( im using a theme)
Click to expand...
Click to collapse
Your SS's were added to Screenshots section of this thread. :good:
Cheerz

Neikosr0x said:
Hi,
Does this ROM works for a i9192? or only the i9190-5? thank you!
Click to expand...
Click to collapse
Really don't know... As far as I know.. It will abort installation If it doesn't fit ...

Good Rom, much smoother than the original CM12, less wifi Problems, no call problems, fine!
Go ahead! :good::good::good:

Miccia said:
Guys here some screenshoot. Dont look the color and the font ( im using a theme)
Click to expand...
Click to collapse
is this theme include in the rom??

opexx said:
is this theme include in the rom??
Click to expand...
Click to collapse
No

[RECOVERY][7.0][sprout] TWRP 3.0.2-XI touch recovery | Alpha 1

Unofficial TeamWin Recovery Projects or Unofficial TWRP 3.x , this project has been started to provide latest recoveries announced and officially launched by TWRP. TWRP based on Android N Nougat Fully Supported.
{
"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"
}
TeamWin Touch Recovery for Android One
Code:
/*
* [U][B]Disclaimer[/B][/U]
* Your warranty is now void.
*
* 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 recovery
* 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.
*/
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
Downloads for Sprout:
Nougat Builds 7.0MB (Last NG build: 3.0.2-XI)
Issues:
1. File Manager
- Copying and Moving Files
2. Terminal
3. Mounting SDCARD in few builds
4. If you flash kernel it will show successful but dosen't flash
Marshmallow Builds 6.7MB (Last MM build: 3.0.2-X)
Issues:
None "Completely Stable"
NOTE: Nougat Builds are only Alpha builds, They are only released for preview, there will be frequent "OTA" when each bug is fixed. Nougat build are not daily driver, if you want stable driver prefer the Marshmallow builds.
Installation Guide:
Code:
fastboot erase recovery
fastboot flash recovery <recovery-file-name>.img
Install Temporarily Guide:
Code:
fastboot boot <recovery-file-name>.img
Unlock Bootloader Guide:
Code:
fastboot oem unlock
fastboot format userdata
fastboot reboot
Source Code:
Nougat:
Device
Kernel
Recovery
Marshmallow:
Device
Kernel
Recovery
XDA:DevDB Information
TWRP 3.x [UNOFFICIAL] for Sprout Devices, Tool/Utility for the OEM Cross Device Development
Contributors
MICKEY_ANDRO100, varun.chitre15, MSF Jarvis
Source Code: https://github.com/HostZero/android_kernel_google_sprout
Version Information
Status: Alpha
Current Stable Version: 3.0.2-X/10
Created 2016-04-14
Last Updated 2016-10-02

Reserved

Reserved
Changelogs 3.0.2-XI:
Code:
1. Android Nougat [7.0] is fully supported by this recovery
2. Android Base 6.0.1_r62 -> 7.0_r6
3. Initial 7.0 Kernel Tweaks from @varun.chitre.15 kernel source
4. 7.0 Security Patches [B]"NRD90U"[/B] (September 5)
[B]NOTE:[/B] [I][U]The OmniROM Project based on 7.0 is still in Alpha Stage, so the recovery is not fully stable, but good as daily driver, if any errors occur please provide a log cat.[/U][/I]
Changelogs 3.0.2-X:
Code:
1. Android base r41 -> r62
2. Upstreamed to [B]"MOB30Z"[/B]
3. Kernel v3.10.101 -> 3.10.103
-- Used Linaro 5.2 Toolchain
-- Removed SquashFS and LZ0 Support
Changelogs 3.0.2-9:
Code:
1. Shifting CyanogenMod to OmniROM Source Code
2. Added new partitions like PROTECT_F/PROTECT1 and PROTECT_S/PROTECT2
3. downstreamed to [B]"MTC20F"[/B] (Sorry for this)
4. Now backup data and cache in [B]"F2FS" "EXT2" "EXT3" "EXT4"[/B] (auto)
Changelogs 3.0.2-8:
Code:
1. android base r46 --> r61
2. fixed status 7 while flashing cyanogenmod
3. upstreamed to [B]"MOBR30"[/B] - July Security Patch
4. using advanced LZMA compression method to reduce size of recovery (6.7MB)
5. kernel upstreamed from 3.10.57 --> 3.10.101
Changelogs 3.0.2-7:
Code:
1. Fixed CPU Temperature.
[U]CUSTOM CPU PATH MTK: /sys/devices/virtual/thermal/thermal_zone1/temp[/U]
Changelogs 3.0.2-6:
Code:
1. Fixed Partition Mounting/UnMounting Issues on Few builds
2. Fixed nvram mounting/backup
3. All Backup Option are Back (ex: OEM, RECOVERY, IMEI etc..)
4. Updated June 11 2016 cyanogenmod kernel.
Changelogs 3.0.2-5:
Code:
1. Updated TWRP sources.
2. Based on June's Patch.
3. Based on Latest CM 13.0 NIGHTLY device tree.
4. Added Reboot Download Option.
5. CPU Temperature removed.
6. SuperSU and Install SuperSU Prompts Removed.
7. F2FS Support Added.
8. Faster and Fluid

I flashed the 3.0.2-0 on my sprout8 device (Cherry Mobile One) , I noticed that it cannot read my CPU temps. (see attached picture)
UPDATE: I also tried redownloading the file and flashing it via fastboot mode, no success. It cannot read my CPU temps.

Sean De Jesus said:
I flashed the 3.0.2-0 on my sprout8 device (Cherry Mobile One) , I noticed that it cannot read my CPU temps. (see attached picture)
UPDATE: I also tried redownloading the file and flashing it via fastboot mode, no success. It cannot read my CPU temps.
Click to expand...
Click to collapse
Sorry, for your inconvenience sir, we have ported TWRP's from different devices where as we have done 3 builds till try to upgrade to TWRP 3.0.2-1 BETA 2, where as it was fine one my sprout4 and tester yogeshrockzzz for sprout8 he said it had a successful boot with no bugs in TWRP 3.0.2-1 BETA 2 try that out.
Thanks for Informing we will fix temp as well as one aldready recognized bug.
My device touch screen has bricked so, after 3-4 days there will be a final testing with faster twrp and after that i will launch. :laugh:
Try TWRP 3.0.2-1. :good:

Please don't use pay per click links, it is forbidden according to the forum rules here
13. Advertising and Income Generation
Commercial advertising, advertising referral links, pay-per-click links and other income generating methods are forbidden. Do not use XDA-Developers as a means to make money.
Click to expand...
Click to collapse

KcLKcL said:
Please don't use pay per click links, it is forbidden according to the forum rules here
Click to expand...
Click to collapse
As you said sir, pay per click links would be removed and will be updated.

KcLKcL said:
Please don't use pay per click links, it is forbidden according to the forum rules here
Click to expand...
Click to collapse
Sir, Done! No short links. The links would be linked to our website.

Oke, lets keep it all in one thread.
From what i see this is the official maintainer thread:
http://forum.xda-developers.com/cro...nt/twrp-twrp-android-one-gen-devices-t3365029
Thread closed.
Edit: seein al the trouble with official version I open this up again.

Reserved

Nice work bro..... Thks

Whiskey103 said:
Oke, lets keep it all in one thread.
From what i see this is the official maintainer thread:
http://forum.xda-developers.com/cro...nt/twrp-twrp-android-one-gen-devices-t3365029
Edit: seein al the trouble with official version I open this up again.
Click to expand...
Click to collapse
Trouble resolved : http://forum.xda-developers.com/showpost.php?p=66517613&postcount=2

MSF Jarvis said:
Trouble resolved : http://forum.xda-developers.com/showpost.php?p=66517613&postcount=2
Click to expand...
Click to collapse
Sorry MSF but this is TWRP 3.0.2-3 but the OFFICIAL is 3.0.2-1.

Thanks for the TWRP. I tried twrp 3.0.2-3 it worked without any problem

MICKEY_ANDRO100 said:
Sorry MSF but this is TWRP 3.0.2-3 but the OFFICIAL is 3.0.2-1.
Click to expand...
Click to collapse
From the official announcement :
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
Click to expand...
Click to collapse

MSF Jarvis said:
From the official announcement :
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
Fine but this TWRP 3.x UNOFFICIAL Projects Page. As i have tested again your twrp 3.0.2-1 its still non-bootable and please don't try to Close the Thread.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

mithun mpk said:
Thanks for the TWRP. I tried twrp 3.0.2-3 it worked without any problem
Click to expand...
Click to collapse
Thankyou a lot. If you found any kind of bug please PM me or add it it bug reports tab. I ll fix on coming up version.

3.0.2-3_v2 out!

Twrp 3.0.2-3 final stable out!

HostZero said:
3.0.2-3_v2 out!
Click to expand...
Click to collapse
HostZero said:
Twrp 3.0.2-3 final stable out!
Click to expand...
Click to collapse
Changelogs don't hurt, you know. It helps people appreciate your hard work even more (As if copy-pasting is remotely hard).
Sent from my PixelV1 using XDA Labs

[OFFICIAL][v.2.9.0] PitchBlack Recovery Project [lv517, MP260, TP260][32/64bit]

Pitchblack recovery project
{
"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:
/*
* 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.
*
*/
PitchBlack is a TWRP based on TWRP 3.2.3 developed by Reza Adi, maintained by Manjot Sidhu and Mohd Faraz and themed by FireWolf.
For devices (OFFICIAL) : https://sourceforge.net/projects/pitchblack-twrp/files/
Authors build : @Reza_adi, Mohd Faraz
Developers : @Reza_adi, Mohd Faraz
Thanks : @Reza_adi P - Indonesia (Owner / Lead Developer PBRP), George Pasakalis (G.M.L) - Greece (UI Developer), FirewolfXDA - Bangladesh (UI Developer), Manjot Sidhu - India (Source Maintained), Mohd Faraz - India (Co-Lead Developer, Source Maintained), Arbaz Khan - India (Source Maintained), PitchBlack Recovery, @ATG Droid & @dadi11 (Redwolf Developer) for MIUI OTA Support, @arra_quen for Helping and Uploading @faizhifzhan for layout to sourceforge, All Maintainer and User PBRP.
DOWNLOAD :
Recovery zip
BUGS:
When booted while charging, battery level shows 0%.
If you find any other bugs please let me know and i'll try to address them or update this section of the thread to let the bug be publicly known.
F2FS filesystem format is limited to 4GB for some reason so don't use it for /data ( I currently use /cache and /system as f2fs instead of EXT4 with no issues )
INSTALLATIONS :
Flash Zip file as if it were a ROM in TWRP, or you can flash the Recovery.img as you would TWRP (adb commands, apps such as flashify, kernel auditor/mtweaks, terminal dd commands, or using TWRP under Install > install image > recovery )
If using installing the Zip file through TWRP or other custom recovery, it will reboot automatically to recovery. If using the recovery.img method, reboot into recovery as you normally would.
Enjoy
XDA:DevDB Information
PitchBlack Recovery Project, Tool/Utility for the LG K20 Plus
Contributors
Travisholt92,
Deadman96385 (helped to provide bandwidth and the Q6 Stock Oreo kernel which my Oreo+ builds and this project utilize)
Source Code: [url]https://github.com/PitchBlack-Recovery[/URL]
Version Information
Status: Official
Current Version: 2.9.0
Release Date: 2019-02-05
Created 2019-02-03
Last Updated 2019-02-07

My to do list for tonight, update the Fstab to properly support F2FS filesystem format and address the filesystem error.
I should have a new official build up tonight.

I must say this recovery is ? % awesome. I like the extra features that include the options to install/uninstall SuperSU and/or magisk and various more. I think twrp has met it's match.

kieffey said:
I must say this recovery is ? % awesome. I like the extra features that include the options to install/uninstall SuperSU and/or magisk and various more. I think twrp has met it's match.
Click to expand...
Click to collapse
And that's why I went for Official PBRP before official TWRP, to get people to at least give it a try. Its based on the latest TWRP so it has all of the features TWRP users love with quite a few extras.

will this work on stock rom

chacon16 said:
will this work on stock rom
Click to expand...
Click to collapse
It should, I haven't tested. The only reason to stay on stock is VoLTE.

chacon16 said:
will this work on stock rom
Click to expand...
Click to collapse
It works fine in stock. It works with every flavor of ROM out for the K20 Plus.
Sent from my LG K20 Plus using XDA Labs

New build up today that addresses the issue with rebooting to recovery from within recovery.

Screenshots

ROMs?
I read earlier that "every flavor of K20 Plus" will work with PB, so I just want to make sure I am 100% clear and sure I understand before I **** up (another) phone...
I am using a Rooted LG K20 Plus with the Resurrection Remix OS ROM and Pitch Black recovery. The only problem is that my phone has no audio function. Mic, and Speakers are nonfunctional. It won't play videos, make or receive calls, play music, or even the background sound on Games. It is my understanding that this is a common bug with Resurrection Remix ROM, so I'd like to just put a new OS. I just need to know if any OS will work as long as its compatible with the K8+ or if it has to be tailored/compatible for PB as well?

CrookedYoungHeretic said:
I read earlier that "every flavor of K20 Plus" will work with PB, so I just want to make sure I am 100% clear and sure I understand before I **** up (another) phone...
I am using a Rooted LG K20 Plus with the Resurrection Remix OS ROM and Pitch Black recovery. The only problem is that my phone has no audio function. Mic, and Speakers are nonfunctional. It won't play videos, make or receive calls, play music, or even the background sound on Games. It is my understanding that this is a common bug with Resurrection Remix ROM, so I'd like to just put a new OS. I just need to know if any OS will work as long as its compatible with the K8+ or if it has to be tailored/compatible for PB as well?
Click to expand...
Click to collapse
This phone is not compatible with k8 at all. I released lineage 15.1 and it is currently the only stable Oreo rom for this device

Travisholt92 said:
This phone is not compatible with k8 at all. I released lineage 15.1 and it is currently the only stable Oreo rom for this device
Click to expand...
Click to collapse
Whoopee, where it says K8+ on my post is a typo, idk why but my boyfriend was under the impression initially that this K20+ was a K8, I still get confused and mixed up, especially since I also tinker with an LG K4 Rebel lol. But the phone I am using/inquiering about is indeed the LG K20+.
P. S do you have any input/suggestions/advice about the Resurrection ROM 8I can just 7 send 8tnti you

leave your /system partition formatted as ext4
Flashing this ROM uses block-based patching; instead of copying the necessary files to the filesystem, it copies blocks to the disk. These blocks are data representations of files as they were expressed on the filesystem they originate from, thus copying blocks from an ext4 filesystem to any other filesystem will corrupt it.
Since this is my first post I cannot post the pictures I took of PBRPs output after flashing the ROM to both f2fs and ext4 filesystems and then running e2fsck. On f2fs, the partition is recognized as ext4 after the flash, and e2fsck.f2fs fails as the partition is corrupt beyond repair. On ext4, e2fsck executes as expected. You can also search "block-based OTAs" to find the entry on the AOSP website for more information.

dode417 said:
Flashing this ROM uses block-based patching; instead of copying the necessary files to the filesystem, it copies blocks to the disk. These blocks are data representations of files as they were expressed on the filesystem they originate from, thus copying blocks from an ext4 filesystem to any other filesystem will corrupt it.
Since this is my first post I cannot post the pictures I took of PBRPs output after flashing the ROM to both f2fs and ext4 filesystems and then running e2fsck. On f2fs, the partition is recognized as ext4 after the flash, and e2fsck.f2fs fails as the partition is corrupt beyond repair. On ext4, e2fsck executes as expected. You can also search "block-based OTAs" to find the entry on the AOSP website for more information.
Click to expand...
Click to collapse
Only /cache and /system will currently work with F2FS which needs to be formatted that way before install and only my Lineage 15.1 supports f2fs filesystem format. I have tested and confirmed it works at the time of implementation. Formatting /data as F2FS limits the partition to 4GB for some reason i have yet to figure out. I hope this bit of information helps.

CrookedYoungHeretic said:
Whoopee, where it says K8+ on my post is a typo, idk why but my boyfriend was under the impression initially that this K20+ was a K8, I still get confused and mixed up, especially since I also tinker with an LG K4 Rebel lol. But the phone I am using/inquiering about is indeed the LG K20+.
P. S do you have any input/suggestions/advice about the Resurrection ROM 8I can just 7 send 8tnti you
Click to expand...
Click to collapse
RR 8.1 was a total flop. I built it once and it had so many ROM source related bugs from no longer being supported by the RR team that i just gave up on it. More or a variety of ROMs will come after i get pie working.

Travisholt92 said:
Only /cache and /system will currently work with F2FS which needs to be formatted that way before install and only my Lineage 15.1 supports f2fs filesystem format. I have tested and confirmed it works at the time of implementation. Formatting /data as F2FS limits the partition to 4GB for some reason i have yet to figure out. I hope this bit of information helps.
Click to expand...
Click to collapse
I'm not saying it doesn't boot, only informing everyone that the f2fs partition is corrupted by the flashing process and cannot be repaired with fsck. I'm honestly not sure of the total effect of this, but those who are cautious may be thankful for this information.

I can flash the recovery.img for PBRP after doing bootloader unlock via fastboot correct? I don't need to flash TWRP and do all the flashing steps under "How to Disable encryption and flash super su [Install Root]" in the TWRP v3 thread to get PBRP and Magisk on my device? Eventually plan on putting LOS 15.1

SomeDooD123 said:
I can flash the recovery.img for PBRP after doing bootloader unlock via fastboot correct? I don't need to flash TWRP and do all the flashing steps under "How to Disable encryption and flash super su [Install Root]" in the TWRP v3 thread to get PBRP and Magisk on my device? Eventually plan on putting LOS 15.1
Click to expand...
Click to collapse
That is correct, you can use PBRP for those steps.

@Travisholt92 I am trying to flash PBRP and i can only find the .zips linked above. I have tried flashing the .zips in TWRP 3.2.1 . I am failed with "Invalid zip file format" . What am i doing wrong?

chugs said:
@Travisholt92 I am trying to flash PBRP and i can only find the .zips linked above. I have tried flashing the .zips in TWRP 3.2.1 . I am failed with "Invalid zip file format" . What am i doing wrong?
Click to expand...
Click to collapse
You have to unzip the file and fastboot flash recovery.IMG or install the image through twrp under install image

[OFFICIAL][RECOVERY][ONCLITE] OrangeFox Recovery Project [R11.0_0][STABLE]

{
"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"
}
OrangeFox Recovery Project
Code:
/*
* 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 recovery
* 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.
*
*/
OrangeFox Recovery is one of the most popular custom recoveries, with amazing additional features, fixes and a host of supported devices
OrangeFox Recovery have been operating for over two years. In that time we have improved the quality, stability, and device support of the recovery. Today OrangeFox is the leader in stability, UI design, and UX. Installing OrangeFox means being with the latest code and fastest fixes.
OrangeFox Recovery was originally designed for Xiaomi Redmi Note 4X Snapdragon (mido). Right now we support 47+ devices.
Installations
Download the OrangeFox zip file to your device
Reboot to your custom TWRP-based Recovery
Install the OrangeFox zip file as a normal zip
The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
Enjoy!
Downloads
OrangeFox Official siteㅤNEW! & RECOMMENDED!
https://orangefox.download/device/onclite
OrangeFox Stable release
https://files.orangefox.download/OrangeFox-Stable/onclite/
OrangeFox Beta release
https://files.orangefox.download/OrangeFox-Beta/onclite/
Features
Supports Treble and non-Treble ROMs
Increased compatibility with TWRP
Updated with latest TWRP commits
Built-in support for installing init.d functionality
Built-in support for installing Magisk
AromaFM [only for some devices]
Password
Support for Miui and Custom ROMs
Better language support
Optimized versions of community scripts
Fox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
Alternative lockscreen
And many more!
Frequently Asked Questions
OrangeFox Guides & FAQs
https://wiki.orangefox.tech/en/guides
OrangeFox Setup OTA
https://wiki.orangefox.tech/en/guides/ota
OrangeFox FAQs for this device
https://forum.xda-developers.com/showpost.php?p=82504299&postcount=23
Connect with us
OrangeFox Recovery Building
https://t.me/OrangeFoxBuilding
OrangeFox Recovery Updates
https://t.me/OrangeFoxUpdates
OrangeFox Recovery Support
https://t.me/OrangeFoxChat
OrangeFox Recovery Beta tracker
https://t.me/OrangeFoxBetaTracker
OrangeFox Recovery Beta testing
https://t.me/OrangeFoxBeta
Credits
TeamWin - for TWRP
The OrangeFox Team - for your hard work
All our testers - for your patience and help
Report bugs
OrangeFox reporting problems
https://wiki.orangefox.tech/en/guides/report
Notify bugs through the comments column
Take screenshots and give reasons clearly
Grab a log right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing).
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
XDA:DevDB Information
OrangeFox Recovery Project, Tool/Utility for the Xiaomi Redmi 7
Contributors
hadaddarajat
Source Code: https://gitlab.com/OrangeFox
Version Information
Status: Stable
Current Stable Version: R11.0_0
Stable Release Date: 2020-07-19
Current Beta Version: R11.0_0
Beta Release Date: 2020-07-04
Created 2020-04-09
Last Updated 2020-07-20

Warning!
before downloading this recovery, you must first read this Frequently Asked Questions
OrangeFox R11.0 Stable version is available, download via link on thread, for all updates will not be posted here again. So you can immediately check official site!
Before download, look first at "Changelogs" and "Build notes" on official site
R11 Changelogs: https://wiki.orangefox.tech/en/changelog
OrangeFox R11.0 Beta version is available, download via link on thread!
STABLE
Click to expand...
Click to collapse
R10.1_5
Build Date: 2020-05-23
Changelog
Update prebuilt kernel
Update recovery tree
Fixed no boot on some devices
Use mke2fs to create ext4 images
Multi decryption improvement
Release Notes
No need to wipe data, no need to re-install ROM. You can use this on FDE & FBE Encryption.
R10.1_4
Build Date: 2020-05-09
Changelog
Switch back from bash to shell
Updating cryptfs_hw (R10.1_3 corrupt)
Release Notes
No Need to Wipe Data, No Need to Re-Install ROM. You can use this on FDE, FBE & Metadata Encryption.
R10.1_3
Build Date: 2020-05-07
Changelog
Resync with Latest OrangeFox Source Code
Including QCOM Haptics Vibrator
Including QCOM LEDS Haptics
FDE: Automatic Decrypt of /data
FBE: Insert Lockscreen Password for Decrypt /data
Metadata: Same as FBE
Update Device Tree
Release Notes
No Need to Wipe Data, No Need to Re-Install ROM. You can use this in FDE, FBE & Metadata Encryption.
R10.1_2
Build Date: 2020-04-27
Changelog
Rearrange source code
Reconfigure fstab file
Disable system vold debug
Remove CPUs online
Reduce heat on front screen
50% default screen brightness
100% maximum screen brightness
Adding SELinux Policy
Adding Metadata decryption support
Update prebuilt kernel with Metadata support
Auto detect MicroSD Card partition type
Auto detect USB-OTG partition type
Release Notes
If you use the same type of Encryption, then wipe data and re-install ROM is not required. But if you move from a ROM that has a different type of Encryption, you must wipe data and re-install ROM. You can use this in FDE, FBE & Metadata Encryption.
R10.1_1
Build Date: 2020-04-19
Changelog
Added FBE decryption support
Added F2FS support
Recovery fast charging
Bring back Aroma File Manager
Improved "onc" detection
Release Notes
No need to wipe data, no need to re-install rom. You can use this in FDE & FBE rom.
R10.1
Build Date: 2020-04-14
Changelog
Automatic decrypt of /data
Remove Patch AVB 2.0
Auto detect onc & onclite
Fix CPUs online
Fix heat on the front screen
Release Notes
No need to wipe data, no need to re-install rom, this release is for FDE.
Because stock MIUI on Redmi 7 does not support FBE.
BETA
Click to expand...
Click to collapse
R10.1
Build Date: 2020-04-09
Changelog
Initial official build
Using precompiled stock kernel
Patch AVB 2.0
Remove Aroma File Manager
Flashlight work
Using system fingerprint
Fix OTA update manual flash error
Disable treble compatibility check
Release Notes
Need more test of Encryption, Decryption, Recovery fast charge, Patch AVB 2.0.
After installing OrangeFox it is recommended that you wipe the data, cache, and system, then re-install ROM.

Reserved

FBE Support?

loco1911 said:
FBE Support?
Click to expand...
Click to collapse
For the current release yet. Maybe I will add FBE support in the next version.

Hello, I have a problem, when I want to install the miui global stock rom it gives me an error 7 and tells me that it is for the Onc model and not Onclite, but I can install it without any problem in the TWRP

loco1911 said:
FBE Support?
Click to expand...
Click to collapse
loco1911 said:
Hello, I have a problem, when I want to install the miui global stock rom it gives me an error 7 and tells me that it is for the Onc model and not Onclite, but I can install it without any problem in the TWRP
Click to expand...
Click to collapse
Thank you for telling, for the next version I will change the prop setting to "onc"

loco1911 said:
Hello, I have a problem, when I want to install the miui global stock rom it gives me an error 7 and tells me that it is for the Onc model and not Onclite, but I can install it without any problem in the TWRP
Click to expand...
Click to collapse
Which twrp did u use??

Har****@5 said:
Which twrp did u use??
Click to expand...
Click to collapse
The official TWRP 3.3.1-0

loco1911 said:
The official TWRP 3.3.1-0
Click to expand...
Click to collapse
Try using the latest version of Orangefox (R10.1_1). I added decryption support for FBE, F2FS support, and improved "onc" detection when flashing ROM.

Thank you for your amazing work!!! This recovery works perfect!

loco1911 said:
Thank you for your amazing work!!! This recovery works perfect!
Click to expand...
Click to collapse
I'm also grateful to you for reporting a bug.

hadaddarajat said:
I'm also grateful to you for reporting a bug.
Click to expand...
Click to collapse
Can this be used to flash miui based custom roms?

olayinkajnr said:
Can this be used to flash miui based custom roms?
Click to expand...
Click to collapse
You can,
but try it first if you are still in doubt.
Then give your answer here.....

hadaddarajat said:
You can,
but try it first if you are still in doubt.
Then give your answer here.....
Click to expand...
Click to collapse
Alright. So, it means it supports both FDE and FBE based roms.

olayinkajnr said:
Alright. So, it means it supports both FDE and FBE based roms.
Click to expand...
Click to collapse
try

so far i can see FDE Works but FBE does not work. i was using andriod 9 aex then upgrade to andriod 10 clean format i cant see files anymore and it says Device not encrypted/unable to decrypt FBE device when i boot into recovery

neijzen said:
so far i can see FDE Works but FBE does not work. i was using andriod 9 aex then upgrade to andriod 10 clean format i cant see files anymore and it says Device not encrypted/unable to decrypt FBE device when i boot into recovery
Click to expand...
Click to collapse
I inserted wrappedkey on fstab, so it can't decrypt FBE. I forgot to delete it. For now, use SHRP Official, I will update the orangfox more or less after the month of Ramadan.

Hello sir,
When I searched the codename for Redmi7 all the websites showed only only one name "ONCLITE"....
But why My phone codename is showing "ONC", when it's real codename is " ONCLITE ". I checked it with cpu-z, Aidax64.. And many more other apps.
Is " ONC" and "ONCLITE" Both are same can i flash "ONC" files for "ONCLITE" and vice versa.. Can i flash "ONCLITE" TWRP file to "ONC".....
Please help me....
I hope you will understand my problem and reply me as soon as possible.
Thanking you..........

Please reply me

Development [ROM][AOSP][13.0][UNOFFICIAL][sweet] CherishOS v4.8 [22/06/2023]

Features / Changelog 2023-06-22
- Fixed bootloop on 3rd party kernel flashing (give a try to included one!)
- Ripple Effect on fingerprint unlock disabled by default (laggy on sweet)
- Some sepolicies improvement
- Kernel:
-- Upstreamed to 4.14.319
-- Added initial support to LN8000 charger (needs testing)
-- Switch to strep_wise thermal governor
-- Energy model recalculated and non-efficient freqs removed
-- Added initial support to FTS_TS touchscreens (no idea if works, needs testing and feedback)
Features / Changelog 2023-06-18
- Changed base kernel
-- Older version based on Vantom 13 branch
-- Newer version based on Vantom courbet-13-KSU
-- The reason is a pair of fails with touchscreen that forced me to reboot.
-- Enabled AUDIT to see selinux auditing on logcat.
- Introduced my own TWRP.
Features / Changelog 2023-06-15
- Gapps version passes SafetyNet out-of-the-box, even using KernelSU app to root. Banking apps work fine and can be used to pay with Google Pay. Other configs (Vanilla + Gapps, or with Magisk) must be checked.
- SoftAP:
-- Add AP band preference
-- Add list to select Country Code spoof
-- Extend funcionality to QS button
- Launcher3:
-- Modded CherishOS base
-- New app icon and modified name
-- Import widget overlap from Lawnchair
-- Switch from Google's Smartspace to Quickspace
-- Option to force monochrome non-themed icons
- ThemePicker:
-- Changed to moded ProtonPlus base
-- Allow color picker on vanilla versions too
- System:
-- Removed keyguard Google's Smartspace
-- Add Omnijaws Weather API
-- Add Jelly browser on vanilla version
-- Add latest MIUI Camera from V14.0.3.0.TKFEUXM
- Selinux Enforcing
- Vendor:
-- Blobs updated to V14.0.3.0.TKFEUXM
- Kernel:
-- Updated to 4.14.318
-- Added KernelSU support

Reserved

OK, this looks better than crDroid. Plus, I won't have to use adb sideload to install it! I like that the Pixel launcher is replaced... dislike that launcher a lot! Time to give it a try.

Well... let see if you need or not adb sideload... maybe the installation instructions must be modified with user feedback.
It's known that FDE devices wont recreate /data/media folder so you cannot use internal storage to copy rom and install it.
I always recommend better to "adb push" the rom file to recovery. Also you can use USB-OTG or SDCard.
In my case, I always go unecrypted. In that case, switching roms is easier as internal storage never get lost between roms.

Also, maybe you can:
- Copy ROM to your internal storage.
- Do a factory reset (don't format data)
- Flash the new ROM (Gapps, Vanilla + Gapps, with or without DFE-NEO, with or without Magisk...)
- Format data
In this case internal storage will be recreated on first boot, and rom is actually inside.

I've modified flashing instructions to avoid adb-sideload or other methods.
Remember that you always can use SDCard or USB-OTG to avoid internal storage problems.

I never attempt to use internal storage to install ROMs, though I found today a YT instruction video for mojito on the RN10 (not RN10P) where he uses TWRP to manually recreate a data/media folder by typing it in using the "Open terminal here" functionality in TWRP, then he installs it from internal, which is bizarre because mojito has a dedicated external SD slot.
I am aware that internal data is recreated on first boot, which is another reason why I just skip attempting to install from internal SD. I was having problems on crDroid since it refused to read my external SD card which was formatted in exFat FROM THE PHONE! I had to format it in NTFS from Windows before it would read it, and crDroid is annoying in requiring adb sideload to install its ROM.
Thanks for your helpful info and suggestions. I appreciate your effort! Now I just need to give this ROM a once-over.

Interesting the way to recerate /data/media... but if you go encrypted... it will destroy it on first boot.
CRDrind problem with sdcard seems to be kernel related. So tell me if my rom works with it. Maybe I can modify config on kernel or add some drivers.

Huexxx said:
Interesting the way to recerate /data/media... but if you go encrypted... it will destroy it on first boot.
CRDrind problem with sdcard seems to be kernel related. So tell me if my rom works with it. Maybe I can modify config on kernel or add some drivers.
Click to expand...
Click to collapse
There is no optional kernel for crDroid today that I am aware of. I did notice some recent XDA kernels warn emphatically that MIUI kernels are not supported right now for some reason, and crDroid uses an MIUI kernel. (the others only support OSS kernels)
I repaired an issue with deep sleep by installing their firmware *.12 update for V13 MIUI, which thankfully remained on their *.02 V14 MIUI firmware install. Not sure if the mojito video was unencrypted, but he did suggest users turn off Screen Lock in MIUI before beginning, so perhaps it was. It won't matter if data is destroyed anyway since the ROM install procedure that he used was successful - next time, he'd have to go the "long way around" procedure again instead of just using the external SD, which works and destroys nothing on it. I never install unencrypted, and as long as I can read the external SD, I won't need to change that.

You cannot jump between different encrypted roms AFAIK, because every rom uses his metadata.

Quick question: where is the control to reverse the buttons for Back and Recent Items?

Idk man, to be honest I always use full screen gestures. I'll look but it should be on Cherish Settings.

Huexxx said:
Idk man, to be honest I always use full screen gestures. I'll look but it should be on Cherish Settings.
Click to expand...
Click to collapse
This is ALWAYS the hardest to find setting in all ROM's. crDroid hides it too. I have yet to find it!

Found.
Cherish Settings -> Buttons -> Invert 3 button navigation bar

FYI, I like that this unofficial CherishOS is keeping MIUI cam -- one of the few reasons I've stuck with Xiaomi.eu.
But does it work on Focaltech (fts_ts) touch devices?

No man... Sorry. In fact the ROM should give error when flashing thanks to an assert.

I have one idea... Maybe using stock kernel...

pnin said:
FYI, I like that this unofficial CherishOS is keeping MIUI cam -- one of the few reasons I've stuck with Xiaomi.eu.
But does it work on Focaltech (fts_ts) touch devices?
Click to expand...
Click to collapse
I've tried some attempts to make stock kernel run on my rom without sucess...
I've tried to inject it with anykernel3 but there's something on dtb that is ****ing up everything... ROM boots but a lot of FCs everywhere so no way ATM to make that work.
You must wait for proper fts_ts drivers integrated on kernel sources.
Sorry.

pnin said:
FYI, I like that this unofficial CherishOS is keeping MIUI cam -- one of the few reasons I've stuck with Xiaomi.eu.
But does it work on Focaltech (fts_ts) touch devices?
Click to expand...
Click to collapse
Huexxx said:
I've tried some attempts to make stock kernel run on my rom without sucess...
I've tried to inject it with anykernel3 but there's something on dtb that is ****ing up everything... ROM boots but a lot of FCs everywhere so no way ATM to make that work.
You must wait for proper fts_ts drivers integrated on kernel sources.
Sorry.
Click to expand...
Click to collapse
correct me if i am wrong... since sleepy kernel seems to have fts_focaltech drivers integrated (take a look at its github source below) https://github.com/itsshashanksp/kernel_xiaomi_sm6150/tree/t13/drivers/input/touchscreen
does it mean that if i flash it with any rom it will make focaltech screen work with it including your cherishos ??

Database Develop

welcome