> Attention!

We strongly recommend to readRules section "Android - firmware"

New threads need to be created only inroot partition! In the future, they will be processed by moderators.



Xiaomi Mi Max 2 - Unofficial firmware
What kind of firmware and TWRP do you prefer
Android 7.1_NOUGAT
LOS 14.1 [ 37 ] ** [11,25%]
RR 5.8.3 [ 35 ] ** [10,64%]
AOSP Extended [ 58 ] ** [17,63%]
Viper [ 7 ] ** [2,13%]
AOKP [ 4 ] ** [1,22%]
AICP [ 4 ] ** [1,22%]
Xenon [ 9 ] ** [2,74%]
crDroid [ 9 ] ** [2,74%]
Dot [ 2 ] ** [0,61%]
Other [ 132 ] ** [40,12%]
Android 8.1_OREO
RR [ 39 ] ** [11,85%]
LOS [ 25 ] ** [7,6%]
Xenon [ 6 ] ** [1,82%]
MSM [ 3 ] ** [0,91%]
Dot [ 4 ] ** [1,22%]
AOSP Extended [ 43 ] ** [13,07%]
Bootleggers [ 5 ] ** [1,52%]
Pixel Experiens [ 36 ] ** [10,94%]
Havoc [ 22 ] ** [6,69%]
Other [ 115 ] ** [34,95%]
Android 9.0_PIE
Havoc [ 91 ] ** [27,66%]
RR [ 19 ] ** [5,78%]
LOS [ 21 ] ** [6,38%]
Bootleggers [ 3 ] ** [0,91%]
Pixel Experiens [ 44 ] ** [13,37%]
Arrow [ 14 ] ** [4,26%]
Posp [ 6 ] ** [1,82%]
Viper [ 4 ] ** [1,22%]
AOSP Extended [ 30 ] ** [9,12%]
Other [ 83 ] ** [25,23%]
TWRP
TWRP by rkmadotra [ 20 ] ** [6,08%]
TWRP Red Wolf [ 15 ] ** [4,56%]
TWRP by ashwin [ 4 ] ** [1,22%]
TWRP official [ 80 ] ** [24,32%]
TWRP by NFound [ 11 ] ** [3,34%]
TWRP by brigudav [ 8 ] ** [2,43%]
TWRP by Codered [ 5 ] ** [1,52%]
Orange fox [ 38 ] ** [11,55%]
Pitch black [ 4 ] ** [1,22%]
TWRP by greeshan [ 11 ] ** [3,34%]
TWRP_MOD by sanek-creed [ 22 ] ** [6,69%]
TWRP_mod_ pie [ 39 ] ** [11,85%]
Other [ 73 ] ** [22,19%]
Total votes: 329
 



Rep: (3424)
Xiaomi Mi Max 2 - Unofficial firmware
PictureXiaomi Mi Max 2
Description | Discussion � | Purchase � | Accessories � | Marriage and Repair � | Camera talk � | Power consumption (autonomy) � | Modification and decorations � | Mi Account � | Unlocking XIAOMI bootloaders � | FAQ of general instructions and recommendations for Xiaomi devices | MIUI firmware � | Custom kernels � | Unofficial firmware �


mini - F.A.Q.

Important information!
  • Carefully read the cap, we study the necessary information. We use Picture
  • Before any manipulations with the device, it is recommended to dobackup efs
  • Be sure to make a full backup before any manipulations with the device!



Drivers and Utilities
Drivers
Utilities

Tools

Firmware
7.1.2_Nougat
8.1.0_Oreo
9.0_Pie
10

Ports
Reviews

Project treble
Instructions
TWRP / ROOT
GApps
Useful
miscellanea
Polls archive
Attached Image
Attached Image

Attached Image

For questions about filling the caps, contact the curator of the topic. sanek-creed

Post has been editedsanek-creed - 13.11.20, 08:04
Reason for editing: HavocOs



Rep: (1875)
M
dantist_140 Shot from supervision theme for personal request.


Posted on 06/04/2018, 15:51:

M
destroyer71 Appointed by the curator of the topic. Please love and respect.



