yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] flinttownbrown:
Yep I booted into it just fine.

And if one flashed a broken recovery, they could always just boot into the regular ROM and flash the Loki one manually.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
good to know, i was downloading the whole tar to make a recovery opnly tar for everyone :)

see above post :)
[AT&T Samsung Galaxy S 4 Android Development] chrisc93:
Except I can't even boot into my ROM now.
[AT&T Samsung Galaxy S 4 Android Development] brosenz:
This is TRUE ONLY if you have a regular ROM installed, I did not :mad:

---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------

Is it possible to have an ODIN version of the recovery?, that will be much easier
[AT&T Samsung Galaxy S 4 Android Development] flinttownbrown:
Not sure why that is. From my understanding the bootloader only checks recovery when booting into recovery, and only checks boot.IMG when booting into the kernel.

Thus, there doesn't seem to be a reason why a broken recovery would prevent ROM booting because they are Loki'ed separately.

---------- Post added at 02:02 PM ---------- Previous post was at 02:01 PM ----------

I have task AOKP installed and it worked fine.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
no since odin cant flash loki'd files

www.shabbypenguin.com/OUDstuff/Samsung/ATT/jflteatt/Recovery/Stock-recovery.tar
[AT&T Samsung Galaxy S 4 Android Development] brosenz:
I cannot boot either
[AT&T Samsung Galaxy S 4 Android Development] chrisc93:
That's strange. Cause I have task AOKP too. Did you flash it over your 1.0.3.4 recovery?
[AT&T Samsung Galaxy S 4 Android Development] flinttownbrown:
Yep. I originally flashed the zip version from .4 version. Then I rebooted it and went directly back into recovery. Got the error message, and rebooted into the ROM just fine. Fixed using the manual Loki method and bingo.
[AT&T Samsung Galaxy S 4 Android Development] chrisc93:
Hmm. Well I booted back into the rom after odin flashing stock recovery. Will do the manual loki now.

EDIT: It appears that the dl link is down. I guess shabby is fixing it?
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
i didnt wnat people flashing more of it while it was causing issues :P

since the lok file is confirmed working then the zip should be working fine as well and ill restore the links
[AT&T Samsung Galaxy S 4 Android Development] chrisc93:
Haha, yeah that makes since. Thanks for the quick fix! :good:
[AT&T Samsung Galaxy S 4 Android Development] SysAdmNj:
Not being picky but can you fix the nandroid backup dates, or is there something I can do? :)
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Please correct me if I am wrong, but if you have the AT&T S4, there isn't a reason to update from 1034 to 1035? Unless you just want the latest and greatest. The benefits with 1035 are for those with the unlocked bootloaders? So if you have an I337 and 1034 is working for you it's OK to just stay with it for the time being.
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
Yes, it is perfectly fine to stay with 1.0.3.4 if you have an AT&T Galaxy S4.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
i use nandroid manager from the market :)

as far as teh time stamps, recovery boots up and isnt getting the proper time (hence why it thinks its unix time nad the 70's)

for teh most part, yea...
[AT&T Samsung Galaxy S 4 Android Development] ErasZhou:
I flashed 1.0.3.5 with 1.0.3.4 rev

covery, why is it still 1.0.3.4?
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Hey OP Updated your recovery in my one click tool. Uploading now
[AT&T Samsung Galaxy S 4 Android Development] highaltitude:
Mine too
[AT&T Samsung Galaxy S 4 Android Development] RiNo808:
Is it confirmed that the new version is fixed, safe to flash and is working?
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
all set and uploaded to dropbox :)

apparently i hit my usage for this month :)
[AT&T Samsung Galaxy S 4 Android Development] sangerpb:
same here, thought i did something wrong so I did this.

Flashed back to TWRP

Tried to Flash .5 no luck

Flashed .4 and it worked just fine.

Tried to flash .5 no luck.

