Database Users

[RECOVERY][aries][UNOFFICIAL] TWRP Recovery 2.8.1 for Mi2/2S

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
With this recovery you can install android 5.0 roms like AOSP or CM 12, without problems with wipes, nandroid backups and restores.
Device tree: TWRP_android_device_aries​
Install instructions:
1.With fastboot:
Extract recovery.img from TWRP_2.8.1_Mi2S_miuies-Juliusssss_20141126_signed.zip
Run fastboot
Code:
fasboot flash recovery recovery.img
2.With MiRecovery using flashable zip:
Copy TWRP_2.8.1_Mi2S_miuies-Juliusssss_20141126_signed.zip in root of internal storage
Rename it to update.zip.
Enter into recovery (volume up + power)
Install update.zip from sdcard.
Reboot.
3.With CWM or TWRP using flashable zip:
Copy TWRP_2.8.1_Mi2S_miuies-Juliusssss_20141126_signed.zip in root of sd card
Enter into recovery (volume up + power)
Install zip from sdcard.
Reboot.
Known Issues:
tdb don't work, all work in system 1
If you want install roms based on KK or fewer don't choose format system in advanced wipe
Original thread: http://miui.es/index.php?topic=14282.0#forum
XDA:DevDB Information
[RECOVERY][aries][UNOFFICIAL] TWRP Recovery 2.8.1 for Mi2/2S, Tool/Utility for the Xiaomi Mi 2
Contributors
juliusssss
Staff from miui.es
Version Information
Status: Stable
Current Stable Version: 2014-11-26
Stable Release Date: 2014-12-04
Created 2014-12-04
Last Updated 2014-12-04

Reserved

very good!

juliusssss said:
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
With this recovery you can install android 5.0 roms like AOSP or CM 12, without problems with wipes, nandroid backups and restores.
Device tree: TWRP_android_device_aries​
Install instructions:1.With fastboot:
Extract recovery.img from TWRP_2.8.1_Mi2S_miuies-Juliusssss_20141126_signed.zip
Run fastboot
Code:
fasboot flash recovery recovery.img
2.With MiRecovery using flashable zip:
Copy TWRP_2.8.1_Mi2S_miuies-Juliusssss_20141126_signed.zip in root of internal storage
Rename it to update.zip.
Enter into recovery (volume up + power)
Install update.zip from sdcard.
Reboot.
3.With CWM or TWRP using flashable zip:
Copy TWRP_2.8.1_Mi2S_miuies-Juliusssss_20141126_signed.zip in root of sd card
Enter into recovery (volume up + power)
Install zip from sdcard.
Reboot.
Known Issues:
tdb don't work, all work in system 1
If you want install roms based on KK or fewer don't choose format system in advanced wipe
Original thread: http://miui.es/index.php?topic=14282.0#forum
XDA:DevDB Information
[RECOVERY][aries][UNOFFICIAL] TWRP Recovery 2.8.1 for Mi2/2S, Tool/Utility for the Xiaomi Mi 2
Contributors
juliusssss
Staff from miui.es
Version Information
Status: Stable
Current Stable Version: 2014-11-26
Stable Release Date: 2014-12-04
Created 2014-12-04
Last Updated 2014-12-04
Click to expand...
Click to collapse
Hello thank you very much for this! Could you add f2fs driver's to the kernel's recovery? Would be very great!
I have already a stock omni's branch with it integrated. This is a squash of commits that adds f2fs

thanks and +1 for f2fs

I have a problem with sound on calls in omnirom 4.4.4. after updating with this twrp. See here:
http://forum.xda-developers.com/showthread.php?p=57917110
Help very welcome.

No-New-Phone said:
I have a problem with sound on calls in omnirom 4.4.4. after updating with this twrp. See here:
http://forum.xda-developers.com/showthread.php?p=57917110
Help very welcome.
Click to expand...
Click to collapse
Sorry I didn't research enough (I was already on my trip to France and had limited connection)
Found this thread
http://xiaomi.eu/community/index.php?threads/26386/
Cm11- suddenly no mic and earpiece is working
In short: audio works when I disable check in service from Google play.

juliusssss said:
tdb don't work, all work in system 1
If you want install roms based on KK or fewer don't choose format system in advanced wipe
[/INDENT]
Click to expand...
Click to collapse
What happens if you choose format system in advanced wipe? For now, when I want to format /system, I first flash Cwm recovery, format system there and the flash twrp again...

juliusssss said:
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
With this recovery you can install android 5.0 roms like AOSP or CM 12, without problems with wipes, nandroid backups and restores.
Device tree: TWRP_android_device_aries​
Install instructions:
1.With fastboot:
Extract recovery.img from TWRP_2.8.1_Mi2S_miuies-Juliusssss_20141126_signed.zip
Run fastboot
Code:
fasboot flash recovery recovery.img
2.With MiRecovery using flashable zip:
Copy TWRP_2.8.1_Mi2S_miuies-Juliusssss_20141126_signed.zip in root of internal storage
Rename it to update.zip.
Enter into recovery (volume up + power)
Install update.zip from sdcard.
Reboot.
3.With CWM or TWRP using flashable zip:
Copy TWRP_2.8.1_Mi2S_miuies-Juliusssss_20141126_signed.zip in root of sd card
Enter into recovery (volume up + power)
Install zip from sdcard.
Reboot.
Known Issues:
tdb don't work, all work in system 1
If you want install roms based on KK or fewer don't choose format system in advanced wipe
Original thread: http://miui.es/index.php?topic=14282.0#forum
XDA:DevDB Information
[RECOVERY][aries][UNOFFICIAL] TWRP Recovery 2.8.1 for Mi2/2S, Tool/Utility for the Xiaomi Mi 2
Contributors
juliusssss
Staff from miui.es
Version Information
Status: Stable
Current Stable Version: 2014-11-26
Stable Release Date: 2014-12-04
Created 2014-12-04
Last Updated 2014-12-04
Click to expand...
Click to collapse
http://d-h.st/jP78 The last M1cha's TWRP from MiFlash4Linux packages. v2.8.7.0 for both partitions
Code:
fastboot oem unlock
Code:
fastboot erase recovery
Code:
fastboot flash recovery therecoveryname.img

