yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] v00d007:
The 'pre ramdisk patched' kernel is backed up in sdcard/multiboot/rom-slot as "boot.img.before-ramdisk-update.img". You can simply rename it to boot.img i.e. with your preferred custom recovery's file managing function.
[Galaxy S 4 i9505 Original Android Development] Steven1962:
Thanks a lot for your tip but my problem was actually not being able to use app sharing with this rom.
[Galaxy S 4 i9505 Original Android Development] whymoo:
Rapture/Back-to-N0t3

I'm trying to dual boot two roms and I get a bootloop.

Primary Rom: Rapture v2.1

Primary Kernel: arter97 4.1

Secondary Rom: Back-to-N0t3 v5 xposed

Secondary Kernel: arter97 4.1

Recovery: arter97 Philz Touch 4.1

Partitions: f2fs

Device: g920t

Bootloader: 5.0.2 engineering bootloader

Result: Bootloader than blackscreen loop

log attached
[Galaxy S 4 i9505 Original Android Development] v00d007:
App sharing is known to be a buggy/future feature, I don't use it anymore after having lots of trouble and data mess/loss. My tip was just for the case that activating app sh. results in unbootable roms.
[Galaxy S 4 i9505 Original Android Development] todivefor:
Galaxy S6 Sprint. I have Primary and 2 roms in data slot, all 3 TW. I flashed my current rom (OGE-deodexed-v1.zip) and kernel (UniKernel-v6-0001-920P-080215.zip) sometime ago with R1607 in data slot. I haven't flashed anything in almost a month. Today, I decided to backup (TWRP 2.8.7.1) in preparation for reflashing primary. The backup failed due to not enough space. I rebooted, it looped in the rom boot animation. I rebooted recovery for DB utilities. The rom in data slot I wanted to select was not listed, just primary and my other data slot rom. I flashed boot.img from /sdcard/multiboot/my-data-slot. Rebooted. Same thing boot loop. I flashed the patched kernel I had around and everything is back to normal. Anything I should capture if it happens again? Any idea what caused this?
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=2688336]todivefor[/MENTION]

Are you sure that none of the partitions ran out of space with 3 big, fat TW roms? In that case the roms won't boot anymore.
[Galaxy S 4 i9505 Original Android Development] sronweb:
Question: any suggestion about individual app sharing? In example I have Firefox on primary rom (Echoe), i share apk or data and then I repeat on a CM12.1 which on data-slot 1 but when I open Firefox I get force close. Luckily it does not happen with all apps.

I understand that sharing apps between Touchwiz based rom and AOSP rom might not work for some compatibility? But I don't understand if I simply share data which problem might be generated. Thanks
[Galaxy S 4 i9505 Original Android Development] v00d007:
You'll have to wait until chenxiaolong announces that he made it and releases a stable version with a full functional app sharing feature...
[Galaxy S 4 i9505 Original Android Development] cruor.am:
Hi dev!

First I have to say thank you for your work, I think it is great!

Unluckly, I'm not able to multiboot ROMs anymore. After installing patched ROM my phone stucks for a while on samsung logo and then reboot to recovery.

My phone is a Samsung Note 3 sm-N9005 (international version). My primary ROM is Arya Mod 7.2 with ShintoKernel and I tried to multiboot Dirty Unicorns 9.6 then unofficial BlissPop 3.7. I've tried to install them using both TWRP and in-app flashing.

I've system, data and cache partition formatted in f2fs. My recovery is TWRP 2.8.7.0.

Before formatting in f2fs I was able to multiboot all ROMs without any issues, so is f2fs the bad guy??:confused:

Here attached the log. Thanks again!
[Galaxy S 4 i9505 Original Android Development] todivefor:
No. After flashing kernel, I am running fine.
[Galaxy S 4 i9505 Original Android Development] sronweb:
Since a couple of weeks I have started to use xposed modules on CM12.1 nightly but as I could see from previous post (@todivefor I guess was one of the user If I remember correclty) flashing Xposed modules might generate issues with Dual boot.

Currently after flashing or updating a rom it happen that I los the primary rom and I cannot boot again from it. Xposed module was installed on CM12.1 on multi-slot 1 and now I'm testing on data slot 01.

When I use latest multiboot utilities I don't see the primary rom but only the data-slot.

Is it xposed currently not compatible?

---------- Post added at 08:07 PM ---------- Previous post was at 08:03 PM ----------

For some apps I can say is working fine but I understand that is not stable, but here on xda I guess nobody is expecting a "stable" release. Perhaps with some testing, reporting might help Chen to understand how to improve the patcher.
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=4277844]chenxiaolong[/MENTION]

