Related
Schedule Post:
#1 - What Is ClockworkMod Recovery And How To Use It On Android
#2 - Nandroid Backup & Restore
#3 - Onandroid Backup
What Is ClockworkMod Recovery And How To Use It On Android
ClockworkMod – also known as Clockwork or CWM – is a custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery. In what follows, we will cover all that this recovery is capable of doing, and how to do it. We do not discuss about TWRP (TeamWin Recovery Project) in this thread.
1.All About Android Recovery
All Android devices ship with a recovery console that is basically a partition on the device’s internal memory and can be booted into. The stock recovery of almost all Android devices provides a few basic yet handy options that allow you to factory reset your device and also to recover its operating system using an official ROM in zip format, but that’s all you can do with it. That’s where a custom recovery comes handy.
A custom Android recovery basically replaces the stock recovery with one that lets you do all you can do with the stock recovery, plus a plethora of more options to give you a lot more control on your device. With a custom recovery, you can install official and unofficial ROMs as well as other updates including apps, themes, kernels etc. using zip files, wipe not just user data but pretty much every partition on your device, mount the storage card for USB mass storage access without leaving recovery, partition your SD card, wipe Dalvik cache and battery stats, fix permissions, perform, manage and restore backups and so on.
2.Introduction to ClockworkMod
ClockworkMod recovery is one of the most widely used custom Android recoveries that is available for most mainstream Android devices. It is the needed recovery for AOKP, AOSP, CM. ClockworkMod recovery has been developed by Koushik Dutta (also known as Koush) – the same guy who brought us the Android ROM Manager.
3.Booting into ClockworkMod
On most Android devices including ones by Samsung, you can enter recovery by powering your device off and then powering it back on while keeping either the Volume Up+Home+Power buttons pressed in the same time. This will enter the bootloader from where you can select the ‘RECOVERY’ option by navigating to it with the Volume key and entering it with the ‘Power’ key.
Tour
1. reboot system now
Reboot/restart your phone.
2. apply update from sdcard
This can be used for installation of any official or unofficial update, ROM, kernel, theme etc. That is in a zip format installable from recovery, as long as the file is named update.zip and it has been placed on the root of your SD card (i.e. not in any sub-folder). Selecting this option (and most of the options featured below) will bring up a rather annoying confirmation prompt but this has saved us on multiple occasions from a lot of trouble we would have been into due to accidental key presses. This is what we are talking about:
3. wipe data/factory reset
This option wipes all user data on the device as well as cache. Doing this will leave your phone in the state it was in when you bought it or when any custom ROM was first installed. It will also wipe any sd-ext partition that you might have setup (more on this later).
4. wipe cache partition
Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery.
5. install zip from sdcard
This option brings up the following sub-menu:
a. apply /sdcard/update.zip
This one is essentially the same as the ‘apply update from sdcard’ option of the main menu.
b. choose zip from sdcard
Lets you install any zip file (with any name) from any location on your SD card. The file can be for a ROM, a kernel, an application, a theme or any mod as long as it is in recovery-flashable zip format. This is the most widely used option for installing a ROM that you have downloaded and copied to your SD card.
c. toggle signature verification
Turns the signature verification on and off. When signature verification is on, you will not be able to install any custom ROMs that haven’t been signed by the developers (most custom ROMs aren’t signed). Switching it off skips the signature verification check and proceeds with the installation.
d. toggle script asserts
Seldom-used option for a vast majority of users. It simply turns script asserts on or off. If you don’t know about these (we don’t), it’s best not to change this option.
e. +++++Go Back+++++
Takes you back to the main recovery menu, obviously!
6. backup and restore
Undoubtedly one of the most important features provided by a custom recovery, the backup and restore feature – also known as Nandroid backup – allows you to take a snapshot of your phone’s entire internal memory including all partitions, and save it on the SD card.
a. Backup
Takes a Nandroid backup, as explained above.
b. Restore
Lets you restore a previously taken backup. Entering this option presents you with a list of existing backups from the SD card that you can choose from for restoration.
c. Advanced Restore
This option is similar to the Restore option but once a backup has been selected to be restored, this option allows you to choose what parts of it to restore. You can choose to restore the boot, system, data, cache and sd-ext partitions.
7. mounts and storage
Allows you to perform maintenance tasks on all the internal and external partitions of your android device
a. mount/unmount /system, /data, /cache, /sdcard or /sd-ext
These options let you toggle between mounting or unmounting these respective partitions. Most users don’t need to change these options.
b. format boot, system, data, cache, sdcard or sd-ext
These let you directly format any of these partitions. Take extreme care with this option as formatting any of these partitions will result in losing all data on them, especially the boot and system partitions. Formatting the system partition will remove your ROM and leave your phone without an operating system while wiping the boot partition may brick your phone unless you restore or flash another one before rebooting your device.
c. mount USB storage
Lets you enable USB mass storage mode for your SD card right from recovery so that you can connect it to your computer via USB and transfer any files to/from it without having to leave recovery.
8. advanced
This section contains a few options most users will not require, though these can come handy quite often, especially wiping Dalvik cache, which is required before most ROM installations.
1. Reboot Recovery
Lets you directly and very conveniently reboot from recovery right back into recovery. This is useful option for certain back-to-back installations that require the device to at least boot once between them.
2. Wipe Dalvik Cache
Allows you to wipe the cache for the Dalvik virtual machine (the custom-built Java virtual machine for Android).This is required before most ROM installations and at other occasions too, for fixing some problems.
3. Wipe Battery Stats
Wipes the saved battery usage statistics and effectively recalibrates the battery. Useful in various scenarios when Android isn’t showing correct battery levels.
4. Report Error
In case of errors, this feature can be used to save a log of recent ClockworkMod recovery operations on the SD card that you can later report from Android using ROM Manager.
5. Key Test
Lets you press any of the hardware keys to see if they are properly functioning, and to see their key codes.
6. Partition SD Card
This option gives you a no-frills way to partition your SD card properly for use with ROMs that support data2ext (a very handy hack for low internal memory devices that enables an /sd-ext partition on the SD card to be used as the internal user data storage i.e. as the /data partition). Once this option is selected, you will be given options to choose the sizes for the /sd-ext partition as well as an optional /swap partition on the SD card, and will then automatically format it for you, leaving the remaining space for normal SD card usage. This option will wipe all data from your SD card so use it with caution!
7. Fix Permissions
Fixes the file permissions for the internal memory partitions back to default. This is very useful as a fix for several errors and Force-Closes that start appearing after you or an application you installed and provided root access end up messing up the permissions of important files.
4.Using ClockworkMod for ROM, kernel, apps, theme or mod installation
While in the complete feature tour we have already shown you how to install a ROM, kernel, app, theme or any similar mod from a recovery-flashable zip file using the recovery options, those of you who jumped straight to this section expecting to get just this information quickly are at the right place!
This guide is primary focused on a full feature tour of CWM but in our previously written guide on how to flash a ROM or app from a zip to an Android device file from recovery, we have already covered in detail how to use ClockworkMod for installing any ROM, kernel, app, theme or mod using a recovery-flashable zip file. While that guide is based on an older version of ClockworkMod recovery, everything in it still applies to the latest versions and should work flawlessly.
5.How To Install A ROM or App from zip file to Android device from recovery
Please note that the terms ‘installing’ and ‘flashing’ can be used interchangeably here and will mean the same thing.
Rooting your device renders its warranty void.
ALWAYS take backups before rooting or flashing a custom ROM or app to your phone.
Flashing a defective ROM or app to your phone might brick it so choose the ROMs and software that you flash wisely and never install a ROM or application from an untrusted source.
AddictiveTips will not be liable if your device gets damaged or bricked during the process.
Official ROM updates from device manufacturers or carriers are released in conveniently packaged installation files that you can run on your computer while your Android device is connected to it, and they automatically take care of updating your phone’s system. Similarly, most applications are available directly in the Android Market for easy installation, or come packaged as convenient ‘.apk’ files that you can just run on your Android phone to install. The case is not the same with most custom ROMs and several custom applications, which come in .zip files rather than PC installers or .apk files.
The idea of installing a customized operating system to their smartphone can be quite intimidating for inexperienced users. Though once they get used to it, some of them end up trying out different ROMs for their devices several times a day. While I don’t exactly recommend that you flash every new ROM that is made available for your Android phone, we are here to help you get over the fear of flashing a ROM that enhances the capabilities of your device so that you can use it to its fullest potential.
Here is a quick look at what we will be covering in this guide. Feel free to skip to the real deal if you already meet the prerequisites.
• Before We Begin: Battery Check
• Before We Begin: Unlocking the Bootloader (Stock Android Devices Only)
• Before We Begin: Rooting
• Before We Proceed: Installing a Custom Recovery
• The Real Deal: Installing a Custom ROM to your Phone
• The Real Deal: Installing an App From a Zip File to your Phone
There are certain steps that you might not require, and we shall be mentioning them in each section.
Before We Begin: Battery Check
Before you proceed with any of the following steps, make sure your phone’s battery level is not too low. It is recommended to have it at 50% or more. Do NOT take this lightly. If your phone’s battery runs out while you are attempting to flash a custom ROM, there is a significant chance of your phone getting bricked and becoming unusable PERMANENTLY.
Before We Begin:Unlocking the Bootloader (Stock Android Devices Only)
Note: This step applies only to Android devices with stock version of Android installed. At the moment, Google Nexus One and Nexus S are the only two such devices available. You may skip this step if you are using any other Android device.
Users of stock Android devices such as the Google Nexus One or Nexus S also need to unlock its bootloader before they can proceed. Once you have done this, you may proceed to the next step.
Before We Begin: Rooting
Note: You may skip this step if your device is already rooted, or if you already know how to root it.
Before you can install a custom ROM to your device, your phone needs to be rooted. Rooting is basically administrator or root level access required to perform administrative tasks on your Android device. Once you are done with the rooting process, you may proceed to the next step.
Before We Proceed: Installing A Custom Recovery
Note: You may skip this step if you already have a custom recovery installed on your device.
Rooting grants you the necessary access level to execute administrative tasks on your Android device but it is the recovery that provides the tools necessary to actually perform those tasks. While every Android device ships with a recovery, the stock recovery is quite limited in what it lets you do, and you need a custom recovery image to perform advanced operations on your device. Once you have a custom recovery installed on your phone, you will be ready to proceed to the next step.
The Real Deal: Installing a Custom ROM to your Phone
Now that you have a custom recovery installed on your phone, you can perform all sorts of wonderful advanced operations on your device and this includes the ability to flash a ROM or application from a zip file. The procedure is pretty standard for most ROMs, though there are certain ROMs which require additional steps for their installation. Since those steps differ from ROM to ROM, pay attention to instructions and this includes only the standard instructions here.
• Manually
1. Download the ROM from the link given in the article featuring that ROM. It should be a zip file.
2. Connect your phone to your computer via USB and mount its storage card.
3. Copy the downloaded ROM to the root of the storage card.
4. Power your phone off and reboot it into recovery. This will involve using a combination of your device’s hardware keys. Once in recovery, you can navigate its menu using the volume up and volume down hardware keys or your phone’s trackball / optical track pad if it comes equipped with one.
5. Use the ‘backup and restore’ feature of recovery to backup your existing ROM installation, software and data. This step is known as performing a nandroid backup. ALWAYS perform a backup before flashing a custom ROM, UNLESS you can afford to lose everything that’s on your phone at the moment.
Note: ALWAYS choose to perform the following steps 6, 7 and 8 UNLESS the ROM you are attempting to flash is an updated version of the same ROM that you are currently using, and is compatible with the current installation’s data. It is usually mentioned with the update whether you can install it over a previous version without wiping its data or not.
6. Get back to the main recovery menu and use the option ‘wipe data/factory reset’. You will be prompted to confirm this action. Select “Yes – Delete all user data”.
7. From the main recovery menu, select ‘wipe cache partition’. You will be prompted to confirm this action. Select ‘Yes – Wipe Cache’.
8. From the main recovery menu, enter the ‘advanced’ menu. From this menu, select ‘Wipe Dalvik Cache’. You will be prompted to confirm this action. Select ‘Yes – Format/System’.
9. From the main recovery menu, enter the ‘Mounts and Storage’ menu. From this menu, select ‘Format/System’. You will be prompted to confirm this action. Select ‘Yes – Wipe Dalvik Cache’.
10. Go back to the main recovery menu by pressing the back button and select the ‘Install zip from SD card’ option.
11. Select ‘choose zip from sdcard’ to get a list of the files and folders on your SD card. Scroll to the ROM’s file that you copied there in step 3, and select it. You will be prompted to confirm this action. Select ‘Yes – Install file_name.zip’ where file_name.zip is the name of the zip file that you are trying to install.
12. Wait patiently while the ROM is flashed to your phone via recovery.
13. Once the installation is complete, head back to the main recovery menu if you aren’t there, and select ‘reboot system now’. Your phone will now boot into the newly installed ROM.
The Real Deal: Installing an App From a Zip File to your Phone
While most apps for Android devices are available at the app store for direct download and installation or as .apk files for direct installation, there are certain apps which are only available as zip files installable from recovery. Their installation procedure is the same as installing a custom ROM that we just featured above. However, there are a few minute differences.
• When installing an app from a zip file, you do NOT need to perform the ‘wipe data/factory reset’ or ‘wipe/system’ step so NEVER do that unless you know what you are doing, have a complete backup and want to start using your ROM as a fresh installation with the new app added.
• You might or might not need to wipe the cache and the dalvik cache for installing apps from zip file. This varies from app to app and the developers of such apps as well as many reviewers including us mention when featuring an app whether it requires a cache and dalvik cache wipe or not. However, it never hurts to wipe these caches anyway, and it does not effect the data on your device or its storage card.
There you go, this concludes the guide on how to flash a ROM or app from a zip file to your Android device using a custom recovery. To try out the skills that you just learned, search our site for custom ROMs for your phone and start flashing, always remembering to take backups first!
Important note: This guide is retrieved from the VeNum Complete Guide with only few additions and corrections by me, so All thanks should go to him!
PS: If you see any error, please contact me to edit the OP.
Nandroid Backup - CWM
What is a Nandroid Backup?
It is a full backup of the partitions on your device’s NAND flash (NAND actually stands for NOT AND, which in simple terms means an electronic gate). Basically a backup of your phones hard drive if you will...
The Nandroid Backup is a snapshot of your device (it means everything on your phone – your apps, data, your current ROM and even the kernel is backed up) at the time you do the back up. If you restore the back up, it changes your phone BACK to that state. You will need custom recovery (CWM/TWRP). So make sure you have CWM or TWRP on your device.
The SD Card data is not backed up in the process. Although, the Nandroid Backup itself is created on your SD card. Make sure you have enough space on your SD card to make a COMPLETE copy of your phone.
It’s highly recommended that once you have done a backup, you manually copy it to your computer in case your sd card is wiped or corrupted.
Pre-requisites:
1. Rooted Device:
2. Custom Recovery (CWM or TWRP)
While the OS is running you cannot do a backup. The bootloader in the recovery enables you to take a backup of the OS while it’s not running.
How to Make a Nandroid Backup via CWM:
Backup via CWM:
1.Boot into Recovery pressing in the same time Volume Up + Home + Power buttons for our Galaxy S4 mini LTE/3G phones
2. Select ‘Backup and Restore’ from the recovery.
Once you are in recovery, scroll down to the option ‘Backup and Recovery’ with volume Up/Down and select it (Power button for select).
3. Start the backup.
Once you are on the Nandroid screen, select ‘Backup’ to start the backup process. You have the option to ‘Restore’ backup on the same screen.
The backup process may take a while. Take a break for a coffee.
4. Transfer the backup to your computer (recommended).
Once you reboot, you can see the backup in the ‘clockworkmod/backup/…’ (or similar file) directory on your SD card.
Move, copy, or paste this folder on your PC safely.
Restore from a Nandroid Backup via CWM:
1. Boot your device into CWM and navigate to the Nandroid screen.
2. Choose ‘Restore’ and begin the process.
If you select ‘Advanced Restore’ option, you may select which part of the backup to restore – i. e. the boot,system, data or cache. Or choose the whole backup.
3. Reboot your device. Your system is now restored and is exactly the same as the time when the backup was taken.
Video guide (ignore phones from videos ) :
CWM guide
TWRP guide
[app] Online Nandroid Backup
Online Nandroid Backup - FULLY SUPPORTED with our Samsung S4 mini GT I9195/I9190/I9192
Online Nandroid - Supported Devices
Nandroid backups are usually performed in recovery mode. This means you would have to turn off your phone and reboot in recovery mode, which wastes a whole lot of time rebooting and a lot more time offline. With this tool you can do nandroid backups without switching off your device.
Requirements:
1. Rooted android phone
2. A terminal emulator installed on phone
3. Latest version of Busybox
4. A working CWM or TWRP
5. Patience
Features:
* Creates backups in the CMW 5 and 6 style or TWRP!
* Full support of the onandroid script.
* Create custom names for your backups.
* Choose what partitions get backed up.
Important: This tool requires a rooted phone with busybox to work!
Download from market: https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup
Or from original thread: http://forum.xda-developers.com/showthread.php?t=1620255
Reserved, for future.
I will complete with more info's and screenshots in few days.
Please, keep thread clean and don't post "Thanks".
Regards
I assume this guide was written for nexus devices because the nexus one and nexus s are mentionend and you wrote that the bootloader has to be unlocked (Which has to be done on most devices. Only Samsung(?) has unlocked bootloaders. You could add that unlocking wipes user data.)
The second thing is: Your phone doesnt have to be rooted to install a custom recovey. Either you flash a recovery with Odin (add this aswell) and wipe everything to install a custom rom or you the superuser app to root your stock firmware.
But excuse me if you weren't finished with the post
Did you read carrefully OP and the note from the end?
Important note: This guide is retrieved from the VeNum Complete Guide with only few additions and corrections by me, so All thanks should go to him!
Click to expand...
Click to collapse
Excellent guide, thank you!
R_a_z_v_a_n said:
Online Nandroid Backup - FULLY SUPPORTED with our Samsung S Advance GT I9070 (Janice)
Click to expand...
Click to collapse
Are you saying that the onandroid Partition Script for I9070 works perfectly fine with S4 Mini i9195?
impactor said:
Are you saying that the onandroid Partition Script for I9070 works perfectly fine with S4 Mini i9195?
Click to expand...
Click to collapse
Yep its fully supported, that post its copy/paste from my previous phone/thread. :highfive:
Edited my post, thanks for report.
Check here compatibilities:
Online Nandroid - Supported Devices
Nice really great information Thanks again:good:
I have looked around and haven't seen anyone mention this so I thought I would post about it since I've been using it and thought it was cool. I hope others find this useful.
The thread I'm talking about: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
The original thread quoted by @aukhan: http://forum.xda-developers.com/showthread.php?t=2447534
All credit goes to the original developers for this tool.
Thanks to @aukhan, @rlorange, @chenxialong, and other contributors.
Download the first .apk (Dual Boot Patcher). That is the only app that you should need to complete the process. A video guide is posted by @aukhan here: https://www.youtube.com/watch?v=h_i3GW_s-VE&spfreload=10
That is the best walkthrough I've seen.
Since it was requested, I've made a video walkthrough of this process: https://youtu.be/5VzYED1hhUA
Basically you patch all of the .zip files that you would have flashed normally and then you flash them to a new ROM slot. If there are more questions that the video doesn't answer I'll be happy to answer them or post a better walkthrough if needed.
It should be noted that to switch back and forth you'll need to install the Dual Boot Patcher apk on both ROMs. This does not affect TWRP Recovery.
I have run this with JasmineROM as the primary and CM13 as the secondary as well as CM13 as primary and JasmineROM as Secondary. I currently have this set-up to try different ROMs without needing to completely wipe my phone and deal with backups/restores. I also use it to use CM13 as my primary while having stock options (S-Pen, Car BT, and other Samsung stuff) available in a quick reboot.
Edit:
More Specific Instructions:
1) Download all .zip files that you would flash if you were going to flash the ROM normally (ex. CM13, Gapps, SuperSu, XPosed, datafixes, kernels, etc)
2) Download the Dual Boot Patcher apk: https://snapshots.noobdev.io/ and install it on your phone
3) Open ES File Explorer or another Root Explorer app and navigate to /sdcard/MultiBoot
4) Create a folder labeled "dual" in that directory (now there is a folder /sdcard/MultiBoot/dual)
5) Open Dual Boot Patcher app and tap the three lines in the upper left then select "Patch Zip File"
6) Tap the plus button and find each of the .zip files that you will be flashing. After selecting one make sure to change "Partition Configuration" to "Secondary"
7) A file browser will now open. Navigate to /sdcard/MultiBoot/dual and save the patched zip file there.
8) You may now repeat steps 6 and 7 to add the rest of the zip files
9) Tap the check mark in the upper right to "Patch" all of the .zip files
10) Tap the three lines in the upper left again and select ROMs
11) Tap the phone icon in the lower right and push okay
12) Tap the plus button in the lower right and navigate to the /sdcard/MultiBoot/dual folder. Select the main ROM (CM13, Kyubi, JasmineROM, etc) and tap "keep location"
13) Repeat step 12 until all zips are added in the order you want them flashed (the order is important). If you mess up swipe the one that's wrong to the right to remove it from the list
14) Tap the check mark in the upper right. A console should appear and it should virtually flash the ROM as you would expect in TWRP
15) Once it says "x/x completed" in cyan text and it has stopped you can just tap the back arrow in the upper left
16) If you go back to the ROMs page there should now be a "Secondary" ROM. To test it out you'll need to select it and then reboot the phone.
17) Once it has booted and you are past the setup you'll need to enable "unknown sources" in the menu and install Dual Boot Patcher. Once it's installed, open it. It should find the two ROMs and you'll be able to select Primary from the ROMs menu and reboot back
Edit 2:
This process can be done using any of the partition configurations listed when patching a Zip file. Secondary and Multi Slots go to the System partition, data slot goes to internal storage, and Extsd slot goes to the External SD card. I recommend not using the Multi Slots since more than two ROMs is a lot on the system partition.
If you have problems make sure to set the kernel and update the ramdisk before flashing and that the files are in the right folder typed exactly as it says in the prompt when patching the file.
I have noticed many problems when using a non-Touchwiz ROM as stock and trying to dual boot to a Touchwiz ROM. I have had bootloop situations when trying to dual boot to Kyubi or PaulPizz from CM13, but with PaulPizz as primary I have no issues switching back and forth.
In the event of a bootloop you can recover your primary ROM by entering TWRP, tapping install, selecting image in the bottom right corner, navigating to the /sdcard/MultiBoot/primary folder, and selecting the "boot.img" file. This will return your phone back to the primary ROM.
Edit 3: Video Tutorial: https://youtu.be/5VzYED1hhUA
If it is too blurry I can make another one, but I think you can see what you need to just fine. I hope it helps. I also forgot to mention that if you later want to flash anything to the ROM that you're "dual booting" into then all you have to do is patch the zip files and flash them like before except you're flashing to a slot that already has a ROM now.
Edit 4: I have now tested this on Marshmallow with success. I still recommend using a Touchwiz ROM as primary and you'll need to have a kernel that's permissive. I'm using Emotion, but I think Oscar's kernel should work as well. I have PaulPizzRom.VRU2CPF3.r-2 installed as primary with the CPF3 modem and Emotion kernel and CM13 as secondary (pretty much my daily driver at this point). Everything has been working so far.
Isn't there a kernel patch requirement for this to work?
Just tried it and working great for me. Jasmine primary, cm13 secondary. Definitely easier than messing with twrp to test roms. Thanks for the info!
jal3223 said:
Isn't there a kernel patch requirement for this to work?
Click to expand...
Click to collapse
I didn't need one to get this to work. You may be thinking of Multisystem, which is different and requires both ROMs to run the same kernel.
As far as I can tell this method boots each ROM with its own kernel. CM13 and JasmineROM both use a version of the Multisystem kernel, but I just checked and they are running different kernels.
I'll probably try the PaulPizz or Kyubi ROMs since I've been having some freeze issues with JasmineROM and see if the others work just as well.
shadeau said:
I didn't need one to get this to work. You may be thinking of Multisystem, which is different and requires both ROMs to run the same kernel.
As far as I can tell this method boots each ROM with its own kernel. CM13 and JasmineROM both use a version of the Multisystem kernel, but I just checked and they are running different kernels.
I'll probably try the PaulPizz or Kyubi ROMs since I've been having some freeze issues with JasmineROM and see if the others work just as well.
Click to expand...
Click to collapse
Awesome, thanks! I'm definitely going to give it a try.
I cannot seem to get it to recognize the path with the patched ROM file. none of the storage paths on my device show as "sdcard", they are either sdcard0 or ExtSdCard.
Even though the folder structure is created on the Internal storage, the DualBoot app does not recognize it.
EDIT: Nevermind, I realized I do not need that app. I just patched the ROM and then added it in the Patcher app mentioned above. The added the patched ROM to it and it shows up in the ROMs menu
EDIT2: This is just not working, I try and apply the ROM for dual boot/swap, however it fails to complete the configuration. I am on a rooted stock phone..could that be the issue?
jal3223 said:
Awesome, thanks! I'm definitely going to give it a try.
Click to expand...
Click to collapse
I just wanted to give an update and say I tried Kyubi ROM the other day and got it to boot just fine. I had one time where I needed to pull the battery, but then it rebooted to Kyubi and ran normally. I don't know if that was just bad luck or something else. I'm planning on trying PaulPizz's ROM today.
ssb13 said:
I cannot seem to get it to recognize the path with the patched ROM file. none of the storage paths on my device show as "sdcard", they are either sdcard0 or ExtSdCard.
Even though the folder structure is created on the Internal storage, the DualBoot app does not recognize it.
EDIT: Nevermind, I realized I do not need that app. I just patched the ROM and then added it in the Patcher app mentioned above. The added the patched ROM to it and it shows up in the ROMs menu
EDIT2: This is just not working, I try and apply the ROM for dual boot/swap, however it fails to complete the configuration. I am on a rooted stock phone..could that be the issue?
Click to expand...
Click to collapse
I added some better instructions in the OP. Can you tell me what step you're having problems with? JasmineROM is pretty close to stock so I assumed this would work just as well on the PaulPizz or stock ROM, but I personally haven't tried on either yet.
shadeau said:
I just wanted to give an update and say I tried Kyubi ROM the other day and got it to boot just fine. I had one time where I needed to pull the battery, but then it rebooted to Kyubi and ran normally. I don't know if that was just bad luck or something else. I'm planning on trying PaulPizz's ROM today.
I added some better instructions in the OP. Can you tell me what step you're having problems with? JasmineROM is pretty close to stock so I assumed this would work just as well on the PaulPizz or stock ROM, but I personally haven't tried on either yet.
Click to expand...
Click to collapse
I'll give it a try with the more specific steps. I think part of my issue was all the videos and other walk-throughs are with older versions of the software. I was also trying to use the other Dual Boot app that is in the other posts....that is where I had the path name issue.
I was finally able to get CM13 on the list of ROMs, however it would fail to switch to it....but that was using the Win32 app to patch it. I'll try it all with the phone app.
ssb13 said:
I'll give it a try with the more specific steps. I think part of my issue was all the videos and other walk-throughs are with older versions of the software. I was also trying to use the other Dual Boot app that is in the other posts....that is where I had the path name issue.
I was finally able to get CM13 on the list of ROMs, however it would fail to switch to it....but that was using the Win32 app to patch it. I'll try it all with the phone app.
Click to expand...
Click to collapse
I followed it to the T and here was my result...(screenshot attached)
EDIT: Added log file. Seems like perhaps it is either permissions, path, and or space issues.
ssb13 said:
I followed it to the T and here was my result...(screenshot attached)
EDIT: Added log file. Seems like perhaps it is either permissions, path, and or space issues.
Click to expand...
Click to collapse
I'll have to look at it tomorrow when I have time. You said you were on stock. What exactly are you running on your phone? What are the firmware version and the kernel? Also, how much free space is on your internal storage and are you using an SD card?
shadeau said:
I'll have to look at it tomorrow when I have time. You said you were on stock. What exactly are you running on your phone? What are the firmware version and the kernel? Also, how much free space is on your internal storage and are you using an SD card?
Click to expand...
Click to collapse
14gb free. About 40gb free on SD card.
Stock 5.1.1 bpa1.
Xceed kernel
Sent from my SM-N910V using Tapatalk
ssb13 said:
14gb free. About 40gb free on SD card.
Stock 5.1.1 bpa1.
Xceed kernel View attachment 3739482
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Try deleting all of the patched zip files and starting over. In the ROMs menu tap the three dots on the primary ROM and scroll down to the bottom. Update the ramdisk and set the kernel then reboot. Make a new folder in the sdcard/MultiBoot folder labeled "data-slot-1" all lowercase. Patch your .zip files and instead of selecting secondary select "Data Slot" and when it asks you what slot name, type "1". After tapping continue, navigate to the sdcard/MultiBoot/data-slot-1 folder and save the .zip files there. After the first time you should be able to select "1 (Data Slot)" for partition configuration instead of manually assigning one for subsequent .zips. Once you're done patching the files go back to the ROMs page and add a ROM then the .zips (selecting keep location like before) and see if that works.
The dual slot saves all ROM data to your system partition which could be pretty full even if your internal storage shows plenty of space. Since all apps are still on the system partition regardless of which slot you pick it may be good to look at how much free space is left before flashing. You can see how much space is left by tapping "Free Space" underneath the "Patch Zip File" button. The /system directory is your system partition.
shadeau said:
Try deleting all of the patched zip files and starting over. In the ROMs menu tap the three dots on the primary ROM and scroll down to the bottom. Update the ramdisk and set the kernel then reboot. Make a new folder in the sdcard/MultiBoot folder labeled "data-slot-1" all lowercase. Patch your .zip files and instead of selecting secondary select "Data Slot" and when it asks you what slot name, type "1". After tapping continue, navigate to the sdcard/MultiBoot/data-slot-1 folder and save the .zip files there. After the first time you should be able to select "1 (Data Slot)" for partition configuration instead of manually assigning one for subsequent .zips. Once you're done patching the files go back to the ROMs page and add a ROM then the .zips (selecting keep location like before) and see if that works.
The dual slot saves all ROM data to your system partition which could be pretty full even if your internal storage shows plenty of space. Since all apps are still on the system partition regardless of which slot you pick it may be good to look at how much free space is left before flashing. You can see how much space is left by tapping "Free Space" underneath the "Patch Zip File" button. The /system directory is your system partition.
Click to expand...
Click to collapse
Thank, I will try this method. I did check and the /raw/system partition is full. Should it be?
ssb13 said:
Thank, I will try this method. I did check and the /raw/system partition is full. Should it be?
Click to expand...
Click to collapse
My system partition says "Total size: 3.94 GiB, Free: 569.43 MiB" and that's with CM13 on Primary and PaulPizz on Secondary with Kyubi on data-slot-1. I haven't booted Kyubi yet so that may decrease my free space even further, but if your system partition is already full I don't think you'll be able to flash anything. You might try looking for big files in the /system directory. Also check to see if there are any files in /system/multiboot/dual and delete them. Do you have a lot of apps installed?
shadeau said:
My system partition says "Total size: 3.94 GiB, Free: 569.43 MiB" and that's with CM13 on Primary and PaulPizz on Secondary with Kyubi on data-slot-1. I haven't booted Kyubi yet so that may decrease my free space even further, but if your system partition is already full I don't think you'll be able to flash anything. You might try looking for big files in the /system directory. Also check to see if there are any files in /system/multiboot/dual and delete them. Do you have a lot of apps installed?
Click to expand...
Click to collapse
Mine says 56K free. Maybe I should revert to my nandroid which is pre-dualboot attempts and see. However I am on stock , rooted. Not even ROM, just the a rooted converter retail to DE. So perhaps the stock uses more system space.
ssb13 said:
Mine says 56K free. Maybe I should revert to my nandroid which is pre-dualboot attempts and see. However I am on stock , rooted. Not even ROM, just the a rooted converter retail to DE. So perhaps the stock uses more system space.
Click to expand...
Click to collapse
That might be a good option. If I tap the three dots for each of my ROMs the PaulPizz (essentially stock) lists a system size of 2.09 GiB, which is half the size of the system partition. You might want to check yours and see what it lists as the system size.
You might also just try using the data-slot-1 and see if it works before the nandroid revert.
shadeau said:
That might be a good option. If I tap the three dots for each of my ROMs the PaulPizz (essentially stock) lists a system size of 2.09 GiB, which is half the size of the system partition. You might want to check yours and see what it lists as the system size.
You might also just try using the data-slot-1 and see if it works before the nandroid revert.
Click to expand...
Click to collapse
Using data-slot-1 I received an exit code of 0 and a 2/2 completed!!!
I cannot reboot now because I am waiting for a phone call, but when I do I'll report in. :highfive:
ssb13 said:
Using data-slot-1 I received an exit code of 0 and a 2/2 completed!!!
I cannot reboot now because I am waiting for a phone call, but when I do I'll report in. :highfive:
Click to expand...
Click to collapse
So that did work. Now I have a follow up question. Say I flash a ROM, like CM13 and GAPPS...but when I boot a bunch of apps keep FC'ing and they keep relaunching, like the SetupWizard...basically I'm stuck clicking OK on all the messsages and they just keep coming back.
My question...am I stuck? How can I flip back to booting to my primary ROM? can I delete the files from the data-slot-1 folder? Any thoughts?
ssb13 said:
So that did work. Now I have a follow up question. Say I flash a ROM, like CM13 and GAPPS...but when I boot a bunch of apps keep FC'ing and they keep relaunching, like the SetupWizard...basically I'm stuck clicking OK on all the messsages and they just keep coming back.
My question...am I stuck? How can I flip back to booting to my primary ROM? can I delete the files from the data-slot-1 folder? Any thoughts?
Click to expand...
Click to collapse
It's actually pretty easy to revert back with TWRP. I was going to add this to the OP when I had time: Boot to recovery and tap install, then select image in the bottom right and navigate to /system/MultiBoot/Primary and select the boot.img, then flash it to the boot partition. That will let you boot to the primary ROM.
shadeau said:
It's actually pretty easy to revert back with TWRP. I was going to add this to the OP when I had time: Boot to recovery and tap install, then select image in the bottom right and navigate to /system/MultiBoot/Primary and select the boot.img, then flash it to the boot partition. That will let you boot to the primary ROM.
Click to expand...
Click to collapse
Thanks.
Multiboot project is a work done by @chenxiaolong , I do not own any of the work presented over here.I just sent the author need logs.Support All Version
About Multiboot : A project to handle different ROMS at the same time so that you actually can use different ROMS without having to wipe up device to flash ROMS, it allows installation of more thn one ROM with all the features enabled.
USAGE1. First, boot into your primary ROM and install the Dual Boot Patcher app
2. Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
3. Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
DOWNLOAD : https://snapshots.noobdev.io/(Added support 10.04)
ORIGINAL THREAD : http://forum.xda-developers.com/show....php?t=2447534
Manual
Step 1
download and install DualbootPatcher app
if you are in motion rom do this
Step 2
Open the app
Slide the menu and go to ROMs
It will request for root access
Allow the root access
and a message will ask about to set the kernel
Select "set now" and after it said kernel set now
Step 3
reboot your device
Now after device is turned on
Go to the app and navigate "Patch Zip File" from the menu
and tap that + button select zip of ROM you want to patch
A window will come up and if you see in "your device selected by default" you done everything right.
then:
If you are CMuser ( means you have a cm12.1 , cm11 or ... on your primary rom)
and want to install another cyanogeonmod rom (cm11 , cm12.1 ...)
Select the partition configuration as "Secondary"
If you are trying to install another ROM that has a huge system
Select partiton configuration as "data slot" and select an ID for the ROM
better to be a number
(It will be installed on data partition this means it will use the device internal storage space )
and select continue and set where to place patched file .
you can add more files to patch there .
and after you are ready to patch the files tap that tick button in action bar
to start patching
Step 4
After you patched the zip ROM go ahead and navigate to ROMs from the menu
select button down corner and select patched zip you patched
and then select keep location (or if you want you can change the location ) and add more patched zips or tap the up corner tick to start install
note : if any thing wrong happend PM me on telegram and send me multiboot.log in internal storage.
Step 5
after ROM is installed
it should be selected the installed rom .
tap and switch to primary rom
now use three dot on side of primary and select update ram disk
and then select reboot now
now after device rebooted go back to the app navigate to roms
now use three dot on side of new ROM you installed and select update ram disk
after it said done
select the rom you installed . ( tap on the icon of it or name )
( if you saw a message about checksum select continue )
reboot the device and see the magic !!!!
your new ROM is booting !!!!
Cool, let's stop enjoying and continue
Step 6
now after your new ROM booted
take your time to setup the device
and go and install dualboot patcher app again
now open the app
Go to ROMs and allow root access and
now use three dot menu in side of primary ROM and select update ramdisk
now use three dot in side of new ROM and select update ramdisk
and reboot
Soon there will be video instruction
NOTE:Support 4.2-6.0
CREDITSAll credits goes to @chenxiaolong for his hard work on this project, kindly say thanks to him
INFO
Code:
Quick info
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
App and data sharing
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
thx so much inote 2 still not get work on it so sad
I'm proud to present the first dual boot project for the all Exynos7870 and Exynos7880-based Samsung devices. This project started off as a feature in my ROM, but not anymore. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
Well, Just flash the patched zip file via recovery (Custom Recovery, like TWRP of course)
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads
Here is the latest build : https://www.androidfilehost.com/?fid=962021903579496224
XDA:DevDB Information
DualBoot Patcher APP, Device Specific App for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
lzzy12
Source Code: https://github.com/Mysteryagr/DualBootPatcher
Version Information
Status: Beta
Created 2017-12-03
Last Updated 2017-12-03
thanks bro ,Great Work
Wow Good Work Bro It Will Be Very Useful For Us Bro
??
Great
got error 1 when flashing lineage as second rom
Tried it. It works if I flash the ROM from recovery but if I want to switch to primary using DualBoot utilities it doesn't work. Fortunately I had made a buk up...
One more thing : The secondary ROM detects the SD card as corrupted and needs formatting if installed to external storage :/
Can anybody help my?
I want to install second ROM on sd card, it will be perfect on ext4 separete partition.
I'v tried it.
I install second ROM on sd card (now it have only one partition vfat), but it cycle rebooting. Helps only restore from TWRP recovery.
DualBootUtilities..zip dont work and have an ERROR 1 in TWRP both 3.2.1.0 and 3.1.1.0.
My primary ROM is last oficial Android 6.0.1. , second ROM is [ROM] Stockrom Lite SM-A520F
Primary ROM rooted SuperSu, CSC - BTU, bootloader - A520FXXU4BRC4, PDA - A520FXXS2AQH1, Radio - A520FXXU4BRC1, ROM - A520FXXS4CRE1/A520FOXA4CRD3/A520FXXU4CRD3, Kernel 3.18.14-10911830 [email protected] #1 32-bit
Here is recovery log file
---------- Post added at 12:02 PM ---------- Previous post was at 11:56 AM ----------
May be it is the reason?:
I:Legacy property environment initialized.
mount: mounting /dev/block/mmcblk0p20 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p25 on /data failed: Device or resource busy
Click to expand...
Click to collapse
I have this problem when I go to roms. Anybody know what's wrong?
iloveoreos said:
I have this problem when I go to roms. Anybody know what's wrong?
Click to expand...
Click to collapse
You need root for this to work. Do you have that?
sheepkill15 said:
You need root for this to work. Do you have that?
Click to expand...
Click to collapse
Yes, I'm rooted with magisk. I wonder if it matters what version I am running. I am running stock 8.0 on an A520W.
iloveoreos said:
Yes, I'm rooted with magisk. I wonder if it matters what version I am running. I am running stock 8.0 on an A520W.
Click to expand...
Click to collapse
Oh right. I don't know if op patched something about this, but originally touchwiz roms don't work with DualBoot, not even Hades.
Or, at least, I couldn't get it to work.
sheepkill15 said:
Oh right. I don't know if op patched something about this, but originally touchwiz roms don't work with DualBoot, not even Hades.
Or, at least, I couldn't get it to work.
Click to expand...
Click to collapse
Ok, that makes sense, I tried a different version on my note5 and it didn't work either. The OP said to set Tw rom as primary though, is there a way to do that?
Edit: Would it work to flash lineage os, install dualboot, and then flash touchwiz as primary?
Do ROMs boot normally from an SD card? Or are they a bit slow?
iloveoreos said:
Do ROMs boot normally from an SD card? Or are they a bit slow?
Click to expand...
Click to collapse
Depends on the SD Card ;p
But, in my experience, SD is slower than internal memory
Where to get the DualBootUtilities? Cant find them in this thread. Can I use the official ones from the website? Or can I just install the App and im fine?
iloveoreos said:
Do ROMs boot normally from an SD card? Or are they a bit slow?
Click to expand...
Click to collapse
Did you fixed the error when going to ROMs? Im having the same error and I dont know what to do. Im rooted with magisk on Stock ROM 8.0
simon151102 said:
Did you fixed the error when going to ROMs? Im having the same error and I dont know what to do. Im rooted with magisk on Stock ROM 8.0
Click to expand...
Click to collapse
Try a custom ROM like lineage os and it should fix that error. However, when I updated ramdisk through dual boot on lineage os 16, my internal storage would quit showing up in stock file manager and downloads would fail. Haven't tried on any other ROM s though.
DualBootUtilities.zip?
lzzy12 said:
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
Click to expand...
Click to collapse
Great job ,thanks. I did'nt find the download link "DualBootUtilities.zip"
I am getting an error 1 while flashing a patched ROM. It looks like the ROMs aren't compatible by looking at the logs. Don't know if that is the correct verdict though.
C A O S(Note, I did not make this rom. This is a Generic System Image (GSI) made by Caos' devs. so it is not specifically built for the A51, but it's really stable and I am using it now. ALL CREDIT GOES TO CAOS' DEVS!)
Your warranty is now void!We're not responsible for bricked devices, dead SD cards,thermonuclear war, or you getting fired because the alarm app failed. Pleasedo some research if you have any concerns about features included in this ROMbefore flashing it! YOU are choosing to make these modifications, and ifyou point the finger at us for messing up your device, we will laugh at you
CAOS (Custom AOSP OS) is a project which is based on @phhusson's Treble GSI AOSP 10. CAOS' devs began it because ASOP has stability, speed and support but also some issues and limitations - pure AOSP's code has some bugs and it doesn't have much useful things and it's hard to pull it. So CAOS' devs did this fork. System can run with SELinux enforced state, as an original Phh AOSP GSI. Fully compatible with PHH-Treble patches exclude few low level changes: no root app, no "su" binary in system; by default exist file /system/phh/secure (for Google Certification PASS), so if you can boot AOSP GSI, but can't boot CAOS - try to removing that file
UPDATE VERSION
latest build: 2020.10.29
treble patches: v222+
SPL: 5 Oct 2020
File Downloads/InstallationTHINGS THAT YOU NEED ON YOUR WINDOWS COMPUTER.
Odin
Unzip the file. There is a EXE file in it. Double click it to launch. There will be a pop up, just press ok.
FILES THAT YOU NEED TO FLASH THE ROM.The rom itself
Make sure you have 7-zip installed. Right click it and click extract files. Go into the unzipped folder and rename the file inside to "system.img"
TWRP Decrypter
Just leave this file as a zip. Don't unzip it.
ChonDoe Flasher
Just leave this file as a zip, Don't unzip it.
INSTALL RECOVERY AND UNLOCK BOOTLOADER (SKIP THIS PART IF YOU ALREADY HAVE TWRP.)I have made a reddit post on twrp. DO NOT DO THE MAGISK PART.
FLASHING THE FILESGo into TWRP. Press wipe and go into format data. Type in yes and wipe your data. Press the home button in your nav bar and go back into Wipe. Press advanced wipe, tick "data", "Dalvik / ART cache" and "Cache". Format it.
Press the home button in the nav bar again. Now, go into reboot and click recovery. Don't do anything. Once it's back into TWRP, plug your phone into the pc if you haven't already.
On your Windows PC, go into File Explorer, This PC, A515F and then internal storage. Take the "system.img" file and drag it into there. Do the same with "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip" and "ChonDoe_Flasher.zip"
Once all of them are copied, go onto your phone. Click install and you should see your files. If you don't, go into /sdcard. Flash "ChonDoe_Flasher.zip". Once it's done, flash "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip". Press "Reboot System" once "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip" is installed.
If this looks really confusing to you, there is a tutorial for this. However, it's for HavocOS. But everything is the same except the rom. But the steps are the same. Watch it here.
Congrats! You have installed Caos!
CONTACTS
> telegram group
> project page
KNOWN BUGS:
• excluding fixes, the same as on AOSP Quack (in some cases doesn't work: broadcasting on TV, calls via BT; offline charging does not work normally fingerprint doesnt work; problems with GPS etc etc)
NOTE: always test ROM first without Magisk (with clean boot ramdisk). and don't send me bug reports if you have:
a) Magisk installedb) modified/custom vendor or kernelc) dirty flashing rom without wiping data
CREDITS
persons: @phhusson
projects: TrebleGSI • BlissROMs • crDroid • PixelExperience • ION • neon-OS • Havoc-OS • LineageOS • Evolution-X • LiquidRemix • ExtendedUI • GrapheneOS • abc rom