yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Wow, a lot has happened since my midterms started :p Once midterms are over, I'll start replying to posts here again (starting from around page 731 when I last posted).

I haven't been doing absolutely nothing over the past couple weeks though! We now have a very basic backup and restore implementation. This is still very much a work-in-progress and currently has no UI (nor does it work outside of recovery mode). But anyway, I figured some people who love bleeding edge stuff will want to give this a try. (And yes, backing up one slot and restoring to another already works!)

Like the installer, DualBootUtilities, and pretty much everything multiboot-related, backup and restore is handled by mbtool. I've compiled debug versions here with the new backup & restore features: https://snapshots.noobdev.io/misc/mbtool/mbtool_recovery_8.0.0.r1855.gfeb767e_DEBUG.tar.xz EDIT: Extract "mbtool_recovery" from the PC zip (easier) or from assets/data-8.0.0-rVERSION.tar.xz in the apk.

To give this a try, you'll want make sure your adb command is set up properly and reboot into recovery. Then you'll need to copy the appropriate mbtool_recovery binary to /tmp/:

# For 32-bit ARM devices
adb push armeabi-v7a/mbtool_recovery /tmp/
# For 64-bit ARM devices
adb push arm64-v8a/mbtool_recovery /tmp/
# For x86/x86_64 Intel devices, you guys probably already know what you're doing

Then, make sure /system is mounted because TWRP does not mount it by default.

adb shell mount /system

Now, to backup a ROM, run, for example (to backup extsd-slot-cm to a backup named "my_backup_name"):

EDIT: One thing to note because the tool doesn't detect this yet. If you want to backup the primary ROM, make sure to do a ramdisk update from the app first. Otherwise, the kernel will not have any multiboot code and won't boot if you decide to restore it to another slot.

adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery backup -r extsd-slot-cm -n my_backup_name

To restore a ROM, run, for example (to restore "my_backup_name" to multi-slot-1):

adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery restore -r multi-slot-1 -n my_backup_name

If you want to do partial backups (say, backing up the data and kernel only), you can add "-t data,boot" to the command. For more command arguments, see:

adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery backup --help
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery restore --help

I expect there to be a lot of bugs, so feel free to blame me or yell at me for whatever issues you run into :)
[Galaxy S 4 i9505 Original Android Development] MatrixDJ96:
I have 32 GB of internal storage where 20gb are free so this isn't the problem
[Galaxy S 4 i9505 Original Android Development] v00d007:
Note:

Hey guy, what do you think is the "thanks" button for??
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
well that's interesting. do you have logs? please receate the steps and use the getlogs.zip in snapshots.noobdev.io post it here. and I will see what I can do. because right now chen is busy.
[Galaxy S 4 i9505 Original Android Development] physwizz:
This sounds great.

I'm looking forward to trying it out.

Good luck in your mid-terms
[Galaxy S 4 i9505 Original Android Development] GioBasi:
ok maybe problem was philz touch , I flashed from dual boot patcher without problem on my another 16gb class 10, with 4gb free space. I haven't formatted anything, patcher created 1.5 gb system.img but apps still installed on internal storage about 200mb.

I was creating 4 partition because I read somewhere , first one need for system , 2end for cache, 3rd for data (all 3 format to ext4) and 4th for apps -format fat32.

now I have 1 problem all apps include system apps, for extsd-slot rom was installed on internal storage. it's ok or ...
[Galaxy S 4 i9505 Original Android Development] xdasree:
[MENTION=4277844]chenxiaolong[/MENTION]

This is on Touchwiz primary ROM. After updating the ramdisk, while rebooting it hangs at the manufacturer logo forever.

Attached the Getlogs tar here.

And also the kernel link here that I'm using.