Hola @juliusssss
Partition SD Card is not working.
Code:
E: Unable to locate device to partition.
Any advice?

Thought it only had 2.8.3. Then I saw the 3.1.1.0 on the offical twrp website. Sooo glad the developer hasn't left!! Thanks for the newest twrp version!!

[NEWBIE GUIDE] MIUI ROMs, TWRPs, ZIPs, UNLOCK, BACKUP, ROOT, FLASH, RESTORE

GUIDE SECTIONS QUICK LINKS
#1 - MIUI ROM, Types of MIUI ROM
#2 - TWRP, Types of TWRP, Flashing TWRP
#3 - Unlock, Root, Flashing via TWRP
#4 - Custom ROM, Types of custom ROMs
MIUI ROM
MIUI (pronounced as Me-You-I) is Xiaomi's custom built firmware like Samsung's OneUI, HTC's SenseUI, OnePlus's OxygenOS which is built on top of Android's AOSP base with its own modifications and features. At first glance it resembles like a hybrid between Google's Material Design and Apple's iOS. But unlike Stock Android or iOS, MIUI is very intuitive, feature rich and has multiple tweaking options. MIUI is updated regularly depending on the development branch. Xiaomi gathers reports, feedbacks and suggestions from the community, addresses the bug-fixes and integrates new features upon request. Most of Xiaomi devices are regularly patched with security updates every 2-3 months. The flagship "Mi" series like Mi9 receive quicker Android version updates than their budget "Redmi" series like Redmi 7, Redmi Note 7 Pro etc.
TYPES OF MIUI ROM
There are 2 development branches of MIUI ROMs for all Xiaomi devices.
A) Stable Builds
It is updated on a monthly basis or longer
New features are added slowly after testing
Higher system stability and less bugs than Beta ROMs
It has a four digit numbering scheme (X.X.X.X)
For eg. 8.X.X.X is MIUI8 Stable Build
Stable builds come in 2 variants
1. MIUI China Stable ROM
This ROM is pre-installed on all Xiaomi devices sold in China.
It is made for the Chinese market & contains Chinese MIUI apps.
Google Apps are absent. You can install them manually.
It supports Chinese & English languages.
2. MIUI Global Stable ROM
This ROM is pre-installed on all Xiaomi devices sold outside China.
It is made for the International market & contains English MIUI apps.
Google apps are pre-installed by default.
It supports 50+ languages.
B) Beta Builds
It is updated on a weekly/bi-weekly basis or longer.
New features are added quickly for testing.
Lower system stability and more bugs than Stable builds.
It has a three digit numbering scheme (X.X.X)
For eg. 6.11.21 is MIUI8 Beta build for 21th Nov, 2016.
This ROM is not pre-installed on any Xiaomi device.
You can install Beta build over Stable build manually.
Beta/Developer builds come in 2 variants.
1. MIUI China Beta ROM
It is made for the Chinese market & contains Chinese MIUI apps.
Google Apps are absent. You can install them manually.
It supports Chinese & English language.
2. MIUI Global Beta ROM​ It is made for the International market & contains English MIUI apps.
Google apps are pre-installed by default.
Supports more than 50+ languages.

TWRP
Team Win Recovery Project is a custom recovery which is flashed over the stock recovery as it gives user more options such as flashing custom ROMs, kernels & scripts, take full system backups, restore backups, root etc.
TYPES OF TWRP
1. TWRP by iscle: https://forum.xda-developers.com/mi-max-2/development/recovery-twrp-3-1-1-0-touch-recovery-t3652762
Based on Stock TWRP 3.1.1-0 with no modifications.
Ported from Redmi Note 4 (mido)
English language as default
Need to flash dm-verity zip immediately after flashing this TWRP, else your phone wont boot.
2. TWRP by xuefer: https://forum.xda-developers.com/mi-max-2/development/twrp-max2-oxygen-t3634437
Built using LineageOS 14.1 source
Built and tweaked for Mi Max 2 (oxygen)
Decryption support added for /data
Faster transfer using adb push
Extra fonts added
FLASHING TWRP
Unlock bootloader here: https://forum.xda-developers.com/mi-max-2/how-to/guide-unlocking-bootloader-mi-max-2-t3641257
Install "Minimal ADB+Fastboot Drivers": https://forum.xda-developers.com/showthread.php?t=2317790
Download TWRP file and copy the file in the C:\Program Files (x86)\Minimal ADB and Fastboot folder
Download dm-verity disabler and copy the file in your phone: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Switch off phone. Hold Power + Volume Down to boot into fastboot mode. Connect it to PC.
Inside the folder where TWRP file is present, open command prompt window.
Type "fastboot devices". Your phone will get detected with serial number.
Type "fastboot flash recovery <recovery_name.img>". TWRP will get flashed on your device.
E.g. "fastboot flash recovery twrp_3.1.1-0.img".
Type "fastboot boot <recovery_name.img>". You will boot into TWRP. Disconnect phone from PC.
E.g. "fastboot boot twrp_3.1.1-0.img".
On the screen, swipe to allow modifications and select your language. Uncheck "Keep system read-only"
Select Install and then choose the dm-verity disabler zip and swipe to flash.
Select Backup and check all partitions. Swipe to backup. The backup will be stored in "TWRP" folder
Select Reboot and then system. You will be asked if you want to disable the stock recovery. Swipe to disable.
You will boot into MIUI with TWRP installed.
TWRP ZIPs
These zips are meant to be flashed with TWRP with a specific order. Before flashing any zip make sure you have taken full backup of your device partitions using TWRP.
1. no-verity-opt-encrypt: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Also called as dm-verity disabler/lazy flasher
"dm-verity" is a feature in the MIUI kernel which checks and prevents the phone from booting normally if you modify the phone. (e.g. flash TWRP)
To prevent that, you need to flash the dm-verity disabler zip which removes dm-verity check and also decrypts the /data partition so that you can boot into MIUI normally.
Else you can flash a custom ROM immediately after flashing TWRP which removes the MIUI system and kernel
2. Xiaomi.EU ROM Patch: https://forum.xda-developers.com/mi-max-2/development/xiaomi-eu-rom-patches-dpi-change-t3656296
You need to install Xiaomi.EU ROM before installing these zips via TWRP.
MIUI to Google Apps: Replaces default MIUI apps with Google apps.
Google Now/Pixel Launcher: Replaces stock MIUI launcher and enables Google Assistant via build.prop tweak.
DPI changer: Change values from stock 440 (low res, bigger) to 325 (high res, smaller).
3. Hardware Key Disabler : https://forum.xda-developers.com/mi-max-2/themes/mod-disable-hardware-keys-lineageos-rom-t3696108
This mod enables on screen navigation bar and disables the hardware keys
You can revert back to stock configuration by flashing "enable_HWkeys.zip"

