yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chavdar:
Will do that and post the recovery log.But the strange thing, is that the same file (Echoe_KK.2.2) gets flashed with no comments with 6.07

I also have the same issue with Jamals KK R1.2, also using 6.13.1

Maybe you can try flashing those roms just for the fun of it :D
[Galaxy S 4 i9505 Original Android Development] Bejda:
:)

Since Philz 6.09.6 version there's a check for updater-scripts set_perms failures and Echoe updater (on both TW and GE roms) set permissions for two file that doesn't exists in the zip,/system/etc/dbus.conf and init.goldfish.s

You could remove these lines or use Philz up to 6.09.2 version.
[Galaxy S 4 i9505 Original Android Development] gaww:
If you had previously flashed and booted a secondary ROM with it, then you are probably right. I only had trouble flashing secondary ROM's with that version - other things I flashed with it were ok.

Just to see if it is the patching giving you trouble, you might want to try flashing a noobdev ROM (modded CM11) and see if it boots up. You would have to run the enable duelboot zip from the OP first.
[Galaxy S 4 i9505 Original Android Development] Technical:
[LINK] Dual Boot Patcher

[LINK] Dual Boot Switcher app

[LINK] DualBootUtility zip

Do you mean the first "dual boot patcher"?
[Galaxy S 4 i9505 Original Android Development] Bejda:
Gaww meant that you could give a try to Chenxiaolong's Noobdev builds to see if things differs:

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

The rom is "pre-patched",if you want to flash it as secondary you just have to flash before the dual-boot enable zip that you'll find there under dual-boot instructions.

[MENTION=4277844]chenxiaolong[/MENTION],

LiquidSmooth rom builds are now named LS-KK- ...a little tiring isn't it? :)
[Galaxy S 4 i9505 Original Android Development] gaww:
Yeah - I forgot to mention which OP - me bad.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
lol... Fixed now ;) https://github.com/chenxiaolong/DualBootPatcher/commit/c637e6ad59a3c5e4837883c6e6c6788b8dd8845e
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Version 4.0.2 is now released :) Changes:

Remove generic boot.img support. Use the GUI patcher or patch-ramdisk script instead.

Add support for patching unsupported boot.lok files by unifying the file type detection code in the CLI and GUI programs

Add support for BlackBox 2.2

Add support for Echoe v14, 14.1 (untested)

Add support for jamal2367's Google Edition version R1.1 final

Add support for jamal2367's old Android 4.2.2 build

Add support for LiquidSmooth Kit Kat

Add support for AOSB

Add support for Bobcat Google Edition

Add support for SHOstock (TW4.4 tested)

Fix bug where the newly flashed kernel for devices needing loki is not saved properly

Fix modem partition mounting in TouchWiz 4.4 ROMs -- Fixes unknown baseband bug
[Galaxy S 4 i9505 Original Android Development] gaww:
Question on finding space to flash a TW 4.4 ROM in multiboot.

I think duel boot only shares /system with primary, and the slots with the same cache. So if I clear out all present slot ROMs, will that create enough space?
[Galaxy S 4 i9505 Original Android Development] Bejda:
That's it but..

:o
[Galaxy S 4 i9505 Original Android Development] gaww:
But (did not need those comments reposted - I was well aware of them) - I am looking at smaller ROMs than Echoe 14, which those comments referred to. Also, have tried debloating the ROMs I am trying to get them smaller.

Plus - given the above - if Echoe 14 was too big to install - just what is the reason for making it patchable "Add support for Echoe v14, 14.1 (untested)at this point" - unless it will only fit in /system/duel if there is a VERY small primary (whats the point then - make it the primary...)?

As for "support for SHOstock (TW4.4 tested)", was that patched with 4.0.2 (app or PC), flashed and booted successfully? If so - was it installed as secondary, or installed in a slot ?
[Galaxy S 4 i9505 Original Android Development] Mussels84:
i installed echoe v14 myself and it worked, but i slimmed it down first.

