yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] RK:
lol Ill try it but the ROM as primary flashes perfect with the latest Philz.. so if your theory is correct, is it Phil's derp or Chen's? :P

EDIT: For all having IMEI and cell not avalable after install - check "allow old update binary" in latest Philz touch recovery or use TWRP..

If that setting is not checked, Philz touch forces bundled new update binary regardless of what update binary is in the ROM zip. That new update binary is causing all the issues. When that setting is enabled, the update binary that came with the ROM is used and everything is fine!

[MENTION=404574]chavdar[/MENTION], thanks for the hint.

[MENTION=4991991]gravedigger76[/MENTION] The SLIM-F4ST Tool does not cause any issues. Its good to go :)

[MENTION=4277844]chenxiaolong[/MENTION] Sorry to cause trouble in your thread for recovery update binary issues

ANOTHER EDIT: I spoke too soon. I have baseband and signal now but I still get camera failed.
[Galaxy S 4 i9505 Original Android Development] gravedigger76:
Thank you @RK

I will give this a shot tonight.
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Anyone have any Idea I have my main rom setup TW 4.3 I go to flash my patched LS 4.4.2 I then go to flash Ktoonz 3-12 Kernel VZW and when I reboot I get system software not authorized message? I am on TWRP 2.7.1
[Galaxy S 4 i9505 Original Android Development] dandan_00000:
Is it possible to dual bobcat rom and slimkat?

Sent from my GT-I9505 using Xparent BlueTapatalk 2
[Galaxy S 4 i9505 Original Android Development] jthrasher47:
The patcher unloki's the kernel so you need to flash loki doki after the kernel then reboot..
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Thank you !!!!!
[Galaxy S 4 i9505 Original Android Development] qtwrk:
4.0.4 r12 windows gui.exe is reported a trojan horse by ESET Anti-Virus , can you confirm ?

it's ok to me , i don't care , but it's would be kinda annoying if every update i have to manually exclude it again ...:crying:
[Galaxy S 4 i9505 Original Android Development] nikosma:
It works great with UltimaAOSP 4.4.2 by Kryten2k35 as secondary Rom.

Thank you very much!
[Galaxy S 4 i9505 Original Android Development] gravedigger76:
[MENTION=4485012]RK[/MENTION]

Hey so, yep un-checking that option got the ROM installed and EMEI is there, wireless working, sound working,

but yep, you also right Camera crashes.

Were you able to find out why, or how to fix it?:good:
[Galaxy S 4 i9505 Original Android Development] RK:
Nope.. I was hoping [MENTION=4277844]chenxiaolong[/MENTION] would be able to reproduce the camera problem and figure it out :)
[Galaxy S 4 i9505 Original Android Development] gravedigger76:
Have you tried the international version of Skyfall? does it have the same issue with cam?

What about goldeneye?
[Galaxy S 4 i9505 Original Android Development] RK:
Both versions of skyfall have issues. Have not tried GoldenEye..
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Fixed
[Galaxy S 4 i9505 Original Android Development] gaww:
Was the KT kernel patched also ?
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Got it figured out thanks !
[Galaxy S 4 i9505 Original Android Development] gaww:
I often get similar notifications by BitDefender and AVG - they don't like code that involves or has root access - even on Google - lol.

It is a pain though - see if you antivirus allows you to ignore the file.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
If I don't deactivate Eset, I can't even download it!
[Galaxy S 4 i9505 Original Android Development] qtwrk:
All hail ESET and deactivate it temporarily
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Yes I know, I did it. But thanks! ;)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The issue with Ktoonsez's AT&T 20140319 kernels are fixed in the latest experimental version. It was giving a very ugly error like:

Detected Ktoonsez Google Edition kernel
--- Please wait. This may take a while ---
Loading ramdisk with minicpio ...Traceback (most recent call last):
File "/stuff/chenxiaolong/Android/DualBootPatcher/dist/DualBootPatcher-4.0.4-jflte/scripts/patchfile.py", line 75, in <module>
newfile = patcher.patch_file(file_info)
File "/stuff/chenxiaolong/Android/DualBootPatcher/dist/DualBootPatcher-4.0.4-jflte/scripts/multiboot/patcher.py", line 378, in patch_file
newfile = patch_zip(file_info)
File "/stuff/chenxiaolong/Android/DualBootPatcher/dist/DualBootPatcher-4.0.4-jflte/scripts/multiboot/patcher.py", line 262, in patch_zip
bootimagenew = patch_boot_image(file_info, path=bootimageold)
File "/stuff/chenxiaolong/Android/DualBootPatcher/dist/DualBootPatcher-4.0.4-jflte/scripts/multiboot/patcher.py", line 98, in patch_boot_image
cf.load(f.read())
File "/stuff/chenxiaolong/Android/DualBootPatcher/dist/DualBootPatcher-4.0.4-jflte/scripts/multiboot/minicpio/minicpio.py", line 233, in load
pos = member.unpack(data, pos)
File "/stuff/chenxiaolong/Android/DualBootPatcher/dist/DualBootPatcher-4.0.4-jflte/scripts/multiboot/minicpio/minicpio.py", line 99, in unpack
self.magic = unpacked[0].decode('ascii')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xd3 in position 0: ordinal not in range(128)

