[RECOVERY][7.0][sprout] TWRP 3.0.2-XI touch recovery | Alpha 1 - Android One (First-Generation) Cross-Device Origin

[RECOVERY][7.0][sprout] TWRP 3.0.2-XI touch recovery | Alpha 1 - Android One (First-Generation) Cross-Device Origin

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

Related

{All 2011}[DEV][Marshmallow 6.0.1][LegacyXperia] unofficial CyanogenMod 13.0 builds

Reserved

## Nightly build 20160227 - cm-13.0
* Latest cm13.0 changes
* Initial public build
* Included Google's security bulletins up to February 1
* WARNING: Switched to emulated storage. More info [here](https://github.com/LegacyXperia/Wiki/wiki/Installing-Marshmallow)
* Marked SD as nonremovable in kernel: Reduces time spent in mmc1_detect wakelock
* Removed SD eject option from settings
* Fixed charger led staying always on
* Replaced aosp Camera2 with Snap camera app
* Changed to half-resolution boot animation to reduce boot time
* Actually using lz4 to compress zRAM
* Updated yaffs to latest upstream code
* Added workaround for urushi flash. More info [here](http://review.msm7x30.org/1119)
* Added low resource fake material progress spinner to improve dex2oat time
First builds will roll based on device popularity in the next 2 days.
Special thanks to LX team and everyone who helped so far with testing and bug fixing! Functionality should be the same as cm-12.1 or better, but let us know of any issues.
Bluetooth is reported as not quite stable yet (some devices not reconnecting, turning BT on/off through settings not working reliably)

Nightly build 20160326 - cm-13.0
Latest cm13.0 changes
Included Google's security bulletins up to March 1
Fixed CVE-2015-5697, CVE-2015-8539, CVE-2015-8215, CVE-2015-7509, CVE-2015-8785, CVE-2015-7550, CVE-2016-0723, CVE-2015-1805, CVE-2016-0728, CVE-2015-7872, CVE-2016-0821
Updated f2fs to latest f2fs-stable linux-3.4.y code
Replaced low resource fake material progress spinner with simple boot dialog

mikeioannina said:
## Nightly build 20160227 - cm-13.0
* Latest cm13.0 changes
* Initial public build
* Included Google's security bulletins up to February 1
* WARNING: Switched to emulated storage. More info [here](https://github.com/LegacyXperia/Wiki/wiki/Installing-Marshmallow)
* Marked SD as nonremovable in kernel: Reduces time spent in mmc1_detect wakelock
* Removed SD eject option from settings
* Fixed charger led staying always on
* Replaced aosp Camera2 with Snap camera app
* Changed to half-resolution boot animation to reduce boot time
* Actually using lz4 to compress zRAM
* Updated yaffs to latest upstream code
* Added workaround for urushi flash. More info [here](http://review.msm7x30.org/1119)
* Added low resource fake material progress spinner to improve dex2oat time
First builds will roll based on device popularity in the next 2 days.
Special thanks to LX team and everyone who helped so far with testing and bug fixing! Functionality should be the same as cm-12.1 or better, but let us know of any issues.
Bluetooth is reported as not quite stable yet (some devices not reconnecting, turning BT on/off through settings not working reliably)
Click to expand...
Click to collapse
Hi, Mike!
CM13 it's for anzu only? Or I can find build for hallon on AndrianDC basketbuild?

RomanLarkin said:
Hi, Mike!
CM13 it's for anzu only? Or I can find build for hallon on AndrianDC basketbuild?
Click to expand...
Click to collapse
As he said "First builds will roll based on device popularity in the next 2 days."

Some screenshots please

Wow I hope coconut is 2nd most popular after anzu!!
Great work as always by @mikeioannina

How to flash anything only ADB sideload???
How can we flash anything if you can only do a ADB sideload?????????? And to flash you need some things on a storage like your sd card??????
But after figuring out the ADB download the rom works like a charm.....very good work....keep it up ....thx ...

RdH5 said:
How can we flash anything if you can only do a ADB sideload?????????? And to flash you need some things on a storage like your sd card??????
Click to expand...
Click to collapse
You can flash from ADB sideload, just use the "Apply from ADB" option why flashing

cant use flash tool only sideload?

Superrman said:
cant use flash tool only sideload?
Click to expand...
Click to collapse
You can flash the kernel using flashtool.

Ritonz said:
You can flash the kernel using flashtool.
Click to expand...
Click to collapse
and that's it? what about the "Rom.zip"?
i cant use recovery?
also i couldn't find lastet adb drivers
the description says i can use recovery
Steps required for correct installation (order is important):
1: Flash boot.img in fastboot & reboot into recovery
2 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
3: Enter recovery
4: Format /system, then /data and then /cache (Important step!)
5: Flash update zip
6: Flash gapps
Click to expand...
Click to collapse

Superrman said:
and that's it? what about the "Rom.zip"?
i cant use recovery?
also i couldn't find lastet adb drivers
the description says i can use recovery
Click to expand...
Click to collapse
You need to use recovery, so you can flash the rom.zip using adb sideload.
For the lastest adb drivers, download the android sdk or try this

Ritonz said:
Some screenshots please
Click to expand...
Click to collapse
Here is some screenshots

Well done, Android hero!

Finally the GAME in play

The rom is fast or not? Like kitkat?

EugenStanis said:
The rom is fast or not? Like kitkat?
Click to expand...
Click to collapse
It is as fast (maybe more) as kitkat. But make sure you have a fast sd card.

What's the difference between this new build and the one from AdrianDC from the beginning of this month?

[MOD] [hydrogen] TWRP 3.1.0 + MultiROM v33 (NO-KEXEC) [UNOFFICIAL]

{
"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

[8.1.x][OFFICIAL][WEEKLIES] CarbonROM | cr-6.1 [tissot][11-08-18]

RESERVED
Thanks to: Carbon Team, Abhishek, TEAM OREO and all the testers who tested my builds
ROM Changelogs
Device Specific Changelogs:
08-05-2018:
*Initial Build
15-05-2018:
1.Enable Camera1 API for legacy targets.
2.Updated blobs to 8.1
3.Updated vendor blobs
4.Updated cam blob list
5.Overwrite mac address if config file exists
6.Ship and enable atfwd daemon
7.Enable battery light settings for tissot
8.Ship with a different kernel(based on void kernel)
9.Overall changes in source and trees to improve performance and experience
22-05-2018:
* Upstreamed Kernel to 3.18.109
* Compiled kernel with clang
* CTS Mismatch Fixed
* Overall changes in source and trees to improve experience
29-05-2018:
* Carbon Upstream
* Upstreamed Kernel to 3.18.110
* NavBar Enabling/Disabling issue fixed
* Fixed USB tethering not working for users
* BT Mac should now be readable
* Added Missing atfwd dependency to DT and Vendor
* Adjust MODEM_PA_MITIGATION and MODEM_PROC_TEMP_MITIGATION as per stock mido
* Generated thermal-engine.conf
* Added displayconfig to vendor
05-06-2018
* Carbon Upstream
* Merged latest June security patches
* Upstreamed Kernel to 3.18.112
* Merged latest CAF tags
* gpt-utils: fix block path for non ufs devices
12-06-2018
*Set GPU and CPU Max speed to stock speeds on boot
*Camera: Only link and use vendor.qti.hardware.camera.device if specified
*Camera: CameraHardwareInterface changes to support Extended FD
*audiopolicy: Add AudioSessionInfo API
05-07-2018
* Carbon Upstream
* Merged latest July security patches
* Upstreamed Kernel to 3.18.114
* Merged latest CAF tags
*drivers: prima: Update to CAF Tag LA.UM.6.6.r1-09000-89xx.0
* fixed bluetooth crash on boot
11-08-2018
* Carbon Upstream
* Merged latest August security patches
* Upstreamed Kernel to 3.18.116
* Merged latest CAF tags
* drivers: prima: Update to CAF Tag LA.UM.6.6.r1-09200-89xx.0
* Update V1.0 media profiles
* Enable display always on feature
* Set Bootanimation to half-res (for faster boot)

*RESERVED*
Join the Carbon ROM-Tissot Support Group
&
Screenshots

Tez working?

sudipta08sarkar said:
Tez working?
Click to expand...
Click to collapse
Yes

Can you list out what's working and what's not? And looks like it supports OTA updates ?

Does this ROM have the function to prevent app from using mobile data completly?

Wow!, can't believe in my eyes!
Finally, carbon for A1!, thanks u guys!
The only reason i'm still love and use my Mi4 is that it running Carbon, battery life and performance is superb!
Downloading now
(I will report any bugs with logcat)

GVN.Gallus said:
Wow!, can't believe in my eyes!
Finally, carbon for A1!, thanks u guys!
The only reason i'm still love and use my Mi4 is that it running Carbon, battery life and performance is superb!
Downloading now
(I will report any bugs with logcat)
Click to expand...
Click to collapse
am using rom, no bugs as of. now, selinux is not fully functional though, but its initial build, great work, fan of carbon rom

AkashAlien said:
am using rom, no bugs as of. now, selinux is not fully functional though, but its initial build, great work, fan of carbon rom
Click to expand...
Click to collapse
What do you mean "selinux is not fully functional"?
I'm downloading with very slow speed, about 20kbps , test both on 4G and wired internet, took me 14hrs to finish

AkashAlien said:
am using rom, no bugs as of. now, selinux is not fully functional though, but its initial build, great work, fan of carbon rom
Click to expand...
Click to collapse
What do you mean selinux is not "fully functioning". It is set to enforcing and everything is working fine. What else do you mean?

Can we make feature requests here? If yes. Is it possible to add inbuilt themes like many other ROMs have?

What is this fix for ??? What does it fix ???
Why it won't flash without ??? Didn't see that before.
Are you able to suppress caller ID with this rom or does it end to network or simcard error ?

coremania said:
What is this fix for ??? What does it fix ???
Why it won't flash without ??? Didn't see that before.
Are you able to suppress caller ID with this rom or does it end to network or simcard error ?
Click to expand...
Click to collapse
"Carbon ROM Official builds are signed with custom keys like our stock ROM so inorder to flash the ROM it needs to verify the key for which though can be surpassed if we update the TWRP( it will take for me to do that) so, that fix.zip file replaces the key and adds OTA support to the ROM." ~ This is what developer told me when I asked him the same question.
And I didn't understand the suppress caller ID part. Can you elaborate?

rahulrishi said:
"Carbon ROM Official builds are signed with custom keys like our stock ROM so inorder to flash the ROM it needs to verify the key first which though can be surpassed if we update the TWRP so, that fix.zip file replaces the key and adds OTA support to the ROM." ~ This is what developer told me when I asked him the same question.
And I didn't understand the suppress caller ID part. Can you elaborate?
Click to expand...
Click to collapse
Thanks for info.
For the caller id, open your phone app and try to suppress your number on outgoing calls. On all custom roms I get Network or simcard error and the option stays grey. It only work on every stock rom so far. Doesn't matter which phone app i use, doesn't matter which gapps I flash.

Navigation bar isn't working

Thanks for the rom. Does it have a true OTA or does it only download a zip we must then flash via TWRP?
Also, is it possible to add Live Display instead of Night light?

neyvermore said:
Thanks for the rom. Does it have a true OTA or does it only download a zip we must then flash via TWRP?
Also, is it possible to add Live Display instead of Night light?
Click to expand...
Click to collapse
It has OTA, but he said he needs to fix TWRP first to support OTA.

most awaited rom finally on the ground.
Thanks CarbonRom team.
Edit-
After flashing the ROM it's not boot normally I forced it by pressing power key after it boot it's not detecting sim card so I can complete the setup wizard I'm only network data user no WiFi. I did clean flash wipe system wipe data wipe delvik and art cache then flash fix.zip, rom.zip, twrp.zip reboot to twrp flash gapps then mazisk 16.0.
I did flash mazisk first then gapps but no luck please correct me where I'm wrong

coremania said:
Thanks for info.
For the caller id, open your phone app and try to suppress your number on outgoing calls. On all custom roms I get Network or simcard error and the option stays grey. It only work on every stock rom so far. Doesn't matter which phone app i use, doesn't matter which gapps I flash.
Click to expand...
Click to collapse
Oh no idea about that, never used it. I will try and let you know

[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

[ROM][10.0][UNOFFICIAL] LineageOS 17.1 [RMX1971] [19/11/2020]

Updates
1911
19/11Changelog
- Updated security patch
- Added some smoothness tweaks in ui
- All Audio Issues Fixed
- Lineage source upstream
- Improved app opening speed
- Fixed ui shutters
- Added VOOC Charging support
- Some misc improvements
- More fixes and improvements.
1510
15/10 Changelog
- Enforceing Build
- Source Upstream
- Fixed audio delay on audio players
- fixed audio always high on incall
- fixed some other issues with audio
- Kernel Upstreamed to 4.9.237
- Using coral R fp for safetynet
- Several fixes and improvements
- Improved wifi stability/speed
- Updated Radio and CNE blobs from LA.UM.8.6.2.r1-08400-89xx.0
- Added KharaMeParts
- Fixed cast crashing after some time
- Fixed focus not working in camera apps
- Fixed high exposure while trying to scan barcodes in apps like whatsapp, gpay etc
- KCAL Support
- Vibration control inside kharaMeParts
2008
20/08 Changelog
- Enforceing Build (one more step to offical)
- August security patch
- Android-10.0.0_r40 -> android-10.0.0_r41
- Source Upstream
- Built kernel with clang
- Added FM
- Fixed cts failing(U need to enabled magisk hide)
- Updated camera blobs to Q
- Updated audio blobs to Q
- Updated media and audio configs
- Removed unnecessary blobs
- Fixed wifi display crashing
- Kernel upstreamed to 4.9.227
- Several performance improvements & misc changes
- F2FS Support (you can format data and cache to f2fs now)
0308
03/08 changelog:
- Moved to RUI Base
- source upstreams
- Kernel based on Realme 10 Kernel Source
- qcacld-3.0 upstreamed to LA.UM.8.8.r1-07300-SDM710.0
- fw-api upstreamed to LA.UM.8.8.r1-07300-SDM710.0
- qca-wifi-host-cmn upstreamed to LA.UM.8.8.r1-07300-SDM710.0
- Kernel Upstreamed to .226 tag
- Updated some blobs to realemui
- Enabled aosp bluetooth hal v2
- Fixed mic
- July security patch
- Moved audio panel to left side
- Updated Carrier Settings from Coral RPB1.200504.018 6520161
- Updated Blobs to RealmeUI
- Improved app launching speed
- Fixed Random reboot while device kept idle
- Fixed audio crashes and other audio issues
- Updated aptX blobs
- Fixed Vowifi and Vilte(Both should be working fine now)
- Kernel Upstreamed to LA.UM.8.8.r1-07600-SDM710.0
- Builts kernel with clang
- minior bugs fixes
- preformance improved
- Improve dt2w
- overall improments
1704
16/04 change log:
source upstreams
minior bugs fixes
preformance improved
kernel changelog:
Wakelocker is here
overall improments
1805
Update:-
- Sorce side upstream
- Move from android-10.0.0_r33 to android-10.0.0_r35
- Kernel upstream to 4.9.223
- Kernel compiled with Clang 11.0.1
- SELinux Enforcing.
- Updated May coral fingerprint for safety net.
- Fixed mic issues while gaming.

F&Q
1) ROM is bootlooping?
Use the right way to boot it and keep in mind theres 2 variant of Realme 5 Pro
1.RMX1971EX (this one which i test my roms on it)
2.RMX1971 (Q)
both have the same hardware but it not the same software as the some changes in storage,
but both need this steps to boot successfuly on your phone.
Curious_guy said:
From TWRP i followed the steps bellow.
1) Wiped everything
2) Installed C.05 and rebooted to recovery (didnt start on C.05 RUI)
3) Again wiped everything, flashed 20200820 (latest build) and bitgapps(Recommended).
4) Then reboot to system.
Click to expand...
Click to collapse
Thanks for Curious_guy sharing his experiance for the other users to follow
P.S: MAKE SURE U DONT USE OPENGAPPS and use the recommended bitgapps for avoiding anyway of bootlooping until next annoucment
2) What is Unified Realme SDM710 (Realme X,XT,3pro,5pro) Project ?
Unified Realme SDM710 is a project for the SDM710 phones from realme to make it easier for users to get update faster
HOW ?
in an easy way to explin it
its a rom it can be flash and work in [Realme X,XT,3pro,5pro] this way it will be get faster updates for all in the same way.
right now its in beta stage with a booted rom worked for the four roms but there a lot bugs to be fixed before any public release.