Rep: (515)
Red wolf recovery mod
Maud cut test "of pirated applications," well, support Ntfs
Installation: through twrp well or via fastboot
Attached filered_wolf_mod.img.(33.8 MB)

Link toxda (Original version without Fashion)

Post has been editedsanek-creed - 28.01.19, 15:22



Rep: (18)
Faced a problem on AEX from EVA (April 25). If in the settings put the closing of applications to hold the back button. Go to hours and hold the button back until the application closes, then the alarms will not call. Even if you open the application after that, the alarms will not be ringing anyway. To start them, I had to shake them all.

I do not know, maybe it should be some kind of bug or it should be attentive :)



Rep: (3019)
mini - F.A.Q
Introduction
If you have a desire to establish a custom firmware, first of all it is worth thinking, and is it worth it? Why do you personally need it? What do you want to change in your device? Pluses have a lot of custom Roma, but ... there are cons. If you still want to deviate from the official framework in the use of the device, please remember one thing - all you have gathered to do, you should do a thoughtful, and not to rely on whose one would have any opinion. No one, besides you, is not responsible for what you do with your phone.
Select firmware
Decided still install custom ROM? Now a new dilem. Choosing a big thing to put? How to choose his firmware? In this question you can only tell you, and not recommend. What is the best firmware? The answer is banal. That that you yourself You consider the best, and the one that is most consistent and fully working on your specific device. No one knows what the soul lies with you, no one will give guarantees of the efficiency of one or another Roma in your device. Read reviews. Do not save extra half an hour to read the topic. It is impossible to stupidly poke your nose in the medium of Customs, where you can join. You need to at least understand what you want and what you do. The path to searching for your ROMA thorny. Everything is relative. That's when you try everything, only then can judge the pros and cons of firmware.
In order to constantly not sew the device in search of the best firmware, you can use the DualBootpatcher utility. Link and instructions in the header. Plus this method - you always have a working firmware on the device.
PS ... if the main firmware is 7.1 (Nougat), then the second firmware cannot be installed 8.1 (OREO). DBP costs. If the main 8.1, then the second one can put any
Installation
The decision is made, the ROM is selected. Now you need to install the chosen. We read the header, follow the instructions for installing TWRP (if not yet). Remember one important thing - before any manipulations with the device, be sure to make a backup. The priority backup, which should do everyone, be it an advanced guy or a beginner user - EFS backup. This is your IMEI, SN. It is easier to spend several minutes than later to search for recovery options.
Who is not familiar with the custom rekaveri worth readingTWRP recovery FAQ
Here the instructions for creating a backup and installing firmware
Xiaomi Redmi Note 4X Snapdragon - Informal firmware (Post vovcik3 # 65756590)
Attitude
I would like to pay attention to the posts of this type - "promised to do and there's nothing," "for which they make such firmware" and I will explain. No developer, modulated any of us should not. They all do on his bare enthusiasm. We spend time, traffic, nerves so that the rest can use the fruits of their works. To write such claims ... It is necessary at least to conclude a certain agreement. So that both sides are interested. For example, pay work (because we all work and get money for it). In this case, you can require something. And with the current situation, you can only ask for something to do and fix. I would like to treat someone else's work with respect.
Basic terms and concepts
ROOT rights - This is the Administrator account, only under Android. An administrator can do anything, unlike a simple user - not an administrator. Root rights give full control over your system.
Backup - Saving all parameters and settings for the purpose of recovery in case of data loss.
Recovery - System and network section comprising means for firmware, backup, restore from a backup, and more. In our case it TWRP. FAQ on TWRP
Nandroid backup - A full backup of the system with the ability to raise the phone from any state in case of failure in work.
Dalvik cache - Intermediate fast access buffer that carries the information most likely to be requested (in this case created by the Dalvik virtual machine). Simply put, Dalvik Cache is the result of optimization of the most frequently launched programs by the Dalvik virtual machine.
Full Wipe - Full reset settings. All installed applications, multimedia data, cache + dalwick cache are deleted and all system settings are reset.
Bootloop - Cyclic boot, this is when the OS boot, in our case AndroidOS, does not boot to the end, the bootlogo (boot image) is shown endlessly.
Cyclic reboot of the device, which occurs during the boot phase due to the inability to boot completely. (in translation, boot is boot, loop - loop, loop, etc.)
Busybox - is a set of console utilities for Linux systems. Essentially needed by programs that require root-rights for proper functioning.
Deodex - APK system files together with them have "in the load" file with the same name and extension .odex. With their help, it is estimated that you can save any place. Deodexing means that you convert this ODEX in DEX (the same file stored inside APK) and shove it back to APK. This allows us to freely replace systemic applications without worrying about Odessa. In custom firmware, the ODEX files from the firmware were removed from the firmware, speaking the information contained in them inside the APK files, thereby decreasing the firmware size and most importantly - now the APK files themselves can be changed as you like, it does not affect the operation of the system. This is called deodex.
This is good - in the deodexed firmware, you can easily open the APK file with the archiver, change the resources in it (pictures, etc.) and return the changed file to a place in the firmware.
Error 7 in recovery
Description
Quite often, when installing custom firmware (in particular LineageOS) on the rutted smartphones or Android tablets, you can encounter "error 7". Error 7 in TWRP Recovery occurs when there is no name of the model of your phone in the firmware script, or there is a name, but the firmware is intended for a different modification of the device (many models of smartphones have several versions - for example, to work in networks of different operators, and it is necessary to install Your "firmware).
Behind the correct selection of the firmware is responsible for the "Asserts" protection mechanism. The script checks the device model and the firmware version of the RO.Build.fingerPrint system variable requested from the Recovery itself. In the case of coincidence of the codes, it issues a confirmation of the level legitimacy, and when the absence (absence) does not confirm the possibility of this action. As a result, you see an error 7, but this device does not turn into a brick. There are such cases when even if you choose the firmware for your device, you still receive an error message 7. They are extremely rare and associated with the firmware developer error.

Solutions :
1: I am a fresh firmware
2: Change TWRP
3: Makes
#
Or delete a string in a script with a device check (first)
Attached Image
. The script can be edited directly on the device without unpacking (Total Commander copes with this). Located in the folderMETA-INF / COM / Google / Android / Updater-script
Why deleted my post
According to the rules resourcesavagemessiahzine.comBefore writing a post in a thread, you should familiarize yourself with the header, FAQ, perform a search by subject, and only then, if there is no answer to the question of interest, ask it in the thread. If your message is deleted, then the answer to your question is in the header, topic, FAQ, or the question is offtopic for this topic. If you are interested in the reason for deleting a post, then you can contact the curator of the topic in QMS to get an explanation about the deletion of your message.
The points of the rules that must be carefully read and executed before writing a message in the subject:

4.1. Before creating a new topic or message, you should carefully read the rules adopted in this section.

4.3. Do not rush to create a theme message. It is very likely that your question was discussed earlier, or there is a topic for discussion of your device. Do not forget to pay attention to the section "Important" in the appropriate section of your question. Use the search. In this case, consistently perform a search for several suitable keywords. For example, if your question is related to the use of Bluetooth on the Qtek S100, you should look for the words “Bluetooth†and “Qtekâ€.

4.4. If you find a topic that fits your subject, do not immediately write a message in it. Perhaps your problem has already been discussed, and a solution has been found. Use the "print version" and search by keyword in it. Be sure to read the topic header - it contains useful information, especially for you.

4.7.1. When answering an existing topic, try to formulate a question or answer so that it is understandable to the other forum participants. Avoid flooding, philosophizing, lyrical digressions.

And also, according toRules section firmware android:

3.1. Before asking a question, read the FAQ on the Device and the Firmware (the link to the FAQ is located in the header of the discussion thread of the device firmware), if there is one. If you did not find the answer to your question in the FAQ for your device, or if it is missing, then look for similar questions in the general Android FAQ and only if there is no answer ask. Users asking questions, the answers to which are listed in the FAQ can be punished at the discretion of the moderator (PO from 1 to 3 days).
Doze mode for google services
In some firmware by default, Google services "do not save" battery charge. "Kindly" will provide them with this opportunity (in order not to "bother" a device once again).
Flash the archive from recovery without wipes
Attached fileEnable_Doze_Google.zip(148.27 KB)

Attached fileOREO_EnableDoze.zip(148.5 KB)
Password removal
Flash the archive from recovery without wipes
Attached fileDelete_parol_twrp.zip.(142.2 KB)
md5
Check the integrity and authenticity of files by calculating the checksum. Sometimes it is convenient to check the hash of the downloaded firmware to make sure that it does not be bought when downloading.
Attached fileHashTab_v6.0.0.28_Setup.exe(1.09 MB)
Check MD5 on Windows
Hash droid Check MD5 on Android
"Dumps" simcart
On custom firmware, some have problems with a periodic "dump" simkart, i.e. At times there is no connection, there is no Internet. "Treatment" is very simple:
We go toSettings / Six Settings Sims (Select Six 1 or 2, on which problem arises). Turn off the checkbox on the contrary 4G / LTE mode (Volte) . Further - The access point (APN) . Select the point of access, the values ​​of the value under your operator. Or make a screenshot of the APN settings while being on the meow, then correct the settings of the APN on the custom. In the case of iota, you need to change 3 values ​​to such
Attached Image
Reboot is not required
E: Unknown Command
When installing in TWRP patches / fixes and other things, some observe an error (one or two (depending on the version of the recovery) of the red rows) E: Unknown Command
The bottom line is that the binary file (Update-Binary), which is on the wayMETA-INF \ com \ google \ android Compiled to install Android and contains a new command (installation time log), which is not supported by some versions of TWRP.
This command, in terms of the correctness of the installation of the firmware, does not affect anything. Seeing a similar "error" you can not worry and calmly reboot into the system. Everything was installed correctly.
You can change TWRP to newer, or replace the binary on the older
How to enable safe mode
Press the power button until the Shutdown menu. In this menu, tap and hold your finger click "Restart." Confirm your selection in the pop-up dialog box.

Now that you are booted into safe mode, you can make your own eyes how the Android in its original form and how it inhibit you installed the utility, launchers, icons, background programs and other unnecessary elements. After making the changes you need by removing disturbing the normal operation of the program or restoring the default settings, you can go back to normal mode. To do this, simply restart your device.

This method is simple and fast method of treating the problems of the operating system Android, which sometimes helps to avoid more radical intervention - a complete reset and flashing.
Fasting during filling

Post has been editeddestroyer71 - 05.11.18, 14:02



Rep: (26)
Good day to everyone, guys, who will tell on the issue of volume? Put the last LINAGE 14.1, switched from 9 global. So, the volume of the spoken dynamics is simply "Ringing the ear" which is big, used the Destroyer71 instruction, but changing the value of Handset and even any other RX1, etc. The sound remains the same where the dog is buried? The phone has nasty reloaded, the right to file is, where to dig?
The story has a continuation, installed Hard Kernel hoping to fix it - the volume is the same, I tried to change it in
Faux Control Sound and Kernel Auditor - no result. Now the volume of the spoken speaker does not change at all - consistently high



Rep: (369)
So AEX 5.5 Oreo from today.
According to the first impressions, all the main functions are working, except for adjusting the volume when talking (but as already written above the volume sufficient for comfortable use).Dynamics when playing music are not hoarse.What else noticed from the bugs is not a working LED indicator. So it seems like the most suitable firmware on the halo from now available. Not counting small bugs, it seems to be used for every day.

What I liked that in addition to a large number of settings, there is a separate selection of a variety of fonts in the menu. I still test further.

With sound, all the same hurried. When I checked on the built-in player, the sound was normal (with audio effects off). But only I was worth installing a third-party player, as the sound immediately became as terrible as on the other OREO firmware. Sadness ...

Post has been editedDotsmaster - 09.06.18, 12:25
Reason for editing: Completed



Rep: (11)
Who will smugget as in RR Oreo disable kids kotoriya all vrummes when the phone is blocked. Thank you



Rep: (310)
* Resident evil , Screen / Automatic screen on / always enabled - Disable. You can only leave the inclusion with new ones.



Rep: (272)
Method is found how to reinitive LED indicator on the firmware.
Using Root Explorer (APK will be attached) Copy the init.qcom.rc file (will be attached) along the way with the replacement! VENDOR / ETC / INIT / HW, set the rights 644 or RW-R-R-, then reboot, and voila, ice indicator works. (File file with Pixel Experience, and the method of EVA0034)
Note: The file is laid out in the APK format as in the .rc format does not load before moving to the system to remove .apk to be .rc
Attached filerootexplorer_v4.1.7.apk(3.34 MB)

Attached fileinit.qcom.rc.apk.(20.84 KB)



Rep: (272)
MSM Xtended X10 (8.1 Oreo) Official

Based on GZOSP
Requirements
  • TWRP Recovery (custom recovery)
  • Installation .zip archive
  • .zip archive with gapsami
  • Straight arms
Changes
1. Holded
Update to x8.5:
Fixed screen lock to unlock the problem.
Rounded point of view in view mode.
Full EXFAT support.
Fixed loading error.
QC has improved the lack of need for any Magisk module.
Added USB fast charge.
Added support for Microg
Changed some names about names. Now the release version will appear in the "About Phone" section
Added some improvements in camera parameters
Added Flashlight Blink on Call Options
Added Xtended Platlogo. Click several times on ABOUT XTended & Build Number for Entertainment
Added Complete OMS Support for Subpita
Fixed Size Synchronization Lock N Font Reset Error
Aligned all PowerMenu icons in accordance with the accent
Fixed Systemui FC option for Simcard Option
Added information about security AOSP in patch (about phone)
Fixed action Lockdown in PowerMenu
Added Shamsung fonts and another option blocking
Added Xtended, Deepnight and Simple Analog Clock for Lockclock
Added some settings for better screen turn on. Now the use of the screen will be 25-30 minutes for 1% of the battery
Added Magisk in the main settings
Added Flip to Mute n Activate the DND function when calling (Dailer settings)
Added Noisy Notification Options
Added 3 additional devices in official devices - LEECO MAX2, MI MAX 2, Redmi Note 5 | 5 Plus.
Some improvement within and system
Known Issues
1. It changes the volume when telephone conversation 2. DublTap does not work for inclusion (is treated with ISCLE in Telegram). 3. Speaker wheezing
Screenshots
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Installation
  1. Drop the .zip archive onto the phone
  2. In the recovery we do:
    • Wipe Data
    • Wipe cache
    • Wipe Dalvick Cache
    • Wipe System
  3. Flash archive: Install .zip ->Install Custom.zip
  4. Flash GAPPS (if needed)
  5. We flash the root Magisk / SuperSU (if necessary)
Download
Feedback
Firmware fast, settings are much but not translated into Russian. Lags did not notice. Battery will not say. Who knows English and you need a lot of settings can try
Originaltheme (a source)

Post has been editedNikitel - 23.09.18, 11:50
Reason for editing: update to x10



Rep: (515)
Destroyer71 @ 06/16/2018, 20:36*


XenonHD_8.1.
Reloaded because From the google file is removed.

Post has been editedsanek-creed - 17.06.18, 20:20



Rep: (272)
Resurrection Remix_v6.1.0 - V.6.2.0 (8.1 Oreo) Final

Based on Lineageos
Requirements
  • TWRP Recovery (custom recovery)
  • Installation .zip archive
  • .zip archive with gapsami
  • Straight arms
Changes
1. Holded
Known Issues
1. It is changing the volume when telephone conversation. 2. It works LED indicator. 3. It works correctly with an SD card. 4. In all applications sees a fingerprint.
Screenshots
Attached Image
Attached Image
Attached Image
Attached Image
Installation
[List = 1] [*] Skip .zip archive on phone
[*] In recovery we do:
  • Wipe Data
  • Wipe cache
  • Wipe Dalvick Cache
  • Wipe System
[*] We flash the archive: Install .zip ->Install Custom.zip
[*] Sewn GAPPS (if necessary)
[*] We flash the root Magisk / SuperSU (if necessary)
Download
Feedback
Stable and fast firmware with a bunch of settings (which work correctly!) I did not notice the lags, the battery holds adequately, I worked fast. On daily use will go. ;)
Originaltheme (a source)

Post has been editedNikitel - 23.09.18, 11:45
Reason for editing: Upgrade to 6.2.0



Rep: (272)
Attached Image
AospExtended
5.7


✔️ Status: Official
Based on: AOSP
SA source:XDA
AVersion of Android: 8.1 Oreo
PAssembly author: EVA0034

❗️ Known bugs
  • Volume does not change when telephone conversation
  • Speaker wheezing
YScreenshots
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
^ Installation
  1. We put TWRP
  2. We make wipe partitions / dalvik / system / cache / data (internal memory optional)
  3. Reboot the phone and go back to TWRP
  4. We sew firmware & Gapps / Magisk (optional)
  5. Reboot into system
& List of changes
09.07.2018:
Upgrade to 5.7:
- Build Kripto from the source;) [EVA0034]
- MSM8953-COMMON: Delete Enable_CPusets [EVA0034]
- MSM8953-COMMON: Enable download and system server Dex-Preopt [EVA0034]
- MSM8953-COMMON: Create LiveDisplay Hal [EVA0034]
- MSM8953-COMMON: Add persist.sys.usb.config.Extra [EVA0034]
- MSM8953-Common: Config.fs: Posted by Wake_Alarm Capabiltiy [EVA0034]
- MSM8953-COMMON: Allow Syscall MediaExTractor Marmap [EVA0034]
- MSM8953-Common: Add Policy SECEXTP MediaExTractor [EVA0034]
- initialize USB state [EVA0034]
- Camera2 API [EVA0034]
- MSM8953-Common: Correct trusted face with open Gapps [EVA0034]
- MSM8953-COMMON: Add facial detection support [EVA0034]
- Mido: KCal: Install a specific RGB to display Tianma [EVA0034]
- MSM8953-Common: Low backup delay delay switching to reduce power consumption [EVA0034]
- MSM8953-COMMON: Set the CPU option for Cortex-A53 [EVA0034]
- MSM8953-COMMON: Enable download and system server Dex-Preopt [EVA0034]
- MSM8953-COMMON: HWUI: Compile for better performance [EVA0034]
- Mido: Enable Pre-download and Texture Download Caching [EVA0034]
- Mido: add support for BFQIO groups [EVA0034]
- Overlay: Import configuration configuration formatting from Xiaomi Max [EVA0034]
- Add custom image charger [EVA0034]
! Download
From July 9: AFH