FLASHING VIA TWRP
Some important terms to remember:
Formatting data: Factory resets the phone, will erase internal storage, will remove encryption
Wiping data: Factory resets the phone, will not erase internal storage, will not remove encryption
Clean flash: Flashing a new ROM or an updated version of the same ROM by wiping or formatting data of current ROM in TWRP. Cache & dalvik is automatically wiped in TWRP.
Dirty flash: Flashing an updated version of the same ROM without wiping or formatting data of current ROM in TWRP. Cache & dalvik wipe is recommended in TWRP.
Treble TWRP: Custom TWRP which uses existing /cust partition and formats it into /vendor partition which is needed for non-MIUI Oreo and Pie ROMs where Treble is used.
Notes:
Always read the entire post & comments of the custom ROM page before asking any questions, chances are your query has already been answered.
You do not need to wipe /system partition manually, it its automatically wiped when a ROM is flashed by the updater-script inside the ROM zip. General rule of thumb is always clean flash any ROM, unless mentioned by the ROM developer or maintainer that dirty flashing is okay.
Requirements:
Unlocked bootloader with TWRP installed
Phone partition backup using TWRP
All data backup from internal storage (sms, contacts, files etc.)
Official MIUI ROM encrypts /data partition, you will need to Wipe > Format Data to decrypt it completely else need to flash dm-verity disabler zip or Magisk zip.
1. Rooting MIUI / non-MIUI ROM
Boot into TWRP (Power+Volume Up)
Install > Magisk zip
Reboot > System
2. Flashing official MIUI recovery ROM
Boot into TWRP
Wipe > Format data (if storage is encrypted)
Reboot > Recovery
Install > MIUI ROM zip + Magisk Zip
Reboot > System
3. Flashing custom MIUI ROM (Xiaomi.EU / RevOS / Mi Globe)
Boot into TWRP
Wipe > Format data (if storage is encrypted)
Reboot > Recovery
Wipe > Factory reset
Install > Custom MIUI ROM zip
Reboot > System
4. Flashing LineageOS/AOSP ROMs (Non-Treble)
Boot into TWRP
Wipe > Format data and Reboot > Recovery (if storage is encrypted)
Wipe > Factory reset
Install > Firmware + ROM Zip + Google Apps Zip
Reboot > System
5. Flashing LineageOS/AOSP ROMs (Treble)
Boot into Treble TWRP
Wipe > Format data (if storage is encrypted)
Reboot > Recovery
Wipe > Factory reset
Install > Firmware + ROM Zip + Google Apps Zip
Reboot > System

TYPES OF CUSTOM ROMs
There are mainly two types of custom ROMs for any Android device. You need to flash them on your phone using custom recovery such as TWRP.
1. Stock based ROMs
They are based on the factory ROM which came pre-installed on your device. In case of Xiaomi devices, developers take the stock China Stable/Beta MIUI ROMs as base, perform modifications and tweaking and then re-pack it. Examples of stock based MIUI ROMs.
Xiaomi.EU: https://xiaomi.eu/
MIUI Pro: https://miuipro.by/
Mi Globe: http://mi-globe.com/
Epic ROM: http://www.epicrom.pro/
2. Custom based ROMs
They are typically based on either AOSP or LineageOS code. They can either be ported from similar devices or built using the kernel source code of a particular device. Xiaomi has not yet released kernel source code for Mi Max 2. Kernel source codes are needed for relatively stable and bug-free experience on custom ROMs. Examples of some popular custom ROMs
A) AOSP based ROMs
AOSPExtended: https://www.aospextended.com/
Nexus Experience: http://www.nxrom.us/
SlimRoms: https://slimroms.org/
B) LineageOS based ROMs
LineageOS: https://lineageos.org/
Resurrection Remix: http://www.resurrectionremix.com/
XenonHD: http://www.xenonhd.com/

Reserved #4

Reserved #5

Thanks for wonderful explanation and for content too

Hi,
I flashed TWRP from PC using above procedure & tried to install no-verity-opt-encrypt (version 5.1.zip).
I got below error while installing :
Error: unpacking ramdisk failed
Phone booted normally & TWRP is not there.
How to fix this issue?

I know these questions are sometimes annoying, but for someone who hasn't been following Android development since Android 4.4.4, I'm a little overwhelmed by all this information. What does the "Oxygen" mean? Is it just a certain model of the Mi Max 2? I see all ROMs say Oxygen but none explain what it means. If it's a model of the Max 2, how can I know if the version I have is Oxygen?
Thanks and sorry if it's a dumb question

It's a code name for Max 2, so you don't mistakenly flash the wrong ROM, if it says Oxygen, than you're sure it's for your model, not for i.e. Mi Max...
Sent from my Mi Max 2 using Tapatalk

Hello,
I have a Mimax 2 bootloader unlocked, rooted, SuperSU, twrp 3.1.0-0 (cofface) installed. I installed, after some difficulties, the rom xiaomi.eu 7.12.28. When I'm in recovery, after the flash I sometimes have a red line that says "... no-verity-opt-encrypt ..." blah blah. But the phone boot normally, everything works fine. Do I have to install lazyflasher-no-verity-opt-encrypt or can I do without it?
thank you and sorry for my bad english

