yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] Dyaus:
Yes, you can flash the loki'd version from your recovery.
[AT&T Samsung Galaxy S 4 Android Development] Christopher3712:
Have you correctly formatted your sdcard? 64GB sdcards need to be formatted with a program such as fat32format or guiformat in order to be properly read by this recovery. There are threads on XDA about it.
[AT&T Samsung Galaxy S 4 Android Development] Dinky:
yea... Don't want to give up exFAT format on the sdcard just yet...
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Ensure it is formatted as a primary volume, not logical
[AT&T Samsung Galaxy S 4 Android Development] Dinky:
I bought a 64GB sdcard which came with exFAT format. I have trouble to access the external sdcard while in recovery. I looked around and it appears that most of recoveries don't support exFAT format as it's closed source. But I keep all the flashable .zip and backups on the external sdcard which I don't have access to in recovery. When i saw the title of your thread

[17.06.2013]CWM 6.0.3.2 Advanced Edition / PhilZ Touch 5.06.7 + JB 4.2 + exFAT...

I got so excited and went ahead flashing it (even got trapped before it got loki'ed), but I still don't seem to be able to access my external sdcard in recovery. Am I missing something stupid?
[AT&T Samsung Galaxy S 4 Android Development] Dinky:
I plug it into my PC's card reader, and it says it's primary partition in Disk Management...
[AT&T Samsung Galaxy S 4 Android Development] fast96:
Just flashed the lokified version of Philz Touch recovery using CWM 6.0.3.2 just because I like the user interface. When I try to access Philz Touch settings it says "can't find aroma files" , I will search, but can someone point me there? And how to install/use them?

Thanks

Dan

Update; found it, had a little trouble, had to create the folder /aromafm in clockworkmod directory, paste the zip file in there, then install it again. All is well, I love it.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
exfat debug

WARNING: backup your external exfat storage before testing

Please, for people having exfat issues:

download http://d-h.st/k51

While in recovery

adb push mount.exfat-fuse /sbin
adb shell
chmod 0775 /sbin/mount.exfat-fuse
/sbin/mount.exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd

This should mount external storage exfat

Test backup and restore speed if ok

If it is stable, I will embed in next update
[AT&T Samsung Galaxy S 4 Android Development] Dinky:
Bummer... In prepare of my relocation, I need to "stabilize" my phone, so decided to reformat my sdcard from exFAT to FAT32. Else I'll definitely help (actually helping ourselves, isn't it...). Sorry...
[AT&T Samsung Galaxy S 4 Android Development] jeboo:
Heya Phil, good to see ya over here!

I went with the fuse approach, works great (though I havent tested anything beyond read/write).
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Most i need is backup speed for people having issues

Thank you a lot
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
So let me get my understanding straight.....I understand the issues as described, but ultimately this recovery I presume will now or shortly:

1. Auto-LOKI all applicable zips flashed via this recovery.

2. Allow full compatibility with reading and writing to SDXC / exFAT memory cards.

Am I understanding this correctly?

If this is the immediate goal, Im all in. I have had my S4 fo 3 weeks, and Im ready to crack open my new 64GB Samsung Pro extreme speed SDXC card.
[AT&T Samsung Galaxy S 4 Android Development] BigE:
Hi Phil, certainly great to see you on the AT&T S4 forums.. had great performance and battery tweaks with your work on the S2..

Sadly, i removed your current work. EXTFAT issues. Could not make the stupid SD card even to mount. First I had to figure out why your ADB SHELL commands did not work (Needed to be SU.. ) and finally the last command stated it failed to install.. so I can't even comment about speeds. From the lack of responses to you on this thread and the generic 9505 i assume many have hard time dealing with ADB shell. Since I am experimenting quite a bit with this phone, and backup/restore is critical for me, as unfortunately I have about 6gig free internal memory so keeping 2-3 backups are not an option, and moving images to and from the SD card finally made me just remove your great CWM .. back to OUDHS. not as half as nice as yours, but works.. I'll keep an eye for the next releases. Thanks.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
ad works perfectly on i9505 and exfat-fuse was tested there :rolleyes:
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
Phil,

So let me get my understanding straight.....I understand the issues as described, but ultimately this recovery I presume will now or shortly:

1. Auto-LOKI all applicable zips flashed via this recovery.

2. Allow full compatibility with reading and writing to SDXC / exFAT memory cards.

