yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] bobblesop:
Failed to set kernel

Hi chenxiaolong. I have used your awesome app on my LG G3 D855 sucessfully.

I now have an LG G4 H815 but I get "Failed to set kernel."

Flashing a patched rom works but I can't switch back to the primary rom using the app (I dirty flashed to boot back to primary)

Any advice appreciated!
[Galaxy S 4 i9505 Original Android Development] Whitest:
Could you describe more detailed how you did it? Did you simply use the App/BackupTool v4? I'd like to backup my current CM13 primary, wipe all, install a TW on Primary (advice is to put it always primary right?) and then restore CM13 as secondary (dual-position)

Or is it possible to simply install TW rom on secondary as your post implies you've got no problems with TW on secondary?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
I am currently using my phone (hard for me to type and link to references). Will help as much as I can when at pc a little later. One thing, if you place TW other than primary use data or ext_sd as there may not be enough space in cache to support it.
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
[MENTION=4286584]Whitest[/MENTION], the backup function is not yet working in the Patcher app, to back up a rom you must follow the instructions given by [MENTION=4277844]chenxiaolong[/MENTION] in post #7419 http://xdaforums.com/showpost.php?p=63505436&postcount=7419

In order to save your backed roms to external sd follow the instruction given by [MENTION=4277844]chenxiaolong[/MENTION] in post #7920 http://xdaforums.com/showpost.php?p=64143679&postcount=7920

two things to remember:

1. If you are unable to push mbtool_recovery to /tmp/ then copy and paste it there

2. Do not forget to chmod 755 mbtool_recovery as described by [MENTION=2688336]todivefor[/MENTION] in post #7908 http://xdaforums.com/showpost.php?p=64114351&postcount=7908
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I've found out what was wrong with the Windows builds. I made a dumb assumption: static libraries that are linked by shared libraries/DLLs won't export all of their symbols, since code unused by the shared library itself is discarded. It just happened to work when I was testing on Linux since libraries aren't stripped by default.

Aside from the technobabble, this means I'll probably have this fixed today or tomorrow :)

EDIT: Should be fixed in 8.0.0.r2228.g9632ad8
[Galaxy S 4 i9505 Original Android Development] monkteo:
I notes that to and my option is to , change the rom and reboot from phone menu (not from app option)

For my it's working perfect and not big deal (3 rom on S5, primary, data-slot and extcard)
[Galaxy S 4 i9505 Original Android Development] nutpants:
Some where around update 2100 my Canadian s4 started hanging on booting the primary touchwiz rom (wamanlite 1.5 Android 442) after updating mbtool (which I'm not sure what it's used for) it updates the dual aosp rom fine.

Log attached.

(I've tried up to the latest apk yesterday and all worked fine back when)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r2229.gcfefa87 might fix the issue :) It seems like the charger mode fstab file was being used and that fstab file does not mount the system and cache partitions, which led to the boot failure.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Oh sorry if I was unclear. I didn't mean that patching multiple files was the cause of the issue. The issue just started occurring around the time I introduced that feature. The freezing is caused by an issue with the background service that handles the patching. That code was originally rewritten because the old code was slow and had an issue where the service would restart every 10 seconds, potentially causing battery drainage.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
A reboot should have fixed that. Linux allows deleting files that are in use, so the space is not freed until everything using the file is closed. I have a pretty good idea of why this is happening and will try to fix the issue. EDIT: It may not be possible to fix this due to the way Android's mount namespaces work. A reboot is the best way to free up the space.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Any chance you could send me /sdcard/MultiBoot/patch-file.log after the failure occurs? Error 100 means it was unable to open the file, so I'm guessing it's probably a simple mistake I made. Thanks!
[Galaxy S 4 i9505 Original Android Development] Spoochie:
can someone help me? i have a touchwiz rom as my primary and cm13 rom as secondary. i patch it on data slot. on app sharing i select titanium backup then reboot. after that switch to 2nd rom then install titanium backup. after isntalling it stuck at searching for data application.. i did format and remove my 2nd rom then patch and flash again but no luck.

hope somone can help.

thanks mates
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This is now implemented in 8.0.0.r2231.g31d64dc :) You'll need to copy the modem to /sdcard/MultiBoot/[Your ROM ID]/modem.img and NON-HLOS to /sdcard/MultiBoot/[Your ROM ID]/apnhlos.img ("apnhlos" is the actual name of the partition).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r2232.g491371d should fix this :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you link to the exact ROM you're using for primary? I'll flash it on my S4 to see if I can reproduce the issue. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Having more that one partition on the external SD is currently not supported. It will be supported in the future, but I don't have any timeframe as to when it'll be implemented.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure! If you could flash the GetLogs zip from https://snapshots.noobdev.io/ and send me the log files it creates in /sdcard/logs/, I'll add support for the device :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
There may be an issue with the ROM (or the way it was installed). The radio daemon (rild) failed to start because a file was missing, which prevents Android from communicating with the modem:

