yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Benrap:
I read it. Seems iffy. It involves all sorts of reboots and stuff of the kind, and I'm questioning it's functionality. Plus, somewhere in the middle of the post it becomes unclear which ROM the person means.

I just want to make it clear i got app sharing to work, it's just that it cleared my apps' data.
[Galaxy S 4 i9505 Original Android Development] monkteo:
Congratulation for graduated !

Glad you back !:laugh:
[Galaxy S 4 i9505 Original Android Development] Andycar:
Congratulations! We all missed you here!
[Galaxy S 4 i9505 Original Android Development] takis:
works great on my lg g3 really thank you! [MENTION=4277844]chenxiaolong[/MENTION] congrats as well! All the best!
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
[MENTION=4277844]chenxiaolong[/MENTION] : congratulations !
[Galaxy S 4 i9505 Original Android Development] physwizz:
Congratulations on your graduation Chen!!

Have you made any progress on the backup and restore options from the ap?
[Galaxy S 4 i9505 Original Android Development] chavdar:
[MENTION=427477]chenxi[/MENTION]along: Congratulations! Welcome back. Your plans sound exciting
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Congrats bro!!

The boot menu was a feature I always wanted.. Thanks for implementing it. All the plans look cool. Seems like we are going to have a very good time from now on :)
[Galaxy S 4 i9505 Original Android Development] bomboem:
Need root?
[Galaxy S 4 i9505 Original Android Development] jroq8400:
"Data sharing" is actually pointing your application data to a different "shared" folder. Current data will not be copied to the shared folder so it will look as if you had lost it. I have never tried to backup/restore but you can try it to see if it works.

Here is the process to share Apps a,b,c,... data

1. Boot into ROM A

2. Install Apps a,b,c,.. in ROM A

3. Enable apps sharing in ROM A

4. Select Apps a,b,c,... data sharing in ROM A

5. Reboot into ROM A!!!!!!

6. Setup Apps a,b,c,... (you are now using the shared folders)

If you want to access this data from ROMs B,C,D

7. Repeat steps 1-5 in each ROM

8. When you start Apps a,b,c in ROM B,C,D will be using the same shared folder as each app a,b,c,.. in ROM A.

Hope that helps
[Galaxy S 4 i9505 Original Android Development] Benrap:
Thanks!!!! You helped me understand some things.

So is there a way to copy data for an app from ROM A to the shared data folder? Where is this shared data folder? Can the data be manually moved using root?
[Galaxy S 4 i9505 Original Android Development] timz1313:
GREAT Job

Yeah thanks a lot if I ain't got it figured out it's not as easy as people say it is.... Lmfao.... :D
[Galaxy S 4 i9505 Original Android Development] jroq8400:
I think people have used Titanium backup tool to back up and restore the data but I haven't tried it

Shared data folder is under /raw/data/multiboot/shared or something like that (don't have that phone with me right now)
[Galaxy S 4 i9505 Original Android Development] Benrap:
Thanks! Found it in /data/multiboot/_appsharing/data
[Galaxy S 4 i9505 Original Android Development] YousKoose:
I have two ROMs installed on my Verizon note 4: what happens if I turn my phone off and boot into recovery with TWRP; what ROM will be flashed if I install something how would I choose where to flash or what to wipe, how does dual boot work with custom recovery TWRP?
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Yes titanium backup will restore data in shared folder.
[Galaxy S 4 i9505 Original Android Development] Dnorris55:
You have to patch the zip file first, with the rom location where you want it flashed. Then flash it in twrp.
[Galaxy S 4 i9505 Original Android Development] YousKoose:
Yes but how will twrp know witch rom I want to flash it, when I'm in twrp there is no option to choose the rom.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Please read the OP (first post) before asking any questions. Most of the FAQs are answered there. It helps to reduce reposts.

From the OP:

"Flash a mod or custom kernel for the primary ROM?

Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.

Flash a mod or custom kernel for a non-primary ROM?

Just patch and flash it :)"

You need to patch the zips just as you patch ROMs.
[Galaxy S 4 i9505 Original Android Development] YousKoose:
I still don't understand how that works in recovery when the phone is shut off and in twrp.
[Galaxy S 4 i9505 Original Android Development] Dnorris55:
When you patch the zip file, the destination is hard-coded inside it.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Well, I have bad news regarding the future of dualbooting TouchWiz ROMs:

