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.
Related
{
"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!
TWRP Recovery
{
"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"
}
DISCLAIMER
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Features
Recovery gone App: Designed to mimic the look and feel of an Android app.
Customisable UI: 15 different accent colors, center clock option, different navbar button layouts...
Added functionality: ability to flash image files (recovery, radio, boot), ability to change the recovery splash screen, bookmark function for file lists, Aroma File Manager support, theme changer...
Availability and Compatibility
Supported TWRP versions: 3.0.X0.
Supported screen resolutions: 1080x1920 (Note 3).
The theme stays compatible with new versions of TWRP until TWRP changelog says otherwise.
DOWNLOAD:
TWRP 3.0.2.0 (N900)
TWRP Themes and Splashes
SCREENSHOTS
Don't get confused as Recovery version in Screenshots is 2.8.0.0. This is because these themes are also available for other version of TWRP here.
SPECIAL THANKS
@z31s1g for all of his Work.
@TWRP for their Recovery.
@halaszk88 for all of his Work.
@Phil3759 for Philz Recovery
@xiaolu
INFO
Original Thread
Code:
What's new in 3.0.2-0:
Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
Add Greek translation to some builds.
PhilZ Recovery
PhilZ Touch 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.
It also adds a full touch interface a completely configurable GUI.
Download
PhilZ 6..4.7 (N900)
CWM Recovery
ClockworkMod Recovery (CWM) is a replacement recovery option for Android devices, made by Koushik "Koush" Dutta. It is based on the Android 2.1 (Eclair) recovery image (updated to Kitkat and Lollipop). Features include Nandroid backup, adb shell, advanced update.zip options (ignore asserts and signature checks), and file browser for choosing update.zips
Download
CWM 6.0.5.0 (N900)
CWM 6.0.7.0 (N900)
How to
Install Recovery:
Simply flash the .tar file by odin.
OR
Extract the recovery.img file from .tar file and flash it using Flashify.
Install the theme:
The theme zips are flashible now.
Download the theme of your choice.
Flash it as normal zip in recovery.
Done
Restart to recovery.
Change the theme:
In Materialised settings, select CHANGE THEME.
Select the theme zip you want to use.
Confirm the change.
Remove the theme:
In Materialised settings, select the delete icon on the app bar.
Confirm the removal.
Alternatively, delete the ui.zip from /sdcard/TWRP/theme with a file explorer.
Change the recovery splash screen
In order to change the splash, one must unpack the recovery image, replace the splash and then repack the image.
General prerequisites:
Make sure the splash screen you want to use is in .jpg format and matches your screen resolution (e.g. 1920x1080).
Download a stock TWRP recovery image for your device.
Samsung users have to download .img files or pull them from the .tar files. Repacking .tar files won't work.
Change the splash while in recovery:
Download the AIK Mobile Installer
Flash the AIK zip in recovery.
This will install the required scripts and binaries to \data\local\AIK-mobile.
In Materialised settings, select CHANGE SPLASH.
Select the stock TWRP .img file.
Select the .jpg file you want to use as splash screen.
Set options:
Make Sure
If Automatically install... is unchecked, the repack will only be created and saved to the same folder as the stock TWRP image.
If checked, the repacked recovery will also be installed on your device.
If Include current theme... is checked, the theme in its current state (accent color) will be included in the repack, replacing the stock TWRP ui.
The ui.zip will automatically be deleted from /sdcard/TWRP/theme, as it is no longer required.
Be aware that changing the accent color won't be possible with an integrated theme.
In general, I'd recommend to not include the theme into the repack. By keeping the ui.zip, there's always the stock ui as a fallback option in case there's something wrong with the theme.
Start repacking/flashing with a swipe.
During the process, Repacking in progress... will be shown.
Install image files while in recovery:
The theme currently utilises the Flashify script by @osm0sis to install boot, radio and recovery images.
The script comes with the theme and will automatically be installed to /sdcard/TWRP/flashify if required.
On the Install page, tap on Install Zip.
Select Install Image.
Select the .img file you want to flash.
Select the image type.
This selection determines the target partition. Make sure not to flash a radio.img to the boot partition...
Start flashing with a swipe.
Use the AROMA File Manager:
AROMA File Manager is not part of the theme.
The theme just contains a "shortcut" for directly starting AROMA FM, rather than going through the "install > flash zip" procedure.
Download this Flashable zip.
Flash the zip in recovery.
This will copy the Aroma FM package to \TWRP\aromafm.
In Materialised settings, tick the option to use Aroma FM.
From the main menu, the theme will now start Aroma FM instead of the TWRP file manager.
Resolve common issues
When I reboot to recovery, the theme isn't applied. Any ideas?
This is most likeley due to wrong naming of the theme folder or the ui.zip.
Make sure the folder is named "theme", without capital letters.
Also check if you accidentally renamed the downloaded zip to "ui.zip.zip" (common pitfall when renaming the zip in windows explorer).
When I reboot to recovery, I get a "recovery bootloop". Is my phone broken?
Nope, this is most likeley due to a bad download.
Please download the theme again using another browser or app.
reserved #2
Wow thanks men!
very nice thanks:good:
Thanks you it looks awsome.
thank you very much!!
Update
philz and CWM recovery added
uzairabdulmajeed said:
PhilZ Recovery
PhilZ Touch 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.
It also adds a full touch interface a completely configurable GUI.
Download
PhilZ 6..4.7 (N900)
How to
Install Recovery:
Simply flash the .tar file by odin.
OR
Extract the recovery.img file from .tar file and flash it using Flashify.
CWM Recovery
ClockworkMod Recovery (CWM) is a replacement recovery option for Android devices, made by Koushik "Koush" Dutta. It is based on the Android 2.1 (Eclair) recovery image (updated to Kitkat and Lollipop). Features include Nandroid backup, adb shell, advanced update.zip options (ignore asserts and signature checks), and file browser for choosing update.zips
Download
CWM 6.0.5.0 (N900)
How to
Install Recovery:
Simply flash the .tar file by odin.
OR
Extract the recovery.img file from .tar file and flash it using Flashify.
SPECIAL THANKS
@halaszk88 for all of his Work.
@Phil3759 for Philz Recovery
Click to expand...
Click to collapse
Are these updated versions of philz recovery and cwm ?
djmax81 said:
Are these updated versions of philz recovery and cwm ?
Click to expand...
Click to collapse
no
cwm is 6.0.5.0
philz is 6.47.7
do you think will we get philz 6.59 update ever?
uzairabdulmajeed said:
no
cwm is 6.0.5.0
philz is 6.47.7
do you think will we get philz 6.59 update ever?
Click to expand...
Click to collapse
Alright.!!! Thanx but its very hard to say about philz recovery new update as project was started by Halaszk88 as he busy with new devise n backed off from n900 sadly . But lets if ican do in free time will have a look at his source .
djmax81 said:
Alright.!!! Thanx but its very hard to say about philz recovery new update as project was started by Halaszk88 as he busy with new devise n backed off from n900 sadly . But lets if ican do in free time will have a look at his source .
Click to expand...
Click to collapse
Thnx for your support for our device
Surely N900 is not dead until men like you and dr.ketan are here.
Sent from my SM-N900 using Tapatalk
INFO
djmax81 said:
Are these updated versions of philz recovery and cwm ?
Click to expand...
Click to collapse
CWM updated to 6.0.7.0
my twrp looks so perfect with the play theme :laugh::laugh::laugh:
Will the CWM 6.0.7.0 work on 5.0 stock rom ??
uzairabdulmajeed said:
Thnx for your support for our device
Surely N900 is not dead until men like you and dr.ketan are here.
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
HEY BRO, RECOVERY TWRP IT HAS COMPATIBILITY WHITH SM-N900W8, THANXS :fingers-crossed:
Is it possible to flash it as an update without the need for odin ?
Sorry if its the wrong thread but where can i find the twrp recovery for sm n900L ?
please help me - i keep flashing TWRP but every time i load the recovery i see the stock recovery
im on lollipop stock rom
munirshah77 said:
Sorry if its the wrong thread but where can i find the twrp recovery for sm n900L ?
Click to expand...
Click to collapse
same question here, is there any custom recovery that will work for SM-N900L version of Note3?
thank you
Introduction
{
"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 for Xiaomi Mi4i. 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
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
You can install it either from MultiROM Manager app or from this guide:
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM - download the ZIP file from second post and flash it in recovery.
Modified recovery - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Thanks a lot to Tasssadar for creating this awesome utility.
XDA:DevDB Information
MultiROM for Mi4i, Tool/Utility for the Xiaomi Mi 4i
Contributors
haikalizz
Source Code: https://github.com/webhaikal/android_device_xiaomi_ferrari-twrp
Version Information
Status: Alpha
Created 2015-12-11
Last Updated 2017-06-07
Reserved
Downloads
MultiROM : https://transfer.sh/Lz0kx/multirom-ferrari.zip
Modified Recovery : https://transfer.sh/fILcp/recovery-mr-ferrari.img
MultiROM Uninstaller : Coming Soon
Supported Kernels
This kexec-less multirom
Reserved
FAQ and other notes
About securityIn order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
What do the ROMs share?All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
Where can I find files from other ROMs?http://forum.xda-developers.com/mi-4i/general/index-xiaomi-mi4i-roms-kernels-toolkits-t3187438
Can I have different versions of Android working alongside? How to use Lollipop and Marshmallow at the same time?Yes. The systems are separated.
The menu with all the ROMs won't show up during boot, how to fix it?Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
The boot animation shows after a few seconds on primary ROMs, why?Because the framebuffer gets blanked for a few seconds after it gets closed by MultiROM.
Can I use MultiROM without root?Yes, if you don't use MultiROM Manager app but flash everything manually
Will I get OTAs when I have MultiROM installed? Do I lose secondary ROMs after an OTA?Probably not, you will have to install them manually and you'll have to reinstall MultiROM
No, you won't lose secondary ROMs
My secondary ROM doesn't boot, what should I do?Probably you forgot to inject current boot sector once, MultiROM didn't run, so /data SELinux context is set to secondary ROMs that are in /data/media so secondary /system has /data contexts.
Go into recovery Advanced > MultiROM > List ROMs > Choose the non booting ROM > Run restorecon
This will fix SELinux contexts and the ROM will boot again
Will this work for cm13 and MIUI 7 as they have different partition tables.
sykomaniac said:
Will this work for cm13 and MIUI 7 as they have different partition tables.
Click to expand...
Click to collapse
Haven't tested with Miui but CM and CM works...
hello friends which is the best rom with reduce heating issue and best battery back up?
jai25993 said:
hello friends which is the best rom with reduce heating issue and best battery back up?
Click to expand...
Click to collapse
Wrong thread Ask this question in Q&A thread please.
jai25993 said:
hello friends which is the best rom with reduce heating issue and best battery back up?
Click to expand...
Click to collapse
@jai25993: Please, don't spam the thread, your question have no any relation with this thread, you should ask this in Xiaomi MI 4i Q&A section.
I am a person who always prefered multi boot on computer, and who like to play with OS's. At this moment, I have four GNU/Linux distros, one Windows and one Android x86 installed on my laptop hdd, and can't belive that finaly can try similar things on my phone.
Thanks to dev(s), and God bless you
EDIT:
haikalizz said:
You can install it either from MultiROM Manager app or from this guide:
Click to expand...
Click to collapse
I installed MultiROM Manager app, and app said "ferrari is not suported":
Is it safe to try manually, is somebody try allready?
Awesome ! Great job !! waiting for report of Miui / Polska / Pro + CM rom combination..
stiw47 said:
EDIT
I installed MultiROM Manager app, and app said "ferrari is not suported":
Is it safe to try manually, is somebody try allready?
Click to expand...
Click to collapse
It's safe though, the app still hasn't recognised our phone yet..
I uploaded a new recovery image. Old one wasn't built with multirom... My mistake, sorry.
stiw47 said:
@jai25993: Please, don't spam the thread, your question have no any relation with this thread, you should ask this in Xiaomi MI 4i Q&A section.
I am a person who always prefered multi boot on computer, and who like to play with OS's. At this moment, I have four GNU/Linux distros, one Windows and one Android x86 installed on my laptop hdd, and can't belive that finaly can try similar things on my phone.
Thanks to dev(s), and God bless you
EDIT:
I installed MultiROM Manager app, and app said "ferrari is not suported":
Is it safe to try manually, is somebody try allready?
Click to expand...
Click to collapse
sorry dear i will be careful in next time
Push to github and link them ! Good job
haikalizz said:
I uploaded a new recovery image. Old one wasn't built with multirom... My mistake, sorry.
Click to expand...
Click to collapse
I didn't try first uploaded (wrong) recovery image, but I think that new one, aka second uploaded, is not good. I was try to flash several times, either via Flashify, Rashr or fastboot, I downloaded again, and flash again via all above tools, everytime flash is succesful, and every time i got only black MI splash screen, when I try to boot to recovery (no recovery screen). If I execute "adb devices" in that moment, I got recognized device with number (List of devices attached *some number* recovery), and yes, it says is in recovery, but no recovery screen on phone.
Did you try your method? Is it working with you?
I am on Ressurection Remix if that is meather (I think no), and using TWRP Mi4i by magdag.
P.S. Can you be more specific in which order we should install a files? I think:
1. MultiROM .zip
2. Modified recovery
3. Sensei kernel
4. Second ROM
Am I wrong?
stiw47 said:
I didn't try first uploaded (wrong) recovery image, but I think that new one, aka second uploaded, is not good. I was try to flash several times, either via Flashify, Rashr or fastboot, I downloaded again, and flash again via all above tools, everytime flash is succesful, and every time i got only black MI splash screen, when I try to boot to recovery (no recovery screen). If I execute "adb devices" in that moment, I got recognized device with number (List of devices attached *some number* recovery), and yes, it says is in recovery, but no recovery screen on phone.
Did you try your method? Is it working with you?
I am on Ressurection Remix if that is meather (I think no), and using TWRP Mi4i by magdag.
P.S. Can you be more specific in which order we should install a files? I think:
1. MultiROM .zip
2. Modified recovery
3. Sensei kernel
4. Second ROM
Am I wrong?
Click to expand...
Click to collapse
You're right on the order. About the recovery, both versions didn't have UI... I'm guessing some ui scripts didn't compiled... Need to check.
haikalizz said:
You're right on the order. About the recovery, both versions didn't have UI... I'm guessing some ui scripts didn't compiled... Need to check.
Click to expand...
Click to collapse
So what now? Can we use this recovery without ui on some way via adb/terminal (or some other way, I don't know), or we should waiting for ui fix?
Don't know how to use it without the ui though, no harm trying. I've pm'ed the multirom dev for any info on this...
Account removal
Deleted
Is it whole this method usable at this moment. How? (without gui in recovery)?
I may have found an error in the TWRP compiled for multirom... Can't get a logcat to actually ensure it but compiling TWRP from omnirom works just it doesn't have the multirom features
{
"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?
Read the update post if you are updating(click here to go there)
{
"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"
}
What is MultiRom?
MultiROM is one-of-a-kind multi-boot mod. It can boot any Android Rom as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. Roms are installed and managed via the modified TWRP recovery. You can use standard ZIP files to install secondary Android Roms, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Warning!
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is possible that something goes wrong and you will have to re-flash yours current Rom zips again. Make backups. Always!
Features:
MultiBoot any number of Android Roms
Restore Nandroid Backup as secondary ROM
Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
Boot from USB drive Attached via OTG cable (untested)
Compatibility
Theoretically any ROM can be used as primary or secondary, but I only test the bellow scenario:
Nougat Custom ROM Primary and secondary OK
Marshmallow Stock secondary OK
All the other possibilities of ROM are untested, also important encryption wasn't tested yet.
Installation instruction:
Via The MultiRom Manager App:
This is the easiest way to install everything MultiROM needs... Just follow the Below Instructions:
Install the app (MultiROMMgr_Quark_xx.apk) From Download folder
Select MultiROM and Recovery on the Install/Update card.
Press "Install" on the Install/Update card to start the installation.
Done.
You current rom WILL NOT be erased by the installation.
Manually via TWRP
Download the files
Install the Multi_ROM TWRP just like normal TWRP, check norma TWRP installation instructions in case of doubt
Flash MultiROM.zip in the primary ROM
Reboot to recovery and start using it
On secondary if Custom ROM and you have bootloop problem flash the Quark_Multi_ROM_FIX_CustomROM_V_1_0.zip to the secondary ROM
Download Folder Click here
Files description:
MultiROMMgr_APP_Quark_xx.apk MultiROM manager app adapt for Quark
multirom_twrp-X.X.X-mod_X-quark.img Normal TWRP image, but with a TWRP adapted for multiROM
multirom-XXXXXXX-vXX-quark.zip flashable zip of multiROM boot manager interface
multirom_uninstaller.zip flashable zip to remove multiROM boot manager interface and cleanup any secondary ROM
Quark_Multi_ROM_FIX_CustomROM_V_1_0.zip flashable zip, if using latest version of my kernel or Nougat ROM released by bhb27 no need to flash this but if you not, this is temp fix for any custom ROM running old version of my kernel or not as a secondary ROM, eventually this won't be need but to day it is, need to re-flash this in case of a kernel change.
XXXX are related to version and dates
Credits:
Tasssadar -Developer of MultiRom
nkk71 - For his No-KEXEC workaround that allow multi_boot to work without complicated kernel modifications
TWRP and MultiROM source click here and read the README.md
App source click here
Developer donation link:
To donate via paypal click here
No other donation option is available.
Help and etc:
Adding ROMs:
Android
Boot into MultiRom Recovery -> select MultiRom (top right corner menu) -> Add Rom -> Select the Rom's zip file or backup and click Confirm.
Switching ROMs (primary to secondary and vice versa):
To make the boot process faster I recomende to disable boot manager interface from showing on every time the device boot's and enable the "keypress-based boot", to enable it go to TWRP top right corner (Multirom menu on TWRP) > Settings > Auto boot > mark "keypress-based boot" and if you wanna to go to "boot manager interface" durring boot after the device vibrate press and hold volume up
Now to switch ROM the "boot manager interface" can be used just go there and click over the ROM you wanna to boot.
Or use the MultiROM manager app
On the app just open it slid left to right or click on left corner to open the tab menu > Manage ROMs > Click on the ROM > click BOOT
Warning!
Very importante always go back to primary ROM from a secondary before going to another secondary this is to prevent the boot.img of primary be override with the secondary and cause boot problems, in case that happens is always possible to restore a boot.img of primary using TWRP backup or flashing a boot.img that can be found on the ROM.zip of your current ROM
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 unless you wipe internal memory or format Data)
* 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 the Rom, follow these steps:
* Go to MultiRom -> List Roms and select the Rom you want to update.
* Select "Flash zip" and Flash the Rom's zip File.
Explanation of recovery menus:
Main menu
- Add Rom - Add Rom to Boot
- List Roms - List Installed Roms and Manage Them
- Inject boot.img File - When you Update something, for example a Kernel or a ROM, which is Distributed as a Whole boot.img (eg. ROM update zip), you have to use this option on it, otherwise you would lose MultiRom.
- Inject curr. boot sector - Use this option if MultiRom does not show up on boot, for example after Kernel Installation.
- Settings - Well, SETTINGS!
Manage Rom
- Rename, Delete - No Need to Explain this I Think!
- Flash Zip (Only Android Roms) - Flash zip to the Rom, for example GAPPS
- Add/Replace boot.img - Replaces boot.img used by this Rom, this is more like a Developer Option.
In case of a problem related to this project use @bhb27 on a post on this thread.
If anyone test different combinations of primary+secondary and or encryption let me know on the thread.
When we think our phone is going to die... BAM!
THANK YOU!
@bhb27
Your skills will never cease to amaze me my friend, great work!! Now I want to buy another Quark :good:
Wow! Sounds really good. Great job @bhb27
@bhb27 I installed the installation instruction but i think i may have now 2 Nougats. I made a backup of my current system. Installed the multiROM.zip file and then went to add ROM and installed my backup on internal memory. When i rebooted it did the 5 second countdown and i saw boot options internal and my backup. i though nothing of it until it finished booting and it was a barebone Nougat install.
On initial install is the multirom.zip going to be our base zip so i need to do a clean install and TiBU all my apps on to that, and then if i wish, install a second ROM. or can i install my backup on that base internal ROM which is currently a blank Nougat RR? Or did i choose wrong option when installing my backup?
johnbravado said:
@bhb27 I installed the installation instruction but i think i may have now 2 Nougats. I made a backup of my current system. Installed the multiROM.zip file and then went to add ROM and installed my backup on internal memory. When i rebooted it did the 5 second countdown and i saw boot options internal and my backup. i though nothing of it until it finished booting and it was a barebone Nougat install.
On initial install is the multirom.zip going to be our base zip so i need to do a clean install and TiBU all my apps on to that, and then if i wish, install a second ROM. or can i install my backup on that base internal ROM which is currently a blank Nougat RR? Or did i choose wrong option when installing my backup?
Click to expand...
Click to collapse
the multirom.zp doesn't change yours current ROM you did something that cause that, it is just the boot manager support.
on main twrp menu you manage yours primary ROM, on MultiROM menu the extra secondary, you can restore yours backup via normal twrp menu and all must be fine, inject the multiRom boot after restore before reboot.
I push the manager app to download folder, it allow in android changes, direct boot, etc...
when open the app it will point out that the TWRP is out of date, I push a new twrp that is the same as the previously but this "new" one has a version tag that can be see in twrp and by the app that version tag will help with future updates via app.
:good:
This is nice. Kinda like having safestrap again from the Moto Droid Maxx I had before the turbo.
bhb27 said:
I push the manager app to download folder, it allow in android changes, direct boot, etc...
when open the app it will point out that the TWRP is out of date, I push a new twrp that is the same as the previously but this "new" one has a version tag that can be see in twrp and by the app that version tag will help with future updates via app.
:good:
Click to expand...
Click to collapse
:good:
Seven android nougat!!
Links to all those?
Bumpn gums from my vzw DROID Turbo xt1254
---------- Post added at 04:14 AM ---------- Previous post was at 04:13 AM ----------
Which is best? RR I'm sure haha
Bumpn gums from my vzw DROID Turbo xt1254
@bhb27 this is fantastic !! Thanks !!
Never tried custom ROM as using quark as daily driver. This will allow me to try and test Roms.
Which partitions to backup before trying this ?
RSDamasceno said:
:good:
Seven android nougat!!
Click to expand...
Click to collapse
gangrenius said:
Links to all those?
Click to expand...
Click to collapse
I'm sure you are joking? You know they are all the Development section of this forum. Well, except for AOKP, which is over in the Development section of the split "Droid Turbo" forum.
But if you really are serious, then it's always a good idea to keep an eye on this thread:
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
That link is to the most recent post.
Rarely I speak before thinking and this was an occasion
Bumpn gums from my vzw DROID Turbo xt1254
z4ck1n said:
@bhb27 this is fantastic !! Thanks !!
Never tried custom ROM as using quark as daily driver. This will allow me to try and test Roms.
Which partitions to backup before trying this ?
Click to expand...
Click to collapse
system and boot, for ROM only.
system, boot and data if you wanna keep apps and they data...
if you test stock ROM as primary let me know the result.
Fantastic work
It's really great to see that devs are still working on quark. I'm also very excited to see Multi ROM for our device. It would be even more great if someone ports any Linux based OS to our device...
there is no need to flash Quark_Multi_ROM_FIX_CustomROM_V_1_0.zip to a secondary ROM if you have update your secondary to the latest version of the ROM or the kernel that I released...
It worked very well on my Maxx :good:
Thank you!
Is it possible to include the queue function for the secondary ROMs?
bhb27 said:
system and boot, for ROM only.
system, boot and data if you wanna keep apps and they data...
if you test stock ROM as primary let me know the result.
Click to expand...
Click to collapse
I don't want to mess with primary rom (current stock mm). Want to install this over it, without losing data.
My Data is to big to be backup ...
Few Questions
How does multirom work? Does it change boot sector record like normal desktop oses?
In multirom installation which partitions are impacted?
Where is secondary rom installed?