yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] rav4kar:
Yes very much :D
[AT&T Samsung Galaxy S 4 Android Development] freebee269:
removed at philz request.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Please remove these links

It is beta and not suitable for daily use

Stick to latest official versions please
[AT&T Samsung Galaxy S 4 Android Development] freebee269:
i dont know how to differentiate between whats the official version and what isnt so i'll just not do them so this doesnt happen again.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
I appreciate your efforts, really

Was my fault too. I now moved beta to a new subfolder on top of old version you see here

http://d-h.st/users/philz_touch/?fld_id=16685#files

5.15.8 is a good stable build you can repack for S4 US variants

Between 5.15.0 and 5.15.8 you have mainly a small improvement in touch and scroll expierience
[AT&T Samsung Galaxy S 4 Android Development] freebee269:
ah thank you very much. that's much easier to tell the difference. i will do the ones that are in the main folder and not the beta. have already done v5.15.8. it's a page or 2 back. thanks again.
[AT&T Samsung Galaxy S 4 Android Development] PapaMag:
Thanks for this recovery been struggling to get it flashed and on my device, but once I pulled my head out and followed instructions worked like a charm. Been so disappointed with twrp as of late, and couldn't get regular cwm to go touch even with the paid version, now things work well
[AT&T Samsung Galaxy S 4 Android Development] freebee269:
v5.17.1 for at&t and canada.

http://d-h.st/ZBY = AT&T

http://d-h.st/tHA = Canadian
[AT&T Samsung Galaxy S 4 Android Development] seanpr123:
Never mind, problem fixed itself.
[AT&T Samsung Galaxy S 4 Android Development] eak1080:
Philz Recovery 5.17.6

do not use. it is broken
[AT&T Samsung Galaxy S 4 Android Development] geomax45:
Sorry, but what's broken?
[AT&T Samsung Galaxy S 4 Android Development] eak1080:
http://xdaforums.com/showpost.php?p=46314153&postcount=2106

http://xdaforums.com/showpost.php?p=46313716&postcount=2104
[AT&T Samsung Galaxy S 4 Android Development] freebee269:
that was a beta version. if you read a page or 2 back phil doesnt want the beta version put out as official versions therefore i didnt loki it. you can use v5.17.1 on this page, that is an official version. it works fine.
[AT&T Samsung Galaxy S 4 Android Development] f100cleveland:
He actually called it his final stable build. The faster backup/restore would've been nice, if it worked right.
[AT&T Samsung Galaxy S 4 Android Development] 78Staff:
Tried this, not sure if this is the latest stable loki patched for ATT, but it was the one linked in the OP so I went with this one. Similar to TWRP 2.5.0.2 it reports crazy large data partition size on my phnoe, ie 19Gb, so not able to do backups of course. Since I see this in twrp 2.5.0.2 also (and have seen others reporting this, with no resolution found), I don't think it's a philz recovery issue, however TWRP 2.6.3.1 reports the correct sizes. Just hate TWRP's inability to reboot normally 90% of the time lately :(.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Most people fixed this by a factory reset

In my recovery, you can force backup even on the warning
[AT&T Samsung Galaxy S 4 Android Development] freebee269:
philz touch v5.17.7 for at&t and canada.

http://d-h.st/Iww = AT&T

http://d-h.st/Ith = CANADA
[AT&T Samsung Galaxy S 4 Android Development] 78Staff:
OK, I will try it again, also moving to 5.17 linked above :good:
[AT&T Samsung Galaxy S 4 Android Development] eak1080:
5.18.2

v5.18.2

https://db.tt/36y7Z93S -jflteatt version
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
v5.18.2 official

-- devhost --

- it is specifically recompiled for ATT/VZW to allow auto loki on flash

You can enable/disable auto loki flashing in Advanced menu