On the S7 series and presumably, older phones running the official TouchWiz 6.0 update, the device disables access to the TEE (trusted execution environment) if the boot image is not signed by Samsung. Aside from the loss of security features, this would generally not be bad, except for the fact that a kernel compiled with TEE support will no longer boot. It is possible to disable TEE support in the kernel, but this causes random reboots when Android tries to use the TEE, for example, when verifying your fingerprint. That's why there are no custom kernels for the S7 right now.

Why does this impact DualBootPatcher? Well, the patcher needs to modify the ramdisk, which is part of the boot image. That means even if you were originally using the stock, signed boot image, after running the patcher, it will be modified and thus, no longer signed by Samsung. Since the stock kernel has support for TEE, it will no longer boot after being patched. That is why I haven't been able to debug the TouchWiz Marshmallow issues before.

Needless to say, I'm pretty disappointed by this. Knowing this, I probably won't buy the international S7 Edge. This is not much better than my T-Mobile S7 Edge with a locked bootloader.

(Source: http://xdaforums.com/s7-edge/how-to/bounty-custom-kernel-sm-g935f-fd-t3361460)
[Galaxy S 4 i9505 Original Android Development] midi_1996:
That means that all devices starting from S5 updated to MM are pretty much useless now? But I've read that they made CM13 boot on MM bootloader on S5, and it has FP support, is that only affecting the TW6.0 roms or all other roms? (didn't test it but reports say it does boot). Maybe it's affecting S6/S7 and some Note phones?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
If you patch and flash a ROM that uses the stock TW 6.0 kernel and it boot loops right at the Samsung logo, there's a good chance that the device is affected by the issue and no stock kernel will work. Custom kernels (including AOSP-based ROMs) can disable TEE support to allow the device to boot and if I remember correctly, the S5/Note 4's fingerprint implementation can store your fingerprints in both the hardware and a file on the /data partition. I'm assuming if access to the TEE hardware is blocked, it will just fall back to storing the fingerprints in a file, which is probably why CM13 is working with the fingerprint sensor. The S7 (and maybe the S6) doesn't have this option and can only store fingerprints is hardware.
[Galaxy S 4 i9505 Original Android Development] pc boy:
[MENTION=4277844]chenxiaolong[/MENTION]

Having all the awesome work you have done already in mind, is there any way to make the edited kernel or boot image look like signed by Samsung? or even truely signed?!

Though I'm not a developer, but I've seen you guys do alot more:)
[Galaxy S 4 i9505 Original Android Development] Cambapo:
Hi there! Really liked your idea, however, I can't install a second ROM. My variant is E330L, and it says the zip was made for ks01lte, ks01ltektt and ks01lteskt, but my device is ks01ltelgt. Could you please help me out? I really want to install cm 13 withouth losing my stock ROM and features. I still have to figure out how to make the tv antenna work with DVB-T2.
[Galaxy S 4 i9505 Original Android Development] ceanth:
chenxiaolong, would you be supporting any other Galaxy S devices? I am looking for a similar solution for Galaxy S5.
[Galaxy S 4 i9505 Original Android Development] Mussels84:
this works on heaps of samsung devices - dont let the location on the forum fool you.
[Galaxy S 4 i9505 Original Android Development] ceanth:
Sweet!

If I install this on stock Galaxy S4 or S5 and I am booted into secondary rom, if I want to switch back via recovery can I switch back using the stock recovery? So would flashing DualBootPatcherAndroid.zip via stock recovery to get to the ROM switching screen, would that work?
[Galaxy S 4 i9505 Original Android Development] Cambapo:
I think stock recoveries can't install zips. I think you must use TWRP or CWM or whatever recovery you want that can install zips.

---------- Post added at 01:32 PM ---------- Previous post was at 01:03 PM ----------

I think the problem comes when I patch the ROM and asks me to choose a device. Your app just recognises as LTE-A S4 devices lte, ltektt and lteskt and assigns the ROM to those devices. My device is out of the list even though is yet another name for the very same device. Is there a way that you could include my device? Or what can I do to solve this?
[Galaxy S 4 i9505 Original Android Development] midi_1996:
CONFIRMED on S5, I did install SuperSU and then updated ramdisk and I got a bootloop to Recovery (I choose reboot to System, it shows the S5 logo, then reboots then shows "Booting Recovery"). Most probably this is affecting the Note4 too!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That would be the ideal solution :) But it would also allow custom ROMs and kernels on devices with a locked bootloader so you can bet Samsung did everything they could to prevent this.