I'm on an ATT 32 GB
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
when did you download teh files?
[AT&T Samsung Galaxy S 4 Android Development] sangerpb:
about an hour ago.
[AT&T Samsung Galaxy S 4 Android Development] h3r3tic:
Just tried this now with tasks newest build and got system software not authorized. thats on .5
[AT&T Samsung Galaxy S 4 Android Development] fastblack:
Same issue here.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
im working on it currently, some kind people were nice enough to join irc and test for me so it will be resolved soon enough, rather than me throwing darts trying to figure out what the issue is :)
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Thank you for your hard work.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
all set, links working and its all good :)
[AT&T Samsung Galaxy S 4 Android Development] highaltitude:
It worked, thanks!
[AT&T Samsung Galaxy S 4 Android Development] flinttownbrown:
I had an issue with this version and the updated task AOKP which has auto-loki in the ROM install script. Wouldn't boot the kernel.

When I reverted to the .4 version it worked without issue.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
i would need to see cache/recovery/last_log in order to have an idea of what happened
[AT&T Samsung Galaxy S 4 Android Development] flinttownbrown:
Unfortunately I wiped my cache after reverting to .4 so I don't think I have what you need. I'll look at reproducing this tomorrow and provide it to you.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
ok, thanks :)

1.0.3.5 is just a bump up to make sure auto loki works a bit smarter, so if 1.0.3.4 is working for yall there really isnt any need to upgrade. i just happened to be working on my auto loki script with dees_troy and wanted to update for yall :)
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
You are seriously doing some major work for everyone here. There should be an admission fee to get into this thread..and I hope people are remembering you when it comes to the donations. It is because of Dan, you, and dees_troy that we even have custom recoveries and all the goodies that come with them. Again, thanks.
[AT&T Samsung Galaxy S 4 Android Development] russiandivxclub:
I am afraid to touch anything cause things change so fast BUT. Right now I am on TWRP and obviously my device is rooted. How do I go from TWRP to CWM with auto-loki feature ... ? Can I use guide on first page if this post or for me I need to do something else. ATT i337

Thank guys.
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Its been stated several times in this thread already but all you should need to do is flash the first download (version 1034 zip if available or 1035) in the OP through TWRP. There are a few issues that you might come across that have been identified and answered already that is why it is important that you read this entire thread to prepare yourself. Good luck.

**Edit**

Some people are claiming issues with version 1035 so if you get that version you can just wait a day or two until it is verified as OK just to be on the safe side.
[AT&T Samsung Galaxy S 4 Android Development] russiandivxclub:
Thank you. I was a bit confused it said CWM Flashable - OUDHS CWM-based Recovery 1.0.3.5 (need to already have a recovery for this) "CWM Flashable" I tought I need to use Rom Manager to flash this OUDHS-Recovery-jflteatt-1.0.3.5.zip file. Now I know I need to flash that zip within TWRP recovery.

Thank you !
[AT&T Samsung Galaxy S 4 Android Development] DeathAngel66669:
I had issues yesterday with .5, but everything is fine so far today. i started fresh on a new phone after rooting it, no issues to report yet. Thanks for all that you have done for us now and in the future shabbypenguin.
[AT&T Samsung Galaxy S 4 Android Development] Skyrocket2:
Hi Shabbypenguin,

Is this recovery exFAT support?

Thanks in advance for your response.
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Clearly, I am not shabbypenguin, but maybe I can help. Post 212 in this thread would suggest that it does not. There are other posts in this thread that reference it as well.

http://xdaforums.com/showpost.php?p=41878743&postcount=212
[AT&T Samsung Galaxy S 4 Android Development] Skyrocket2:
Thanks [MENTION=4398886]scott14719[/MENTION]. Just missed it. It would be nice to have that capability since it's such a great recovery.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
you are correct :) thanks for helping

exfat is closed source, not to say its not possible.. but it makes it harder and custom kernels dont support exfat as well (closed source issue again :/) which normally wouldnt be a terribly big deal.. but since the setuid stuff custom kernels may be required for future rooting attempts :/
[AT&T Samsung Galaxy S 4 Android Development] russiandivxclub:
Last quick one. For people with TWRP to flash this auto-loki CWM all they have to do is Go to TWRP ----> Install ---> select OUDHS-Recovery-jflteatt-1.0.3.5.zip (zip from first link) ---> Done

Correct ?
[AT&T Samsung Galaxy S 4 Android Development] cwburns32:
I did and everything seemed just fine. I installed this recovery with the intent to install Task's AOKP ROM... did everything as I usually do as I have been using his ROMs for a very long time now, most recently his GSIII AOKP ROM.

