yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] PeterGuru:
Brief scare ...

Well, I up-dated TWRP to v2.5.0.3 a few minutes ago through Goo Manager, and when I tried to boot into recovery, I got to the TEAMWIN screen, and that was it. It stayed on that screen for at least two minutes before I decided to press and hold the power button to reboot. It went right back into recovery. This time, though, it FINALLY got to the recovery options, but it stayed on that TEAMWIN screen for at least 30 seconds, which is much longer than usual.

I then did a Nandroid and rebooted. All looks okay so far. I will try and reboot into recovery again to see if that long delay is still there. Let you know shortly.

Peter

Addendum: I did another reboot into recovery, and it stayed on the TEAMWIN screen for 14 seconds, which is much closer to normal. Phew! Trying a restore now. Let you know.

Addendum 2: The time is still WAY off. It varies, but now it's about 3 hours ahead of what it should be. Depending on the reboot, it can be anywhere from 1-4 hours ahead of the real time. WHY is this such a problem to fix? It's been like this since the first version, whereas, the time is fine on TWRP recoveries for MANY other devices.

Addendum 3: Wiping takes much longer than usual. Performing a Factory Reset swipe usually takes about 5 seconds. Now it takes almost 20. Edit: Subsequent Factory Reset swipes now take about 9 seconds. Much better!

Addendum 4: Restoring my previous Nandroid worked. The time it took was comparable to other restores.

Addendum 5: WOOHOO! 1000 Thanks! Thank you to our terrific xda-membership. You have no idea how helpful you have all been over the last several years. Thank you, again.

Addendum 6: I restored an earlier Nandroid, and then re-installed TWRP v2.5.0.3. This time, however, everything went smoothly. When I rebooted into recovery, the recovery options appeared only 9 seconds after the TEAMWIN screen. Perhaps my earlier attempt simply had a small glitch.
[AT&T Samsung Galaxy S 4 Android Development] apascual89:
[MENTION=899563]PeterGuru[/MENTION] Thanks for your response, always thorough! This update is definitely slow on pretty much everything. But works as intended
[AT&T Samsung Galaxy S 4 Android Development] PeterGuru:
True ...

True!

Peter
[AT&T Samsung Galaxy S 4 Android Development] mg2195:
Is auto Loki included? I remember reading that shabby recently got Dees all the required files and what not a day or two ago...ill see if I can find the link

From 5/30:
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
Is the twrp site down??...
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
Works for me. I just downloaded 2.5.0.3.

http://www.teamw.in/project/twrp2/174

Btw, 2.5.0.3 is verrrrry slow for me also. At least the first time I booted into it. Still waiting for it to eventually load up.

Edit. It took a couple minutes, but it finally loaded into the menu on it's own. I didn't have to force on/off.

Edit. It's slow on every reboot until I plug in the microUSB cable. Then it suddenly speeds up and goes into the menu.
[AT&T Samsung Galaxy S 4 Android Development] _eroz:
Can someone create a .zip? Or point me to how I can do it myself. I'm looking to flash back to twrp but since I'm using a T-Mobile Rom, goo manager wants to install the tmo version.
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
There is no zip yet. Just install the .img. The download and instructions are on this page:

http://www.teamw.in/project/twrp2/174

Copy the .img to the root of your internal SD card.

Go to a command prompt (using administrative privs).

Navigate to a location that has ADB.

adb devices

adb shell

su

dd if=/sdcard/openrecovery-twrp-2.5.0.3-jflteatt.img of=/dev/block/mmcblk0p21
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Try changing your build prop to show AT&T and then change it back to how it is after installing TWRP.
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
I wouldn't flash 2.5.0.3 though. It's nothing but issues IMO. I'm going back to 2.5.0.2.

It hangs when booting into it sometimes.

It hangs when simply wiping cache & dalvik.

It hangs here.

It hangs there.

No bueno. Some really flakey stuff going on here. Uninstall it if you have it. I would not be surprised to see a hard brick from 2.5.0.3.
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
I just went back to 2.5.0.2. So I did a screenshot of how I did this in case anyone needs it. Note that I renamed the file to "recovery.img".

I'm in the "motochopper" directory because that's where I have ADB at. It's what I originally used to root my phone.
[AT&T Samsung Galaxy S 4 Android Development] cjkacz:
Luckily the latest version has been fine for me . After reading all this I got scared but so far no issues(knocks wood)
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
Is anyone experiencing issues wit goo??.. Been trying to get twrp but won't dl.. How else can I flash recovery??..
[AT&T Samsung Galaxy S 4 Android Development] joeybear23:
Have you made any changes to your build.prop?