installed it so far so good gonna try battery performance and games

Hey, can I flash this ROM after I've updated to Realme UI? Thanks!

sansgood said:
Hey, can I flash this ROM after I've updated to Realme UI? Thanks!
Click to expand...
Click to collapse
no u have to flash coloros first (you dont have to boot it just flashing it will do the job) then flashing this rom

Is fast charging working on this rom I have installed it and installed ampere app to measure it says 3520mA
No clue if its fast charging

whats New
Is there chance of getting official support from lineage os

kemo12533 said:
no u have to flash coloros first (you dont have to boot it just flashing it will do the job) then flashing this rom
Click to expand...
Click to collapse
The fact is, I didn't find any way to downgrade RUI to Color OS. Is there some tutorial for the european version? Big thanks.

sansgood said:
The fact is, I didn't find any way to downgrade RUI to Color OS. Is there some tutorial for the european version? Big thanks.
Click to expand...
Click to collapse
now u can unlock the bootloader u can flash twrp or anyonther recovery then flash coloros

kemo12533 said:
now u can unlock the bootloader u can flash twrp or anyonther recovery then flash coloros
Click to expand...
Click to collapse
I have already my bootloader unlocked and twrp working, but i cant find anywhere to download Color OS firmware for Realme 5 pro. In realme website I can only download the RUI one.

