[Galaxy S 4 i9506 Android Development] jupeke:
Greetings everyone,

I've been using [MENTION=4188575]DeHAWK[/MENTION]'s wonderful kernel and ROM pretty much as long as I have owned an I9506. They have always been working absolutely great and I would like to thank for the awesome work done!

Today however, I ran into problems for the first time and I cannot seem to be able to solve them.

First, I am going to explain the situation as it happened:

I had NEE-XUDOF2 installed with NON-OC XXUDOF2 v1.7.0 insecure kernel and I had used file called "update_XXUDOF2_Full_De-Odexed_v1.zip" (I assume this was the name of the file for I don't have it anymore, my first mistake, but we'll come to that later) to DeOdex my ROM. Things were working fine and I even had arter97's Xposed installed (xposed-v65-sdk21-arm-arter97-V5-krait.zip) and working. For recovery I was using TWRP 2.8.5.0.

Yesterday, realizing that a new kernel had come out (ver 3.0.7) and that there was new version of the Full DeOdexed system update (ver. 1.0.7), I decided to update these to my phone. I downloaded both files to my phone's external SD card and at the same time deleted the update files for the previous ones (a stupid move). First I installed the kernel and rebooted the phone. Everything went absolutely perfect. After having downloaded the Full DeOdexed system update 1.0.7., I booted to the recovery and installed this update. This is where things started to go wrong. Now, upon rebooting my phone, I was greeted with the familiar Samsung logo for far too long. My phone was just rolling the booting logo for something like 45 minutes before I rebooted it to recovery. During this 45 min I had thought that maybe the reason for this was the fact that I had arter97's Xposed v65 installed, so I downloaded his uninstaller and uninstalled that before rebooting my phone again. This time my phone booted indeed, however I realized that all my personal settings had been resetted. Also the pulldown menu was not working properly (buttons for settings and more tiles did nothing) and no any kind of notifications appeared there (the sounds of the notifications did play but nothing appeared in the pulldown menu); clock, WiFi, BlueTooth states etc. were working and showing fine. Also the home button did not work (did not take me to dashboard). I of course thought this might have been an effect caused by the fact that I had my phone stuck in the boot sequence and had to forcefully reset it, so I didn't get too worried yet.

Next what I did was to use Odin 3.09 to install the original NEE-XUDOF2 ROM. This did fix the pulldown menu and the notifications. Alright, next to use the same Odin 3.09 to install recovery TWRP 2.8.7.0 (successful), then the latest kernel 3.0.7 from the external SD from within the recovery (successful). Finally it came the time to install Full DeOdex system update ver. 1.0.7. Recovery manager said that everything went fine and told me to reboot, I did, and I did not end up stuck in the boot logo this time, however, once I got the system all booted up again I found out that my personal system settings had been wiped out, home button didn't work and the pulldown menu didn't work (the same as last time, buttons for settings and additional tiles didn't work and the notifications were nowhere to be found).

This is basically where I am right at the moment. I have thought out that my options would be:

1) To try out using older version of the Full DeOdexed system update, because this is the part of the process that seems to cause trouble and I do know for sure that the previous version I used (I think it was just numbered v1) did work. However, this I cannot do because I was stupid enough to delete the older version of the file when I downloaded the current v107 (so if anyone can provide my with older version of this file, that would be HUGELY appreciated)

2) Installing the Full DeOdexed system update while on the 1.7.0 version of the insecure kernel and see if that has any difference

3) To do a full wipe, installing everything a new (I really hope I won't have to do this).

I am starting to be very much afraid that I will need to do the full wipe. However, before that I would so much want to try other version of the Full DeOdex system update to find out if they cause the same effect or if it's just this latest one.

I hope I was comprehensive enough in my description of the problem. If that is not the case, I apologize in advance, and promise that I will strive to provide any information that might be deemed necessary so that someone might possibly be able to help me with this problem.