Is there a way to have a backup.sh in system/addon.d that will restore the file after a flash when the system is installing the same file? Say for instance on a personal zip I have it install a a mixer_path to the system and a module to etc., I modified a gapps backup package to keep the two modified files on a dirty flash. The module which was not part of the rom zip will stay with a dirty flash but the mixer_path that is modified from the system zip will get overwritten. I hope this makes sense.
Related
I am making an customized version of Stock ROM so I decompiled the 4 sparse files and did the modifications I wanted to,so now I have so make it a Flashable Zip to install it For that process I have to Make the System in System.new.DAT like CM or System.IMG or I can push the System directory directly in the Zip to sign.
Any attempt to help will be appreciated.
Hi, I have an android device with a custom recovery, I also have the ROM package and I can flash the system directory using the recovery, and I can modify the contents of the ROM package and then flash it, I want to add to this ROM GApps, I've downloaded the GApps package,
It has the folder /system and META-INF that includes the installation script updater-script.sh, The ROM package also have updater-script.sh.
1. Is if it possible to install GApps on to this ROM by copying the contents of updater-script.sh of GApps into the updater-script.sh of the ROM package and copying the contents of /system of GApps to /system of the ROM package?
2. Should I be worried about ROM's META-INT signature files? (CERT.RSA,CERT.SF,MANIFEST.MF)
Thanks.
Hi, I have a device with custom recovery that can update ROM using update files, I got a working update file (zip contains system/ and META-INT/), When I'm unzipping it, add files to it and zip it again then flashing it, I get update failed, I even get update failed when I'm just unzipping and zipping without adding files or touching the content in the zip. Does anyone know why it might happen?
Thanks.
Hello guys,
i have a Geotel Amigo with Android Nougat.
I need your help.
No tools working for root (King(o), Towel, Eroot, Frama, Iroot, Genius.
No costum rom existent.
Have you are a idee?
Need help for root
Try to use magisk. You will need Magisk manager and also the boot.img rom file that you extracted from the stock rom file. Load the boot.img file in the magisk manager and patch it. Then flash the patched boot.img file with using fastboot. If your device is rebooted normally after flashing, you're lucky. But, before you want to patch, make sure that you will need to perform some changes in boot.img file like turning off security properties inside default.prop config file when extracting boot.img file.
One more thing is you must perform backup before flashing!
amirzaim said:
Try to use magisk. You will need Magisk manager and also the boot.img rom file that you extracted from the stock rom file. Load the boot.img file in the magisk manager and patch it. Then flash the patched boot.img file with using fastboot. If your device is rebooted normally after flashing, you're lucky. But, before you want to patch, make sure that you will need to perform some changes in boot.img file like turning off security properties inside default.prop config file when extracting boot.img file.
One more thing is you must perform backup before flashing!
Click to expand...
Click to collapse
Hello amirzaim,
not possible. I need TWRP? For my device not TWRP.
Or can you step by step informations give for me?
Many thanks
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 J7 (2017)
Contributors
lzzy12
Source Code: https://github.com/Mysteryagr/DualBootPatcher
Version Information
Status: Beta
Created 2017-12-03
Last Updated 2017-12-03
Thanks for this MOD
will definitely use this when/ if we get los for our phone thanks
How can I flash GApps ??
is this mod still alive ?
I'm trying to make a flashable zip for TWRP to install a Lenovo Z6 Pro stock ROM. I create the .zip file with Boot, System and Vendor (I'd add the rest of the firmware later). Boot and Vendor are installed but system.img is not installed. I know that I could use .dat files but I'm specially interested on using the image files.
I took as template another ROM which uses .IMG files too with the function 'package_extract_file'. I just replaced the .IMG files making sure that the names are exactly the same, and also I'm sure that my system.img is raw. When I try to install the flashable zip from recovery it prompts the uiprint "Patching system unconditionally" but nothing is installed and skips directly to patch the vendor partitions which is successfully patched.
Any help or clue will be much appreciated. Thanks in advance.