goo needs your device parameters to be stock
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
No only thing I did was root my phone after it booted up I dl goo granted su permission and I can't dl anything not even a rom
[AT&T Samsung Galaxy S 4 Android Development] joeybear23:
I don't know i there are any ROMs for our phone registered with GooManager.

I only use it to download TWRP recovery.

When you open Goo, click on your phone's menu button and choose the "Install OpenRecoveryScript" option

This will download and install the recovery for you.

Once you have that, you can download ROMs and Kernels, etc from the developer's links (not inside GooManager, but in threads on XDA).

When you find a ROM or Kernel you want to apply (make absolutely sure of compatibility) then download it onto your device,and do the following:

Open GooManager, and choose the Reboot Recovery option. (This will shutdown your phone and boot up into recovery mode [kind of like BIOS for a PC])

The you choose the install option and browse to the ROM or Kernel you downloaded.

Hope this helps.
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
Yeah thanx man i tried again this morning and now I have twrp.. Carbon rom is on goo.. Still haven't flashed a rom yet been trying to read up..
[AT&T Samsung Galaxy S 4 Android Development] bigal1542:
So I searched through here and didn't find it, but I just came from the SGS3 and preload was not an option for the advanced wipe. Should I be doing that for ROM flashing? I do the top four to do a clean wipe.

Thanks!
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
+1 also would like to know which options should b checked for backups..
[AT&T Samsung Galaxy S 4 Android Development] h3r3tic:
I haven't touched preload. Just been sticking to wiping system/dalvik/cache and data before installs. No issues. For backups data/system/boot are the only ones needed.

*a lot of stupid people with smart phones*
[AT&T Samsung Galaxy S 4 Android Development] DuMKaSD:
Having fun with CM, one thing I noticed is during updates, when I flash, TWRP hangs, I have to restart my phone, and boot back into recovery. Afterwards everything updates and goes smooth, any ideas? I tried reinstalling TWRP. same thing happens with cold boot, I have to start TWRP 2 times for it to work, anyone with same issues?
[AT&T Samsung Galaxy S 4 Android Development] trparky:
Is TWRP better than say... OUDHS's Recovery? Any differences?
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
You need to read both threads to see the differences, they are clearly listed. And asking which one is "better" is all personal preference. It's the same as saying one ROM is better than another...and should not happen.
[AT&T Samsung Galaxy S 4 Android Development] trparky:
CWM seems to have some kind of auto-loki in it. Does this version of TWRP do the same?
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Not at this time. There is a script called Loki-Doki (you can search for it) that you can use to flash in TWRP recovery directly after you flash a non-lokied kernel or ROM that is supposed to loki the kernel or ROM for you. I have not tried it personally.
[AT&T Samsung Galaxy S 4 Android Development] CPA Poke:
Nope.

---------- Post added at 06:59 PM ---------- Previous post was at 06:42 PM ----------

For everyone screaming for a flashable zip, here you go:

TWRP 2.5.0.2

TWRP 2.5.0.3
[AT&T Samsung Galaxy S 4 Android Development] sloanster:
So... Does your 2.5.0.3 version still report 2.5.0.2? (as looking on the recovery screen)
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
Is it the norm now for nandroids to b over 2 gb??.. I tried cwm and it was 3.9 gb and TWRP does 2.3 thts crazy lol

Edit also it took like 30 mins to make a nandroid
[AT&T Samsung Galaxy S 4 Android Development] sloanster:
Does any Have?

Hello All!

Does anyone have in their arsnal odin flashable TWRP 2.5.0.2 for sch I-337?

Thanks,
[AT&T Samsung Galaxy S 4 Android Development] sholsten:
Does either one of these add Loki to non-Loki Roms'
[AT&T Samsung Galaxy S 4 Android Development] sloanster:
Thanks man you twrp 3 version works... see a few post back...
[AT&T Samsung Galaxy S 4 Android Development] bvm1228:
Does anyone know how to install TWRP by not using Goo Manager as goo.im is down so it cant be installed? On the website it says:

Download the above file. Using adb shell or terminal emulator:

su

dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p21

Make certain that you get this command right. Typing the wrong number could result in a brick!

Do I just type in exactly what this says number included? I just really dont want to brick my phone.
[AT&T Samsung Galaxy S 4 Android Development] _eroz:
I asked the same question earlier in the thread here is the response I got and yes it worked.

