yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs and boot.img! Unfortunately, it's still not dumping the kernel log and your kernel & recovery don't support /proc/last_kmsg. We'll just have to use the good old guess-and-check method.

You said that the device hangs at the device name, right? It doesn't automatically reboot into recovery? Could you do the following two things for me?

Flash the attached UeventDump.zip and send me /sdcard/uevent.log

Install the attached debug version of the app and try the ramdisk update again. (The app installs separately to the regular version and is named "DualBootPatcher (Debug)"). When the device boots, it should do a 1-second long vibrations at various points in the boot process. If it does 7 long vibrations, the main part of the multiboot code was successful. If it does 5 short vibrations in a row, then the code failed. Please let me know how many long vibrations occur, so I know how far the boot process got.

Thanks!
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
Right but after that it reboot automatically into recovery, i forgot to mention that :P

I'll do both of them and let you know :)

Edit:

[MENTION=4277844]chenxiaolong[/MENTION]

When i flashed UeventDump it didn't work, i got updater process ended with error = 127

And I tried to update ramdisk for primary ROM and same result, and the device vibrate only once

When i tried CM boot after device name nothing happens black screen then it reboot automatically to recovery but with stock boot it hangs at device name and keeps bootloop without rebooting to recovery
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for all the details once again. Reboot to recovery is good news :) That means the issue can be fixed (eventually....). If the CM boot only vibrated once, then it was unable to mount the partitions. The UeventDump zip will give me some hints as to why it's not working. Could you try the new attached zip? If it fails again, see if /sdcard/uevent.log is created anyway and send me that file.

EDIT: I don't believe I ever answered your question about the boot.img size after updating ramdisk. When you flash a new ROM, the patcher unpacks and repacks the boot.img file so it knows what the exact file size should be. When you update the ramdisk, the backup file is just a dump of the boot partition, without any additional processing. It will include the junk data the partition has after the "real" boot.img contents. That's why it's quite a bit larger.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
[MENTION=4277844]chenxiaolong[/MENTION] Is this error due to some bug in the ROM or patching??
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It's caused by crappy programming of the update-binary :silly: the error code 11 from the newest log is a segmentation fault, which happens when a program accesses invalid memory. It's a nightmare to debug when you don't have the source code.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
The source code we have hasn't got anything related to updater-script??

This is very sad :(
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I will be away on vacation until New Year's Eve. I wish everyone a Merry Christmas and don't you break your phones while I'm gone!

(And if you live somewhere in the US with the same-ish latitude as Ohio, enjoy not having snow while it lasts ;))
[Galaxy S 4 i9505 Original Android Development] monkteo:
By By have a good vacantion !
[Galaxy S 4 i9505 Original Android Development] whitenoyz:
cannot send/attach the file trough this, I've sent you a MP with the text content of the file. thank so much [MENTION=4277844]chenxiaolong[/MENTION] I will try with the day's snapshot version to see if it works, until now same result as explained.
[Galaxy S 4 i9505 Original Android Development] monkteo:
7A2943610C025214C

for vacation
[Galaxy S 4 i9505 Original Android Development] gaww:
You are happy no snow (I guess there is no skiing in Ohio..)? I would kill for a good snowstorm right now - lol !
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
No snow here also! I'm sad. The weather gone mad! lol :laugh:

Happy holidays dude! Also happy holidays to everyone in this thread. :highfive:
[Galaxy S 4 i9505 Original Android Development] onbeskarakterli:
[MENTION=4277844]chenxiaolong[/MENTION]

I have been using Dual Boot Patcher on my Note 4. There is a problem with Solid Explorer v2.1.7. Dual Boot Patcher can't grab the file path SE is providing (at least this is what I understand). I contacted SE's developer and he said he made a change and that was the cause of this problem and he will provide a workaround, but he also said that Dual Boot Patcher should be fixed too.

This is the response I got:

"Hi,

Thanks, I got it. This happened, because I've changed format of the Uris sent to other apps when you pick the files. Dual Boot Patcher takes wrong assumption, that Uris always contain real paths to files, which is not true.

I'll fix this problem with a workaround, but this should be also fixed in the patcher app.

Cheers"

I wanted to let you know. Thanks.
[Galaxy S 4 i9505 Original Android Development] sronweb:
I'm having the same version of Solid Explorer and I use it to grab the file to patch with Dual boot patcher but I have no problems to select the file via SE. Or maybe I misunderstood your issue.
[Galaxy S 4 i9505 Original Android Development] onbeskarakterli:
Selecting a file is fine. Try to apply the patch. It will give an error (error code 15).

