yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
I saw you post in kangakat thread about you're brand new phone and I warned you to check you're firmware. Were you on post mf3 and you were trying to do what? I mentioned you that you should read about it right? Find mf3 Odin firmware. That's you're last ditch effort and hope it was not already on mk2. If it was you done. You can't go back now with Odin. Hope mk2 Odin is leaked but it took good 3 or 4 month for mf3 to be leaked. So may be a long and painful wait.

Sent from my GT-I9505G
[AT&T Samsung Galaxy S 4 Android Development] Jodicus6645:
I'm on 2.6.0.0 should I update to the latest before the kitkat update of GE ROM? Also what would be the best method of updating TWRP? Ive tried GOO last time I updated and it broke everything had to stock and re root ect. Thanks in advance.
[AT&T Samsung Galaxy S 4 Android Development] trunzoc:
That's weird. Like CZ Eddie, I have not gotten a single hang with 2.6.3.1, even the unofficial version I've used since Oct

Sent from my AT&T S4 running KangaKat.

---------- Post added at 08:31 AM ---------- Previous post was at 08:28 AM ----------

The GE rom says 9505 in the build prop so Goo tries to install that version and Messes up the phone. Best method is via adb or to wait until someone makes a flashable zip

Sent from my AT&T S4 running KangaKat.
[AT&T Samsung Galaxy S 4 Android Development] 78Staff:
Yeah, not sure why I have trouble with it - with the unofficial .1 posted earlier in the thread a few weeks back - occasionally I will get a hang at the GS4 logo screen and have to long power to reboot again and then it's fine, with the official I had to long press reboot several times to get it to boot after being in recovery. May be issue with my hardware only, I suppose, or a glitch b/c I had just flashed a modem, not sure. I'll try official .1 again and see if the issue persists. It's just that 2.5.0.2 has no issues other than the annoying fix root message everytime, and the data format bug I suppose :(

Ed - OK I have reloaded the official .1 image, so far no hangs...Fingers crossed it holds true this time ;)
[AT&T Samsung Galaxy S 4 Android Development] aycockonxion:
I just want all my ducks in a row before I start jacking with my S4, but I just got the 4.3 OTA. Is it correct that this recovery won't work properly with MK2? I'm hoping to go through the Vroot process tonight and I'd like to have a better recovery in hand before I move on to something custom 4.4.
[AT&T Samsung Galaxy S 4 Android Development] Bradl79:
Correct do not attempt. Go to safestrap and see it it is compatible with u r software
[AT&T Samsung Galaxy S 4 Android Development] 78Staff:
If you took an OTA, then you are effectively boot locked (MF3 and up), even if you weren't before (MDL and below).

