yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] gadget!:
I would use Goo Manager if you want 2.6.

Myself and others are having issues with 2.6 hanging at the TWRP screen.

There is a link in this thread for 2.5.0.2, that is what I use and you just flash it in recovery.

I have never heard of anyone in this thread that has bricked thier phone using either of the above methods.

I gave up on the date :)

In the backup screen it lets you set your backup name, I just name mine what I want it to be before doing a backup.

Example: beans-07.31.13

Makes it real easy to see what is what when restoring.
[Verizon Samsung Galaxy S 4] sevron:
So would I just flash it like I did when first installing it to update it?
[Verizon Samsung Galaxy S 4] idelgado782:
Got my S4 yesterday. Still had the original firmware on there, i'm rooted and have twrp installed! Thanks so much!
[Verizon Samsung Galaxy S 4] HowardZ:
I got tired of booting into recovery hanging or freezin

I gave up.

Went back to the earlier version of TWRP
[Verizon Samsung Galaxy S 4] gadget!:
You, me, and a lot of others.

I wish they would fix it, I liked some of the new features on 2.6

Sent from a Galaxy S4... Far far away
[Verizon Samsung Galaxy S 4] dmarden:
Did anyone actually report it?

Edit: I'm not personally having the problem.
[Verizon Samsung Galaxy S 4] 00negative:
Change the time zone to one you don't really want and apply it then switch back to the one you actually want and set it and see if that does it
[Verizon Samsung Galaxy S 4] xMopx:
Is this working on ME7?
[Verizon Samsung Galaxy S 4] hlxanthus:
Nope, can't flash recoveries on it until a fix is found.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] xMopx:
Gotcha, thanks.
[Verizon Samsung Galaxy S 4] JamesPumaEnjoi:
is it just me or is 2.5.0.2 much more stable than 2.6.....with 2.6 it will take a very long time to boot into recovery and it will take a VERY long time to wipe dalvik and cache.....on 2.5.0.2 this is not the case.....

EDIT

as i look a few pages back im glad to see im not the only one having problems with 2.6 because I swear only about half the time it would fix permissions and wipe cache and dalvik....I guess Ill downgrade to 2.5.0.2
[Verizon Samsung Galaxy S 4] brizey:
2.5.0.2 is stable. It's a recovery, not a game.

Still rooting for 4ext, though.
[Verizon Samsung Galaxy S 4] JamesPumaEnjoi:
I dont know what you mean by "It's a recovery, not a game." but ok...Maybe trying to be funny/sarcastic? I dont know what you're talking about but if you look at the last 3 pages everyone is having problems with 2.6.....thanks for the "help" though buddy
[Verizon Samsung Galaxy S 4] brizey:
Just echoing your point that stability is what matters...more than having the latest features. 2.5.0.2 is stable for most folks.
[Verizon Samsung Galaxy S 4] BoostinBen:
Not real sure what's going on. I did this with Goo, rebooted phone, and it basically stays in the ODIN mode with the little green Android guy and says "Downloading..." but it stays there forever. I did a few things and came back an hour later and it was still at the green Android guy saying "Downloading..." Anyone have any ideas on what I can do to at least get into something on the phone?
[Verizon Samsung Galaxy S 4] shawnten:
i cant get goomanager to install this recovery. everytime i do it and go into recovery i still have cwm
[Verizon Samsung Galaxy S 4] BoostinBen:
Got my problem fixed!
[Verizon Samsung Galaxy S 4] andybones:
You did this?

Goomanager

Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.

you can also download the actual .img and do this:

Using adb shell or terminal emulator:

su

adb push recoveryfilename.img /sdcard

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

Why don't you share it with us encase someone else runs into the same issue.
[Verizon Samsung Galaxy S 4] ffd173:
Hi. I could use a little quick help.

I installed twrp through goomanager and when i tried to boot into recovery, i kept getting the download screen. So i tried to boot into recovery through the option in goomanager.

Every time i try and boot the phone now, i go to the download screen. I can't get a normal boot.

How do i fix this???

I am rooted on the latest stock rom.