dlopen failed: dlopen failed: library "/system/lib/libril-qc-qmi-1.so" not found

I'll download the ROM and do some testing with my SGH-M919 and see if I run into the same issue. There's also the chance that you might have ran out of space on /cache. Could you check how much free space you have there?
[Galaxy S 4 i9505 Original Android Development] Andycar:
Fantastic, thanks!

Отправлено с моего SM-N910G через Tapatalk
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION], here you go.
[Galaxy S 4 i9505 Original Android Development] ewangw:
Support for Moto X Pure

[MENTION=4277844]chenxiaolong[/MENTION], Thanks for adding support for the Moto X Pure. I have attached the file created from GetLogs. Please let me know if you need anything else.
[Galaxy S 4 i9505 Original Android Development] nutpants:
This should be the exact rom I'm running

I have not updated in a long long time as I'm happy with it.

(Add there is no touchwiz mm and the loli has significant bugs)

The link appears to be dead however. As it's discontinued

But I have not found anything better yet.

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

I'll see if I can find an alternate download link than the official

If you have mega pm me and I'll send you a link to my mega archive of the file
[Galaxy S 4 i9505 Original Android Development] bobblesop:
It now works! You sir, are a star. Thank you!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! This should be fixed in 8.0.0.r2233.gdacf0f3.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Added support in 8.0.0.r2234.gd732885 :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I found a link to a shady site that had the file, but the MD5 matches so we're good.

If anybody else is looking for this ROM, I've uploaded it to Mega:

Original XDA thread: http://xdaforums.com/showthread.php?t=2283194

Archive.org backup of original website: http://web.archive.org/web/20150417...lite-xxugnh7-v3-1-android-kitkat-4-4-2-xposed

Download: https://mega.nz/#!RgpUxYpD!5crleuPVGSkXC9yo1UpxDTkF_Vkvkmplvlhf3bIMAZ8

MD5: f50cdee8973d9cd47c66762c46f62833
[Galaxy S 4 i9505 Original Android Development] Spoochie:
HI [MENTION=4277844]chenxiaolong[/MENTION], can you help me on titatnium backup issue?

on my 2nd rom the titanium backup stucks at "searching system data"

i had my 2nd rom on datda slot along with the gapps & kernel.

thanks in advance
[Galaxy S 4 i9505 Original Android Development] SaschaHa:
Update ramdisk and set kernel failed. Seems that mbtools are missing. What can I do?

Galaxy Note 4 N910C (Exynos 5433), DN5 (TouchWiz 5.1.1 OJ5 rom).

Log is here:

https://www.dropbox.com/s/0lgcd2ypjqa657d/MultiBoot.zip?dl=0

Thanks!!
[Galaxy S 4 i9505 Original Android Development] gaww:
What about letting the user specify a size ? It would then be a fixed size through the rest of the process, so wouldn't that eliminate the issues above?

---------- Post added at 03:57 PM ---------- Previous post was at 03:30 PM ----------

Quote:

Originally Posted by gc_geforce View Post

