yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Eleo:
I am using data sharing for whatsapp and it works perfectly around three ROMs and I get notifications on each of them. But when using data sharing on outlook I dont get notifications on other ROMs, I only get notifications on which I installed the app firstly.
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Since app data sharing support is planned to be dropped, I'm thinking to test the app data directory linking to the other ROM.
[Galaxy S 4 i9505 Original Android Development] farovitus:
How is it working lol i tried it on my s7 and it's not working. What device are you using btw
[Galaxy S 4 i9505 Original Android Development] Eleo:
N9005. Tried only whatsapp and outlook. Both worked. Once you select an app for data sharing, its data is cleared. Then you install same app on the other ROM (you dont need to do this if it is already installed), then go to dbp app and share its data on that ROM, which also clears the app data.

Then you again restart (or go back to previous ROM) and configure the app. Now it works on both sides with same configuration, missed calls/read/unread notifications and etc
[Galaxy S 4 i9505 Original Android Development] jcrompton:
I think I asked this months ago but I'm still looking to see if anyone had made headway on being able to use Magisk, Magisk Hide , and be able to pass SafetyNet on secondary ROMs?

I tried a couple yesterday and no luck

Any new tricks or ideas?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Magisk is already working on dualboot, tried on data slot. Safetynet was updated. Maybe that is why you cant pass it.
[Galaxy S 4 i9505 Original Android Development] webmaster33:
I made a few tests with symlinks.

Created a symlink to the app data of Clipper app in primary rom.

When started Clipper, it crashed.

I looked into logcat, and found, that the user/group id of the data dir & subdirectories of it has 10216 id (id of Clipper in primary rom) instead of 10019 (id of Clipper in current rom).

This is why Clipper gets permission denied when accessing the data dir.

One solution could be, that when changing rom, a boot script should change the ownership of the data directory & subdirectories & files to the id of app in current rom.

This means, that:

- We need to retrieve the user/group id of each shared app in each rom. The ids can be retrieved from packages.xml file.

- On each rom change we need to change user/group owner ids to target rom of each shared app. This can be done in the flashable dbp.zip, when the rom change is done. Also in mbtool, which handles the booting phase.

This way there would be possible to use app sharing with maximum compatibility.

One risk:

- if the ownership is not restored for the target rom & shared apps, then the shared apps will be crashing in the booted rom.

However if it is programmed correctly, I think this case will be not happen.
[Galaxy S 4 i9505 Original Android Development] farovitus:
Thanks for your fast reply. But can you please repeat those steps and note which is the first rom and which is the second ...
[Galaxy S 4 i9505 Original Android Development] jcrompton:
I can get Magisk to work on dual boot ....

But can't and never have been able to get SafetyNet to pass on secondary ROMs. That's what I'm hoping for

Works great on primary ROMs
[Galaxy S 4 i9505 Original Android Development] Eleo:
No first or second ROM. One slot where you configure app, other slots where you take shared data from the slot where it was configured and paste to app. That is it. They can be any slots. You can even share the data from extsd slot 5 to primary slot.

Did you try swapping ROMs? Maybe your secondary ROM is not able to pass by itself? Not because of it is secondary ROM.

You can check by these methods;

1. Backup primary and secondary ROMs. Wipe primary slot and restore secondary ROM into primary slot. Try safetynet.

Or

2. Backup primary and restore it to data slot or extsd slot (depending on available space and try safetynet.

Because maybe your primary ROM can pass by itself no matter of its slot.
[Galaxy S 4 i9505 Original Android Development] jcrompton:
I'll try and report
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
Here's my question and dev's answer, maybe it'll help you out

https://xdaforums.com/showthread.php?t=2447534&p=69223735

https://xdaforums.com/showthread.php?t=2447534&p=69246354
[Galaxy S 4 i9505 Original Android Development] TehMerkMods:
Aroma?

This is the only place I could find that I could imagine getting support for... obviously I'm using a later version of the app but hey does this support aroma installers cause I got a few Roms worth dual Booting but can't seem to start the aroma session...
[Galaxy S 4 i9505 Original Android Development] Eleo:
Yes it does. As long as you use recovery that supports aroma installer, like twrp 2.8.7.0. You cannot flash aroma based ROM from inside app. You have to flash the patched ROM via custom recovery. Aroma installer was built for recoveries.

P.S. Please edit your post and remove whole OP from quote
[Galaxy S 4 i9505 Original Android Development] Eleo:
:good:

Everything correct. You forgot one single detail I told you. Once you enable data sharing the data of app is cleared. So once you have it shared on both ROMs, now you need to configure the whatsapp in either of them. Enter configuration page, enter phone nunber, wait for acceptance and once you finish it, all is done. And after configuring the whatsapp it will be working on both ROMs with same parameters/unread/read notif. and etc;) and you will not need to enter to configuration page after each time switching ROMs.