BTW, that was how the Loki exploit for the Galaxy S4 bootloader worked. It exploited a buffer overflow bug in the bootloader and injected it's own verification code that always return "true" so the device would think that the kernel is indeed signed.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, maybe not. There's a small chance the S5 still may work if it's rebooting to recovery since my dual boot code also triggers a reboot to recovery if an error occurs. Could you flash the GetLogs zip from https://snapshots.noobdev.io/ and grab the log file from /sdcard/logs/? With the logs, I should be able to tell you whether the S5 has the same restrictions as the S7.

If the S5 is affected, then you're probably right about the Note 4 being affected too. I'll know for sure once T-Mobile releases the MM update (if they ever do).
[Galaxy S 4 i9505 Original Android Development] midi_1996:
Here :
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The issue most likely affects the S5 as well :(
[Galaxy S 4 i9505 Original Android Development] takis:
Mate i just wanted to let you know that it works pretty damn good on my lg g3 (d855) keep it up!
[Galaxy S 4 i9505 Original Android Development] pc boy:
?

[MENTION=4277844]chenxiaolong[/MENTION]

If you were in our shoes, would you give up on MM and revert back to LP to have the awesome dualboot feature on S5?

Or you would rather wait for a solution and keep up with MM?
[Galaxy S 4 i9505 Original Android Development] tito480:
[MENTION=4277844]chenxiaolong[/MENTION]

First i have to thank you for the amazing app.

Can you help me with some problem?

Everything is working fine with zenfone 2, I am using cm13 as primary and stock rom, both working. The only problem is when i try to flash the DualBootUtilities with TWRP, i am receiving the following error: updater process ended with error 2.
[Galaxy S 4 i9505 Original Android Development] takis:
Can someone help me with this error?
[Galaxy S 4 i9505 Original Android Development] midi_1996:
Use the GetLogs zip from the snapshot website and upload it here, chen may look into it later.
[Galaxy S 4 i9505 Original Android Development] Cambapo:
Could anybody help me with the E330L version?
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
,My guess would be not enough free space on your internal SD
[Galaxy S 4 i9505 Original Android Development] takis:
Thanks i will try freeing some storage and the logs...

---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------

Okay thanks for the suggestion will try that!
[Galaxy S 4 i9505 Original Android Development] kingknuts:
Hard to help

If you don't put your multiboot.log of your internal storage is very hard to help you.

I actually have the dirty unicorns on my Ext-SD slot.
[Galaxy S 4 i9505 Original Android Development] takis:
A dev i know told my its probably a memory issue and it could be cause i only have 500 mb free
[Galaxy S 4 i9505 Original Android Development] hi_blues:
CONFIRMATION....

Same problem on Note 4. After updating ramdisk I got bootloop to recovery. Only full restore makes ph boot again.
[Galaxy S 4 i9505 Original Android Development] midi_1996:
Just restore the boot.img from Multiboot folder, i kept the original one in case of emergency.
[Galaxy S 4 i9505 Original Android Development] hi_blues:
Well in most cases it does not work. I know it sounds odd but ph keep going to Samsung logo and then back to recovery. I might playing with it for some time now tried almost everything. Most of times only full restore works. Now I m going to try some custom kernel. Let's see[emoji14]

---------- Post added at 08:44 AM ---------- Previous post was at 08:43 AM ----------

Well in most cases it does not work. I know it sounds odd but ph keep going to Samsung logo and then back to recovery. I am playing with it for some time now tried almost everything. Most of times only full restore works. Now I m going to try some custom kernel. Let's see[emoji14]
[Galaxy S 4 i9505 Original Android Development] midi_1996:
Weird! Normally it should work, if anything happened you always need a backup boot.img, save yours using twrp backup menu, you only need that to fix any issue with DBP.
[Galaxy S 4 i9505 Original Android Development] hi_blues:
Quick update. Everything working fine.

I m on stock MM 6.0.1 Samsung Note 4 910F.

MAKE A FULL BACKUP!!!!!!

1. Get Vitamin Karnel and flash it through TWRP

2. Reflash Supersu (i lost root after karnel update)

3. Install newest version of snapshot patcher.

4. Set ramdisk and reboot. Wola

Rest is normal as usual.

Already got 2 roms up and running.[emoji4]
[Galaxy S 4 i9505 Original Android Development] midi_1996:
FP is still working?
[Galaxy S 4 i9505 Original Android Development] hi_blues:
FP????
[Galaxy S 4 i9505 Original Android Development] midi_1996:
FingerPrint ...
[Galaxy S 4 i9505 Original Android Development] hi_blues:
I never used FP before. Anyways I CONFIRM that its working I just checked it.

Thanks[emoji4]
[Galaxy S 4 i9505 Original Android Development] deneimainoob:
Guys, can someone help me with a problem? I installed a modded version of the app to my S3 Neo (GT-I9301I) and now, after installing 2 ROMs and upgrading RAM Disc, I can't install apps or play music from my external SD Card while I can see photos and copy files to my internal storage. Also, when I try to open music files, I get an "I/O Error". Lastly, My external storage now is located to "/>raw>extsd" and not to "/>storage>sdcard1" as it was previously located. Thank you and sorry if my English are bad.
[Galaxy S 4 i9505 Original Android Development] hi_blues:
I am not sure but. Sometimes it does happen. If u are on Android 6.x.x it could be permissions issue.

2nd thing comes to my mind never update ramdisk after adding more roms. Maybe I am wrong but who knows.

Thanks[emoji4]
[Galaxy S 4 i9505 Original Android Development] deneimainoob:
I'm on Resurrection Remix android 5.1.1 as secondary and CM 12.1 android 5.1.1 as primary. I followed the tutorial step by step and the tutorial says to update RAM Disk on 1st and 2nd ROM while booted in the 1st and then 2nd and first while booted in the 2nd.
[Galaxy S 4 i9505 Original Android Development] sronweb:
This is very good for the Note 4 users. It seems that we can still use Dual Boot even after MM update.
[Galaxy S 4 i9505 Original Android Development] dave7802:
Kernel is up and running for the S7 Series

First version of Kernel lost the use of SD Card and Fingerprint.

Both are now working.

SE Linux, Permissive.

Its Echo Rom who have released, They are holding there support page away from XDA.

If you want a link ill PM You, or send the Kernel over.

Happy to help bring support to this device if i can be of assistance in the testing / guinea pig

Here is the MultiBoot.log from my first attempt

(I understand it wont work, as no support has been included, But a starting point)

S7 Ael Kernel*

FEATURES:

- Built from the newest official Samsung Kernel Source Code G935FXXU1APE9

- Built with the incredible SaberMod 5.3 Toolchain

- Newest Linux Base 3.18.34

- Ability to Overclock the "Big Cores" up to 2.7 ghz

- Ability to Overclock the "Little" Cores up to 1.8ghz

- Ability to Underclock the "Big Cores" down to 520 mhz

- Voltage Control for both core clusters

- GPU Voltage Control

- Added the following additional CPU Governors:

Conservative, ondemand, bluactive, dancedance, lionheart, ondemandplus, nightmare, darkness, alucard, conservativex, intelliactive,

bioshock, preservative, barry_allen, wave, interactive_pro, yankactive

- Added the following additional I/O schedulers:

. Tripndroid, vr, sio, sioplus, fifo, deadline

- Added Screen Sleep Functions

(Double Tap 2 Sleep ans Sweep 2 Sleep)

- Added Powersuspend v1.7

- Added LED Fading controls

- USB/Keyboard Mouse Hack (use your phone as a mouse or keyboard to control any other device in which you plug your usb)

You need this app: play.google.com/store/apps/det…hid.keyboard.client&hl=en )