So, yes, you are correct this will not work for you. If you are on 4.2.2/MF3, or can get back to Offical MF3 (there are tars out there for Odin) then you could use SafeStrap (http://xdaforums.com/showthread.php?t=2448925) which has a TWRP-variant recovery... However at this time SafeStrap does not work with 4.3+.

Unless something new has come out in the past week or so, if you OTA'd to 4.3 then you are stuck there until someone can figure out how to work around the locked bootloader.
[AT&T Samsung Galaxy S 4 Android Development] aycockonxion:
Thanks, that was my thought.

I appreciate the detail. I had that feeling. OTA 4.3 MK2 feels janky, but I'll just hang in there for a few weeks until a good root and recovery come along hopefully in a couple of weeks.
[AT&T Samsung Galaxy S 4 Android Development] Bradl79:
Have you looked into safestrap so u can flash a custom rom

---------- Post added at 11:17 PM ---------- Previous post was at 11:11 PM ----------

I can't install 2.6.3.1 downloaded the img and installed through terminal and still shows 2.5.0.2. Goo.im will not download
[AT&T Samsung Galaxy S 4 Android Development] oak:
I have zero hangs on 2.6.3.1.
[AT&T Samsung Galaxy S 4 Android Development] Bradl79:
Any flash able zip available
[AT&T Samsung Galaxy S 4 Android Development] Febby:
Here's 3.

MediaFire: http://www.mediafire.com/?k9okxzy2yozuyxb

Box: https://app.box.com/s/eckh8a0krm05iuklsjmt

Dropbox: https://db.tt/oWgPH1m0

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

- Emmitt Smith
[AT&T Samsung Galaxy S 4 Android Development] 78Staff:
I'm still getting hangs on reboot occasionally, as the GS4 screen, same as always :(. Must be something with my phone. It's a minor thing, I guess. I would just stick on 2.5.0.2 but I know at some point I would forget about the data format issue and hose up my phone...

I had loaded the img via wireless adb, but will try the zip file Febby provided, not sure that would make any difference though...
[AT&T Samsung Galaxy S 4 Android Development] Bradl79:
thank you

---------- Post added at 06:03 AM ---------- Previous post was at 06:02 AM ----------

i think the hang on the GS4 screen is based on ur kernel, are u using KT kernel?
[AT&T Samsung Galaxy S 4 Android Development] 78Staff:
No, the stock kernel from Task650's AOKP Rom - Kernel: 3.4.0-Underwear.Kernel - although they may have similar traits - Task and Ktoonsez have worked together on Sx before...

https://github.com/task650/underwear_kernel_samsung_jf
[AT&T Samsung Galaxy S 4 Android Development] jproy12:
I'm also getting the occasional hang at the GS4 logo, I'll learn to live with it! What do you mean by the "data format" issue? I've never done a "data" format, but should I try it out?

I used the .tar file from twrp site and loaded it via odin, nice and simple!
[AT&T Samsung Galaxy S 4 Android Development] 78Staff:
Apparently formatting data with 2.5.0.2 can cause issues (although I can't confirm, I've never formatted data with that version). However, you really don't need to format data often, I do it sometimes when changing roms, ie from TW to AOSP type rom, etc...
[AT&T Samsung Galaxy S 4 Android Development] jproy12:
Thanks! So formatting data with the new 2.6.3.1 should be ok? What are the advantages of doing a "Format Data" where you have to type "yes"?

Thanks,

JP
[AT&T Samsung Galaxy S 4 Android Development] :
I have never formatted data with twrp even on previous phones. I go thru advanced menu and wipe system/data/caches 3x and have never had an issue on 2.5.0.2. With aosp/gpe/tw--:good:
[AT&T Samsung Galaxy S 4 Android Development] 78Staff:
yep none of that is formatting data, so you should not have seen any issues...

Heck it may not even be an issue, as I stated I've never done it in 2.5.0.2 in fear of the problems others have mentioned. There is also an option to use rm -rf instead of formatting iirc, which may not cause any issue at all as well.

I've had no issues formatting data in other versions of TWRP, however. But It really isn't necessary in normal use, tbh.
[AT&T Samsung Galaxy S 4 Android Development] :
lol yeah just pointing out what you mentioned. No need to use the format feature. :)
[AT&T Samsung Galaxy S 4 Android Development] Locoman_:
While that may be true, some do. I did it with TWRP before and screwed up my partitions. Had to Odin to stock, reroot, etc. Since then I've been on Philz but I really dig the TWRP interface.

So again, is the wipe issue resolved in this latest version?

.
[AT&T Samsung Galaxy S 4 Android Development] :
I scan the thread on occasion and believe it is. So many use 2.5.0.2 including some devs. Still believe it is best for most--:good:

Interface is slick--:)
[AT&T Samsung Galaxy S 4 Android Development] 78Staff:
Just a clean slate, you'll notice if you just do a standard wipe old directories, etc will still exist. If you are upgrading same rom, or similar style rom and using same apps, etc - it's pretty much a non issue. I would definitely do it if selling phone or trading in or anything like that though.
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
The hang at the GS4 logo (splash screen) has been around for me at least, with ANY recovery. It started happening after I flashed my first 4.3 ROM. I never had the issue on 4.2.X ROM's.