And the beauty is, if you would need to remove one of the ROMs, as long as other ROM has shared whatsapp, after you share whatsapp data on a newly installed ROM instead of the wiped one, it will be automatically configured and ready to use after one reboot
[Galaxy S 4 i9505 Original Android Development] jcrompton:
Well crap!!

I tried to restore a backup of a ROM that easily passes SafetyNet while in the primary position and it does not pass in any non primary position.

I even did a fresh install of that same ROM in a non primary position and it won't pass.

There must be something about the files being somewhere they aren't supposed to be????

Any other ideas?
[Galaxy S 4 i9505 Original Android Development] farovitus:
Thanks now everything works !

But my only question is what happens now when you want to backup your apps and data on TW using titanium backup
[Galaxy S 4 i9505 Original Android Development] Eleo:
Doesnt matter:

1. Dont backup whatsapp. Install whatsapp from playstore after boot. Restore other apps. Share whatsapp data. Reboot. You will have shared data on whatsapp without needing of configuration.

2. If you restore app, once you share data it will clear the app data again and after reboot it will use the shared data (which also will be more fresh than restored one, since it also includes data added after finishing of app backup on titanium). I advise this, because restoring app on titanium will be faster than opening playstore, finding app, downloading app and installing it. Also on titanium it is done automatically, not manually.

As you see both of them end the same, since once you share app data, it clears app data from that ROM and uses shared data from general data.
[Galaxy S 4 i9505 Original Android Development] mitch_t:
Please, add Redmi Note 3 SE (Kate), it is the same Redmi Note 3 Pro (Kenzo) with the different modem, but all the other hardware is the same. Because of the different codename "Kate" I faced with the problem that leads me to an error.
[Galaxy S 4 i9505 Original Android Development] webmaster33:
No, it doesn't delete app data from the rom, just changes the path to the shared app path.

If you disable app sharing for the app, then you get back the previous data, as the path is changed back.
[Galaxy S 4 i9505 Original Android Development] Eleo:
I know, but the data that was present before sharing is not used anymore after sharing data. That is what I was going for. App's current data is not of interest. And the data that was present is dispatched from app.

I tried to explain as short as possible. Or the explanation could be long and boring.
[Galaxy S 4 i9505 Original Android Development] cd716:
Hi. Can you add suport for Samsung galaxy express 4g (expressltexx) please ?

T i a.
[Galaxy S 4 i9505 Original Android Development] Letrix:
My devices is BLU VIVO 5 and it's similar (same mount points) to Jiayu S3 Plus. It is possible to add support for my device for Dual Boot Patcher?

I tried to flash the ROM but it's says than my device is unsupported.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Get logs, attach to post and patiently wait
[Galaxy S 4 i9505 Original Android Development] Letrix:
Logs
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
Hi,

Hopefully someone knows the answer:

I uninstalled DBP and deleted all folder i could find related to it. After that i wiped both caches and the system partition in twrp and dirty flashed my primary rom. everything is ok except for one things:

whatever i do, there is a folder that keeps comming back after delete and reboot. This folder is /data/multiboot/extsd-slot-XXXX. So everyhting DBP related is gone but still *something* keeps on making this folder again and again. My device works fine but still i would like to have it fully cleaned. (The reason i uninstalled is the lack of space to have many roms)

Anyone?
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
[MENTION=4277844]chenxiaolong[/MENTION]

First time seeing this error. Hopefully this log will be useful. File patched successfully but when trying to flash through app or twrp, got this error.

Thanks.
[Galaxy S 4 i9505 Original Android Development] cd716:
The .zip file was patched for benefit3 ark3 phone. You have to patch it to oneplus2
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
File should be patched for the model it's patched on. I didn't patched it for a different phone, beside I don't it can be done if you follow normal procedure.

By the way patching it again made it work. Strange, I know.

Sent from my "1+2" powered by Official RR 7.x.x

Compiled by myself
[Galaxy S 4 i9505 Original Android Development] jcrompton:
Sorry for a little delay in getting back with you. I was able to do the swaps