Thanks in advance!!
[Verizon Samsung Galaxy S 4] gadget!:
If you are on ME7 (the update) you won't get into a custom recovery.

Sent from a Galaxy S4... Far far away.
[Verizon Samsung Galaxy S 4] ffd173:
Thanks, but that doesn't help with my situation. I keep rebooting into download mode and i can't get a normal boot.

I need to fix that.
[Verizon Samsung Galaxy S 4] gadget!:
Sorry, I misread your post, I thought you couldn't boot into custom recovery.

If I'm understanding you right, you are on ME7, the factory update.

If you are on the factory update to ME7, boot into download (sounds like that won't be a problem).

Plug the phone into you pc and run the Verizon update utility and select "repair"

You will have to root again but it should get you going again.

Sent from a Galaxy S4... Far far away.
[Verizon Samsung Galaxy S 4] ffd173:
You were right. I couldn't boot into custom recovery. But it was my not being able to boot at all that I was trying to fix. And I am on me7, rooted.

Thanks gadget. I managed to get myself out of the loop. I did a battery pull and then powered up holding the vol down key and power. I got to a screen that talked about installing an alternate os. Never saw that before. But it gives you an option to continue to load an os or to boot normally. I chose to boot normally and I'm good. Bored right up. No problem.

Now, how do I load the original recovery back so that I have one?

Thanks again for the help!
[Verizon Samsung Galaxy S 4] akne:
Am I able to flash this if I am not loki'd on my phone?
[Verizon Samsung Galaxy S 4] Travisdroidx2:
No, to use TWRP your device must be on the MDK build and not ME7 and also you must root and unlock bootloader first with the loki method. Then you can install TWRP.
[Verizon Samsung Galaxy S 4] akne:
I already have TWRP on my phone but like everyone else I am having the same problem. I am rooted and everything but i used the motochopper one and I didn't do any loki unless i am without me knowing. I am trying to flash back to 2.5 and i was wondering if i am able to do it if im not loki'd
[Verizon Samsung Galaxy S 4] Travisdroidx2:
If you already have TWRP installed then you had to unlock the bootloader. I am guessing you are using 2.6 and now trying to downgrade to 2.5.0.2? But like I said if you currently have TWRP installed then you already unlocked your bootloader and should be able to flash the 2.5.0.2 with no issues.
[Verizon Samsung Galaxy S 4] akne:
Thanks for helping out. I just wanted to make sure before I brick my phone :)

do you also know if there are anyway I can find out if I am Loki'd or not. Or do you just automatically assume I am because I have a recovery?
[Verizon Samsung Galaxy S 4] Travisdroidx2:
Do you remember the process you used to root and unlock your phone? The only way to get a custom recovery installed is if you already did that.

Steps were:

1) Use odin to flash the unsecured kernel

2) Use motochopper to root

3) Use odin to flash the stock (Loki) kernel

If you did not do this you would not be able to install TWRP in the first place. And since you said you already have TWRP on your device then you must have taken these steps.

Besides if you ever brick or screw up your recovery as long as you can get into download mode you can always odin back to stock and do the process over again with a clean start.
[Verizon Samsung Galaxy S 4] akne:
nope this does not work. im assuming cuz im not loki'd like i feared. The TRWP splash page doesnt even show up. It stuck at the custom unlock page with the blue words recovery rebooting on the top left.
[Verizon Samsung Galaxy S 4] Travisdroidx2:
What method to get into recovery are you using? Also you are on the mdk build and not me7 correct?
[Verizon Samsung Galaxy S 4] akne:
im actually on MDL lol
[Verizon Samsung Galaxy S 4] Travisdroidx2:
So if you are not on Verizon why are you posting in the verizon thread? I would recommend posting in the correct carrier thread.
[Verizon Samsung Galaxy S 4] michaelg117:
I've read somewhere that Loki modified recoveries don't work correctly on me7. Is this true..?

Sent from Navi
[Verizon Samsung Galaxy S 4] hlxanthus:
That is true, no way to flash a custom recovery yet on the me7 update.
[Verizon Samsung Galaxy S 4] michaelg117:
Could I possibly root then flash mdk in Odin..?