The reason it did that is because the new kernels had another instance of 0x1F8B0800 in the file, which is the "magic" number for the gzip file format (ie. the ramdisk). During the unloki process, it would find that, treat it as the ramdisk, and try to extract that junk data. The fix is to check the next four bytes to make sure it is valid :) https://github.com/chenxiaolong/DualBootPatcher/commit/5f50622a33870994ebce2fe16060d3e74727d40d

The fix is in experimental version 4.0.4-r14: http://dl.dropboxusercontent.com/u/486665/Snapshots/DualBootPatcher/index.html
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I have absolutely no idea how that is possible... That exe is a simple 100 lines of code that does nothing other than including an icon and running "pythonportable/python.exe". It doesn't need admin rights either. Maybe I somehow magically learned to write viruses, I don't know :D

Source code: https://github.com/chenxiaolong/DualBootPatcher/blob/master/build/shortcuts/windows-exe.cpp

EDIT: Yep, some AVs don't like it. Let me see what I can do about it. https://www.virustotal.com/en/file/...5251eea2ef59982aed465246/analysis/1395291376/

EDIT2: If I don't compress the exe files with UPX, then only 2 antivirus software complain: https://www.virustotal.com/en/file/...f76e643a03a6ea718d7c0d61/analysis/1395291571/

EDIT3: So if I rewrite the launcher in C# instead of C++, the antivirus no longer complains... I don't get it. https://www.virustotal.com/en/file/...1f5a073c9bb396b6ffc14713/analysis/1395296960/
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Is there a simple way to move a Rom from Dual to Primary with all data, Apps etc. intact? I realise I can use a script to share Apps. I'm assuming a standard Nandroid Backup/Titanium Backup would not reinstall correctly due to path issues?
[Galaxy S 4 i9505 Original Android Development] Mussels84:
some antivirus are just crap, its their heuristics algorithms complaining, your code looks like a generic virus.