A ROM that would pass safetynet as a primary will not pass safety net in any secondary slot whether it is freshly installed or recovered from a backup .

I guess the real question is has anybody out there been able to do this.
[Galaxy S 4 i9505 Original Android Development] BJumperBR:
Hi, guys...

I'm having problems trying to share whatsapp data between MIUI ROMs and other ROMs.

Everytime I enable sharing data for WhatsApp on Dual Boot Patcher, WhatsApp crashes during opening (only occurs for MIUI ROMs).

I tried flashing another MIUI version as Extsd slot and share WhatsApp data but the same crashing on opening happened.

I did the same for LineageOS and Ressurection Remix ROMs as Extsd slots and no erros ocurred after sharing whatsapp data...

Any hints on what could be the problem? System log says something about "can't open sqlite database"...
[Galaxy S 4 i9505 Original Android Development] A_Random_Guy:
Anyone know how to install roms to ext slot from TWRP?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Patch zip to extsd via dbp app and flash in twrp
[Galaxy S 4 i9505 Original Android Development] A_Random_Guy:
It errors out claiming about storage
[Galaxy S 4 i9505 Original Android Development] Eleo:
Screenshot/log of error? Screenshot of dbp/storage page? It basically means you are out of storage.
[Galaxy S 4 i9505 Original Android Development] A_Random_Guy:
Here
[Galaxy S 4 i9505 Original Android Development] Eleo:
Can you share the multiboot.log created?
[Galaxy S 4 i9505 Original Android Development] A_Random_Guy:
https://drive.google.com/file/d/0B0xv8aoodDpMSFgyb2I4OGVtZTg/view?usp=drivesdk
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Try to rename the patched file, remove spaces from it.
[Galaxy S 4 i9505 Original Android Development] A_Random_Guy:
Same error
[Galaxy S 4 i9505 Original Android Development] BJumperBR:
Has anyone tried "App Sharing" on MIUI ROM?

I've tried sharing both WhatsApp and Instagram and after rebooting the apps won't open. They crash and the error message is something related to SQLite db error.
[Galaxy S 4 i9505 Original Android Development] webmaster33:
I checked, but it has no enough information.

Could you make a full log in TWRP?
[Galaxy S 4 i9505 Original Android Development] A_Random_Guy:
How?
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Read this page how to report logs.

https://dbp.noobdev.io/downloads/
[Galaxy S 4 i9505 Original Android Development] A_Random_Guy:
https://drive.google.com/file/d/0B0xv8aoodDpMNWdjQkI1Y2hIemc/view?usp=drivesdk

Log from TWRP. Will upadate this post from the GetLogs file

Multiboot.log from GetLogs

https://drive.google.com/file/d/0B0xv8aoodDpMMFZfY2NmUDVMbFk/view?usp=drivesdk
[Galaxy S 4 i9505 Original Android Development] psihop:
Lenovo Vibe P2a42

Hello! I would like to see in the list - Lenovo Vibe P2a40
[Galaxy S 4 i9505 Original Android Development] Eleo:
Getlogs
[Galaxy S 4 i9505 Original Android Development] AceLine:
Galaxy Note 10.1 codename not recognized

Hi Chenxiaolong,

I'd be so happy if you could add support for Samsung Galaxy Note 10.1 (WIFI, GT-N8010) to Dual Boot Patcher.

I installed recend version (9.1.0.r188.gbc0c2130-), but my codename p4notewifi couldn't be recognized on trying to set kernel.

GT-N8010: p4notewifi

Please send me a short reply if (and when) this codename could be Implemented.

Thank you so much for your great work!

Best regards,

Ingmar

PS: As I know: the codename for GT-N8020 is p4notelte
[Galaxy S 4 i9505 Original Android Development] NitroOxid:
Hi. add please to the configuration file Xiaomi Redmi Note 3 Pro codename Kate. It too device, as well as Xiaomi RedmiNote 3 Pro(codename Kenzo). I established third-party insertions, everything works, everything is good. The only problem - I can't establish MBTool on primary rom. At secondary ROM - everything works.

Kate and Kenzo - identical phones, except for the radio module. Custom roms between them are compatible. I ask to add support. Thanks!

Block device paths - identical Kenzo

Device ID: kate

Codenames: kate

Architecture: arm64-v8a