Edit: The app just got an update with the same version and build number. I believe the dev made the change and released it. So if you got this update, you won't have this problem.
[Galaxy S 4 i9505 Original Android Development] Dnorris55:
I get the error 15 if i try to select a file on the external sdcard, but not if I select one from the internal.
[Galaxy S 4 i9505 Original Android Development] onbeskarakterli:
Are you using Solid Explorer? I contacted the dev and he confirmed the problem and fixed it. He also said what I wrote in my first message. There should be an update in Play Store, just update it.
[Galaxy S 4 i9505 Original Android Development] Dnorris55:
No, I don't use SE. I use ES File Explorer. Just suggesting that the location causes the error, maybe not the file explorer..?

Booting primary = ASOP 6.0

Data1 = Slim 5.1.1

Data2 = CM 5.1.1
[Galaxy S 4 i9505 Original Android Development] onbeskarakterli:
Maybe, I don't know. ES File Explorer has two options to provide a path to the app. Try the other one.
[Galaxy S 4 i9505 Original Android Development] :
Only for note, here the list of all devices supported by DualBootPatcher - XDA Topic
[Galaxy S 4 i9505 Original Android Development] pc boy:
I tried to patch a Mokee rom for installing on extsd and it failed with error code 12

Patching xposed framework v79 also returned the same error!

What's wrong? How to make it right?:)

links:

Mokee rom: http://rom.mk/l52esv

xposed: http://xdaforums.com/attachment.php?attachmentid=3580247&d=1450386638

EDIT: Found the solution:)

Files were corrupted, bad download;)

Since the cause of error code 12 has not been discussed in the topic (searched and found nothing;)) I decided not to delete this post. [MENTION=4277844]chenxiaolong[/MENTION], if you think it's not right, feel free to delete it;)

Many thanks fro the AWWWESOME work again:)
[Galaxy S 4 i9505 Original Android Development] rolexconfuse:
Can you do a nandroid backup of the rom you are in or will it do a backup of both roms?
[Galaxy S 4 i9505 Original Android Development] todivefor:
If you do a nandroid backup it will backup all roms.
[Galaxy S 4 i9505 Original Android Development] rolexconfuse:
so there is no way to backup either of the roms then without doing the whole system. My second rom is in the data partition which means it will backup all my data and everything in it, that's huge.
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
[MENTION=4277844]chenxiaolong[/MENTION] explained how to perform backups for individual roms in post #7419 and also how to save the backups to external sd in post #7920.

http://xdaforums.com/showpost.php?p=63505436&postcount=7419

http://xdaforums.com/showpost.php?p=64143679&postcount=7920
[Galaxy S 4 i9505 Original Android Development] rolexconfuse:
Thanks i saw that but I do have a questions regarding a specific

So are you supposed to update the ramdisk in the primary rom before doing the backup or are you doing the ram update in the secondary rom prior to backing up the primary?
[Galaxy S 4 i9505 Original Android Development] monkteo:
when i want to patch a rom I get (error code 15) , what this mean ?

THX

Ps. found it (I use Fx explorer and i can't pick up a file from ex-sd, so I move the file to internal storage and it's working)
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Hi, Just tried to Install JDC Teams ASOP 6.) as MultiSlot 1 and it installed OK but the initial boot seemed very fast and subsequently it comes up to the lock screen and looks fine but I can make no touch inputs to get the lockscreen open plus the Sim Card is showing as none installed. I've done a quick search but couldn't find anything. Is this a known issue or should I just redo it and try again?

EDIT

A couple more boots and it seems to have fixed itself :)
[Galaxy S 4 i9505 Original Android Development] MBariya:
Ohh man get frustrated with Aroma and TWRP on my Note 4.

Don't want to loose functionality and flexibility of TWRP.

Any solution for qualcomm devices and Aroma??
[Galaxy S 4 i9505 Original Android Development] monkteo:
I try many time but I cannot install in dualboot a rom with aroma ! :confused:

So i give up to try , I install only rom without aroma !:fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] MBariya:
I need support for dualbootUtility.zip file which is aroma
[Galaxy S 4 i9505 Original Android Development] nayanwaghmare:
Error executing updater binary

My recovery, TWRP v2.8.7.0 is saying E:Error executing binary in zip'/sdcard/Download/cm-13.0-20151225-UNOFFICIAL-temasek-hlte-V2.0_dual.zip'. As you can see I am trying to dual boot UNOFFICIAL-temasek-hlte-V2.0 which is android 6.0.1r3 (CM13).

