Related
hi, i wanna ask...if i wanna flash to another devoid.Franco ROM (previously using void.echo) do i still need to dl the Terminal Emulator & Custom Recovery Tool Image and its Flash Image then run the Terminal Emulator & key in the codes then only start flashing another ROM?
i've did tat at the first time i flashed to a void.echo ROM now i wanted to flash to devoid.franco, do i still need to repeat all that step again? or i just enter the "power button, volume down button and home button" mode then wipe then flash will be good?..need advice thanks..
Just wipe and flash..
thanks for quick reply!
another question...how do i know that i already have the ext partition?...after i wipe everything included wipe ext..do i still need to create again?
Wiping doesn't remove partition..
On Mike mod
can we install franco kernel on mike mod 6.5.2
If your from void#echo previously, do these:
1. Backup all your user apps+contacts via Titanium Backup and all SMS via SMS backup
(they're all available free in the market)
2. Turn off phone. Reboot to recovery (hold power button+home+vol down)
3. Wipe user data, .android secure, cache, dalvik-cache, battery stats, and wipe ext.
4. Since your on void#echo already, you don't need to partition your sdcard.
5. Download devoid.franco, use usb-toggle on the recovery menu and copy it from pc to your phone while on the recovery and flash it.
6. Reboot (first boot might take a while)
7. Configure settings, Install titanium backup and sms restore app, Then restore all apps+settings+SMS. Enjoy~
8. Well if you know already what your doing and want some further improvements (completely optional, just do a nandroid backup incase) :
8.1 Reboot to recovery
8.2 Flash the latest kernel version from franco's thread
8.3 Reboot
8.4 Flash the ZRAM module
8.5 Reboot and Enjoy your phone
Thanks Kira.Lawliet!
hmm...i actually partition my sdcard again...yea..i flash before saw your reply ._.
will it harm? i partition my sdcard again....n flash to devoid.franco
You have to partition only if you want apps2sd. Else let it be. You can easily remove the ext partition by partitioning with 0mb ext partition in recovery.
sanmore said:
can we install franco kernel on mike mod 6.5.2
Click to expand...
Click to collapse
definitely you can. just flash your device with mik_os mod first. then flash the franco kernel (v15 now) and lastly flash the ZRAM initializer.
just make sure you wipe the cache and dalvik cache first before you're flashing.
flashing
Ok guys just remember that rom flashing requires you to follow rom partition conditions while kernel flashing may not need to recreate partitions. In my case, I'm using Nessy Hypnos2 and been running with much fluidity after flashing FrancoKernel 14.2. But I did wipe all just to make sure there wont be any conflicts. HYPNOS2 + FRANCOKERNEL 14.2 is like coffee and cream, a perfect match like newlyweds.
This script doesn't include the wipes (data, cache and dalvik), only the formats.
What does that mean?, That if you use the formats, that also include wipes?
Or put another way, if I use this script is not necessary to manually wipes because those are included in the formats?
Then, which is the difference into wipe and format?
Thanks
Formats wipe all your data in selected patrition.
You must flash new rom after that.
Manolit said:
This script doesn't include the wipes (data, cache and dalvik), only the formats.
What does that mean?, That if you use the formats, that also include wipes?
Or put another way, if I use this script is not necessary to manually wipes because those are included in the formats?
Then, which is the difference into wipe and format?
Thanks
Click to expand...
Click to collapse
It is not necessary to manually wipe after you use the script. If you are about to do a new rom install, these are the steps that you need to do:
When you are at a stage whereby you want to flash a new ROM and want to do a FULL WIPE before doing so (which I would ALWAYS recommend) the steps are as follows:
1. Reboot into CWM Recovery
2. Install zip from SD card>Run GS2ROMWipe or GS2ROMNuke
3. Install zip from SD card>Flash your new ROM
4. Reboot
Click to expand...
Click to collapse
Of course, if the installation instructions for the rom itself require you to do some more steps, you do those at point 4 instead of rebooting, and then reboot.
Btw, if you want to exactly know what is going on when you run the script, here's what the dev wrote about the script himself:
GS2ROMWipe
This wipes pre-defined areas of your device without performing any backups beforehand.
Does the following:
1. Runs GS2KernelWipe:
....a) Saves all current startup scripts to /sdcard/MyBackups. To change this location, see Changing the Backup Location below.
....b) Removes Voltage Control and NSTools startup scripts (only if saved as init.d, and not as a service) along with many other kernel-specific startup scripts from /system/etc/init.d
....c) Removes ExTweaks, STweaks, Voltage Control, NSTools and SetCPU dalvik-cache areas.
....d) Removes old kernel-specific files (currently Siyah, DorimanX, PhilZ, Jeboo, Void, Andoidmeda, NEAK and Abyss are cleared)
....e) Removes /data/user.log
2. Formats /system
3. Formats /cache
4. Formats /data
5. Clears /sdcard/LOST.DIR
6. Clears /sdcard/.android_secure
7. Clears /preload
8. Clears Specific ROM folders off SD Card for Neat ROM and Alliance ROM:
....a) /sdcard/SaleTweaks
....b) /sdcard/Alliance
....c) /sdcard/alliance-tweak
....d) /sdcard/com.ficeto.darkyromota
9. Clears pre-defined files/folders of your own choosing (see Extra user-defined files/folders for removal below)
10. Runs GS2MediaWipe to clear all known cache and temporary files relating to Media to aid media scanning process on your new ROM.
Click to expand...
Click to collapse
You can find more info in the original thread here.
How to switch recoveries
Index
1. Benefits of BMM and SS
2. Switch from SS to BMM
2.1 Basic usage of BMM
3. Switch from BMM to SS
This little guide is a work in progress! Within the next time I will insert pictures, detailed explanations about several features, etc. For now it's only a quick switching guide for SS users or beginners.
Who wants to know everything?
Whirleyes, the creator of BMM provided a great virtual BMM on his website! It works like you had a working BMM on your computer, you can browse through the menus and get detailed explanations. A user tutorial is also available which explains everything!
Find it here: http://www.projectlense.com/BootMenuManager/Tutorial/
Any help is welcome to extend this guide. Otherwise give me some time to finish it. Thx!
1. Benefits of BMM and SS
BMM:
BMM is a full featured recovery system and is recommended for developers or advanced users. While a high featured recovery is nice for developers it can be a big disadvantage for normal users. If you don't know how to handle BMM you can brick your device very fast! But besides of that there are many benefits, such like the possibitlity to flash roms to the stock or 2nd system (webtop partition) - which aren't virtual systems. A generic partition provides better performance and it could affect the behavior of some tweaks too. For me it provided also better battery life.
The system Keeper can be used to install root to your selected system, unroot or also install BMM after flashing to the stock system - after flashing to stock system BMM will install itself autmatically! So it protects you from loosing BMM.
An additional feature is the compatibility to Safestrap! You can boot your Safestrap Slots with BMM, or restore nandroid backups from SS to one of your BMM systems. I'm not sure if this works with SS vice versa.
Based on CWM 6 Touch
Multiple Boot (Select any system on startup)
Boot modes (Kexec, 2nd-init, Insecure adb)
6 Rom Slots (2 generic, 4 virtual img-slots)
Backup (Fast, Full, Selective)
Restore (Fast, Full, Selective)
Wipe (Data, Cache, Dalvik Cache, Battery stats)
System Keeper (Backup, Install, Uninstall Root, Install BMM)
Mount (Format ANY partition, mount partitions - e.g. for use with Filemanager)
Stock System flashable
2. System uses the Webtop partition (which is unused since Moto ICS! That means there are 1,3gb of unused space! BMM uses the webtop partition for userdata. Only disadvantage is: Userdata size is limited at 1.3gb)
Virtual Slots (Create partition images with preferred sizes)
Custom Install-Binary allowed on all slots (e.g. usefull for updater-script commands using Busybox, Aroma Installer, etc)
File Manager (Aroma Filemanager, Root)
ADB
No Rom-side hardcoded slots! Roms will work on every slot!)
Firmware Flashing Section (Stock ONLY:
- Backup Kernel
- Restore Kernel
- Flash Kernel
- Flash Baseband (Radio.img, bp.img, lte.img)
- Backup CID
- Erase CID
- Restore CID
Safestrap:
The main intention of Safestrap is to be SAFE for users. The stock rom system will stay untouched so you cannot brick your device. But the use of virtual slots isn't always an advantage. Roms running on virtual slots can cause lower performance. For normal users who just want to play around or test a new rom SS is the best choice. For users who want to try their own developed stuff or just take the best out of their devices, the best choice is BMM.
Based on TWRP Touch
Fixed Dual Boot (select a slot in recovery as default boot)
Boot modes (Kexec, normal)
Backup (Full, Selective)
Restore (Full, Selective)
Wipe (Data, Cache, Davlik Cache)
Mount (mount partitions - e.g. for use with Filemanager)
5 Rom Slots (Stock + Only virtual img-slots)
Slots for Kexec Roms are hardcoded!!
Virtual Slots (Create partition images with preferred sizes)
File Manager (TWRP)
ADB (?)
Click to expand...
Click to collapse
2. Switch from SS to BMM
I will only describe the process for installation and the basic usage of BMM. Advanced users might know of find our how to handle additional features - otherwise you can still ask here.
If needed make a full backup of your slot and place the backup somewhere on your computer or wherever it's safe.
Boot into your stock rom
Open the Safestrap app
Hit "Uninstall recovery" and wait for the process to be finished
Open Play Store and search for "Bootmenu Manager" (Make sure it's the version 0.3.4!)
Download and install it
Open the new app and allow su rights
In the appearing menu hit "Install" and finish the process
When done, BMM is installed
2.1 Basic usage of BMM
I will describe the step by step process to install a rom.
But Whirleyes postet on his website an awesome "virtual Bootmenu" where you can brwose through the full menus! It's great, so you can get in touch with it and see how it looks like! You can find it here:
Virtual Bootmenu Website
Reboot
Wait until the BMM splash screen appears, touch the screen and select "Settings"
Now select a system you want to prepare (for rom installation)
- System 1 is your Stock System
- System 2 has limited userdata (max 1.3gb)
- System 3-6 are virtual slots, similar to Safestrap
For System 2 you will only have to prepare the Cache partition. This can be done by hitting the "ACTIVATE" button in System 1 settings
For System 3-6 you have to create the partition images - similar to Safestrap - just pick your preferred sizes.
After preparing your system, you can go back by pressing the "Back" hardbutton until you see the splashscreen again
Now enter "Recovery"
You will see several options (similar to CWM)
First you need to switch to your prepared system
Tick "Switch System" and select that system you've just prepared. You will notice that the color of the buttons has been changed (Each system has its own color!)
Now are able to flash a rom
Select "Install zip from sdcard"
If needed "change the zip location" to int/ext storage
Navigate to your rom zip, select it and confirm
Repeat the last 3 steps for Gapps or whatever you want to flash
When done, enter the "reboot options" in the main menu
You can select whether to reboot as usual, reboot directly into your preferred system, reboot into bootloader or stock recovery)
Otherwise just perform a normal reboot and select your system at the splashscreen
That's it!
3. Switch from BMM to SS
I will only explain how to uninstall BMM safely and install SS!
Boot into System 1
If needed make a full backup of your slot and place the backup somewhere on your computer or wherever it's safe.
Open the BMM app
Select "Installer"
Select "Uninstall"
When the process has finished BMM is removed
Make sure you have the Safestrapxx.apk on your sdcard
Open it and select "Install recovery"
That's it.
CREDITS
*Thanks Whirleyes, the creator of BMM, for the great work!
*Thanks Hashcode, the creator of SS, for his awesome work!
Great initiative!
It would be nice to add for BMM users
system 2, in order to be used, it has to be activated first:
when device boot, do not press recovery, but settings, system 2 and activate
for flashing kernels, there must be NO SPACE into the path like
firmware/kernel.EU.JB/boot.img
heblu said:
Great initiative!
It would be nice to add for BMM users
system 2, in order to be used, it has to be activated first:
when device boot, do not press recovery, but settings, system 2 and activate
for flashing kernels, there must be NO SPACE into the path like
firmware/kernel.EU.JB/boot.img
Click to expand...
Click to collapse
The system 2 thing ias already there - but for all systems.
Safestrap only has 5 slots (stock + 4 virtual) you might also want to note that safestrap kexec requires specific slots.
How do I restore a ss backup?
Sent from my DROID RAZR using Tapatalk 4 Beta
---------- Post added at 06:53 PM ---------- Previous post was at 06:51 PM ----------
I am now on bmm and I would like to restore my cm10.1 backup with out losing my files thanks
Sent from my DROID RAZR using Tapatalk 4 Beta
Copy the backup folder into /sdcard(-ext)/clockworkmod/backup/ and try to select it in bmm.
OP updated! Now added the full virtual bmm tour! Watch out!
M.o.t.o.r.o.l.a.R.a.z.r - JBX-Kernel 0.5x - Tapatalk4
OK this is a good explanation
until now convinced me 60% to move from SS to BMM
I will read more and I will see .......
thanks for the tutorial
File manager?
All,
I have recently made the jump to BMM. I am enjoying using it once I had it figured out..kind of. I am up and running with stock/2nd slot and a third vurtual. How do you get the file manager working once in BMM? It gives an error saying aromafm is not installed? Is this an additional add on? If so how do you install it so it works in BMM? TIA
twith70
twith70 said:
All,
I have recently made the jump to BMM. I am enjoying using it once I had it figured out..kind of. I am up and running with stock/2nd slot and a third vurtual. How do you get the file manager working once in BMM? It gives an error saying aromafm is not installed? Is this an additional add on? If so how do you install it so it works in BMM? TIA
twith70
Click to expand...
Click to collapse
YOu have to pick the Aromafm.zip from the internet. Just search for Aroma File Manager and store the zip in /sdcard(-ext)/clockworkmod/
dtrail1 said:
YOu have to pick the Aromafm.zip from the internet. Just search for Aroma File Manager and store the zip in /sdcard(-ext)/clockworkmod/
Click to expand...
Click to collapse
Do I have to change the name or permissions of that file? It shows aromafm.zip.cfg? TIA
twith70 said:
Do I have to change the name or permissions of that file? It shows aromafm.zip.cfg? TIA
Click to expand...
Click to collapse
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1646108
Rename the zip to aromafm.zip. That's it.
Great guide!
I'm using SS only have two questions:
What if I messed up my stock rom and can't boot into it? Is there any way to install BMM (beside flashing my phone to stock rom via RSD)?
I have never used BMM and probably won't switch... but I thank you kindly for your time and work on this guide...
Sent from my DROID RAZR using xda app-developers app
kamikass said:
Great guide!
I'm using SS only have two questions:
What if I messed up my stock rom and can't boot into it? Is there any way to install BMM (beside flashing my phone to stock rom via RSD)?
Click to expand...
Click to collapse
If you have an accessable recovery installed you can restore your system (resotre nandroid, flash rom, etc). But if you cannot boot into any rom you have to flash using RSD.
dtrail1 said:
If you have an accessable recovery installed you can restore your system (resotre nandroid, flash rom, etc). But if you cannot boot into any rom you have to flash using RSD.
Click to expand...
Click to collapse
Ok, I"m using liquidsmooth on slot 3, but still can't restore my stock rom to stock slot. I messed it up by flashing cm10(JB) accidentally on stock slot, while I had an ICS stock rom installed on it.
What if I don't have a nandroid backup? What rom should I flash to go back to stock ICS on stock slot (XT910, Latam)?
Thanks in advance!
you should know before you flash something... Look inside the firmware super thread.
M.o.t.o.r.o.l.a.R.a.z.r - JBX-Kernel 0.5x - Tapatalk4
also I have been unsuccessful and restoring a backup made from SS...MD5 mismatch error or something. Not a big deal just commenting
chiahead52 said:
also I have been unsuccessful and restoring a backup made from SS...MD5 mismatch error or something. Not a big deal just commenting
Click to expand...
Click to collapse
Have you copied the md5 files too? If yes, try it again without them.
Great job!
Sent using Tapatalk 2
Is there a how to thread for using bmm? I can't find anything recent with step by step instructions. I managed to get a rom flashed, but I'd like a better idea of how to use BMM/Aroma.
My phone are rooted and have recovery but i cant delete system app nor activate xposed installer..seem like it cant mount system or something like that..can someone tell me how to fix it? my phone is on the latest firmware..
Are you on 4.4.4? Do you have supersu installed??
To delete system apps better use titanuim backup
for xposed install it via recovery
4.4.4 has enhanced the security... You are no longer able to write on the system partition unless you disable the security, I don't remember if it is kernel related or if a recovery is enough when flashing a file to disable ric... Search for the "disable ric.zip" file
Preliminary guide to BACKUP / RESTORE with
OrangeFox recovery by ManoloRey
LINK
or
TWRP recovery 3.5.X_10-x by brigudav
LINK
! ! ! USE ONLY LINKED VERSIONS OF RECOVERIES ! ! !
Consider this guide for (decrypted vendor (or encryption disabler) + decrypted storage used) as BETA, I don't recommend backup/restore procedures with OrangeFox recovery Beta or TWRP 3.5.0_10-x for actual backups of your data (TRY THIS ONLY AT YOUR OWN RISK) ONLY FOR TESTING / EDUCATIONAL PURPOSES !
Do not ask for help if your data have been lost because they can't be restored, or suddenly your backup - successfully restored several times before - now can't be! This is still buggy and sometimes for unknown reasons restore of your data can fail ! Restore process always worked 100 % for me, but results sometimes differ !
YOU HAVE BEEN WARNED!
(decrypted vendor (or encryption disabler) + decrypted storage used)
Spoiler: Backup method A (not recommended):
- backup boot and data partition
Restore:
- wipe cache, dalvik, data
- flash ROM + GAPPS that you have installed when you created backup
- restore backup of boot and data partition
- remove Android password (OFOX recovery functionality) restored from backup either directly after restore or later from the menu with OFOX addons (the file PassReset.zip MUST EXIST in this location: /storage/emulated/0/Fox/FoxFiles/ for this to work !) but before reboot!
- in case you lost your OFOX addons thanks to format data or you are using TWRP 3.5.0_10-x, you can also directly delete all file(s) in /data/system which starts with locksettings* = remove password
Reboot
Comment(s):
- if you remove your password/PIN/pattern protection directly before backup you can end up after restore with system where you can't change your password/PIN/pattern anymore
- if you forget to remove your password/PIN/pattern protection AFTER RESTORE you can end up after boot with system demanding to enter your password/PIN/pattern which MAY or MAY NOT BE ACCEPTED even if it is CORRECT and maybe INACCESSIBLE because of that
- Google Pay will never be restored properly (or anything depending on actual password in time of backup), because of the removed password, you will need to set up it again after restore
Spoiler: Backup method B (recommended):
- backup super, boot, dtbo and data partition (metadata partition is optional)
Restore:
- wipe cache, dalvik, data (optional)
- restore super, boot, dtbo and data partition (metadata partition is optional)
Reboot
(everything will be restored to the state in time of the backup) ¹)
- if needed remove Android password (OFOX recovery functionality) restored from backup either directly after restore or later from the menu with OFOX addons (the file PassReset.zip MUST EXIST in this location: /storage/emulated/0/Fox/FoxFiles/ for this to work !)
- in case you lost your OFOX addons thanks to format data or you are using TWRP 3.5.0_10-x, you can also directly delete all file(s) in /data/system which starts with locksettings* = remove password
Comment(s):
¹) your backups will be fully restored along with password/PIN/pattern and fingerprints - this will work until you'll format data (or for something else that needs to be discovered yet), after that you'll loose the ability to use your password to enter the system and depending on ROM features you can either skip password entering with fingerprints (RRemix) or reset your password so you can enter the system (CrDroid), in RRemix everything works, except you can't change your password etc, in CrDroid you need to re-setup your password depending apps
- if you remove your password Google Pay will never be restored properly (or anything depending on actual password in time of backup), you will need to set up it again after restore
x x x(encrypted vendor and storage used)
Spoiler: Backup method A (OFFICIAL for OrangeFox & UNOFFICIAL for TWRP)
Backup:
- backup boot and data partition
Restore:
If you are restoring a data backup of an encrypted device, there are precautions that you should take before starting the restore process (obviously, your backup must be on MicroSD or other external storage medium - NOT on the internal storage):
Format the data partition (NOTE: format - not just wipe)
Reboot OrangeFox / TWRP
Flash the original zip of the ROM whose backup you are trying to restore
Wipe cache and dalvik
Reboot to system to ensure that the newly-flashed ROM actually boots, and that it re-encrypts the device with its own encryption
Reboot to OrangeFox / TWRP
Tap on the Backup icon
Select the partition(s) that you wish to restore
Swipe to restore
If you do not follow all these steps, you can expect problems with restoring data
Reboot
Comment(s): TBA
Credits: OrangeFox devs as this guide (for encrypted vendor and storage used) is copied directly from OrangeFox wiki slightly modified by me by adding "/ TWRP" to the text
this guide will be updated if I discover new facts or post new, updated steps or how-to's
reserved
jeryll said:
reserved
Click to expand...
Click to collapse
Thanks for your experiments and hard work in putting this together!
backup super, boot, dtbo and data partition (metadata partition is optional)
Click to expand...
Click to collapse
there is 2 checkboxes for super with the same size in OF. one says (Product, Vendor, System).
which one to select or both?
drahtwurst said:
there is 2 checkboxes for super with the same size in OF. one says (Product, Vendor, System).
which one to select or both?
Click to expand...
Click to collapse
Only one, backup of super from either is identical
Thanks for this flashlight on the darkness.
Let me ask you a help. How can I decrypt my device? Wanna do it just like my old MI8, where I didnt need to do format data ever when go to update a rom.
Ever I go do recovery (OFOX or TWRP) I got this in screenshot.
- download and flash decrypted (hacked) vendor from this thread or
- use encryption disabler zip, but that is a little tricky to use - you need to flash encryption disabler every time you update your MIUI base, or custom rom, if you forget that, on next boot your internal storage will be encrypted
- - to remove encryption from data partition after - you need to do initial format data (yes) - after that you can start to use wipe data if needed (some ROMs still need to use format data (yes) or they'll not boot - RR 8.6.6/8.6.7 for example)
jeryll said:
- use encryption disabler zip, but that is a little tricky to use - you need to flash encryption disabler every time you update your MIUI base, or custom rom, if you forget that, on next boot your internal storage will be encrypted
Click to expand...
Click to collapse
Yep, that fact just bit me today as I was away from the computer and had to reflash the latest Xiaomi.eu...
jeryll said:
- use encryption disabler zip
Click to expand...
Click to collapse
Are there further instructions for first install? I did google but failed to find anything reliable...
pnin said:
Are there further instructions for first install? I did google but failed to find anything reliable...
Click to expand...
Click to collapse
not that I know of, just flash it as last thing before you reboot (either recovery or to system), but you need to format data (yes) to remove encryption
As this [surya] 'encryption-disabler-v1' is basically a shell script (pasted to https://paste2.org/804aemGx, BTW), I took the risk to flash it without formatting 'Data' -- only I disabled any security beforehand, i.e., no pin, password or fingerprint.
It appears to have worked, cause I rebooted into system with no issues. But how to verify?
not sure what do you want to achieve by flashing of encryption disabler without actually disabling encryption by formatting your data partition...
so what do you want to verify?
if you start OFOX, on the initial screen you can see the state of your data partition (encrypted/decrypted)
Thanks for your patience. I was under the impression that if you disable security locks then you had no encryption and the script would just ensure it would remain so. By your reaction I'm assuming I was wrong...
Overall, I am just getting fed up with always having to format data and having to start from scratch.
I not longer have OFox, I'm currently running brigudav's TWRP "v3.5.0_10-5-surya".
pnin said:
Thanks for your patience. I was under the impression that if you disable security locks then you had no encryption and the script would just ensure it would remain so. By your reaction I'm assuming I was wrong...
Overall, I am just getting fed up with always having to format data and having to start from scratch.
I not longer have OFox, I'm currently running brigudav's TWRP "v3.5.0_10-5-surya".
Click to expand...
Click to collapse
As you said, that encryption_disabler.zip is a shell script, which makes the folder in /product/vendor_overlay/29/etc and copies fstab.qcom from vendor to it. Then edits every line using the shell command sed (aka stream editor) that includes the string fileencryption= with the string encryptable=.
The above described process is usually done on the first boot of a newly installed ROM as is with every vendor_overlay entry in product (minus the edited strings ofc). Editing it after the ROM reads vendor fstab.qcom and encrypts the data partition is useless. However, formatting data (deleting keystore essentially) and flashing that .zip should also do the trick. Might as well update your base MIUI and ROM while you're at it
Thanks for the detailed explanation, Slim K. Sadly there's no escaping formatting data, which I'll do next...
Slim K said:
Might as well update your base MIUI and ROM while you're at it
Click to expand...
Click to collapse
I had done so already, hence my reluctance to do it again.
jeryll said:
Preliminary guide to BACKUP / RESTORE with
OrangeFox recovery by ManoloRey
LINK
or
TWRP recovery 3.5.X_10-x by brigudav
LINK
! ! ! USE ONLY LINKED VERSIONS OF RECOVERIES ! ! !
Consider this guide for (decrypted vendor (or encryption disabler) + decrypted storage used) as BETA, I don't recommend backup/restore procedures with OrangeFox recovery Beta or TWRP 3.5.0_10-x for actual backups of your data (TRY THIS ONLY AT YOUR OWN RISK) ONLY FOR TESTING / EDUCATIONAL PURPOSES !
Do not ask for help if your data have been lost because they can't be restored, or suddenly your backup - successfully restored several times before - now can't be! This is still buggy and sometimes for unknown reasons restore of your data can fail ! Restore process always worked 100 % for me, but results sometimes differ !
YOU HAVE BEEN WARNED!
(decrypted vendor (or encryption disabler) + decrypted storage used)
Spoiler: Backup method A (not recommended):
- backup boot and data partition
Restore:
- wipe cache, dalvik, data
- flash ROM + GAPPS that you have installed when you created backup
- restore backup of boot and data partition
- remove Android password (OFOX recovery functionality) restored from backup either directly after restore or later from the menu with OFOX addons (the file PassReset.zip MUST EXIST in this location: /storage/emulated/0/Fox/FoxFiles/ for this to work !) but before reboot!
- in case you lost your OFOX addons thanks to format data or you are using TWRP 3.5.0_10-x, you can also directly delete all file(s) in /data/system which starts with locksettings* = remove password
Reboot
Comment(s):
- if you remove your password/PIN/pattern protection directly before backup you can end up after restore with system where you can't change your password/PIN/pattern anymore
- if you forget to remove your password/PIN/pattern protection AFTER RESTORE you can end up after boot with system demanding to enter your password/PIN/pattern which MAY or MAY NOT BE ACCEPTED even if it is CORRECT and maybe INACCESSIBLE because of that
- Google Pay will never be restored properly (or anything depending on actual password in time of backup), because of the removed password, you will need to set up it again after restore
Spoiler: Backup method B (recommended):
- backup super, boot, dtbo and data partition (metadata partition is optional)
Restore:
- wipe cache, dalvik, data (optional)
- restore super, boot, dtbo and data partition (metadata partition is optional)
Reboot
(everything will be restored to the state in time of the backup) ¹)
- if needed remove Android password (OFOX recovery functionality) restored from backup either directly after restore or later from the menu with OFOX addons (the file PassReset.zip MUST EXIST in this location: /storage/emulated/0/Fox/FoxFiles/ for this to work !)
- in case you lost your OFOX addons thanks to format data or you are using TWRP 3.5.0_10-x, you can also directly delete all file(s) in /data/system which starts with locksettings* = remove password
Comment(s):
¹) your backups will be fully restored along with password/PIN/pattern and fingerprints - this will work until you'll format data (or for something else that needs to be discovered yet), after that you'll loose the ability to use your password to enter the system and depending on ROM features you can either skip password entering with fingerprints (RRemix) or reset your password so you can enter the system (CrDroid), in RRemix everything works, except you can't change your password etc, in CrDroid you need to re-setup your password depending apps
- if you remove your password Google Pay will never be restored properly (or anything depending on actual password in time of backup), you will need to set up it again after restore
x x x(encrypted vendor and storage used)
Spoiler: Backup method A (OFFICIAL for OrangeFox & UNOFFICIAL for TWRP)
Backup:
- backup boot and data partition
Restore:
If you are restoring a data backup of an encrypted device, there are precautions that you should take before starting the restore process (obviously, your backup must be on MicroSD or other external storage medium - NOT on the internal storage):
Format the data partition (NOTE: format - not just wipe)
Reboot OrangeFox / TWRP
Flash the original zip of the ROM whose backup you are trying to restore
Wipe cache and dalvik
Reboot to system to ensure that the newly-flashed ROM actually boots, and that it re-encrypts the device with its own encryption
Reboot to OrangeFox / TWRP
Tap on the Backup icon
Select the partition(s) that you wish to restore
Swipe to restore
If you do not follow all these steps, you can expect problems with restoring data
Reboot
Comment(s): TBA
Credits: OrangeFox devs as this guide (for encrypted vendor and storage used) is copied directly from OrangeFox wiki slightly modified by me by adding "/ TWRP" to the text
this guide will be updated if I discover new facts or post new, updated steps or how-to's
Click to expand...
Click to collapse
Hello
I tried to do a backup with this orfox version including 'super'. At the end it says:
Backing up Super...
Backup Failed, Cleaning Backup Folder
Do you have a idea what happened?
Edit: I guess it's because my phone is encrypted
XtraWater said:
Hello
I tried to do a backup with this orfox version including 'super'. At the end it says:
Backing up Super...
Backup Failed, Cleaning Backup Folder
Do you have a idea what happened?
Edit: I guess it's because my phone is encrypted
Click to expand...
Click to collapse
Make sure you have enough space on the destination. Have a look at the OF log.
I guess this is as good a place as any to ask: what is the advantage of decrypting data?
I don't think running encrypted slows things down (not like it used to in the past when devices weren't as powerful), and there is the huge benefit of having your data secure. Any lost/stolen phone will soon send up in the hands of someone (on either side of the law) who knows adb/fastboot, so just having a password isn't going to protect your data if it's not encrypted.
It's possible to do backups of encrypted data, just the same as unencrypted.
Formatting vs wiping: ends up doing the same - all the data is gone and has to be restored. So that's a non-issue.
So, why should one prefer to decrypt?
temporarium said:
I guess this is as good a place as any to ask: what is the advantage of decrypting data?
I don't think running encrypted slows things down (not like it used to in the past when devices weren't as powerful), and there is the huge benefit of having your data secure. Any lost/stolen phone will soon send up in the hands of someone (on either side of the law) who knows adb/fastboot, so just having a password isn't going to protect your data if it's not encrypted.
It's possible to do backups of encrypted data, just the same as unencrypted.
Formatting vs wiping: ends up doing the same - all the data is gone and has to be restored. So that's a non-issue.
So, why should one prefer to decrypt?
Click to expand...
Click to collapse
From my understanding the only benefit would be to update firmware without format data.
re backup super: There are about 70GB available on the SD card (destination of the backup). I tried to backup it again with the same result. Just looking at the log file but can't see what has failed. The line before Backup failed is:
I:Error writing destination fd(operation not permitted)
XtraWater said:
From my understanding the only benefit would be to update firmware without format data.
re backup super: There are about 70GB available on the SD card (destination of the backup). I tried to backup it again with the same result. Just looking at the log file but can't see what has failed. The line before Backup failed is:
I:Error writing destination fd(operation not permitted)
Click to expand...
Click to collapse
Your card is probably formatted as fat32 which won't allow such big files.