Haven't seen anyone else discussing this particular solution yet so figured I'd share that we can boot multiple roms using dual boot patcher by @chenxiaolong.
*The only things I'd recommend are the following:
*MAKING A BACKUP FIRST IN RECOVERY. Especially if you've never used the app, this helps in case you misunderstood something or didn't read enough or didn't think enough or the dog ate your homework.
*I recommend using TWRP version 3.0.3-0 which can be found here - https://dl.twrp.me/angler/
* I have not tried this with f2fs only ext4 so naturally I'd only recommend using ext4 partitioning on your device.
* If your device is encrypted in any way booting multiple roms will not work, which should be obvious but I'll state that anyways. Thanks @JKforUA for helping us figure this out.
*If you want to boot more than just two roms, that you use the data slot options for your roms which can be named anything you'd like and they will be stored on the phones internal storage.
* Make sure you're on the latest Radio and Bootloader for the nexus 6p, I flashed this and it works fine and is backwards compatible with Marshmallow roms.
Radio & Bootloader link -
https://forum.xda-developers.com/nexus-6p/general/nexus-6p-radio-bootloader-recovery-t3433637
* Use the patcher app to update the ramdisk and set your primary rom's kernel as Primary before patching or flashing anything.
*If you use the fingerprint scanner you'll have to delete the file /data/system/locksettings.db in each multi boot directory, this disables getting an incorrect pin error when switching roms.
*If using a marshmallow and nougat rom you'll need to flash the appropriate vendor image in recovery before boot.
*Vendor images should not be patched.
This process is fairly simple to me because I've been using it for years but if you have any questions feel free to ask in this thread and hit thanks if I helped ya.
* Before reporting errors I would suggest you try the following steps-
1. Make sure you're using this version of the patcher app because it is the one I have been using without issue -
Version 9.1.0r80-
https://dbp.noobdev.io/files/9.1.0....atcherAndroid-9.1.0.r80.gd5920b2-snapshot.apk
2. Make sure you have enough free space to have two of the zips you want to use because that is what you will have after you patch.
3. Make sure your path to the zip is correct when browsing for the zip, go through internal storage to the directory where the zip is.
4. If you get any error patching, uninstall the patcher app, re-download it, and reinstall it.
5. There is also a Windows version you can try if you prefer.
*If you are still having issues we can discuss it here, and if nobody can seem to come up with a fix in this thread then errors can further be reported by following instructions here - https://dbp.noobdev.io/downloads/
Credits - @chenxiaolong for the patcher app!
Links :
Dual boot patcher (All versions) - https://dbp.noobdev.io
Original forum - https://forum.xda-developers.com/showthread.php?t=2447534
* Screen shots of my current setup attached below for additional guidance if desired.
Status - sharing, using, in some cases testing, always learning (^_-)...
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Thanks for sharing. Used this on my further G4. Didn't know that our device is supported. So no need to wait until multirom is working on 7.1.1. Gonna play around now.
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
DaringDomino3s said:
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Click to expand...
Click to collapse
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
OmegaBlaze said:
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
Click to expand...
Click to collapse
Hmmm I found this
https://forum.xda-developers.com/showpost.php?p=64727670&postcount=8259
I would try re-downloading the app because I haven't had it crash in any roms I've used yet, I just grabbed the latest build, installed, opened, granted root when prompted, updated the ramdisk if needed which is indicated the app, rebooted when prompted, set kernel, and done.
If it's still crashing for you there's the usual force closing the app from your roms settings and clearing the apps cache and data but you probably already tried that?
t83wood said:
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
Click to expand...
Click to collapse
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
DaringDomino3s said:
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
Click to expand...
Click to collapse
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
t83wood said:
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
Click to expand...
Click to collapse
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
DaringDomino3s said:
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
Click to expand...
Click to collapse
Yep looks good!
t83wood said:
Yep looks good!
Click to expand...
Click to collapse
Awesome, thanks, I'll see what happens :good:
Edit: it worked! It's a little more involved than multirom, but it seems to be fine! Easier than I thought.
I've not yet switched between the two, but the app on the secondary (data slot) recognizes the primary
Wow great. Running great on data-slot. Even magisk is supported. Good to have a new playground. Happy to have the 128 GB variant. Gonna do some test with Viper.
How do I switch roms
All perfect. Viper running with magisk. Every rom i tried booting without any problem. So atm the perfect tool to test other rom!
---------- Post added at 11:45 AM ---------- Previous post was at 11:43 AM ----------
DEVILOPS 007 said:
How do I switch roms
Click to expand...
Click to collapse
Install dualpatcher app and choose rom in 'ROMs'. Then reboot. Or run utulities in twrp (install).
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Donric13 said:
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Click to expand...
Click to collapse
Okay thanks Bro, I might try out lineage. Also open gaps failed for me bit do I need the rom first or do I need to use dynamic gaps? I appreciate the help!
DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Donric13 said:
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Click to expand...
Click to collapse
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
DEVILOPS 007 said:
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
Click to expand...
Click to collapse
Did you flash in twrp (3.0.3.0)? I only use twrp to flash a new multiboot rom. Before flashing a new rom just make sure, you patch all necessary zip files (rom, gapps, etc.). Same name means u choose where (on angler i always choose Data slot - this is internal sd card). Then you give the name (no capital letters) and choose the directory to save the patched file. This you do with every zip file for the rom u gonna flash. The new zip file have the original name and the text "....._data-slot-namegiven.zip" (example for data-slot). The part "data-slot-namegiven" should appeir in every name of the patched zip file. I think with our device it's goot to use the data-slot if you have enough space on your internal sd-card. Using Multi Slot could lead to space problems on system partition of the device. Then just flash the patched files one after another in twrp. Don't forget to flash also patched supersu.zip oder magisk.zip to get root (if it's not in the rom included). You need to patch gapps and supersu or magisk for each slot separately. The name of the patched file just says the path for the multiboot rom. So twrp flashes the patched zip to the right place. Sorry if i wrote to much. Hope it's gonna give you some help. More information you find in the original thread of multiboot.
Hi,
I have a T-Mobile S5 and I'd like to get a link to the stock ROM with latest security upgrades so that I can debloat and mod it.
Can anyone point me to some resources on how to debloat and create a custom ROM.
Is it possible to use the international ROM and flash it on the T-Mobile S5?
Thanks
1) Download the ROM
Download from sammobile.com (look for G900T, latest should be ~April 2017)
You'll need to make an account (free), and it's pretty slow, but there isn't really an option.
You might be able to grab the international version, but I haven't tried. I heard it's not compatible with some of the US locked versions, but the T-Mobile and AT&T versions were supposed to be exactly the same so they shouldn't have a problem. Also, it probably won't come with Wifi Calling.
2) Extract zip with `unzip` and then, extract the .tar.md5 with `tar -xf`
3) Download sgs2ext4.zip (google it:
forum.xda-developers.com/attachment.php?attachmentid=645192) and extract it
4) Run `java -jar sgs2ext4.jar system.ext4.img system.img` (and then do the same for cache).
5) Mount both images (`mount -o loop system.img system/` and same for cache).
6) Get `sec_csc.zip` from the cache folder and extract it.
7) Make a copy of the system/ mounted folder, chown it to yourself so that you can easily modify it later on.
8) Merge system/ folder from extracted sec_csc.zip with the system/ folder you created.
9) Copy boot.img and system/ into a new folder, let's call it build/
10) Get a copy of META-INF (update-binary is the important one) and also place it in build/
11) Use the updater-script from here: https://forum.xda-developers.com/tm...pment/odexed-development-starter-kit-t3386186 and delete everything between "Symlinking and Setting Permissions" to show_progress (aka get rid of all of the set_metadatas).
12) Generate appropriate permissions (as described here: https://forum.xda-developers.com/tm...pment/odexed-development-starter-kit-t3386186) and place them right after "Symlinking and Setting Permissions".
13) At this point, you should be able to zip everything up and install on your phone. This is a fresh full ROM with no mods and all the bloat.
14) Delete and don't forget to also remove set_metadatas that correspond to whatever you deleted or else the updater will complain that something might have failed. My old post (again: https://forum.xda-developers.com/tm...pment/odexed-development-starter-kit-t3386186) also describes a couple of simple mods you're likely to make.
Note that if you disable selinux, you might not have to deal with permissions, but I think you have to modify boot.img for that, and I don't know how to do that. (Aside: Almost all ROMs posted not by me on this forum have selinux disabled. EG: if you install them, on every boot, it will say something about kernel not being selinux enforcing.) If you need more advanced modding, you'll need to deodex. I don't know how to do that and have never needed to. You'll have to look somewhere else for guides for that.
You just now flashed a custom rom, then gapps, and when you booted it up, it gave an annoying message "unfortunately setup wizard has stopped" and due to that you are stuck at setting up your android device. This problem is not in your custom rom which you flashed just now(so no need to blame device maintainers or source developers for it ) instead, this problem lies in gapps package itself, But after doing a bit of research I was able to come up with the fix(tbh, this really didn't took too much effort for me ).
There is also an alternative method by @prashantvrm. Find link here
So, what actually I did
The entire root of the problem was that setupwizard.apk, so removing it fixed the issue.
DISCLAIMER
I am not responsible for anything, that happens to you or your device, it was your decision to follow my steps, so you bear all risk for this.
After following my steps setupwizard.apk file will be removed from your system, so you have to set up everything on your device manually(that is adding google accounts, etc).
PREREQUISITE
A gapps package which you are going to flash(ofcourse you need it)
A windows/linux/android/any other os with any file archiver utility installed(such as winrar, 7zip, etc)
a BRAIN.exe(most important)
STEPS
1.1) For OpenGapps
For gapps with android version 5.0 or above
open the gapps zip file
Go to folder named 'Core'
Delete the file named 'setupwizarddefault-all.tar.lz' and 'setupwizardtablet-all.tar.lz'
Now reflash your custom rom with your modified Gapps
Thats it.
For gapps with android version 4.4 or below
Open your gapps zip file
Goto folder named system<priv-app
delete SetupWizard.apk
Now reflash your rom with your modified Gapps
Thats it.
1.2) For NikGapps
open nikgapps zip file
go to folder named packages
Delete PixelSetupWizard.zip PixelSetupWivardOverlay.zip and setupwizard.zip
Now, reflash your rom with your modified Gapps
Thats it.
GAPPS LINK
OpenGapps
NikGapps
Don't forget to press thanks button :good:
Thanks in advance! Hope it will work!
Thanks to rajatraj. Your solution worked like charm! I installed LOS 17.1 and Open Gapps nano on Mi Max Helium but a message - "set up keeps stopping" was constantly popping up on my phone screen. I was frantically searching for a solution to this problem. In fact I was about to uninstall LOS 17.1 due to this problem when I found your post. Amazing!
My sisters phone rebooted itself. After we connect to our wifi that message pops up. We cannot access anything else. The screen turns white. Can't access settings. Can't access notifications, nothing. We've tried every option. Nothing works.
We can't follow your steps...
l0kust said:
My sisters phone rebooted itself. After we connect to our wifi that message pops up. We cannot access anything else. The screen turns white. Can't access settings. Can't access notifications, nothing. We've tried every option. Nothing works.
We can't follow your steps...
Click to expand...
Click to collapse
reflash the rom
rajatraj said:
You just now flashed a custom rom, then gapps, and when you booted it up, it gave an annoying message "unfortunately setup wizard has stopped" and due to that you are stuck at setting up your android device. This problem is not in your custom rom which you flashed just now(so no need to blame device maintainers or source developers for it ) instead, this problem lies in gapps package itself, But after doing a bit of research I was able to come up with the fix(tbh, this really didn't took too much effort for me ).
There is also an alternative method by @prashantvrm. Find link here
So, what actually I did
The entire root of the problem was that setupwizard.apk, so removing it fixed the issue.
DISCLAIMER
I am not responsible for anything, that happens to you or your device, it was your decision to follow my steps, so you bear all risk for this.
After following my steps setupwizard.apk file will be removed from your system, so you have to set up everything on your device manually(that is adding google accounts, etc).
PREREQUISITE
A gapps package which you are going to flash(ofcourse you need it)
A windows/linux/android/any other os with any file archiver utility installed(such as winrar, 7zip, etc)
a BRAIN.exe(most important)
STEPS
1.1) For OpenGapps
For gapps with android version 5.0 or above
open the gapps zip file
Go to folder named 'Core'
Delete the file named 'setupwizarddefault-all.tar.lz' and 'setupwizardtablet-all.tar.lz'
Now reflash your custom rom with your modified Gapps
Thats it.
For gapps with android version 4.4 or below
Open your gapps zip file
Goto folder named system<priv-app
delete SetupWizard.apk
Now reflash your rom with your modified Gapps
Thats it.
1.2) For NikGapps
open nikgapps zip file
go to folder named packages
Delete PixelSetupWizard.zip PixelSetupWivardOverlay.zip and setupwizard.zip
Now, reflash your rom with your modified Gapps
Thats it.
GAPPS LINK
OpenGapps
NikGapps
Don't forget to press thanks button :good:
Click to expand...
Click to collapse
A few years later, but it keeps working!, Thanks
Hi!
I noticed that all change i made in system or vendor build.prop are ignored, or in some other xml files, even if i made a factory reset!
I try to add camera2 API and doesn´t work as example, APN changes to, etc...
The files i add, Change after boot still like stock but if i mount it on twrp it shows the changes i made!
Why?!
After some research i think there is no way to tweak system or vendor.
In some way i think vendor and system are writed in data when is flashed and stay in encriped data partition and when it boot only read data.
I read in some where that images only are use for fast update like dual images something problably the tweak image is not the one in use...
https://source.android.com/devices/tech/ota/ab/
Only customs ROMs will work maube because it have their own boot images and works in a diferent way.
I think it is the end of stock mods... :\
Thanks
Hello i had the same problem in android 10 miui 11.0.3 // you will need to reinstall your stock rom from https://xiaomifirmwareupdater.com/miui/platina/ fastboot rom using mi flash tool
After flash done flash twrp / magisc / install root explorer.
After that you should be able to edit again these files.
Or you can use twrp file manager to edit that .xml files // find a recovery that have the ability to edit those files.