yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] _Sofos_:
1st. Pac Metallica's Black version (aosp).

2nd. Foxhound lite version (TW).

Flawless so far, no lags, no freezes. Thank you very much!

I just wish there was a faster way to simply update the primary rom without all those changes/or flashes but still, impressed with what you've done and the support you provide here.

Keep it up :good:
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
Yup, all versions. I'm running it on Verizon right now

Sent from my dual boot PAC'd/touchwiz S4
[Galaxy S 4 i9505 Original Android Development] scott62185:
Wow, this sounds great!

If possible, can we get support for (for Verizon S4):

Vanir rom http://xdaforums.com/showthread.php?t=2439295 and

Smooth AOKP http://xdaforums.com/showthread.php?t=2439295

Thanks!

Also, question: Is it safe to assume that the AOSPA port for jfltevzw will work since it's already patched for other versions?

http://xdaforums.com/showthread.php?t=2291740
[Galaxy S 4 i9505 Original Android Development] Hecatrice™:
Can we help me??i don t understand!!:(

Inviato dal mio GT-I9505 con Tapatalk
[Galaxy S 4 i9505 Original Android Development] Hecatrice™:
Guys but I have to change the rom or the kernel with dualbootpatcher?

Inviato dal mio GT-I9505 con Tapatalk
[Galaxy S 4 i9505 Original Android Development] Nick0703:
If you patch a ROM then no need of patching a kernel. As the kernel inside the ROM will get patched.

But if you using another kernel beside the one that's included with the ROM, then you'll need to patch that also.

If you still don't understand then I don't think you should be doing this.
[Galaxy S 4 i9505 Original Android Development] Hecatrice™:
okay, now I understand ,but why when I tried to patch the ROM with dualbootpatcher (just like the picture of the guide) does not work for me?

Inviato dal mio GT-I9505 con Tapatalk
[Galaxy S 4 i9505 Original Android Development] Nick0703:
What ROM? If it's not supported then it won't work. Please check the support list!
[Galaxy S 4 i9505 Original Android Development] todivefor:
I just backedup dual while running dual. Is that OK? Doesn't look good:
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
it looks right to me, although i would not try to restore to same slot while it is in use.
[Galaxy S 4 i9505 Original Android Development] flexxoo:
This is my backup
[Galaxy S 4 i9505 Original Android Development] flexxoo:
No is not right look at the size
[Galaxy S 4 i9505 Original Android Development] rlorange:
No thats not good failed for some reason

---------- Post added at 06:27 AM ---------- Previous post was at 06:26 AM ----------

Yep that's perfect
[Galaxy S 4 i9505 Original Android Development] flexxoo:
I don't think that external backup works
[Galaxy S 4 i9505 Original Android Development] v00d007:
The "nothing happens" problem seems to only be related to the microSd. To my internal storage the backup and restoration of a dual cm12 rom worked.
[Galaxy S 4 i9505 Original Android Development] flexxoo:
Yep
[Galaxy S 4 i9505 Original Android Development] rlorange:
You guys trying to backup to external on which ROM version and from which slot?
[Galaxy S 4 i9505 Original Android Development] todivefor:
Backedup and restored to external without a problem.
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Tried this and it gets further booting but just sits for ages on boot animation. I no longer get kicked back to recovery so it's a step in the right direction ;)
[Galaxy S 4 i9505 Original Android Development] flexxoo:
In my case the app said backing up to no micro SD card any ideas?
[Galaxy S 4 i9505 Original Android Development] flexxoo:
Like this
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
I know you are looking at the sizes reported from internal multibackup dual folder, it may be mis-represented, below is a screenshot from when I was testing for [MENTION=3145598]rlorange[/MENTION] and even with the small sizes shown it still restored properly. Now my backups on internal and on external are showing much larger files.(Also note the files stored on external are considerably larger then those on internal.)
[Galaxy S 4 i9505 Original Android Development] flexxoo:
The problem is that the path is not reconized by the app and is not writing anything to the external sdcard, you did the backup on cm12 but try to do it in touchwiz to see if it let you because the paths are not the same one is sdcard1 and the other one is extSd and that's the issue
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Touchwiz 5.0 [MENTION=5804776]Kushan02[/MENTION] rom.......
[Galaxy S 4 i9505 Original Android Development] flexxoo:
This is the app in cm12 and I know for sure that is going to work because it shows me the path but in touchwiz not!
[Galaxy S 4 i9505 Original Android Development] flexxoo:
That's the same backup that you did in cm12 my friend you didn't do that in touchwiz
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
You are absolutely correct, I managed to fool myself! It ran the backup but did not store on ext sd.
[Galaxy S 4 i9505 Original Android Development] flexxoo:
See above this message for the external issue people have with touchwiz
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Crap! Fixed now :) I accidentally deleted it while cleaning out my public Dropbox folder.
[Galaxy S 4 i9505 Original Android Development] rlorange:
OK thanks guys for the help. The TW detection problem for extSDcard should be easy to.