So it's been ever since 4.3 and now on 4.4.

Happens with Philz Recovery and all versions of TWRP. And it's only once in awhile, not every time. So I highly doubt it's a recovery issue. I'm more inclined to think it's firmware related.

As for the hang while loading TWRP, that is gone for me now. That used to happen all the time on older TWRP versions for me. And that is the hang that is gone with 2.6.3.1. Also, the phone would occasionally hang while wiping cache. And that is gone now too.

2.6.3.1 is working pretty good for me so far still.
[AT&T Samsung Galaxy S 4 Android Development] jzd5032:
I've tried every option/feature in the latest 2.6.3.1 and it works flawlessly. The only two twrp recoveries I completely trust are 2.5.0.2 and 2.6.3.1.
[AT&T Samsung Galaxy S 4 Android Development] WarlockW:
TWRP 2.6 - Samsung Galaxy S4 (AT&T)

TWRP 2.6 - Samsung Galaxy S4 (AT&T) ONLY!

DATE: 2013-11-25 8:03:41 PST

Made a Recovery zip of the S4_ATT_Twrp.v2.6.3.1 - Official

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

Download Link: http://d-h.st/45y
[AT&T Samsung Galaxy S 4 Android Development] Aqua1ung:
Many thanks! Got TWRP 2.6.0.0 on mine, and I'm not happy (hangs a lot while loading TWRP). Trouble is, the Goo.im method doesn't work for me (long story, can't load Android). Can I flash this one from within TWRP 2.6.0.0 itself, just as I were flashing a ROM? Also, does this Loki ROMs automatically, or should I keep a loki-doki copy handy nearby? (Note that I am looking to flash danvdh's 4.4 GE ROM.)
[AT&T Samsung Galaxy S 4 Android Development] WarlockW:
Can I flash this one from within TWRP 2.6.0.0 itself, just as I were flashing a ROM?

YES

Also, does this Loki ROMs automatically, or should I keep a loki-doki copy handy nearby? (Note that I am looking to flash danvdh's 4.4 GE ROM.)

This is ONLY the recovery ...

So you do not need to flash loki

LOKI Is For KERNELS Not recovery :)
[AT&T Samsung Galaxy S 4 Android Development] CPA Poke:
To clarify (so he doesn't get a yellow triangle :cool: ), this recovery does NOT auto-loki non-ATT ROMs. To my knowledge, the only recovery that does that is OUDHS CWM recovery (which I don't think has been updated for some time). You need to flash loki-doki anytime you are flashing a ROM or kernel that was not specifically developed for jflteatt.

Edit: So I feel like I'm taking crazy pills....are [MENTION=4274380]CZ Eddie[/MENTION] and I the only ones that can see the unofficial and official download links for 2.6.3.1 that have been out for awhile now? Every time someone posts another link to it, people come back to this thread and start asking flashing questions, etc etc.

Lol
[AT&T Samsung Galaxy S 4 Android Development] MAFU21:
Where can I find the loki doki file and how it works im newnon this device. Just 3 days with ot. Sorry for noob question.
[AT&T Samsung Galaxy S 4 Android Development] CPA Poke:
No prob...I'm sure it's floating around here somewhere, but here is a link:

http://www.mediafire.com/?kka6fbfcs5bviuh

As far as what it does, you need to just search "loki" in the ATT S4 forums and read the Q&A thread by [MENTION=4229979]djrbliss[/MENTION].

You only need to use it if you're flashing a ROM or kernel from any of the non-ATT Qualcomm chipset variants. One you flash the ROM, just flash the loki-doki zip BEFORE YOU REBOOT for the first time. From recovery, it will loki the boot.img from the ROM you just flashed so it doesn't get picked up by our locked bootloader.
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
I flashed an AOSP 4.4 ROM on my Galaxy S4 i337 and it started hanging like CRAZZZY at the splash screen.

I was ready to throw in the towel for TWRP at that point.

So I full-wiped and ODIN'd to stock and installed CWM that everyone raves about.

Still had the same problem.