Sent from Navi
[Verizon Samsung Galaxy S 4] hlxanthus:
Again, no. There is no way yet to roll back to the mdk rom. If you are on me7 it is just waiting for either a recovery workaround, bootloader unlock, or a method to roll back to the previous mdk rom
[Verizon Samsung Galaxy S 4] jova33:
I've been using TWRP 2.6.0.0 and have been having it hang at the team win screen many many times. Is 2.5.0.2 better? And any way to flash without adb?
[Verizon Samsung Galaxy S 4] Zer0r:
Yes, 2.5.0.2 is much more stable. I have also rolled back. Seach through this thread - there are flashable zip-files for flashing recovery from recovery (yeah, funny thing, true. But it's working).
[Verizon Samsung Galaxy S 4] hlxanthus:
Here is a v2.5.0.2 that is flashable via recovery

Download - twrp-2.5.0.2_jfltevzn.zip
[Verizon Samsung Galaxy S 4] jova33:
Tango Mike!
[Verizon Samsung Galaxy S 4] StifflerServices:
I'm confused, cab someone please verify how to revert back to 2.5.0.2 from 2.6. Do we just download the 2.5 file and then flash it in the 2.6 twrp recovery? And how can I make my backups compression smaller. 2.5 +gb seems double what cwm was doing. .. Thank u in advance
[Verizon Samsung Galaxy S 4] jova33:
Just flash. Worked for me.

Isn't there an option to compress backup?
[Verizon Samsung Galaxy S 4] royredman:
Hey, every once and A while, when I boot into TWRP, it sticks on the TWRP splash screen. Is this common? If so, how do I fix this?
[Verizon Samsung Galaxy S 4] what be up:
are you on version 2.6.0.0?
[Verizon Samsung Galaxy S 4] an21281:
Had the same thing happen on 2.6. Just reflashed 2.5.0.2 back and it's fine ... On 4.3 roms 2.5.0.2 was giving me problems... After flashing it would boot fine, but after that my phone would get stuck on the Samsung splash screen permanently. Could not run any 4.3 roms, Only fix was to use different recovery.
[Verizon Samsung Galaxy S 4] HowardZ:
I had intermittent booting getting stuck on the Samsung splash screen. Going to the 2.5.0.2 TWRP eliminated this problem.

I noticed the problem coming back again once in a while, so I again flashed 2.5.0.2 TWRP again and the problem went away.

I wonder if I will need to reflash TWRP every time I flash a new nightly version of cyanogenmod?
[Verizon Samsung Galaxy S 4] silverfang77:
Does installing OpenRecovery wipe the current OS installation on my phone? Sorry for the newbish question, but read I needed this installed in order to get the patched Google Wallet to work on my Galaxy S4.
[Verizon Samsung Galaxy S 4] jova33:
Are you on ME7 software version? If so, then you can not install this.
[Verizon Samsung Galaxy S 4] silverfang77:
Yes. I am. I'll just uninstall it.

Tappin' and talkin' with Tapatalk.
[Verizon Samsung Galaxy S 4] bunklung:
Is there a way to install this recovery directly in Odin without rooting your phone?

I don't want to root my phone, I just want to run a custom recovery to stop the OTA update from applying. I have had a few scary moments when I accidentally hit install now and got stock in a recovery loop. Odin was the only thing that saved me.

I am on MDK and would like to stay that way as stock unrooted.
[Verizon Samsung Galaxy S 4] jova33:
Root, remove/freeze the updater app, unroot.

Edit: But.... if you're not running any custom ROMs, don't need/want root, or don't plan on using root, why not update?
[Verizon Samsung Galaxy S 4] bunklung:
I want to run custom ROMS and root later. If I update with the OTA file I can't (and maybe never) run a custom ROM.

I used the root method and I was able to debloat the SDM/FOTA apks and delete the OTA file.

I also installed a custom recovery and unrooted.

All is well thanks.
[Verizon Samsung Galaxy S 4] vaeevictiss:
Awe come on! Why couldn't I get a time machine phone!?

Sent from my SCH-I545
[Verizon Samsung Galaxy S 4] StifflerServices:
Can we use mobile odin to flash back to 2.5.0.2 instead of pc odin, I've tried to flash back in twrp but still says 2.6.0.0, or is backwards twrp flashin not possible in twrp?
[Verizon Samsung Galaxy S 4] jova33:
I flashed back. There's a zip file in this thread.
[Verizon Samsung Galaxy S 4] Travisdroidx2:
Flash this and you will be on twrp 2.0.5.2 I got this from this thread somewhere and have used it myself.

http://db.tt/YeZ3cp4c
[Verizon Samsung Galaxy S 4] StifflerServices:
Ya I got that too must have transwarped it to u it to u, just send it back after u fix it thanks lol :p

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

Ok thanks, so I assume I do this thru twrp correct? And is this the loki one, not that I know the difference and what the hell it means lol
[Verizon Samsung Galaxy S 4] andy_fr:
You need to change the offset to match your time zone. even though I am EST, I needed to set the offset to -5 hrs for the correct time and date. I also had to flash back to 2.5.0.2 because when I was on 2.6 it was not working for me.
[Verizon Samsung Galaxy S 4] Dubbsy:
Does anyone know how to successfully take a screen shot on the gs4 or any 1080p twrp recovery for that matter.

Ddms screen shot didn't work. Fb2png didn't work.

I only need it for theme sharing reasons.

Thanks if anyone knows a way.

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] brizey:
So are we going to get 2.6.1.0? The change log says there are some fixes that sound like it would fix some issues folks here have had. Nothing on their server yet, though.
[Verizon Samsung Galaxy S 4] HowardZ:
I do not see a new version yet