killerhaha100 said:
Is fast charging working on this rom I have installed it and installed ampere app to measure it says 3520mA
No clue if its fast charging
Click to expand...
Click to collapse
As far as out charger is 4 Ampers, I would say yes.

sansgood said:
I have already my bootloader unlocked and twrp working, but i cant find anywhere to download Color OS firmware for Realme 5 pro. In realme website I can only download the RUI one.
Click to expand...
Click to collapse
u can see and download it from here , make sure u select and download RMX1971EX_11_A.17 or earlyer builds

I managed yesterday to downgrade and flash this one and it works like a charm. Very smooth and stable. Thanks for sharing and for the help!

dude this is absolutely great. do you plan releasing updates for this in the future? because it seems like its the first release of 17.1 so there are still a lot of fixes to be done yet by the lineage devs.

sansgood said:
I managed yesterday to downgrade and flash this one and it works like a charm. Very smooth and stable. Thanks for sharing and for the help!
Click to expand...
Click to collapse
Brother,
Can u tell me the procedure to downgrade? now i m in Color OS 7 c02? and is it possible to Realme Ui from custom Rom?

vistaabalaji said:
Brother,
Can u tell me the procedure to downgrade? now i m in Color OS 7 c02? and is it possible to Realme Ui from custom Rom?
Click to expand...
Click to collapse
If you're in Color OS then you have the right firmware and you can flash this rom via TWRP. Make sure you wipe your data and cache before flashing. If you get into recovery after first reboot (could happen if you are in a rom with data encryption), format data and reboot again.