or you can try flashing the zip files. I tried those as well and they work.
[AT&T Samsung Galaxy S 4 Android Development] bvm1228:
Can I just used the Android Terminal as I have no experience with ADB
[AT&T Samsung Galaxy S 4 Android Development] _eroz:
Yeah just use steps 3 and 4. Make sure the name of the recovery file matches. Or you can use the zip files I quoted as well.
[AT&T Samsung Galaxy S 4 Android Development] bvm1228:
With the .zip can I just flash it like I would with a custom rom?
[AT&T Samsung Galaxy S 4 Android Development] _eroz:
Yes.
[AT&T Samsung Galaxy S 4 Android Development] bvm1228:
The reason I wanted to do this was because I wanted to restore from a backup that I had moved from my phone to my computer and then deleted from the phone. But the recovery wasnt seeing the backed up file so I thought flashing the newest version of the recovery would fix that but it didnt. If someone knows how I can get it so that TWRP will recover my backup I would appreciate it.
[AT&T Samsung Galaxy S 4 Android Development] _eroz:
Did you use twrp initially to make the back up?
[AT&T Samsung Galaxy S 4 Android Development] bvm1228:
Yes
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
Did it take 30 mins?.. Was it over 2gb??
[AT&T Samsung Galaxy S 4 Android Development] bvm1228:
No. It took like 5 minutes and was like 500mb I think
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
Which version did you use??..
[AT&T Samsung Galaxy S 4 Android Development] bvm1228:
I used TWRP version 2.5.0.2
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
Thanx I'll try tht I'm on TWRP 2.5.0.3 now
[AT&T Samsung Galaxy S 4 Android Development] _eroz:
When you made your back up, what boxes did you check?
[AT&T Samsung Galaxy S 4 Android Development] Mike:
1) I was on mobile and thus can't view signatures

2) If you brick the device there is NO need to worry about resetting a flash counter bc you can't even boot into the OS

3) You guys are talking about flashing files onto your device that, at times, may be untested and can result in bricks. There is always a chance of a brick when flashing and it isn't a worry as you can just lie your way into a new one

4) There are many reasons to send in for repair that are hardware related in which the device is still functional and thus you need to return to stock and remove evidence of rooting / custom ROMs as that voids your warranty REMEMBER. These issues include screen lifting, defective audio jack, issue with camera, stuck power button, etc.

5) This is a development thread on TWRP and none of this discussion relates. Message me via pm if you wish to continue the discussion, but lets not clog the thread any more then it already has been with meaningless back and forth on an unrelated topic.
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Though I am hoping this thread will be cleaned by a mod at some point, I must point out that doing "anything" to the kernel or counter or OS on a phone invalidated the TOS and therefore constitutes fraud if you try to return or replace it so splitting hairs isn't necessary. If it all bothers you that bad than XDA is NOT the place to be. Picking and choosing your sin doesn't make you less of a sinner. Personally, none of it bothers me, I am all for open development. So someone that condones violating TOS, yet condemns others for doing so is just wrong.

Back to TWRP...I hope.
[AT&T Samsung Galaxy S 4 Android Development] lessthanzach:
Thank you for the list and invitation but I'm not much for bickering.

That being said, Verizon needs to launch their S4 so I can flash this bad boy. Thanks to the OP for this, I've always preferred TWRP.
[AT&T Samsung Galaxy S 4 Android Development] DvTonder:
Its been said before - works perfectly on Bell Canada S4 :good:

Now to get CyanogenMod working on it ...
[AT&T Samsung Galaxy S 4 Android Development] Thermalwolf:
You can set your device status back to Official and still remain rooted by installing SuperSU, update your SU binaries and uninstall the old SuperUser app. Reboot the device twice and the unlock boot icon should go back to the standard GS4 bootscreen. Your device status will also be back to Official but you will still be rooted. OTA should then be installable but guaranteed it will take away root.
[AT&T Samsung Galaxy S 4 Android Development] mickliq:
I must admit I had to read the review a second time to catch the bootloader comment before I posted it here originally! Excited to see that people have now confirmed that through TWRP install :D. Custom ROM's please so we can rid ourselves of some of the TW bloat and/or AOSP based ROM's.
[AT&T Samsung Galaxy S 4 Android Development] KryptosXLayer2:
I'll just repeat what I said on the Sprint forum for this exact post:

gah..... CAN'T. WAIT. to be able to use this on my AT&T S4 once it's unlocked! Great work, love using it on all my other devices.

Soon............. :good: :good:
[AT&T Samsung Galaxy S 4 Android Development] Kevin36:
i recently installed twrp on an canadian s4 my bootloader status says write protection enabled. Yet I installed twrp and booted into it and I am currently making a backup of stock rom and efs.
[AT&T Samsung Galaxy S 4 Android Development] KCtheGREAT:
Thank you for confirmation Peter! Great to know Canadian sgs4's already have an unlocked bootloader
[AT&T Samsung Galaxy S 4 Android Development] sk8trix:
Im waiting patiently for the bootloader unlock........but it feels like an eternity OMG flashing my GS3 for now and Nexus 4 for the time being Im so mad att version is locked argggg
[AT&T Samsung Galaxy S 4 Android Development] SysAdmNj:
This thread is such a tease.

I havent been teased this bad since.... n/a
[AT&T Samsung Galaxy S 4 Android Development] Cusa:
Lol, I was going to post the same thing.
[AT&T Samsung Galaxy S 4 Android Development] David Dee:
You aren't really missing that much, there won't be a hell of a lot to flash until at&t comes on board with an unlocked bootloader.
[AT&T Samsung Galaxy S 4 Android Development] DespairFactor:
Does the Goo Manager method reboot the device?
[AT&T Samsung Galaxy S 4 Android Development] SysAdmNj:
Yea but by seeing this thread title I thought it got unlocked today. Wishful thinking.
[AT&T Samsung Galaxy S 4 Android Development] Zer0_:
Works great with the my Koodo S4 (Canadian)! :)
[AT&T Samsung Galaxy S 4 Android Development] Cusa:
Highly doubt that the greedy att will unlock the bootloader.
[AT&T Samsung Galaxy S 4 Android Development] David Dee:
They definitely won't. I meant when the bootloader is unlocked by someone else.
[AT&T Samsung Galaxy S 4 Android Development] gdevil:
If I want to know whether my device is locked or not I must flash a custom recovery in order to see what happens, what if it is locked? It wouldn't boot, right?