Hi, I have unlocked BL and installed Developer ROM 7.12.28. for a few weeks now. Can I install latest 8.1.4 developer ROM with TWRP without wiping cache/dalvik and will I keep my data/apps that way?
Thanks.
Sent from my Mi Max 2 using Tapatalk

@frulex, I installed the 8.1.4 (via updater) after using the 7.12.28, without any problem. That you erase the cache where not, you will not lose the data of your apps

What was the size of that update file you installed? I first got notification of 8.1.4 update and it said it's something like 95 MB file size. Tried to install it twice via updater, it starts updating, boots to TWRP and ends with error without installing. After reboot notification changed and now it offers update of full 1.5 GB 8.1.4 version ROM. I didn't have time to download and try that but I wonder will that also end in error and that's why I ask about downloading .zip and flashing through TWRP.
Sent from my Mi Max 2 using Tapatalk

These are the roms I used, as you see 8.1.4 weighs 1.2 Go
edit: I had uploaded an image of the explorer but it does not appear! (decidedly i'm struggling with this forum, lol)

Not many roms for this phone..it sux..I regret exchanging it with my oneplus 3..

How many ROMs have you expected in 3 days since kernel source has been released?
Sent from my Mi Max 2 using Tapatalk

good tutorial
thanks to you @SharkcpN . this is such a clearly, easily tutorial "How to Flash TWRP" for newbie like me..
I tried and succeed with no error at all.. once again, thanks for your good job :good:

Hi there! Thanks for the excellent thread and collection of links. I started here and found a setting on this phone's NVRAM that I have not seen mentioned anywhere else, and you will need it for LTE unlocking.
Below are the exact steps, many taken from this guide, that I used to go from a phone with an unlocked bootloader to flipping the LTE B2 and LTE B4 bits on. After I did it and rebooted, I suddenly had a working LTE connection!
I cannot yet PROVE that this actually enabled the bands, but it hasn't hurt anything. I will test for that in a couple days, because the only dumb thing I did was afterwards, when I accidentally re-locked the bootloader by not paying attention to what I was doing. If you use the MiFlash program to install a ROM, don't forget to change the setting in the lower right corner!
Notes for those wishing to use this as a guide:
I don't think you can brick the phone completely playing with just these settings, but you should be prepared to restore everything. Take backups where I mention them, and if you need the device working, you should have a current MIUI fastboot flashable image, available from the official website, on hand.
This is LTE only and there are different settings for GSM that work the same way.
The steps are numbered, but you should also understand mostly what they do.
You may ignore the VM part and just boot your normal Win7 with driver signature checking DISABLED (F8 on boot). I use Linux and I'm security-conscious about downloading programs that I can't verify, so I'm using a VM.
There is a dialpad option for opening the diag port (if you have root), but it did not work for me, so I have provided a method that I know works and it clears itself upon reboot
QXDM's NV browser has a checkbox for "DUAL SIM". You don't need to check it for this process, you won't lose SIM2.
Downloads section:
(REQUIRED) Most are in the links provided by OP:
MiFlash (official one)
QPST 2.7.460
QXDM 3.12.714
Minimal adb and fastboot
no-verity-opt-encrypt-6.0.zip
twrp-3.2.1-0-oxygen.zip
SuperSU-v2.82-201705271822.zip
(OPTIONAL, needed if you mess up. I chose to have it ready to go.):
From MIUI official site, go to the ROMs for the Max 2. The one on the download button here is NOT what you want.
Select Flashing guide, then on on the left hand side select FastBoot.
Download the image for your device. I have a copy of oxygen_global_images_V9.0.3.0.NDDMIEI_20171209.0000.00_7.1_global_298fd5f49c.tgz
SETUP SECTION (install tools and root phone):
Enable developer mode and USB debugging on phone
Boot into a Windows VM, pressing F8 to go into unsigned drivers mode
Install MiFlash, just to get the drivers
Install QPST and QXDM for later
Install adb and fastboot
Pass USB port through to VM and check adb is working by twice typing
Code:
adb devices
Shutdown phone and remove SD card from phone.
Add no-verity-opt-encrypt-6.0.zip and SuperSU-v2.82-201705271822.zip to SD card
Put SD card back in phone
Reboot phone into fastboot mode using PWR & VOL-, and re-pass to VM if needed
From cmd terminal in adb folder,
Code:
fastboot flash recovery twrp-3.2.1-0-oxygen.img
Code:
fastboot boot twrp-3.2.1-0-oxygen.img
Once TWRP comes up, install no-verity-opt-encrypt-6.0.zip
(OPTIONAL) Make a backup. I didn't because I don't want the ROM that's on there anyway.
Reboot and ensure MIUI loads
Shutdown phone and reboot into TWRP using PWR & VOL+
Install SuperSU as a system app
Reboot into MIUI
Access and edit the NVRAM:
Connect the device back to the computer, pass to VM if necessary
From your terminal in the adb folder,
Code:
adb devices
Grant debug permission on the device, if it asks again
Code:
adb shell
Code:
$su
Grant permission in superSU popup
Code:
#setprop sys.usb.config diag,adb
When the device reconnects, re-pass to VM if needed, and it may install another driver
Open QPST Configuration and make sure the device's port is enabled.
At the top, go to "start clients" and open "software download"
In the "Backup" tab, choose a location to save your file and hit Start, just in case you do break something
Once finished, close "software download" but leave QPST Configuration running
Open QXDM Professional
Under Options->Communications, make sure your phone is set "active" then set "target port" to the port it's on, then press OK
Go to NV Browser in the dropdown on the upper left.
Scroll down to 06828 :"nv_lte_bc_config_type.lte_bc_config"
Press READ and save this value somewhere in case you forget which bits you set! Mine was: 2061584302293
It's little-endian, and I wanted to flip bits from 0 to 1 to enable bands {2} and {4}, so I added 2^({2}-1)+2^({4}-1) = 10 to get a value of 2061584302303
Enter your new value in the "value" field and press "write"
Now, scroll down to the corresponding LTE prefs value at 65633
Read again. This should be the same number you had before, in hexadecimal format. Mine was 0x1E0000000D5, so to add B2 and B4 (Combined value 0xA), I changed it to 0x1E0000000DF
Again, enter your new value in the "value" field and press "write"
I doubt this requires any sort of "safe shutdown," but I hit "offline" then closed QXDM, then closed QPST, then rebooted the phone.
For a quick test, you can set network preferences to "LTE ONLY" by going to the dialpad and hitting *#*#INFO#*#*, then selecting your SIM card and using the dropdown in there. Mine was preferring HSPAP because the signal was stronger, even though the data was blocked.
Further testing I want to do when I get the bootloader unlocked again:
Use an app that shows what bands are in use to prove I'm on B2 or B4
Try disabling bands I will never use that have similar frequencies to the bands I want to see if signal improves

TWRP ZIPs
These zips are meant to be flashed with TWRP with a specific order. Before flashing any zip make sure you have taken full backup of your device partitions using TWRP.
1. no-verity-opt-encrypt: https://build.nethunter.com/android-...y-opt-encrypt/
Also called as dm-verity disabler/lazy flasher
"dm-verity" is a feature in the MIUI kernel which checks and prevents the phone from booting normally if you modify the phone. (e.g. flash TWRP)
To prevent that, you need to flash the dm-verity disabler zip which removes dm-verity check and also decrypts the /data partition so that you can boot into MIUI normally.
Else you can flash a custom ROM immediately after flashing TWRP which removes the MIUI system and kernel
2. Xiaomi.EU ROM Patch: https://forum.xda-developers.com/mi-...hange-t3656296
You need to install Xiaomi.EU ROM before installing these zips via TWRP.
MIUI to Google Apps: Replaces default MIUI apps with Google apps.
Google Now/Pixel Launcher: Replaces stock MIUI launcher and enables Google Assistant via build.prop tweak.
DPI changer: Change values from stock 440 (low res, bigger) to 325 (high res, smaller).
What does It mean??

[ROM][7.1.2][AOSP] UltimateROM [BETA][11.03.2018]

Current Information
Hi there, UltimateROM is AOSP-based ROM with some features and optimizations added.
Everything I do with UltimateROM I always test personally on my phone, but anyway...
Code:
#include <disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
What's working:
RIL (phone/SMS/3G)
Video (playback & recording)
Audio (playback & recording)
Wi-fi
Bluetooth
Camera (Front and rear)
2D/3D HW Acceleration
USB, MTP, ADB
all native tethers (Wifi/BT/USB)
external storage
What's not
GPS
Vibration doesn't work (disabled temporarily due to an userspace vibrator driver issues)
Internal storage is not recognized
Formatting SDcard as adoptable storage will make it unusable
Buggy MTP implementation
Download
UltimateROM
Installation
before installation make sure you have a TWRP recovery
install chrono kernel (both ROM and the corresponding kernel are located in the same directory - see ROM link below)
reboot recovery
install ROM
install SuperSU
install chrono kernel again
If you proceed with installing GAPPS, you might have running out of space on /system partition. If you are planning to flash Gapps, you're likely need to use sdcard repartition (see below how to). Below is installation sequence with the repartition of the internal sdcard:
like before, make sure you have kernel with TWRP recovery inbuilt
install chrono kernel
reboot recovery
flash ReParted zip. This will wipe system, data and cache partitions!
install ROM
install SuperSU
install chrono kernel again
*please note a possibly undesirable effect of the repartition: cache partition will be decreased to 15 MB and some ROMs that rely upon this partition won't boot. To restore original sdcard partition layout, flash stock 4.1.2 ROM (with PIT file).
Sources:
https://github.com/UltimateROM/android_manifest
Credits
SergeyL - many-many thanks for an initial set of patches, device tree and TWRP 3.x.y! Also thanks for helping me implementing some features to this ROM.
mickybart, millosr, MWisBest - thanks for great cherry-picks!
@Meticulus - thanks for his great contributions on our devices!
@AGONTUK - thanks for an initial Marshmallow bring up!
@nieltg - Sources for Galaxy Ace 2 device
@golden-guy - thanks for great cherry-picks !
@TeamCanjica - vendor and hardware sources
@Unjustified Dev - Audio fixes
Google
CyanogenMod
AOKP
SlimROMs
EuphoriaOS
OmniROM
AOSPA
Viper4AndRroid Team
And many other devs, I could forget (please write me if I did so).
Special Thanks:
@isaak, @enkflr, @Pdevo, @prometej-zg for donating this phone!
[*]@S.AMU for providing FTP-Server
XDA:DevDB Information
UltimateROM, ROM for the Samsung Galaxy S Advance I9070
Contributors
ChronoMonochrome, SergeyL, mickybart, millosr, MWisBest
Source Code: https://github.com/UltimateROM
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP recovery
Based On: AOSP, LineageOS
Version Information
Status: Beta
Created 2018-03-11
Last Updated 2018-03-11

Changelogs
11.03.2018 - build #1
initial release

Reserved

Flashed both of your roms on janice and... wow, nougat is much smoother than mm (w/o gapps)

Great JOB Chrono , Will test it immediately .
Was dreaming of this.

[YOUTUBE][https://www.youtube.com/watch?v=JgSBPf-jiiM&lc=z23gzrkgcrqcffykaacdp43bvodf3st2izucbuxtgidw03c010c]
Ok Chrono MC I installed the ROM on 2 on my Advance's and you are official KING of the Advance i9070 Now
Thank you very much , this helped me to create my Mod but now under Android 7.1.2 thanks to You and all that worked on this .
Keep up the fantastic work.
Channel48

Hey I have a problem with the reparted script. I get "error opening "data/media"" and "error: No such file or directory"

ErackGamer said:
Hey I have a problem with the reparted script. I get "error opening "data/media"" and "error: No such file or directory"
Click to expand...
Click to collapse
Do these messages lead to any other problems? Try formatting /data partition. If that doesn't help, flash stock 4.1.2 ROM (with PIT file).

ChronoMonochrome said:
Do these messages lead to any other problems? Try formatting /data partition. If that doesn't help, flash stock 4.1.2 ROM (with PIT file).
Click to expand...
Click to collapse
I think that the problem was due to the old twrp I had installed. After flashing the kernel and getting the newer twrp that it includes I was able to successfully run the script. More details at your Lineage 15.1 ROM post

Going to test

can't get it pass thru Setup Wizard :thinking:
it just stuck at Just a sec, do I need a data enabled sim?
I've inserted a fat32 sdcard.
I will try without gapps later...
EDIT : First boot cannot have GAPPS, it needs to be flashed after first boot. Whole system seems slightly unstable with GAPPS.
logcat is weird, the output looks "choppy"

Hi @ChronoMonochrome
I saw you successfully booted this ROM
Did you change much in kernel 6.0.1 to make it boot

unknown said:
Hi @ChronoMonochrome
I saw you successfully booted this ROM
Did you change much in kernel 6.0.1 to make it boot
Click to expand...
Click to collapse
I don't really remember exact changes, since we have booted 7.1.2 a long time ago. You might want to look mostly at the SELinux changes, probably there should be implemented some more (which is recommended but not required to boot the ROM).

For those who are going to use GAPPS on this ROM:
1. Flash GAPPS after first boot! If you flash GAPPS before first boot, you won't be able to pass through Setup Wizard.
2. After flash GAPPS, do not wipe cache/dalvik cahce/data. Wiping these partitions after flash GAPPS seem to make GAPPS causing massive instability to the system.
3. On every boot, open once Settings -> Google and wait for Google Play Services to crash once. I don't really know why, but several GMS services kept crashing and restart GMS is restarted non-stop by the system. After Google Play Services crash once, the GMS services won't crash anymore. This should lead to a more stable system.
Overall, I don't recommend GAPPS with this ROM. With and without GAPPS on this ROM is almost a day and night difference, in terms of stability.
Janice + Nougat (w/o GAPPS) = BEST!

fix ur instructions i got confuesed

hi there, am seeing no comments of usability of this rom after Jun 2018.
Also there have been no no updates on the rom, seems like the developer has given up on the development.
can anyone confirm the bugs and can it used with microg?

[EXPLAINED] z2_plus | /factory to /vendor | revert to /factory - TREBLE

A GUIDE TO FLASH LATEST TREBLE ROMS, OLDER TREBLE ROMS OR NON-TREBLE ROMS ROMS
UPDATE: A guide to rename our /factory partition as /vendor so that you can flash OLDER Android Oreo treble builds! We do not need this guide on Android Pie custom ROMs or for Stock ZUI WE ONLY NEED THIS FOR ANDROID OREO TREBLE BUILDS REQUIRING /factory renamed as /vendor
for Lenovo Zuk Z2 Plus
Latest Treble : /factory renamed i.e switched to /vendor
Older Treble:/factory mounted as /vendor
Non-Treble: Nothing to do with Vendor, Factory stuff lol
INTRO
As you all know that we now have TREBLE, and Zuk-devs are working hard to improve it further so that when the time comes we can move to GSI builds of future Android versions.
Recently, Zuk-devs have renamed the /factory partition into /vendor partition previously we were mounting /factory as /vendor but now it has been converted(renamed) to /vendor partition with this you'll be able to use a Proper Magisk zip, and you don't need a modded/edited Magisk, etc and lotta other kinds of stuff that we will discuss and come to know in the future.
rootdir: fstab: Use the right label for our vendor partition.
TUTORIAL:
What you want to do:
** Flash OLD TREBLE ROMS /factory is renamed to /vendor - NOTE NOT NEEDED FOR NEWER ROMS! **
Instructions:
* Flash "Factory2Vendor_plus.zip",
*Flash below linkedTWRP,
*Reboot To TWRP,
*Flash ROM,
+ GApps / + Magisk etc
* Reboot.
*Enjoy :fingers-crossed:
Downloads:
Factory2Vendor_plus: https://androidfilehost.com/?fid=962187416754475515
treble-TWRP 3.2.2 v2: https://www.androidfilehost.com/?fid=5862345805528044154
** REVERTING BACK to NORMAL aka renaming /vendor back to/factory **
Instructions:
*Flash "Vendor 2Factory_plus.zip",
*Flash LATEST OFFICIAL TWRP,
*Reboot TWRP,
*Flash ROM,
(+ GApps)
*Reboot.
*Enjoy :fingers-crossed:
Downloads:
Vendor2Factory_plus: https://androidfilehost.com/?fid=962187416754475514
https://twrp.me/zuk/zukz2.html
3. Flashing a Non-Treble RoM which has nothing to do with /factory /vendor partition etc.
Instructions:
*Coming from the above procedure, no need to do anything! the new OFFICIAL TWRP will work for Non Treble roms as well and No patches need to be flashed*
*Flash ROM,
+ GApps / + Magisk etc
*Reboot.
*Enjoy :fingers-crossed:
Notes:
This 'New TWRP' will work for both Latest Treble and Non-Treble ROMs
For ZUI also no need to flash any patch, New TWRP shall work (Needs to be tested)
You can flash Non-Treble ROMs and Nougat Builds or other builds with the new TWRP and no patches need to be flashed
Once you flash "factory2vendor" or "vendor2factory" you do not need to flash again unless mentioned in the build
or if you want to revert back to Old Treble ROMs where /factory was mounted as /vendor
CREDITS
Zuk-devs - Davidevinavil, DD3Boh and Cosmedd (https://github.com/zuk-devs)
@Fedor917 for giving the idea
And all others who have contributed in any manner! :highfive:​

Team win recovery project - 3.2.2 - treble [unofficial]
Treble supported TWRP 3.2.2 ONLY FOR ROMS with /factory renamed as /vendor
CHANGELOGS:
V1-
Device Specific:-
- Persist option
- Download Mode (edl)
- Fixed Partition Size
- Update the kernel image to get the latest commits for ext4, f2fs etc (cosmedd)
- Default brightness to 40%
General:
- adb backup fixes
- OTA style update zips will now install automatically without prompting for decrypt
- minor tweaks to handling date/time on Qualcomm devices
- updates to some language translations
V2-
- Vendor Wiping option
- Persist Backup/Restore
- Splash backup/restore and now can be flashed via img
DOWNLOAD:
https://androidfilehost.com/?fid=5862345805528044154
Source Code:
Device: https://github.com/kubersharma001/twrp_device_zuk_z2_plus
Kernel : https://github.com/cosmedd/android_kernel_zuk_msm8996/tree/twrp[/url]
SPECIAL THANKS TO
Alvaro
DD3Boh
Cosmedd
DavideVinavil
Pavan & Starman for testing!
FOR ANYTHING ELSE OR NORMAL TREBLE BUILDS (aka just using /factory) or NON TREBLE BUILDS USE ONLY FROM:
https://forum.xda-developers.com/le...-official-teamwin-recovery-project-3-t3899166

Reserved

So we'll have an updated TWRP for this full treble now? Is it still backward compatible with non treble rom like the partial one?

pipyakas said:
So we'll have an updated TWRP for this full treble now? Is it still backward compatible with non treble rom like the partial one?
Click to expand...
Click to collapse
New TWRP is for New Treble ROMs where /factory partition has been renamed to /vendor partition and It is for all the Non Treble Builds
Old TWRP is for Partial/Full Treble ROMs where /factory partition is mounted as /vendor partition

Thanks for the detailed instructions!
I was before on non treble builds and as instructed on AEX thread (Davide recommendation) I flashed Zuk stock ZUI rom (Oreo)
Than I flashed partial treble rom with new TWRP he instructed, and also future full treble roms.
Now I'm on latest 5.4
I once did revert to 5.2 but before that I wiped everything and installed old TWRP and made come back to 5.2
But as new build came out fast with fixes I flashed again TWRP with treble support and flashed 5.4 rom
My question is do I need to do any step here explained or not?
Everything working fine here, TWRP saw and flashed vendor partition.
Thanks for answer in advance

I couldn't understand completely
Im on latest AEX With developers twrp
Should i flash New Twrp first and then the factory package
Or its the opposite
And which factory zip should i flash
To be on the next AEX version

The steps mentioned above applies for the new builds that are going to come.

Now I'm on AEX 5.4 with the treble TWRP from #2...
So with the next build I should flash the Factory2Vendor.zip then a new (official?) TWRP img and then (after a recovery reboot) clean install the new build as usual? @kubersharma

frozenfirevr said:
Now I'm on AEX 5.4 with the treble TWRP from #2...
So with the next build I should flash the Factory2Vendor.zip then a new (official?) TWRP img and then (after a recovery reboot) clean install the new build as usual? @kubersharma
Click to expand...
Click to collapse
Yes

Does New Twrp (#1) can Be used for Non Treble ROMs.?

--------

Please clarify, which zip should be flashed first, vendor zip or twrp zip.

Moto-B said:
Please clarify, which zip should be flashed first, vendor zip or twrp zip.
Click to expand...
Click to collapse
+1

Moto-B said:
Please clarify, which zip should be flashed first, vendor zip or twrp zip.
Click to expand...
Click to collapse
First flash,factory2vender zip....
And then flash new twrp.img

I am on bootleggers ROM
Can anyone explain sequence of flashing the files??

Dhinesh1999 said:
Does New Twrp (#1) can Be used for Non Treble ROMs.?
Click to expand...
Click to collapse
Yes you may. Already mention by Kuber somewhere in the first page.
---------- Post added at 01:37 PM ---------- Previous post was at 01:29 PM ----------
vuckovic_stefan said:
Thanks for the detailed instructions!
I was before on non treble builds and as instructed on AEX thread (Davide recommendation) I flashed Zuk stock ZUI rom (Oreo)
Than I flashed partial treble rom with new TWRP he instructed, and also future full treble roms.
Now I'm on latest 5.4
I once did revert to 5.2 but before that I wiped everything and installed old TWRP and made come back to 5.2
But as new build came out fast with fixes I flashed again TWRP with treble support and flashed 5.4 rom
My question is do I need to do any step here explained or not?
Everything working fine here, TWRP saw and flashed vendor partition.
Thanks for answer in advance
Click to expand...
Click to collapse
I suggest you follow steps in part 1 again so that you can clean flash AEX 5.4 04/16 build.
Further can you advice best way to flash Oreo zui and revert back to latest AEX? I assume bootloader gets locked when you flash back to Oreo zui? Do advice.

Will flashing the mentioned zips on AEX 5.4 do any harm ? It's official one and treble TWRP only.

lokendra17 said:
First flash,factory2vender zip....
And then flash new twrp.img
Click to expand...
Click to collapse
Naveenjain said:
+1
Click to expand...
Click to collapse
need to do full wipe before flash rom?

ERHAN53 said:
need to do full wipe before flash rom?
Click to expand...
Click to collapse
No need to full wipe...you can dirty flash aex rom over 11/04 built
---------- Post added at 09:50 AM ---------- Previous post was at 09:44 AM ----------
ashwath230 said:
Will flashing the mentioned zips on AEX 5.4 do any harm ? It's official one and treble TWRP only.
Click to expand...
Click to collapse
No...it will not do any harm....it only rename /factory partition to /vendor partition..By factory2vendor.zip

[EXPLAINED] z2_row (pro) | /factory to /vendor | revert to /factory - TREBLE

A GUIDE TO FLASH LATEST TREBLE ROMS, OLDER TREBLE ROMS OR NON-TREBLE ROMS ROMS
UPDATE: A guide to rename our /factory partition as /vendor so that you can flash OLDER Android Oreo treble builds! We do not need this guide on Android Pie custom ROMs or for Stock ZUI WE ONLY NEED THIS FOR ANDROID OREO TREBLE BUILDS REQUIRING /factory renamed as /vendor
for Lenovo Zuk Z2 PRO
Latest Treble : /factory renamed i.e switched to /vendor
Older Treble:/factory mounted as /vendor
Non-Treble: Nothing to do with Vendor, Factory stuff lol
INTRO
As you all know that we now have TREBLE, and Zuk-devs are working hard to improve it further so that when the time comes we can move to GSI builds of future Android versions.
Recently, Zuk-devs have renamed the /factory partition into /vendor partition previously we were mounting /factory as /vendor but now it has been converted(renamed) to /vendor partition with this you'll be able to use a Proper Magisk zip, and you don't need a modded/edited Magisk, etc and lotta other kinds of stuff that we will discuss and come to know in the future.
rootdir: fstab: Use the right label for our vendor partition.
TUTORIAL:
What you want to do:
** Flash OLD TREBLE ROMS /factory is renamed to /vendor - NOTE NOT NEEDED FOR NEWER ROMS! **
Instructions:
* Flash "Factory2Vendor_plus.zip",
*Flash belowTWRP,
*Reboot To TWRP,
*Flash ROM,
+ GApps / + Magisk etc
* Reboot.
*Enjoy :fingers-crossed:
Downloads:
Factory2Vendor_pro: https://androidfilehost.com/?fid=746010030569969371
TWRP for /factory renamed as /vendor roms https://github.com/cosmedd/android_...eases/download/20180413/20180413_recovery.img
** REVERTING BACK to NORMAL aka renaming /vendor back to/factory **
Instructions:
*Flash "Vendor 2Factory_plus.zip",
*Flash OFFICIALTWRP,
*Reboot TWRP,
*Flash ROM,
+ GApps / + Magisk etc
*Reboot.
*Enjoy :fingers-crossed:
Downloads:
Vendor2Factory_pro: https://androidfilehost.com/?fid=673956719939835215
https://twrp.me/zuk/zukz2row.html
** REVERTING BACK to NORMAL aka renaming /vendor back to/factory **
Instructions:
*Flash ROM,
+ GApps / + Magisk etc
*Reboot.
*Enjoy :fingers-crossed:
Notes:
This 'New TWRP' will work for both Latest Treble and Non-Treble RoMs
For ZUI also no need to flash any patch, New TWRP shall work (Needs to be tested)
You can flash Non Treble RoMs and Nougat Builds or other builds with the new TWRP and no patches need to be flashed
Once you flash "factory2vendor" or "vendor2factory" you do not need to flash again unless mentioned in the build
or if you want to revert back to Old Treble RoMs where /factory was mounted as /vendor
CREDITS
Zuk-devs - Davidevinavil, DD3Boh and Cosmedd (https://github.com/zuk-devs)
@Fedor917 for giving the idea
And all others who have contributed in any manner! :highfive:​

Reserved

You'll be able to use above method for Latest AEX coming soon by Davidevinavil and all the ROMs compiled using the latest sources as per by Zuk-devs
Links added, enjoy

thx

Can we make this procedure opposite? i.e. flash first twrp and than that zip? I normally flash twrp with official twrp app

1 or 2 should I do if I want to flash from the latest zui to AEX5.4 ,thx

thanks

Thanks zuk developer

I just tryed to flash Vendor 2Factory_pro..zip but I get following error "failed to mount '/vendor' (invalid argument)". I was in previous version 5.4 (1104). After restart, it does not load the rom but the bootloader. problem is the devices is not recognized under "adb devices" when in bootloader. Any ideas will be very welcome

darquesp said:
I just tryed to flash Vendor 2Factory_pro..zip but I get following error "failed to mount '/vendor' (invalid argument)". I was in previous version 5.4 (1104). After restart, it does not load the rom but the bootloader. problem is the devices is not recognized under "adb devices" when in bootloader. Any ideas will be very welcome
Click to expand...
Click to collapse
In bootloader (fastboot) you must use
fastboot -i 0x2b4c
ADB works in twrp or with system . Just follow this guide .

mar.ur said:
In bootloader (fastboot) you must use
fastboot -i 0x2b4c
ADB works in twrp or with system . Just follow this guide .
Click to expand...
Click to collapse
I installed the vendor, but the twrp is only black.
Any solution?

JustBr said:
I installed the vendor, but the twrp is only black.
Any solution?
Click to expand...
Click to collapse
Did you install latest twrp after flashing f2v

mar.ur said:
In bootloader (fastboot) you must use
fastboot -i 0x2b4c
ADB works in twrp or with system . Just follow this guide .
Click to expand...
Click to collapse
Thanks. I flashed last rom and after that updated twrp with twrp app and now I get no error about partitions.
I thought that to flash a twrp image with adb, I should do into fastboot mode. Can I also do it into recovery or system just with command : fastboot -i 0x2b4c flash recovery twrp.img?
Which guide do you mean? I checked on this thread and could not find a guide about adb.
Many thanks!

You can install twrp.img in any twrp .Just go to install/ install image and choose new twrp.img , then mark recovery and flash it .

mar.ur said:
Did you install latest twrp after flashing f2v
Click to expand...
Click to collapse
my twrp and 3.1, downloaded a recovered image(new twrp ), select image, recover and flash .. and the screen continues black, do not start twrp ... !!!!

JustBr said:
my twrp and 3.1, downloaded a recovered image(new twrp ), select image, recover and flash .. and the screen continues black, do not start twrp ... !!!!
Click to expand...
Click to collapse
I test a lot of systems . Last I was on mokee 7.1.2 with redwolf twrp with vendor partition ( not the latest ) . I install f2v.zip then twrp https://github.com/cosmedd/android_...eases/download/20180413/20180413_recovery.img . After that restart to recovery . Finally install to the latest Aex . No problems at all . First of all start with 2018.03.11 twrp , then install f2v.zip , 2018.04.13 twrp , restart to recovery and install aex or rr . That's all

Hy bro,
Can you send me the twrp version 2018.03.11 link?

failed to mount 'vendor'
After following the previous steps. TRWP start to show "failed to mount 'vendor' (invalid argument)'" message. I'm able to install the AEX 5.4, but the google apps do not crashes.
Any help?
Solved: wrong TWRP.
Nice boot animation

JustBr said:
Hy bro,
Can you send me the twrp version 2018.03.11 link?
Click to expand...
Click to collapse
https://github.com/cosmedd/android_...eases/download/20180311/20180311_recovery.img

mar.ur said:
https://github.com/cosmedd/android_...eases/download/20180311/20180311_recovery.img
Click to expand...
Click to collapse
Last help, I do everything by the pc, in fasboot mode ? or last twrp by his flash (twrp).