As I mentioned before, I didn't have problems flashing cm12.1 roms some time ago. So, I installed an older build v1460 and - boom, it worked. You seem to have changed some things in the meantime that force this (new) errors.
[Galaxy S 4 i9505 Original Android Development] todivefor:
sronweb, I don't think my xposed issues were dualboot related. I had to do a clean flash of my rom to get exposed to work. Xposed on the S6 is pretty alpha. I have been running it on my data slot TW rom for some time with no issues.
[Galaxy S 4 i9505 Original Android Development] sronweb:
Thanks. Most probably the boot problem with Echoe is due to limited space on primary slot but I'm not sure if also there are some changes on recent Patcher versions which has some new issue because to be honest I didn't had these problems before in the same configuration.

In case of space issue I should find another Touchwiz rom based on Lollipop which has less space requirement. In the past I used Shostock 8.0 but its for KitKat.
[Galaxy S 4 i9505 Original Android Development] todivefor:
Was running my data slot rom (happens to be my main rom). This time I ran TWRP backup which completed successfully. Boot lopped in data slot rom boot animation. Rebooted directly to TWRP. Pushed GetLogs-20150827.zip to /sdcard (don't know if this does anything to screwup the logs). Flashed logs zip which are attached. Reflashed kernel on data slot, it boot looped. I tried flashing boot.img (from data slot). After thinking about this, that probably flashes to primary? Reflashed primary kernel. Booted up primary, switched to my data slot which now boots (showup in apk rom list, but not DB utilities rom list). Sorry this is so convoluted, but would like to get a grasp on how a TWRP backup can do this. Seems like I can reproduce, so please let me know what is needed.
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Hi [MENTION=4277844]chenxiaolong[/MENTION]

Do you know why I got "Failed to remount / as ro" ?

I installed MIUI on my S5 SM-G900F (klte) and got bootloop.
[Galaxy S 4 i9505 Original Android Development] !Led*Eyes!:
may i make a suggestion? Can you, from the mac, make a tar.zip and then it can be flashed from odin ( if you can) or just unzipped through recovery?? I just thought it may be easier to make a tar ball with a mac than a pc
[Galaxy S 4 i9505 Original Android Development] ad346:
Im in like Noob101, i have no idea what a tar is?
[Galaxy S 4 i9505 Original Android Development] scott62185:
could you add support for euroskank versions of cm 10.2 (for jfltevzw)? http://fitsnugly.euroskank.com/?rom=cm10&device=jfltevzw
[Galaxy S 4 i9505 Original Android Development] !Led*Eyes!:
No worries man! .tar files can be flashed through the PDA section of ODIN while the zips need to be applied through a custom recovery... I dont know what recovery you guys have cause ive been running around like crazy but isnt the AROMA installer being flashed through recovery?
[Galaxy S 4 i9505 Original Android Development] ad346:
im running clockwork mod
[Galaxy S 4 i9505 Original Android Development] !Led*Eyes!:
How stable are we with that yet... I cant try anything right now
[Galaxy S 4 i9505 Original Android Development] scott62185:
Not sure what you mean...as far as I know the rom is very stable.
[Galaxy S 4 i9505 Original Android Development] scott62185:
I havent tried it but im sure its good. But if it hasnt already been stickied there is either a problem, or its on another page already.

I have no idea what you're trying to say here. :)
[Galaxy S 4 i9505 Original Android Development] !Led*Eyes!:
when the mods find good roms, they "stickie" them so they stay around for people to Download. If they arent "stickied" there may be a problem... im not sure exactly but i cant sticky it myself.... look harder on the site, im sure its somewhere
[Galaxy S 4 i9505 Original Android Development] jova33:
Will this work for Hyperdrive VZW? It's the most popular VZW ROM.

And this'll work with all the loki stuff for the people on the MDK bootloader?
[Galaxy S 4 i9505 Original Android Development] DreenHotdog:
Just after reading how to actually manually patch zip files, I will be adding patcher support for both of the Omega ROM types for the S4. I will be patching v13.1 of the original Omega ROM (Android 4.3 Touchwiz) and the Omega Google Edition ROM v2.0 (4.3 GE AOSP).

Just posted this so everyone who likes Omega ROM knows.

Links: http://xdaforums.com/showthread.php?t=2253528

http://xdaforums.com/showpost.php?p=40778494&postcount=6

:good:
[Galaxy S 4 i9505 Original Android Development] !Led*Eyes!:
wish i wasnt strapped in!! im riff boxing mine this week in an attempt to get back MDK
[Galaxy S 4 i9505 Original Android Development] !Led*Eyes!:
But if you are confined to me7... I didnt think you could keep stock 4.2.2 running in the background and successfully flash 4.3 roms and gapps? I was under the impression if you had ANY 4.2 apps left behind it was doomed?!?!
[Galaxy S 4 i9505 Original Android Development] rlorange:
I think it's possible to make the Patcher run from the device!! Python for Android but its beyond me. ..

https://db.tt/MajpsQ5t
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Awesome, thanks! I'll see if I can get version 2.0 of the patcher released today. With that version, only the updater-scripts (or aroma scripts) need to be modified. The ramdisk is handled automatically now.
[Galaxy S 4 i9505 Original Android Development] The1nonly1:
Would this mean that all ROMS are supported or would they still require manual patching?
[Galaxy S 4 i9505 Original Android Development] DreenHotdog:
No problem dude, I'm happy to help! Yeah, I've realized how busy you've been with requests! I'll just help lighten the load when I have spare time!
[Galaxy S 4 i9505 Original Android Development] DreenHotdog:
Haha, I just looked at the Github postings. I hate windows with a passion haha. Well so do I! :) I think everyone hates windows with a passion unless they're hard core gamers :P
[Galaxy S 4 i9505 Original Android Development] gaww:
Not 100% sure what you saying, but I have 4.2 base (ROM 1) with 4.3 second ROM + gapps with no issues.