Am I understanding this correctly?
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
Anybody home??
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Asking for ETAs from Devs is discouraged.
[AT&T Samsung Galaxy S 4 Android Development] Ker~Man:
He technically didn't mention anything regarding ETA's. I took it as more-or-less a friendly nudge at a seemingly-dead thread! :D
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
If i'm not mistaken (and , i'm not) ETA means estimated TIME of arrival; I asked if I am understanding the potential goal or plan correctly. Not deep .
[AT&T Samsung Galaxy S 4 Android Development] kiru:
I have a i337m and installed the latest i9505 version of this recovery. I have no issues with backing up to my 64gig SanDisk card that is formatted in exfat and restoring from it. The only problem that I do have (I don't think it is related to this recovery) is that aroma cannot see the SD card.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
I will update as soon as things are fixed on jfltexx
[AT&T Samsung Galaxy S 4 Android Development] Jonnyredcorn:
So using this recovery since it is loki'd I can flash any ROM & kernel combo from the i9505 forums and it will work? I haven't had to deal with loki-doki or anything as I have always flashed(using TWRP 2.5.0.2) Ktoonez's kernel which is loki'd already. TWRP has been giving me issues with backups/restores so I figured I'd try out Philz recovery which is very popular over in the i9505 forums and I really like the interface.

Is Aroma now possible on the AT&T gs4? I had heard that Aroma wasn't possible?
[AT&T Samsung Galaxy S 4 Android Development] Dyaus:
This recovery won't auto-loki, so you'll have to loki-doki if you flash a kernel or ROM for the i9505.

I can't comment on aroma, I haven't tried.
[AT&T Samsung Galaxy S 4 Android Development] WoodburyMan:
Bye bye TWRP. Flashing this. CM10.1 just added exFAT so I need a recovery that has exFAT. This fits the bill perfect. Cheers!
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Does latest official cwm loki-doki?
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
I have a 32GB microSD card formatted with exFAT, but this recovery says it has a problem mounting it.

I can read and write to the card just fine while Android is booted. What could be the problem?
[AT&T Samsung Galaxy S 4 Android Development] Dyaus:
As far as I know the latest CWM doesn't auto-loki.

The OUDHS recovery auto-loki's however and is based on CWM. I checked out how it's doing it once upon a time. It's simply including the loki-flash and loki-patch as part of the recovery. It then pulls the aboot image and the boot image, patches it using loki-patch and then flashes the loki'd version back. This all takes place via a shell script run when the recovery exits. You can check out the source here: OUDHS.
[AT&T Samsung Galaxy S 4 Android Development] Gandalf:
I'm pretty sure CM auto-loki's now...

http://review.cyanogenmod.org/#/c/44503/

im pretty sure it is, but i've been using auto-loki recoveries. i'm about to flash this and find out though.

also, you're OP has a changelog for version 5.0.8, but jflteatt only has 5.0.6 available and grouper has 5.0.7, are you planning on updating all of your supported devices or just certain ones?
[AT&T Samsung Galaxy S 4 Android Development] Dyaus:
Nice! Thanks for pointing that out, I had missed it. Let us know how it goes if you flash the latest CWM.
[AT&T Samsung Galaxy S 4 Android Development] Gandalf:
I used the loki'd version from the OP and everything worked just fine

I figured I might as well just use that since itll definitely work woth flashing lokidoki, and its based on Phils most recent release
[AT&T Samsung Galaxy S 4 Android Development] carlospr21:
Please make a auto loki version of this recovery
[AT&T Samsung Galaxy S 4 Android Development] Obartuckc:
+1

Sent from my AT&T Samsung Galaxy S4 Badass
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Released v5.08.5 NON LOKI PATCHED

Change list 5.07.1 ---> 5.08.5

Please Note: Device specific threads will no longer be updated. I monitor them for support and feedback though

To check if you have a new version, subscribe to main thread:

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

Thank you for your understanding
[AT&T Samsung Galaxy S 4 Android Development] Dyaus:
Here's a loki'd version of 5.08.5.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Link added to post 1

Many thanks :thumbup:
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
I went to the OP of the main Phil's Recovery, and read the whole thing....I must say, that TWRP, and, CWM are very good, BUT after looking at this recovery, I was like "WOW". I mean its a piece of impressive work. Im very impressed. I am not even worried about the auto loki functionality, since its easy to just flash loki-doki when needed.

#EXCELLENT_RECOVERY
[AT&T Samsung Galaxy S 4 Android Development] ryang:
nandroid size?

I seem to have a strange issue.

Installed the latest version, and went to do a nandroid. It said the free space is 20891Mb, and the Needed Space is 2381552Mb, with another line of "Unknown partitions size (1): -/sd-ext. above it tells me "low free space" Continue anyway?. Why is my nandroid going to be 290GB? I must have something wrong here...
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Size estimation seems wired on S4. i9505 seems a very special device. Not having it makes things a pain to fix.

Please someone post a log so that i can see what's going on and maybe fix it
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Well, as I said, log should contain the error!

- start a backup

- when you see the erroneous size estimation, cancel it

- create log and attach it again here

Thanks
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
Is ExFat working now with 5.08.5? On the last AT&T build, I couldn't read from my 32gb sdcard formatted with ExFat. I got an error that it couldn't mount the partition.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
yes, it should

However, on some cards, exfat is slow, mainly the 64Gb ones

Reasons were explained many times in i9505 thread
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
Thanks, I'll give it a try.
[AT&T Samsung Galaxy S 4 Android Development] Obartuckc:
Does this contain the auto-loki upon flashing something, or that the recovery itself is lokied? Either way, thanks!

Sent from my AT&T Samsung Galaxy S4 Badass
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
I renounced to introduce auto-loki like in OUDHS

I have no idea how Samsung can implement their next anti-loki code. Having a soft that still patches your device boot/recovery images under such future bootloaders will have unpredictable results. I am not sure if loki binary checks for bootloaders compatibility before patching

Maybe that's the reason TWRP and CWM did not add such a script!

Since I do not have the device, I decided to take 0 risks with yours ;)
[AT&T Samsung Galaxy S 4 Android Development] Obartuckc:
Thanks for the prompt and specific answer, sir!

