Database Info

[RECOVERY][TOUCH] TeamWin Recovery Project (TWRP) 2.3.2.1 [UPDATE!]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are you tired of scrolling through huge lists of files in ClockworkMod with the volume rocker?
Don't you wish there was a recovery with a graphical interface and controlled using the touchscreen?
Team Win Recovery is just that!
Built by TeamWin from the ground up based on AOSP recovery, it has a themeable GUI with touch interface, file manager, keyboard, terminal emulator and much much more...
NEW VERSION 2.3.2.1!
Note: A few devices experience random reboots/shutdowns in recovery with the latest version. If this is the case for you, use version 2.2.1 which is completely stable.
Features
Graphical touchscreen interface with buttons and drag-to-scroll!
Compressed backups that can save you up to 50% disk space
Ability to choose which partitions to back up and which to restore
Custom names for backups, rename and delete backups inside recovery
Integrated Terminal Emulator
Install queues allow you to install multiple zips in one go (e.g. CM9 zip together with gapps zip)
Easy one-button cache & dalvik cache clearing after an installation
Recovery settings are saved to the sdcard and persist through reboots
File Manager that allows you to move, copy, delete and rename files and change their permissions
Battery percentage indicator, charging indicator and clock (set your timezone in settings!)
Reboot into download mode (bootloader)
ADB support
Sideloading for automated ROM install: http://teamw.in/ADBSideload
Detailed logfile
Themeable
Download
2.3.2.1 as installable zip
http://www.mediafire.com/?6i91q2lvez9bj9p
Click to expand...
Click to collapse
Install by copying the zip file to your sdcard, booting into recovery (VolumeUp+Power) and then using "install zip from sdcard" ("apply update form sdcard" on stock recovery) to install it.
2.3.2.1 as flashable image file
http://www.mediafire.com/?ji7z7yznh25zjjp
Click to expand...
Click to collapse
Flash using broodplank's Quickflasher. Connect phone via USB, start sgsflasher_x86.exe, activate "Flash a new Recovery", select the twrp2.2.1-recovery.img and press "Start Now".
Please pay particular attention to this:
Some zips may no longer work in TWRP 2.3 if the developer is using an out-of-date update-binary. If this is a problem for you, please use TWRP 2.2.1 (download link in post below)! Zips can be fixed by replacing their old update-binary with this one.
Click to expand...
Click to collapse
FAQ
I installed this but my phone keeps booting into recovery over and over again.
You need to re-flash your bootloader as described here.
Click to expand...
Click to collapse
Can I use TWRP to restore my CWM backups?
No. The only way is to convert your uploads like this: flash CWM, restore a backup, flash TWRP, create new backup, repeat.
Click to expand...
Click to collapse
Where is my external SD card?
The external SD is under /emmc (as is standard for all CyanogenMod-based ROMs). The internal SD is under /sdcard.
Click to expand...
Click to collapse
What is the size vs speed tradeoff for compressed backups?
For my test, compression shrunk the total backup size by 43% and took 1.4 times longer.
Click to expand...
Click to collapse
Can I use this to flash CyanogenMod9?
Yes!
Click to expand...
Click to collapse
Can I use this to flash XYZ ROM?
Yes!
Click to expand...
Click to collapse
The clock shows the wrong time!
You need to set your timezone under Settings -> Time Zone. The setting is saved in a config file on your sd card so you only have to do this once.
Click to expand...
Click to collapse
My .zip file won't install!
Turn off signature verification!
Click to expand...
Click to collapse
Can I mount my SD cards on my PC in recovery?
Yes, but only one at a time. Go into the Mount menu and select which card to mount with the "Use external SD" or "Use internal storage" radio buttons. Connect your USB cable and press "Mount USB storage".
Click to expand...
Click to collapse
How can I restore single apps (and/or their data) from a TWRP backup?
Use TitaniumBackup, it supports TWRP! In Titanium Backup, open up the menu and select "Extract from Nandroid backup...". It will list all your TWRP and CWM backups and allow you to restore as many apps and their data as you want.
Even though all TWRP backup files carry the extension .win, they are either tar archives or filesystem images. System, data, cache and .android_secure are backed up as tar archives or gnu-zipped tar archives if compression is enabled. You can rename those .win files to .tar (.tar.gz if compressed) and extract them like a regular archive. Boot and recovery partitions are backed up as .img files using dd.
Click to expand...
Click to collapse
I have tried to test all recovery features and they all seem to work. I successfully flashed several different ROMs and performed backups and restores. However, there could still be bugs lurking somewhere - if you find one please report it!
Screenshots
Credits
TeamWin - Everything here is their work, I only provide a precompiled binary for our device. Particular thanks to Dees_Troy from TeamWin for his help.
arco - For the config files for our device.
Disclaimer
Do not install this if you don't know what you are doing. Incorrect flashing of a recovery can lead to a hard brick! Bugs in the recovery could result in data loss so always have a backup! I am in no way responsible for anything you do to your phone and offer no guarantees.
For Developers
TWRP has an optional companion app called GooManager. It offers a frontend for the goo.im archive which hosts ROMs and the gapps. Unlike CWM and ROM Manager, it is completely free, developers can upload their ROMs to goo.im and users can easily flash them with GooManager. It would be awesome if developers started uploading their ROMs there!
To take screenshots inside the running recovery, use adb to dump the framebuffer and then use ffmpeg to convert the raw image to a jpeg like this:
adb pull /dev/graphics/fb0
ffmpeg -vframes 1 -vcodec rawvideo -f rawvideo -pix_fmt rgba -s 480x800 -i fb0 -f image2 -vcodec mjpeg fb%d.jpg
Click to expand...
Click to collapse
Sources:
- TWRP2 github
- arco github with BoardConfig.mk etc. for I9001/ariesve
- Configuration parameters for TWRP in BoardConfig.mk:
Code:
DEVICE_RESOLUTION := 480x800
TW_INTERNAL_STORAGE_PATH := "/sdcard"
TW_INTERNAL_STORAGE_MOUNT_POINT := "sdcard"
TW_EXTERNAL_STORAGE_PATH := "/external_sd"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"
TW_DEFAULT_EXTERNAL_STORAGE := true
TW_FLASH_FROM_STORAGE := true
This is a straight, unmodified compile of TWRP2 sources. TWRP2 is made available under the Apache License 2.0.