Now besides all that because this happens anytime I try to install any ROM for that matter. I get message stating that AT&T unauthorized software is recognized yada yada yada. Top left corner has "Secure Fail : Kernel." I don't want to have to ODIN back to stock just yet but it seems more and more likely... anyone have any suggestions?

P.S. I DID download the .5 file after shabby fixed it and I followed instructions on how to install this recovery to a T as well as the ROM instructions.

Any help would be great!

EDIT: I came from TWRP and flashed through TWRP as well.

EDIT 2: Shabby I downloaded your stock recovery tar and am in the process of downloading 1.0.3.4 as I can see after a little more research that seems to work just fine and .5 seems to have a few issues for certain people. I can just ODIN back to stock recovery, put the .4 version on my SD card and somehow install .4 version?!?
[AT&T Samsung Galaxy S 4 Android Development] acruxksa:
You should be able to just download the .4.zip Boot into .5 recovery and flash it.
[AT&T Samsung Galaxy S 4 Android Development] russiandivxclub:
After flashing CWM .5 I backed up my system. After I tried to reboot and it told me that root is possibly lost "should I fix it ?"

What do i do ? should I let it fix or ignore ?

And another thing what is SUPER PROPER way for installing CM for very first time. I mean should I format /system or ....like what is 1.2.3.4.5 for me here ?

---------- Post added at 03:24 AM ---------- Previous post was at 03:07 AM ----------

No Install-Recovery.sh file for me too. I installed .5 CWM without any problem.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
ok so something is wrong with my auto loki script. ill let deestroy know, however i cant do anything to fix it without any logs as i said last time :/

as it stands idk what is going on that is causing issues...
[AT&T Samsung Galaxy S 4 Android Development] cwburns32:
I did indeed revert back 1.0.3.4 and the ROMs all flash just fine but now I have no internet. This is obviously not an issue with your auto loki script but just wanted to let you know 1.0.3.4 works perfectly fine. I am sorry I did not provide with a log.... I believe it is too late now.
[AT&T Samsung Galaxy S 4 Android Development] Thermalwolf:
I'm looking up now on how to grab the log, will post in a little bit but I can also validate that something is up with smart loki in .5 but in .4 everything flashes just great :confused:
[AT&T Samsung Galaxy S 4 Android Development] xTristinx:
when trying to use adb i get

[+] loki_flash v1.1

[-] Failed to open aboot for reading.

can anyone help
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
whoa, you have a canadian sgs4 and dont need to use loki.

what do you mean when you used adb?
[AT&T Samsung Galaxy S 4 Android Development] xTristinx:
Ahahah ok thanks
[AT&T Samsung Galaxy S 4 Android Development] gg_monogram:
i realize when i reflash from .5 back to .4, my boot screen "Samsung Galaxy S4" is gone, instead it shows SAMSUNG CUSTOM with a padlock logo now, any specific reason for this not happening on .5 but .4?
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Make sure you have SuperSU installed and update binaries. Several threads throughout the forum discuss this issue further. Search for "custom" or "SysScope" should help to answer your questions.
[AT&T Samsung Galaxy S 4 Android Development] gg_monogram:
no wonder the issue is resolved after my reboot, thank you.
[AT&T Samsung Galaxy S 4 Android Development] Jgm3590:
just wanted to say great work

just wanted to say great work brother i am relatively new to this whole thing and have learned a lot about so far and this thread helped a lot
[AT&T Samsung Galaxy S 4 Android Development] pokedroid:
None of the download links will work on my phone or tablet, regardless of browser. Anyone else experiencing this or is it just me?
[AT&T Samsung Galaxy S 4 Android Development] riassan:
I see you still doing BIG things bro! How you been? I'll be using this sometime this week with my I337 when I pick it up on a even swap for my note 2. I'll catch up with you in a irc near you. Lol ;)

---------- Post added at 01:51 PM ---------- Previous post was at 01:49 PM ----------