Give your feedback
[AT&T Samsung Galaxy S 4 Android Development] blackwing182:
so this recovery is loki patched and have the option to auto loki all?
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
No, it is not locki patched, but has option to loki doki on flash
[AT&T Samsung Galaxy S 4 Android Development] blackwing182:
:( ill need to wait till is gets patched :( thanx btw no i dont have to worries on flashing the loki-doki thing!!!! thank you!
[AT&T Samsung Galaxy S 4 Android Development] Gandalf:
Its already been loki'd by eak one post above Philz
[AT&T Samsung Galaxy S 4 Android Development] blackwing182:
sweet thanx! bro!
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
No,

He repacked and patched that version from i9505 international

The official I compiled and posted adds a new option found only on vzw and att: you can choose in Advanced menu to auto loki files you flash
[AT&T Samsung Galaxy S 4 Android Development] eak1080:
I had loki'd the 5.18.2 version found in Phil's i9505 directory.

I have removed that one and re uploaded the loki'd version which phil specially compiled for us and was located in the JFlteatt directory on his hosting site.

here that is. Phil feel free to update OP

https://db.tt/8TRPOZQX
[AT&T Samsung Galaxy S 4 Android Development] Gandalf:
Ah OK good catch, I saw the time differences but didn't catch that. Thanks!
[AT&T Samsung Galaxy S 4 Android Development] eak1080:
they both worked fine, jus this later one has auto loki checking enabled when phil compiled it. #showing us some love

oh btw i had to clear cache/dalvik to get my device to boot up after flashing 5.18.2
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
Updated OP

Many thanks for the follow up :good:

I could release a lokied one directly, but many like the original non lokied. Releasing 2 distinct versions is too much work to maintain on the long run
[AT&T Samsung Galaxy S 4 Android Development] eak1080:
if you keep doing the hard part ill keep doing the easy part to help you out :)
[AT&T Samsung Galaxy S 4 Android Development] REDFOCZ:
Just to clarify for myself, the recovery is not just Loki patched, but now supports auto Loki? So with updating to this most recent version of the recovery I no longer have to flash Loki doki? Am I correct in my assumption.

Some times I need it spelled out for me :P
[AT&T Samsung Galaxy S 4 Android Development] MikeC4510:
Yes lol.

Sent from my I337~SGS 4 using Xparent Skyblue Tapatalk 2
[AT&T Samsung Galaxy S 4 Android Development] eak1080:
[MENTION=4666971]Phil3759[/MENTION]

Since you custom compiled 5.18.2 for the S4 jflteatt to support auto loki checking, will you be sending us updated builds in the att s4 folder for newer recovery versions. The only reason i ask is because i don't want to go loki patch the recoveries in the i9505 folder and post them here because they dont have the auto loki checking feature enabled.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
I will
[AT&T Samsung Galaxy S 4 Android Development] eak1080:
You might just be the F*$&ing man....
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
I won't be able to do it, important life things

If you look at change log from 5.18.2 to 5.18.5, there is nothing important, really

5.18.2 is just perfect for now. Next update will sort some bugs like virtual buttons not canceling nandroid job unless you keep finger on button
[AT&T Samsung Galaxy S 4 Android Development] RobPiazzajr89:
How do i install on AT&T Galaxy S4

How the heck do I install this on the AT&T Galaxy S4, why are there no instructions that I can find?
[AT&T Samsung Galaxy S 4 Android Development] blackwing182:
also in jflteatt i noticed a little lag when selecting tabs. just my 2 cents here bro!
[AT&T Samsung Galaxy S 4 Android Development] eak1080:
Oh i did not mean every release, that would be a crazy thing to assume.

I just meant the major releases with device specific fixes/features.

:laugh::good:
[AT&T Samsung Galaxy S 4 Android Development] HiDEFF:
I recently installed Philz recovery over standard CWM and I'm coming across an issue. I'm trying to clean wipe my device by formatting the system and data folder but I'm still getting old folders from previously installed applications and old pictures on my internal SD memory; am I doing something wrong?
[AT&T Samsung Galaxy S 4 Android Development] DreenHotdog:
I'm using Philz touch recovery as well. I've done this dual boot with it before and you just need to press the 'clean to install new rom' button and it will automatically wipe the /data, /system, /cache, dalvik cache, and I think 2 other partitions. I will usually have my internal memory reset after doing that. It also helps to have the latest Philz touch installed if you have not done so already.
[AT&T Samsung Galaxy S 4 Android Development] HiDEFF:
[AT&T Galaxy S4][CWM Advanced Edition] PhilZ Touch

I reverted to the version that's posted in GoldenEye's OP and now everything is working perfectly; it formatted and wiped clean my internal sdcard.

I do find it weird that the latest version wasn't allowing me to get a clean install.
[AT&T Samsung Galaxy S 4 Android Development] Locoman_:
If you have the loki patched version, does that mean that it runs the loki patch on the recovery installation, or when flashing roms or both?

Thanks.
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
You can wipe everything

It is just a small effort to read op, main thread guide and faq
[AT&T Samsung Galaxy S 4 Android Development] blackwing182:
i got this error formating Preload

i hope this log helps
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
I am aware about it. Look in i9505 thread. Will be fixed when I am back. Just ignore it meanwhile
[AT&T Samsung Galaxy S 4 Android Development] blackwing182:
oooo sorry i did not know that you know about it :D sorry!!!

thank you!
[AT&T Samsung Galaxy S 4 Android Development] slojko:
i keep getting a error message during setup connection when i try to odin this recovery
[AT&T Samsung Galaxy S 4 Android Development] eak1080:
[MENTION=4666971]Phil3759[/MENTION]

is there any need for jflteatt users to update to 5.18.7.

Like should i loki the i9505 recovery or wait until you provide a special compiled recovery update for us?

just curious.

Thanks man
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
for now they are only minor updates in my opinion

Please check change log in main thread
[AT&T Samsung Galaxy S 4 Android Development] hemmie:
Philz, I'm in the process of migrating to Philz from TWRP. Should I loki the i9505 latest version or get the one for jflteatt. If I loki the i9505 latest do I get auto loki features after flashing.

I was just curios installing this using Odin, since Odin takes ATT signed packages so can you confirm I can odin the recovery without getting blocked by verifier.

Or I should get it flashed using insideTWRP

Thanks
[AT&T Samsung Galaxy S 4 Android Development] jgruberman:
I have this recovery flashed and I went to install a new ROM from my external SD card, bu got the following error when I tried to load a zip from external SD:

/storage/sdcard1: Checking

/storage/sdcard1: Idle-Unmounted

E:Can't mount /storage/sdcard1

Then I tried to mount it manually from the mount screen and got this error:

/storage/sdcard1: Checking

/storage/sdcard1: Idle-Unmounted

Error mounting /storage/sdcard1!

If I try and mount USB storage, I can see the files on the external SD card just fine on my computer. I'm dead in the water until I can either A) Get my ROM onto my internal SD card since I can access that still or B) Get my recovery to be able to see my External SD card.

Any thoughts? Help! :eek:
[AT&T Samsung Galaxy S 4 Android Development] stefan75:
Are all the att recoveries lokid or do I need to have the Loki patch on my SD card?

Thank you in advanced
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
Keep it on your SD card and use it whenever you flash something you're not sure about. Trust me.

Most times you won't need it.

Some times you will, such as if you flash some kernels.
[AT&T Samsung Galaxy S 4 Android Development] virus_spreade121:
hey guys, I bought a GS4 last week, its from At&t. I have got the phone rooted now. Am I suppose to directly place the phil touch file directly in the sd card folder and go into recovery and flash it? Or do I need to go through the loki version thats here

Waiting for someones help. Please
[AT&T Samsung Galaxy S 4 Android Development] Jonnyredcorn:
Since you just got your galaxy S4 I would double check the baseband and build and make sure it is not MF3 . You can only flash ROMs using safe strap recovery . You cannot use this recovery it will break your device

Sent from my AT&T Galaxy S4 Running Task650's AOKP powered by ktoonez's Kernel!
[AT&T Samsung Galaxy S 4 Android Development] Torlugic:
I'm on 5.18.2 and looking to update to 5.18.9

I have a jfltecan model i337m and I don't see another subsection for my model so I'm asking here where can I get the latest?
[AT&T Samsung Galaxy S 4 Android Development] shawn0223:
Hi,

I used to have this recovery and it worked great, but for some reason it was having issues with the rom i wanted to install so i flipped to TWRP. I dont like TWRP and wanna have this recovery again, but whenever i flash the latest release, i get the yellow triangle saying system software not authorized by AT&T. up in the top corner, it says "secure fail: kernel".

I got stuck like this and ended up having to odin back to stock. got everything on stock again. rooted again with casual, which installed TWRP. then i tried flashing this again but i got stuck on the triangle again.

Any idea? I even tried flashing the TAR through odin but it failed as well.

The stock rom im odining back to is AMD so idk why this isnt working.

any ideas?
[AT&T Samsung Galaxy S 4 Android Development] Galaen:
http://xdaforums.com/showthread.php?p=46499887

Try using this version. It Auto-Loki's the rom you are flashing if necessary. If you are still on twrp, use that to flash this recovery. Should take care of it.

Sent from my AT&T Galaxy S4
[AT&T Samsung Galaxy S 4 Android Development] hemmie:
Flashable autoloki zip to Philz Recovery

Only thing missing from grabbing the I9505 latest Philz Touch versions getting installed on ATT S4 variant is that the auto loki patch.

I should be able to patch the recovery.img to be loki'd but wondering if can we get a auto_loki flashable zip to philz touch, so all the people having ATT S4 variant can reap full benefits as soon a new release comes up for international I9505 without waiting a device port from Philz.

Thanks, hope this gets some attention.
[AT&T Samsung Galaxy S 4 Android Development] Febby:
I don't know if Phil loki'd the latest official 6.00.8 for the JFLTEATT/I337 but I made a loki'd version for all to take advantage of without waiting.

to download click the zip in the attachtments of this post.

[MENTION=4666971]Phil3759[/MENTION] Feel free to link this post to your OP for users waiting to download loki'd recovery of your latest release. :)
[AT&T Samsung Galaxy S 4 Android Development] Completely_Clueless:
Boy did I wish you were here two hours ago! I downloaded the newest 6.00.8 recovery from Phil's website and install it from TWRP, then I thought I could install loki-doki after it and all would be well. Nope! I got that dread yellow triangle and "not authorized by AT&T crap," and had to Odin back to stock re-do everything!

But everything is okay now, and I'm not blaming ya :p. Totally my fault; I should've just stuck with his older 5.0 recovery in the OP that was loki'd. Oh well, live and learn: now I know not to load up a non-loki'd recovery. Although, I'm still puzzled as to why loki-doki didn't patch the recovery. Does that tool only work for ROMs?

And just so I don't get burned again, and so I have it crystal clear: the recovery you posted is loki'd and will work on SGH-i337 without causing that "unauthorized by AT&T" locked bootloader message? If yes, then how does one go about making a loki'd version of Philz recovery? Would it be possible for an average Joe like me to loki-fy his recovery whenever a new version comes out?

Lastly, I can install this via TWRP, right? Not via Odin like Phil's main thread states? The TeamWin website also says that you can just flash a new recovery on top of TWRP and it'll replace it. Sorry for so many questions; I'm trying to be very careful now and do this properly, as that yellow triangle the first time around nearly made me crap myself :(.
[AT&T Samsung Galaxy S 4 Android Development] Febby:
Next time you go flash a non Loki recovery and get in authorized message just boot into download mode and reboot into phone via vol buttons. It will bypass the unauthorized message.

Yes this recovery (the one I posted) is lokied so you should be good to go! You can flash it via twrp recovery or any recovery. Using Loki tool isn't for the average unless u know how to use it with Linux. The Loki doki is only for kernels ;)

"All men are created equal, some work harder in pre-season."

- Emmitt Smith
[AT&T Samsung Galaxy S 4 Android Development] Completely_Clueless:
It Worked!

Yes! It worked perfectly! :good::) Many thanks to you, and many thanks to Phil for his recovery!
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
[MENTION=2587828]Febby[/MENTION]