Then.... I installed a different kernel for the same ROM.

And I have not had a single Galaxy S4 splash screen hang since then. And I've done about 15 reboots since.

So, the splash screen hangs IMO, are something in the kernel. Nothing to do with the recovery or ROM.

Loving TWRP all over again.... :good:
[AT&T Samsung Galaxy S 4 Android Development] byte9:
Many thanks, I had lost track of TWRP since 2.6 original build that hung to the heavens, went back to 2.5.0.2 and now loaded this bad boy for test rebooting into recovery. Did like 10 reboots with no hangs. <3 LOVE
[AT&T Samsung Galaxy S 4 Android Development] fnkyscotty:
Will this recovery work if i1337 is updated to baseband ending in MK2?
[AT&T Samsung Galaxy S 4 Android Development] WarlockW:
Yeap .. Seems to work Much Better ...

v2.6.3.1 - DATE: 2013-11-25 8:03:41 PST

I Get No Hangs from this Ver. Also :)
[AT&T Samsung Galaxy S 4 Android Development] ozziedog:
What Kernal did you flash if you don't mind me asking?
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
I installed Ktoonsez 4.4 AOSP kernel that was released on 12/4/13.
[AT&T Samsung Galaxy S 4 Android Development] ozziedog:
Thanks I'm going to try that nothing else is working for me on CM11, I'm getting random restarts, screen freezing, and I can't read nor write to SD card. Thanks again.
[AT&T Samsung Galaxy S 4 Android Development] Aqua1ung:
Not sure what to say, as my i337 AT&T was also hanging at the splash screen (Samsung/Custom/padlock) with Danvdh's Dandroid. Once I upgraded to TWRP 2.6.3.1 (from 2.6.0.0), flashing new ROMs no longer produced unbootable ROMs.
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
I did the same upgrade, to 2.6.3.1 and continued to get the splash screen hangs.
[AT&T Samsung Galaxy S 4 Android Development] kevin_3_57:
Is there a way to uninstall TWRP without going completely back to stock?
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
Install a different recovery or install the stock 3E recovery.

But you have to have *some* kind of recovery one way or the other.
[AT&T Samsung Galaxy S 4 Android Development] kevin_3_57:
Great, thanks!
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
Is there 2.6.3.4 available for I337 yet by chance?

Sent from my SGH-I337
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
2.6.3.1 it's the latest on team win site
[AT&T Samsung Galaxy S 4 Android Development] hednik:
What's the thinking on using mobile odin to flash the recovery.img on MDL ?
[AT&T Samsung Galaxy S 4 Android Development] twcobra:
I just came back to TWRP from a CWM recovery. I had the same issue coming to 2.6.3.1 along with random reboots when the ROM would reboot. I did a permission fix and the problem was resolved.
[AT&T Samsung Galaxy S 4 Android Development] titaneds73:
i have been using 2.6.3.1 since it came out and have not had one single issue flashing or booting in to recovery very happy
[AT&T Samsung Galaxy S 4 Android Development] 78Staff:
Is 2.6.3.1 official now - I only ask since the thread still references 2.6.3.0 in the title. Usually it gets updated to the current official version and date of release...
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
TWRP website says so....
[AT&T Samsung Galaxy S 4 Android Development] boogiecornejo:
i installed this over an older version twrp using goomanager and now my phone wont enter recovery. a warning about unauthorized software just keeps on popping up when i try although the phone still boots up and functions normally. what do i do to get my recovery back?
[AT&T Samsung Galaxy S 4 Android Development] beast3300:
No problems out of 2.6.3.1 here. I have not tried the format internal memory thing though. I did have hangs on other versions besides of course 2.5.0.2.
[AT&T Samsung Galaxy S 4 Android Development] trunzoc:
Are you using KangaKat?

Sent from my AT&T S4 running KangaKat.
[AT&T Samsung Galaxy S 4 Android Development] ksj0823:
quick question.