http://techerrata.com/browse/twrp2/jfltevzw
[Verizon Samsung Galaxy S 4] purple_zergling:
It's been half a month since someone posted about this, but ME7 cannot install TWRP (even with root) correct?
[Verizon Samsung Galaxy S 4] crookedview:
Correct.
[Verizon Samsung Galaxy S 4] westhaking:
I would also like to know if TWRP 2.6.1.0 will be available to us?
[Verizon Samsung Galaxy S 4] Lw00d:
new version 2.6.3.0: still not available to us..:(
[Verizon Samsung Galaxy S 4] igotroot:
Funny, and I know I'm all late in the day, but I have been using 2.5.0.3 for like 4 months on my S4 with no issues...I'm I missing something? What is allegedly wrong ?
[Verizon Samsung Galaxy S 4] westhaking:
Yes. The 2.6.1.0 version introduced some fixes for 4.3 based Roms and is currently unavailable to us. Without it you can not use any 4.3 based Rom as it will not boot up past the Samsung logo after rebooting your phone for the first time.
[Verizon Samsung Galaxy S 4] igotroot:
But I AM on 4.3....Google Edition on my at&t S4...I'm using 2.5.0.3 and I have no issues flashing anything.
[Verizon Samsung Galaxy S 4] nawdman:
I'm on 2.6.0.0 with absolutely no problems
[Verizon Samsung Galaxy S 4] dmarden:
I run 4.3 based AOKP with TWRP 2.5.0.2 just fine.

That aside, remember what the OP said... If you have questions or want attention on a matter, you need to PM him, he cannot check every device thread regularly.
[Verizon Samsung Galaxy S 4] Travisdroidx2:
Eclipse 4.3 also flashes just fine with version 2.5.0.2
[Verizon Samsung Galaxy S 4] dmarden:
I have NOT tried it, but I noticed that 2.6.3.0 became available for our device today on Goo and teamw.in
[Verizon Samsung Galaxy S 4] egore93:
Did you flash it?
[Verizon Samsung Galaxy S 4] dmarden:
uhhh... lol.
[Verizon Samsung Galaxy S 4] egore93:
I thought you were caught up with the posts above and was saying you had not. I was just skimming thru all the post because of some problems I've had with 2.6.o.o.;)
[Verizon Samsung Galaxy S 4] HowardZ:
I tried to install it using Goo Manager. Goo Manager downloads it and says it installed it, but when I reboot to recovery I get the CWM Touch which had previously been installed.

So, I once again modified the zip flashable, and was able to flash it.

During the flashing it says it is the old version of TWRP, but after rebooting into recovery the top line says "Team Win Recovery Project v2.6.3.0"

I have only booted it, and have not yet tried flashing Roms/CM nor making nandroid backups.

Here is the file I made: http://db.tt/hivIIUH9

Regards
[Verizon Samsung Galaxy S 4] brizey:
Thanks.

On my n7 you have to change goo's download directory to get it to work (the legacy vs 0 thing). Going to try it later and report back.
[Verizon Samsung Galaxy S 4] dmarden:
I haven't done much with it, but I installed it via Goo with no issue.
[Verizon Samsung Galaxy S 4] westhaking:
Happy to report that the latest version (2.6.3.0) is working great! Finally able to boot up a 4.3 Rom with TWRP.
[Verizon Samsung Galaxy S 4] brizey:
I am getting hung boots on 2.6.3.0. It will get to the TWRP screen and hang. One thing I noticed is that it will "unhang" immediately if i plug the phone into my PC. Anyone else?
[Verizon Samsung Galaxy S 4] bsimpson1:
I've found that it also works to press the power button when this happens.
[Verizon Samsung Galaxy S 4] deviousmrtaco:
2.6.3.0 Is working fine for me, i've done everything from flash a new rom to back up and restore with no problems
[Verizon Samsung Galaxy S 4] zeroxg4:
Have you tried wiping before installing a ROM including the "Format Data" option?
[Verizon Samsung Galaxy S 4] HowardZ:
http://xdaforums.com/showthread.php?t=2428194

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

I have been reading about the nexus 7 tablet which has been experiencing touch problems. Google has been publishing OTA updates with new touch firmware to try and fix it.

Well, it turns out that TWRP will flash its own version of the touch firmware during its first boot up. This causes a delay in TWRP booting up. Having the kernel and TWRP both trying to update the touch firmware can cause some confusion.

Now back to the verizon S4, I have randomly been experiencing both booting delays, and also minor touch problems. TWRP and touch firmware might be the cause of both problems.

P. S. I have installed non-touch CWM as an experiment to see if booting delays are eliminated.
[Verizon Samsung Galaxy S 4] bsimpson1:
I guess that explains why non-touch-based events like plugging into a computer or pressing the power button causes it to "snap out of it" when it's hanging.
[Verizon Samsung Galaxy S 4] strikeir13:
How is everyone installing the latest version? Goo Manager didn't work for me
[Verizon Samsung Galaxy S 4] deviousmrtaco:
Yes
[Verizon Samsung Galaxy S 4] HowardZ:
Here is the file I made: http://db.tt/hivIIUH9
[Verizon Samsung Galaxy S 4] mlin:
It took rebooting several time last night before the power button or plugging into AC would stop the hanging. As such, I've gone back to 2.5.0.2. I works perfectly fine for me for ROMs of all variants. I guess I'll just sit tight until the hanging issues are truly resolved.
[Verizon Samsung Galaxy S 4] SellswordShev:
Still getting hung up on boot with cm10.2 nightlies, but with 2.6.0.3 atleast when I yank the battery and reboot it comes back up. Previously I had to fix permissions or sometimes even reflash my ROM for the boot to happen. Not sure whats screwing up that first reboot.
[Verizon Samsung Galaxy S 4] HowardZ:
I have been using the plain non-touch Clockworkmod recovery for several days now.

Every day I have been installing a new Cyanogenmod nightly.

I find CWM less user friendly than TWRP, and rather clunky pressing volume buttons so many times.

I have been experiencing 100% reliable boots with non-touch CWM - usually taking about 10 to 15 seconds for the boot animation to begin.
[Verizon Samsung Galaxy S 4] amoeller:
Does CWM support exfat formatted sd cards because I don't think it does.
[Verizon Samsung Galaxy S 4] Alxoom33:
I have had no success using TWRP 2.5.0 through 2.6.0.3 with my encrypted VZW MDK S4. Tried your zip as well, but no luck.

Have been using encrypted Xoom for a while with runanhide's TWRP versions through 2.6.0.3. Any suggestions or help would be appreciated. :rolleyes:
[Verizon Samsung Galaxy S 4] Surge1223:
Anyone know why our device name is set to m919's? Even though everything else says mdk...
[Verizon Samsung Galaxy S 4] alixyz:
Same here, been trying to find a solution. I'm running CM10.2 (latest nightlies) with my data encrypted. With TWRP 2.6.0.0 in recovery I'm prompted for a password to decrypt/mount the data but it won't accept my password, giving me "E:Failed to decrypt data.". With TWRP 2.6.3.0, it doesn't detect the encryption and without prompting me, it gives me the following error "E: Unable to mount '/data'"
[Verizon Samsung Galaxy S 4] iwearthebelt:
I think I read somewhere that flashing back to 2.5.0.2 fixes that issue.
[Verizon Samsung Galaxy S 4] Alxoom33:
I found that none work. Fortunatly there are aosp emails that you can use that don't require encryption. I use them on Oct.4.3 and Hyperdrive 9.1.

:cool:
[Verizon Samsung Galaxy S 4] fireattack7:
Nevermind.
[Verizon Samsung Galaxy S 4] dadoc04:
I see TWRP 2.6.3.1 is rolling out for some devices, anybody know how to build it for this device?
[Verizon Samsung Galaxy S 4] HowardZ:
The latest version I see is 2.6.3.0

http://techerrata.com/browse/twrp2/jfltevzw
[Verizon Samsung Galaxy S 4] dadoc04:
^

Correct. I said it rolled out for other devices.

Sent via Galaxy s4
[Verizon Samsung Galaxy S 4] HowardZ:
Do you know where the TWRP source code is available for the S4 ?
[Verizon Samsung Galaxy S 4] HowardZ:
I am reading up and trying to do it.
[Verizon Samsung Galaxy S 4] HowardZ:
Well, I just - finally - managed to make TWRP for the Nexus 7 (2013) LTE (deb) tablet.

I decided to start with the Nexus 7 because I don't have to be concerned about LOKI.

I booted it up on the Nexus 7 Tablet and it is version 2.6.3.0

I don't know if it actually works properly - and if done wrong it has the ability to brick a device.

Next I will try making it for the S4, but it will also end up being version 2.6.3.0 which is not what you want.

So, I might need to figure out where the Team Win stores the 2.6.3.1 source code
[Verizon Samsung Galaxy S 4] dadoc04:
really appreciate you trying to get that figured out.
[Verizon Samsung Galaxy S 4] HowardZ:
Well it seems the TWRP source code for 2.6.3.1 is not in the github - and this version is only available on the S4 I9505.

So, if one really wants it, I suppose it "probably" will work on our phone if it is first LOKI'd.

But, I wouldn't recommend trying it, as I don't know if all the partition names and locations are identical or not.

I have managed to build TWRP from https://github.com/TeamWin/Team-Win-Recovery-Project/tree/twrp2.7 , but when I boot it up, it displays 2.6.3.0 as the version. The code changes every week or so. It is like cyanogenmod that one can build something that is a work in progress and might not work right or has debugging in it.

It is probably safest to stick with official releases.

Here are my cyanogenmod builds and twrp builds in google drive:

https://drive.google.com/folderview?id=0B88bR12MKYUKc0FOZ1M0bFd0c00&usp=sharing#list

recovery.img is not LOKI - do not flash this.

recovery_loki.img is LOKI'd

recovery-twrp-jfltevzw-loki.zip can be flashed by CWM or TWRP and contains an non-LOKI recovery.img which gets LOKI'd automatically while installing the zip file.

Again - I don't see any advantages of trying to use a pre-release or work-in-progress version of TWRP. A bad TWRP can brick the phone.

Learning to build this might be useful if someday in the future new versions of TWRP stop getting built for the S4 because the developer doing it has sold his S4 moved on to some better phone.

This often happens when a phone gets to be 2 or 3 years old, as the developers move to newer phones and don't want to continue maintaining their work.