Hey dude. I see you said you're release is lokied but does it have the autolokie option in it to lokie other stuff like kernels automatically?

Sent from my Nexus 7
[AT&T Samsung Galaxy S 4 Android Development] Febby:
Yes. The Phil version for the i337 has s built in auto Loki feature. :)

"All men are created equal, some work harder in pre-season."

- Emmitt Smith
[AT&T Samsung Galaxy S 4 Android Development] Shawn7656:
Well crap. I downloaded the version that was apparently NOT lokied.

I used the previously mentioned method to boot back into Android, and normally I know I could install a recovery through Goo.IM or ROM Manager then flash this through that, but I'm on KangaKat which has the build.prop showing that I'm on the i9505 instead of the SGH-i337. This means that these apps would install a non-lokied recovery and not solve anything.

Is there a way I can install this recovery from within Android? I'm searching around online but only finding ways to do it through the computer with ADB or from recovery. There's gotta be a way with Terminal Emulator, no?

...

I tried searching some more and I'm finding stuff to do with "flash_image" but these articles are two years old and not for this device. On top of that I looked for such a file in our subforums and didn't see it.

EDIT: My lack of patience is showing. I couldn't stop trying to figure out a workaround so I found an app in the play store called "Recovery Tools" by DSLNexus and then downloaded a recovery .img for the device (I used TWRP because I found it first). Installed it using this app then rebooted to recovery and flashed the lokied version of Philz! Everything is working. Hopefully if someone makes the same mistake as me they can use this method to get themselves out of a sticky situation!
[AT&T Samsung Galaxy S 4 Android Development] TRusselo:
you could have also edited your build.prop file to change your model number so apps could properly find loki recoveries and files for you.
[AT&T Samsung Galaxy S 4 Android Development] Torlugic:
Does Philz touch work for 4.4.2 anyone know? I'm running 6.00.8 on my i337m