Over 27000 downloads as of November 17th! Rock on!
Changelog:
2.3.2.1
- Small bugfixes
2.3.1.1
- Fixed keyboard not working for backup rename bug
2.3.0.3
- Faster boot
- Much faster permission repair
- Charging indicator (only updates once a minute)
- Major code rewrite to C++ and Jelly Bean base
- ADB Sideload functionality - for automated ROM installs, see http://teamw.in/ADBSideload
- USB storage mounting now mounts both internal and external sd cards simultaneously
2.2.1
- Small bugfixes
- Trying to fix the random shutdown bug that happens on some devices
2.2.0
- Integrated Keyboard
- Set custom backup name
- Terminal emulator
- Rename files in file manager
- Set file permissions using octal notation in file manager
- Rename and delete backups
- Restore menu has switch for internal/external SD
- Fixed timezone names
- Wipe external SD option
- Wipe battery stats and rotation data options removed (Google says it's unnecessary. You can still do it manually/with apps if you want.)
- Fixed themes not loading bug
2.1.8-fix
- Fixed USB storage mounting
2.1.8
- Initial release for the Galaxy S Plus
Old Downloads:
2.3.1.1 as installable zip
http://www.mediafire.com/?l78dskdap2xghd7
2.3.1.1 as flashable image file
http://www.mediafire.com/?hhqmgmqq3a37q7s
2.3.0.3 as installable zip
http://www.mediafire.com/?ld9iupspojsdmq2
2.3.0.3 as flashable image file
http://www.mediafire.com/?zqwou2f353n945p
2.2.1 as installable zip
http://www.mediafire.com/?0ufe8dcv5kkajay
2.2.1 as flashable image file
http://www.mediafire.com/?aknf6rjpxj16wrv
2.2.0 as installable zip
http://www.mediafire.com/?6nb6clnwn9w1247
2.2.0 as flashable image file
http://www.mediafire.com/?7afs5n39nbkop22
2.1.8 as installable zip
http://www.mediafire.com/?9bh66rw6uqbt9tm
2.1.8 as flashable image file
http://www.mediafire.com/?km077vhodky7rsb

Cm9 compatible ?

UpGado said:
Cm9 compatible ?
Click to expand...
Click to collapse
Yes!

no problem in cm9？ example.. wifi .BT....because arco recovery fixed some problem in cm9
Sent from my GT-I9001 using XDA

Ezekiel1998 said:
no problem in cm9？ example.. wifi .BT....because arco recovery fixed some problem in cm9
Click to expand...
Click to collapse
This is a Recovery, not a ROM!
A recovery is a small bootable operating system on a seperate partition on your device. Changing your recovery does not in any way affect your running system. And when booted in the recovery you don't have access to WiFi or Bluetooth anyway.
The reason FeaMod does not work with CM9 is because it was compiled with a wrong list of partition sizes. I compiled this using arco's CM9 repository, so it has exactly the same settings, kernel config etc. as the CM9-compatible CWM that arco compiled.

looks awssum shall try flashing an xperimental.zip
Sent from my GT-I9001 using Tapatalk 2

Is this somewhat related to cmw touch recovery ?

Awsome work!!!
Sent from my GT-I9001 using XDA

In restore it is showing nothing....can anybody else confirm it?
Sent from my GT-I9001 using Tapatalk 2

You must make a backup with teamwin recovery. Maybe you can copy your CWM Backup into the Teamwin recovery folder for restore your backup.
Sorry for my english.
Gesendet von meinem GT-I9001 mit Tapatalk

Awesome thanks for your work
Sent from my GT-I9001 using Tapatalk

wow...nice recovery... thanks for your work!!

This is RECOVERY it has nothing to do with any of the ROMS !!! RESTORING BACKUP from other RECOVERIES is not recommended, it will end up bricking your phone! NEVER RESTORE BACKUP WITH DIFFERENT VERSIONS OF RECOVERY, EVEN IF IT IS MADE FROM SAME SOURCE.
RECOVERY cannot be "compatible" or "incompatible" with ANY of ROM distro's.
Restoring someone's nandbackup (CM9 with arco recovery, for example) on own phone is other story.

BzArEx said:
Is this somewhat related to cmw touch recovery ?
Click to expand...
Click to collapse
No, it was developed from scratch by TeamWin. It is also open source and completely free unlike CWM touch which you have to buy.
You can read more at the official project website: http://teamw.in/project/twrp2

F**k the system . AMAZING WORK!!!!!!

Yay!
Awesome work! I was waiting for a touch recovery!
btw, can we flash CWM over this afterwards, just in case i want to restore a CWM backup later on?

Awesome work bro....
Sent from my GT-I9001 using xda premium

sidsweb said:
btw, can we flash CWM over this afterwards, just in case i want to restore a CWM backup later on?
Click to expand...
Click to collapse
Yes, you can change recoveries without a problem.
For arco's CWM flash this zip file and then reboot the recovery. Later in CWM you can just flash the TWRP zip, reboot recovery and you're in TeamWin Recovery again.
This is also how I suggest people migrate their backups (if really necessary): Install and reboot into CWM, restore a CWM backup, install and reboot into TWRP, perform a backup, repeat.

Works great, just installed Arcos build 4 with your Recovery.
Awesome!

[RECOVERY][Unofficial][ICS] TWRP 2.2.1.4 Custom Recovery (DOES NOT WORK WITH MTD)

Hello, Infusers...im back and ive brought with me TeamWin Recovery Project! Official TWRP website: http://www.teamw.in/project/twrp2
What is this?
-Its an alternitive to CWM recovery
What are the advantages?
-Full touch screen interface
-Built in file manager
-keyboard (gives you the ability to name your backups...or rename other files from with in recovery)
-clock
-battery percentage
-swipe to confirm flashes/wipes (no more of the "no no no no yes no no"
-themeable!!!
-and more!!!
***DOES NOT WORK WITH MTD JELLYBEAN...yet***
Unfortunatly our recovery is built into the boot.img after flashing any ics rom you will lose the twrp recovery and get cwm recovery again...just tick the box to re-inject twrp before sliding to confirm your flash...or go to advance options and click on re-inject twrp
Download:
TWRP
Flashing Instructions (does not effect your current set up/kernel...only replaces CWM)
1) boot into recovery
2) flash zip
3) reboot
4) next time you go to recovery you will have TWRP
5) Flash this zip after every new rom flash to keep TWRP
***important for updating***
-if updating twrp from a previous build make sure you disable "re-inject twrp after flash" if you dont it will reinject the old twrp
-If coming from gingerbread you have to boot into your ics or jb Rom before being able to flash the zip...after that you can flash after every Rom flash
how does the zip work? i thought it was built into the boot.img?
Credit goes to smasher816 for this..he made an install script that takes your boot.img of your rom, then takes the recovery ( ramdisk-recovery.img) and injects it into your current boot.img...leaving the actual kernel untouched!
Satandard Disclaimer
Use this recovery at your own risk!!! im not responsible for anything that happens to you, your phone, your friends, your family, or anything but i will do my best to resolve any and all problems you may encounter
Thanks/Credit:
TeamWin-Recovery/source/compiling instructions
Entropy-CM9/kernel/guide for compiling/source
JT-for getting us ics in the first place
JScott30-sold me his infuse which allowed for me to do this
Smasher816-your install script has allowed for an easy recovery flash
Did i miss anyone? -let me know...dont want to leave any one out