Thank you!
[Galaxy S 4 i9505 Original Android Development] v00d007:
Well, we'll see if it works. But I really hoped for a solution like the old backup&restore by [MENTION=3145598]rlorange[/MENTION] with which you could do a amora based backup of the dual rom from within the recovery. That's what I'm so long waiting for...
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
if it cause no lag no problem at all. it is not an issue for me. i dont know if the data partition for your multiboot is also created on exts. afaik it will create a data folder on your internal storage only the system.img is created on extsd.

---------- Post added at 10:52 PM ---------- Previous post was at 10:37 PM ----------

did you set your kernel on your primary? just restore your boot.img on your primary and set the kernel again.
[Galaxy S 4 i9505 Original Android Development] GioBasi:
so if I install any app from extsd slot rom like game RR3 with big data, it will be always installed on internal memory, and I can't change install location of data from internal to extsd ?

for me it's one of the main reason why I decide to install rom on extsd-slot to get more free space on internal storage ))
[Galaxy S 4 i9505 Original Android Development] xdasree:
Yes, I did set the kernel on primary. I flashed the boot.img from recovery after ramdisk updated , but it's still hung at manufacture's logo.
[Galaxy S 4 i9505 Original Android Development] gaww:
Good luck with midterms - I expect nothing less then 4.0 on all !
[Galaxy S 4 i9505 Original Android Development] benji667:
whats the best way to wipe a secondary rom to build it fresh
[Galaxy S 4 i9505 Original Android Development] Darkwing_X:
Use the DualbootUtillities flash them in recovery and delete your secondary rom there.
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Using the patcher app go to roms-->click 3-dots upper right corner of the rom (secondary/dual)--> choose "Wipe Rom"--> select all 5 boxes, system, cache, data, dalvik cache & multiboot files. That's it the secondary rom and all files will be gone.
[Galaxy S 4 i9505 Original Android Development] nds850:
I have always selected all boxes and wiped. Does anyone know what 'reset image' does exactly?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
It resets the image of your rom if you have changed the icon from android to something other...sometimes people change the icons for each rom like in screenshot attached.....
[Galaxy S 4 i9505 Original Android Development] GioBasi:
Need help

help

can't install gapps on extsd-slot and any other zip files. can't from dual boot patcher and from recovery philz touch.
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
tbh I have not really explored all of dual boot patcher features and functions. I don't know if you can change the storage of the apps especially the /data/data and the apks which can get pretty big. but you can always use Link2sd. atleast you save space because your system.img is on extsd.

maybe it's because you patched the custom kernel for your primary rom. you don't need to patch the updates(rom,kernel,gapps,zip) for the primary rom. just flash it from custom recovery. reboot then set kernel.
[Galaxy S 4 i9505 Original Android Development] physwizz:
I found that this method doesn't give back all the space on the extSD. I always use the dual boot utilities from recovery.

---------- Post added at 05:33 AM ---------- Previous post was at 05:31 AM ----------

You need to patch the Gapps first and flash the patched file from the dual boot patcher app
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
read his Logs. i think he patched the gapps. there was some error. and im not sure if it was because of aroma binary.
[Galaxy S 4 i9505 Original Android Development] GioBasi:
Yes I patched gapps and other zip files. as patched rom . rom installd and booted from extsd without problem. but can't install other patched zip files like gapps, xposed and etc
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
still the same errors you got.

try to install latest busybox on your primary. wipe everything on your seconday extsd. repatched and flash it. if you have nandroid before dualboot patcher you may wanna start from there.
[Galaxy S 4 i9505 Original Android Development] empat:
Dear friends, I am having some troubles dealing with shared apps. I have a note 4 exynos, and was using dual boot for some time, this is a fantastic app! Yesterday I had to do an update, and I installed both the primary and the secondary rom again doing a full wipe. I previously used to share some apps, whatsapp between them. For some reason, this time when I finished the installation process, even with whatsapp checked to be shared on the primary rom, it was impossible to share it on the secondary rom. Also it was impossible to uncheck the app to be shared on the primary rom. Even with the tiny square ticked this way, when returning to the app the configuration was the same.