---------- Post added at 07:25 PM ---------- Previous post was at 07:07 PM ----------

I am not clear on how this whole process (not the patcher itself) works. When you add patcher support for the Omega ROMs - how (and will) they be available ?

And are you doing this so it can be used as secondary ROM - and will Aroma run OK on the install?
[Galaxy S 4 i9505 Original Android Development] v00d007:
They are buggy right now. v1685 i.e. fails to switch to my 2nd rom with (wrong) "kernel has wrong hash" error message. Older versions like snapshot 4 work.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
[MENTION=4277844]chenxiaolong[/MENTION] Sorry to disturb you with a new device request.. [emoji6] But this one is my friend's phone - a Lenovo S650 with a Mediatek SOC too..

ro.product.device=Lenovo S650 (screenshot is attached)

The result to the command line you gave (ls -lR /dev/block/platform/) is:

u0_a78@Lenovo S650:/ $ ls -lR /dev/block/platform/

/dev/block/platform/:

drwxr-xr-x root root 2015-09-11 21:12 mtk-msdc.0

drwxr-xr-x root root 2015-09-11 21:12 mtk-msdc.1

/dev/block/platform//mtk-msdc.0:

drwxr-xr-x root root 2015-09-11 21:12 by-num

lrwxrwxrwx root root 2015-09-11 21:12 mmcblk0 -> /dev/block/mmcblk0

lrwxrwxrwx root root 2015-09-11 21:12 mmcblk0boot0 -> /dev/block/mmcblk0boot0

lrwxrwxrwx root root 2015-09-11 21:12 mmcblk0boot1 -> /dev/block/mmcblk0boot1

lrwxrwxrwx root root 2015-09-11 21:12 mmcblk0p1 -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 2015-09-11 21:12 mmcblk0p2 -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2015-09-11 21:12 mmcblk0p3 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2015-09-11 21:12 mmcblk0p4 -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2015-09-11 21:12 mmcblk0p5 -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2015-09-11 21:12 mmcblk0p6 -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 2015-09-11 21:12 mmcblk0p7 -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2015-09-11 21:12 mmcblk0p8 -> /dev/block/mmcblk0p8

/dev/block/platform//mtk-msdc.0/by-num:

lrwxrwxrwx root root 2015-09-11 21:12 p1 -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 2015-09-11 21:12 p2 -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2015-09-11 21:12 p3 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2015-09-11 21:12 p4 -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2015-09-11 21:12 p5 -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2015-09-11 21:12 p6 -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 2015-09-11 21:12 p7 -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2015-09-11 21:12 p8 -> /dev/block/mmcblk0p8

/dev/block/platform//mtk-msdc.1:

drwxr-xr-x root root 2015-09-11 21:12 by-num

lrwxrwxrwx root root 2015-09-11 21:12 mmcblk1 -> /dev/block/mmcblk1

lrwxrwxrwx root root 2015-09-11 21:12 mmcblk1p1 -> /dev/block/mmcblk1p1

/dev/block/platform//mtk-msdc.1/by-num:

lrwxrwxrwx root root 2015-09-11 21:12 p1 -> /dev/block/mmcblk1p1

u0_a78@Lenovo S650:/ $

I hope this is the required info and you can add support for this device..