Post has been editedNikhaj - 20.04.20, 23:16
Reason for editing: xs why, but editing



Rep: (272)
Pixel Experience (8.1 Oreo) Official (Gapps built into the firmware, it is not necessary to flash them separately) Project Treble

Based on AOSP
Requirements
  • TWRP Recovery (custom recovery)
  • Installation .zip archive
  • Straight arms
Changes
1. Holded
Known Issues
1. It is changing the volume when telephone conversation. 2. From scroll.
Screenshots
Attached Image
Attached Image
Attached Image
Attached Image
Installation
  1. Drop the .zip archive onto the phone
  2. In the recovery we do:
    • Wipe Data
    • Wipe cache
    • Wipe Dalvick Cache
    • Wipe System
  3. Flash archive: Install .zip ->Install Custom.zip
  4. Gapps are built into the firmware.
  5. We flash the root Magisk / SuperSU (if necessary)
Download
  • Firmware:AFH
  • Gapps are built into the firmware.
  • Ruth in the header
Feedback
The firmware is ideal for those who love "naked Android", or wants to get sensations from using Google Pixel. The firmware is as close as possible to the drain, but there are chips of smartphones Google Pixel (on that and Pixel Experience). Firmware smooth and stable. Who does not need many settings and customization I ask - Pixel Experience for you.
Originaltheme (a source)

