yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] norml:
You forgot hokey pokey, lol. TWRP is the ONLY way to go. ;) And search, read, search, read, and search more, and read more is the definite way to go here I noticed as well. Take it easy.
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
....and then I turned myself around...thats what its all about! LMFAO funny .

Yeah..if i have a exFAT compatble recovery, and use lokidoki (whether built into the recovery or not) I will be fine.

I wanted to use Phil's modded CWM but obviously hes having some exfat issues. I have used TWRP since my old phones.

RIP Amon_RA

Casual is a great tool. I have to send donations soon.
[AT&T Samsung Galaxy S 4 Android Development] trueking7:
I used twrp to restore and it worked great on my rogers i337m, the only problem is, if I restart or power off then on or even pull battery and power on - - it gets stuck at the Samsung logo. Then I need to full wipe, format, and restore via twrp again. Any ideas what the problem is?

Sent from my stock rooted i337m
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
Did you do a full wipe before flashing your nandroid?
[AT&T Samsung Galaxy S 4 Android Development] trueking7:
Yes sir I do. I have successfully restored 3 times now after full wipe. But if I try to restart, it's stuck at Samsung logo

Sent from my rooted stock-TW Rogers SGH-I337M Galaxy S4
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
Hmm got me on that one. Have you flashed another rom, just to see if you get the same result?
[AT&T Samsung Galaxy S 4 Android Development] jroyalty7:
This is a known problem with twrp and should really be added to the op... if you do a full wipe the kind where you have to type yes to confirm it screws the rom or nandroid where it will boot once but never again after that. It results in you wiping and reflashing but again your rom will boot once but not again. You have to odin back to stock and then reroot/reflash etc.... then never ever do the wipe where ylu have to type yes again. :)
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
Preload option

I saw that TWRP has a "preload" backup option.... can someone PLEASE tell me what this is? When we should use it, etc. ? Thanks.
[AT&T Samsung Galaxy S 4 Android Development] Jonnyredcorn:
I'm having issue's with making and restoring backups. Several times I have been running a ROM(either Wicked v3 from T-Mobile s4, or Omega 5.0 & 7.0 from i9505) and when I create the backup it will say successful. Now when I originally made my backup of my stockROM after rooting that backup is fine and intact, but any backup I make of a custom ROM seems to be hit or miss if it restores successfully.

I have restored my stock ROM a few times to check a few things to see if issues I were having were ROM related or my phone, and when I would go to restore the backup I made before restoring my stock ROM it fails. I was able to make one backup of Wicked ROM that seems to work, but it is totally unreliable. I don't know if it has something to do with whether or not I back it up to my SDcard or my Internal Storage. I tried restoring my backup of Omega 5.0 yesterday and it seemed to go through the whole restore process but it said failed. I rebooted the phone and Omega booted up however I had to go through set up and a few of my apps were installed but it was obviously a corrupted backup, although it did restore some stuff.

Anyone else having this issue? I"m not experiencing unusually long backup/restore times, I know that when it does a backup it say's it is breaking it up into multiple archives and I don't recall ever seeing that before(I run TWRP on my Nexus 7 & GS3 as well, ran it on my Note 2 too. I've never used compression, and I usually backup boot, system data, and EFS. I would consider switching to a different recovery, I'm not quite sure what most people are using...but if I did switch would I lose the ability to restore my stock ROM backup? I really like TWRP but I need something reliable for nandroids.
[AT&T Samsung Galaxy S 4 Android Development] ex-28:
i just updated from

twrp 2.5.0.0 to the newest 2.5.02

havign this same problem i can only reboot once then i get stuck , this sucks , is there anyway to fix this issue with this version ?

or rool back to

twrp 2.5.0.0 and have it work normally agian , not sure what to do now as im stuck.

such a major bug would think it would be in op
[AT&T Samsung Galaxy S 4 Android Development] ex-28:
flashed back 2.5.0.0 restored my backup and still can only boot 1 time then it stuck at samsung galaxy s4 logo , ...danggg
[AT&T Samsung Galaxy S 4 Android Development] jroyalty7:
You have odin completely back to stock reroot and do recovery over again... trust me I learned the hard way!!!
[AT&T Samsung Galaxy S 4 Android Development] ex-28:
ok so once i go compleatelly back to stock then do i root again via twrp mothod ? install old version then i should be able to restore my latest backup ? , im lost here as i didi get back to my old version but after dumping my nandroid it still froze on boot screen.