you could complain to them one by one, and then have it fixed a month after you've changed to a new version they detect as a new virus :P
[Galaxy S 4 i9505 Original Android Development] qtwrk:
Finally, 404r14 is working on the phone without crash, thanks man!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Awesome! :D I finally figured out how to compile the latest Python 3.4.0 for Android (we were on 2.7.6 earlier), so I guess that fixed everything.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Gah, antivirus false-positives are so annoying. Yesterday, the windows exe launchers (written in C++) had 4 false-positives, so I rewrote them in (C#), and now there's only one false-positive (yay).

[MENTION=4251861]qtwrk[/MENTION], would you mind testing the PC version of 4.0.4.r15? ESET shouldn't complain about it anymore. Thanks!
[Galaxy S 4 i9505 Original Android Development] gaww:
Not yet. Duel Boot backup/restore will be set up to do that down the road. Titanium can restore your user apps from anywhere you are booted in at the time
[Galaxy S 4 i9505 Original Android Development] qtwrk:
Will do once back home.

One more thing I noticed quite annoying

If I installed secondary system, and then use TWRP to backup, TWRP continuously crashes, I guess due to large partition?
[Galaxy S 4 i9505 Original Android Development] gaww:
I don't think the size is an issue. Between TW primary and noobdev secondary, my system partition s almost full. Then the cache and data combined are much larger than that (you have to back up cache if you want everything).

I have made a number of backups with TWRP. They are very large (even compressed) and take quite a bit of time, so you are having some other issue.

Note - I am still using 2.5.0.2
[Galaxy S 4 i9505 Original Android Development] qtwrk:
Oops, I'm on 2.7.0.1, however I could backup with Phliz...
[Galaxy S 4 i9505 Original Android Development] gaww:
I was thinks of updated to that TWRP version but think i will stand pat - lol.
[Galaxy S 4 i9505 Original Android Development] qtwrk:
confirmed ,404r17 ,ESET doesn't hate it any more for whatever reason it had :fingers-crossed::fingers-crossed:

thanks for your efforts :good:
[Galaxy S 4 i9505 Original Android Development] gravedigger76:
So I tried GoldenEye as well as both skyfall version and all 3 have the camera crash the same way :(

Anyone found anything? This is when installing in dual. [MENTION=427477]chenxi[/MENTION]along

Any ideas by chance?
[Galaxy S 4 i9505 Original Android Development] qtwrk:
Goldeye v26 seems to be fine?
[Galaxy S 4 i9505 Original Android Development] gravedigger76:
No. Camera crashes on v26 just the same. :(
[Galaxy S 4 i9505 Original Android Development] qtwrk:
You mean on secondary system or what?

Primary goldeneye v26 and carbon in secondary, camera works fine on goldeneye
[Galaxy S 4 i9505 Original Android Development] gravedigger76:
My original message had that info--- referring to dual partition.
[Galaxy S 4 i9505 Original Android Development] qtwrk:
Well, sorry for that, I just got here for dual boot things, would you mind repeat it again?
[Galaxy S 4 i9505 Original Android Development] marvi0:
Any solution with trying to patch gapps please?. I keep getting an error trying to patch using app on my phone?
[Galaxy S 4 i9505 Original Android Development] gravedigger76:
There are plenty of solutions. But to get them you will need to provide relevant info and not just I'm getting an error. Good luck.
[Galaxy S 4 i9505 Original Android Development] marvi0:
Thanks am getting unsupported file?
[Galaxy S 4 i9505 Original Android Development] qtwrk:
He also wants know what Gapps... They are many different Gapps
[Galaxy S 4 i9505 Original Android Development] gravedigger76:
Read the OP for supported packages. Try PC latest beta. Search the thread.
[Galaxy S 4 i9505 Original Android Development] Technical:
I've managed to install FoxHound as secondary ROM if I install, like instructed, the stock kernel (and not KT) within Aroma installer of the ROM.

Now I need to manage WiFi in FoxHound as it is not working.
[Galaxy S 4 i9505 Original Android Development] bubba949:
Try going into the secondary Rom's build.prop and changing "ro.securestorage.support" from false to true or vice versa, reboot and see if that works.
[Galaxy S 4 i9505 Original Android Development] Technical:
It was not necessary. Just flash 4.6.1 and the WiFi is there. Thanks anyway.
[Galaxy S 4 i9505 Original Android Development] gravedigger76:
@RK, [MENTION=4277844]chenxiaolong[/MENTION]

So i tried a few more 4.4.2 TW ROM's as dual - ShoStock one of them,

All are having camera crash the same way as Goldeneye and Skyfall

So it's not ROM or dev, it's something with patching for 4.4.2 :(

Have you been able to check on this by chance yet?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
@RK, [MENTION=4991991]gravedigger76[/MENTION]: Thanks for the all the testing you guys did! I have a lot of schoolwork to do this week and probably won't get to fixing these until the weekend.
[Galaxy S 4 i9505 Original Android Development] debbuger:
OK everything works fine.I have slimkat on secondary boot..everything works fine..tried some scripts for sharing data partition but nothing works...any hope for sharing apps?I don't use launchers etc etc but I have to many apps installed in primary ROM .I can't install them again don't have enough space left on my s4...if anyone knows a solution plz help.
[Galaxy S 4 i9505 Original Android Development] marvi0:
I didn't know this was possible to share apps on primary rom. I have pa 4.3 on primary rom and slimkat on secondary and very much interested in this as well.
[Galaxy S 4 i9505 Original Android Development] debbuger:
I found a script for s3 that does the same but not working on s4... I have tried many times.
[Galaxy S 4 i9505 Original Android Development] gravedigger76:
Search thread here. Scripts were posted and work like a charm. Sorry don't remember who posted them to give credit but make sure to thank him in the post when you find it.
[Galaxy S 4 i9505 Original Android Development] debbuger:
I can't find anythingfor s4..only for s3 are there.and those r not working.
[Galaxy S 4 i9505 Original Android Development] sronweb:
I'm a fresh user of S4 since few days and I have already rooted my phone:p installing Cyanogenmod as second rom using this great topic.

My question is related the "sim lock" feature which I should have on stock Samsung rom. I guess that the sim lock its' at kernel level (I'm not sure), then I wonder if this limitation will appear on the second rom as well if I get another region sim.
[Galaxy S 4 i9505 Original Android Development] anned20:
Then it will be very easy to remove the sim lock ;)

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Original Android Development] sronweb:
I have seen some procedures to remove the sim lock using sammy service menu. Then if I understood correctly it should write on internal memory and should not be related to rom version or kernel.
[Galaxy S 4 i9505 Original Android Development] gaww:
Maybe move it over to slot1 if you are not currently using any slots (you should have enough room there unless your internal SD is totally maxed out).

Below is a link to a app that will move it over without the need to reinstall.

http://xdaforums.com/showthread.php?t=2491299
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Can't patch Eclipse S4 v3.0: http://www.androidfilehost.com/?fid=23329332407578777 with windows or android anyway to have this added please?
[Galaxy S 4 i9505 Original Android Development] sronweb:
Please, do you know why since I'm using these patches I have difficult to enter in recovery mode? Basically I see the Samsung logo and recovery on top but then I get black screen or start the primary rom. I have tried both CWM and TWRP but I'm not sure if this due to some wrong procedure. I have i9505 European sim free version.

Also there is another doubt: the procedure on the OP says that I can flash directly the primary rom or the patched secondary rom. But I suppose we should better clean cache or dalvik for example in case of upgrading or format data in case of new rom. Is it correct?
[Galaxy S 4 i9505 Original Android Development] gaww:
You did not say which secondary ROM you are trying and what version of patcher (PC or app on device). If you are using noobdev as secondary, you have to enable duel boot first (as in noobdev OP).
[Galaxy S 4 i9505 Original Android Development] sronweb:
You are right!! I had the original TW rom as primary (rooted) and yesterday I flashed TouchliteGE as new primary. I use official CM11 nightly as secondary. I have flashed the recovery using odin but I have tried also with zip files and I have difficult to get to the recovery menu using classical procedure (vol+, pwr, home button press at the boot) or if from CM11 I select reboot/recovery. Then most of the cases the primary rom starts.

For flashing I have patched the secondary rom using the apk from the primary and flashed from recovery but most of cases I can access to recovery only after new recovery flash via odin.

I have just repeated the sequence on "Instructions for dual booting" but when I select boot to recovery it starts the primary rom and not the recovery.

PS: now I'm testing different kernel version as OP.
[Galaxy S 4 i9505 Original Android Development] Bejda:
Try to start your S4 normally and just press Volume Up button (of course maintained until you see "recovery booting" message) right after device start vibration.
[Galaxy S 4 i9505 Original Android Development] mahasmb:
How do you ... errr... flash GApps after setting up the dual-boot?

So I have stock TouchWiz as my primary and Cyanogenmod 11 as my secondary. Patching the KitKat GApps (4.4.2) with the Dual Boot Patcher tells me the file is not supported.

Would I just have to wait until KitKat GApps are supported?
[Galaxy S 4 i9505 Original Android Development] sronweb:
I would recheck the original gapps if its ok (perhaps download was not completed?) and try to download again. I have patched gapps-kk-20140105 and they can be flashed for secondary rom as CM11.

---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------

Thanks. Something strange but not regular. Sometimes works and sometime not. I notice that on reboot the text on top of Samsung logo is different (I cannot read, too small!!). I have reflashed Phil kernel and seems to work better.
[Galaxy S 4 i9505 Original Android Development] Technical:
Edited
[Galaxy S 4 i9505 Original Android Development] Technical:
Is there a way to flash a primary ROM OTA and do not need to flash the secondary again to get access to it?

I mean, when I flash a primary ROM I "lose" the kernel settings for booting the secondary. Only flashing the secondary again allows the correct boot again.
[Galaxy S 4 i9505 Original Android Development] mahasmb:
Thank you very much for your response but I have triple checked the md5sum for the gapps-kk-20140105-signed.zip and they match.

I have tried using the Dual Boot Pather v4.0.4 to patch the Gapps and then tried to use v4.0.0. They both give me a "Failed to patch zip file: Unsupported zip" error no matter which option (Normal Android Way or File Way) I use.
[Galaxy S 4 i9505 Original Android Development] rlorange:
Search for Paranoid Android Zero day gapps on.XDA 'Full Modular' is the best version and it will patch just fine

---------- Post added at 09:45 PM ---------- Previous post was at 09:44 PM ----------

http://xdaforums.com/showthread.php?t=2397942

here's the link
[Galaxy S 4 i9505 Original Android Development] Bejda:
Rename the zip,replace "kk" by "jb" and it should work fine.

You can check patchinfo>Google_Apps folder of patcher zip version to see which file name is expected for cyanogenmod gapps (gapps-cyanogenmod.py file)

And If a file name check needs an update let's ask Chenxiaolong to edit next version ;)

For now,as it's just a gapps pack and Android 4.3 or 4.4 doesn't really matter here,a simple rename to match its .py file should work just fine.

In that Google_Apps folder you'll see others supported gapps packs btw.

[MENTION=4277844]chenxiaolong[/MENTION],

BaNkS Core gapps are now named "Minimal" instead of "Core" :)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I'm agree, I take those there also.
[Galaxy S 4 i9505 Original Android Development] spinacz100:
if i choose miui oficial i must have miui kernel for it -> http://xdaforums.com/showthread.php?t=2306650