Post has been editedNikhaj - 20.04.20, 22:58
Reason for editing: 1. in the header 2. Feedback under the spoiler



Rep: (515)
XenonHD
XenonHD 7.1
It was not a fan of this firmware and treated with suspicion, because the basis of Linage was taken (for me the usual firmware without buns): HUH: What is the best of others? Also a naked android with a small modification, a list of custom settings is also small ... But it was pleasantly surprised by autonomy: blink: almost like Miui. Small, smooth no is nothing too.XenonHD 7.1

XenonHD 8.1
Firmware smart and smooth autonomy no worse than others 8.1.
The sound is kind of normal, but somehow quiet than at 7.1 (I did not hear wheezing)
LED works fine.
The volume of the conversational dynamics is quite a comfortable level, the truth is not regulated.
Ruth (SuperSU) start through the recovery after downloading to the system failed to install .apk
There is nothing to say about gaps
because I do not use
There are points that are not translated into extended settings.
-Sew settings little and part is in conventional settings (there is no possibility to disable unused sensors to save battery case)
In terms of autonomy and speed will be better than the rest) But this is in my opinion)
- Another minus Bluetooch works, but does not work on a challenge, for me it is the main minus in connection with this! RESENT:
For use will go, but only those who do not have bluetooch headset: ok:
XenonHD 8.1