It's particularity tricky to get consistency across binary versions and device models... Hence my rlbbox solution. I'll figure out what's going on.

I'm still on TW 4.4.4 primary so something must have changed in the paths
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
Dual boot on Sprint S4 SPH-L720

Hi Guys, I'm a noob and very late to this game. I need help to make dual boot working on my Sprint S4 (SPH-L720). Here's what I have done:

1) Primary system: Phoenix ROM 10 (tw 4.4.2). Installed DualBootPatcherAndroid-8.0.0.r1083, set primary Kernel.

2) Secondary system: Patched Albe95's rom (tw Lollipop 5.0.2) in primary system. Option used: Device and partition configuration: jflte (Samsung Galaxy S 4); Preset: Custom.

3) Rebooted into recovery (Phliz Recovery) and installed patched rom to multislot 1. At the end of the flashing, it shows:

[MultiBoot] Boot partition was modified. Setting Kernel

[MultiBoot] Destroying chroot environment

4) Reboot. Instead of booting into system, it boots into recovery. Now the phone is stuck at recovery.

It seems like the flashing process destroyed the dual boot from the log. Is that so? If that's true, how to fix it then?
[Galaxy S 4 i9505 Original Android Development] monkteo:
No the dualboot was not damage , simple you don't have space for 2 TW rom.
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
Is there anything I can do to make more room for the 2nd TW rom?
[Galaxy S 4 i9505 Original Android Development] monkteo:
Look in the forum the list with the app that can by deleted and clean primary rom.
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
I was told by someone that this only impacts dualboot slot, rather than multi slot 1, 2 or 3. On the other hand, I have debloated most of the samsung apps from the primary system.

Anyway, how to tell if there is enough space or not before flashing the second rom?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
In dual boot app click 3 lines upper left (same to see roms) 3rd down is free space
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
/system: Total size: 2.82 GB. Free: 1.15 GB

/data: Total size: 10.3 GB. Free: 6.77 GB

/cache: Total size: 2.14 GB. Free 0.11 GB

How much size should be freed?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
The size of rom to be installed + gapps if needed. Looks like you only have 110mb left in cache partition.

---------- Post added at 03:29 AM ---------- Previous post was at 03:20 AM ----------

@shadowcliffs, quick question, what type of chip is your phone running, is it exynos or qualcomm?
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
That's after flashing the second rom to Multi slot 1. Just wiped all on that slot and now it looks like this:

/system: Total size: 2.82 GB. Free: 1.15 GB

/data: Total size: 10.3 GB. Free: 6.77 GB

/cache: Total size: 2.14 GB. Free 2.1 GB

It seems the size of system is not affected by wiping all on multi slot 1, so I guess system size doesn't matter when the second rom is installed to slot 1. Correct me if I'm wrong.
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Did you see my last question, are you running exynos or qualcomm chip in phone? You can download app from play store "Phone INFO" free and scroll down to Hardware/Board it will tell you.
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
qcom / MSM8960.
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
One last shot here, try patching your second rom (slot1,2,3) with patcher r1051 and see if it will boot. Same hardware as mine....

It seems the size of system is not affected by wiping all on multi slot 1, so I guess system size doesn't matter when the second rom is installed to slot 1. Correct me if I'm wrong.

You are correct, multi slot-1, 2 & 3 are made in cache partition, primary and dual are in system.
[Galaxy S 4 i9505 Original Android Development] rlorange:
The Note4 and S5 have only 190MB cache partition vs 2GB I think for the S4.

So you CAN'T install a multi slot rom on the S5 or NOTE4 and you SHOULD also use a cm12 or lollipop ROM as dual as well because the dalvik cache from the system apps of a dual ROM installation will be sent to cache and simlinked back but this DOES NOT occur on lollipop which runs ART not DALVIK

Observe the folder for dalvik cache which is empty for me because my dual ROM is cm12 based ART not D's dalvik

Hope this clears things up. Chen originally designed the patcher on the S4 five him time he will figure out somewhere else to put the multi boot images
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
Patcher r1051 did the trick! The second rom booted into system!