As I really need to be able to use whatsapp on both roms, the only solution I can think about is to repeat the whole installation process, hoping to set it correctly as it was before...

Hope my description was clear... Do any of you found this problem before? Thanks in advance!
[Galaxy S 4 i9505 Original Android Development] gaww:
Before you start over, a few questions:

1. What version of duelboot app are you using?

2. What version did you use when you were app sharing.

3. Did you install the pass you want to share (I am assuming you are using individual app sharing) on the secondary first before trying to app share (per instructions on that by the app many posts back - search)?

I have found the space saved by app sharing that way does not reduce my memory usage that much. Worse case, you can install them on both ROMs and move much on them to SD.

On newer versions of the duelboot app, I believe the OP was going to drop app sharing (don't know if this has happened yet). I am still app sharing, even after updating, as I always try first dirty flashing with data only,. It works most of the time - so I did not have to reset up app sharing.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Okay guys, the app is working fine for me at last. I have to edit the updater-script of the ROMs which I use as secondary and placed on data-slot. But now there is another problem. It seems I can't flash zips to secondary ROM via recovery. Is there any possibility to do this? Any zip I flashed in my TWRP recovery was installed to the primary rom, but I want to flash to secondary. Dear dev, any chance to implement this feature to the DualBootUtilities zip file? For example, now we can only switch roms and there is an option to wipe them, but it would be great that we're able to flash zips to a specific rom( primary, secondary, data slot, extsd, etc.) I'll be glad to donate to your project if you think this can be done.:)
[Galaxy S 4 i9505 Original Android Development] gaww:
I was not aware you could not flash patched secondary and multi-slot roms with recovery anymore to their respective slots. I am still using an older version of the patcher and have no trouble flashing them to their slots.

I have not used newer versions that flash to extSD yet, so cannot directly comment on your issue.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
EDIT: Patched zip files I wanted to flash to data-slot, flashed within the app and all is working excellent! Great!

Just to clarify, do I have to set the kernel for the rom I'm going to switch on, before I reboot into it? I mean, I'm using the secondary rom and I want to go back to primary - do I have to set the kernel within the app?
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
setting the kernel is one time thing for every roms that you have, unless you reflashed the boot.img of a rom in that case you have to set it again for that rom. luckily the app will detect most of the time, if not all the time, should you need to set the kernel(of course you have to go to the rom tab). set the kernel on the primary once only upon installing the app. then on secondary roms upon firs boot after you install the app. AFAIK the you can only set the kernel inside the app I don't know if you can set it any where.

---------- Post added at 07:46 AM ---------- Previous post was at 07:39 AM ----------

I am using the oct 7 2015 build. and I can flash patched zips using the latest twrp. try to recreate the problems and get the logs. might as well post it here other users might help you what is the problem.
[Galaxy S 4 i9505 Original Android Development] Wongher:
hi [MENTION=4277844]chenxiaolong[/MENTION] , first of all thanks for your great work.

i'm using dual boot on oneplus two.

i know that we dont have to share apps and update ramdisk right now.

i've a problem when i flash a custom kernel on secondaries, i got bootloop, i must to go back to recovery and reflash stock patched rom.

is it somenthing known? am i doing something wrong?
[Galaxy S 4 i9505 Original Android Development] so_ang:
Is it work on Note2 ?
[Galaxy S 4 i9505 Original Android Development] Casual Gamer:
Does anyone know how to fix the bootloop of Resurrection Remix installed in dual?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done! It will be supported in the next release.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It has support for the Qualcomm-based S3 models (the ones with codenames beginning with "d2", like "d2lte").

EDIT: Not true anymore. [MENTION=5382797]corncobman[/MENTION] provided the information necessary to support the i9305 so it should work in the next release :)
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Wow, good to see that more support it's being added, I'm loving unsing this app on my note 3!!

Thanks a millions!!