{
"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"
}
the above screen shots were taking from http://www.teamw.in/project/twrp2
the below screenshots are pictures taken of my infuse with it in action
And...video of it in action
http://www.youtube.com/watch?v=7gJ7idj8y0g&feature=plcp

TWRP-2.2.1.4 8-6-12
-fixed aroma
-should be completly bug free
TWRP 2.2.1 6-8-12
-updated to twrp 2.2.1.4
-fixed backups
TWRP 2.2.1 8-3-12
-Added the abilty to reinject twrp through an option under the advanced menu...use that option or reflash zip
TWRP 2.2.1 sdfix
-Fixed sdcard error
-fixed install script so you no longer have to mount system in mounts instorage...just flash the zip and it will mount for you
8-2-12
-initial release

Things to do...
1) Figure out if its possible to compile the recovery and flash it with out messing with a user's kernel/current set up
-solved...op has been updated with fix
2) fix the sdcard error
-solved...op has been updated with fix
3) fix backup problem (cant create a backup)...currently the only known bug
-solved fix uploaded to goo.im
4) make a CWM recovery zip for people who want to go back to CWM
-done, added as an atachment to the op
5) fix the aroma bug...
-fixed...uploaded to goo.im
6) Keep this up to date with official twrp source
-on going process...ill check every other day for updates to the source
TWRP THEMES
You can find some themes for twrp here: TWRP 2.X Themes
-keep in mind that themes can introduce bugs...so use them at your own risk...if your intrested in creating your own them check out this: http://teamw.in/project/twrp2themers
-themes must go in this directory /sdcard/TWRP/theme/ and it must be named ui.zip -reboot to recovery and it will be applied...thats right just reboot no need to flash!
My TWRP Themes -hosted on goo.im (soon to be featuring every color of the rainbow...and then some)
Inverted theme! by supernewbdev

First....
Very nice bro..this is awesome no more vol up+down button and power when flashing roms when your are in recovery mode and all fully touch screen...good job sir

Nice man always great to have options!
Sent from my SGH-I997 using xda app-developers app

I have been wanting to try twrp in my infuse since I tried it on my transformer.
This is a great addition to our community, Thanks for bringing it! :victory:
Edit: I presume it still not compatible with JB, am i right?

andros11 said:
I have been wanting to try twrp in my infuse since I tried it on my transformer.
This is a great addition to our community, Thanks for bringing it! :victory:
Edit: I presume it still not compatible with JB, am i right?
Click to expand...
Click to collapse
At the moment no...its built into the ics boot.img -so flashing this would give you an ics kernel
Not sure when and if ill be able to bring it to JB...will have to wait for TeamWin to update it for JB
EDIT: i think i know how to let people use this without messing with there current kernel/set up...gotta test the theory first
Edit #2...theory correct...no more will you have to flash the boot.img or CM9 to get TWRP...OP will be updated shortly with details

Omg. Mg this is awesome downloading as of now
Edit: can the boot.img be flashed with sgs kernel flasher?
Edit#2: saw the zip flashed it and it works like a charm.
Sent from my AOKP'd Infuse 4G​