If the MK2 is the last update from AT&T. I mean IF there is no update from AT&T anymore. Is that means all MF3 MK2 user not able to flash any KitKat rom?
[AT&T Samsung Galaxy S 4 Android Development] trunks_ss2:
have u gotten it fix yet? just turn off the phone push the volume button down and home key button the power up the phone while still pressing those buttons then just follow the commands and reboot
[AT&T Samsung Galaxy S 4 Android Development] MOster:
Thanks. Using goo.im for this has never worked for me.
[AT&T Samsung Galaxy S 4 Android Development] Werewolf88:
I can't flash recovery over the Goomanager, it says there are no recoveries for my device

I'm on Canadian i337 with Omega Rom v19

Sent from my i337m
[AT&T Samsung Galaxy S 4 Android Development] aycockonxion:
Rooted with MK2 currently..

What would happen if I flashed TWRP from Safestrap? Would the world end? Would my phone turn into a giant lizard and eat my dog?
[AT&T Samsung Galaxy S 4 Android Development] twcobra:
No the giant lizard would breathe fire and burn your house down.
[AT&T Samsung Galaxy S 4 Android Development] tjizzle:
Is there a serious answer for this question? I'm trying to do the same thing. Can the latest twrp be flashed from safe strap running a 4.3 at&t rom? I've never had this much hardship rooting/modding a phone before.

Also can I flash 4.4 roms like cm 11 with this recovery? Any help will be greatly appreciated. Thanks
[AT&T Samsung Galaxy S 4 Android Development] ozziedog:
Check out safestrap thread, but I don't think CM11 won't and not sure about TWRP but would venture to say more than likely not.
[AT&T Samsung Galaxy S 4 Android Development] :
Respectively, it's been answered all over the forum. NO custom recoveries or kernels. TW only if MK2 and, I believe, 4.2.2 if on MF3. That is AFAIK. Things can change, the latest beta SafeStrap 3.7.? offered some new things.

And as ozziedog said, get heavy into the SafeStrap threads. There are numerous ones and not just on the first page of General and Q&A. May need to go back a few pages on them also.--:good:
[AT&T Samsung Galaxy S 4 Android Development] tjizzle:
Thanks for the replies guys. I've been doing tons of research the past week or so. I guess I'll do some more. But thanks for saving me extra headache
[AT&T Samsung Galaxy S 4 Android Development] sgndroid1:
What's the recommended sd card format? I formatted my sd card to exfat, but takes like 15 min to do a backup compared to about 5-6 min when is formatted as fat32. I don't know it it could be an issue on my end.
[AT&T Samsung Galaxy S 4 Android Development] :
I have a Sammy 64gb and it came exfat--never any issues with any rom---:good:

Some folks awhile back had exfat issues on some roms, don't think it is an issue anymore as i have flashed about every rom out there--
[AT&T Samsung Galaxy S 4 Android Development] LuRock:
Hi I'm coming from philz cwm, I installed twrp thru goo and after attempting to boot into recovery I just get the ATT unauthorized screen which I have to go into download mode to break the cycle. And boot back into my kitkat rom. I tried to install cwm from ROM manager as well but when trying to boot into recovery I get the ATT unauthorized screen again. Im still rooted after checking but don't know what to do from here to get a recovery back. Anyone experienced this with a resolution? Thanks..

Flashing never gets old?
[AT&T Samsung Galaxy S 4 Android Development] lauterm:
You could try motochopper.
[AT&T Samsung Galaxy S 4 Android Development] upndwn4par:
Most likely what happened is that, since you are running a KK ROM, the ROM dev didn't change the device to the SGH-I337 in the build.prop. So when you flashed TWRP with Goo it installed TWRP for another device (most likely the GT-I9505G).

I posted some flashable zips on this thread. Flash one of those (I recommend 2.5.0.2) and you should be GTG. ;)

Also, you should tell your ROM dev to fix the build.prop so it indicates the proper device.
[AT&T Samsung Galaxy S 4 Android Development] LuRock:
Yes your right my built.prop shows I9505G. :banghead: can I just correct the build.prop to I337 and flash the zip you posted?