- Enabled DriveDroid Compatibility (you can flash .iso images from your phone to your pc for example)

For all the info you may need: xdaforums.com/showthread.php?t=2196707

- Ported the Motorolla "quickwakeup" driver (pls google it.. i have been publishing kernels for the last 3 years.. i have explained everything a million times)

- Added Dynamic FSync v1.5

- Added "ZenTune" v4 (its enabled by default)

- Reduced wireless wakelock timeout (its tunable via Synapse "Misc")

- Applied Google Services Wakelock fix

- Network speed tweaks

- Enabled Advanced TCP algorithm and a ****load of more congestion algorithms

- Permissive kernel from source

- Ram management enhancements

- Insecure and adb insecure ramdisk

- Used and modified G935FXXU1APE9 ramdisk

- FULL SYNAPSE SUPPORT
[Galaxy S 4 i9505 Original Android Development] takis:
how can i remove everything related to multiboot so that i can start using it from scratch again?
[Galaxy S 4 i9505 Original Android Development] hi_blues:
Simple.

1. First wipe all roms except primary from shapshot patcher interface.

2. Go to app manager find snapshot patcher tap it this will take u to properties. Wipe data and uninstall.

3. Using any root explorer delete these folders

.from internal and external sd card both Multiboot folder

.in /data/data and /data/app look for com.github.chenxiaolong.dualbootpatcher.snapshot or similar and delete

Done start over again [emoji4]

Thanks!
[Galaxy S 4 i9505 Original Android Development] pc boy:
[MENTION=4277844]chenxiaolong[/MENTION]