with previous echoe releases, they had slim and ultra slim releases that worked perfectly with dual boot. now, they've got it in an aroma installer - so you should be able to patch, install as 'slim' and it should fit fine. cant say for sure how that setup works, as it may need the full space to unpack.
[Galaxy S 4 i9505 Original Android Development] chavdar:
Hi chen,

I tried patching SHOstock but it says "Failed to extract lok". Is this issue known? I tried on the beta 3
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
SHOstock was also too big. For testing, I removed a few apks** to make it fit in an empty /cache. I've tested it in both /system/dual and the multislots and they both work.

Like you, I don't see much point in dual booting these ROMs. They are simply way too big.

**

SamsungLearning.apk

Drive.apk

Hangouts.apk

MobilePrintSvc_Samsung.apk

Peel.apk

SamsungWatchON.apk

SBrowser.apk

SecEmail_J.apk

Dropbox.apk

SecCalendar_SPen.apk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I just double checked and it worked for me. Are you on the version 4.0.2 of the patcher? The version of SHOstock I tried was "SHOstock-i-v5.0b3.zip".
[Galaxy S 4 i9505 Original Android Development] chavdar:
Yes. I tried with the PC version. But the name is not the same: SHOstock-i-v5.0b3-i9505.zip

It gets recognized, but cannot be pached. Treid several times. I will now try with the .apk and get back to you

P.S: Re-downloading again... maybe there was a problem with the download.

[MENTION=4277844]chenxiaolong[/MENTION]

OK, I redownloaded the file again and still get the same error - Failed to patch file. Failed to extract file: boot.lok

I suspect we a are talking about two different versions of the same ROM - this is the ported one for the I9505 jfltexx and it has no boot.lok.

Could this be the problem?

Here is the thread:

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