Logs in attachement
[Galaxy S 4 i9505 Original Android Development] Eleo:
You need to getlogs share in post and wait patiently for new build.
[Galaxy S 4 i9505 Original Android Development] arnelcauilan:
How to flash resurrection remix rom Android 7.1.1 using dual boot patcher I tried many times but not working after flashing its just rebooting back to my twrp recovery..
[Galaxy S 4 i9505 Original Android Development] Eleo:
You are successful when flashing nonpatched ROM but cannot flash patched ROM?
[Galaxy S 4 i9505 Original Android Development] arnelcauilan:
Yes
[Galaxy S 4 i9505 Original Android Development] Eleo:
You will have to provide much much more information. Patched 7.1.1 ROMs have been flashed successfully. It can either be software, hardware or recovery issue on your side.

Phone model, recovery version, dbp compatibility and etc should ve provided.
[Galaxy S 4 i9505 Original Android Development] arnelcauilan:
Sorry, I'm using Samsung Galaxy note 3, i was using the stock rom as my primary rom, im on twrp 2.7.8.0 i tried flash different rom from lollipop to marshmallow any version it was all successful but only when i I tried to flash nougat 711 not working.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Can you please share the logs provided by dualboot patcher upon unsuccessful flash of patched 7.1.1 ROM? It should give the required information.
[Galaxy S 4 i9505 Original Android Development] TehMerkMods:
Here's a log file of failed ext-sd flash

S7 Edge : 6.0.1 [tw]

Rom to flash : Resurrection Remix
[Galaxy S 4 i9505 Original Android Development] Eleo:
It looks like file system error.

I think you need to change file system of your external sdcard. It cannot write system.img more than 4GB, which looks to me as file system error (since you said you uave 15GB free space). If you change file system of external sd card from fat32 to exfat, it will solve yoir issue.

Beware, you will need to format whole sd card for that. Insert your sd card to pc, backup your files to pc, right click to sd card on my computer, select format sd card, on opened window choose file system exfat, choose quick format and click on format. Then restore your files back to sd card and try flashing again and report back please.

That same issue happens if you try to backup ROM to external sdcard which has fat32 file system.

Edit: [MENTION=7028285]TehMerkMods[/MENTION] it should be exfat, not fat32, I edited post
[Galaxy S 4 i9505 Original Android Development] modaifallah:
Awesome... Installed Lineage OS as dual to current touchwiz on S7 Edge... Works perfectly :)
[Galaxy S 4 i9505 Original Android Development] TehMerkMods:
Changed file system to exFat still not letting me. Weird
[Galaxy S 4 i9505 Original Android Development] Eleo:
One thing I can say, it now can form system.img over 4GB. One problem solved. Need to dig it up more to find other issues
[Galaxy S 4 i9505 Original Android Development] TehMerkMods:
Well I'm. Here to help as much as you can XD
[Galaxy S 4 i9505 Original Android Development] TehMerkMods:
After some extensive testing ext-sd Flashes need to be installed via TWRP and in-app Flashes do not work

Tested same rom in Data to test and it installed on ext-sd through TWRP.

Problem solved?
[Galaxy S 4 i9505 Original Android Development] Eleo:
You didnt say anything about in-app flashing:D

If you can flash it, yes it is solved
[Galaxy S 4 i9505 Original Android Development] TehMerkMods:
Yeah just figured I should have mentioned that aye well thanks to your knowledge I should be able to help others with the same issues now:)
[Galaxy S 4 i9505 Original Android Development] farovitus:
So how could we flash a rom on sd ? Mine not working (stuck on splash logo) thankd
[Galaxy S 4 i9505 Original Android Development] Eleo:
Did you share the multiboot log produced?
[Galaxy S 4 i9505 Original Android Development] TehMerkMods:
Once flashed if the rom doesn't boot then I assume something went wrong. Try again also it's handy to have dualboot utilities.zip to get back to your primary rom mate.
[Galaxy S 4 i9505 Original Android Development] farovitus:
On earlier versions of rr it was working just fine....