Sent from my AT&T Samsung Galaxy S4 Badass
[AT&T Samsung Galaxy S 4 Android Development] Febby:
This recovery is simply amazing by the way! I love how it let's you change so many settings. I disabled the touch function and now I'm very much so happy! :)
[AT&T Samsung Galaxy S 4 Android Development] ryang:
I figured it out. my sd card was mounted as read only for some reason. Hence the actual log wasn't getting overwritten. I had to delete the clockworkmod folder, and the usage required is now at 2639Mb. Thanks for the help!
[AT&T Samsung Galaxy S 4 Android Development] Dnice25:
Thanks you very much sir!!!!!:thumbup:
[AT&T Samsung Galaxy S 4 Android Development] STVERDI:
I keep getting the unauthorized error after flashing this.. Even when loki flashing after.. Is there something I'm missing? And is this recovery slow? The regular cwm touch seems laggy.
[AT&T Samsung Galaxy S 4 Android Development] Dyaus:
Are you flashing the loki patched version of the recovery? It sounds like you're flashing the non-loki'd zip. Loki-doki won't work for recoveries, only ROMs.

Use the zip from here: http://xdaforums.com/showthread.php?p=43577518
[AT&T Samsung Galaxy S 4 Android Development] STVERDI:
Well, don't I feel dumb. Lol. I thought that meant that it would auto loki patch roms when downloaded... Thank you :o
[AT&T Samsung Galaxy S 4 Android Development] MrMarkEdward:
Tried this one and wasnt auto loki the kernel
[AT&T Samsung Galaxy S 4 Android Development] Febby:
NVM - Deleted -
[AT&T Samsung Galaxy S 4 Android Development] Planktron:
Hey all, I swear I'm not a noob and I only ask questions after searching and I'm at my wits end. I looked in this thread and the main thread. :D

I honestly don't remember any other recovery backing up /data/media, but it appears this one does. I looked through all the recovery's settings and couldn't find anything.

If I make a backup of /data and a week later restored it, wouldn't I lose all the pics etc that have been added since then?

I really have no interest in backing up /media because it makes for a lengthy process and huge file.

Again I apologize if I have overlooked something blatantly obvious :p

Thanks :good:
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
as far as I know, no recovery backs up /data/media. It is a non sense for most as it would take ages and so much space

That's done on PC
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
Flashed this yesterday and thank god for Odin and nandroids.. When I tried rebooting into recovery I got the famous att unauthorized software detected sand couldn't get into recovery I had to Odin.. Abt ideas what went wrong??
[AT&T Samsung Galaxy S 4 Android Development] Dyaus:
Never said it was. Please understand the difference between a recovery which is loki'd and one which auto lokis. Every recovery must be loki'd in order to be flashed. Auto loki is a feature of a recovery which insures a flashed ROM is loki'd.

