yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
[MENTION=4277844]chenxiaolong[/MENTION] [MENTION=5500870]vPro97[/MENTION] and I have figured out why some of the ROMS and kernels for the G2 don't work. There is a new method that replaced Loki. It us BUMP. I am not to sure about it yet but I know there is a tool to bump recovery.img from recovery so it might be able to be adapted to bump boot.IMG.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Also how does dualbooting work with the f2fs filesystem?
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
Bump is a method to sign the boot.img with LG's signature to work with our locked bootloader. And when the app patches the boot.img this signature get lost and we get security error on boot.

You can search xda for "open bump" for further details.
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
LG G2 D802

Got an error while setting kernel as primary. Error msg "failed to set kernel"

Did a fresh start, wiped all in recovery and installed stock-based ROM (unpatched). After ROM booted I wanted to set kernel as primary so that i can flash another Rom and got that error. Newest snapshot.

Also could not install the same stock ROM (patched) as secondary. flash went fine but did not boot. Thats why tried as primary.
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
Error on Windows Version of patcher. Snapshot 704.

Windows 7 64bit

Error Message:

Failed to load patchinfo files
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I've the same issue with the 699 on Windows 8.1 64 bits.
[Galaxy S 4 i9505 Original Android Development] gaww:
Do you have the 64 bit .dll's in the folder with the patcher ?

Never-mind - they don't help this version. I think it might be 64 bit drivers but not the ones posted earlier in this thread for a different version (the 9.0 alpha - which works).
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I didn't look; I gonna see that.

---------- Post added at 05:53 PM ---------- Previous post was at 05:50 PM ----------

What dll(s) are you talking about? I lost a little over recent times, I'm not much the subject.
[Galaxy S 4 i9505 Original Android Development] peppe130:
Hey mates! Are there news? The syncdaemon (hoping it's written right xD) is now fully working? Actually I'm using this version of the patcher :)
[Galaxy S 4 i9505 Original Android Development] monkteo:
I come back with my problem ,