Thanks in advance.
[Galaxy S 4 i9505 Original Android Development] todivefor:
I just had this happen to me without running TWRP recovery. I just did a normal reboot because galaxy apps was stuck trying to install something. Reboot bootlooped as above. Flashed GetLogs-20150827.zip, logs attached. Booted DB utilities (snapshot7), my rom was not listed. Reflashed kernel and it booted.
[Galaxy S 4 i9505 Original Android Development] sronweb:
I did a clean installation from scratch formatting the internal memory and re-installing the TW based rom (I have installed Hulk which is one of the smaller size) and after CM12.1 nightly as multislot1. For the moment I'm ok.

Just a small issue (a graphical issue) on recent Dual boot utilities zip 8.0.0.r1697 which shows me only primary rom, then I have "save last_kmsg log" but if I select this option instead I have the multislot 1 options (switch, wipe). [MENTION=4277844]chenxiaolong[/MENTION], please, do I need to provide the logs (get logs)? Thanks
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I think I know what's going on. I forgot the patcher added fuse-exfat to the ramdisk in order to support booting from exFAT-formatted external SD. cards That adds an additional ~280KB, which might have made the difference compared to the older versions.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! Could you send me a link to the kernel's flashable zip? The error was this:

<15>[ 2.438538] mbtool: ROM ID is: data-slot-secondary
<11>[ 2.438725] mbtool: fstab does not contain all of /system, /cache, and /data!
<11>[ 2.438753] mbtool: Failed to mount fstab
<6>[ 2.438813] SysRq : Emergency Remount R/O
<4>[ 2.438831] Emergency Remount complete

My code for some reason failed to parse the /fstab.samsungexynos7420 file. When happens it's supposed to reboot into recovery, but the kernel you're using crashed instead, causing the boot loop. This should be a rather easy bug to fix, but I'll need to take a look at the kernel first. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, it looks like proc/last_kmsg is missing from the logs, but if I had to guess, f2fs is most likely the issue. If you format your partitions with f2fs, every ROM you flash must also support f2fs.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The "Failed to remount / as ro" happens for some ROMs, but it is not a big deal and wouldn't cause the bootloop.

When the ROM boot loops, could you reboot into recovery (without turning the phone off completely) and flash https://snapshots.noobdev.io/misc/getlogs/GetLogs-20150827.zip? It will copy a bunch of logs to /sdcard/logs/. That should help me figure out what's going on. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That's a security feature to prevent switching ROMs if anything other than the patcher itself touches the boot.img files in /sdcard/MultiBoot. Of course, this feature makes no sense in the recovery environment where you can do anything. This should be fixed in 8.0.0.r1698.ge9db4ca (which will be built once I figure out why Jenkins on my server is offline).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
https://snapshots.noobdev.io/, https://jenkins.noobdev.io/, and https://noobdev.io/ are going down for repair.

A failure in the latest package updates killed quite a few services running on the box. They will come back online after I restore from the last good backup and redo the updates.

The root cause was running out of disk space on the server. This did not affect any of the DualBootPatcher files (no builds were partially uploaded), but just in case this affected downloads, the following md5sums are known to be good: https://dl.dropboxusercontent.com/u/486665/MultiBootPatcher/20150912.md5sums

Thanks for your patience while I fix this issue!

EDIT: Websites are back online! They now run on better VM on https://www.digitalocean.com/. I've banned a few hundred malicious IPs and set up a 24 hour autoban for any IP that fails to login anywhere (https://jenkins.noobdev.io, etc.). The malicious traffic was getting ridiculous (about 20 times the non-malicious traffic).
[Galaxy S 4 i9505 Original Android Development] cruor.am:
Thanks for your answer [MENTION=4277844]chenxiaolong[/MENTION]! So it seems f2fs is the problem. Though, dirty unicorns and blisspop ROMs and Temasek's kernel (in meanwhile I tried booting some ROMS flashing this kernel) are all f2fs fully compatible. It's a weird problem. [emoji13] If I can provide you some more informations tell me, I will help as I can.
[Galaxy S 4 i9505 Original Android Development] whymoo:
Thank you!

Here is the rom https://www.sendspace.com/pro/dl/qu8w13

And here is the kernel http://arter97.com/browse/S6/kernel/4.3/g920tw8/arter97-kernel-g920tw8-4.3.zip