can You add support for this kernel ?

i cant patch any kernel ;/
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It's probably time to do a stable release after the 17 beta releases :)

Changes in version 4.1.0:

TouchWiz ROMs and Kernels

Add support for GoldenEye ROMs beginning with "GE-i337"

Add support for Echoe v17 (patches all kernels in zip)

Add support for ktoonsez's TouchWiz 4.4 kernel

Add support for SkyFall

Add support for EclipseTW

AOSP-based ROMs and Kernels

Add support for PAC Black Power Edition NG

Fix regex for OSE so any filenames beginning with "OSE-" will work

TouchWiz 4.4 fixes

Use custom compiled AOSP init binary (see source repo for code patches)

Fix sound my setting 666 permissions for /dev/snd* sound devices

Google Apps Packages

Add support for CyanogenMod KitKat Google Apps package

Add support for BaNkS' standard and minimal Google Apps packages

General improvements

Add support for patching multiple kernels in a single zip file

Upgrade Python for Android and Windows to 3.4.0 (fixes segfault on Android)

Upgrade Windows PyQt5 libraries to 5.2.1 (compiled against Python 3.4.0)

Rewrite Windows' exe launchers in C#, because fewer antivirus software complain (even the code is nearly the same as the old C++ launcher)

unlokibootimg: Fix extraction of ktoonsez's boot images caused by multiple instances of the 4-byte gzip header identifier