BTW, I patched it using Windows version.

Do I have to use r1051 in android, or it doesn't matter and I can use the latest version like r1085?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
You should be able to but I'm just guessing, Chen or someone more knowledgeable could tell you for sure. You can also use apk to patch, it works.
[Galaxy S 4 i9505 Original Android Development] gaww:
If you have not gotten this already:

https://www.dropbox.com/s/dh3c2dp6y8jtm9g/DualBootUtilities-4.0-snapshot1.zip?dl=0
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
Thanks! Xiaolong has also had the link fixed.

Do I have to use this utility to switch system?

Update: I got it. Normally I should be able to use the "Dual boot patcher" to switch system by clicking at the rom first then reboot. Alternatively rom can also be switched with DualBootUtilities in recovery mode. I wish OP can have this stated a bit more clearly between 8 and 9 ;)

Here comes another issue: it seems Set Kernel in the second system caused the Settings fc.
[Galaxy S 4 i9505 Original Android Development] gaww:
No need to set kernel in secondary or multiple ROMs - so never did so. Only in primary, so not sure what would happen. Note - the OP instructions are very old - for initial releases.

Can you switch ROMs back and forth OK (hope trying to set secondary with the snapshot didn't do anything to mess it up)?
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
I switch to primary os with Dual Boot Patcher, but can't switch back to os on slot 1 neither with app nor with dualbootutilities. I'm not sure which caused this, or all of below?

1. I accidentally set the device name of the os on slot 1 the same as the primary

2. I set kernel for the slot 1 system as well (which might broke the Settings on the system)

3. After I see Settings fc, I changed device name back to zeroflte.

In one of your message you mentioned that Able95's rom got recognized by Dual Boot Patcher by changing the model from GT-G920F to GT-I9505, and I suppose it's "ro.produce.model=" in build.prop? In my test, "ro.produce.model=SPH-L720" wont work and it seems "ro.produce.device=jfltexx" got it recognized (well, maybe I shouldn't have used that).

Do you have a fully working switchable dual boot? What exact did you changed?

Update: just patched and installed Able95's v3.1 to slot 1. So far so good. Dual boot switches fine.

Update2: Settings fc. It drives me nut.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
[MENTION=4277844]chenxiaolong[/MENTION] seeing as how the S6 edge is coming out tomorrow what would it take to run this bad boy on it?
[Galaxy S 4 i9505 Original Android Development] sronweb:
How to remove previous kernel?

So far I have used CM12 rom as multi-slot1 patching with latest patched rom, gapps and googy kernel.

Now I'm trying again to install a CM12 nightly only with gapps using its original kernel but everytime I flash it I cannot boot again until I flash a kernel.

I tried with a "kernel cleaning script" (I patched before) but I get error "failed to run real update binary" during flashing procedure.

As you mention now is not necessary to select the kernel from the patcher then I don't understand what is wrong....

Thanks for the suggestion:confused:
[Galaxy S 4 i9505 Original Android Development] gaww:
I got settings FC also on patched Able when I had a typo on the build prop settings. Had to reflash it and carefully do it again. Now all is working OK.. Used the settings from Able v2 below::

ro.product.model=SM-I9505 (note - letter I not 1)

ro.product.brand=samsung

ro.product.name=kltexx

ro.product.device=jflte

Note - had to patch and flash another kernel to get WiFi working on v3 and now 3.1
[Galaxy S 4 i9505 Original Android Development] suzook:
OK, so backup and restore worked awesome on dual. Does data wipe work correctly? Need to wipe data on my secondary ROM.
[Galaxy S 4 i9505 Original Android Development] gaww:
Did you wipe multi-slot1system with Duelboot Utilities 4.0 first? There may be something carried over from the different kernel otherwise missed by the kernel cleaner.
[Galaxy S 4 i9505 Original Android Development] sronweb:
Yes. Typically I wipe system, cache and dalvik using the dual boot utilities 4.0 before update. In the past, using previous patcher I remember that it was enough to flash over existing rom to restore the stock kernel of CM
[Galaxy S 4 i9505 Original Android Development] v00d007:
Yes you're right, i got that problem too. Since the new multiboot format was intruduced i always got to flash a custom kernel after flashing cm12. [MENTION=4277844]chenxiaolong[/MENTION] should be aware of that issue as it was posted many times here...
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
Do you set those before or after flash? I used a different set of values in those:

ro.product.model=SM-N910P

ro.product.name=trltespr

ro.product.device=trltespr

Settings works on me at the beginning, then out of a sudden, it fc.

I did the mod according to yours:

ro.product.name=kltexx

ro.product.device=jflte

but kept ro.product.model=SM-N910P. Wipe data for Settings and dualbootpatcher, now Settings works again. Not sure which step actually fixed it.

And yes, I also patched kernel (replaced boot.img) before flash.

---------- Post added at 08:18 PM ---------- Previous post was at 07:27 PM ----------

@chenxiaolong

Can I have a feature request for Dual Boot Patcher? Would you please make the ROMs interface the default interface after starting the app. Currently when I start this app to switch rom, I need to:

1) click Menu

2) click ROMs