I try to patch this rom (http://xdaforums.com/galaxy-s4/i9505-develop/5-0-2-ressurection-lollipop-5-2-7dark-t2994283) but i finish with bootloop

I extract the rom and (I don't know) I think it's a problem ?

any help ?

I want as secondary , I installed on another phone without dualboot and work perfect.

I attach some pic .

THX
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Still not able to patch and run Cyanogenmod 12 AntaresOne version with Patcher r704 in Multislot 2 just getting a bootloop
[Galaxy S 4 i9505 Original Android Development] todivefor:
I am having all sorts of problems. I do not know if they are dualboot or rom related. I am running a GS4 (Sprint). I have sacs-v4 (TW) as primary and cm11, cm12, and pacman as secondary. My problems are with cm12 (AntareOnes optimized), my other secondaries do not have a problem . I had one of the earlier builds running. I am now trying to update it. I was able to update, but with problems (proximity sensor didn't work). The only way I could update was to flash rom, it wouldn't boot flash kernel, then it would boot. Someone in the cm12 official thread repacked Alucard's kernel, but it won't boot. I have been able to flash and boot Alucard's 1.0f kernel, but again with no working PS. I seem to be the only person with PS problem. I know of 1 other person running dualboot and this rom and not having PS issues (he's intl GS4 and has a working unofficial Alucard kernel). I think my issues are a combination of dualboot and kernel. I am patching with snapshot 436. I guess I am wondering why reflashing this rom requires a kernel reflash? Why do none of the kernel repacks not work? I guess maybe I need to hold off on dualboot until the next release.
[Galaxy S 4 i9505 Original Android Development] sronweb:
+1.

Tested and I get the same error with Win7 64 bit.
[Galaxy S 4 i9505 Original Android Development] gaww:
Still think it is problem with some 64 bit drivers (believe development is being done with 43 bit Windows), but unlike the earlier problem with 64 bit, this error message does not point to it.
[Galaxy S 4 i9505 Original Android Development] sronweb:
I guess so. Something missing. But older versions are working fine on my pc.
[Galaxy S 4 i9505 Original Android Development] gaww:
Same here - using the 64 bit dlls posted awhile back (which do not work with latest).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r706.g29e7bb4 should fix the Windows issues (build will be up soon). It was a stupid mistake; I moved the exe files around, but it was still expecting the data files to be "../data" instead of "data".

(If you're impatient, open DualBootPatcher.exe in a hex editor and changes bytes 0x1438-0x143C to "\x64\x61\x74\x61\x00" :p)

EDIT: Also, Windows builds are compiled using gcc instead of Visual Studio and all needed DLLs are included. There is no need to install anything else.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Not yet, still working on it :)
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Great Job!
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
So should the current android patchers, 704/5/6 work with AntaresOne CM12? I've not managed to patch current builds successfully?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
For that:

Use the preview version of the Dual Boot Utilities and migrate the multiboot ROM data: download link

Reinstall multibooted ROMs

Avoid using older versions of the patcher

Can I only patch the kernel like before? Or should I must patch the rom again? I'm with the DualBoot Patcher Snapshot 423.
[Galaxy S 4 i9505 Original Android Development] v00d007:
That's strange while i patched it with 8.00.99/customrom settings. But atm it seems way to early to play around with cm12. It's really what's in Windows world would be called an 'early alpha'/w lots of bugs and completely feature-incomplete, so it's no great loss to let it be at all...
[Galaxy S 4 i9505 Original Android Development] todivefor:
I have encountered all kinds of problems and need to start over. How do I uninstall? Do I just wipe all from dualboot utilities?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Yes
[Galaxy S 4 i9505 Original Android Development] gaww:
I would wipe with recovery to really clean out all the partitions.
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
[MENTION=4277844]chenxiaolong[/MENTION]

On LG G2 (D802) it is not possible to install a patched stock ROM as secondary. Installation finishes but the ROM doesn't boot up. Tried different ROMs with and without aroma installer.

If you install the ROM normally (unpatched) as primary you can not set kernel as primary via app, error message "failed to set kernel". I also tried different ROMs and kernels. Only way to get it working at the moment is by backing up boot.img in recovery before flashing pachted AOSP ROM as secondary. And for switching ROMs back to primary you have to go to recovery and restore boot.img.

Two AOSP ROMs and everything is working as it should.

Could this be kernel related?

Here's the link for a stock kernel if you would like to take a look.

https://www.androidfilehost.com/?fid=95784891001608817

Thank you.

Edit

Another "idea" ;)

Would it be possible to set the modem partition for the different ROMs, just like we set the kernel? For the G2 there are (AOSP) ROMs that use JB source while others use KK source and you need the corresponding modem for the sensors to work.
[Galaxy S 4 i9505 Original Android Development] todivefor:
Can someone please explain what "set kernel" does? Do I only do this once for the primary rom?
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
Yes you do it once on primary ROM before installing secondary. And on secondary after installation.

It copies the content of boot partition (kernel) to be stored somewhere. And when you switch ROM the stored kernel for the chosen ROM is copied back to the boot partition.
[Galaxy S 4 i9505 Original Android Development] todivefor:
Just to get this straight. You have to set the kernel once on primary, and then once for each secondary you install.
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
Yes. But you have to do it for primary before you flash the secondary. Otherwise your primary kernel is gone as boot partition gets overwritten when you flash secondary.
[Galaxy S 4 i9505 Original Android Development] todivefor:
I ran this, but then had problems and don't know where I went wrong. I start with my primary, set kernel. I patch and flash secondary. Do I then boot secondary and set keernel?
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
That's what I did. And as long as primary and secondary are AOSP Roms it works as it should. On LG stock-based ROMs it doesn't work :(

If it works for you that you can set kernel in primary and secondary you should be able to change ROMs with the app. Just "choose ROM" and reboot.
[Galaxy S 4 i9505 Original Android Development] todivefor:
I am having problems with the latest snapshot (710). I am running sacs-v4 (TW). I installed the patcher app, and set kernel. I patched my CM11 rom (cm-11-20150203-NIGHTLY-jflte_patched.zip) and gapps (pa_gapps-modular-full-4.4.4-20150125-signed_patched.zip). Flashed both. CM11 flashed fine, gapps had an error. It said there was a log generated on the sdcard, but I can't find it in multiboot I believe. I switched rom to primary in dualboot utilities and it said it couldn't because no kernel. CM11 did boot. On my sdcard I have /MultiBoot/dual/boot.img and /MultiKernels/primary.img.

Any idea what I am doing wrong? What can I get to trouble shoot?
[Galaxy S 4 i9505 Original Android Development] todivefor:
Found the log for failed gapps.

It was not in /multiboot, but root of sdcard. Looks like it ran out of room for gapps. I'll try a difderent gapps, but why am I having kernel issues?
[Galaxy S 4 i9505 Original Android Development] lukas77:
Dualboot utilities zip is not compatible with newly patched ROMs, to come back to primary ROM just restore only boot image from nandroid.

About Gapps, I had the same problem with pa gapps, this gapps, should work

https://www.androidfilehost.com/?fid=95832962473395379

| Tapatalk | Samsung Galaxy S5 | G900F |
[Galaxy S 4 i9505 Original Android Development] todivefor:
I was using the new dualboot utilities. I'll give the gapps a try. That's what I used before.
[Galaxy S 4 i9505 Original Android Development] todivefor:
Everthing works after gapps installed correctly. Don't know why my primary kernel got screwed up first time.
[Galaxy S 4 i9505 Original Android Development] todivefor:
Using r710 of patcher on Sprint variant. "reboot" option doesn't work, goes to choose rom (minor inconvenience). Sharing applications doesn't work. Says it can't update ramdisk when I try that. Will collect any info if needed.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
[MENTION=4277844]chenxiaolong[/MENTION]

I wanted to install all my roms with the latest patcher (709), for multi-slot-2, it's ok but not for the primary (Echoe 39.1), I can't boot on it.

However, I've got a reinstallation like a full wipes on my multi-slot-2, maybe due to a bad installation the first time, I'd only installed the kernel_patched.

For primary if i want to upgrade.... Have to make a full wipes in primary?
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=427477]chenxioalong[/MENTION]

I tested some snaphots from 699 to 710 and all can't set the kernel for primary and modify ramdisk. No matter which rom, cm11, cm12. What is wrong here? v8.00.99 worked flawlessly but can't patch lp roms, that's why I want to upgrade.
[Galaxy S 4 i9505 Original Android Development] monkteo:
witch new dualboot utilities ? you talking about 3.3 ?
[Galaxy S 4 i9505 Original Android Development] sronweb:
No. He is talking about the 4.0 snapshot. Go to the snapshot link and read from the top.
[Galaxy S 4 i9505 Original Android Development] todivefor:
Most people should start off fresh, but if you want to keep the currently multibooted ROMs, follow the steps below.

Use the preview version of the Dual Boot Utilities and migrate the multiboot ROM data: download link

Reinstall multibooted ROMs

Avoid using older versions of the patcher
[Galaxy S 4 i9505 Original Android Development] todivefor:
The official CM12-jfltespr came out yesterday, which I have flashed successfully as secondary with snapshot r710. Will I be able to dirty flash updates without a kernel? This was problem for me with antareone's.
[Galaxy S 4 i9505 Original Android Development] v00d007:
If someone's interested:

After testing quite lots of DualBootPatcher versions while trying to get cm12 and cm11 to work side-by-side on a S4 Mini 9195, i succeeded with the following:

- Installed cm12 as primary + set kernel (important!)

- patched cm11 as secondary and installed

- Patching done with Patcher v8.00.436 which was the only one that could do all the needed operations (tested most of the various builds from 436 to 710)

proof:
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
I tried several times to patch temasek's cm12 for note 3 with the new snapshot, but without any success. I also tried to migrate my secondary rom(slimkat 9) with the new dualboitutilirues, but instead of migration it just did a clean install of the rom... :(
[Galaxy S 4 i9505 Original Android Development] monkteo:
You are right 435 and 436 are still the most perfect working patch.
[Galaxy S 4 i9505 Original Android Development] v00d007:
...but app sharing between cm12 and cm11 still doesn't work due to the non patchable ramdisk (at least on S4mini). Next I'll try all the stuff on my S4.
[Galaxy S 4 i9505 Original Android Development] sronweb:
I tested last snapshot r725 but if I enter in the rom choice for i.e. it says that I have no root even if I have it. Thanks
[Galaxy S 4 i9505 Original Android Development] franzyroy:
You have to patch your rom with it in order to it works. It already was like that before.
[Galaxy S 4 i9505 Original Android Development] sronweb:
Do you mean from yesterday's snapshot I should re-patch it? Because I have patched yesterday's CM12 release. Anyway I will follow your advice. Thanks
[Galaxy S 4 i9505 Original Android Development] franzyroy:
It worked fine for me with the snapshot 423. I changed in order to have the next roms with Lolipop, otherwise, I would have kept the 423.

With the 709 and I can't:

Change the rom icon

Change the rom name without it comes back by default

Share my apps with other roms

No access to "Sharing to individual apps"

Edit:

With the 719: and I can't:

Change the rom icon

Change the rom name without it comes back by default

Share my apps with other roms

When I've updated the ramdisk, the rom has blocked on Samsung logo. :(

With the 725: and I can't:

Change the rom icon

Change the rom name without it comes back by default

Share my apps with other roms

No root. :(

[MENTION=4277844]chenxiaolong[/MENTION]

Honestly, I should have stayed on the 423, which really worked well.

One question, the "Multikernels" folder. Is it still used? If no, you should implement something in your app to delete it!
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
Nevermind guys, it was temaseks rom that was not working not the patcher. Now I'm running X-Note v21(TW KitKat) as primary and CM12 Nightly as secondary on r710 sbapshot and no cmplains so far. Thx, great work!
[Galaxy S 4 i9505 Original Android Development] gaww:
I am haviving a minot issue with app sharing on non 4.4 ROMs.

When I go back and forth between primary and multi ROMs, all is OK except every time I return to Primary, I get a notice thet Play Services needs to be update - which i do. But I have to do this every time,

I am using older stable versions of Windows GUI to patch these as I wait on the newer versions for 5.0 to settle down (flashing 5.0 ROMs somehow spilled back to the others and required restores to get everything working again - did not app share with 5.0).
[Galaxy S 4 i9505 Original Android Development] sronweb:
Sorry but it's not clear for me how to make the primary rom available for selection if it has been flashed with old patcher and the other rom are patched with latest.

It's not enough to delete system, cache, dalvik cache and flash as an update or I should flash from zero formatting also the multi-slot 1 rom? Currently I have patched the primary (Shostock 8.0) but I get an error and the end of flashing with the result that the phone stuck with Samsung logo.

Thanks
[Galaxy S 4 i9505 Original Android Development] seijisandrei:
With the 423, can it support Danvdh's GPE Lollipop and Official CM12? and would have app sharing too?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
It seems me that yes, I had the CM12 of AntaresOne, if CM12 of AntaresOne worked, the official have to work, and I believe Danvdh's GPE Lollipop was also supported... "App sharing" also worked .
[Galaxy S 4 i9505 Original Android Development] Bejda:
Hello all,

I had to rename latest HellyBean 20131011 zip to previous 20131003 for it regains patcher-tool support (1.17.2).

I know support rely for a part on zip's names but not that much no? I mean such cases doesn't happen with others rom when a simple update with date or whatever changed in its name is released isn't it?

So I thought I could report this,dunno.. :)
[Galaxy S 4 i9505 Original Android Development] Hecatrice™:
Guys as a base there may be a ROM cooked sammy?:)