OP updated...just download the zip and flash it-next time you boot to recovery you will have TWRP...just make sure you mount system before flashing...
EDIT: if my other theory is correct...this may now be compatible with JB...gonna download cm10 now and test the zip with it...will report back later

isaiahe97 said:
Omg. Mg this is awesome downloading as of now
Edit: can the boot.img be flashed with sgs kernel flasher?
Sent from my AOKP'd Infuse 4G​
Click to expand...
Click to collapse
not sure...but you can download the zip and flash that instead in recovery...it will not mess with your rom or kernel

works with jellybean...just mount system and flash the zip...

Recovery updated...fixed the sdcard error, as well as edited the updater script to mount system...in other words you dont have to mount system in "mounts and storage" anymore just download and flash
currently only known bug at the moment is not being able to create a backup...im looking into it
EDIT: Just found out there's a way to enable the recovery to auto insert itself after every Rom flash...currently working on it...if it works then one flash and you will have it for good! It will be added to the advanced settings I believe...so you can enable the auto insert or disable it if you wanna go back to old cwm...
EDIT 2: alright...misread...it doesnt auto insert :/ but still useful tho heres what it does: after flashing a rom instead of flashing the recovery zip again you go to advanced options, in there on the bottom right corner you will see the option to "re-inject TWRP" it essentially does the same thing as the zip...so if you delete the zip or dont wanna flash the recovery zip ever again just use that option after every rom fash and it will inject the recovery into the rom
ill include the re-inject option in the next update (when i figure out and fix the backup problem...) unless you guys want that now...just dont wanna do a bunch of tiny updates in one day lol...i feel like that would be annoying for you guys

Been getting tired of CWM so i am gonna have to try this out. Thks:cyclops::good:
BTW. Doesn't the face plate on the Otterbox case mess with infared sensor in detecting during calls.
I got a Ballastic case the other day and i couldn't seem to hang up a damn phone call after rebooting
---------- Post added at 11:21 PM ---------- Previous post was at 11:09 PM ----------
mg2195 said:
OP updated...just download the zip and flash it-next time you boot to recovery you will have TWRP...just make sure you mount system before flashing...
EDIT: if my other theory is correct...this may now be compatible with JB...gonna download cm10 now and test the zip with it...will report back later
Click to expand...
Click to collapse
Might wanna edit the OP.....
1) boot into recovery
2) Mount system (mounts and storage > mount /system)
3) flash zip
4) reboot
5) next time you go to recovery you will have TWRP
6) Flash this zip after every new rom flash to keep TWRP
Click to expand...
Click to collapse

slicingtaco said:
Been getting tired of CWM so i am gonna have to try this out. Thks:cyclops::good:
BTW. Doesn't the face plate on the Otterbox case mess with infared sensor in detecting during calls.
I got a Ballastic case the other day and i couldn't seem to hang up a damn phone call after rebooting
---------- Post added at 11:21 PM ---------- Previous post was at 11:09 PM ----------
Might wanna edit the OP.....
Click to expand...
Click to collapse
I fixed it so that when you flash it you no longer need to mount system...if you have the twrp 2.2.1 sdfix then you no longer need to mount system (I added the command in the updater script to.mount it)
Sooooo...just download, flash and enjoy...
Anyways...two days of non stop compiling...and I'm only doing recovery...don't know how the guys (Scott) at the CM10 thread do it...I'm pooped, time for bed
Also I don't use my infuse as my DD...so I don't have a sim in it...I use it for development only...my vivid is my DD
Sent from my HTC Holiday using Tapatalk 2

first of all, coolioso ! second, thanks! third, ok so to make sure, do I flash a rom, then reboot into recovery, then flash this alter-recovery, or can I just flash it along with the rom and the gapps ect.?

I'm loving this MG, This looks and feel so good. Thanks
Sent from my SGH-I997 using Tapatalk 2

Excellent work. Thank you.

megazeroxuxm said:
first of all, coolioso ! second, thanks! third, ok so to make sure, do I flash a rom, then reboot into recovery, then flash this alter-recovery, or can I just flash it along with the rom and the gapps ect.?
Click to expand...
Click to collapse
You can flash this and reboot into recovery
You can flash it after a Rom flash
You can flash it anytime...but if you flash a Rom make sure you flash this again
Sent from my HTC Holiday using Tapatalk 2

Back up will be great. I know you are working on that issue.
Also, will this only work with the Samsung Infuse 4G.

CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1

CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1​
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.40.1)
https://docs.google.com/uc?id=0B5c3gpyMBJusXzRMMG1tLUxRMWM&export=download
aromafm_beni.zip (v1.91)
https://drive.google.com/uc?id=0B5c3gpyMBJusc204SHRZdTBucHc&export=download
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
XDA:DevDB Information
PhilZ Touch Recovery for Galaxy Fit, Tool/Utility for the Samsung Galaxy Fit GT 5670
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-07

:FAQs:​
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.

NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary
commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"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"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root

i tried your recovery by creating a zip update
you should work more on it because the graphic in some aroma installer or aroma file manager doesnt work too good!
and just feels the normal CWM and not Philz recovery !
But any way, Good Job!

