yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] rlorange:
Yep Here:

http://xdaforums.com/showthread.php?t=2491299

[APP][DUAL-BOOT][31/10] Dual Boot backup & Restore V1.0d
[Galaxy S 4 i9505 Original Android Development] royredman:
HEy, thanks for the thread!! I am a verizon Galaxy S4 user. I was wondering how I would be able to remove this if I wanted to be back at a single booting rom again?

Also, I plan on using Verizon GS4 Hyperdrive Rom (primary) and Verizon Google Play edition (secondary). So I am required to only patch the secondary rom and not the primary rom, correct?
[Galaxy S 4 i9505 Original Android Development] gaww:
You only patch the secondary ROM.

You could restore a nandriod and you are back in single boot. There is a zip to disable duel boot, but don't think you need to use it (not really sure what it is for).
[Galaxy S 4 i9505 Original Android Development] jova33:
if you wipe everything from recovery and do a clean flash you should be back to single ROM again.

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] toxicpaulution:
Can you please update the foxhound rom? thanks :3
[Galaxy S 4 i9505 Original Android Development] royredman:
Is there any way we can put all the secondary roms info onto an SD card so we don't have to remove bloat ware on our primary touch wiz ROM?

Also, is there a way that the apps from the primary ROM can be synced to the apps on the secondary ROM (very similar to the mo. da. Co. App for the GS4)

(I want all apps synced, not just free apps)
[Galaxy S 4 i9505 Original Android Development] rlorange:
This would be possible if you made an ext4 partition on your extSD card and then simlinked via init.d script
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Anyways you could support Vanir AOSP for S4?

http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/jfltevzw/
[Galaxy S 4 i9505 Original Android Development] DreenHotdog:
Hey everyone with requests to support ROMs, it'd be great if you could read the "how do I manually patch a ROM" section and do it yourself. The developer of the dual boot, chenxiaolong, is busy developing and creating new updates, and he probably doesn't have time to handle everybody's requests on manual patches. Give the developer some breaks guys.
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Ive tried and have failed horribly :(
[Galaxy S 4 i9505 Original Android Development] jova33:
How do you make a patch info thing? I tried on Windows and Ubuntu, and I get some python error on Ubuntu, but I forget the error I get on Windows 8.

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] Bejda:
Hello all,i'm trying to generate patch for VrTheme zip's (i own a manually patched one that basically works) on windows 7 32bits but get that error:

File "C:\Users\G3\Downloads\DualBootPatcher-2.5.1\DualBootPatcher-2.5.1\useful
\\..\scripts\gendiff.py", line 82
elif re.search(r"\+\+\+ ([^\t]+)(?:\t([^\t]+)(?:\t?)(.*))?", line):
^
SyntaxError: invalid syntax
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
There was a syntax error in the source code. I'm uploading version 2.5.2 right now, which should fix the issue :)
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
chenxiaolong,

Thank you for this great app! I can have several ROMs for different things and do not even have to boot into recovery at all for installing, wiping, removing...
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
You need to update primary ramdisk only if you want to share app data or to restore it with mbtool command line.

---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------

@monkteo : it is not small. System on aosp ROMs is only a few hundred MB
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
https://snapshots.noobdev.io/ and https://jenkins.noobdev.io/ are going down so the server can be patched to fix vulnerability CVE-2016-0728. ETA: 20-30 mins.