I have been using the dual boot patcher for a while now with no issues, and I had my first issue updating my ROM JDC AOSP 6 today http://xdaforums.com/gala...ra58v-t3251663 , I had this ROM in the multi-slot-1 and after updating it could not see my sim card. So I wiped my primary and multi-slot-1 and move my ROMs around via the ADB backup commands from the OPs first page(love this), and put the JDC AOSP as my primary and my Mokee android 6 as my multi-slot-1 and then did the update again with no issues and it now can see my sim card.

I also attached my logs from when it did not work in the multi-slot-1 from a clean install.

it looks like the new kernel does not support multi rom, as now I cannot see my ROM installed at multi-slot-1.

I had the same ROM installed on ExtSD of a M919, but had issues patching/flashing the latest ROM update with the latest patcher.

I went back to 2015 and everything went OK - including seeing it when selecting ROMs. Also, it sees and uses the External SD OK in titanium - just backed up an app and restored another to confirm.

Therefore, the updated ROM can work OK with duelboot, so keep on trying.
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
Thanks I will try again with the same version
[Galaxy S 4 i9505 Original Android Development] ewangw:
Support for Moto X Pure

[MENTION=4277844]chenxiaolong[/MENTION],

Tried out DBP version r2234 last night and came up with some errors. The ROM and Open GApps files I chose patched fine for MultiBoot 1, but came up with errors when I tried to install. I also could not set kernel or update ramdisk. I attached the ramdisk and patch file logs to see. Please let me know if you need any additional files to review.