Slim Roms powered

1337m

4.3.1. build 2
[AT&T Samsung Galaxy S 4 Android Development] theshow4life:
I have flashed about 4 or 5 different 4.4.2 ROMS and not a problem at all Philz is the best in my opinion. I have a I337 ATT BTW.:good:
[AT&T Samsung Galaxy S 4 Android Development] gb.sn:
So its the same from the one you posted?
[AT&T Samsung Galaxy S 4 Android Development] f100cleveland:
Has anybody compiled a new version of this? I know Phil has been making a ton of changes.

Thanks and Happy Holidays!
[AT&T Samsung Galaxy S 4 Android Development] Febby:
Here is the latest Phil recovery Loki'ed so us ATT/I337 users can flash it! enjoy and thanks [MENTION=4666971]Phil3759[/MENTION] for supporting this device. Feel free to add this post to OP so users can flash the loki'ed version.

To download it just download via the attachment. Optionally you may use the mediafire link below. :)

1: Attachment link

http://xdaforums.com/attachment.php?attachmentid=2480870&d=1388302561

2: Mediafire link

http://www.mediafire.com/download/wre816dler18r87/Lokied_philz_touch_6.07.9-jflteatt.zip
[AT&T Samsung Galaxy S 4 Android Development] Phil3759:
The zip will auto lokify it, no need ay more to this normally, except for odin version is not lokified
[AT&T Samsung Galaxy S 4 Android Development] Febby:
Awesome! Just tried it and it works. I apologize. I didn't know since he hardly get any noise in this section. :)
[AT&T Samsung Galaxy S 4 Android Development] NHComp:
I'm looking forward to trying Philz. I'm still fairly new to Android flashing so I want to verify that I'm doing the correct steps before jumping in.