3) click at the rom I want to switch to.

If the ROMs interface can be made start-up interface, then 1) and 2) can be saved.
[Galaxy S 4 i9505 Original Android Development] gaww:
Opps - did not change model to GT rather then SM - as in GT-I9505.

I may try retaining the model, as by changing model, you loose connectivity to Galaxy Apps.

Update - need to probably change all back to use the Galaxy App again.
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
Actually after Settings is back to work, I changed those values back to where they were, i.e.,

ro.product.name=trltespr

ro.product.device=trltespr

Settings still work. So I am unable to replicate what caused Settings to fc.

I don't use any Galaxy Apps so model name doesn't matter to me. Is there any good Galaxy Apps that worth trying?
[Galaxy S 4 i9505 Original Android Development] gaww:
I only downloaded a few like office suites, optical reader, remote, etc.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Alright [MENTION=4277844]chenxiaolong[/MENTION] I have my tmo s6 edge in hand. What do you need? :D
[Galaxy S 4 i9505 Original Android Development] suzook:
Gonna answer my own question. Data wipe works fine. I do have another though. If I want to wipe data on primary, can I just do that in normal twrp recovery???
[Galaxy S 4 i9505 Original Android Development] gaww:
You will wipe data for all ROMs, so if you only want to wipe data on primary - use the utility again to do so. Ditto for system - that wiped primary ROM and Secondary ROM, while wiping cache in TWRP would wipe all your multisystem ROMs.

If things are not running well across the board and/or you want a clean start, then wipe everything with TWRP..
[Galaxy S 4 i9505 Original Android Development] Spike97:
Hy people, i.m here with a major problem:

I want to use a cm12 based rom as a primary rom on dual bot.

Second, i need a touchwiz based rom ONLY FOR CAMERA APP, and that.s why i need your advice: can i grab a tw rom and debload it from everything, the only app that need to remain is camera and others basics(gallery, call, message) ?

__I need that the tw rom to have the same baseband/firmware?

__I only want the tw rom to occupy less as posible memory (sorry for my bad english)
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
T-Mobile S6 Edge Stuffs

$ cat /proc/partitions

253 0 1310720 vnswap0
8 0 124960768 sda
8 1 4096 sda1
8 2 4096 sda2
8 3 20480 sda3
8 4 8192 sda4
8 5 28672 sda5
8 6 34816 sda6
8 7 8192 sda7
8 8 43008 sda8
8 9 1024 sda9
8 10 1024 sda10
8 11 768 sda11
8 12 256 sda12
8 13 9216 sda13
8 14 15360 sda14
8 15 4014080 sda15
259 0 307200 sda16
259 1 120451072 sda17
8 16 4096 sdb
8 32 4096 sdc
254 0 3981272 dm-0

$ ls -l /dev/block/platform/15570000.ufs/by-name/ <
lrwxrwxrwx root root 2015-03-31 08:49 BOOT -> /dev/block/sda5
lrwxrwxrwx root root 2015-03-31 08:49 BOTA0 -> /dev/block/sda1
lrwxrwxrwx root root 2015-03-31 08:49 BOTA1 -> /dev/block/sda2
lrwxrwxrwx root root 2015-03-31 08:49 CACHE -> /dev/block/sda16
lrwxrwxrwx root root 2015-03-31 08:49 DNT -> /dev/block/sda10
lrwxrwxrwx root root 2015-03-31 08:49 EFS -> /dev/block/sda3
lrwxrwxrwx root root 2015-03-31 08:49 OTA -> /dev/block/sda7
lrwxrwxrwx root root 2015-03-31 08:49 PARAM -> /dev/block/sda4
lrwxrwxrwx root root 2015-03-31 08:49 PERSDATA -> /dev/block/sda13
lrwxrwxrwx root root 2015-03-31 08:49 PERSISTENT -> /dev/block/sda11
lrwxrwxrwx root root 2015-03-31 08:49 RADIO -> /dev/block/sda8
lrwxrwxrwx root root 2015-03-31 08:49 RECOVERY -> /dev/block/sda6
lrwxrwxrwx root root 2015-03-31 08:49 SBFS -> /dev/block/sda14
lrwxrwxrwx root root 2015-03-31 08:49 STEADY -> /dev/block/sda12
lrwxrwxrwx root root 2015-03-31 08:49 SYSTEM -> /dev/block/sda15
lrwxrwxrwx root root 2015-03-31 08:49 TOMBSTONES -> /dev/block/sda9
lrwxrwxrwx root root 2015-03-31 08:49 USERDATA -> /dev/block/sda17