Post has been editedsanek-creed - 20.05.19, 12:13
Reason for editing: in the header



Rep: (272)
Bootleggers 2.3 (8.1 Oreo) Official

Based on GZOSP
Requirements
  • TWRP Recovery (custom recovery)
  • Installation .zip archive
  • .zip archive with gapsami
  • Straight arms
Changes
General chainzhlog for all phones:
Bootleggers 2.3 Change List:
- combined tag android-8.1.0_r30
- June Protective Patch
- Added optional change and LockScreen style option
- Added the ability to change LockScreen Clock & Date Font
- Added parameter "Hide LockScreen Elements"
- Added Animation for Android P System Animations
- Added Slim Recents 3.0
- Added smart pixels
- Added CARBON gestures
- added gesture anywhere
- Added background shade LockScreen
- Added option Disable tint wallpaper
- Added background shade of the power menu
- Added Sync QS Tile
- added volume control cursor parameter
- Change the color of the battery warning according to Accent
- Added the ability to quickly launch the work of services with QS Panel
- Install the default permanent mobile connection connection
- Added option selection option Screenshot Editor
- Fixed Disable QS Warning Warning
- Fixed GPS.
- Fixed Bluetooth address
- updated default start
- Updated ready-made applications
- Updated transactions
Known Issues
1. It is changing the volume when telephone conversation. 2. From scroll.
Screenshots
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Installation
  1. Drop the .zip archive onto the phone
  2. In the recovery we do:
    • Wipe Data
    • Wipe cache
    • Wipe Dalvick Cache
    • Wipe System
  3. Flash archive: Install .zip ->Install Custom.zip
  4. Flash GAPPS (if needed)
  5. We flash the root Magisk / SuperSU (if necessary)