EDIT: Fixed
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
There is currently no support for running ROMs from a flash drive connected via USB-OTG. It may be possible make the ROM install, but it will not boot (the multiboot code does not scan for USB devices).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r2157.g7d47ab8 should fix the SELinux issues with data sharing and the reboot option in the nav drawer now safely reboots the device using the Android framework. If the reboot confirmation option is enabled in the settings, then the reboot dialog (same as holding power button) will be shown.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
In this case, only a logcat will help to get the logs. GetLogs.zip won't be able to get anything if ramdisk-update.log does not exist. Updating the ramdisk is equivalent to repatching the same ROM with the latest version of the app. :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The size of all of the partitions depends on the manufacturer. Some devices (like the Note 4) have huge system partitions, while others have tiny partitions (Nexus 5 only has 50MB free on /system). You'll probably want to install to /data (data-slot) or the external SD (extsd-slot) since both your system and cache partitions are small.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I've reported the issue upstream: https://github.com/nmoinvaz/minizip/issues/44 Let's see what the minizip developers have to say about it.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
So, it's not necessary?
[Galaxy S 4 i9505 Original Android Development] george stamatos:
Reboot problem in latest version, can't reboot from app most of times
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] Hi mate. One last issue with our crappy Lenovo updater(K3 Note) as you call it and I fully agree lol!

Using the 2147 build I was still not able to flash a "system.new.dat" rom as it is i.e. without any editing of the updater-script. So I went ahead and I changed this code

assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "bootimg"),
delete("/tmp/boot.img"));

To:

package_extract_file("boot.img", "/dev/block/platform/mtk-msdc.0/by-name/boot"); assert(run_program("/system/bin/dd", "if=/dev/zero", "of=/proc/driver/mtd_writeable", "bs=3", "count=1"));

and then the flash process went fine. I also noticed that without editing the updater-script the patched rom was missing the updater-script file in the corresponding Meta-inf folder, while when I edited it the patched rom contains it.

Can you fix it please. Tell me if you need a full log via GetLogs.zip. :)
[Galaxy S 4 i9505 Original Android Development] gaww:
It would probably better to reboot from outside the app as a general rule.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
I've always been using the in-app reboot functionality and never faced any problems. I can't clarify if there is any issue in the latest build, but I doubt it.
[Galaxy S 4 i9505 Original Android Development] Grid4:
Tried bliss on my zenfone 2 which works blissfully but the app sharing feature when enabled says it needs to update mbtool which i dont know how to on which i need help.

Also,updating ramdisk is not supported by zeny's stock rom i think.
[Galaxy S 4 i9505 Original Android Development] gaww:
The OP recommends rebooting outside of the app occasionally as some items build up in the system if only booted from the app, and rebooting from outside cleans them up. Don't remember the specifics but he noted that a while back.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Nice to know, thanks. :)
[Galaxy S 4 i9505 Original Android Development] mike13ftw:
Hello. Now that the aroma works on note 4 can you fix the utilities zip so that it works on note 4 ?
[Galaxy S 4 i9505 Original Android Development] GioBasi:
Hi [MENTION=4277844]chenxiaolong[/MENTION]

here is screenshots is it ok red ones every time anything anywhere I flashed I see "failed to remount / as ro "
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
I have this red line too, don't worry it's not an error. If I'm not mistaken this appears when you're installing a zip on your extsd. Extsd must remain mounted rw and not ro, that's why you get this. :)
[Galaxy S 4 i9505 Original Android Development] moisha:
What would an alternative (manual ?) way of flashing a new boot.img to a data-slot ? I patched for data-slot kernel.zip and flashed it from TWRP and flash is messing up my primary boot, so I have to restore the primary boot. Thanks !
[Galaxy S 4 i9505 Original Android Development] jp007_uk:
I'm currently using Lollirom as my primary ROM and I can successfully use CM Roms as secondary.

However Albe's Note 5 Astra v2 port fails as Secondary but works as Extsd slot, not sure why but at least it works.

But... Aurora Lollipop S4 Snapdragon v5.2 wont work in both secondary or Ext slot, anyone know why?
[Galaxy S 4 i9505 Original Android Development] george stamatos:
Not even chenxiaolong can answer that without logs. He has the get logs zip for that reason. Try it, he will help you, he always does
[Galaxy S 4 i9505 Original Android Development] jp007_uk:
Thanks, how can I get the

get logs zip