Flashing never gets old?
[AT&T Samsung Galaxy S 4 Android Development] twcobra:
Try flahify from the market. When you select install recovery it will give you a selection of recoveries to download. Make sure its a ATT recovery. It sounds like goo mis read your phone and installed a non lokied recovery.
[AT&T Samsung Galaxy S 4 Android Development] upndwn4par:
Yep, that will work.

I would suggest flashing a zip from this thread since you are certain to have the correct one installed. I also highly recommend 2.5.0.2 since it is the most reliable version for 4.3.
[AT&T Samsung Galaxy S 4 Android Development] LuRock:
Man I can't get it to work:banghead:

I changed build.prop tried flashify, ROM manager, and goo to flash recovery but no go:confused:

Flashing never gets old?
[AT&T Samsung Galaxy S 4 Android Development] twcobra:
Last resort is going to be Odin to stock and then re root. Before you do that though try pulling the recovery.img file out of one of your original recovery install zips you have used in the past and you know works. Then direct flashify to that image file then flash. This has got me out of trouble before. At this point you have nothing to loose if you have to go back to stock.
[AT&T Samsung Galaxy S 4 Android Development] LuRock:
OK finally got recovery to flash. I guess I missed a change or two in the build.prop. Thank you twcobra, upndwn and lauterm. Preciate it guys:thumbup::thumbup: there's always a haaaaaaaaa..... Relief when we avoid having to Odin back to crap! :D

Flashing never gets old?
[AT&T Samsung Galaxy S 4 Android Development] sgndroid1:
How long does it takes you to do a nandroid backup?
[AT&T Samsung Galaxy S 4 Android Development] :
I'll let you know. Updating some apps now, then will back all apps up with TB. Then I will time a Nandroid. I never worried about it, just figured it is what it is--:)

---------- Post added at 06:29 PM ---------- Previous post was at 06:05 PM ----------

It took--12 minutes

Not sure what that means to your fat32 times. Text says "breaking backup into multiple archives". Don't know if that is card or recovery specific. Just never had any issues with my Sammy 64gb. Flashed most roms out there from TW to KK and Nightlies. TWRP (2.5.0.2) is the best recovery, no issues--IMHO--:good:

Current rom was 2.31gb--
[AT&T Samsung Galaxy S 4 Android Development] sgndroid1:
Thanks man. I guess that's good. It used to take me about 6-7 min with fat32 before, but it seems like is taking longer now, maybe with the latest 2.6.3.1. I just wanted to make sure it wasn't my phone. Thanks again man.
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
Are we still on 2.6.3.1 version for I337 ATT?

Is there 2.6.3.4 available yet by chance
[AT&T Samsung Galaxy S 4 Android Development] SelfElevated2:
No body wants to use goo man. Can you start posting zips in the op?
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
Nvm
[AT&T Samsung Galaxy S 4 Android Development] ddskier:
2.7.0.0 Was Released, but get error

FYI - It looks like 2.7.0.0 of twrp got released. I flashed it using goo.manager, but whenever I try to boot into recovery the phone reports the following error message: "System software not authorized by AT&T has been found on your phone".

Luckly this error message only shows up when booting into recovery. I can still get the phone to boot back into Android.

Anyone know how to fix this error message or flash back to 2.6.3.0?
[AT&T Samsung Galaxy S 4 Android Development] twcobra:
Odin back to stock and re root.
[AT&T Samsung Galaxy S 4 Android Development] Cusa:
Sounds like you are not using Loki doki. Flash Loki doki right afterwards.
[AT&T Samsung Galaxy S 4 Android Development] brizey:
I came over here from the Verizon side to see if you guys were having issues with 2.7.0.0 as well. Ours seems to be lokified, but it had several other issues for me, and I read similar things on the Sprint page. For ours, wipes crash the recovery UI but seem to work. Backups work, but restores don't. Flashing other recoveries does not work. Flashing ROMs did work.