---------- Post added at 07:55 PM ---------- Previous post was at 07:53 PM ----------

Sounds like you're flashing the wrong zip. I suggest reading the previous page.
[AT&T Samsung Galaxy S 4 Android Development] Planktron:
Thanks. I can see it's backing up a lot of jpg files in the name format the camera uses, so i thought it was backing up media. I used nandroid manager to explore the backup and couldn't find them. Perhaps it's backing up thumbnails and not full photos. I'm not using compression and full nandroids are around 5 gigs which appears to be normal.
[AT&T Samsung Galaxy S 4 Android Development] Namolas:
For everybody saying they had to Odin back to stock because of the unauthorized by AT&T message. You can just reboot into download mode (volume down+home+power), right from that message, and then press volume down to cancel download mode and reboot the phone. No need to Odin. Once rebooted you still need to fix your Recovery.
[AT&T Samsung Galaxy S 4 Android Development] MrMarkEdward:
Got you ty for clarifying for me
[AT&T Samsung Galaxy S 4 Android Development] sofakng:
I posted this in the original thread but hopefully it's ok to ask here as well.

Does anybody have a compiled version of 5.09.2 of PhilZ Touch for the AT&T S4? (SGH-I337)

Does the I9505 version work? (if I loki patch it first of course)
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
i9505 international is getting so many updates because many users are showing their interest and helping to debug it

i9505 is giving me some serious trouble to iron out all bugs

Once it is fixed for i9505 international, you'll get an update. No need to hummer until I am done
[AT&T Samsung Galaxy S 4 Android Development] sofakng:
OK - Thanks.

I was just wondering if the i9505 version worked on the SGH-I337 (AT&T variant) because then I could also help test and report bugs, etc.
[AT&T Samsung Galaxy S 4 Android Development] Namolas:
Recovery working awesome on my AT&T s4. Working perfectly with my Sandisc 64gb ExFat card too. Thanks Phil!
[AT&T Samsung Galaxy S 4 Android Development] sholsten:
Can you Loki the newest 5.09
[AT&T Samsung Galaxy S 4 Android Development] Planktron:
+1. It took me a while to learn it, but since then I've been thoroughly enjoying it. Great job, Phil :good:
[AT&T Samsung Galaxy S 4 Android Development] Dyaus:
No 5.09 version for ATT.
[AT&T Samsung Galaxy S 4 Android Development] sholsten:
Ok. Thank you!

Can we use the one for i9505?
[AT&T Samsung Galaxy S 4 Android Development] Dyaus:
Not really. The device type is different and if a ROM checks the device type before installing (most do) it'll fail to install. So kind of pointless if you want to install ROMs. Of course you could download the ROM, modify the install script to remove the check, re-package the zip, and then install. But that's a hassle and it'll cause way too many issues for people that won't read. So best to just wait on the ATT version.
[AT&T Samsung Galaxy S 4 Android Development] sholsten:
Yes, I'll gladly wait. I'm not into modding files like that at all.
[AT&T Samsung Galaxy S 4 Android Development] gk527:
What file do I need to download for my AT&T I337? I downloaded http://d-h.st/izQ file named philz_touch_5.08.5-jflteatt.zip, but I got the yellow triangle and AT&T error. Luckily I was able to get in to Download mode and cancel from there.
[AT&T Samsung Galaxy S 4 Android Development] Namolas:
You either have to flash loki doki afterwards or flash the already loki'd version courtesy of [MENTION=370698]Dyaus[/MENTION]. Link is in the OP.

http://xdaforums.com/showthread.php?p=43577518
[AT&T Samsung Galaxy S 4 Android Development] turilo:
Will this work on the I337m Canadian s4?
[AT&T Samsung Galaxy S 4 Android Development] cablegooru:
this is the process i have been doing... you say you can fix recovery after boot? can you point me in that direction? from what ive read without adb have to odin, which i can but just havent. Would like to know of other ways for future refrence. thanks
[AT&T Samsung Galaxy S 4 Android Development] Namolas:
Use Goo manager to reflash TWRP. Install Goo Manager from the market, hit menu and then install open recovery script. Otherwise you could try the lokifyed 3 way tool to install recovery of your choice using your PC.
[AT&T Samsung Galaxy S 4 Android Development] supersixevo:
Any word on auto loki function on this recovery?