I'm running a CyanogenMod 10.2 nightly build on the ATT S4.

1. Is this the best build to use? Lokied_philz_touch_6.07.9-jflteatt.zip

2. Can I just wipe and flash over CMG or do I need to do other steps?

Thanks!
[AT&T Samsung Galaxy S 4 Android Development] eak1080:
https://www.mediafire.com/folder/f9x639la72lf2/PhilZ_Touch_6

Download jflteatt and flash in any recovery.

With all builds going forward there is no need to Loki the recovery imgs anymore as the recovery god aka philz builds that in for us now in the zips.
[AT&T Samsung Galaxy S 4 Android Development] Febby:
Does anyone know have an issue with touch wiz roms reporting no sim/signal after flashing a tw 4.3 rom using this recovery? If I use the old twrp or older cwm recoveries all works smooth.
[AT&T Samsung Galaxy S 4 Android Development] hednik:
Awesome. I wasn't aware of that. I know at the end of each action it checks but I wasn't sure if it was lokied
[AT&T Samsung Galaxy S 4 Android Development] Torlugic:
So there's a new 6.07.9 build, site just not updated or is 6.00.8 the latest for jfltecan?

Slim Roms powered

1337m

4.3.1. build 2
[AT&T Samsung Galaxy S 4 Android Development] NHComp:
Thanks for the info. I wiped the data and installed the zip. it seemed to go fine - I got the "Philz successfully installed" message. Then I rebooted and the screen has been stuck on the Samsung Custom with the unlocked padlock for 20 minutes.

