yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] RK:
yup.. Its better if you are running a stock Samsung kernel. Although I have used it just fine with custom kernels too..
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
I think I found the bug for failing of auto-loki. Thanks to your log, I could track it

Anyone interested in trying and help in debugging auto-loki for next versions?

Obviously, you should know how to get out of a bad flash trouble!
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
I'll give it a shot
[AT&T Samsung Galaxy S 4 Android Development] RK:
Yup I'll test..
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
I am quiet sure of the issue

It is an fstat on partition to get its size.

I am working right now on a proper way

Maybe this night

You can test it by flashing it then try to flash my previous jflte non lokifying installer
[AT&T Samsung Galaxy S 4 Android Development] RK:
Will do sir as soon as you post it..
[AT&T Samsung Galaxy S 4 Android Development] emmanueldmc:
So...i have a S4 i337m (Mexico variant)...I can stop using the recovery jfltecan (6.15.4) and use jflte (6.19.3)? everything work properly?
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
Worked perfect with talexop kernel. It took me a couple days before i got the balls to commit. I must've gotten to the part where it says you might brick your device and backed out at least 30 times. LOL
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
[MENTION=4485012]RK[/MENTION] and others that will to help

v6.19.4 Loki

ALPHA

Fix

*** Do not use if you don't know how to come out of a bad flash ***

I did my best to debug it, but I have no loki device to test it

Get it from attachment

philz_touch_6.18.7-jflte.zip was missing the lokifying script in zip installer

Enabling auto loki should be able to flash it in new 6.19.4 version
[AT&T Samsung Galaxy S 4 Android Development] emmanueldmc:
Any help pelease?

Enviado desde mi SGH-I337M mediante Tapatalk
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
Doesn't work for me. I flashed it and can't get into recovery. Instead, get the yellow triangle screen.

---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
6.19.4 should boot perfectly

Once you follow exact steps, provide a log if auto-loki the unpatched image fails. Else no need to try it at all
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Up it:

[MENTION=4485012]RK[/MENTION] and others that will to help

v6.19.4 Loki

ALPHA

Fix

*** Do not use if you don't know how to come out of a bad flash ***

I did my best to debug it, but I have no loki device to test it. I tried it though and it passed the mmap aboot image error, so it should really work now

Get it from attachment

philz_touch_6.18.7-jflte.zip was missing the lokifying script in zip installer

Enabling auto loki should be able to flash it in new 6.19.4 version
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
Am i missing a new step or something? I downloaded 6.19.4, copied to sd card, flashed it by using 6.15.4 jflteatt, and tried to boot but, had to go through download mode, due to triangle.
[AT&T Samsung Galaxy S 4 Android Development] RK:
SUCCESS!!
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
Not sure what I did wrong. But, now recovery doesn't install via goomanager. It downloads the file but when i reboot to recovery, i get the triangle of death. Do I need to Odin back to mdl stock?
[AT&T Samsung Galaxy S 4 Android Development] RK:
are you trying to install TWRP via goomanager? if yes, make sure that your build.prop shows your phone as SGH-I337. (This will not be so if you are using a GE or i-9505 based ROM.) That is, make sure that your phone says SGH-I337 in settings->about phone->Model number)

If your phone says GT-I9505 or GT-I9505G, then goomanager will install a version of TWRP that is NOT loki'd and hence the yellow triangle.. In that case, get any build.prop editor from market and edit these four lines from

FROM:

ro.product.model=XXXXXXX

ro.product.name=XXXXXXXX

ro.product.device=XXXXXXX

ro.build.product=XXXXXX

TO

ro.product.model=SGH-I337

ro.product.name=jflteuc

ro.product.device=jflteatt

ro.build.product=jgedlte

Reboot, and install TWRP using goomanager and then install whichever version of philz you want.

You will still have the custom boot screen but that goes away if you use triangle away
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
Yeah. My build.prop is set. I was able to do this earlier today. I wonder if it's not installing because i chose the option to not allow recovery to flash after flashing this alpha?
[AT&T Samsung Galaxy S 4 Android Development] RK:
Idk as a last resort, I would try installing a recovery via dd.

Download this file

https://copy.com/SSpeJBaDK1di3nz

To your internal SD and run in android terminal emulator:

su

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21

Make certain that you get this command right. *Typing the wrong number could result in a brick!

The file is pre-loki'd TWRP.

Then download this:

http://d-h.st/dMX

Reboot to TWRP and flash latest philz and the Loki_recovery.zip above and you will be on latest philz again..

---------- Post added at 12:08 AM ---------- Previous post was at 12:06 AM ----------