Did you try boat browser and setting the ua string option in settings to desktop?
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
Ok I've dl all the files n the op.. I'm currently running twrp but would like to use this can i jus flash the flashable itself through twrp??..
[AT&T Samsung Galaxy S 4 Android Development] rav4kar:
Yes, you are right.
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
Thanx all the abd talk and all the files trew me off
[AT&T Samsung Galaxy S 4 Android Development] coffeehandle:
Sure hope this is on goo manager!
[AT&T Samsung Galaxy S 4 Android Development] Dinky:
It looks like we have a recovery which works with exFAT in the sister platform forum

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

Will we soon have a version of your great work supporting exFAT? Thanks.
[AT&T Samsung Galaxy S 4 Android Development] russiandivxclub:
I don't know if this is news but my Rom Manager just gave me update notification. Rom Manager now know i337 ATT model and will install recovery automatically , just press install / update button you'll see "jflteatt" build, when before if was "select your phone model" because Rom Manager could not recognize i337. So amazing news. As of right now 6.0.3.2 is showing as latest version.
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Does it work? And is it Lokified / autoLoki? We need to make sure it is a working option before it is posted as an option. Otherwise it's just going to lead to a bunch of threads (more threads, that is) about people screwing their phones up. So, can you confirm that it works?
[AT&T Samsung Galaxy S 4 Android Development] russiandivxclub:
Here is what I did.

I had Rooted Stock with recovery from OP. I had my installation of Rom Manager on. I installed new recovery from Rom Manager. I checked if it's working. It is. Actually it looks exactly like one from OP, with same logo in the middle. Then I used same Rom Manager to download CM 06.06 build and gapps. Then I went to recovery did backup and install of that 06.06 build. Everything work perfect right now. No problems so far.

About loki. I actually not sure what it is. All I know Rom Manager auto installation worked, recovery works, rom provided with rom manager works, after installation of rom I see no problems. In lame terms what's loki ?
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Thanks for responding back. It sounds as if ROM Manager is installing OUDHS, if that is the case it is all good.

Loki is the workaround method that AT&T users have to use for installing custom recoveries and Kernels because of the locked bootloader.

This thread will explain it more...

http://xdaforums.com/showthread.php?t=2292157
[AT&T Samsung Galaxy S 4 Android Development] russiandivxclub:
Oh thanks, now I know. Actually I really like new 06.06 ROM and whole setup in general here are quick numbers:

On stock:

3DMark Ice Storm Normal: 10201

3DMark Ice Storm Extreme: 6612

Quadrant: 12459

On CM Build 06/06/13:

3DMark Normal: 10545

3DMark Extreme: 6393

Quadrant: 6100

So as you can see 3DMark results are pretty much the same but Quadrant is about half less than with stock. I am not sure if it means anything but by just using it and playing games I see no difference at all. So that score don't mean anything. Great work everyone !
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
Ok so I was on twrp and I attempted to to flash the recovery tht has lok and the end amd failed.. so I tried the one witout it and flash jus fine.. thing is i assume the one tht the lok one is what I need right to b Loki ed out??...

Edit I also used rom mgr and got the update tht supports loki hope tht means it has loki pre installed lol
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Yea, as long as you are using the AT&T S4 you will need Loki. At least until /if the bootloader is ever officially unlocked.
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
I tried the zip wit lok and it failed should I re download??... Also WOW my stock rooted nandroid is 3.9gb??.. Insane
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
Both images are loki patched, teh lok file is for loki_flash tool, if you have recovery just flash the other zip and you are golden :)

this is not in rom manager nor will it ever be, its based off cwm but it is not. gweedo pushed out official builds of regular CWM for all the sgs4's. it is loki'd so it will flash just like twrp flashes like goo manager, it does not however have auto-loki so keep that in mind, any further questions about their cwm id suggest directing at them :)
[AT&T Samsung Galaxy S 4 Android Development] tsouza:
Should auto loki work with Wanamlite's kernel (adam kernel)?

Cheers
[AT&T Samsung Galaxy S 4 Android Development] thomasskull666:
As always, fine work mr. Shabby. Hit me up on gtalk sometime bud!
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
Is there a way 2 for into recovery manually
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
should work on all kernels :)

NO U! why are you on att? what terrible evil things happened in your life that made you leave teh awesomeness of sprint? :P