Thanks
[Galaxy S 4 i9505 Original Android Development] gaww:
Note - I had latest problems with PC patcher and ended up using the app to patch.
[Galaxy S 4 i9505 Original Android Development] todivefor:
Tried patching OTA with 2239 and got error 100 again Here is the log. Looks like same. Did successfully patch with windows 10. However, I think there is a problem. Here are the before and after files.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ah, it's failing because it thinks your device is a Note 5 and thus tries to read from the Note 5's boot partition path (which doesn't exist on the Note 4). You'll want to add:

ro.patcher.device=trelte

(replacing "trelte" with your actual device) to your build.prop file and then reboot. This tells the patcher that your device is a Note 4 without affecting the rest of the system.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
AOSP ROMs using the "system.new.dat" format have the system partition size hardcoded into them. They must be flashed to an image that is greater than or equal to the system partition's size. Otherwise, they will be unmountable.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you also grab the remaining logs? (/sdcard/MultiBoot/daemon.log and /sdcard/MultiBoot.log) Thanks!

EDIT: /sdcard/MultiBoot/daemon.log is overwritten on reboot, so you may need to try setting the kernel again for the error messages to show up there.
[Galaxy S 4 i9505 Original Android Development] SaschaHa:
Wow that's great, thank you very much!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Holy cow, thanks for uploading such a massive file! There are two issues going on here. The first is that Samsung named the system image as "system.img" with the Galaxy S6 instead of "system.img.ext4" like on the S4. The second is a mistake I made in my previous fix. There was one other piece of code that was trying to access the file directly instead of going through Android's storage framework.

Both issues should be fixed in 8.0.0.r2241.gec63299.
[Galaxy S 4 i9505 Original Android Development] ewangw:
Support for Moto X Pure

[MENTION=4277844]chenxiaolong[/MENTION], I have attached the daemon log and a screenshot from DBP when trying to install the patched files. For some reason I can't copy or move the Multiboot log file. I will keep trying.

Thanks
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I believe 8.0.0.r2242.g0532bd4 should fix the issues you're seeing.
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
thank you! so I had to patch the rom via my PC using version 2015, and then updated the JDC ROM using the patched file and it worked! the rom nows is able to see the sim card and just works. Thanks for your help!
[Galaxy S 4 i9505 Original Android Development] diogo.sena:
[MENTION=4277844]chenxiaolong[/MENTION] ,

hi, my secondary rom stopped working, dont know exactly why, but i went ahead and reflashed, now it works, but constantly FC every app,

maybe a selinux problem?

theres some workaround for that?
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION], this is what I am trying to do. I have a mostly stock TW rom (mostly 5.1.1 with rooted kernel). I backed it up with DB backup. I restored it to data-slot-stockol1. Booted to it and everything was fine. I had a copy of my primary in data-slot-stockol1. I patched the G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.md5 I was having problems with (BTW patched with both W10 and app and both were successful) to data-slot-ol1. I then flashed the zip I had patched with the app. I was hoping to return my primary rom to stock in the data-slot-stockol1 slot. At about 3/4 of the way through flashing, it rebooted to recovery. Not a usual boot to recovery. The teamwin main page pulsed several times and then it rebooted to recovery. I flashed getlogs which are attached. Hopefully, they have useful information. Both primary and data-slot-stockol1 boot, but they both appear to be the same. Primary is OJ7 based and data-slot-stockol1 should be OL1. Data-slot-stockol1 has same kernel and build number as primary. Hope this makes sense and is useful.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] Thanks!! The rom is working now. :)
[Galaxy S 4 i9505 Original Android Development] r4veren:
Hello, I'm unfortunately having trouble with starting over with the 'dual' ROM: wiping it via the app immediately reboots the phone (this is what I tried first) - as does deleting a folder named multiboot/dual or something via a root file explorer and using terminal rm command. I can't find any relevant directories using TWRP file browser at all (the file structure confuses me, I'm nowhere an expert), and wiping via dualboot utilities throws an undescriptive EXIT CODE: 1.

What would you suggest to do to just destroy any traces of the dual ROM?

Anyway, thanks for your work, I just donated a little to show appreciation.
[Galaxy S 4 i9505 Original Android Development] ewangw:
Support for Moto X Pure

[MENTION=4277844]chenxiaolong[/MENTION], I tried again but realized part of my problem was my TWRP version. I was using 3.0, but downgraded to 2.8.7.1 which allowed the process to run further. In the end I still had errors and the patched files wouldn't load. I still can't get to the Multiboot log file, but added a snapshot of the ROM load process and error.

In case it's important, my phone is running stock MM 6.0, with an unlocked bootloader and rooted.
[Galaxy S 4 i9505 Original Android Development] singh54:
Need Help

First of all thanks for this wonderful app..

I used your app and followed all your procedures.

I set my touchwiz rom as primary and cm 11 as secondary

Patched the cm 11 rom and gapps files through windows gui successfully

And i installed the cm 11 rom in my external sd card (bcuz i am having low space in my system partition)

The rom rebooted successfully...

But now the problem is when i try to install gapps after patching it, it's not getting installed.

I dont know what's the reason, so anyone please help me..

I am eagerly waiting to enjoy this dual boot patcher...

So please tell me the exact procedure to install the gapps,

Please help me....

P.S: i am using s4 mini duos version and i used both the recoveries (in built and cwm) to flash the gapps, but both of them showed errors.
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
You may have done this correctly already...the patched gapps must be named exactly the same as the external slot rom.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This should be fixed in 8.0.0.r2245.gedcde27 :)