Edit: On another forum I was told that the issue was that dual boot patcher doesn't support the boot partition for noblelte which the arter97 kernel uses and unfortunately back-to-n0t3 rom only supports arter97 kernel.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! It looks like arter97 has some sort of minimal dual boot support (maybe the author uses it for him/her-self?). Anyway, I think it should be fixed in 8.0.0.r1705.g8523527.
[Galaxy S 4 i9505 Original Android Development] ItzShadowz:
Haven't checked the latest build yet (so idk if there is support for this) but are you able to add support for the LG G4 (European version)? Just so that when CM comes out I can switch from stock to CM. I use your patcher on my S4 and it's brilliant! Keep up the good work :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Will do :) Could you send me a link to a kernel or ROM for the device? It looks like this device doesn't give names to the partitions (unlike yours, which has paths like "/dev/block/platform/mtk-msdc.0/by-name/system" vs. just "/dev/block/mmcblk0p17"). Thanks!
[Galaxy S 4 i9505 Original Android Development] 54NJ41:
Hello boss [MENTION=4277844]chenxiaolong[/MENTION] with the latest dual boot app in note 3 miui rom is not supported. Patches the file with out any error and while flashing the file also no errors. But after rebooting the system it's stuck on the Samsung logo. Please be kind enough to look in to this matter. Thanks in advance.

S ent from my SM-N920C using XDA Free mobile app
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Does it still do the same thing if you set the kernel in the app? From what I see in the logs, the kernel that was running when it bootlooped is an unpatched and did not load any dual boot code. I'm not familiar with the kernel code, but it looks like the kernel itself might have crashed.

< 1>[ 2.901811] [6: kworker/6:1: 1340] Unable to handle kernel paging request at virtual address 2000000001
< 1>[ 2.901818] [6: kworker/6:1: 1340] pgd = ffffffc000202000
< 1>[ 2.901826] [6: kworker/6:1: 1340] [2000000001] *pgd=0000000000000000
< 4>[ 2.901866] [6: kworker/6:1: 1340] ------------[ cut here ]------------
< 2>[ 2.901874] [6: kworker/6:1: 1340] Kernel BUG at ffffffc000513258 [verbose debug info unavailable]
< 0>[ 2.901882] [6: kworker/6:1: 1340] Internal error: Oops - BUG: 96000005 [#1] PREEMPT SMP

One reason a restore might break this is that TWRP does not back up the internal SD, so /sdcard/MultiBoot is not backed up. If anything in there was changed between the time you did the backup and restored, then it might screw up the ROMs. Since reflashing the kernel allows it to boot again, I think all you need to do is set the kernel from the app.

EDIT: You mentioned you were using DualBootUtilities snapshot 7. That does indeed have a bug where ROMs might not show up in the list. There are newer DBU builds that fix this. In fact, every build now includes the latest DBU.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Crap, I'll take a look and fix the DualBootUtilities. Thanks!

EDIT: Fixed in utilities 8.0.0.r1707.g79cff94. It was trying to read the ROM name you set in the app from /sdcard/MultiBoot/[ROM]/config.json. However, if the name was cleared (reset to default), the name becomes empty and AROMA hides all empty menu entries.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I will need to see some logs to know why it's hanging. Could you flash https://snapshots.noobdev.io/misc/getlogs/GetLogs-20150827.zip and attach the logs in /sdcard/log/?

When it hangs, you'll have to reboot to recovery without shutting down or pulling the battery (or else some logs are lost). On the Note 4, you can do this by holding Power + Vol. Down for 10 seconds and then immediately Vol. Up + Home when it vibrates. I believe it should be the same on the Note 3.

Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, now that I think about it, it really depends on how f2fs is implemented in the ROMs. Some ROMs run a script during boot to determine if the partitions are f2fs. I know for sure those won't work after 8.0.0.r1460.g3f4675b due to the new method of booting needed for supporting extsd-slots.

Could you give me links to the ROMs and kernels that you tried? I'll take a look and see if I can figure out something to make these work. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Absolutely :) But I will need someone with the G4 to flash https://snapshots.noobdev.io/misc/getlogs/GetLogs-20150827.zip and send me the file it creates in /sdcard/logs/[Date and time].tar so I can get all the device information I need to properly add support for the device.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Thank you so much [emoji5] [emoji4]

Were you busy for a while? Didn't post anything..

Anyway, here's the link to an AOSP ROM for that device: https://yadi.sk/d/DDhVRp-1dteou (It is based on 4.4.2)

There's also a CM 12.1 ROM for it: https://yadi.sk/d/PrysaCXjhRrUD

Here's the link to its 4pda forum: http://4pda.ru/forum/index.php?showtopic=567114

Thanks again for your very kind approach [emoji56]
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Hi [MENTION=4277844]chenxiaolong[/MENTION]

Thank you very much efford

I patched new vesrion of MIUI rom (v5.9.11) by your new patcher 8.0.0.r1700.g49a3526 and I booted do MIUI on data-slot1 :)

Thanks a lot!