I really what to try it :)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Doesn't work for me either and another user! That mustn't to be a download issue. :(
[Galaxy S 4 i9505 Original Android Development] wingg:
Patching method for SHOstock-i-v5.0b3-i9505.zip that works for me:

1. manually delete some bloat-( this ROM can be shrinked to 686mb and works)

2.rename ROM to a.zip

3.Use PC version of patcher 4.02 to patch (windowsGui) with custom settings posted here before by [MENTION=4277844]chenxiaolong[/MENTION]

Regards

//->>
[Galaxy S 4 i9505 Original Android Development] Technical:
I'm in a bootloop stopping at the S4 logo.

I've wiped everything in secundary, installed patched OMNI and PA gapps. Have set 1st kernel before flashing.

Can't boot the secundary. Tried to use BootUtilities to boot in primary again. It worked once. The second time, bootloop both for primary and secundary. Need to restore a nandroid.

TWRP 2.6.3.1

What am I doing wrong?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
What have you removed in this rom?
[Galaxy S 4 i9505 Original Android Development] wingg:
Same things as known in TW 4.3 to be safe removable:

from system/ i`ve deleted folders:

-preloadedsso

-opticalreader

-preloadedkiosk

-voicebargeindata

-wakeupdata

from media/:

-video

from sipdp/:

-some lang. files that i don`t use

from tts/:

lang_SMT

tts/lang_SVOXP/all files only svoxkeys.txt left

from VODB/:

-some lang. files that i don`t use

from system/app:

-Allshare ->Castplayer -ControlShare

-Drive

-Dropbox

-GoogleSearchWidget

-Hangouts

-MobilePrintSvc_ all files

-Music2

-MusicLiveShare

-Peel

-PickUpTutorial

-Samsung;-Learning,-OCR,-Music10-TTS, -WatcON

-SBrowser, SBrowserTry (I Use ASOP Browser)

-sCloud - all files

-SPlanner..

-SViewCover...

-S_Translator..

-SPrintSpooler.

-Yahoo - all files

from system priv-app:

-GroupPlay_25

-SVoice

-SecWallpaperChooser

-SMemo2

-SNoteProvider

-SNS

-Velvet

from libs :

some corresponding to removed apps for example bigger ones:

libDioDict4EngineNativeService.so;libDioDict3EngineNativeService.so libDioOcrEngine.so(~6mb)

libearth.....-> 2 files (10mb)

libpolaris....->7 libs (>40mb)Polaris Office

libSamsungTTS(4mb)

libsbrowser.so(30mb)

lbgoogle_recognizer_jini(10mb)-GogleNow(Velvet)

libstoryalbumEffectEngine.so(4mb) StoryAlbum

libsnote_core.so(8mb)

.....and some smaller

Of course deleting to much may cause : bootloop .

Regards

*edit

Removed HwModuleTest.apk from list (it may cause bootloop )
[Galaxy S 4 i9505 Original Android Development] gaww:
I finely got it patched, flashed and booted. After all that - many issues - worst being no network - says to insert SIM. Oh well, don't know if I really want two TW's running - lol.
[Galaxy S 4 i9505 Original Android Development] Bejda:
What should work also for SHOstock rom is to use PC 4.0.2 patcher version but before go into DualBootPatcher-4.0.2-jflte/patchinfo/jflte/ROMs/TouchWiz/ to edit shostock.py file:

file_info.bootimg = 'boot.img'

Instead of boot.lok

Delete:

file_info.loki = True

And then patch the rom.

+ Philz users should use up to 6.09.2 version, otherwise you'll get unknown baseband and imei.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sorry for the confusion, it's the AT&T version of SHOstock that's supported. Because of the patcher's unloki feature, a patched version will work on any device, even the ones with unlocked bootloaders :)
[Galaxy S 4 i9505 Original Android Development] nicholi2789:
Dang, Danvdh and Ktoonsez's Google Edition rom (for Verizon here: http://xdaforums.com/showthread.php?t=2643031) is still unsupported. On the last version of the patcher it wouldn't patch the ramdisk so I couldn't manually patch it. But on this one if I drop the boot.img onto \useful\patch-ramdisk-loki it says "file not supported, will attempt auto-patching" then after I select GoogleEdition the dualboot it says it sucessfully patched it. I'm gonna do a nandroid and flash it. Hopefully I modified the updater-script correctly and everything will work. Then maybe I can get it included in the patcher. We'll see. Knowing me I messed it up somewhere.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
You could install quiet after?

Edit

:

And why don't easily change this:

file_info.bootimg = 'boot.lok'

by that:

file_info.bootimg = 'boot.img'

Because with that I saw in the foxhound.py file, it indicates the location of kernel file.

Edit 2

:

SORRY!!! This is what you wrote... :eek:
[Galaxy S 4 i9505 Original Android Development] Bejda:
I tried in the meantime yes,i didn't kept the rom so can't say much but installation and boot went fine.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
SHOStock, I installed it, installation without issue but... no network, nothing, no modem or IMEI, I freaked out a little but not more than that because I have quite a backup of my EFS folder including one that was made by a rom, surely AOSB. I returned it to see if the same on AOSB, but no, everything is OK! So why the problem? Is what is in the secondary?
[Galaxy S 4 i9505 Original Android Development] Bejda:
Reflash rom Philz 6.09.2 or another recovery, baseband and imei will be back ;)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I gonna try that. And after, you could put again the last phiz or not?

Edit

:

Ok, it works fine now!
[Galaxy S 4 i9505 Original Android Development] chavdar:
Do you have sound? I got everything working whit SHOstock except sound...

Sent from the GT-I9505 Galaxy
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I didn't test that, I gonna check it and I'll say you.

EDIT

:

You're right, there is a problem with the sound! : (

EDIT 2

:

It even creates big slowdown when trying to touch something to do with sound.

---------- Post added at 05:05 PM ---------- Previous post was at 04:16 PM ----------

[MENTION=404574]chavdar[/MENTION]

What is ur modem?
[Galaxy S 4 i9505 Original Android Development] chavdar:
GSM_Modem_XXUEML6_and_LTE_Modem_XXUBMH1...

I think this is an issue with the lack of a new bootloader...

But since 4.4.2 is currently a leak, I will wait untill a proper solution comes with for the very first bootloader, to which I am still very attached :)
[Galaxy S 4 i9505 Original Android Development] Technical:
I beg for help :angel:
[Galaxy S 4 i9505 Original Android Development] gaww:
I had same results with TWRP 2.5.0.2. Installed on slot 1 (with nothing in the other slots). On deleting all the slot 1 files, I found it had somehow messed up secondary (noodev) and it took quite a bit of doing to get that working without issues.

Did not think it would impact primary/secondary - but it did.
[Galaxy S 4 i9505 Original Android Development] zhuchella:
chenxiaolong

Can U add the support of dualboot for this http://xdaforums.com/showthread.php?t=2382805 ? Thank U

And how can I back to oneboot system without wipes?
[Galaxy S 4 i9505 Original Android Development] Bejda:
I would use point 2:
[Galaxy S 4 i9505 Original Android Development] ntajlis:
I love how your dualboot works without needed a specific custom kernel patch. It been working flawless for me. I'll buy you a beer when I get paid.

SPH-L720_!
[Galaxy S 4 i9505 Original Android Development] davidep85:
Hi! I have Omega rom as first rom with Abyss Kernel, is that supported?

http://www.nonsolosmartphone.it/abyss-gt-i9505-kernel-for-samsung-rom-only-t6511.html

Regarding Slim Bean I only have to patch both rom and slim gapps right?

Thank you!!
[Galaxy S 4 i9505 Original Android Development] Bejda:
No need to modify primary rom,no support needed.

You just have,on Omega,to open dual boot switcher app and set current kernel as primary rom's kernel.

Only patch Slim rom and its gapps.
[Galaxy S 4 i9505 Original Android Development] davidep85:
thanks mate I'll try! so no problem with abyss kernel compatibility?

Inviato dal mio GT-I9505 con Tapatalk 4
[Galaxy S 4 i9505 Original Android Development] Bejda:
No compatibility question regarding primary rom and whatever kernel it use ;)
[Galaxy S 4 i9505 Original Android Development] davidep85:
Ok flashed, all is fine except I have no root on Slim Bean, how can I solve?
[Galaxy S 4 i9505 Original Android Development] ntajlis:
You either flash OP supersu_dualboot or download it from Google play store.

SPH-L720_!
[Galaxy S 4 i9505 Original Android Development] davidep85:
All is working fine now! thanks everyone for the quick support! I'll do some tests :)

Inviato dal mio GT-I9505 con Tapatalk 4
[Galaxy S 4 i9505 Original Android Development] Bejda:
Known story on 4.3 aosp based rom I guess,see the big red lines on Slim thread:

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

And to make developers options visible you have to tap 7 times on settings>about phone>build number.
[Galaxy S 4 i9505 Original Android Development] davidep85:
thanks I'll try this way.. now I have flashed supersu_dualboot and is not working fine with slim Bean..

the biggest problem is that when I reboot into aosp rom, it get stucked on samsung logo. when I remove and re insert battery then it works..

Inviato dal mio GT-I9505 con Tapatalk 4
[Galaxy S 4 i9505 Original Android Development] Bejda:
Well it happens sometimes more or less frequently,nothing related to dual boot.

Some peoples see a relation with recovery version used but I don't believe so,it happened or happens to me on any rom and any recovery version (maybe more or less frequently depending on recovery used,maybe...)

Force a reboot by long (very long,until device shutdown) pressing power button when on Samsung splash screen usually does the trick,sometimes two times necessary.
[Galaxy S 4 i9505 Original Android Development] Masami1975:
Please guys, thank you before, I've some questions...

Can I flash Dualboot utilities.zip from CWM?
[Galaxy S 4 i9505 Original Android Development] Bejda:
It's made for yep,will leads into aroma interface.
[Galaxy S 4 i9505 Original Android Development] Masami1975:
I'm bit confusing...

I start from clean deodexed and rooted MGA Touchwiz rom

I've to:

1-Install dual boot switcher apk

2-choose kernel from the app

3-patch the 2nd rom

4-flash dual boot utility and 2nd rom from recovery

5-install dualboot switcher apk in the 2nd rom

Is it correcto or I've to patch also 1st rom zip??
[Galaxy S 4 i9505 Original Android Development] Bejda:
You're right,no need to patch primary rom.

Just to be sure:

Point 2 is,on primary rom,to set current kernel as primary rom with the app.

Point 4: Just flash your patched rom,keep dual-boot utilities zip on your sd for when you'll need it.

Point 5 : Install dual-boot boot switcher app on secondary for you can switch to primary><secondary rom using the app but set secondary kernel is optional.

Point 0 ;) : As your primary rom seems to be a full Samsung firmware make sure you'll have enough place under /system to install a secondary rom.
[Galaxy S 4 i9505 Original Android Development] Masami1975:
thanks Bejda! but I've to flash dual boot utilities or not?? So when I need it???

Edit: it's superslim from Djembey so some bloatware is deleted
[Galaxy S 4 i9505 Original Android Development] davidep85:
I have re-installed slim bean.. I can confirm that root has problem. With integrated and enabled superuses, root works but only for external apps. For setting (ex. dpi change etc) it doesn't work.. The same for flashed supersu. I'll try another rom!

Another problem with the zip in recovery. When I try to wipe secondary system, it works but when I try to format secondary data or cache, it says Device or resource busy, does it works anyway?
[Galaxy S 4 i9505 Original Android Development] angeloumbao:
Can i use phoenix as primary and slimbean as secondary? I mean do i need to patch both or just the secondary?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
For my part, I think the problem is that I put the rom SHOStock like secondary rom, it is written in the post OP, that TW Rom are to put preferably like primary rom, to avoid any problems.

Like this:
[Galaxy S 4 i9505 Original Android Development] franzyroy:
All works fine now with my DualBoot now

First rom (SHOStock v5.0b3) installed with Philz recovery 6.09.2 (forgot to try with the last :silly:)

Installed Philz recovery 6.15.4

Installed DualBoot switcher

Wipe all data with DualBoot utilities

Installed Second rom (AOSB v1.2.9))

All works fine without issue!!!
[Galaxy S 4 i9505 Original Android Development] Bejda:
Philz recovery unknown baseband&imei problem is not related to dual boot it's just that Touchwiz 4.4 roms should use set_metadata on their updater-scripts (like 4.4 aosp roms) instead of set_perms but yeah i could test these two SHOstock and BlackBox rom as multislot's roms and found them pretty buggy.

Just as you and Chavdar no sound with SHOstock (ok for you now as primary? ) although i'm under 4.4 NA5 bootloader + lags,freezes,blackscreens etc...

And same as others reports for Blackbox = Rom Control fc (while apparently it's ok when rom isn't patched) and here also some bugs for me like blackscreens too,root issues,apps uninstalled after reboot etc..

It seems indeed these two rom runs bad as multislot (at least on my side,can't say if patched/used as secondary as i didn't tested) but i don't know why..first time i face such issues.

Indeed for many others reasons it's preferable to use Touchwiz roms as primary but usually it doesn't cause such issues, strange.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I spoke too quickly, after reboot, second rom (AOSB) had lost the IMEI code, it was even written MEID instead of IMEI... so I put again Philz recovery 6.09.2 and install again AOSB like secondary rom with all wipes. All is fine now, even after reboot.
[Galaxy S 4 i9505 Original Android Development] wingg:
I've been testing SHOstock 5.03b as multislot_1.( recovery Philz 09.02)

Deleted additionaly SecSetupWizard2013 and some CSC files.(1st setup goes throuh SerupWizard)

Issues only two so far : 1. No sound. 2. Can't install apks.

My thougt about issues : jeboo kernel(patched stock sammy) used in SHOstock after patching not fully works.

(Before i've tested SHOstock 5.02b as primary and there was no problems with sound)

Regards

//->>
[Galaxy S 4 i9505 Original Android Development] franzyroy:
There is no problem putting in primary.
[Galaxy S 4 i9505 Original Android Development] RK:
I updated my app share cwm zips. They now wipe delvik cache

As a reminder, these zips:

- Share FREE USER apps between primary and secondary (or multi slot) ROMs

- Wipe delvik cache for the secondary (or multi slot) ROM

- Need init.d support in the secondary (or multi slot) ROM

User data, system data, system apps, and paid user apps are NOT shared.

If your secondary (or multi slot) ROM does not support init.d, try the "init.d toggler" app from play store.

All credits to [MENTION=5262999]mkhattat[/MENTION] I just packaged his idea in CWM zips. His original post:

http://xdaforums.com/showpost.php?p=46537673&postcount=544

Downloads:

http://d-h.st/users/RK/?fld_id=32918#files
[Galaxy S 4 i9505 Original Android Development] Chaos ^_^:
anybody mangae to patch any 4.4.2 TW kernel

the patch app report as unsupported for any kerneal I tried to patch
[Galaxy S 4 i9505 Original Android Development] franzyroy:
[MENTION=4277844]chenxiaolong[/MENTION]

Hi,

I've a little issue, I've also made some multiboot on my PC, and it's with that I've this issue. DualBootPatcher-4.0.2 works fine on a system but not the other. You'll say me that's not your problem, only I think yes. I explain me.

On Windows 7 x64, it works fine

On Windows 8.1 x64, no, and I've "0xc000007b" like error, I've another before but I correct it with "msvcr100.dll", that I've put in "Windows/System32" and "sysWOW64". I've tried with netframework for 8.1, an update, but nothing.

Do you know a solution?

Displayed issue

:
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Sorry, I didn't see that! :( I gonna try it.

Edit:

What I had already installed the 64-bit version:"Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)", I've Windows 8.1 x64 on my PC. I'll try anyway because sometimes it takes both, as java example.

Edit 2:

Doesn't work! :(
[Galaxy S 4 i9505 Original Android Development] ipois0n1:
how about omega rom? would be awesome, since it's one of the most used rom
[Galaxy S 4 i9505 Original Android Development] franzyroy:
About that!

I've made that:

First rom (SHOStock v5.0b3) installed with Philz recovery 6.09.2 (forgot to try with the last :silly:)

Installed Philz recovery 6.15.4

Installed DualBoot switcher

Wipe all data on the partition of secondary rom, with DualBoot utilities

Installed Second rom (AOSB v1.2.9))

First start-up, all works fine

Corrected the Youtube issue by the modifiaction of build.prop

Reboot to apply the correction

After reboot, second rom (AOSB) had lost the IMEI code, it was even written MEID instead of IMEI...

So I put again Philz recovery 6.09.2

Wipe again all data on the partition of secondary rom, with DualBoot utilities

Installed again Second rom (AOSB v1.2.9))

All is fine now, even after reboot.

In conclusion, I still doubt that there is not a problem with the Philz recovery. It is great but there is something which creates an issue with IMEI at least.

I would like to know because, since I installed it, I have no desire to change it. :crying:
[Galaxy S 4 i9505 Original Android Development] Technical:
I'm starting to doubt on TWRP 2.6.3.1 that I'm using... But in my case, I'm not being able to boot the secondary ROM.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
So I can't complain! :D
[Galaxy S 4 i9505 Original Android Development] Technical:
Indeed you can, until the point the devs be angry, that's not good :D