Download
Feedback
Stable and smooth firmware, settings a lot, generally recommended to use the audience of which I liked AEX or RR. And so on daily use is suitable.
Originaltheme (a source)

Post has been editedNikita Borisov - 22.06.18, 11:33
Reason for editing: 1. In the header 2. Feedback under the spoiler. Upgrade to 2.3



Rep: (3019)
Installing firmware via adb sideload
Description
Sometimes some face the problem that the computer does not see the phone as a drive. Those. There are TWRP and PC, but not at hand neither OTG, nor the opportunity to throw firmware files, guards, etc. in this case. In this case, you can install / throw the firmware throughadb sideload .
Installation
It is assumed that drivers are already installed on the PC. If not, install these
Attached fileadb-setup-1.4.2.exe(9.18 MB)

Download and unpack this archive with a toe to the root of the disk with
Attached fileTools.zip(651.41 KB)

- We go to the recovery and connect the device to PC
- We throw the archive with the firmware into the unpacked Tools folder
- We bring the mouse cursor to any empty place in this folder, press the right mouse button and select the dropping menuopen command window .
- Check the device's connection by a team
adb devices

- In the recovery we do wipes (if you install it)
- Next we go along the wayAdvanced / AdB Sideload
Attached Image
Attached Image

- Make Svile
Attached Image
In the command line we typeAdB Sideload / Archive name Your firmware / , we press enter . All, installation of the firmware went. After a successful firmware, the device will reboot and the installation will begin.
Example:
- Your firmware archive is calledAOSPEXTENDED-V5.6-OXYGEN-20180612-0313-Official.zip.
- Firmware teamAdB Sideload AOSPEXTENDED-V5.6-OXYGEN-20180612-0313-Official.zip.
In order not to drive the long name (errors are possible), you can simply rename the archive (as more convenient)
Addition
To just throw the archive with the firmware (it should also lie in the folder with Tulse (see above)):
- Check the device's connectionadb devices
- in the command line driveADB PUSH AOSPEXTENDED-V5.6-OXYGEN-20180612-0313-Official.zip.
- Further, everything is as usual - wipes and installation