Rminsh said:
i tried your recovery by creating a zip update
you should work more on it because the graphic in some aroma installer or aroma file manager doesnt work too good!
and just feels the normal CWM and not Philz recovery !
But any way, Good Job!
Click to expand...
Click to collapse
Aroma File Manager has no LDPI resources. If you want it for LDPI, you can do it, it's an Artist's work. I'm not gonna do it.
Please read the first post carefully. It has no GUI options: So, no themes and all that.
It's not at all like normal CWM in terms of functions. It has got many important functions, atleast for me.
Most important part:
I've worked on this advanced only version for 20-25 days already and made it fully stable.
And...I've worked for almost 2 months on FULL VERSION. Discussed a lot with Phil3759 and finally came to conclusion that it won't work on armv6 unless it's (libtouch_gui) specially compiled for armv6, Which Phil3759 didn't have time and resources for.
So, Be happy with this recovery. No one can give you better philz recovery than this, atleast at present.

Installed your recovery.
Selected clean install ROM option.
Installed a ROM.
Selected Reboot System.
Phone rebooted into your recovery.
Tried various ROMS all rebooted into your recovery and not to the newly installed ROM.
Flashed CWM 6.0.4.6 and installed a ROM and rebooted to installed ROM successfully.
Any ideas what is wrong?
I do like the Aroma FM.
jemail

jemail said:
Installed your recovery.
Selected clean install ROM option.
Installed a ROM.
Selected Reboot System.
Phone rebooted into your recovery.
Tried various ROMS all rebooted into your recovery and not to the newly installed ROM.
Flashed CWM 6.0.4.6 and installed a ROM and rebooted to installed ROM successfully.
Any ideas what is wrong?
I do like the Aroma FM.
jemail
Click to expand...
Click to collapse
Yep...you're correct.
It won't boot into system.
I finally figured out that it is a problem in androidarmv6 sources. You can see change #6205 if you want.
It was maybe fixed just 4-5 days ago by androidmeda and I'll be again making the recovery and give you all for testing.
This is not only problem of your device but it is also there in: tass, gio and beni.

Bhargav97 said:
Aroma File Manager has no LDPI resources. If you want it for LDPI, you can do it, it's an Artist's work. I'm not gonna do it.
Please read the first post carefully. It has no GUI options: So, no themes and all that.
It's not at all like normal CWM in terms of functions. It has got many important functions, atleast for me.
Most important part:
I've worked on this advanced only version for 20-25 days already and made it fully stable.
And...I've worked for almost 2 months on FULL VERSION. Discussed a lot with Phil3759 and finally came to conclusion that it won't work on armv6 unless it's (libtouch_gui) specially compiled for armv6, Which Phil3759 didn't have time and resources for.
So, Be happy with this recovery. No one can give you better philz recovery than this, atleast at present.
Click to expand...
Click to collapse
i read that!
pay attention: the aroma that use in every CWM works fine
but in your recovery it has a bad graphic and kind of blue!
i mean before you create this Philz recovery we had a older version that works perfect!
http://forum.xda-developers.com/showthread.php?t=2483327

Rminsh said:
i read that!
pay attention: the aroma that use in every CWM works fine
but in your recovery it has a bad graphic and kind of blue!
i mean before you create this Philz recovery we had a older version that works perfect!
http://forum.xda-developers.com/showthread.php?t=2483327
Click to expand...
Click to collapse
It works perfect just in the sense: It reboots to system successfully. It lacks Aroma file manager also. And, Aroma file manager with that original green colour doesn't come with armv6 sources nor it will come if you download from original thread.
I'll be fixing reboot to system soon.
That recovery doesn't even have Touch, GUI options and all that.

UPDATE:
-Updated PhilZ sources to 6.23.9 (26.03.2014).
-CM-OTA compatibility fixes.
-Reboot to system bug fixed.
Download link updated in first post.

Bhargav97 said:
UPDATE:
-Updated PhilZ sources to 6.23.9 (26.03.2014).
-CM-OTA compatibility fixes.
-Reboot to system bug fixed.
Download link updated in first post.
Click to expand...
Click to collapse
Thanks for this.
Reboot system is working
Aroma File manager is working
I will test and report any bugs if find them.
Does this version reformat ext4 partitions as ext3 when doing a restore?
jemail

jemail said:
Thanks for this.
Reboot system is working
Aroma File manager is working
I will test and report any bugs if find them.
Does this version reformat ext4 partitions as ext3 when doing a restore?
jemail
Click to expand...
Click to collapse
It reformates the partition to the state in which it was in your backup file. The working of this PhilZ Recovery will be the same way as your CWM 6.0.4.7 works. Nothing different except features.

Tested, worked fine with aroma file manager. Flashed cm 11 has no error.
Keep your work
Here is temporary flashable zip file

As I reported previously in another Clockworkmod thread here, this version also does not restore SD-Ext Ext4 formatted partitions correctly. SD-Ext Ext4 partitions are restored as Ext3 not Ext4.
You can verify this by
1. Create an Ext4 partition on your sdcard using MiniTool Partition Wizard.
2. In CWM create a nandroid backup.
3. Immediatley restore the backup.
4. Check sdcard partition structure in MiniTool Partition Wizard, you will find the partition you created as Ext4 is now reported as Ext3.
Can you confirm this?
Can you remove all background images from your release, maybe except the ClockworkMod Logo. Background images make reading the output from operations difficult.
jemail