I read online to take the battery out and retry. I see Philz screens in recovery instead of CM. I wiped the data and cache. It said the phone was not rooted (I'm sure it was) so I told it to reroot. Same issue, the reboot is stuck at the Samsung screen.

Resolved: Ran Odin to get it back to stock. http://xdaforums.com/showthread.php?t=2261573

Now it's unrooted and I get to start all over again. Woo hoo! At least it was fixable.
[AT&T Samsung Galaxy S 4 Android Development] RK:
I flashed shostock as a secondary ROM using Chen's dual boot. It works fine. I didn't have to wipe anything for it tho..
[AT&T Samsung Galaxy S 4 Android Development] s1l3nt:
anyone else getting errors with auto loki? i seem to get an error when it tries to loki after i flash a rom. I'll try getting a log
[AT&T Samsung Galaxy S 4 Android Development] ac3theone:
I got that error as well, i had to flash loki doki manually to fix. It definitely has to be a problem with the version a couple posts up
[AT&T Samsung Galaxy S 4 Android Development] vivek90:
philz did mentioned in an earlier post... Recovery Flash version "zip" version has auto loki in it Odin version doesnt have auto loki.

Btw i did flash the same one im not facing issues like that. Reading earlier posts would address some problems.
[AT&T Samsung Galaxy S 4 Android Development] mixlex:
Me too...Every backup I make is useless now.
[AT&T Samsung Galaxy S 4 Android Development] mixlex:
I notice this too.

I have used all versions. 5.18.2 is the last one that does not give that error. I thought my backups were bad but using lokied cwm recovery no problems. I hope the issue will be fixed in future releases.
[AT&T Samsung Galaxy S 4 Android Development] giler123:
mf3

im using i337 at&t mf3 ... will it work om my divice ?
[AT&T Samsung Galaxy S 4 Android Development] beast3300:
Not if you have the mf3 over the air update or got your s4 with mf3 from AT&T. You need to check out safe strap.