Rep: (272)
Dotos 2.3 (8.1 Oreo) Unofficial

Based on AOSP
Requirements
  • TWRP Recovery (custom recovery)
  • Installation .zip archive
  • .zip archive with gapsami
  • Straight arms
Changes
1. Holded
Known Issues
1. It is changing the volume when telephone conversation. 2.LED indicator does not work.
Screenshots
Attached Image
Attached Image
Attached Image
Installation
  1. Drop the .zip archive onto the phone
  2. In the recovery we do:
    • Wipe Data
    • Wipe cache
    • Wipe Dalvick Cache
    • Wipe System
  3. Flash archive: Install .zip ->Install Custom.zip
  4. Flash GAPPS (if needed)
  5. We flash the root Magisk / SuperSU (if necessary)
Download
Feedback
The firmware is fast and smooth (except for the ployments that I revealed), there are no settings, but there are not so many. I liked the design in the style of Android P. In principle, for continuous use will go.
Originaltheme (a source)

Post has been editedNikita Borisov - 19.06.18, 14:39



Rep: (272)
CRDROID 4.4 (8.1 Oreo) Official

Based on Lineageos
Requirements
  • TWRP Recovery (custom recovery)
  • Installation .zip archive
  • .zip archive with gapsami
  • Straight arms
Changes
1. Holded
Known Issues
1. It is changing the volume when telephone conversation. 2.LED indicator does not work. 3. Lagate some animations.
Screenshots
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Installation
  1. Drop the .zip archive onto the phone
  2. In the recovery we do:
    • Wipe Data
    • Wipe cache
    • Wipe Dalvick Cache
    • Wipe System
  3. Flash archive: Install .zip ->Install Custom.zip
  4. Flash GAPPS (if needed)
  5. We flash the root Magisk / SuperSU (if necessary)
