yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] jean_pulbere:
Any chance to work on S4 GT-I9515 Value edition????

Want to use stock rom + cm11 by sombree .. :(
[Galaxy S 4 i9505 Original Android Development] gigilie:
any options for locked bootloaders?

looks like your App is blowing up again with success from S6 even thats awesome man congrats! I was just wondering if I possibly missed any innovations or developments that would allow those of us on locked bootloaders that require a strictly stock kernel like I545 to use Dual boot or if were still SOL... been trying to skim thru the thread but theres a few hundred pages since I last checked it out and searching didnt come up with any thing positive but still thought I might ask? if not is there possibilities to include support at all? or could implementing parts of safestrap or multisystem be possible to achieve success with locked phones like the hijack etc?
[Galaxy S 4 i9505 Original Android Development] physwizz:
Will this mean we can run more than 2 ROMs on the t700?

Will it also work on external USB ?
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
[MENTION=4277844]chenxiaolong[/MENTION]

After testing different versions of the patcher i have it down to version 1506. From this version on no ROM boots on Oneplus One. Version 1460 works. Zip-files get patched and flashed without problem but bootloop.

I'll attach the multiboot.log from version 1460 (latest working) and 1506.

If you need more infos or files just tell me.

Thank you.
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION], I am trying to flash the new Wanam Xposed beta 3 for S6 (http://xdaforums.com/xposed/unofficial-xposed-samsung-lollipop-t3180960) in primary. I am using patcher r1593 on windows. It patches successfully, but fails on flashing. Looks like it was unable to mount system, cache, and data for some reason. Logs attached. Any ideas?
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
I believe that you don't have enough space in the cache!!
[Galaxy S 4 i9505 Original Android Development] tomaasz:
[MENTION=4277844]chenxiaolong[/MENTION]

I forgot send you link to my recovery. Here is:

https://dl.twrp.me/klte/twrp-2.8.7.0-klte.img.tar.html

thank you very much
[Galaxy S 4 i9505 Original Android Development] todivefor:
That's what I was thinking. I have 2 TW roms, 1 primary and 1 data-slot. I don't know how system, cache, and data are allocated for the data-slot. I wouldn't normally have 2 TW roms, but that's all we got at this time. Probably not going to get around this one?
[Galaxy S 4 i9505 Original Android Development] RuffBuster:
Previously posted this on my device forum:

The link to the kernel thread and file I'm trying to flash:

http://xdaforums.com/showthread.php?p=48453692

https://s.basketbuild.com/filedl/d..._f4k-kk/eur_lte/f4ktion_kk_2.1.0-eur_lte.zip

I can install everything OK except this which works on a standard KK installation but not dual boot?

Thank you.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
extsd-slot support is very, very close to being finished. Just need to ensure in-app flashing works and update DualBootUtilities to allow wiping these ROMs. Both AOSP and TouchWiz ROMs are successfully booting on my Note 4 (trltetmo). I'll do a quick test tomorrow to make sure it's also working on jflte.

In case I haven't mentioned it earlier, ROMs on the external SD do not require a second partition or a specially formatted partition. It works with whatever you have and you can still fully access the card while the OS is booted.

Too bad I only have 2 cats or else each ROM would have a thumbnail :p
[Galaxy S 4 i9505 Original Android Development] chavdar:
Extsd slots - now I finally have to trip knox?

Great work, [MENTION=4277844]chenxiaolong[/MENTION] !
[Galaxy S 4 i9505 Original Android Development] todivefor:
I don't think it is a cache out of space problem. I wiped cache on both roms. Flashed again, and got similar if not the same result. It is failing to mount system and cache. "Invalid argument" or busy. Any ideas?
[Galaxy S 4 i9505 Original Android Development] jean_pulbere:
could you make it work pls on GT-I9515 Value edition with stock rom + cm11 by sombree ???
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Am I right in thinking, having looked at a patched Optimized CM 12 5.1.1. Zip file updater script that the Patcher is now no longer tripping up and formatting Data as well as System?

Just want to be sure before I flash it :)
[Galaxy S 4 i9505 Original Android Development] todivefor:
Looks to me like you should be good to go. It was a similar ststement (in blue) that caused the problem.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
For people who want to use extsd-slots, please vote on this poll: http://www.poll-maker.com/poll393882x940B4541-15

After doing a lot of testing with extsd-slots, I think we need to find a good middle ground between disk usage on the SD card and time it takes to flash a file. Please take a look at the following 3 methods and make a vote :) I personally prefer #3 because of faster flashing and I have a 64GB SD card.

Method 1

(Currently implemented)

This method flashes the zip to a 4GB temporary image on /data, shrinks it to the minimum size, and then copies it to the SD card. The next flash will copy the SD card image to a new 4GB image and repeat the process.

Pros:

Uses the minimum space possible on the SD card. No space is wasted.

Cons:

Takes a really long time to flash files. The copying back and forth between the SD card and the temporary image is slow. (Flashing a kernel can take minutes.)

Method 2

This method installs directly to a 4GB image on the SD card. When the flashing is finished, the image is shrunken to the minimum size. The next flash will enlarge the image to 4GB and repeat the process.

Pros:

Uses the minimum space possible on the SD card. No space is wasted.

Cons:

Also takes a long time to flash files. Enlarging images is very slow filesystems without sparse file support (exFAT, FAT32, etc.).

Easily triggers a kernel bug present on many devices. The uninit_bg bug silently breaks the image when resizing it. It doesn't always happen, but when it does, the system continually FCs and will need a wipe to recover. On jflte, this bug is only fixed in some CM11 and CM12 builds.

Method 3

This method installs directly to a 4GB image on the SD card and keeps it at 4GB. The initial flash will take a while, but all further flashes will be as fast as flashing to the internal storage.

Pros:

Very fast after the first flash. Good for people who flash nightlies.

Cons:

First flash takes a long time because creating a 4GB image is slow on filesystems without sparse file support (exFAT, FAT32, etc.).

Each extsd slot takes 4GB on the external SD
[Galaxy S 4 i9505 Original Android Development] physwizz:
I voted for #3.

I've got a 32 gig SD card.

Any plans to get it working on a otg USB?

I've got a 64 gig USB with 3 partitions - ext4, f2fs and fat32.
[Galaxy S 4 i9505 Original Android Development] sronweb:
Voted. Thanks Chenxiaolong
[Galaxy S 4 i9505 Original Android Development] george stamatos:
Vote on 3. Thanks you are the best!
[Galaxy S 4 i9505 Original Android Development] monkteo:
3 , I think number 3 will be a winer !

THX chen
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
I thought so too but it just keeps booting back to Recovery now I have flashed it :(
[Galaxy S 4 i9505 Original Android Development] leandrop80:
Hi, I voted too for method number 3.

Chan, is it also possible to run Patcher on Nexus 4 ?

My son has one and wants to use it.

Thanks a lot!!
[Galaxy S 4 i9505 Original Android Development] gaww:
Unless I am missing something with respect to your device, it does not have a big enough sized cache for flashing any but the very smallest ROM as a Multi ROM.

However, you have a lot of room in the system partition, so flashing it as a secondary should work.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
There's no way Google would ever let this app go in the Play Store. They recently banned all apps that touch SELinux and while DualBootPatcher doesn't disable it like many of the banned apps, it does modify the policy a little bit to allow dual booting to work.

As far as automatically checking for the latest version, that's a pretty good idea. I'll have to make some changes on my server to support that though. Right now, it just lists every apk in the folder and generates https://snapshots.noobdev.io/. It has no idea what the latest version is :p

Implemented in 8.0.0.r1594.g2bf6495 :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It should be recognized in 8.0.0.r1596.gabdc757 now.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thank you for the support! :D :highfive:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks man! Right now, the patcher does not support methods like Safestrap or Multisystem. It relies heavily on the ability to swap out and modify the kernel on the fly. Workarounds/hacks that patch the kernel, like Loki (jflte) or bump (LG G2), can be added to DualBootPatcher pretty easily though, but I'm not sure if there's anything like that for the I545.
[Galaxy S 4 i9505 Original Android Development] SeraphSephiroth:
Where can I obtain this? I looked at https://snapshots.noobdev.io/ and I didn't see it :3
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
What's the t700?

EDIT: External USB is currently not supported.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for taking the time to track down the last working version!

1506 was the version that introduced the new booting method, so it's not too surprising that it would be broken on the OnePlus One (though a bit disconcerting). When you said that it boot loops, what exactly is it doing? Does it reboot at the OnePlus logo or the ROM's boot animation? Does it automatically reboot into recovery? I only ask that because depending on what happens, it may be a different issue. Thanks!

EDIT: By the way, both logs look good. It flashed fine both times. It's broken probably because I made a stupid mistake in the code that runs during boot.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! It looks like the Xposed update-binary is actually a modified busybox and when it runs the mount commands, it calls itself instead of /sbin/mount. It should be fixed in 8.0.0.r1597.gfc8a858.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It was probably still building. (You can tell if my signature here on XDA has this :)).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the link! This should be fixed in 8.0.0.r1598.g7632a4b. You'll need to repatch the file you want to flash with this new version.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, I'm not seeing anything out of ordinary in that zip file. Could you attach the /sdcard/MultiBoot.log file after it fails to flash?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you flash the attached zip and attach the tar file it saves in /sdcard/logs? That should get me all the info I need to add support for your device
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Starting from 8.0.0.r1599.g88dd15a, it will no longer do that :)
[Galaxy S 4 i9505 Original Android Development] physwizz:
The t700 is Galaxy Tab S 8.4"

Also is there any way to indicate which ROM is running. Perhaps a different colour or a tick?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, that's actually a bug. I've fixed the original issue (changed it to format /system), but the fact that the format.sh line is still there is not good.

EDIT: Fixed in 8.0.0.r1600.gdb94d2f
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
Is there a way that the app know's what roms you have in dataslot when you want to patch a zip? like that you don't have to type the name of the rom for the file you want to patch! Thanks for your hardwork,cheers!!!
[Galaxy S 4 i9505 Original Android Development] -MaD-:
Voted for 3... I think I have to buy a 64 gig SD card.. ? 32 are not enough for these reasons.

Gesendet von meinem SM-N910F mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
At the moment, I don't have any plans to add USB OTG support (at least until extsd-slots become very stable). As far as multiple partitions go, the currently implementation breaks when there are multiple partitions. Instead of mounting the first partition, it mounts the first detected partition, which may or may not be the same.
[Galaxy S 4 i9505 Original Android Development] physwizz:
Thanks for your great work. Looking forward to using ext SD slots.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done :) 8.0.0.r1604.g955c99b
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done! It will list all data-slots and extsd-slots that are currently in use. This feature will be available once I release the new extsd-slot feature :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Dang it. Builds are failing because I forgot to update the SDKs on the build server to API 23 (Marshmallow).
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
Hands down the best!! Thanks man!!!
[Galaxy S 4 i9505 Original Android Development] jean_pulbere:
tar file from sdcard GT-i9515 value edition black

thx in advance for adding support on this model.after you add support pls indicate me what file should i flash for working on my model. i want to use stock rom kk + cm11 by sombree.Thx!
[Galaxy S 4 i9505 Original Android Development] Jamboozlez:
I wrote that on your GitHub repository, but I'll put it here too just in-case! Thanks!
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
Thank you for looking at my problem.

It reboots at the OnePlus logo and it does not reboot into recovery.
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
Hey guys sorry for the dumb question, but is there a way to migrate from secondary to primary?
[Galaxy S 4 i9505 Original Android Development] physwizz:
Thank you
[Galaxy S 4 i9505 Original Android Development] Pannam:
hi,

i have used the update ramdisk function . will this affect in anyway my device performs when i completely uninstall this rom and use a fresh updated stock rom?
[Galaxy S 4 i9505 Original Android Development] murtadha50:
I used dualboot patcher for exynos note 4

Flashed stock rom as primary and CM12 as secondary

Time boot on secondary rom takes very long to startup specially when power on it stuck on Samsung logo for about a minute then boots but if primary is used the starup is normal

Why i encourage the delay if boot cm12 rom as secondary?
[Galaxy S 4 i9505 Original Android Development] Andycar:
Dear [MENTION=4277844]chenxiaolong[/MENTION], would it make sense to suggest to make it possible to put. img file for extSCard on the ext4 filesystem? Can it be beneficial for speed or something else?
[Galaxy S 4 i9505 Original Android Development] nds850:
In older versions there was an option to remove device check when patching a file. I can no longer find that option, is it still there somewhere?
[Galaxy S 4 i9505 Original Android Development] ROBSONMEG:
to update secoundry rom I patch it then do I flash it via recovery while in primary rom or do I need to switch to secoundry rom first and then flash it via recovery please advise many thanks rob
[Galaxy S 4 i9505 Original Android Development] george stamatos:
First option is just fine
[Galaxy S 4 i9505 Original Android Development] ROBSONMEG:
cheers do I have to flash gapps as well again or just the update to rom
[Galaxy S 4 i9505 Original Android Development] george stamatos:
Just update, don't flash gapps
[Galaxy S 4 i9505 Original Android Development] ROBSONMEG:
ok did that just flashed update and after reboot no Google play store and play store services not working so should I flash gapps again or not
[Galaxy S 4 i9505 Original Android Development] monkteo:
patch the gapps and flash it (nothing bad will happen)
[Galaxy S 4 i9505 Original Android Development] Silesh.Nair:
Samsung Mega 6.3 support

[MENTION=4277844]chenxiaolong[/MENTION],

Would you be willing to add support for my device to your app? Requested details are attached.
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION], I am back to this again. I seem to be the only person that can't get the S6 xposed beta to work. It patches and installs since your fix, but then I have no data, In system details I have Software Version: Unknown and Baseband Version: unknown. I am sure there are other S6/(edge) Sprint users, but my known population is 3, and I am the only one experiencing problems and the only one running DB. Xposed does some things I do not understand, but I can see no difference, other than /sbin/mount (flash-script.sh), in a primary and data-slot patched zip. BTW, Xposed works in my data-slot (different rom). When I have time there are a couple things I want to try: 1. Xposed with primary rom in a data-slot. 2. xposed without DB. In the meantime, if you see anything that could be causing my problem, please let me know.
[Galaxy S 4 i9505 Original Android Development] nds850:
No one knows? If I flash a file that's meant for trlte instead of my trltexx I have to manually remove the first line in the updater-script file to be able to flash it.

:fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] physwizz:
I have been able to run 2 roms on my Galaxy Tab S.

What do you put in the data slot?
[Galaxy S 4 i9505 Original Android Development] todivefor:
I tried it in a data-slot and it worked. This of course was a clean install. Don't bother looking at this. I have some more testing to do first (clean install on primary).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The extsd-slot release is nearly ready. I hit a jflte-specific issue where CM refuses to extract system.new.dat and just leaves an empty filesystem. Once that's fixed, I'll make a new release :)

EDIT: It's because CM tries to create /cache/recovery/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/ without creating /cache/recovery/ first. And it sure is "fun" when their ErrorAbort() calls set an error message, but never show it on screen or in the logs: https://github.com/CyanogenMod/andr...ef14c079fe77710080cc2/updater/blockimg.c#L752

EDIT2: And we have success! Just need to test one more time on trlte to make sure everything is working, then I'll merge the changes.
[Galaxy S 4 i9505 Original Android Development] jean_pulbere:
[MENTION=4277844]chenxiaolong[/MENTION] .. did you make it to work on gt-i9515 value edition ?? i post what you ask for it but no answer from you??
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Both are supported in 8.0.0.r1650.g2c40424 :)

The jfvelte has the same partition table as jflte, so they are grouped together. As far as dual boot is concerned, the two devices are identical. melius will show up as a new device in the patcher's device dropdown.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
extsd-slot code has been merged! Just waiting for the build to finish ;)

→ ←
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, that shouldn't ever happen unless mbtool crashed. If you wouldn't mind, could you force a reboot into recovery (without shutting down the device) and flash the attached zip? It will save a tar archive to /sdcard/logs that should contain much more information about why it doesn't boot. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Currently, there isn't a way to do that. However, once I implement backup and restore, you will be able to backup the primary ROM to a file and restore it to the secondary ROM. Hopefully, that'll be close enough to real migration ;)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The ramdisk update only affects the current ROM's kernel. As soon as you flash another kernel (or the same one again), all the changes it made are gone.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
To be honest, I haven't done any benchmarking, so I have no idea. That would be a really interesting thing to look at though. My gut feeling is that it might be a bit slower to have the ext4 image on top of an ext4 partition because both filesystems will be performing journaling, which might cause a performance hit.
[Galaxy S 4 i9505 Original Android Development] jean_pulbere:
[MENTION=4277844]chenxiaolong[/MENTION] help pls..fail to patch secondary rom cm11 for flashing.. :((
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I removed that feature because on trlte, the partition tables for the intl and US versions is slightly different. I encountered a few TouchWiz trltexx ROMs that wiped the hidden partition. Overriding the checks caused the ROM to wipe the data partition on my trltetmo because "hidden" on trltexx and "userdata" on trltetmo have the same partition number. For other devices, slight differences like that might wipe a bootloader partition, which could easily cause a hard brick.

That's why I don't think it's a good idea to remove the checks. Hope you understand :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm assuming you mean the text box for data slot? That's for specifying a name for the data-slot. Because data-slots are installed to the large internal storage (/data) instead of /system, it lets you install an unlimited number of ROMs. That's why you can give it any name.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for testing! Let me know if anything else goes wonky :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I think I have juuuuust a bit too many ROMs :p
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
wow lol!!!

---------- Post added at 05:43 AM ---------- Previous post was at 05:43 AM ----------

wow lol!!! thats a lot!!!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Just a word of warning to those who want to use extsd-slots: SD cards are slow and the SD reader's controller on the Galaxy S4 is slow too. ROMs might take a while to boot and look like they're hanging at the Samsung logo. Just give it some time and it should be able to boot (especially if it's an AOSP-based ROM).
[Galaxy S 4 i9505 Original Android Development] nds850:
I see. Thanks for the explanation [emoji4]
[Galaxy S 4 i9505 Original Android Development] physwizz:
Thanks. I'll try flashing a ROM there.

Edit: battery just died and couldn't be recharged.

Took baby back to the shop.
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
I succesfully install and boot a cm12.1 rom, thanks a lot for this awesome update?

I have a question the apps that I install are going to install in the external sd or internal?

thanks in advance!!!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Glad you're liking it! Apps you install and all data goes on the internal. The ROMs themselves go on the external. 100% of the backend code to support data on external SD is already there, but I really don't want to write a UI to manage (resizing, etc.) a bunch of ext4 image files :)
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
thanks!! I which that feature can come in a future update so I can fully use my 128 gb external sd because that's what takes the most space.

awesome work like always you are a genius keep up the good work like you always do!!!!!
[Galaxy S 4 i9505 Original Android Development] Silesh.Nair:
Mega 6.3

[MENTION=4277844]chenxiaolong[/MENTION],

Thanks for adding support for my device. I have a couple of issues I need to ask you.

While selecting app sharing, I get a message "mbtool must be updated to take advantage of the app sharing feature. Please update the ramdisk". What should I do? Updating ramdisk from ROM Settings results in no external sdcard in primary rom

I don't have access to my external sd card on any rom except the primary rom. I have flashed a secondary rom and one in the data slot.

All Gapps packs are supported?

Attached a few snaps for your perusal. TIA.