I am using a Samsung Galaxy Note 3, with my primary rom being the Phronesis Rom v4.1, which is running android 5.0.

Could anyone help me resolve this issue. I have tried Philz recovery but that too gave the same error.

Thanks.
[Galaxy S 4 i9505 Original Android Development] gaww:
I had patched and installed an unofficial CM13 to external SD OK what version of the patcher are you using ?
[Galaxy S 4 i9505 Original Android Development] MBariya:
You need to patch zip file first. Read the OP in details.

---------- Post added at 07:02 PM ---------- Previous post was at 06:57 PM ----------

[MENTION=4277844]chenxiaolong[/MENTION]

Got one bug. Patching zip file getting failed when file is located from external sdcard on CM13 ROMs. Giving error-15.

Patching works normal If Moved zip file to internal sdcard.
[Galaxy S 4 i9505 Original Android Development] nayanwaghmare:
Thanks for your quick replies.

I know I have to patch the files, I'm no noob haha.

I am using the latest version: 8.0.0.r2037.g0f5ab82 Sun, 20 Dec 2015 20:23:36 -0500.

I had tried to patch to file with locations multi boot-1 but then tried dual, but both are giving me errors. BTW all my files are in my internal storage.

Any ideas guys?

Thanks
[Galaxy S 4 i9505 Original Android Development] MBariya:
Just for confirmation, did u downloaded ROM file correctly?

Did u checked md5 su
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
[/COLOR]

Does the Patcher work for you?? I've got a friend who's got the Note 2 N7100, the 3G version (t03g) and it stucks at "Please wait" dialog when updating ramdisk for a long time. He has changed ro.product.device to t0lte, by the way, as t03g wasn't in the list.. [MENTION=4277844]chenxiaolong[/MENTION] Can please add t03g to device codenames? Also, can this problem be because of the particular version?? Do you need the logs??
[Galaxy S 4 i9505 Original Android Development] nayanwaghmare:
Yes everything is correct. I've tried to download multiple times just to make sure it's not the file I downloaded.
[Galaxy S 4 i9505 Original Android Development] corncobman:
Using version 2037, what I've noticed is in CM13 that the patcher doesn't ask for root and patching fails with error -15. I don't know if these two are related. CM13 is installed on my extsd.

With another ROM (Android Lollipop 5.x) the patcher seems to work fine.
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
I have been using dual boot for a while and I just installed a 64GB SD card so I can use apps2SD+. I have now 2 partitions on my SDcard 50GB Fat32, and 10GB EXT4, and the Dual Boot patcher chould not see my extsd slot1 rom anymore. and when I created another ROM slot in the extsd it created it in the EXT4 partition not the Fat32 partition. How can I get it to use the 50GB Fat32 partition instead of the 10GB EXT4?

Thanks
[Galaxy S 4 i9505 Original Android Development] pvsgh:
I was able to update the ramdisk of my stock AT & T rom that I was using, but then the phone kept rebooting. So I try not to update the ramdisk for the primary ROM.

But I was able to install latest CM 12.1 to a data slot with no issues at all. So probably issue is with stock kernel that I have with stock rom.
[Galaxy S 4 i9505 Original Android Development] Andycar:
Happy New Year ? dualbooters! ☺?

Отправлено с моего SM-N910G через Tapatalk
[Galaxy S 4 i9505 Original Android Development] RK:
[MENTION=4277844]chenxiaolong[/MENTION], I successfully dual booted ATT goldeneye. Here are the files:

https://www.dropbox.com/sh/fouxj74469hlche/wDIeQW4_NG

Just so you know, the zip has a separate /kernel folder for the boot.lok file.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the files! The boot image is specified using the bootimg variable. ie.

file_info.bootimg = 'kernel/boot.lok'

I didn't realize that was missing from the sample file. I've added it now.

Commit: https://github.com/chenxiaolong/DualBootPatcher/commit/85e2a971440f2ccf42043a94d81d7f945eab6feb
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thank you very much for the support! :D Glad you finally got it to work :)

Ktoonsez's Touchwiz and Google Edition kernels aren't supported, but I'll add support right now if I can download the files here at school.
[Galaxy S 4 i9505 Original Android Development] RK:
ah ok. I assumed that after patching, it would be /kernel/boot.img and changed the updater script accordingly. Is that correct?