Inviato dal mio GT-I9505 con Tapatalk 4
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That was a mistake. I'll fit it when I get home :)

I usually copy and paste the filename and then modify it to be a pattern. It seems I forgot to do that for HellyBean: https://github.com/chenxiaolong/DualBootPatcher/blob/master/scripts/patchfile.py#L327
[Galaxy S 4 i9505 Original Android Development] RK:
http://xdaforums.com/showthread.php?t=2397511

That ROM is supported but the patcher says unsupported zip as well..
[Galaxy S 4 i9505 Original Android Development] omnifarious:
Edit: Delete please
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I wish I could support everything automatically, but there are two main issues I have with doing this:

1. One simple typo or change in how the updater-script is written could delete all user data from the phone. There are also many TouchWiz ROMs that separate scripts that do the wiping. It's almost impossible for me to determine what's going to be installed and wiped without manually looking at the scripts.

2. Many ROMs unnecessarily unmount and mount partitions in between steps in the updater script. Some don't even unmount the partitions. Let's say an updater-script is badly written and mounts the same partition twice. Because of the way my dual booting works, this would cause the flashing to fail and could potentially leave the phone unbootable.

Anyway, if you need a little help on manually editing the scripts, please let me know. I'm happy to help :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, I forgot about Metallica's variant of PAC. Give me a few minutes and I'll add support for it :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure :) Could you give me a like to the ROM's page? I need to find a pattern in the ROM's filenames so future versions can be supported.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ahh, it looks like OS X doesn't support static binaries. Could you try this instead?