and what's the process to capture the logs?
[Galaxy S 4 i9505 Original Android Development] george stamatos:
It's at download page of patcher, just run it after something fails and post the log file at thread, he will read it and answer to you.
[Galaxy S 4 i9505 Original Android Development] jp007_uk:
So i tried patching as Ext slot and Dual Secondary. On both occasions after i flash in app the ROM it does not show in the ROMs section. So i flashed in recovery and attached is the log. As it failed to boot from recovery and looped back into recovery. Hope this is ok?
[Galaxy S 4 i9505 Original Android Development] george stamatos:
I think is OK , but I flash roms always in recovery and never had problems.
[Galaxy S 4 i9505 Original Android Development] jp007_uk:
I did flash in recovery but it won't boot, it keeps going back into recovery.
[Galaxy S 4 i9505 Original Android Development] george stamatos:
Let's wait for Chen to answer. And I'm using this recovery, the last updated by AntaresOne

https://www.androidfilehost.com/?fid=24052804347849556
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
There is a high possibility that the Albe's Note 5 Astra v2 port is failing to install as secondary, but works when on extsd because you don't have enough space on your system partition for that particular rom. Secondary roms are being installed to the existing /system while extsd-slot roms are creating a separated system.img image.

For the other Aurora rom you mentioned may be you must change something in the updater-script to get it working. All is guessing without logs and a person who understands them.
[Galaxy S 4 i9505 Original Android Development] apna.suresh0305:
Requesting support for Elephone M2
[Galaxy S 4 i9505 Original Android Development] SaschaHa:
Hey. Some months ago I used this app on my Note 4 for TW and CM roms. Now I want to do the same, but it seems that it is not supported anymore. When I try to set the current kernel, it fails ('Failed to set kernel'). Furthermore I can't update ramdisk and my 'ramdisk currently does not have any version of mbtool'. Is there any way to get it to work?

Could that be related to Xposed or Knox / device status or anything else?

It's the greatest app and feature for Android phones, so I hope, there will be a way to use it. Thanks!!
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
To 3 last posters : provide logs generated by flashing getlogs.zip.
[Galaxy S 4 i9505 Original Android Development] jp007_uk:
Log provided in post #8410
[Galaxy S 4 i9505 Original Android Development] axel87:
Hi

Sorry if this has been mentioned before but can I install I third rom as I have 2 roms which are running fine.

I tried putting a third rom on data slot and extsd but it doesn't work.

Any ideas ?

Thanks
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
You can install as many ROMs as your storage permits.. Until you are running out storage.

What error does it display? And as always provide logs. The multiboot.log first. If needed logs from GetLogs.zip too.
[Galaxy S 4 i9505 Original Android Development] monkteo:
Hi, if I want to change my primary rom but to keep the secondary (data-slot) rom on S5, it's ok just to patch the rom (TW) go in recovery and flash ?

My question is ,,what i need to wipe in recovery,, ?

I have PhilZ recovery

THX
[Galaxy S 4 i9505 Original Android Development] gaww:
Use the patcher utility zip and wipe primary ROM items (ROM, caches, etc.) ONLY. If you simply flash new ROM with recovery - it will also take out your secondary. Patch new ROM as primary after cleaning out present primary and them flash the patched ROM and you should be in good shape.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Just a quick update on what I've been up to regarding DualBootPatcher. I haven't had too much time to work on things since the school semester started, but recently, I've been working on a C++ library for sequential and random reading of Android sparse images. For those who have played around with stock images, these are the `system.img` (Nexus fastboot) and `system.img.ext4` (Samsung Odin) image files. The various bootloaders normally perform the "desparsing" operation, but in order to extract the images or flash them from recovery, they have to be processed by a tool, like "simg2img".

So what does this have to do with the patcher? Well, the patcher will be gaining the ability to patch and flash completely unmodified Odin tarballs very soon. The library will allow the patcher to read from the Odin tar.md5, desparse the image files, and write to the patched zip at the same time without using any additional disk space and only using a tiny bit more RAM. This is significantly faster than extracting the tar.md5 -> running simg2img to create another temporary file -> adding to patched zip.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
This will be a very welcomed feature indeed, especially for the x86 arch tab 3, with very few custom ROMs and a good number of "

unmodified Odin tarballs "...Now this installations will be more flexible once the feature it's incorporated!

Just one question, not asking for ETA or anything!

¿Is there a good progress made on the "in app back up feature" of the patcher?

Thank you and all the best with your academics!

New World Order (NWO)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Haha, same story with my Tab S2! Although it's not too bad for me as I usually prefer to use stock ROMs with Xposed.

Thanks!

Any question is a good question, even ETAs :) I have not finished adding backup and restore to the app yet. It needs lots and lots and lots of testing for that feature to be stable (and I really mean that). One good example is backing up a ROM while the currently booted ROM doesn't support SELinux. The backup process might not be able to read the SELinux labels on the backed up files, leading to an (potentially unfixable) unbootable system. The same issue will happen with permissive kernels that don't load an SELinux policy during boot. I've seen quite a few of those around.

Until I can reliably detect which situations will cause unusable backups, this will probably stay as a command line tool. What is worse than finding out your backups don't work, right? :)
[Galaxy S 4 i9505 Original Android Development] monkteo:
THX a lot and sorry if I am so persistent with my question !

So wipe rom (check all box) with utility (in recovery) and flash my new rom patched as primary ?:confused:

Right ?:laugh:

THX and sorry again !
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hey [MENTION=4277844]chenxiaolong[/MENTION] you're back man, we miss you!! :)

I read about the new libraries you're going to implement in the patcher - nice! I just have one may be completely impossible request lol:

Can we have the ability to install a rom fully on extsd without eating space from /data/media (well to be clear the path is actually /data/multiboot) for the data partition?

Now the /system partition is on extsd at the form of system.img, but the /data is always going to internal. Can you bypass this or this is just how Android works? I have a plenty of space on my extsd but I can't install a new rom because I'm running out of internal space. It seems that 4 roms are the limit for devices with 16GB built-in storage or may be 5 if you only have a very few apps installed on primary. Unfortunately that's not my case, because I have a tons of games installed on my primary rom.
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
If I remember well what chenxiaolong wrote, the problem with /data on external is that there are many writes on that partition, and it will kill the external SD quickly, moreover for most devices it is too slow causing huge lags.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Well fair enough. More write cycles on the card will shorten it's lifetime that's for sure. I think you pretty much answered my question.. Just another limitation we have to live with. sad :crying:

The situation can easly change if the current technology make a progress and a faster and more durable cards appear... Nothing about that yet.

Okay I agree that placing the /data path on extsd and the constant read/write operations will kill the card faster. BUT how much faster is that "faster"? 2 months? 6 months, 1 year, 3 years? If it will kill my card in about a year who cares? I can just buy another, they're dirt cheap. Did someone actually tried? And while I agree about the statement above, I can't agree that it will lags on every card and every device. I have 3 roms installed on my Samsung Evo 64gb cl10 and not a single lag. System is on extsd so why it doesn't lag already? Why not just let us to have this as an experimental option in settings? It doesn't hurt. You can use it if you want, but if you don't just don't use it. It's that simple.
[Galaxy S 4 i9505 Original Android Development] gaww:
In the utility, it is normally best to clean all items in the primary partition. I get away with leaving data intact 80% of the time, but wil not recommend it.

By flashing the new patched as primary ROM , it will go back into this partition and not affect your secondary ROM.
[Galaxy S 4 i9505 Original Android Development] ioannis8828:
root secondary rom

hello all...

can you help me how can root secondary rom,i use multiboot ,Primary stock rom and secondary cm-13.0-20160130-NIGHTLY....????:confused::confused:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
[MENTION=3019752]gaww[/MENTION] is right about that :) I gave it a test about a year ago when I first got my Note 4 and managed to kill a $180 USD SD card in a week. The reason having the system image on the SD card doesn't damage it too much is that the image is written sequentially while flashing and that's it. No more data is written while booted in Android. With a data image, data is frequently written, from installing apps to simple SELinux denial logs. An ext4 image makes things worse because for every write, the ext4 journal will be updated in addition to writing the data. (That's why in general, it's not recommended to format the SD card with ext4, NTFS, etc.) Also, not every ROM mounts the data partition with the "noatime" and "nodiratime" options. If those options are not present, then the kernel will write to the SD card every time a file is read so that it can update the "Last Accessed" timestamp for the file.

So while it's not impossible, I don't really have much interest in finishing up the code for it.

EDIT: And creating a 15-20GB data image is slowwwwww. It took about 30 minutes the last time I tried on my Note 4. If you want, you could time it by rebooting into recovery and running:

time make_ext4fs -l 20G /external_sd/data.img

EDIT2: I may eventually add it as an "advanced feature" (i.e. no options in the app for it). If the data image exists, then use it. Otherwise, nobody even knows it's there :)
[Galaxy S 4 i9505 Original Android Development] richyg81:
Installed patcher: okay

Patched secondary rom: okay

Restart to check secondary rom: okay

Restart to primary rom: okay, but with small problem...

Any apps I had installed and "moved to sd card" are now greyed out in nova launcher. Only way to get them back is to restore with tibu, which restores app back to sd card again. Restart to check, but app has gone again.

I restore app again, but this time after completion I move the app back to device storage. Restart to check and presto app is still there.

So, it seems I can't have apps "moved to sd card" while using dual boot patcher, is this true or is there a workaround? Am I doing something wrong here?

Hope someone can help please.
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Would not the secondary cm-13 be already rooted? Have you looked in "Developer options"?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Lol..just...root it d**mit! :D Flash supersu. CM 13 must have a built in Supersu in settings just like CM 12.1

---------- Post added at 20:07 ---------- Previous post was at 19:54 ----------

You fully explained it thanks! Now I've already lost a part of my enthusiasm lol. 1 week is fast, I won't take the risk.

---------- Post added at 20:12 ---------- Previous post was at 20:07 ----------

Not true mate, this is not a problem of the patcher. Most probably it's an issue to this particular rom you're using right now.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hah, you're welcome. :silly:
[Galaxy S 4 i9505 Original Android Development] cogelindo:
Hello, I have trouble sharing applications between roms. I have a note 4 910c with COJ5 5.1.1, and after the "update ramdisk" and make the restart, stays in constant bootloop. I can not enter the recovery (TWRP 2.8.7.0), only the download mode. this has happened with stock odex and CM13.
[Galaxy S 4 i9505 Original Android Development] yeayap:
dual boot kitkat and loolipop or marshmallow

Hello. Primary rom crdroid 5.1.1. I try flash MM as dual and it work good:)

But after flashing kitkat it didn't boot. I try flash cm11 m6 and GE 4.4.4 RC2 as double and as multi slot. I used different formatting f2fs and ext4.

My question Kitkat is support ? :confused: Please tell me which rom is support
[Galaxy S 4 i9505 Original Android Development] shark jungle:
I am on Albe95 note 5 ROM and when i want to set kernel it shows "impossible to set kernel"

Is that because this is ported ROM ?
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
Which kernel are you using? I use the imperium kernel and have no problems setting the kernel for it using n5 port
[Galaxy S 4 i9505 Original Android Development] artaniss11k:
[MENTION=4277844]chenxiaolong[/MENTION]

can you please add support for Galaxy S5 G901F kccat version? i requested this in the "feature request" section about three months ago but i got no answer.

touchwizz roms and aosp ones completes one another and it would be wonderful if you can ad support for this device.

preety please with sugar lumps on top :)
[Galaxy S 4 i9505 Original Android Development] peppe130:
Updated Italian translation
[Galaxy S 4 i9505 Original Android Development] shark jungle:
That's nice, thanks mate

I had aurora kernel so i will flash the Imperuim kernel and try again.
[Galaxy S 4 i9505 Original Android Development] ItzShadowz:
With the LG G4 H815, when flashing resurrection remix ROM (marshmallow) to an extsd slot, I get an error. Here is the log if you are interested (if this error is to do with the patcher and not the ROM itself, I would be very grateful if a fix was put in place):