Android GUI changes:

Target API 19.0.3

Oh yeah, one thing I don't think I mentioned before: do NOT ever choose the wipe /data option in AROMA ROM installers. These will wipe data for every ROM that's installed. Use the dual boot utilities for any wiping you need to do.

Tagging people who made the requests :)

[MENTION=2465635]ahoslc[/MENTION]

[MENTION=2025370]mahasmb[/MENTION]

[MENTION=3648432]Bejda[/MENTION]
[Galaxy S 4 i9505 Original Android Development] Mussels84:
poor bugger - its already behind! echoe's V18 has been out for a few days :P
[Galaxy S 4 i9505 Original Android Development] chavdar:
I cannot use the 4.1.0 on my device - same as the beta 17. It opens and FCs immediately.

Sent from the GT-I9505 Galaxy
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Did you try to erase the datas?
[Galaxy S 4 i9505 Original Android Development] RK:
Just rename the zip file to 17..
[Galaxy S 4 i9505 Original Android Development] Mussels84:
i know - i gotta poke the echoe guys to make sure their naming scheme is more standardised.
[Galaxy S 4 i9505 Original Android Development] AnaMajhol:
Hi.. Thanks very much for this awesome tool but I have a problem here :(

I'm currently booting TW as primary and GE as secondary.. So the problem is that I can't switch from TW to GE from your app - Every time I want to switch from primary to secondary I have to go to recovery and use your zip.. I tried cleaning data of the app but no hope.. (I can go from GE to TW normally but not viceversa)

Thanks.
[Galaxy S 4 i9505 Original Android Development] Bejda:
The app gives a message when you try to switch from TW to GE? Acts normally and says "successfully switched" or fails?
[Galaxy S 4 i9505 Original Android Development] chavdar:
Yes I did - even full uninstalled and then did a clean one...

Sent from the GT-I9505 Galaxy
[Galaxy S 4 i9505 Original Android Development] allan1313:
I am having 2 issues. I can't get the latest dual patcher to work, it always force closes. Also I can't patch ktoonsez latest kernel with the patcher. Any help is appreciated.
[Galaxy S 4 i9505 Original Android Development] gaww:
Also did you first set the secondary kernel ?
[Galaxy S 4 i9505 Original Android Development] allan1313:
Can AICP rom support be added as well?
[Galaxy S 4 i9505 Original Android Development] AnaMajhol:
Thanks for reply.. Yes it it says "successfully switched"..

Thanks for reply.. Yes I did

---------- Post added at 01:58 PM ---------- Previous post was at 01:18 PM ----------

And this is a video :

[YOUTUBE]B1AjOFHXz34[/YOUTUBE]

Edit2: After 2nd boot to GE ROM I can no longer go to the primary TW rom .. When I try from the app or the flashable zip it always boots 2nd GE ROM :(