gcc -Iinclude mkbootimg/mkbootimg.c libmincrypt/sha.c -o mkbootimg.osx
gcc -Iinclude mkbootimg/unpackbootimg.c -o unpackbootimg.osx
strip mkbootimg.osx unpackbootimg.osx

The warnings that are printed don't actually matter. If the two files, mkbootimg.osx and unpackbootimg.osx, are created, then it succeeded.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
HellyBean and AOSP are fixed in version 1.17.4 :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Metaiiica's PAC-Man is now supported in version 1.17.5 of the patcher :D
[Galaxy S 4 i9505 Original Android Development] munchy_cool:
here you go ..lemme know what i need to do next to get the patcher working on my mac ..the extension of the files is .osx
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I just tested them and they work just fine. (There's an emulator for Linux called Darling that can run very simple OS X programs)

I'll bundle those binaries in the next release. :)
[Galaxy S 4 i9505 Original Android Development] thehacker911:
Add Support for Hacker Kernel v... Light?

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] munchy_cool:
awesome ...Can you please quote me when that is done so that I get a notification
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure. Would you mind testing the beta version attached to this post?
[Galaxy S 4 i9505 Original Android Development] munchy_cool:
worked like a charm :) have only mac to test though
[Galaxy S 4 i9505 Original Android Development] Hecatrice™:
Guys can we help me please??