EDIT: The issue was that the "ro.bootloader" property was not copied to the installation environment, so the ROM couldn't determine which carrier modem libraries to install.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r2250.g594fc03 (EDIT: 8.0.0.r2251.gd9a452d) should fix the issue where SELinux prevents the app's reboot function from working.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That is a very odd error. The reboot happened because the device ran out of RAM, causing the kernel to kill a bunch of processes, including TWRP (and TWRP is set to restart whenever it's killed, resulting in you seeing the main page multiple times). Eventually, there was so little memory left that /init crashed, causing the reboot. If I had to guess, I think somehow the partitions weren't mounted properly. Since a directory that's not mounted is stored in memory, extracting an Odin image could easily cause that issue. That's seems to make sense since you said it failed 3/4 the way through flashing a 4GB image on a device with 3GB of RAM.

EDIT: Btw, the S6 devices have a fantastic last_kmsg kernel log. It not only saves the logs for the last boot, but also for the second last boot (and a little bit of the 3rd last boot). So much better than the Note 4.

EDIT2: I think I know the root cause of the issue.

EDIT3: Should be fixed in 8.0.0.r2255.g1b7e755 (hopefully!)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thank you very much for the support! I really appreciate it.

Regarding the wiping issue, I've never seen anything like that before. I'm not sure why attempting to delete a folder would cause a reboot. I would try deleting the folders manually from TWRP again. From TWRP, go to the mount menu and make sure system, cache, and data are mounted. Then go to the TWRP file manager and delete the following folders:

/system/multiboot/dual

/cache/multiboot/dual

/data/multiboot/dual

/sdcard/MultiBoot/dual

That will remove all traces of the ROM. Let me know if TWRP also has trouble deleting the files.
[Galaxy S 4 i9505 Original Android Development] singh54:
Thanks, but...

Thanks for the reply bro,

But even after renaming as that of the rom package, i still getting the error...

This is the error

Installation aborted - error code 70

There's insufficient storage in your system partition or external sdcard (i tried both the locations)

make some free space by erasing some gapps...............

But the funny thing i am having 150 mb free space in my system partition after installing secondary rom and i am having 7gb free space in extsdcard slot....and another thing i am using the pico gapps package which is the very lowest i.e only 42 mb!!!!!!!!!!!!!!1

So please help me with a way to resolve this...

Sorry for bothering like this:D:D:D:D:D:D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, using a root file manager, are you able to copy the MultiBoot.log file if you browse from the /data/media/0/MultiBoot.log path? If I had to guess what the issue was, I think it might be F2FS. If I remember correctly, a lot of Motorola devices use F2FS, right?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Did you happen to flash a different primary ROM? Some ROMs, especially TouchWiz-based, will mess with the SELinux labels of other ROM's files. Patching the primary ROM prevents that behavior. However, if the SELinux labels are already messed up, there's not much you can do besides flashing a custom kernel that has SELinux disabled or set to permissive mode.
[Galaxy S 4 i9505 Original Android Development] singh54:
Any idea

[MENTION=4277844]chenxiaolong[/MENTION],

Any idea about this error

This is the error

Installation aborted - error code 70

There's insufficient storage in your system partition or external sdcard (i tried both the locations)

make some free space by erasing some gapps...............

But the funny thing i am having 150 mb free space in my system partition after installing secondary rom and i am having 7gb free space in extsdcard slot....and another thing i am using the pico gapps package which is the very lowest i.e only 42 mb!!!!!!!!!!!!!!1

So please help me with a way to resolve this...

Sorry for bothering like this
[Galaxy S 4 i9505 Original Android Development] singh54:
Hurray

Finally

I managed to install the gapps successfully in the ext sdcard...

Everything is working fine in both the roms....

Thanks to the developer for this wonderful patcher app:good::good::good::good::good:

Now will try to take a complete backup of both the roms...:D:D:D;);););)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The gapps packages are highly compressed. The pico package extracts to 204MB :)

EDIT: Glad to hear that installing to the external SD fixed it!
[Galaxy S 4 i9505 Original Android Development] singh54:
Cool Bro,

Actually its my bad, i continuously flashed the gapps after flashing the rom and i didn't switch over the roms before flashing:eek::eek:

Now correctly followed the steps and flashed the GApps successfully.

Once again Millions of thanks for this app.

Bcuz my primary rom have some specifice app oriented bugs, but the rom is pretty much nice.

This app saved me to enjoy the rom as well as to get rid of that bug...:good::good::good:

One more question, if i want to update the primary rom, i have to patch the update of primary and i must be in secondary rom and then i have to flash the patched update file of primary rom, is that correct????????????
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Hi

how did you install successfully gapps (pico?) on extsd-slot-1 ?

I have still pproblem with this.

I can boot my MoKee rom extsd-slot-1 but I can't install gapps (I tried micro, nano and pico OpenGapps)

My SD card has 20 GB free space