yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Bigmar75:
I used and loved this on my note 3. Thank you for your work. Is it possible to add support for sprint note 5?
[Galaxy S 4 i9505 Original Android Development] cruor.am:
Yes I have system, data and cache partions formatted in f2fs. But I don't think my system partition is corrupted, my phone works flawlessly. I have no idea.[emoji13]
[Galaxy S 4 i9505 Original Android Development] MatrixDJ96:
Hlte android 4.4.2 stock as primary after patching kernel the phone stucks in samsung galaxy galaxy note 3 logo

Here logs:

- https://drive.google.com/file/d/0B2ftBoBlBHTINjV6YkFfc2J0dnc/view?usp=docslist_api
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Added support in 8.0.0.r1735.gf3712a2 :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
To be honest, I have no idea if it works with Android M right now. I gave my Nexus 5 to my brother and the Nexus 7 doesn't have a preview build, so I don't have any device to test with :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you send me the boot.img file for the ROM/kernel that won't boot. I think I may have found out why f2fs is causing troubles :) Thanks!
[Galaxy S 4 i9505 Original Android Development] cruor.am:
Yes sure, here the boot.img you need ;) What you've just said sounds very very good :cool: Thank you!!

https://www.dropbox.com/s/nfjb4pv098apxnh/boot.img?dl=0
[Galaxy S 4 i9505 Original Android Development] todivefor:
Thank you. Ran for sometime on my S4. Running now on my S6 (not much action there). Now I have the need on my Nexus 7. Thank you.
[Galaxy S 4 i9505 Original Android Development] cantenna:
Sorry to ask again, does anyone know if it's possible yet to only selectivity share apps amongst different versions of Android? Sharing all works, selective does not. 5.0.1 tw as base, CM 5.1.1 as secondary
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Aha! Here we go. The ROM supports F2FS for /data and /cache only. If you look carefully at the fstab file below, /system only has an entry for ext4, not f2fs. I looked at the links you sent me a while back (http://xdaforums.com/showpost.php?p=62816014&postcount=7009) and only Temasek's ROM has the proper f2fs entry for /system. Maybe time to make a feature request for the ROMs ;)

# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.

#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,noauto_da_alloc,errors=panic wait,check,encryptable=footer,length=-16384
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs noatime,nodiratime,background_gc=on,nodiscard,nosuid,nodev wait,check,encryptable=footer,length=-16384
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,noauto_da_alloc,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs noatime,nodiratime,background_gc=on,nodiscard,nosuid,nodev wait,check

# VOLD
/devices/msm_sdcc.3/mmc_host/mmc2* auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/xhci-hcd* auto auto defaults voldmanaged=usbdisk:auto
[Galaxy S 4 i9505 Original Android Development] cruor.am:
Ah I see! You're great! So I think it is my bad, I was sure Rom had full support for f2fs [emoji28] Now it is clear. I have to thank you for all the time spent with this problem! As soon as I can I'm gonna try to flash Temasek's Rom and tell you if it boots successfully! But I'm sure it will[emoji6] Thanks again [MENTION=4277844]chenxiaolong[/MENTION]!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I ran into the same 30 second delay as well (on multi-slot-1). Looking at the kernel log, this is what happened for me. It looks like CM is hanging for 15 seconds after mounting /efs. I'm not sure why. Did you notice if any other ROMs do this?

I've made a change in 8.0.0.r1740.g99d2f21 that should shorten the amount of time for the "Waiting for hardware scanning process to stop" step, but that's pretty minor compared to CM's 15 second delay.

| Time range | Description |
|-----------------|-------------------------------------------------------------------|
| 0.00s - 8.27s | Kernel and hardware initialization |
| 8.27s - 8.54s | [Multiboot] Initialization |
| 8.54s - 8.89s | [Multiboot] Initialized internal storage and external SD hardware |
| 8.89s - 8.94s | [Multiboot] Mounted partitions |
| 8.94s - 10.80s | [Multiboot] Performed exFAT check/repair on external SD |
| 10.80s - 10.84s | [Multiboot] Mounted exFAT external SD |
| 10.84s - 11.01s | [Multiboot] Patched SELinux policy |
| 11.01s - 17.21s | [Multiboot] Waiting for hardware scanning process to stop |
| 17.21s - 17.23s | [Multiboot] Cleaned up all multiboot files and processes |
| 17.23s - ... | Completely passed control to Android |
| ... - ... | ... |
| 18.14s - 33.08s | Android appears to hang for 15 seconds after mounting /efs |

To answer your question about wiping, as long as the following directories are deleted, there will be nothing left over:

/system/multiboot

/cache/multiboot

/data/multiboot

/sdcard/MultiBoot and /sdcard/MultiBoot.log

[External SD path]/multiboot
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Hey [MENTION=4277844]chenxiaolong[/MENTION] S6 Edge user here. Just wondering if the primary rom uses certain GPU drivers and a certain kernel would I be able to flash a different rom in the data slot with normal drivers and whatever kernel I want?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, I don't think there should be any issues with a setup like that :)
[Galaxy S 4 i9505 Original Android Development] cruor.am:
Hi [MENTION=4277844]chenxiaolong[/MENTION]! I've just flashed Temasek's ROM and multiboot works flawlessly. Thank you again! Great work![emoji41]
[Galaxy S 4 i9505 Original Android Development] ungarsunefille:
Ks01lte (s4 lte a)

Hi chenxiaolong and everybody,

I have two questions : why ks01lte is not in the list ?

Since version 435, all patched file for s4 failed to flash because is not a jflte (or same)

.

How can i add ks01lte to jflte compatibility list please? Because i have already flashed roms with s4 option on 435 and all is ok...or can you add the ks01lte in a new nighly ?

435 doesn't flashed the lasted roms (5.0 and 5.1).

It's a very good app and very hard job. Thanks you so much !

(sorry for my bad english)
[Galaxy S 4 i9505 Original Android Development] physwizz:
I have 2 ROMs on extsd.

Where are the apps stored?

I can only see system.IMG in each of directories on the external SD card.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done! 8.0.0.r1746.gabddfb4 should support ks01lte now. If you have a working multiboot setup with 8.0.0.r435.g144794c, you will need to wipe and start over. There has been a massive amount of not-backwards-compatible changes since that version.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Data is always stored on the /data partition regardless of where you install the ROM. You can find the files in /data/multiboot.
[Galaxy S 4 i9505 Original Android Development] physwizz:
Thanks.

My ES File Explorer shows /data as empty!!!

Edit: with root access I can see folders but not Multiboot.

Edit2: found it at /raw/data/multiboot
[Galaxy S 4 i9505 Original Android Development] ungarsunefille:
AMAZING !

It's fast ! Thank you ! !
[Galaxy S 4 i9505 Original Android Development] sronweb:
[MENTION=3145598]rlorange[/MENTION] As you have used this thread to follow up your back up tool, please do you know if it's currently compatible with the dual boot patcher?. Today I have tried to back up multi slot 1 but it says that I don't have any rom on this location but I have CM12.1. I'd like to use it if possible to restore the rom in case of troubles. Thank you
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Can someone please tell me what to add to my build.prop to have the patcher recognize it as another device? Thanks a bunch!!!

---------- Post added at 04:43 AM ---------- Previous post was at 04:41 AM ----------

By the way the dualboot of a Note 5 port with crazy awesome GPU drivers ;) [MENTION=4898097]arter97[/MENTION] and xtresolite 2.3 and [MENTION=4517211]Xileforce[/MENTION] latest beta kernel. Loving this. I am using the Latest patcher.
[Galaxy S 4 i9505 Original Android Development] mismamente:
(Version I'm using: 8.0.0.r1741)

I have an S4 i9505 (Snapdragon variant). I have a 64gb SD with two partitions: 48gb fat32, 16gb ext4

My primary rom is Imperium v10 http://xdaforums.com/galaxy-s4/i9505-develop/kernel-imperium-ll-kernel-v1-0-t3058867 with the kernel shipped with that rom.

I'm trying to install the same rom as a extSD slot, but doesn't work. As the rom has Aroma installer, I must install the patched version from TWRP. When the rom is patched, after the reboot the phone boots into TWRP again. If I switch and boot to Primary rom, the DualBoot utility doesn't show my secondary rom installed.

The DualBootUtilities from Recovery shows the following behavior (when flashed a secondary rom to extsd) :

- Primary Imperium, flashed other rom (not Imperium) from Dualboot apk. The secondary doesn't appear in dual boot utilities, but boots fine.

- Primary Imperium, flashed Imperium as secondary from recovery (using patched file). The secondary appears in dual boot utilities, but doesn't boot the secondary, it reboots to Recovery.

I have tried also to patch the kernel http://xdaforums.com/galaxy-s4/i9505-develop/kernel-imperium-ll-kernel-v1-0-t3058867, but then phone stay on the first logo from samsung.

So, I don't know if I'm doing something wrong, or my configuration is wrong, or there is a bug.

Regards
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
I'm doing dual boot at primary and multislot1. After flashing a new rom (patched) to primary, I found I can't switch to multislot1 any more, instead, the phone boot to recovery. How am I supposed to fix this? Thanks.

Update: Nevermind, refreshing the kernel on multislot1 fixed it.
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
I tried flashing a tw rom as 2nd but it didn't boot, it got back to recovery, so I tried flashing a custom kernel for it, still no luck. Primary works fine
[Galaxy S 4 i9505 Original Android Development] rajkumar3192:
cant flash

i tried ti flash my secondary rom zip files but command prompt says pls help me seniors
[Galaxy S 4 i9505 Original Android Development] george stamatos:
Try flash aicp in multi slot 1
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
ro.patcher.device=zerolte

(The correct value should be automatically added to /default.prop for ROMs patched with 8.0.0.r1506.gacad6f0 or newer. If not, let me know.)

:highfive::D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, it sound like there are two bugs.

For the auto-reboot into recovery (Imperium), it means the multiboot code was unable mount either the SD card or the system image on the SD card. It purposely reboots into recovery to give you a chance to fix things. If you wouldn't mind, could you flash the GetLogs zip (https://snapshots.noobdev.io/misc/getlogs/GetLogs-20150919.zip) when it auto-reboots into recovery? It will create a tar file in /sdcard/logs/.

The missing secondary ROM in DualBootUtilities is likely a bug also. Which version of DualBootUtilities are you using? I fixed a similar bug recently.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you grab the logs using https://snapshots.noobdev.io/misc/getlogs/GetLogs-20150919.zip when it auto-reboots into recovery? It will save the logs to a tar file in /sdcard/logs/. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Your ROM is reporting that the device is a Note 4. Are you using a Note 4 port on a Note 3? If so, you'll need to either flash from recovery or add the following to your build.prop:

ro.patcher.device=hlte
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
Will do

(btw, it's this rom: http://xdaforums.com/galaxy-s4/i9505-develop/rom-roll-ultra-light-529-mo-t3198449)

Uploaded as attachment. This must be log #1, this is rom only, I also flashed the kernel after that log (imperium kernel, it's included in that rom), but somehow it didn't cap it.

First see if you can diagnose this log.

Used this version (android) to patch the rom: DualBootPatcherAndroid-8.0.0.r1735.gf3712a2-snapshot
[Galaxy S 4 i9505 Original Android Development] mismamente:
The version of Dualbootutilities is: DualBootUtilities-8.0.0.r1741.g5464cb8.zip

The logs are: https://drive.google.com/file/d/0B0W4-th8xTLQNkNTV0sxNC15TFk/view?usp=sharing

regards
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Are you using F2FS by chance? The ROM you linked to only supports ext4 and I saw in the logs that the kernel could not find an ext4 filesystem on the /cache partition.

<3>[ 3.242340] EXT4-fs (mmcblk0p18): VFS: Can't find ext4 filesystem
<3>[ 3.344970] mbtool: Failed to mount /dev/block/platform/msm_sdcc.1/by-name/cache (ext4) at /raw/cache: Invalid argument
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! At the moment, multiple partitions on the external SD is not supported. (It mounts the first partition it encounters, which completely depends on how C++ stores the elements of an std::unordered_map.) In your case, it happened to mount the ext4 partition, couldn't find the multiboot/extsd-slot-imperium/system.img, and rebooted to recovery.

I don't have time tonight, but I'll try implementing support for multiple partitions in the next couple of days. I'll probably have it try mounting every partition until it finds multiboot/extsd-slot-whatever/system.img instead of hardcoding, eg. the first partition.

EDIT: By the way, how does Android and the recovery behave when you have multiple partitions? Does it mount the first one? A random one? Would it be better for me to imitate their behavior or go through every partition trying to find system.img (which will be slower)?
[Galaxy S 4 i9505 Original Android Development] mismamente:
Well, Android doesn't mount the second partition, only mounts with link2sd app.

Recovery (with TWRP and with PhilzTouch) doesn't mount the second partition (the second small partition ext4 formatted).

I'm about to delete the second partition so I can try Imperium Rom TW in extsd. By the way, the only reason I have created the secondary partition was link2sd, but I'm not using it at this moment.

I will report if it works fine with only one partition.

EDIT: With only one partition (Fat32), it's working fine. I have now Imperium tw rom and primary AND also as secondary :) Now I can wipe my primary to install MIU v7 :)

Regards
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
Yes I do, I use F2FS for Cache and Data.

I'm looking for a rom that can boot (F2FS) and where sound mods work (like eΧtremeBeats)
[Galaxy S 4 i9505 Original Android Development] midi_1996:
Is it me or builds since 23/9 have Setting menu broken (get FC)?

I rolled back to 21/9

Cm12.1 on S5 Klte
[Galaxy S 4 i9505 Original Android Development] MRDOCA:
Hey so I have a s5. Is it possible to run a unrooted stock rom and a rooted custom rom (alliance) or no?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Should be fixed in 8.0.0.r1754.g757ff21
[Galaxy S 4 i9505 Original Android Development] rajkumar3192:
again some error

sir i inserted the code in build .prop but does not work . i am using note 3 sm n900k and using dark lord rom. i send you all the pic sir. i tried again and took the screen shot of recent terminals after inserting the code in build .prop
[Galaxy S 4 i9505 Original Android Development] omnifarious:
I tried to install slim LP beta 0.6 for d2vzw on multi-slot-1 patched with latest snapshot and the device isn't being recognized. I've attached the log. Thanks so much for all your work.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! It turned out to be a bug. This should hopefully be fixed in 8.0.0.r1756.g4c0b029
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! I don't think I've ever seen a recovery that doesn't set "ro.product.device=blah" in /default.prop. Anyway, this should be fixed in 8.0.0.r1757.g4faaae6.
[Galaxy S 4 i9505 Original Android Development] kotzir:
[MENTION=4277844]chenxiaolong[/MENTION] since version 8.0.0.r1728.gf31d8aa, I get freezes, random reboots and continuous vibration on my Galaxy Ace 3 LTE. As a result I am stuck on version 8.0.0.r1727.g63a9023. Logs attached
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
Just bought myself a shamu to play with, thank you chenxiaolong!
[Galaxy S 4 i9505 Original Android Development] xdasree:
How to make it work on Note 10.1 2014 edition (SM-P600 or codename lt03wifi) .?

Thank You.
[Galaxy S 4 i9505 Original Android Development] royredman:
hey [MENTION=4277844]chenxiaolong[/MENTION] , on the nexus 6, I cannot update the ramdisk properly. When I click to update it, it says it worked sucessfully, then when I reboot, it sticks on the google startup logo, then goes to TWRP recovery. When I reboot from there, it just bootloops to the twrp recovery again. I was using Pure Nexus 5.1.1 and was using hells-core kernal. They are both unencrypted
[Galaxy S 4 i9505 Original Android Development] monkteo:
Hi, question;

I have r1607 version (and work perfect in my configuration)

primary - TW

data-slot1 - CM 12.1

data-slot2 - MIUI 7

If I want to update to r1757 version it's mandatory to erase old version from phone, or how ?

I whant to test installation on sd-card and to free some space on my phone!

THX
[Galaxy S 4 i9505 Original Android Development] mbonus:
Thanks [MENTION=4277844]chenxiaolong[/MENTION] Being able to dual boot Note 4 is the coolest thing since sliced bread. Your patcher is extremely user friendly, as even I was able use it without issue! :good:
[Galaxy S 4 i9505 Original Android Development] todivefor:
Just install the latest apk over top.
[Galaxy S 4 i9505 Original Android Development] carandcar:
What ROM are you running for your primary?

Is it a 5.1.1?
[Galaxy S 4 i9505 Original Android Development] mbonus:
Slimremix4.7(trltetmo-aosp base) primary, rapture8.0 dual.

Both are 5.1.1
[Galaxy S 4 i9505 Original Android Development] carandcar:
Ok. Thanks

For some reason I can't get past the splash screen on the 5.1.1 TW I'm running as my primary. I haven't had any issues until now. It happens when I update the ram disk and reboot. I'll try Slim as my primary and see what happens.
[Galaxy S 4 i9505 Original Android Development] mbonus:
First boot on the tw ROM took like 20 min
[Galaxy S 4 i9505 Original Android Development] carandcar:
This time around it never made it to the boot screen lol.
[Galaxy S 4 i9505 Original Android Development] mbonus:
Bummer, what are your steps to flashing? I started with stable slim remix, installed patcher app, patched slim remix rom and gapps, patched rapture tw ROM, flashed within the app, selected the tw ROM and rebooted through the patcher app. Once I loaded the tw ROM, I then installed the patcher app, and updated the ramdisk.
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
You could always just install your primary for nor now, set kernel. If at some point you decide to update or change your primary, then patch and replace/upgrade primary.
[Galaxy S 4 i9505 Original Android Development] carandcar:
I'm fairly convinced it's the version of the ROM I'm running. I have not had any issues with dual boot up to this point. I've been running TW as my primary and aosp as dual for months. I'm going to switch it and see what happens. Thanks for your help.

---------- Post added at 02:01 AM ---------- Previous post was at 02:00 AM ----------

That's a good idea. Thank you.
[Galaxy S 4 i9505 Original Android Development] carandcar:
Man, it's tough getting old!

I forgot to set the kernel! [MENTION=2859974]mbonus[/MENTION] and JhoonB51 thanks for your suggestions, and don't laugh at me. ?
[Galaxy S 4 i9505 Original Android Development] royredman:
Well [MENTION=4277844]chenxiaolong[/MENTION] , I tried installing a second rom (to dualboot) onto the Nexus 6 (both through installing in twrp and trying to install it through the app) and when I tried rebooting into the second rom, I bootloop until I get directed to twrp, then after I reboot, it loops again without loading the Rom. So you know, I was using Dirty Unicorns 5.1.1 with hells-core kernel. It should all be unencrypted. Thanks for you help with this and the update ramdisk issue!!

also, when I delete everything (from the 2nd rom in dualboot utillities), it says that the ROM ID dual is not installed. I don't know if that is useful or not. haha
[Galaxy S 4 i9505 Original Android Development] SamuelBegui:
Hey all,

Would it be possible to share bluetooth devices among the two ROMs? Such as the Moto360 or is there a way that allows any Android Wear device connect to the two ROMs without having to factor reset every time?
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=4277844]chenxiaolong[/MENTION]

Some news concerning the 30s boot lag with cm12.1 roms as 2nd or multix rom? I tested 1752 but there's still that issue...
[Galaxy S 4 i9505 Original Android Development] rajkumar3192:
again a great thanks for upgrade

now there is another prob sir . uploaded log also sir
[Galaxy S 4 i9505 Original Android Development] SamuelBegui:
Hey so I own a Moto 360, would it be possible to copy over the bluetooth files so the Moto 360 works on the dual and primary ROMs?
[Galaxy S 4 i9505 Original Android Development] monkteo:
Hi, i try to install BlossPop on ex.sc-card and after patch ( all OK rom and gapps) and flash from app (dualboot)take my directly to recovery interface ,

I have S5 G900F and v1757 dualboot version.

Any idea and help ?

THX
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
Hi all,

I tried to manually copy (to backup) the data partition from a secondary but copying fails. I also tried the backp/restore app made by rlorange but that one fails because it can't install rlbbox which is needed. I'm seeking a way to backup data partitions from secondary roms (system is not needed as flashing roms is easy enough). I tried to search for this but couldn't find a real solution.
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION] said several pages back that he will be working on a backup/restore solution. This will be a tremendous addon to this great product!
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
hi :)

I was aware that this is a future thing to come but i have a problem with my device that needs to be set up from scratch. I was wondering if there was no manual way to do it for now.
[Galaxy S 4 i9505 Original Android Development] todivefor:
You can backup with TWRP or CWM, but this backsup all your roms with no ability to restore individual roms.
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
Hmm, ok. And what exactly gets backed up from extra installed roms? I guess only the data as my rom is on my internal sd?
[Galaxy S 4 i9505 Original Android Development] todivefor:
Sorry, I have not used sdcard support. When not using sdcard support, TWRP would backup everything (all primary and secondary roms). I would say you are correct, everything but what is supported on the sdcard would be backed up.
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
hi, ok.... will invesigate some more. thanks for your time!