jemail said:
As I reported previously in another Clockworkmod thread here, this version also does not restore SD-Ext Ext4 formatted partitions correctly. SD-Ext Ext4 partitions are restored as Ext3 not Ext4.
You can verify this by
1. Create an Ext4 partition on your sdcard using MiniTool Partition Wizard.
2. In CWM create a nandroid backup.
3. Immediatley restore the backup.
4. Check sdcard partition structure in MiniTool Partition Wizard, you will find the partition you created as Ext4 is now reported as Ext3.
Can you confirm this?
Can you remove all background images from your release, maybe except the ClockworkMod Logo. Background images make reading the output from operations difficult.
jemail
Click to expand...
Click to collapse
1) I don't have your device but in my Galaxy 5 it works fine. I make backup (have an sd-ext and has some stuff also inside) and then restore it and everything is still fine. Link2sd still detects it as ext4. Even if it's a bug, it is not related to my PhilZ Recovery but to the androidarmv6 sources and I maybe can't do anything for it (don't have time to submit a patch for review...maybe I don't have that expertise too).
2) Which logo you mean? The one with Big Green Android? I would prefer to keep it that way...don't wanna make it lean more towards an unofficial build. However, I won't be able to do it (even if I want to) right now because my PC is busy and I can't compile on it right now.
Once I get my PC free, I'll make TWRP for your device and provide a final (final for some time) update for PhilZ Recovery (less probability though for PhilZ update).