appreciate the reply thank you

---------- Post added at 06:37 PM ---------- Previous post was at 05:48 PM ----------

is this problem with all versions or only this version ?
[AT&T Samsung Galaxy S 4 Android Development] jroyalty7:
I only tried this version and a slightly newer one so thats all I can vouch for. And yes once you odin back to stock you have to reroot and reinstall twrp. I personally use adam outlers casual as a one click everything. Im not sure if restoring your back up will throw you into bootloop again but you can try it. I just went with a clean install. Then from here on out only use the standard wipe where you swipe dont use the full data wipe where you type yes to complete it. Hope this helps.
[AT&T Samsung Galaxy S 4 Android Development] ex-28:
ok thanks for the info , i installed cwm to try that but couldnt find my nandroid backup i made with twrp , so i installed twrp again , selected restore and dumped my nandroid , it booted up i restarted and again stuck on samsung screen , ,,,,,,,,,,,,,,,

so once you wipe data factory reset with twrp , your sol ? , cant even get your backup to restore and work agian , eventho my twrp backup was made with

twrp 2.5.0.0

i dont get it , has to be somthing in the newest version and restroing a nandroid backup that is cauing it to freeze as my backup worked 100 % prior to updating to this newest version of twrp , mind you this is the 1st time i have ever done a factory wipe/data reset in twrp .............. hmmmmmm
[AT&T Samsung Galaxy S 4 Android Development] jroyalty7:
Just an fyi cwm and twrp nandroids are not interchangeable. So if your backup was done with twrp then you can only restore with twrp. If you made the backup after you already did the data wipe then its probably borked. Just try what I told you before and do a fresh install and re setup sounds like the only way your gonna get it working again.
[AT&T Samsung Galaxy S 4 Android Development] ex-28:
yup found out there not compatible , but after doing above and wipeing cache , it booted up my nandroid after restoring , whee , got lucky on that one i know , had soo many things setup it took me 5 + hrs today but got it to work,

note to self never for a data factory reset with this again unless i wanna start fresh :)
[AT&T Samsung Galaxy S 4 Android Development] trueking7:
If I want to try an AOSP rom, won't I need to choose format data and then type yes? But if I do this in TWRP, the rom will only boot once and then get stuck at the Samsung logo. So how is it possible to go from touchwiz rom to AOSP rom using TWRP on rogers i337m?

Sent from my sgh-337m running Omega v7 with Ktweaker kernel
[AT&T Samsung Galaxy S 4 Android Development] Gandalf:
no. just wipe System, Data (Factory Reset) , Cache, and Dalvik. this is posted in just about every single thread for just about every single ROM ever released.

Do yourself a favor, do a little research on using custom recovery, and how to install custom ROMs, before you do anything. Save yourself from a brick. You can never be too careful
[AT&T Samsung Galaxy S 4 Android Development] trueking7:
There is conflicting information out there. I'm not going to bother linking but thanks for answering my question....

PS is it even stated in the op that formatting data will lead to stuck on boot after initial boot?

Sent from my sgh-337m running Omega v7 with Ktweaker kernel
[AT&T Samsung Galaxy S 4 Android Development] Gandalf:
no, that's just a bug with TWRP right now, it'll be fixed soon.

formatting Data will erase the contents of your Internal SDCard, which is not required. you want to wipe the /data partition.