Can I ask support also for galaxy tab 3 10.1" p5200 3G version,
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
hwp7 will be supported in the next release :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done! m3 (i9305) will be supported in the next release.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you post the logs immediately after the boot failure. The logs you attached seem to indicate that everything is working fine. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It doesn't support the S6 Edge+ yet. If you have a custom recovery, could you flash the GetLogs zip from https://snapshots.noobdev.io? The file it creates in /sdcard/logs/ should be enough for me to add support for the device. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done and done! They will be supported in the next release :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
All three filesystems you tried should work (FAT32, exFAT, and ext4). Maybe there's an incompatibility with the larger card. Do exFAT and ext4 work with your 16GB card?

It may be that it simply takes a longer time to detect the 128GB card. The patcher expects the SD card to be detected and available immediately. I'll have to think a little bit about how to solve this without introducing a delay to wait for the card.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ever since KitKat, 3rd party apps are not allowed to write to the external SD card, which is why you're having issues patching the file (custom ROMs usually remove this restriction). You can remove the restriction with this app https://play.google.com/store/apps/details?id=nextapp.sdfix or patch the file from the internal storage.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That's actually a really great question. To answer the question: it depends. I'll go into some detail here.

DualBootPatcher uses a client-server design, which consists of the app (which is really a dumb interface) and the mbtool daemon (which handles all of the multiboot tasks). mbtool runs under the root user during boot, so it automatically gets root privileges no matter if you're "rooted" (eg. with SuperSU) or not. Therefore, any operation done by mbtool will work on an "unrooted" ROM. This includes switching ROMs and setting the kernel.

The tricky part comes in when you try to update the app. Each version of the app requires a minimum version of mbtool to be running so they can communicate properly. If mbtool is too old, the app automatically kills the old version using root and starts the new one. This is where we'd run into issues on an "unrooted" ROM. The app will fail to launch the new mbtool and show an error message, not allowing to switch the ROM or do anything else. Other features that the mbtool daemon doesn't handle, such as in-app flashing, will also fail to work.

I'm actually very interested in completely removing the dependency on root in the near future though. I have the exact same use case and it would be wonderful to have a separate ROM for all the Maas360 stuff.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
My dad actually has the Galaxy S3 Mini :) Only problem is that he's on a business trip for 2 weeks, so it might be a while before I can add support for it and test it.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Hello sir [MENTION=4277844]chenxiaolong[/MENTION]

Plz if possible help with support for tab 3 10.1 3G gt p5200 model, currently not supported saying device not recognized coz "santos103g" not recognized!!

How can I provide you with with logs attempt help you add support!!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the info! The "Kernel is not SEAndroid enforcing" message is actually not an error and will show up if the kernel is not an unmodified stock kernel in newer bootloaders. The new bootloader may very well have another change that broke dual booting though. When you say it boot loops, at what point does it reboot? (ROM animation? Samsung logo?) Does it automatically reboot into recovery?

Could you flash the GetLogs zip from https://snapshots.noobdev.io and attach the file it creates in /sdcard/logs/?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Always pick the actual device you have (S4), because you may cause a hard brick if you don't. If you're using a ported ROM and it reports a different device, add the following to your build.prop file:

ro.[b]patcher[/b].device=jflte

and reboot. That will tell the patcher that the actual device is jflte.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The link to the kernel 404's for me. But looking at the logs, the kernel ramdisk's fstab file is missing entries for /system, /cache, and /data. I'm not sure why since I can't download the kernel to see, but in any case, this kernel won't be able to work with multiboot unfortunately.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
And that's why the next sentence after your quote was "This is still very much a work-in-progress and currently has no UI" :)

This will eventually be part of DualBootUtilities and will also be integrated in the app.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you send me the log after flashing from recovery? Also can you flash the GetLogs zip from https://snapshots.noobdev.io and send me the file it creates in /sdcard/logs/?

This is the issue:

[E] Failed to set up loop device /dev/block/loop45: No such file or directory

but I can't imagine why it would need the 45th loop device unless you have 45 apps moved to the external SD.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Right after a boot loop occurs, can you flash the GetLogs zip from https://snapshots.noobdev.io and send me the file it creates in /sdcard/logs/?

Also, there's no need to reflash your entire primary ROM. If you use TWRP, you can go to Install -> Images (button in bottom right) -> and flash /sdcard/MultiBoot/primary/boot.img.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Please flash the GetLogs zip from https://snapshots.noobdev.io/ and attach the file it creates in /sdcard/logs/. Thanks!
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
[MENTION=4277844]chenxiaolong[/MENTION] tried flashing the getlogs.zip file and it gives me this error, I'm using x86 arch tablet!

---------- Post added at 07:57 AM ---------- Previous post was at 07:47 AM ----------

[/COLOR [MENTION=4277844]chenxiaolong[/MENTION] TRWP managed to create this logfile after failing install the getlogs.zip!

Thanks again for your time!!

Here's link to the file!!

https://www.dropbox.com/s/t2w0pmqif5elp22/recovery.log?dl=0
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
well that was weird. cause chen need the logs to debug or add support to your device.

edit: tried to flash the getlog and was successful. but the logs were not found in sdcard/logs/ but in /data/media/0/logs/. is it normar or weird? [MENTION=4277844]chenxiaolong[/MENTION]
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
https://www.dropbox.com/s/t2w0pmqif5elp22/recovery.log?dl=0
[Galaxy S 4 i9505 Original Android Development] Wongher:
I got this 2 log took with syslog, dont know if they are helpful.

Today i try to flash a kernel and give you the log.

I dont reflash the primary but the patched secondary and everithing works fine.

Because the problemi is on secondaries.

When i flash a custom kernel on primary no problem.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
[MENTION=4277844]chenxiaolong[/MENTION] hoping that the log file generated would be enaf to add support for the santos103g , galaxy tab 3 10.1

https://www.dropbox.com/s/t2w0pmqif5elp22/recovery.log?dl=0
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
your logs says

that causes your error. just search about it.

upon searching for quick good some suggested that you need to get an updated bootloader.

You can do a search for an updated bootloader by searching for your specific device on Google

I don't see you flashing custom kernel in your multiboot logs. I can only see you are trying to patch incompatible gapps.
[Galaxy S 4 i9505 Original Android Development] Wongher:
OK i post you wrong log.

I flashed getlog zip in the primary, right?

Or i have to patch it too, andò flash on secondarie.

Then ill give u the correct log.

Many many thanks
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
you can flash it in your recovery. I think you also use twrp. no need to patch. it will create a log file in your sdcard/logs/.

btw you have to recreate the problem before flashing the logs so we can see what is wrong.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
[MENTION=5322723]crazyraiga[/MENTION] hey mate,I'm having trouble figuring this out, I'm on latest TRWP for my tab3, I'm currently on AOSP Marshmallow and I'm having latest bootloader and modem!

Arch x86,the that getlogs.zip file doesn't work for me, my device(santos103g) is obviously not supported yet, so what diagnostic error is this log suppose to contain coz I won't have any patched zip file to install matching my hardware?
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
it is probably your device is not supported. because the getlog.zip has no binaries for x86. right now we will just wait for the dev. he had just had his midterms. he is developing the back.up feature of dual boot utilities. and he is probably resting.

just read the logs you posted and try to pick up the errors. if it is twrp related Look it up. if it is dualboot related we just have to wait.
[Galaxy S 4 i9505 Original Android Development] xdasree:
updated kernel link here in case if you want to double check.

Thank you again
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
I'm not using RR anymore, so I can't, sorry.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Hello, asking support for CM 13, file failed to install during flash!! Log attached

https://www.dropbox.com/s/an59bwflld4pby4/20151102.055808.tar?dl=0