Please advise..

Thanks
[AT&T Samsung Galaxy S 4 Android Development] Namolas:
The recovery itself is not lokied nor does it auto loki what it flashes. Does that answer your question?
[AT&T Samsung Galaxy S 4 Android Development] supersixevo:
Yes. Thanks
[AT&T Samsung Galaxy S 4 Android Development] Simonzi:
I was on TWRP 2.5, and was getting fed up with it, so I decided to swap to this recovery. I downloaded the loki'd zip, and flashed it in TWRP. Said it went fine, rebooted recovery, and now it won't boot. Can't even get into recovery. I'm stuck at the blue "recovery booting" text.

Can still get into download mode, so I grabbed the philz_touch_5.08.5-jflteatt.tar.md5 file, and tried flashing that with ODIN, and it just says it fails.

Any suggestions? I'm in the process of downloading the 1.6gb stock firmware file, but wouldn't mind trying anything else while waiting for it to download....
[AT&T Samsung Galaxy S 4 Android Development] estanenmi:
Download again for ur phone use tar and flash on pda option using odin for pc again.. Maybe corrupted download.. Or try again twrp

Enviado desde mi GT-I9505G usando Tapatalk 2
[AT&T Samsung Galaxy S 4 Android Development] freebee269:
go into download mode and select restart device. this will get you out of the recovery loop. then go to goo manager and install twrp again. then download this loki'd version of philz cwm http://xdaforums.com/showthread.php?p=43577518 then go to recovery and install this cwm.
[AT&T Samsung Galaxy S 4 Android Development] JiNYx007:
Hey Phil awesome work. I noticed other devices get steady updates. Any way we can get some love on the 337 side?

Sent from my tricked out S Quatro
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Things are slow because S4 is taking me a lot of time and my only phone, i9100, is dying on me

If there are enough donations to buy a new phone, hopefully, dev can speed up again
[AT&T Samsung Galaxy S 4 Android Development] turilo:
I'd wait for the note 3 if I was you Phil3759 :D
[AT&T Samsung Galaxy S 4 Android Development] Delakit:
There's no 5.11 for our device?
[AT&T Samsung Galaxy S 4 Android Development] freebee269:
i have v5.11 loki'd. it is from the jfltexxx build. i was going to share it with the community. everything was working fine til i went and tried to install a rom. i would get status 7 error for android 4.3 and android 4.2.2 aosp roms. a work around to this was to go into the updater script and delete the assert line in the script. then the rom installed fine and booted up without any issues. i just didnt want to share the loki'd v5.11 that i have with this going on. i dont know if the build has to be changed at all to look specifically for jflteatt and that's why the jfltexxx is throwing the status 7 error or not. so i deleted my post. aside from that, jfltexxx works fine doing everything else on my att gs4.

edit: i see there's a new version out. will try that and see if it clears up the status 7 errors.

edit2: v5.11.1 didnt fix the status 7 errors. status 7 error is a get prop error when it looks for a certain device to be a certain name.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
You shouldn't use a version not built for your phone without being sure...

To fix the error, you have to unpack and repack recovery.img with correct phone id
[AT&T Samsung Galaxy S 4 Android Development] milicigoran:
I want to switch to this from TWRP. Can I just flash the lokid version from the OP or do I need to do something before that?
[AT&T Samsung Galaxy S 4 Android Development] freebee269:
you can flash the loki version in OP in twrp. but keep in mind, if you plan to go to android 4.3 aosp roms like cm10.2 or supernexus, the loki version in OP will not work. the rom will not recognize your radio. in version 5.11.0 this was fixed but that's jfltexxx not jflteatt. when he gets around to doing a new jflteatt build for verison 5.11.0 or later, i or someone else will loki it for us.
[AT&T Samsung Galaxy S 4 Android Development] milicigoran:
Not planning on going to 4.3 I actually like TW. It's all the cheesy features TW has that made me get the S4. I had AOSP roms on my S3 and they were boring, gave up a lot of features for a little more speed. Thanks for the info though.
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
I am looking forward to this with 4.3 support. It's the only solid recovery I'm aware of that supports exFAT. Having a 64GB card is almost pointless if we're forced to use FAT32, with it's file size limitations. Thank you very much for working on this.
[AT&T Samsung Galaxy S 4 Android Development] Febby:
Me too. Patiently waiting for the latest recovery that the other S4 model has. :)