$ cat /proc/cpuinfo
Processor	: AArch64 Processor rev 2 (aarch64)
processor	: 0
processor	: 1
processor	: 2
processor	: 3
processor	: 4
processor	: 5
processor	: 6
processor	: 7
Features	: fp asimd aes pmull sha1 sha2 crc32
CPU implementer	: 0x41
CPU architecture: AArch64
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 2

Hardware	: SAMSUNG Exynos7420

[/QUOTE]

major minor #blocks name
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
major minor #blocks name[/QUOTE]

Wow! You sure do like getting your hands on the latest devices don't you? :D

I'll try adding support for it ASAP. That part shouldn't be too difficult. I just need to make sure I compiled 64-bit libraries for everything, so the app doesn't crash when you try to do anything.

EDIT: And /dev/sda*... The kernel is treating the memory like an actual hard drive/SSD on a PC. Cool!

EDIT2: What's the ro.product.device value in build.prop?
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Haha thanks and I do :D but I'm stuck now. Lol I believe it is zeroltetmo for the tmo edge also SM-G925T
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I won't change the default, but in 8.0.0.r1086.g8e42908, I've added an option to the settings for changing the initial screen when you open the app :laugh:
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
Just installed r1093, it works very well for that purpose.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The reboot to recovery issue with AntaresOne CM12 and some other ROMs is now fixed in 8.0.0.r1093.g8aecc27 :)
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
EDIT: Just rerooted now that the Deep Sleep Issue was fixed.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sweet! Any way you could dump the kernel for me? It's the last bit I'm missing to add support for the S6 Edge :)
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
How?

EDIT: uploading to mega now
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Try running this command as root in either adb or the Terminal Emulator app. It should create a boot.img file on the internal SD.

dd if=/dev/block/platform/15570000.ufs/by-name/BOOT of=/sdcard/boot.img
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
https://mega.co.nz/#!wgt1QTxT!QvCst316q_CXzglbVtU272I2yuFDDuYpIt2A7mKqAm0 check that out. Was made with wanams partition backup apk on playstore.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! That's exactly what I need.

(And that profile pic change really threw me off... It's gonna take me a while to associate your name to your new picture :D)
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Don't associate it with that one.. lmao it's not permanent I'm in the midst of looking for anew. Also thank you and I can't wait to hear from you and we might have a custom kernel being released with GCC 4.9.x

Edit: this is the one

Edit2: the avatar pic lmao
[Galaxy S 4 i9505 Original Android Development] sronweb:
Today I have flashed CM12 update without any kernel and finally its' working and booting fine. Before it was necessary to flash a kernel (googy, alucard, etc) otherwise I had a bootloop. Thanks for the great job!!

PS: false alarm! I got infinite boot animation after the apps check. One step more but not fixed. Also I cannot flash a different kernel (Hulk) otherwise I get bootloop but it is fixed if I reflash the original one (Googy-Max).
[Galaxy S 4 i9505 Original Android Development] flexxoo:
I think that adding a widget for the ROMs it should be a good idea for fast booting from home screen if you can add that feature will be awesome!!! Thanks for your hard work
[Galaxy S 4 i9505 Original Android Development] gaww:
Normally TW should be primary ROM and something like CM12 secondary. If not enough room in secondary (on top of the primary), then a MultiSlot.

You can only have one firmware on the device - the ROMs don't affect it.
[Galaxy S 4 i9505 Original Android Development] aukhan:
Hi Chen,

is Sammy LL supporting Multiboot i am not sure I dint mind to update to LL as I am satisfied with Sammy KK and AICP. So please throw some light on this Chen thank you.

Powered by ET!
[Galaxy S 4 i9505 Original Android Development] suzook:
I have a note4, so wipe using utility works on that too? Wipe rim just wioew data??? Thanks
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yes :D