In that case, Can I restore to factory with Kies? (I have check it and it does recognise my device and says it can flash a backup rom.

Regards

Enviado desde mi GT-I9300 usando Tapatalk 2
[AT&T Samsung Galaxy S 4 Android Development] prking07:
Also want to know what will happen 8f I flash this to a locked bootloader. Will it not boot, just give error, what? I have a i337m and desperately want to know if my bootloader is locked or not
[AT&T Samsung Galaxy S 4 Android Development] bvm1228:
I had Boot, System, and Data checked
[AT&T Samsung Galaxy S 4 Android Development] _eroz:
How many items are in your back up folder? I checked the same boxes. I have 9 items in my back up folder. My back up folder is 2.5GB.
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
Boot, system, data, cache
[AT&T Samsung Galaxy S 4 Android Development] bvm1228:
I have 7
[AT&T Samsung Galaxy S 4 Android Development] vance74:
The new TWRP update is working great on my sgh i337m
[AT&T Samsung Galaxy S 4 Android Development] PeterGuru:
TWRP v2.5.0.3 removed ...

It looks like TWRP version 2.5.0.3 has been removed from the TWRP web site. It's also no longer available through Goo Manager.

I have to admit, I've been having a few problems with 2.5.0.3, especially the fact that it often "hangs" when attempting to boot into recovery, and/or attempting to flash an up-date for CM10.1.

... going back to v2.5.0.2.

Peter
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
Change the name of the file to recovery.img and follow the steps in my screenshot.

ADB is required for these steps btw.

And this same information could have been found if you searched the thread before you posted.

Post #345.
[AT&T Samsung Galaxy S 4 Android Development] mg2195:
Considering our stock Rom is about 2gb in size...and depending which options you pick (so with added user data and what not for apps) I would say yes its normal to get nandroids over 2gb
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
Thanx I wasn't aware tht it would b tht size.. On the s3 they're abt 1.6 gb.. I noticed also to make a nandroid takes 20 mins on cwr it takes 10.. Honestly tho since I first ran TWRP I've loved it..
[AT&T Samsung Galaxy S 4 Android Development] geoldr:
I am using 2.5.0.2 and my backup size is 4gb. Only data system and boot is checked.

Also can't figure out how to wipe internal storage
[AT&T Samsung Galaxy S 4 Android Development] baddaybeav:
Encrypted storage

has anyone gotten data to mount with encrypted storage?

It comes up asking for the password, I enter it, logs show it decrypts, then says it failed to mount /data

flashing still works if I move the zip file to the sd card and install from there, just an annoyance.
[AT&T Samsung Galaxy S 4 Android Development] CPA Poke:
Nope. Either use Penguin's CWM with auto-loki or just flash the loki-doki.zip (found here: https://www.dropbox.com/s/vhh5pwd81x0ppek/loki-doki.zip) after flashing a non-AT&T ROM or kernel.

The second option (with loki-doki) is what I use...I'm just too attached to the TWRP UI, and so far it's worked on everything I've tried.
[AT&T Samsung Galaxy S 4 Android Development] rfb813:
I second the use of loki doki until TWRP gets the auto loki feature. I too prefer to use TWRP
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
I'm wondering y the op states it is loki modified
[AT&T Samsung Galaxy S 4 Android Development] boostmx:
I think it's referring to the recovery itself needing to be loki'd in order to be able to run on the device.
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
Yes, this is right. The recovery itself is loki'd to be able to run on the device but it doesn't auto loki things you flash on the device. Love TWRP so hopefully it will soon.
[AT&T Samsung Galaxy S 4 Android Development] orlandoxpolice:
Just so I have everything straight, you flash the ROM via twrp, and then before rebooting, you flash the loki-doki zip?
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
Correct n when n doubt do it anyway
[AT&T Samsung Galaxy S 4 Android Development] coffeehandle:
Is goo been down for a couple of days?
[AT&T Samsung Galaxy S 4 Android Development] JJ5150:
Odin Loki TWRP .tar

Can anyone make a .tar Odin package for the TWRP recovery loki'd for the S4? I'm bricked with no way to reinstall TWRP at the moment. HELP!!!
[AT&T Samsung Galaxy S 4 Android Development] coffeehandle:
You coukf do shabby penguins recivery fir the time being
[AT&T Samsung Galaxy S 4 Android Development] jeboo:
You can only ODIN signed images (stock).
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
I'm currently using OUDHS Recovery, and wanted to switch back over to TWRP.

I installed goomanager, and ran install OpenRecoveryScript. it took some time, but then i got a toast message saying recovery is installed.

Great - reboot into recovery, but for some reason OUDHS Recovery is still there.

Any idea's how to switch back to TWRP in this instance? anyone got a flashable zip with recovery .2 possibly, that would work?
[AT&T Samsung Galaxy S 4 Android Development] _eroz:
Do a search it's here in this thread, I don't remember the post number or page. I'm on my phone and searching sucks on the app.
[AT&T Samsung Galaxy S 4 Android Development] orlandoxpolice:
The one click root recovery that adamoutler made should work in this instance.
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
Thanks guys... I tried a few more times through goo and finally after 3rd time it took. Weird'
[AT&T Samsung Galaxy S 4 Android Development] turilo:
Seems the odd time if I choose wipe/advanced and only choose to wipe caches it will put me in a bootloop :confused: anyone else?
[AT&T Samsung Galaxy S 4 Android Development] TBayTom:
Yes! it boot loops for me now and asks me for a password... I have to format the internal sd card in order to restore a nandroid.... anyone else having this issue??
[AT&T Samsung Galaxy S 4 Android Development] azz72:
Hey all

I was wondering how can I change the time on this? And also is there a way to change the color or the home screen?

I tried looking through the posts but didn't see anything unless I'm blind..

OK I got the time to change...
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
AUTO LOKI

Any word on TWRP having an update to support auto-LOKI'ing ?
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
Is it just me...or is there not a direct link to just download TWRP by itself???
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
Besides what it says in the OP to use goo manager?
[AT&T Samsung Galaxy S 4 Android Development] _eroz:
That is because you can just go to the Team win recovery project website.
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
I went to their website....directs you to GOOManager...

I dont see a .zip file at all.

I wish it would support exFAT like Phil's CWM variant (their having some issues resolved with it).
[AT&T Samsung Galaxy S 4 Android Development] _eroz:
And it gives you a .img file that you can use in adb or in terminal emulator.
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
Thanks. My trying to play catch up has caught up with me...read read read is the name of the game here on xda.

I found out that TWRP does in fact support exFAT so Im good with staying with it. I flirted with the idea of getting OUHDUS (sorry typo) recovery but it doesnt support exFAT i believe. So I will keep TWRP, use my 64gb HSXC card, and loki doki.........okie dokie!! LOL:good: