yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Andycar:
Thanks.

Previously, like you mentioned, there was a big lag with SupeSu app asking for the SU rights... I noticed it yesterday when SuperSu request popped up __after all actions__.

So I've done two logs. Here is the links:

1. http://pastebin.com/1H9ab27Z

2. http://pastebin.com/NnYg7T2m

The first one was after I cleared both superSU's and Patcher's (r1522) apps' data. Then ensured that Patcher app gets the root explicitly from SuperSu app. Then tried to patch ramdisk. (no avail again)

Second time I just tried again. What's relly bad, __nothing__ is shown in SuperSu in the "App acces log" section... :eek: Like there was no request for granting of SuperSu right.

Very strange. I'm going to reinstall my system and report back, there is something totally wrong with my ROM.

---------- Post added at 08:35 AM ---------- Previous post was at 07:57 AM ----------

Actually, it would be nice if you implement ROM switching by the other method, i.e. intents receiving:

"My dream" is:

You app could receive intent from Tasker, e.c.

com.github.chenxiaolong.dualbootpatcher.SWITCH_PRIMARY would reboot system into primary ROM,

com.github.chenxiaolong.dualbootpatcher.SWITCH_DUAL would reboot system into dual ROM,

and so on...
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
I would like to know the benefit of switching from tasker. Just to integrate with another app?
[Galaxy S 4 i9505 Original Android Development] Andycar:
You could automate switching by e.c., connecting to Bluetooth in the Car (CM ROM works better for me in the Car).

Another thing is fun and cool: You could Voice Command your phone to reboot into other ROM by AutoVoice... and so on :)
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
THAT, would be cool !
[Galaxy S 4 i9505 Original Android Development] sronweb:
What about having the switch pressing the power button. In AOSP roms typically we can add the options as shut down, reboot, screen capture, flight mode and then could be nice to have the "dual boot" menu to select the other roms.

I have the idea but I don't know how to implement :)
[Galaxy S 4 i9505 Original Android Development] Andycar:
Shamelessly quoting myself here :) Reinstaleld the ROM and successfully patched boot.img of the same kernel. Patcher app receives SU rights correctly.
[Galaxy S 4 i9505 Original Android Development] godmode1970:
I installed Alliance v9 (TW 5.0) as primary and BlissPop (AOSP 5.1.1) as secondary on my S5. Is there a way to make independent backups of the ROMS?

and how can I install/flash Gapps on the secondary ROM?
[Galaxy S 4 i9505 Original Android Development] nds850:
I know I asked a while back why I got errors when installing a third ROM and some said it was probably because the Note 4s cache was too small. Just wondering if there is any possibility to install a third ROM at all? Would it be possible to temporarily disable one or something? :)
[Galaxy S 4 i9505 Original Android Development] gaww:
If they were shared with data already - how do you clear things out? Tried unsharing data and wiping data from both - no impact. Then unshared them - and no impact on free space also.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That will come as part of the implementation. Patching files via an intent will be supported as well :)

Proposed:

Patch file intent:

Action: com.github.chenxiaolong.dualbootpatcher.PATCH_FILE
Argument: path [required][string] Path of file to patch
Argument: rom_id [required][string] ROM ID (primary, dual, multi-slot, etc.)
Argument: device [optional][string] Device ID (jflte, trlte, zerolte, etc.) (autodetects by default)
Argument: has_boot_image (optional][boolean] Whether file has a boot image (autodetects by default)
Argument: boot_images [optional][string array] List of manually specified boot images (very rarely needed)
Returns results: (WIP)

Switch ROMs intent:

Action: com.github.chenxiaolong.dualbootpatcher.SWITCH_ROM
Argument: rom_id [required][string] ROM ID to switch to
Argument: auto_reboot [optional][boolean] Automatically reboot after switching (default: false)
Returns results: (WIP)

(Maybe more?)
[Galaxy S 4 i9505 Original Android Development] Andycar:
Seems like a nice way to implement. Also, that would be enough - for me, at least.
[Galaxy S 4 i9505 Original Android Development] monkteo:
Patch the gapps and flash from recovery or dualboot app.
[Galaxy S 4 i9505 Original Android Development] sireebob:
I'm one of the folks who is on a different phone (LG G3, vs985), but this used to work great for me. Lately, I get a black screen on boot for whatever I try to flash (BlissPop, Validus, ...), using TWRP 2.8.7.0 or flashing from Dual Boot Patcher itself (8.0.0.r1522.g287a13a-SNAPSHOT).

Also, when I try to flash the AOSP 777 Kernel ( https://www.androidfilehost.com/?fid=24052804347789389 ), I get a "boot certification verify" error, like the kernel doesn't get properly bumped. It flashes fine if I don't patch it. Any ideas?

You'd probably do this anyway, but I would recommend a notification to confirm an intent-based ROM switch :) to save us from ourselves! (You wouldn't have to click to confirm or anything, but just so you knew the change happened.)
[Galaxy S 4 i9505 Original Android Development] jean_pulbere:
Hello .. Can someone tell me if i can have dual boot ( two roms) on my GT-I9515 VE ???

I want to use the official stock rom kk + cm11 for gt-i9515 by Sombree .

In this moment i have only cm11 by sombree but i cant find any tutorial for this,so pls help anyone.

I so many threads but not sure wich one of solution is for my gt-i9515.Can someone post an step by step tuttorial or something ??

thx in advanced
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4491606]ktetreault14[/MENTION] could you tell me what roms you are dualbooting and which slots? I am about to try on my Sprint S6 (g920p). We don't have many choices, so will have to flash 2 TW roms.
[Galaxy S 4 i9505 Original Android Development] nutpants:
I'm on release 1459

Primary is liquid Smith smooth 4.4.4 milestone

Secondary Is omni rom 4.4.4 final

I recently reinstalled my nexus 7 2013 to update and i have been slowly been adding apps.

Today in getting a "out of space" to install error

And while a have a number of apps installed i don't have anywhere as many as before..

I've checked free space in the dual boot app and i have gigs everywhere except cache (568 mb) and persist (10 mb) and system (200mb)

What else can i check?

Should i everything get the newest and start over?

( i can still install apps in second rom but not primary)
[Galaxy S 4 i9505 Original Android Development] gaww:
That space error usually pops up when your internal SD has less than 500mb left. Checkin settings for "storage" and see how much space you have on your primary. If you are not app sharing, start moving some to SD card to free up some space. Also, when you checked storage in settings - if the cache is large (more then 20 mb or so), clear it (in settings - not in recovery or utilities zip).
[Galaxy S 4 i9505 Original Android Development] nutpants:
Cleared cache just because, and i have 560+mb free

Internal storage is 17gb + free.

I'll keep looking to see what's is what and if i can't fix it I'll wipe and try again.
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Is there a thread for this or any way to keep up with the progress specifically?

Google+ group or something?
[Galaxy S 4 i9505 Original Android Development] gaww:
Which cache did you clear - the on in settings/storage/cache ? If so, and you only have 560 mb in Internal memory/SDcard free - you need to look elsewhere.

Where are your photos going - internal or external - can really fill internal up. Ditto for backups. You have to move as much as possible to external and out of memory and internal SD or you will just end up in the same place after wiping and reinstalling your apps again.

Again - sharing apps or moving them as much as possible to the SDcard can usually free up a few to several hundred mb.
[Galaxy S 4 i9505 Original Android Development] nibbel:
Is it possible to remove all multiboot roms permanently? I have several problems with slot 2 and "secondary". Permanently FCs of the most apps (g-apps and shared apps) from the beginning (fist start). A wipe does not help.. Same problems :/

I tried to clear cache from the Recovery and I see no roms in multiboot app. So I tried a second time and make a clean install in "secondary" slot. But after first start it FCs several apps like G-apps (no package installed!) and some apps from my first rom... I think its a problem with app sharing from the first try.

My ROMS

* First - CM12.1 Optimized

* Second - Orion LP (tried GAPPS from SLIM-ROM)

thx :)
[Galaxy S 4 i9505 Original Android Development] physwizz:
I'm having a lot of fun with this patcher. Thanks heaps!!!

I have 2 questions

1. Has anyone managed to get more than 2 ROMs at a time on the Galaxy Tab S?

2. What is the data slot for?
[Galaxy S 4 i9505 Original Android Development] todivefor:
I can confirm that dualboot works on the Galaxy S6 Sprint variant. I have been waiting for a reason to use this on my Sprint S6 as I used extensively on my S4. The Sprint S6 has only 2 TW roms to speak of and a couple kernels. I have the Ramified V1 OGA rom by [MENTION=2410609]ram9200[/MENTION] as primary and Twisted Project 6 V4.0.1 rom by [MENTION=3795788]pwnyourace[/MENTION] in a data slot. I patched both successfully in Windows 10 with DualBootPatcher-8.0.0.r1522.g287a13a-win32.

Thank you [MENTION=4277844]chenxiaolong[/MENTION] (BTW best developer on XDA).
[Galaxy S 4 i9505 Original Android Development] gaww:
It is possible, but you are going to have to search the thread. The OP has posted instructions to do this a number of times.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
/sdcard/MultiBoot is probably what you're looking for. That's where the app sharing configs, ROM thumbnails, etc. are stored. To completely remove all traces of other ROMs, delete

/sdcard/MultiBoot

/system/multiboot

/cache/multiboot

/data/multiboot
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
Have you had any success with external sd slots on the patcher?

Thanks in advance!!
[Galaxy S 4 i9505 Original Android Development] ROBSONMEG:
I take it to update primary rom u have to flash it while in secondary rom correct?
[Galaxy S 4 i9505 Original Android Development] todivefor:
You flash from recovery, so it does not matter what rom you are in.
[Galaxy S 4 i9505 Original Android Development] ROBSONMEG:
but u have to patch it first yes is that correct
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The upcoming release (with support for intents) is almost ready. I had to take some time to implement some security measures against malicious apps. For example, an app won't be able to inject malware into, say, /sdcard/MultiBoot/primary/boot.img and then fire off an intent to switch to primary.

The app will record the boot.img sha512 hashes in /data/multiboot/checksums.prop when a ROM or kernel is flashed. If the checksums match, automatic switching via intents is allowed. If the checksums don't match, a manual ROM switch is required to confirm that that the changes were expected.

This should be done either today or tomorrow (but you guys know how well I reach my own deadlines :p)
[Galaxy S 4 i9505 Original Android Development] Andycar:
Very wise, I'd say... No problem, take your time, but of course eagerly waiting for this update! Thanks in advance!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r1584.ge21bd22 is now released!

The biggest feature is that third party apps like Tasker can switch ROMs and patch files by launching an intent for DualBootPatcher. As a side effect, we can now add icons for ROMs to the launcher. Take a look at the ROM's menu in the app!

Documentation for the intents is available here: https://github.com/chenxiaolong/DualBootPatcher/blob/master/docs/INTENTS.md Note that intents are not allowed by default unless enabled in the app's settings.

Changes:

Removed device-check removal feature. The patcher really shouldn't do anything extra besides making the ROM boot.

Removed PatchInfo and .patch file support. The last few PatchInfo files for SuperSU, the Xposed disabler, and the defunct PA GApps are now automatically handled by autodetection routines. This change allows us to significantly reduce the size of libmbp due to it no longer needing the XML parser.

Removed most error messages for the patcher. They were completely meaningless without context and were more confusing than helpful. The app now logs patcher output to /sdcard/MultiBoot/patch-file.log and lets the user know that details are there when the patching fails.

Added proper tokenizer for updater-script files. This replaces the crappy regex replacement technique used before and now properly handles multi-line statements, inline comments, nested functions, etc. in updater-scripts. Syntax errors during flashing should no longer occur. This also reduces the libmbp binary size due to the removal of the regex engine.

Switched to OpenSSL for computing SHA1 and SHA512 checksums in mbtool. OpenSSL has hand-written assembly routines for computing the checksums. This allows the boot.img (and other *.img) checksum verification to complete very quickly.

Minor backwards-compatible changes to the mbtool socket protocol to enable support for checksum verification when switching ROMs.

Fix NullPointerException caused by unset fields when MbtoolSocket throws an IOException while loading the ROMs list.

Screenshots:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That is no longer required for any builds newer than 8.0.0.r1210.gf059479 (which was released around May 11th).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! People like you are what makes the project so much fun to work on, even after 2 years :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The next big release will have support for backing up and restoring individual ROMs. (And yes, you will be able to back up the primary and restore it as secondary, etc. ;))
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmmm, yeah that does sound like a bump issue. Do you happen to have the MultiBoot.log file for one of the failed installations? I'll poke around the code a little bit to see if I made a dumb mistake that broke this.

Right now, it just shows a toast popup. Great point though, I can work on adding a notification tomorrow :)
[Galaxy S 4 i9505 Original Android Development] ROBSONMEG:
to update primary rom do I need to patch the update zip first then flash via recovery. Ps how do I get updates for dualpatcher when they are available cheers rob
[Galaxy S 4 i9505 Original Android Development] sronweb:
Yes. You should patch the primary rom otherwise will be necessary to reinstall the other roms on secondary, multislot etc.
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Dear [MENTION=4277844]chenxiaolong[/MENTION]

Thank you very much for your great patcher!

Request: Could you add some tools (filters, sorting, action for selected) for "Manage shared applications" view ?
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Ash this will be amazing. Going to test a note 5 built rom on my s6 edge ;)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Glad you like it! I can probably get filtering implemented today. What kind of sorting and batch actions would you like to see implemented?

EDIT: Searching is now implemented in 8.0.0.r1589.g8af183d (with animations! lol)
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
thanks man!!! this is amazing work,I'm so waiting for this thanks again!!! also in the future will be possible to install roms in external sd?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yes, installing to external SD will definitely be an upcoming feature :D The latest changes from 8.0.0.r1506 make this significantly easier to implement. That said, It is still a work in progress and I'm don't really know when I'll finish developing and testing the feature yet.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Trued dualbooting a note 5 firmware port on the s6 edge and couldnt get it to work. Clean flashed and good to go
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
What went wrong? Couldn't flash or couldn't boot?
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Couldnt boot. But just as i set up my rom a lovely S6 Edge+ ported rom comes over
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
thanks
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Thank you very much for implementation of searching!

My proposals for sorting, filtering and actions

Sorting (ascending / descending)

- by name

- by size

- by share (apps full shared on top, next apps with shared only apk, next apps with shared only data, next unshared apps)

- by date (installation date?)

Actions:

- select/unselect all

- share/unshare data for selected

- share/unshare APK for selected

- share/unshare APK and data for selected

Filter

- apps with shared/unshared apk

- apps with shared/unshared data
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
If you flash a patched zip in recovery is there still an AROMA script starting? Just asking cause I have a Oneplus One and i can't use AROMA (problem with TWRP for OnePlus One, the phone freezes in TWRP if u use AROMA). [MENTION=4277844]chenxiaolong[/MENTION]

could you add A0001 as codename for Oneplus One? Most ROMs have this in ro.product.device
[Galaxy S 4 i9505 Original Android Development] sronweb:
The patched zip does not use aroma script. Just just go from recovery as any normal zip but it will flash the rom/zip in the proper location.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
AROMA is no longer used because the same issue happens on the Note 4 (and I think Note 3 also).

EDIT: A0001 should be recognized in 8.0.0.r1591.g0132f5c :)
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
[MENTION=4277844]chenxiaolong[/MENTION] any reason why this one particular zip wont patch but flashes fine before hand? https://docs.google.com/uc?id=0B1d_Il6yTO73VkZ5RlNIVjhIZnM&export=download

Thanks and this patcher gets vetter every update
[Galaxy S 4 i9505 Original Android Development] Andycar:
Dear Chen, thanks for great updates!

---------- Post added at 07:10 PM ---------- Previous post was at 07:09 PM ----------

Quick question: if I manually put my file into /storage/emulated/0/MultiBoot/dual/Boot.img

(Its a CM kernel), will it boot off my file? Just making sure... Thanks.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yes it will. Once you copy the file, you'll need to switch to dual from the app to make sure your boot.img is actually used.

EDIT: If you're using 8.0.0.r1584 or newer, the app will warn you that the boot.img was changed. Just click OK.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
ROMs on external SD should hopefully be done by the end of the week for FAT32-formatted cards. I haven't quite decided how I want to handle exFAT yet. mbtool currently handles 100% of it's operations internally using a single binary (< 500KB, yes I'm proud lol), so it would suck to have to depend on a separate fuse-exfat executable on ROMs that don't use Samsung's exfat kernel module.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Awesome
[Galaxy S 4 i9505 Original Android Development] tomaasz:
+1

Wysłane z mojego SM-G900F przy użyciu Tapatalka

---------- Post added at 07:48 AM ---------- Previous post was at 07:42 AM ----------

Does it mean the packer could start support devices with low memory? Like Galaxy S3 mini?

Wysłane z mojego SM-G900F przy użyciu Tapatalka
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
Thank you very much.

Coming from LG G2 I prefer your app over Multirom, easier to handle, no kexec-patched kernel needed and app-sharing.

could you do this also for oneplus one?

as some roms are checking for correct version of tz partition / firmware and won't flash otherwise.

tz on oneplus one is mmcblk0p8
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
You are the best!! Man good job can't wait for that!!!
[Galaxy S 4 i9505 Original Android Development] SeraphSephiroth:
Any chance this will work on SM-N910U
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Maybe. The patcher currently only supports Android 4.2 and up, but it might not be too hard to add Android 4.1 support. My dad has the i8190 (intl S3 mini), so it might be a good device to test with.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done! :) 8.0.0.r1593.g832a287
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The SM-N910U is an Exynos Note 4 right? Technically, it should work, but I don't remember if anyone really tested it.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sounds very reasonable, will do :D
[Galaxy S 4 i9505 Original Android Development] tomaasz:
[MENTION=4277844]chenxiaolong[/MENTION]

great news for me :)

Other proposal:

You should offer your Dualboot Patcher app in play store.

I think many people would be interested in buying this.

or

Could you create in patcher app mechanism for checking newest version as it is f.e. available in Boeffla config app (http://boeffla.df-kunde.de/bc/) ?

---------- Post added at 08:14 PM ---------- Previous post was at 07:30 PM ----------

And widget for reboot to selected rom

Wysłane z mojego SM-G900F przy użyciu Tapatalka
[Galaxy S 4 i9505 Original Android Development] SeraphSephiroth:
Latest snapshot of DBP I tried said device name unknown (trhplte)
[Galaxy S 4 i9505 Original Android Development] Ather:
Try selecting the trelte and patch the zip...

---------- Post added at 09:40 AM ---------- Previous post was at 09:39 AM ----------

I second this, in app updater would be handy!

Ps. My 128gb card awaits your update [MENTION=4277844]chenxiaolong[/MENTION] :p
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You guys should have seen the look on my face when I got my first successful boot from the SD card. If my mouth opened any wider, I'd probably have to go to the hospital :D

Just have a few things to do before this is ready:

Fix SELinux policy patching so SELinux doesn't need to be set to permissive for exFAT-formatted SD cards

Test TouchWiz ROM that uses Samsung's exFAT kernel module

Automatically resize the system image to the minimum size (so each ROM doesn't take 4GB)

Update libmbp to put fuse-exfat into the ramdisk when patching

Update Windows and Android apps to support extsd-slot-*

Update DualBootUtilities to support extsd-slot-*

(Probably some more stuff I'll think of later)

EDIT: The initial flash takes a very long time because fat32/exfat/etc. don't support sparse files. For example, in Lollipop CM, the system.new.dat file is around 500MB, but it actually represents the whole 2+ GB system partition (the empty areas are mostly omitted). When flashing this to an exfat SD card it needs to write the full 2+ GB, even though the majority of it is just zeros. I think we should install to a temporary image on /data, shrink it, and then copy it to the SD card. That is pretty close to what we do for Lolliipop ROMs right now anyway.
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
Thank you very much. In-app flashing went through this time.

But sadly the Rom does not boot. If you'd like you can take a look at the rom https://www.androidfilehost.com/?fid=24052804347796049

Edit

I must correct myself. Did some more test and with version 1593 no ROM boots. Tried with 3 different roms in-app flashing and recovery flashing.

Even Roms that worked when i tried last time with patcher version 1388.

I have a log attached from last try with in app flashing.
[Galaxy S 4 i9505 Original Android Development] -MaD-:
Just a beer or a coke for your great work - Thank you!!! 1KX44967FG198671E