@Phil3759 the alpha is working perfect on my device.. :)
[AT&T Samsung Galaxy S 4 Android Development] Christopher3712:
Awesome. I'll assume someone will figure this out before I do, but I'll look into it when I get home. I'm about to get off work. In the meantime, it might be a good idea to update your OP to warn other users that this recovery isn't ready for flashing yet. Or else we'll have a lot of people using ODIN tonight :)
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
First, a developer must pull the aboot image from a target device:
dan@pc:~$ adb shell
shell@android:/ $ su
shell@android:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
shell@android:/ # chmod 644 /data/local/tmp/aboot.img
shell@android:/ # exit
shell@android:/ $ exit
dan@pc:~$ adb pull /data/local/tmp/aboot.img
3293 KB/s (2097152 bytes in 0.621s)

Next, a .lok image can be prepared using loki_patch:

dan@pc:~$ loki_patch
Usage: ./loki_patch [boot|recovery] [aboot.img] [in.img] [out.lok]
dan@pc:~$ loki_patch recovery aboot.img cwm.img cwm.lok
[+] Detected target AT&T build JDQ39.I337UCUAMDB or JDQ39.I337UCUAMDL
[+] Output file written to cwm.lok

Finally, the .lok image can be flashed using loki_flash:

dan@pc:~$ adb push cwm.lok /data/local/tmp
dan@pc:~$ adb push loki_flash /data/local/tmp
dan@pc:~$ adb shell
shell@android:/ $ su
shell@android:/ # /data/local/tmp/loki_flash
Usage: /data/local/tmp/loki_flash [boot|recovery] [in.lok]
shell@android:/ # /data/local/tmp/loki_flash recovery /data/local/tmp/cwm.lok
[+] Loki validation passed, flashing image.
2253+1 records in
2253+1 records out
9230848 bytes transferred in 0.656 secs (14071414 bytes/sec)
[+] Loki flashing complete!

Looks easy. Either some one does it for me or provide the aboot.img so that I can do it

Pre-compiled binaries are here:

https://github.com/djrbliss/loki/tree/master/bin
[AT&T Samsung Galaxy S 4 Android Development] Dyaus:
Here's an aboot.img. I had it on my microsd card...
[AT&T Samsung Galaxy S 4 Android Development] Christopher3712:
There you go. Looking at the rest of it now.
[AT&T Samsung Galaxy S 4 Android Development] Christopher3712:
doh! lol. Leaving work, home in an hour. Will pick up from there.
[AT&T Samsung Galaxy S 4 Android Development] Dyaus:
Here's a zip file which contains a .lok image of this recovery. DO NOT FLASH THIS ZIP DIRECTLY. It's only a zip of the .lok file because the forum doesn't let me post a .lok file directly.

Unzip this and flash the .lok file using the loki_flash tool.

I'll leave it to Phil to create a flashable zip which can be used in a recovery...
[AT&T Samsung Galaxy S 4 Android Development] Dyaus:
Okay guys had a minute, so I made a zip you can use to flash this recovery. Flash this with CWM or TWRP. I tested flashing with OUDHS CWM and it worked just fine.

Really enjoying this recovery. Nice work Phil.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Added link in op, thank you
[AT&T Samsung Galaxy S 4 Android Development] Kole_Ackerson:
This is so bad*** man! Always have wanted my recovery to basically be MY recovery, how I wanted it to look! Simply awesome
[AT&T Samsung Galaxy S 4 Android Development] tdevaughn:
Great work Phil. Thank you dyaus!!
[AT&T Samsung Galaxy S 4 Android Development] odinfire:
Confimation

Flashed this to my Galaxy S4 ATT I337 using CWM. Works wonderfully. Made an immediate nandroid backup and it had the correct date and rom name. One question though, from all the talk of loki throughout the last few pages, was auto-loki included? Just want to be sure, so I can keep a copy on my sd card if needed.

Great work, this is a beautiful recovery. The best I've seen. :victory:
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
I only released a raw image, non patched

There is a link to loki patched version by users here in OP
[AT&T Samsung Galaxy S 4 Android Development] carlospr21:
Is it auto loki like the OUDHS-Recovery-jflteatt???

Love your recovery used it when i had the att note 2
[AT&T Samsung Galaxy S 4 Android Development] Dyaus:
It does not auto-loki.
[AT&T Samsung Galaxy S 4 Android Development] Dinky:
Questions about storage

I flashed this because it is supposed to support exFAT (at least so I thought by reading the original thread). But it can't mount the external 64GB sdcard formatted in exFAT. Second thing is, it does backup to path /data/media instead of internal sdcard (/sdcard or /storage/sdcard0). Won't the backups be wiped out when we flash a new ROM? Thanks.
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Post #3 in the original thread should cover the SD card issue.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Some 64gb exfat cards do not work