Inviato dal mio GT-I9505 con Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] The1nonly1:
I'm on stock TouchWiz software. How much space did I need to free in /system to make room for the [AOSP]Official 4.3- S4 Google Edition- Finaly v2.0 - Feel the Experience of Nexus ROM?
[Galaxy S 4 i9505 Original Android Development] v00d007:
how to patch supersu.2.45.zip for secondary rom? which patcher is able to? script that's to be patched is located in update-binary instead of update-script, so all patchers i tested FC. maybe i'll edit the binary manually...
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION] I have read your warning about r718 and above. Are you encouraging people to not test with these? Are chances of this working better or worse with newer or r710 in above situation?
[Galaxy S 4 i9505 Original Android Development] sronweb:
If you wanna go for recent version I would go for r.709 for now.

Otherwise for older patcher follow the suggestion from Franzyroy some posts ago.
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
I patched cm12, gapps, aand supersu with r710 no complains so far
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
I've tried to patch AntaresOne CM12 and it fails to patch with various recent itterations of the Patcher :( I'll try again later
[Galaxy S 4 i9505 Original Android Development] v00d007:
Sorry but here the 710 is neither able to set kernels, switch roms, patch ramdisk, nor to patch supersu245.zip correctly. It corrupts the supersu script (update-binary) and blows it up from 16kb to over 640kb of binary waste... :confused:
[Galaxy S 4 i9505 Original Android Development] todivefor:
I patched cm12-jfltespr with r710. I was able to set kernel and switch roms. I did not install SU. I am unable to patch (update) ramdisk as you say.
[Galaxy S 4 i9505 Original Android Development] sronweb:
For r728 I still see the "no root" issue using the patcher on the phone. Just for info.
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
I tried latest Patcher last night. It fails to patch AntaresOne CM12 .zip but the Official .zip patches OK but I just end up in a bootloop when I install it.
[Galaxy S 4 i9505 Original Android Development] Darkwing_X:
[MENTION=4277844]chenxiaolong[/MENTION]

Patched Echoe V40 Lollipop with Snapshot 625. Now have Echoe V39 as primary and V40 as Multislot 1.

All is runnig great :good::good: 29195262DT7473143