sansgood said:
If you're in Color OS then you have the right firmware and you can flash this rom via TWRP. Make sure you wipe your data and cache before flashing. If you get into recovery after first reboot (could happen if you are in a rom with data encryption), format data and reboot again.
Click to expand...
Click to collapse
sorry, i m in Realme Ui, can you provide me the steps/procedure to downgrade from Realme Ui to Color os 6.

vistaabalaji said:
sorry, i m in Realme Ui, can you provide me the steps/procedure to downgrade from Realme Ui to Color os 6.
Click to expand...
Click to collapse
Yes, of course. This are the steps I followed. I assume you haven't an unlocked bootloader and TWRP installed. If so, you can skip the 3 first steps.
1 - Unlock bootloader following this tutorial. https://c.realme.com/in/post-details/1184734239149522944 . If you face any issue when entering the commands in fastboot mode I would recommend connecting the usb to another port of your computer and try again.
2 - Flash TWRP. You can find a guide here https://forum.xda-developers.com/re...de-newbie-resource-thread-bootloader-t3995285 . It is pretty simple, in summary you must flash the TWRP image and the VBMETA image in fastboot mode.
3 - Enter in TWRP, make a backup of all partitions.
4 - Download ColorOS firmware from here https://realmeupdater.com/downloads/archive/RMX1971EX/ (thanks kemo12533). I downloaded the RMX1971EX_11_A.17 version. You will get an OZIP file that you must copy to your phone. I would recommend copying it to an external SD card.
5 - From TWRP, wipe system, data, cache and dalvik cache. Press install and select the ColorOS ozip you moved to SD.
6 - Press reboot system and you should boot into color OS. If your phone reboots into recovery mode again, format data (keep in mind that this will erase everything in your phone storage).

Thank you very much for your effort. May I ask if this will work with european models? Are there really no known issues in the very first release? Will this be added to the official download lists?

Database Develop

welcome