(Patch rom, flash rom, reboot , now stuck on splash boot s7 edge.... you have to use dbp utilities to select primary rom again to boot again
[Galaxy S 4 i9505 Original Android Development] TehMerkMods:
To force reboot hold volume down and then power if you didn't know that already and yeah I've used the RR had no issues but with ones like superman rom and stuff I can't get it working
[Galaxy S 4 i9505 Original Android Development] farovitus:
You can flash rr on data slot it will work just fine, but flashing it on ext-sd get it stuck on boot....
[Galaxy S 4 i9505 Original Android Development] Eleo:
Logs?
[Galaxy S 4 i9505 Original Android Development] farovitus:
Ok i will do the process again, what do i have to do to get those logs ?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Logs are automatically created after successful/unsuccessful patched zip flash. You see the dialogue of logs created and its location at the very end of flashing.

Are you using recovery or in-app flash?
[Galaxy S 4 i9505 Original Android Development] farovitus:
Im using in app patching and flashing process and both finish successfully. Is there a way to flash in recovery and how ?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Flash same patched zip on recovery:eek: what recovery are you using?
[Galaxy S 4 i9505 Original Android Development] farovitus:
Oh okay i didn t know that lol, i will try that and report ( using twrp )
[Galaxy S 4 i9505 Original Android Development] farovitus:
Tried flashing the patched rom over twrp, but as always stuck on splash screen (usually after couple of moments device reboot or vibrate but now nothing happens except showing that splash scree)
[Galaxy S 4 i9505 Original Android Development] Eleo:
Zip is using aroma installer? But you cant run aroma installer on twrp 3.0.2.4 or via in-app flashing, can you? :eek:

You have to downgrade recovery to twrp 2.8.7.0
[Galaxy S 4 i9505 Original Android Development] farovitus:
I don t think that s the problem, as i said before from a month or month and a half everything was great and i was using 3.0.2-4 twrp .... so it maybe something that was changed in rr rom or dbp updates .... i was hoping that this problem get fixed soon because it take alot of space on internal storage so that kinda sucks
[Galaxy S 4 i9505 Original Android Development] Eleo:
I saw these aroma installer lines. But at the end it says boot image was installed. So I need to read it some other time. It is late right now:silly:
[Galaxy S 4 i9505 Original Android Development] farovitus:
Okay man, np . Good night
[Galaxy S 4 i9505 Original Android Development] TehMerkMods:
I'll test this when I get home aswell. See if I can reproduce this error.

---------- Post added at 11:52 PM ---------- Previous post was at 10:53 PM ----------

As a response haha TWRP 3.0.2.4 is what I use and aroma is perfectly fine :')

---------- Post added at 01:20 AM ---------- Previous post was at 12:52 AM ----------

Does anyone have a working .exe for this (Might save me time on my flashes
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
As an FYI, https://dbp.noobdev.io/ (or any domain at *.noobdev.io) will now auto-ban IPs that generate too much traffic for up to 24 hours. Some people/bots generated 1.6 TB of traffic in the past 12 hours, which is causing my hosting bill to go up.

I highly doubt the new limits will affect anyone, but if it does, please let me know.

EDIT: On another note, only 0.3% of all legitimate downloads come from an IPv6 address. Those lazy ISPs...
[Galaxy S 4 i9505 Original Android Development] farovitus:
Can you please help me figure it out why i am not able to use dualboot option on external sd.... it used to work but not anymore ..... patching and flashing is done perfectly and always succeed but it always stuck on splash boot screen

Using s7 edge tw + rr

(Flashing it on data slot work just fine.... but it reduce my internal storage free space .

Thank you for your work !!
[Galaxy S 4 i9505 Original Android Development] TehMerkMods:
I will try flash the rom to ext-sd now I'll keep you updated pal

Edit: The rom is installing now
[Galaxy S 4 i9505 Original Android Development] TehMerkMods:
Ah yes I managed to replicate your issues. Trying fixes, I am tired and it's 1am can you try something for me and report back.

Patch as data slot and then change location (when asked) to the ext-sd. If you can't do this I'll try in the morning. Night man
[Galaxy S 4 i9505 Original Android Development] farovitus:
Tried it as well not working :/
[Galaxy S 4 i9505 Original Android Development] sn0w89:
hi, when I start windows application on windows 7 x64, it writes my an error about missing file libnettle-6-1.dll, how I can fix it? Thx!
[Galaxy S 4 i9505 Original Android Development] Eleo:
Read here. I think you are better off using mobile app:confused:
[Galaxy S 4 i9505 Original Android Development] sn0w89:
is not always available to do on the phone, so I use old version of patcher under windows, but if win app is dysfunctional, so have to use mobile app, thx!

then why do the upgrade of this app:confused:
[Galaxy S 4 i9505 Original Android Development] TehMerkMods:
Flash from TWRP let me know if superman rom works ^^

---------- Post added at 09:38 AM ---------- Previous post was at 09:37 AM ----------

Well I'm awake now so I've got a free day basically to test :) I'll let you know if I come up with something mate

Edit: I get stuck at S7 Edge screen which I have to force restart my device ^^