When I was flashing a rom with aroma (miui v4 to be precise) its showed me get.prop errors.
Saying that my device is not beni and not 5670
And this happened only on this recovery and only with roms with aroma installer, rest of the roms work fine.
And for the TWRP version, TWRP cannot flash memory scripts (like cronmod's int2ext)
Can something be done for that?

Harpratap said:
When I was flashing a rom with aroma (miui v4 to be precise) its showed me get.prop errors.
Saying that my device is not beni and not 5670
And this happened only on this recovery and only with roms with aroma installer, rest of the roms work fine.
And for the TWRP version, TWRP cannot flash memory scripts (like cronmod's int2ext)
Can something be done for that?
Click to expand...
Click to collapse
Aroma installer's dev OR miui rom's dev is lazy to update the update-binary. KitKat requires new update-binary because Google changed the way getprop worked uptil Jellybean.
TWRP? I don't think I've made a TWRP for Galaxy Fit yet.
I wanna tell you only one thing: You are using everything from latest KK branch: PhilZ Recovery and TWRP (maybe you're talking about the one of Galaxy Mini), so please take some time to read on: What all Google changed in recovery with KitKat. Your int-ext script is suffering from old update-binary for sure.

MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJusVmZUN2UxdHFtaWs/edit?usp=sharing

Awesome!
All gui and touch functions work properly.
Flashed a zip and everything works fine except reboot system and power off.
Both of them simply reboot into recovery.
Will report other bugs if found.
And nice job :good:

A little bug. Fixed it.
https://drive.google.com/file/d/0B5c3gpyMBJusSk41Q002c3lneUk/edit?usp=sharing
Give me feedback. Everything else like: screenshot double-tap shortcut for aroma fm (read first two posts to understand), GUI options, etc are especially needed for testing. Post some screenshots also.

Twrp recovery

TWRP for XOLO Q3000​
Here is TWRP for xolo Q3000 .
{
"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"
}
I request
chinasa
@allan.vaz
@amrutb
@Jagadish-ravi
@qwerty.3551
@ravikumarbeniwal
@rohithdivakaran
@rufus.reynolds
@sushbabblu
@Vineet3
@smahalgavaiya
@vijay jay
m0han
@aabidhashmi
@barath anandan
 @drlalitbida
 @fort21
@nihar13
@qwerty.3551
@sanyamjain
@Sandy d Candy
@SPG30759
@ranjanshandilya
@Rishi45
 @indigo110
@rahulhacker007
@sunny76900
@patilsb
@akxolo
@xoloq3000
@ravi_21
@mhp1995
@Karan_Kapuria
@nicksaisw
@Aftab Memon
@ashuchem
@Haldar_dhruv
@rohitsinghpu
@beinglazy
@viru_192 
 @chaobuddy
@irfanjunaid
@arnabbiswasalsodeep
@Anand Ramesh
@ashishji12
ApriliaM3
Please try this recovery and report back about JB and KK rom switching.
In TWRP 2.8 u cant root with it as supersu is deleted from recovery to reduce size.
As we have other flashable zips to root it wont be an big issue.
Waiting for response from u guys.​
Credits-
@yuweng Sir this wont be possible without his tool
TWRP team 
 @hanuma for help:good:

avi3230 said:
In TWRP 2.8 u cant root with it as supersu is deleted from recovery to reduce size.
As we have other flashable zips to root it wont be an big issue.....
Click to expand...
Click to collapse
i'm on clone stock kk rom with cwm v6.0.2.8 now. i wanna have twrp v2.8 and also root. how best to go about it?
does your op imply "if twrp v2.7 is used, root is not lost"? - on rooted device having any other custom recovery.
and, what if i flash your twrp v2.8 and then flash supersu zip file from here? will i have proper root?
btw, can this be installed using flashify or mobileuncletools? or, is spftools procedure itself required?
suggest that you make the op clearer and noob-friendly. thanks.

m0han said:
i'm on clone stock kk rom with cwm v6.0.2.8 now. i wanna have twrp v2.8 and also root. how best to go about it?
does your op imply "if twrp v2.7 is used, root is not lost"? - on rooted device having any other custom recovery.
and, what if i flash your twrp v2.8 and then flash supersu zip file from here? will i have proper root?
btw, can this be installed using flashify or mobileuncletools? or, is spftools procedure itself required?
suggest that you make the op clearer and noob-friendly. thanks.
Click to expand...
Click to collapse
Make sure you flash stock rom first before flashing this recovery! When i was using Q900, it used to give variety of errors! So always begin with clean flashed device! The error that i got frequently was E: cannot mount /Data bla bla.... Always ended up with mounting errors! Then came Shikar bro who ported the recovery and after which i developed the custom first custom ROM!

irfanjunaid said:
Make sure you flash stock rom first before flashing this recovery! When i was using Q900, it used to give variety of errors! So always begin with clean flashed device! The error that i got frequently was E: cannot mount /Data bla bla.... Always ended up with mounting errors! Then came Shikar bro who ported the recovery and after which i developed the custom first custom ROM!
Click to expand...
Click to collapse
Anyone having this issue???
I didnt got it.
working correctly till now
but thanks for the info:good:

m0han said:
i'm on clone stock kk rom with cwm v6.0.2.8 now. i wanna have twrp v2.8 and also root. how best to go about it?
does your op imply "if twrp v2.7 is used, root is not lost"? - on rooted device having any other custom recovery.
and, what if i flash your twrp v2.8 and then flash supersu zip file from here? will i have proper root?
btw, can this be installed using flashify or mobileuncletools? or, is spftools procedure itself required?
suggest that you make the op clearer and noob-friendly. thanks.
Click to expand...
Click to collapse
U cant root using 2.8 recovery.
sometimes if rom is not rooted then at end of flash it ask u to root, 2.8 cant do that but 2.7 can:good:.
u cant have 2.8 with root facility as size will exceed 6mb.
u can root device using any flashble root zip.
================================================================================================
For kitkat 4.4.2 the zip in link is not at all useful.
Also it cant be rooted with supersu provided in recovery
so if u wanna use 2.8 u cant use rooting within recovery.
if u wanna root ur 4.4.2 see this post method 8 definatly works.
also if u want supersu as root app head over to this post.
For recovery flashing I always prefer sp tool method which will work 100% and u dont have to bother about properly rooted device.
if u have rooted device flashify or mobileuncle tool should work.

Hi Avi, when i tried to flash the recovery via flashify my stock recovery is gone as well as the one which i flashed twrp also gone and currently my phone is running without recovery

sushbabblu said:
Hi Avi, when i tried to flash the recovery via flashify my stock recovery is gone as well as the one which i flashed twrp also gone and currently my phone is running without recovery
Click to expand...
Click to collapse
Please try with sp tools.
if u running 4.4.2 flashify may give this type of error.

TWRP - 2.8 - 94 downloads:good::good::good:

avi3230 said:
TWRP - 2.8 - 94 downloads
Click to expand...
Click to collapse
weird graphics and touch issues were reported in 2.8.0.0. how about 2.8.2.0?
bovirus said:
TWRP released a bugfix for TWRP 2.8.1.0 . Now it's available TWRP 2.8.2.0.
Click to expand...
Click to collapse

m0han said:
weird graphics and touch issues were reported in 2.8.0.0. how about 2.8.2.0?
Click to expand...
Click to collapse
Yes Sir,
I ported 2.8.2.0 but the size is 6.54mb way too much than recovery partition.
I am trying much hard for more than 6 mb partition which can boot in recovery.
Already bricked my device several times for the same.
But still only 6 mb recovery can boot.
NOw we have two options.
Compile new kernel with less size - source codes are needed
we have bq codes - but it may not work for our device - so i am much reluctant to take chance.
we need to compile new uboot.bin which can make booting in recovery of even 11mb size
again source code and compiling.
If anyone from ur side can help in compiling that would be great- as i am just beginner for it
u can get source code for BQ here.
Thank you.

avi3230 said:
....If anyone from ur side can help in compiling that would be great.....
Click to expand...
Click to collapse
sorry. no knowledge in these matters. hope someone else would come forward.

avi3230 said:
...I ported 2.8.2.0 but the size is 6.54mb way too much than recovery partition.
I am trying much hard for more than 6 mb partition which can boot in recovery.....
Click to expand...
Click to collapse
any hope for latest version of twrp?
please see screenshots of twrp v2.8.0.0. the interface is not clear (highly pixelated). the actual display is worse than seen here. can anything be done about it?
does anyone know of any themes than work on twrp v2.8.0.0 for xolo q3000? the ones i tried didn't work although i chose the correct resolution.
also, what exactly does "repair or change file system" do?
my device gets connected as an mtp device and shows up as a separate device in "my computer". i mean, the sd cards do not get connected as separate usb drives.
i can open the device and see both my sd cards listed and also browse & carry out operations. but, any changes made are not reflected even after 'refreshing'.
if i click "disable mtp" as seen in the 3rd screenshot, will the disabling be temporary or permanent? will my sd cards get connected as separate usb drives?
i'd appreciate it if someone who has authentic knowledge about these matters responds with suggestions. thanks for any help.
btw, i hope @avi3230 is following this thread. maybe we can hope for ctr v3.0 kitkat for xolo q3000 soon.
edit: saw this thread only now . will try that and report :good:. please answer the queries in blue. thanks.

@m0han
TWRP 2.8.2.0 coming soon.
themes for 2.8.0.0
what exactly does "repair or change file system" do?
answer is here.
What's new in 2.7.1.0:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Click to expand...
Click to collapse
MTP is also mentioned under 2.8.0.0
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Click to expand...
Click to collapse
I am following CTR :good::good:

avi3230 said:
....MTP is also mentioned under 2.8.0.0....
Click to expand...
Click to collapse
i'd like to know about this:
m0han said:
....if i click "disable mtp" as seen in the 3rd screenshot,
will the disabling be temporary or permanent?
will my sd cards get connected as separate usb drives?....
Click to expand...
Click to collapse
any idea about this?

[RECOVERY][MOD] MultiROM v33 + TWRP v3.1.1 for Xiaomi Mi MIX (lithium)

{
"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"
}
MultiROM is one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
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.
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
To decrypt your device:
Backup ALL your data if you need to recover later (TWRP backup to USB or copy to your PC)
In fastboot mode:
Code:
fastboot format userdata
In TWRP: Flash Magisk (recommended) or SuperSU to avoid auto-encryption in next boot.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP). Flash it as usual TWRP (fastboot flash recovery, or any flasher app if you're rooted).
MultiROM. Install it as usual zip from modded TWRP once flashed.
Go into TWRP MultiRom settings and be sure that "Enable No-KEXEC Workaround" is enabled (enabled by default)
Your current rom will not be erased by the installation.​Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to 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 MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
MIUI ROM as Secondary <--- Latest versions fix this, so you shouldn't need it anymore
Install MIUI as secondary via MultiROM settings in TWRP
Boot into your (rooted) primary
Edit fstab.qcom file in /storage/emulated/multirom/roms//boot/ and add /cache partition entries:
Code:
/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait,check,formattable
/dev/block/bootdevice/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check,formattable
Alternatively you can use attached file "fstab.qcom.txt" (rename to: fstab.qcom without .txt ). Be sure to set proper permissions (copy from original fstab.qcom, after renaming to fstab.qcom.bak, don't delete it...)
DON'T FORGET to flash Magisk / SuperSU after flashing to avoid re-encryption if you're flashing stock (not modded).
Known issues
You must wait a few seconds (3-5) before you get touch screen responsiveness in TWRP and MultiROM. (fixed by 2017.08.01 build) -- USUAL WHEN SWITCHING FROM MIUI
Some FCs on some secondary ROMs: Try using multiromfix.zip, thx to @Startrek852 (to disable sdcardfs support in that secondary) -- USE MAGISK 13.5+
Issues with TWRP to boot on 4GB/128GB model... (Working on troubleshooting...) -- PRELIMINARY FIX HERE
Reporting issues
As you surely understand, a simply "it does NOT work" is not enough... so please, report your issue describing scenario as much as you can, try following this (as much as possible information is welcome, it's very tiring for me asking what this, what that, etc...):
Issue description (what, how, when, etc...)
Device model : 4GB or 6GB RAM
Decrypted? /cache and /data FSs ? (We assume IS decrypted becaues you're using MultiROM, and EXT4 FS for /cache and /data if you don't know or manually formatted to F2FS)
TWRP version + MultiROM version
Primary ROM (name, better with version)
Firmware version
Secondary ROM (the one with the issue, name and better version)
Custom kernel ? (name and version if so) <--- In theory, we shouldn't support scenarios with custom kernels.... (they can touch system stuff that make things more complex)
Xposed ? <--- Sorry we DON'T support MultiROM if you use Xposed
Google Apps (name, better with version)
Magisk / SuperSU (version and if you use it in Primary and/or Secondary and version)
Logs <--- This would be amazing great and helpful !!!! (you can get them via adb shell, terminal or using any tool)
*Original post and example in this post, please: ​
Download
You can download all stuff from here, where you can find latest TWRP and MultiROM. If you need to uninstall MultiROM, you can use this uninstaller.
MultiROM Manager (apk) available here.​
Source code
MultiROM - https://github.com/MultiROM-dev/multirom
Modified TWRP - https://github.com/multirom-dev/Team-Win-Recovery-Project
MultiROM device tree - https://github.com/BitOBSessiOn/android_device_xiaomi_lithium​
Special thanks to:
@Tasssadar for creating this awesome utility
@nkk71 for the No-KEXEC workaround
@AdrianDC and all MultiROM guys involved in its development
@jcadduono for TWRP port

We will have to try soon... It's the perfect set up for flashaholics

Great news [emoji847][emoji847]
Envoyé de mon MIX en utilisant Tapatalk

I can't make it work

fil0s0f0 said:
I can't make it work
Click to expand...
Click to collapse
The MultiROM app from market is only for official devices (I haven't updated the Android app, imo it's not very useful), So you must follow OP steps.
If you have some issue, please, describe your problem and we will try to help.
Keep in mind that you must have unlocked bootloader, decrypted device, etc...

Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback

fil0s0f0 said:
Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback
Click to expand...
Click to collapse
Yes, there are, please, revise OP, and describe which steps have you followed to find out what's your issue. Thx

provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output

Superb, I missed it in this great smarphone

acasmc said:
provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output
Click to expand...
Click to collapse
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.

BitOBSessiOn said:
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.
Click to expand...
Click to collapse
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.

acasmc said:
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.
Click to expand...
Click to collapse
Too weird... I've just downloaded and flashed again with rashr and ok.
Which model do you own (128/256)? Primary rom...?
TWRP must work ok with encrypted /data (but you need decrypted for MultiROM).

I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.

acasmc said:
I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.
Click to expand...
Click to collapse
Can you try some of older versions in testing or backup folder in n AFH, please...?
Can you take a photo of error if it still occurs...?

there is only one TWRP in your folder. can you point me to another. I'll try no worries

acasmc said:
there is only one TWRP in your folder. can you point me to another. I'll try no worries
Click to expand...
Click to collapse
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564

Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]

Konsstantine34 said:
Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]
Click to expand...
Click to collapse
Usually I don't start to develop for a device before I can use MultiROM....

BitOBSessiOn said:
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564
Click to expand...
Click to collapse
tried other two that are on that link. still the same. sadly don't have another phone with me, to take a picture.
guess gonna have to wait for an update. :/

BitOBSessiOn said:
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
Click to expand...
Click to collapse
About encrypting, Is it enough to flash the "no-verity-opt-encrypt-5.1".zip?, And if its not, Is there a guide of how to encrypt my device?