Thank you for your hard work! This tool is awesome! :)
[Galaxy S 4 i9505 Original Android Development] Dugan1017:
Which files to patch?

Infamous Alpha (TW) is my primary ROM, and I'm attempting to dualboot IOKP as my secondary. I've been able to download the 3 files I need and have patched the ROM I intend to install as my secondary. Do I also have to patch the gapps I'm gonna flash with it?

Thanks for any help you can offer.
[Galaxy S 4 i9505 Original Android Development] jova33:
one more question, the boot_dualboot.img, do i need to rename it to boot.img and put it back in the ROM zip?

Edit: so I patched the updater script, patched the boot.omg, flashed dualboot.zip, flashed loki-doki, and it got me to the unauthorized software screen telling me to take my phone to Verizon. I've obviously done something wrong.

How do you do the loki stuff? Patching the boot.img de-lokis it, so what am I doing wrong?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Glad you're enjoying the patcher!

I actually made it so the filenames remain the same. That way we don't need more changes to the updater script :D
[Galaxy S 4 i9505 Original Android Development] ahoslc:
While trying to patch KT-SGS4-JB4.3-AOSP-VZW-10.25.2013

Detected ktoonsez kernel zip

--- Please wait. This may take a while ---

Extracting boot image: boot.imgTraceback (most recent call last):

File "C:\Users\Brandon\Downloads\DualBootPatcher-2.4.3\DualBootPatc

scripts\patchfile.py", line 559, in <module>

newfile = patch_zip(filename, fileinfo)

File "C:\Users\Brandon\Downloads\DualBootPatcher-2.4.3\DualBootPatc

scripts\patchfile.py", line 451, in patch_zip

z.extract(file_info.bootimg, path = tempdir)

File "C:\Users\Brandon\Downloads\DualBootPatcher-2.4.3\DualBootPatc

ythonportable\lib\zipfile.py", line 1040, in extract

member = self.getinfo(member)

File "C:\Users\Brandon\Downloads\DualBootPatcher-2.4.3\DualBootPatc

ythonportable\lib\zipfile.py", line 913, in getinfo

'There is no item named %r in the archive' % name)

KeyError: "There is no item named 'boot.img' in the archive"
[Galaxy S 4 i9505 Original Android Development] veloso:
Latest Vertigo's Paranoid Android (with updated Android 4.3.1)

pa_jfltexx-3.99-RC2-20131027.zip

DualBootPatcher-2.5: :(

DualBootPatcher-1.9: :good:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Fixed in 2.5.1 :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You need at least version 2.5 because that's the first version that supports loki'd kernels :good:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The steps look fine to me. The patcher de-loki's the boot.img and patches it. In theory, loki-doki should re-loki it without issues.

Could you try again and pull the recovery log for me? The DualBootUtilities zip has an option for saving the recovery log to the internal storage.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, the gapps needs to be patched. Any zip that would want to be installed for the secondary ROM needs to be patched :good:
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Here is the error I get in 2.5

Extracting ramdiskTraceback (most recent call last):

File "C:\Users\Brandon\Downloads\DualBootPatcher-2.5\\scripts\patchfile.py", l

ine 577, in <module>

newfile = patch_zip(filename, fileinfo)

File "C:\Users\Brandon\Downloads\DualBootPatcher-2.5\\scripts\patchfile.py", l

ine 477, in patch_zip

new_boot_image = patch_boot_image(boot_image, file_info)

File "C:\Users\Brandon\Downloads\DualBootPatcher-2.5\\scripts\patchfile.py", l

ine 303, in patch_boot_image

extracted

File "C:\Users\Brandon\Downloads\DualBootPatcher-2.5\\scripts\patchfile.py", l

ine 207, in process_ramdisk_def

plugin.patch_ramdisk(directory)

File "C:\Users\Brandon\Downloads\DualBootPatcher-2.5\scripts\..\ramdisks\jflte

/AOSP/AOSP.py", line 101, in patch_ramdisk

modify_init_rc(directory)

File "C:\Users\Brandon\Downloads\DualBootPatcher-2.5\scripts\..\ramdisks\jflte

/AOSP/AOSP.py", line 48, in modify_init_rc

write(f, line)

File "C:\Users\Brandon\Downloads\DualBootPatcher-2.5\scripts\..\ramdisks\jflte

/AOSP/AOSP.py", line 10, in write

f.write(line)

TypeError: 'str' does not support the buffer interface

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

Looks like 2.51 works thanks :)
[Galaxy S 4 i9505 Original Android Development] jova33:
Ok, miraculously it worked this time. For some reason the recovery.log is blank.