Wipe /system, /data (it's labeled as generally labeled as Wipe Data/Factory Reset) /cache, and /dalvik-cache

then you can switch between AOSP-based ROMs and TouchWiz ROMs without issues
[AT&T Samsung Galaxy S 4 Android Development] Aqua1ung:
Will flashing a ROM with TWRP Loki the new ROM? Or will I have to run LokiDoki after flashing?
[AT&T Samsung Galaxy S 4 Android Development] jroyalty7:
Run loki or flash a loki'd kernel
[AT&T Samsung Galaxy S 4 Android Development] Jonnyredcorn:
Is anyone else having issues with failed nandroid backups and restores? It's happened several times to me. I would be running Omega or Wicked ROM(both touchwiz) make a backup then restore my original stock backup to test something out. Then I will go to restore my nandroid of whatever ROM and it will fail even though the backup was successful. Or the restore will be successful but I will see some errors in the log and my restore won't be completely restored. I will have to go through setup again and only some apps will be restored.

Also if I want to format my 32GBP class 10 sdcard should I do it from within the touchwiz settings, TWRP recovery format extracts, or on my PC? Twice it's happened where when taking a photo it will out of no where default to device storage say it can't save to external. I then formatted the sdcard in touchwiz and copy my files back and it works fine.

Sent from my Galaxy S4
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
Two posts above yours?
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
Erase all .zip

Back in the Evo 4G (OG) days, when we had issues with doing a full wipe, with Amon Ra recovery, CWM, or even TWRP, we used to use a zip that erased all partitions, etc automatically. Does such a flashable zip exist for the i337 / S4 ?

Thanks.
[AT&T Samsung Galaxy S 4 Android Development] :
i thought i saw something on that but don't remember for sure

used it on my One S

also had a kernel wipe

all flashable zips

wow--i just caught a portion of the restore issue and said wth

then after more reading realized it was for formatting data which is not part of a normal wipe to change roms--relieved--:)
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
What exactly do you mean, wiping DATA is not part of the normal wipe for flashing a new ROM?

I thought that a full wipe was a full wipe? Why would we not want to wipe a previously used ROM's data?