Look in Advanced menu to set to /0
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
Nope, your link is bad in your OP. It just links people back to the OP.

Here is the correct link to what you're talking about:

http://xdaforums.com/showpost.php?p=42555511&postcount=28
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Try a different browser :rolleyes:
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
Thank you. That did the trick. I didn't realize I needed to lokydoki the latest recovery.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
6.19.4 is final

It was reported working with detailed loki logging info

To flash it from older versions you need at least 6.18.7

From now on updates should be smooth

You came from too old 6.15.4

You must at least install 6.18.7 or latest by enabling ro.loki_enabled to 1
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
Where do I add that line? Is that a setting in the gui? Looks like build.prop?

The closest line i found like that was was in loki.sh:

"LOKI_ENABLED=`getprop ro.loki_enabled`

if [ "$LOKI_ENABLED" == "1" ]; then"
[AT&T Samsung Galaxy S 4 Android Development] theshow4life:
Is the new 6.19.4 pre loki because I'm coming form a older 6.15.4 too? or can someone just point me in the direction on how I loki the recovery.

Thank you
[AT&T Samsung Galaxy S 4 Android Development] RK:
Flash 6.19.4 and then flash this: http://d-h.st/dMX

---------- Post added at 12:31 PM ---------- Previous post was at 12:25 PM ----------

In 6.19.4, go to "advanced" and make sure "Apply loki patch" is ON. If not, toggle it. Then, you should be good to flash any ROM or recovery..
[AT&T Samsung Galaxy S 4 Android Development] theshow4life:
Thanks man didn't want to screw anything up.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Uploaded 6.19.6 final

Enjoy auto loki and huge thanks [MENTION=4485012]RK[/MENTION] for his logs and help
[AT&T Samsung Galaxy S 4 Android Development] geomax45:
Still need to flash 6.18.7 first if we are older than that?
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
yes
[AT&T Samsung Galaxy S 4 Android Development] Tylorw1:
So for those on AT&T S4, but on an older version of your recoveyr, I cant flash the latest jflte then loki doki afterwards? Just wanna make sure.

Tylorw1
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
yes you can

It is just my installer zip:

- the recovery.img is not lokied

- since we moved to new jflte common device, to avoid lokying other variants like jfltexx, we use ro.loki_enabled

- if your current recovery doesn't have that property, my zip installer will consider that the device doesn't need to be lokied

- you can flash it and loki-doki after it before rebooting

- you can also do "adb shell setprop ro.loki_enabled 1" and flash latest zip after that to auto loki on flashing
[AT&T Samsung Galaxy S 4 Android Development] Tylorw1:
Ok thank you. I just wanted to be 100% sure. The easiest way since I have the AT&T variant that requires loki, is to just flash the loki-doki recovery zip afterwards, that way you know for a fact it will be loki'd either way.

Thanks a bunch for the quick reply.

Tylorw1
[AT&T Samsung Galaxy S 4 Android Development] RK:
The standard loki-doki.zip does not patch recoveries. It only patches kernels. You need to do the adb shell setprop thing OR flash the loki_recovery.zip I posted a few posts back instead of loki-doki.
[AT&T Samsung Galaxy S 4 Android Development] gorgy76:
fix permission option

I have flashed the latest posted recovery a while ago but I can't seem to find where is the fix permission option in the recovery. I tried navigating on the advance and philz setting but can't locate it or is it simply not included. Thnx
[AT&T Samsung Galaxy S 4 Android Development] scloutkst:
THANK YOU!!!!!

I couldn't get onto the newest version of philz no matter what I tried. I had an already lokied recovery of philz that was old. When I tried to flash new version the auto loki kept failing. I had no idea their was a loki recovery zip. I was getting ready to pull my hair out when loki doki kept failing to make the new recovery load. And no matter how many google searches and thread searches I did, I kept coming up empty handed, until I happened upon your post. Thank you for the link to the recovery zip!
[AT&T Samsung Galaxy S 4 Android Development] Locoman_:
Im using a slightly older version and couldn't find it. I use rom manager for that.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
notice:

seems like latest versions under jflte are not loki enabled (no loki menu, not lokify enabled on install)

6.24.9 will fix this
[AT&T Samsung Galaxy S 4 Android Development] kevin_3_57:
Hi!

I'm trying to flash philz_touch_6.25.4-jflte.zip to my SGH-i337 using TWRP v2.6.3.1 on STOCK Slot, but when flashing I get this message:

Installing '/sdcard/philz_touch_6.25.4-jflte.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/philz_touch_6.25.4-jflte.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip does not contain SELinux file_contexts file in its root.

######################
PhilZ Touch Recovery
Full Touch CWM Based
+
Advanced Features
Phone jflte
######################

Flashing Recovery...
minzip: Extracted file "/tmp/loki.sh"
minzip: Extracted file "/tmp/loki/loki_tool"
about to run program [/tmp/loki.sh] with 1 args
4096+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.089508 seconds, 22.3MB/s
Loki tool v2.1
[-] Failed to find function to patch.
run_program: child exited with status 1
script aborted: assert failed: run_program("/tmp/loki.sh") == 0
assert failed: run_program("/tmp/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/philz_touch_6.25.4-jflte.zip'
Error flashing zip '/sdcard/philz_touch_6.25.4-jflte.zip'
Updating partition details...

Can someone enlighten me a little into what's going on here?

Thanks very much!

PS: I also tried setprop ro.loki_enabled 1 before flashing but with the same result as mentioned above.

PS2: I337 on 4.2.2 MF3
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
You can not Install any other recovery besides safestrap. Read up on locked boot loader or you will brick you're phone.

Sent from my Nexus 7 2013
[AT&T Samsung Galaxy S 4 Android Development] kevin_3_57:
I knew Safestrap was the one to go, but I also thought I could install PhilZ Touch to be able to install a touchwiz-based rom. Thanks
[AT&T Samsung Galaxy S 4 Android Development] MJD:
The time and date in recovery have suddenly changed and are incorrect. It currently says 23:16 UTC +1:30 - 2014-01-07. It is 14:16 and 2014-04-28. I have been into Philz settings and changed the time and date and validate the new time and date but when I exit out and go back into recovery it has changed back to the wrong time and date.

Running 6.15.4.

Is there any way of fixing this as all my backups are starting to get odd dates.
[AT&T Samsung Galaxy S 4 Android Development] JT1510365:
question

to get this on my s4 do i flash loki doki.zip with the recovery? PS i am on android 4.4.2 kitkat with the SGH-i337 S4
[AT&T Samsung Galaxy S 4 Android Development] Tylorw1:
If you are on stock 4.4.2 then your boot loader is locked. If you are on the AMDL boot loader, Then yes you flash jflteatt version 6.15.4. This is a recovery, and version 6.15.4 is already loki'd. Recoveries and kernels use different Loki's. loki-doki.zip is for kernels ONLY.

And if you want the most updated version, you can go under jflte versions and download latest, but after you flash it, you must flash the loki-recovery.zip in which can be found in this thread. But, I would suggest just flashing 6.15.4 as it is already loki'd and will prevent any error. Just remember, you must have a boot loader that is unlocked and can be hacked via loki-doki.

Tylorw1
[AT&T Samsung Galaxy S 4 Android Development] JT1510365:
I have the nb1 bootloader so that means i never can get clockworkmod? How do i get the other bootloader?
[AT&T Samsung Galaxy S 4 Android Development] Tylorw1:
You cannot. AMDL is the last loki'able firmware and you cannot downgrade to it. Since you are updated, you are stuck using Safestrap ONLY. Meaning the only custom recovery you can use IS Safestrap and you CANNOT flash any custom kernels.

Tylorw1
[AT&T Samsung Galaxy S 4 Android Development] JT1510365:
well that sucks! I don't want to bore you with my questions but do you think that we will ever be able to root 4.4.2 kitkat and be able to get a custom recovery to install pac rom? How long would it take?

Thanks for your help!

Peace!
[AT&T Samsung Galaxy S 4 Android Development] Tylorw1:
Lookup SafeStrap Recovery. That is about all you can do right now, and how long it will take is unknown, and is likely to never happen as people will just move to carriers with phones with unlocked boot loaders.

Tylorw1
[AT&T Samsung Galaxy S 4 Android Development] cmdru1980:
I got a galaxy s4 and it refuses to let me install the .zip or .md5 phillz. Anything that can help?

Thanks.

C:confused:
[AT&T Samsung Galaxy S 4 Android Development] ozziedog:
What firmware do you have? If other than MDB or MDL on AT&T I don't think is will work.
[AT&T Samsung Galaxy S 4 Android Development] cmdru1980:
Yeah. I got NB1. I saw somebody else said i can't use anything but, safestrap which sucks cause I love customization and I can't figure out how to theme with safestrap. Oh well.

Thanks,

C:good:
[AT&T Samsung Galaxy S 4 Android Development] NHComp:
ATT S4 I337 issues

ATT S4 I337 issues

I had your recovery working fine some months ago and installed a CM ROM. After playing with it for a while I went back to 4.2.2 stock (MDB). Now I can't get a custom recovery on the phone - ROM Manager says CWM or TWRP are there but it keeps booting into Android recovery. Today I tried installing philz_touch_6.15.4-jflteatt.tar.md5 but it failed in Odin 1.85. It seemed to be going fine until:

<ID:0/007> Complete(Write) operation failed.

The text on the phone says;

WRITE PROTECTION Enable

Start [224,1440]

SECURE CHECK FAIL: recovery

(the last two lines are in orange)

Any idea what's going on? Titanium Backup confirms that I'm rooted and I have the latest USB drivers on the computer. Using Windows 8.1, running Odin in Admin mode. SuperSU. Changed USB port, changed cable.
[AT&T Samsung Galaxy S 4 Android Development] RK:
If you are rooted then forget Odin and do the following.

1 Download the latest loki'd twrp recovery image file from here:

http://techerrata.com/browse/twrp2/jflteatt

2 Rename the file to recovery.img and move it to /sdcard (internal memory)

3 Download latest philz recovery from here : http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte

4 Download loki_recovery.zip from here: http://d-h.st/dMX

5 Install terminal emulator app

6 open terminal emulator and run the following commands:

su

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21

7 Reboot to recovery. You should boot into twrp recovery at this point. Now flash latest philz recovery and then flash loki_recovery.zip

Done!
[AT&T Samsung Galaxy S 4 Android Development] yishay:
Hello

The 2 last recoveries for LG Optimus 4x HD (P880) don't work properly, no control from touch or arrows.

The only version that works well is philz_touch_6.26.6-p880.zip.

Please check.
[AT&T Samsung Galaxy S 4 Android Development] NHComp:
Thanks, I'll try it this weekend.
[AT&T Samsung Galaxy S 4 Android Development] kpirnie:
Am I right in assyming this is only for thise on unlocked bootloader?
[AT&T Samsung Galaxy S 4 Android Development] rob219:
can this be used on rooted 4.4.2 stock with safestrap installed? or is it only for older android versions with loki support? im asking because i have the at&t note 3 and im setting my friends s4 up for him and would like to see if anything but safestrap can be used before i flash a rom.

nevermind i think i figured out it cant be used.
[AT&T Samsung Galaxy S 4 Android Development] svs57:
i337 mdl jflteatt 6.15.4

flash talexop 9505 kernel:

Got error while lokify:

E: [-] Failed to mmap aboot.

E:Error loki-ifying the boot image
[AT&T Samsung Galaxy S 4 Android Development] RK:
This has been fixed update to the newest jflte unified version
[AT&T Samsung Galaxy S 4 Android Development] svs57:
Thank you.

I think needs to add instruction how to flash latest Philz Touch and lokied it.
[AT&T Samsung Galaxy S 4 Android Development] rohailadnan:
aboot version not matched ??
[AT&T Samsung Galaxy S 4 Android Development] mocsab:
I have been using OUDHS CWM recovery and wanted to know if the nandroids I created in that recovery will be compatible with this version of CWM?
[AT&T Samsung Galaxy S 4 Android Development] Dyaus:
They are.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Looking at OUDhs cwm source, it is basically a cwm base mod with minor changes, so it is barely a cwm and backups should be fully compatible
[AT&T Samsung Galaxy S 4 Android Development] mocsab:
thanks - now that this had been "loki-fied' I think I will give it a shot! thanks for all your work - it is appreciated.
[AT&T Samsung Galaxy S 4 Android Development] Dinky:
Hmmm... switching storage to /data/media/0 in Advance put backup on internal sdcard instead of internal storage, At least it won't get wiped out by flashing a new ROM I guess. It doesn't work for installing zip from sdcard either. If I select "Choose zip from External sdcard", I get "E: Can't mount /external_sd/" error at the bottom. I intentionally went with name brand sdcard hoping it will get better compatibility, I guess it doesn't help... :(
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
I think you are confusing things

Try to explain better your issue and eventually post a log
[AT&T Samsung Galaxy S 4 Android Development] fast96:
First, thanks for all the hard work going on here. :good:

I have a new (2 days) AT&T SGH-I337, tried to flash the Philz-touch because I LOVE it on my Gtab2 7.0. Had some serious resets. So I got my head extracted from my butt, and read my way to the end of this post. LOL

Is the "loki-fied" version ready to flash from CWM 6.0.3.2 touch version? Or should I wait for more feedback? I don't mind the padlock so much, but I really like the Philz version of CWM. :D

Thanks for your time.

Dan