Download
Feedback
Firmware Fast and smooth, lag some animations. Multiple settings, design standard. I did not like much, but you can try. And in general, daily use is suitable.
Originaltheme (a source)

Post has been editedNikita Borisov - 19.06.18, 15:03



Rep: (272)
AICP 13.1 (8.1 Oreo)

Based on Lineageos
Requirements
  • TWRP Recovery (custom recovery)
  • Installation .zip archive
  • .zip archive with gapsami
  • Straight arms
Changes
1. Holded
Known Issues
1. It is changing the volume when telephone conversation. 2.Eho with a telephone conversation.
Screenshots
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Installation
  1. Drop the .zip archive onto the phone
  2. In the recovery we do:
    • Wipe Data
    • Wipe cache
    • Wipe Dalvick Cache
    • Wipe System
  3. Flash archive: Install .zip ->Install Custom.zip
  4. Flash GAPPS (if needed)
  5. We flash the root Magisk / SuperSU (if necessary)
Download
  • Firmware:Dropbox
  • Gapps in a hat
  • Ruth in the header
Feedback
During the test, the lags are not observed, fast and smooth firmware. Many settings. It is recommended for daily use.
Originaltheme (a source)

Post has been editedNikitel - 14.01.19, 13:51
Reason for editing: 1. Hap 2


Full version    

Help     rules

Now: 13.01.21, 04:20