New problem, I can't boot my primary ROM. It just sticks at the Samsung custom screen. Tried multiple battery pulls, and nothing. Booted into recovery, flashed the utils, switched to secondary ROM, and am able to boot fine here.

My primary ROM is Hyperdrive, a touchwiz VZW ROM.

Edit: ok, I missed a line in the updater script. Backing up now and will try again in a few.
[Galaxy S 4 i9505 Original Android Development] RK:
Oh in that case the patcher file I sent you needs to be edited..
[Galaxy S 4 i9505 Original Android Development] hemmie:
I actually made the my Temp Ramdisk configuration just so it acts as a real physical disk then I do not get the problem and all goes smoothly.

I still think Python should be relaxed in checking the my temp folders since all other apps I have in my PC does not complain against that, only once I found another disk Utility program complained about it.

And also you beta or rather I would say 2.5.1 did fix the syntax error, now I could patch it in Windows as well. Don't need to try it in OSX now :)

Thanks again for your your hard work. Just pointer it may be helpful to remove only the buggy/syntactically incorrect (like 2.5) patches from the download sites, so that users don't have to test on them.

---------- Post added at 01:52 AM ---------- Previous post was at 01:45 AM ----------

It could also make sense to rename it as loki-kernal/boot.img or that loki is contained somewhere in the path so anyone looking at the update_script would not miss the kernel used here is already patched and no need to flash loki_doki.zip afterwards.
[Galaxy S 4 i9505 Original Android Development] jova33:
Holy cow, I finally got everything to work. I missed one line in the updater script. I went off the AOKP example, but for some reason the official nightly I had an extra line.

TW as ROM one, AOKP as ROM two on my VZW S4.

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] SkizzyNinja:
Can you add support for dirty unicorn? I did a search and checked the supported list but couldn't find it http://xdaforums.com/showthread.php?t=2487771 sorry if someone already asked....my xda app cuts up a lot and I can never see posts above mine lol

sent from my infamous kanged S4
[Galaxy S 4 i9505 Original Android Development] allan1313:
OK just did this on my vzw s4. Awesome work! One question , what is the easiest way to get apps to show on both roms, is that even possibe?
[Galaxy S 4 i9505 Original Android Development] george stamatos:
Can we dual boot 2016, and 2006........? Is it possible to make an application [MENTION=4277844]chenxiaolong[/MENTION] ?

Happy New Year everybody !
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Many of us are currently dual booting in 2037.. We are some 20 years ahead of time. [emoji23] :P ;)
[Galaxy S 4 i9505 Original Android Development] monkteo:
question ?

way only in Samsung TW rom the GPS work ? I mean in dualboot on data-slot or ext-SD !

I tested MIUI TW cm12 and cm13, can't start the GPS !
[Galaxy S 4 i9505 Original Android Development] gaww:
One thing to note because the tool doesn't detect this yet. If you want to backup the primary ROM, make sure to do a ramdisk update from the app first. Otherwise, the kernel will not have any multiboot code and won't boot if you decide to restore it to another slot.

What if it is done without updating ramdisk and won't boot - can you simply patch the kernel to the slot and flash it to get it to boot ?

---------- Post added at 05:02 PM ---------- Previous post was at 04:27 PM ----------

I have a 6.0 AOSP ROM patched to WtSD and GPS works fine.
[Galaxy S 4 i9505 Original Android Development] yilun:
Hello, you said that if we're going to use a tw rom we should set it as main. Does that mean that if I set as secondary it will likely run in to problems, or just to avoid them?

<a href="http://www.danasoft.com"><img src="http://www.danasoft.com/sig/Yilun9.jpg" border="0"></a><div style="font-family:arial,sans-serif;font-size:11px;"><p>Sign by Danasoft - <a href="http://www.danasoft.com">For Backgrounds and Layouts</a></p></div>
[Galaxy S 4 i9505 Original Android Development] steno3131:
Dual boot problem with stock LL 5.01 and Miui 4.4

help I go crazy if I can not solve the problem with the rom miui 4.4.

I tried everything. My setup is: primary stock rom lollipoo 5.1 galaxy s4 and secondary miui rom definitely works because already installed as rom primary.

the problem is that I can not install any miui where am I wrong?

Possibly because the rom miui is installed on the external sd?

The rom miui not report errrori during installation seems okay. Part but get stuck on the starting screen where there is the logo miui.

I'm grateful if you help me.

Attached logs