I read there is a glitch in TWRP with respects to some yes or no question in a wipe option (not sure what the glitch really is because I haven't flashed ANY Roms yet, as I dont want to screw up my phone de-virginizing it).
[AT&T Samsung Galaxy S 4 Android Development] :
I said Format Data not wipe. Two separate options.

Sent From My 32gb Samsung Galaxy S4 Running Tapatalk 4 Beta
[AT&T Samsung Galaxy S 4 Android Development] Jonnyredcorn:
That is the post 2 posts above mine, and just to be sure I checked several other posts above mine as I did before I posted the question and don't see relevant information. What I see is people having issues over factory reset/format data & the format data option(selecting yes after selecting format data).

Factory reset/format data is similar to the format data/factory reset in CWM in that it doesn't format you Internal SDcard. Format Data in TWRP will format the internal SDcard and delete whatever ROM you have on your internal SDcard(I believe).

My question is are people having issues with Nandroid backup's that are successfully backing up but not successfully restoring.

I really want to try out this new Google Edition and Task's latest AOKP build's but I have Omega 7.0 set up perfectly and it has been running great I want to be confident that my backup won't be broken when I go to restore it.

I am running TWRP 2.5.0.2

I apologize if I just am not understanding how the second post above mine is relevant to my question. The only thing I can think of is that there are mentions of a bug in TWRP that could be causing this.

Is there a better a more reliable recovery option than TWRP for the AT&T model? I see ODHUS recovery and CWM and Philz options(which I believe are all CWM based and do auto-loki, but my StockROM backup won't be compatible with these new recovery's if I switch. However I would be willing to switch as if I ever needed to restore my stock backup I could just reinstall TWRP.
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
OMG....now I'm all confused...wow, not by you, but by all the stuff in general I'm reading....I mean, the fact that I hear that we all need the new modem that was in the at&t update....AND, then hearing we really can't flash the modem in any recovery alone presents a basis that maybe THAT is part of why we are having issues.

http://xdaforums.com/showthread.php?p=43267845#post43267845
[AT&T Samsung Galaxy S 4 Android Development] :
I posted this on another thread may clear things up for some folks--:)

Here is a post by TeamWin on wiping for Roms. Formatting Data is not part of "normal" wipe process. It wipes your internal sd.

http://teamw.in/whattowipe

These guys are far above me. But my preferred method is to "Wipe" System/Data/Both Caches. I actually do it twice. I know many say no need, but I do. I did this for many years on previous phones and never had issues. If on Nightlies or incremental updates did not wipe unless OP said to.
[AT&T Samsung Galaxy S 4 Android Development] force70:
So in other words just do a basic "full wipe with twrp" for now to avoid the boot looping issue? I just got my s4 a few hrs ago and glad I'm doing a little reading on it before I start messing with it.
[AT&T Samsung Galaxy S 4 Android Development] DuMKaSD:
Can someone please help me, I flashed a ROM, but forgot to flash Loki, when I reboot to recovery, TWRP is asking me for a password, log says "E:Failed to decrypt data" I'm stuck at work, with no PC, is there a default password?
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
TWRP
[AT&T Samsung Galaxy S 4 Android Development] cjkacz:
This happened to me the other day. I have been switching between backups of a tw rom and Google edition. I always factory reset before I restore but when attempting to restore to TW rom twrp said the factory reset failed. I then tried to restore and that failed as well. I realized that twrp was acting funny so I quick flashed the Google edition rom and let it boot up. I then went back into recovery and twrp worked just fine. I should mention that prior to starting all this I was attempting to install the TW camera into the Google edition rom and could not get the rom to boot up. I assumed this was why twrp was borked and why I decided to reflash Google edition. Not sure if any of this helps but it was just a similar experience
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
I would download the app called GOOMANAGER, and then install open recovery script (TWRP) again.

Let me know! :D
[AT&T Samsung Galaxy S 4 Android Development] Jonnyredcorn:
I want to try some of these GE rom's as well as task's latest releases to see if they can pull me away from touchwiz(can't believe I'm saying that as I've always ran task's ROM's on my galaxy devices but I honestly don't mind touchwiz on Omega ROM with 3mint customization's).

I've been faithful to TWRP for a long time and believe it to be the best recovery. However there are obviously issues with 2.5.0.2 on the AT&T gs4 so I just recently switched to Philz CWM touch which so far seems pretty awesome. The plus to it is that it can also restore TWRP backups. The main thing I'm worried about is my stockROM backup which I have backed up on my PC and is known to restore fine in TWRP. I just created a backup in Philz of my Omega ROM and am gonna check out some of these GE rom's. There are so many builds in the i9505 forum I don't know which one to choose. I'm weary of swtiching to AOSP as well because I hear ktoonez's AOSP kernel has some random rebooting issues. Philz touch has auto-loki so I suppose that means I can flash international modems as well.

I don't know my phone is just working so awesome as it is I don't wanna mess with it. I can only imagine how fast AOSP will run on this phone. I may just wait a while and wait to see what these dev's do with the GE firmware. I imagine down the road AOSP on this device is going to be amazing.
[AT&T Samsung Galaxy S 4 Android Development] Dees_Troy:
[RECOVERY] TWRP 2.6.0.0 touch recovery [2013-07-08]
[AT&T Samsung Galaxy S 4 Android Development] MegaGalan:
auto-loki ???????
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
It doesn't say it in the change log in op so probably not
[AT&T Samsung Galaxy S 4 Android Development] :
did you check out changelog
[AT&T Samsung Galaxy S 4 Android Development] stevehkim:
Does 2.6.0.0 fix the issue with flashing VR themes not flashing correctly?
[AT&T Samsung Galaxy S 4 Android Development] cjkacz:
Goo still says 2.5.0.2
[AT&T Samsung Galaxy S 4 Android Development] icedmayhem:
I was about to post the same

Sent from my Galaxy
[AT&T Samsung Galaxy S 4 Android Development] :
get the image from there site and SU from Terminal
[AT&T Samsung Galaxy S 4 Android Development] cjkacz:
Edit

Now shows latest recovery
[AT&T Samsung Galaxy S 4 Android Development] ex-28:
Wonder if this fixed restoring a backup after a full wipe
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
Through goomanager it tells me "no recoveries were found for your device" any idea why it would say that?

I'm on ATT i337.

Buildprop says:

ro.product.model=SAMSUNG-SGH-I337

ro.product.brand=samsung

ro.product.name=jflteatt

ro.product.device=jflte
[AT&T Samsung Galaxy S 4 Android Development] m0bstr:
does anyone have a zip file of the 2.5.0.2 update, the 2.6.0.0 update keeps freezing on me
[AT&T Samsung Galaxy S 4 Android Development] :
go to page 37
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
Same exact thing here.
[AT&T Samsung Galaxy S 4 Android Development] CPA Poke:
For anyone who is interested, here is a flashable zip of 2.6 (I haven't gotten a chance to use 2.6 yet, so flash it at your own risk):

http://www.mediafire.com/?3vdahe1ptxprzpz

Flash using any custom recovery.

---------- Post added at 06:18 PM ---------- Previous post was at 06:16 PM ----------

Here you go:

http://www.mediafire.com/?4519q4rgg34f77g

What kind of freezing issues? I haven't updated to 2.6 yet but I'll hold off if everyone is having issues with it.
[AT&T Samsung Galaxy S 4 Android Development] geoldr:
These are both LOKI'd right?
[AT&T Samsung Galaxy S 4 Android Development] devilsadidas:
has anyone used the fix permissions option under advanced? i wiped caches and then ran this and it soft bricked my phone. luckily it was easy to fix but still odd. just seeing if anyone else has had this issue??? this was not on the new version.
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
Any chance anyone on touchwiz rom ( stock or not) who sucesfully updated to latest can paste in device info from buildprop?

Thanks.
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
Perfect :good: Thank you for this because for some reason mine want update through goomanager. But after reading the freezing issue kinda skeptical.
[AT&T Samsung Galaxy S 4 Android Development] Ker~Man:
Very odd, indeed. Never happened to me on any version... :confused:
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
Yes, I've used this option couple times. No issues at all here.
[AT&T Samsung Galaxy S 4 Android Development] Xetalx:
Goo manager downloads 2.6.0.0 here for my JFLTECAN. It does flash it corectly but when i go in recovery it still shows 2.5.0.2...

To bad for me i didnt notice and did a FORMAT DATA....... Soft bricked my phone.... Had to odin the original .tar and do a factory reset from the stock recovery to unbrick it...

So ppl make sure you confirm the version before loosing one hour ganing stress for nothing.
[AT&T Samsung Galaxy S 4 Android Development] CPA Poke:
They aren't ROM's, they don't need to be Loki'd :)

To answer your question though, these are the AT&T-variant recovery images. If you already have a custom recovery from which to flash them, then you've already implemented the loki patch - and you don't need to do anything else but flash the zip. You're getting confused with ROMs/kernels, which need to be loki-patched in order to work with your existing recovery.

---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------

That sucks man. I'm always so worried that I'll accidentally do that, that I always use the advanced wipe option and choose each partition manually. Like you said, just not worth the time/effort involved after wiping the internal SD.
[AT&T Samsung Galaxy S 4 Android Development] Xetalx:
The TAR image on TWRP is accurate though. Since i ****ed up my night already i will do the FORMAT DATA once more...

I confirm the fix. FORMAT DATA now works with version 2.6.0.0 :D

***EDIT*** FORMAT DATA still makes phone behave. Do not use it for now.
[AT&T Samsung Galaxy S 4 Android Development] geoldr:
Oh, I thought since our bootloader is still locked, the recoveries also need to be LOKI'd to use the exploit.
[AT&T Samsung Galaxy S 4 Android Development] :
twrp is already loki'd it just doesn't auto loki kernels that aren't already loki'd by Dev/OP

So, with twrp you would need to flash loki-doki after flashing a rom with a non-loki'd kernel or just a non-loki'd kernel by itself

most att roms are good to go--it will say in OP
[AT&T Samsung Galaxy S 4 Android Development] :
Installed latest from goo mgr. On my third boot into recovery phone hung on Team Win screen. Pulled battery and tired a couple reboots to no avail. Finally it booted into recovery. I cleared caches and fixed permissions. Will try again. May go back to 2.5 0 2. Never had TWRP do that before.

Sent From My 32gb Samsung Galaxy S4 Running Tapatalk 4 Beta
[AT&T Samsung Galaxy S 4 Android Development] zolom:
S4 hangs after a short while

Installed 2.6 TWRP, i9505 rebooted OK, then after few seconds it hanged. Dir reinstall TWRP 2.5 (which was working OK) with same results. Now I try to restore my nandroid.
[AT&T Samsung Galaxy S 4 Android Development] :
Where did it hang. On OS or TWRP screen?

Sent From My 32gb Samsung Galaxy S4 Running Tapatalk 4 Beta
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
I installed v2.6 on first boot to recovery it hung on teamwin screen so while on that screen did a reboot to recovery by vol up-power-home button. Then booted to recovery fine. So far so good each time after that. Will report back if any more hangups
[AT&T Samsung Galaxy S 4 Android Development] :
same here, but took several reboots and even a battery pull before twrp rebooted into recovery.
[AT&T Samsung Galaxy S 4 Android Development] CPA Poke:
Had the exact same problem re: the hanging on the Teamwin screen...like everyone else I was able to get into recovery eventually using battery pulls, but it just got too annoying for me and I just flashed back to 2.5.2.0.