volume up as you power on teh device
[AT&T Samsung Galaxy S 4 Android Development] djmouse:
quick qestion? im loving this recovery i was having so many problems with twrp 2.5.0.3 ,anyway is there a way to name the backup? and i see option for default backup format, or something along those lines, what is the default backup format?
[AT&T Samsung Galaxy S 4 Android Development] Mike:
The default backup is a .tar format. As for naming backups you can edit the names via a file explorer after you backup

Sent from my AT&T Galaxy S4 Running AOKP 4.2.2
[AT&T Samsung Galaxy S 4 Android Development] djmouse:
gotcha thanks man.

---------- Post added at 12:43 AM ---------- Previous post was at 12:40 AM ----------

if this recovery keeps my phone stable,i gotta good donation coming to the dev of this,just wish i would have done this a week ago would have saved me some time and aggravation.

i like to just boot to recovery and mess with the rainbows hahah, and im using goo manager to boot into recovery,hope thats not gonna mess anything up?
[AT&T Samsung Galaxy S 4 Android Development] MikeC4510:
Let's just hope you don't wait 1 hour and 40mins for a backup to finish (like I did today. It was absolutely brutal [*note: Idek why it took so long. Usually never takes more than 10-15 o_o]).

As far as booting into recovery, depending which ROM you're in, you can just boot into it via the power menu :p

Sent from my I337~SGS 4 using Xparent Skyblue Tapatalk 2
[AT&T Samsung Galaxy S 4 Android Development] djmouse:
all is good backups are done, i dont have that scary feeling anymore when i reboot now,and yea the rom im using MINT JELLY v2.1 has it built in the power menu....
[AT&T Samsung Galaxy S 4 Android Development] Planktron:
I have one small question... In TWRP you can select to backup EFS/IMEI. I don't see this in CWM. Is this done automatically or is it incapable of backing up that partition?
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
do not just rename teh folders, it will cause md5 mismatches which will break your backups. i use nandroid manager in the market to rename them.
[AT&T Samsung Galaxy S 4 Android Development] Planktron:
How did you know I did that? I'm sitting at work with a half-dead phone because I renamed the folder and for some reason Mint Jelly refuses to flash on my phone.. Gotta ODIN to stock when I get home :(

When I tried to restore after my failed Mint Jelly attempt and saw the MD5MISMATCH! I didn't know whether to laugh or cry.
[AT&T Samsung Galaxy S 4 Android Development] tsouza:
When I flash Adam Kernel (wanamlite kernel) I get the warning screen stating that kernel isn't a recognized... :/
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
because mike on xda told you to do it like that, i wanted to step in and stop it before something like that happened :/
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
something is wrong in my new script and i cant figure it out, since it had been several days and no one had mentioned it i wasnt sure if it was a passing issue, or something else. since i asked for logs when the first people started to mention issues and i never got them i assumed they worked the issue out themselves.

ill revert teh links back to 1.0.3.4 for now, everyone should roll back.
[AT&T Samsung Galaxy S 4 Android Development] Planktron:
No harm no foul on anyone...I should have verified my backup would work before I went flashing things that deep down in my heart I knew wouldn't work anyway. I could download the required items here at work to ODIN to stock but the internet connection is about 50kb/s:eek:

I'm so bored now:cyclops:
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
if you have adb access you can fix the md5 actually.

# cd /data/media/0/clockworkmod/backup

# ls

(figure out which folder is the backup you want)

# cd (foldername)

# rm nandroid.md5

# md5sum *img > nandroid.md5

that should make a new md5sum for ya and thus let you recovery. bear in mind recovery adb drivers are a bit more of a hassle to get working (it does work i assure :P )

i use a mix of samsung drivers and koush's universal adb drivers.
[AT&T Samsung Galaxy S 4 Android Development] Planktron:
Thanks buddy, but by the time this machine downloads the SDK and I spend time googling the difference between ADB and Recovery ADB, we will all be drowning because the poles melted :p Plus, as I'm still unaware of why that rom wouldn't flash properly, I might as well go through with it all and start fresh.

And BTW...you never answered my question on EFS/IMEI backups through CWM :cyclops:
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
Couldn't you just uncheck, check md5 in the recovery?
[AT&T Samsung Galaxy S 4 Android Development] Planktron:
I saw no option for that. Believe me I looked..