looks like that the chances are high that the issue with MM BL be fixed soon??

It's so sad that there is no custom kernel for my device g900fd, hope the issue be fixed without need to use custom kernels.
[Galaxy S 4 i9505 Original Android Development] Cambapo:
Hello there. I've been trying to flash the patched ROM through the app and recovery, but it keeps saying that there isn't enough storage even though I have 20 GB of free storage. Could anybody please help me out?
[Galaxy S 4 i9505 Original Android Development] NoFrown:
Oxygen OS 3.0.1

[MENTION=4277844]chenxiaolong[/MENTION] can you maybe help me. I'm on oos 3.0.1 and I'm unable to select zips, it opens them instead. For oos 2.2.1 you added a workaround for third party apps. Is it possible to implement this again for oos 3.0.1, would be awesome!:D
[Galaxy S 4 i9505 Original Android Development] bo_hai:
Please support Galaxy E5. Thanks
[Galaxy S 4 i9505 Original Android Development] 54NJ41:
Help needed

[MENTION=4277844]chenxiaolong[/MENTION] we need help for note 5 users.

Issues:

1.	while flashing the patched zip, get error in recovery saying cant recognize nobleltezt and the zip is for noblelte. I fix it by mbtool.installer.ignore-codename=ture. And installed the rom.

2.	in the secondary rom cant set kernel or do anything give the same error "nobleltezt" it's not recognized. Even the app is not asking for root permission.

I believe the above issues are because for marshmallow we are using nobleltezt TWRP recovery. Is there a fix for the above issues? I have tried adding ro.patcher.device=noblelte to build.prob but didn’t work.

/// Never mind i have fixed it, thanks...
[Galaxy S 4 i9505 Original Android Development] Dang !!!:
What should i do? i have i9500 international s4 variant
[Galaxy S 4 i9505 Original Android Development] El_Wray:
Please port your program on my lg g2 f320 device
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
By providing logs from GetLogs.zip
[Galaxy S 4 i9505 Original Android Development] Cambapo:
It seems you selected the wrong device when you patched the ROM. I9500 devices have a different CPU than I9505, which are the ones named "jlte". You're device is the Exynos variant, not the Qualcomm one, and they're not cross-compatible.
[Galaxy S 4 i9505 Original Android Development] Benrap:
Little question: how do you determine which system to boot? Is it a file? If so, where?

OR just make the option to change the ROM a proper shortcut that you can create from the widgets tab, not one that has to be created via the app.
[Galaxy S 4 i9505 Original Android Development] hi_blues:
Look at internal storage Multiboot folder you will fine some files and folders in there. Each folder is named just as u named your roms. Each folder has a boot.img, this the file help determine which rom too boot. Thanks
[Galaxy S 4 i9505 Original Android Development] Benrap:
What do i look for in these files? Plus what's the encoding for these files? (.img)

Are you sure this is the way? Seems too hard and complex.
[Galaxy S 4 i9505 Original Android Development] 54NJ41:
Let me ask you one thing. Are you asking how to switch roms???
[Galaxy S 4 i9505 Original Android Development] Benrap:
How to manually switch roms
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Open app, go to menu and choose Roms, select Rom you want to switch to, then reboot.
[Galaxy S 4 i9505 Original Android Development] hi_blues:
As mentioned earlier you can switch roms by just tapping on the name in roms tab of app. Manually switching is also possible but its bit complicated for you.
[Galaxy S 4 i9505 Original Android Development] Benrap:
Is there any activity or task or fragment or whatever I can launch to get the ROM I want to boot in? I know you can add to home screen, but how do i make it automated with tasker or automate?
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
No, that's not what I meant. I can't port it. I ain't no dev. Chen does the porting. I meant these were files needed.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Coming soon :) This is not TWRP (though it's based on TWRP's graphics code). It's a boot menu to allow choosing ROMs when the device boots up.

EDIT: The primary reason I started working on this is actually to support encryption. With new devices shipping with mandatory encryption, this is something that will have to be supported sooner or later. To input the pattern, PIN, or password, a graphical interface and touchscreen support is required, so why not use TWRP's graphics code?
[Galaxy S 4 i9505 Original Android Development] JoshDaWhite:
That 's really cool ;)
[Galaxy S 4 i9505 Original Android Development] bnwg:
I would like to know if either "set kernel" or "update ramdisk" (or both) will flag the knox trap.

I know this may be newbie question or question that most of the people might not care too much but still I hope someone could guide me to the answer.