yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] HowardZ:
The random booting problem - where the Samsung S4 screen never disappears until the battery is pulled - it seems this problem is gone.

I don't know if it from building the TWRP directly from their github (latest and possibly experimental code), or if something has changed in cyanogenmod (as I also build my own cyanogenmod for the S4 but the only change I make is for the cyanogenmod build process to create TWRP recovery instead of CWM recovery).

I have rebooted 5 times, then rebooted 5 times with the charger connected, then powered down and powered up 5 times.

And not a single time did it hang on the Samsung S4 screen.

I did not change any code.

I am just building the latest Cyanogenmod and TWRP from their githubs.

I am pleased, but have no idea who to thank for it. :)

P.S. My TWRP made 06 NOV has TWRP debugging displayed every time I touch the screen during backup, restore, or installing rom. I asked and was told how to turn off the debug (event logging), and am Rebuilding it now.

---------- Post added at 04:30 PM ---------- Previous post was at 04:06 PM ----------

Oh Darn!

I had my S4 off for several hours, and just turned it ON to try flashing the latest TWRP with event logging turned off - and it froze on the Samsung S4 screen requiring a battery pull.

Oh well.
[Verizon Samsung Galaxy S 4] deviousmrtaco:
I believe I saw some CM commits fixing the problem when you built yours it should work fine, thanks for the new recovery :)

I think this was the commit

http://review.cyanogenmod.org/#/c/52006/
[Verizon Samsung Galaxy S 4] um009:
Works perfect !
[Verizon Samsung Galaxy S 4] Legacystar:
when aree we going to see 2.6.3.1 which i guess fixes flashing of 4.4 roms. it's out for nexus 7's and Gnex.
[Verizon Samsung Galaxy S 4] dmarden:
I run 2.5.0.2 and had no issues flashing 4.4 ROMs.
[Verizon Samsung Galaxy S 4] DroidForLife33:
:thumbup:
[Verizon Samsung Galaxy S 4] LasVegasRomeo:
Ya not sure but nothings changing when i tried to flash that 2.7. But it also hasn't changed with any of the fresh rom installs i have don't lately either when i know they had cwm. TWRP stayed with me . But ould that recovery loki be same as like the recovery img goo downloads and is already ready patched? The previous zips and ones i put together from those just have the img file at the base of the zip not packaged with the loki flash / patch etc in system/bin. Not taking up more room just wondering if renaming that recovery_loki to just recovery.img and flashing be be good to go or not. Yet again there was changes made since then but no ones had a issue from sounds of it. Thanks in advance for your time.
[Verizon Samsung Galaxy S 4] HoodBoogie:
TWRP not downloading with Goomanager.. Any ideas? Ive rebooted, uninstalled, full restored to stock root and still will not download. Just times out the webpage.. Been doing this for last 3 days.

I imagine I can flash via odin? Just not sure why I need to do
[Verizon Samsung Galaxy S 4] DroidForLife33:
I restored using terminal emulator. Download the newest twip from here. http://teamw.in/project/twrp2/181 Put the file on the root of your sdcard. Go to the terminal emulator and type.

su

dd if=/sdcard/openrecovery-twrp-2.6.3.0-jfltevzw.img of=/dev/block/mmcblk0p21

reboot

That's should work for you

---------- Post added at 10:46 AM ---------- Previous post was at 10:33 AM ----------

I posted below for your help.
[Verizon Samsung Galaxy S 4] res0prw2:
Will flashify work for installing as well?
[Verizon Samsung Galaxy S 4] binqker:
I'm in the same boat as you..... **** is not downloading.... I heard there's a bug on the latest version.
[Verizon Samsung Galaxy S 4] amoeller:
TWRP 2.6.3.1 is now up on both Goo's site and Team Win's site. I installed it and it seems to work fine. I can't seem to find a change log for it though.
[Verizon Samsung Galaxy S 4] brizey:
I have now used it a few times. Seems OK. Have not restored a back up yet. Just been flashing euro's CM11 nightlies and making backups. I used flashify to flash it.
[Verizon Samsung Galaxy S 4] tkacer:
TWRP 2.5.0.2 has really been solid for me - I'm going to hold off on 2.6.3.1 until further confirmation that it works properly and that there is additional advantages to the newer build....
[Verizon Samsung Galaxy S 4] gadget!:
I've been using 2.6.3.1 for a couple of days now and it seems pretty good so far.

No hangs on the splash screen so far.

Back up and restore, flashing files, wiping, works fine.

Maybe it's just me but I believe the font is slightly bigger and easier to read.

Sent from a Galaxy S4... Far far away
[Verizon Samsung Galaxy S 4] tkacer:
other than the font - anything else different??
[Verizon Samsung Galaxy S 4] gadget!:
I'm sure there's more but that's all I've noticed so far

Sent from a Galaxy S4... Far far away
[Verizon Samsung Galaxy S 4] brizey:
Yeah, the font on the console screen is much easier to read for this old man.
[Verizon Samsung Galaxy S 4] tkacer:
Anyone have a zip of 2.6.3.1 ?

NVM - found the .img and used flashify
[Verizon Samsung Galaxy S 4] drt054:
In recovery, does mounting USB Mass Storage work for anybody for transferring files? I am on 2.6.3.1. but it didn't work on my phone while on 2.5.0.2 either and don't like MTP while in CM because it seems a lot slower and can only move one file or folder at a time
[Verizon Samsung Galaxy S 4] Thatguy4life:
Has anyone else encountered issues when trying to update through goomanager? When I go to install open recovery script it shows the new update available shd then it says your download is starting but it never goes beyond that point. I had the same problem running on hyperdrive rom, just flashed an aosp rom last night and still having the same problem. Also haven't been able to run a backup in months through current twrp
[Verizon Samsung Galaxy S 4] dorioo:
Yes, I encountered the same issue and ended up doing a manual install. If you go to the TWRP site and download the file, it's hosted at a different location now than the one goomanager uses.
[Verizon Samsung Galaxy S 4] deviousmrtaco:
I'd use TWRP manager that updated just fine for me, goo has been having some serious issues
[Verizon Samsung Galaxy S 4] Deeked:
Thank you so much. As you said, GooManager has been problematic. TWRP Manager got the job done. I appreciate your advice sir. One more step completed. :highfive:
[Verizon Samsung Galaxy S 4] saul1991:
I'm having an issue I tried flashing it through goo manager but I get an 500 internal error.....
[Verizon Samsung Galaxy S 4] mcconvict:
I quit trying updates after 2.5.0.2. There's no point. This is the holy grail of recoveries
[Verizon Samsung Galaxy S 4] saul1991:
[RECOVERY] TWRP 2.5.0.2 touch recovery [2013-05-23]

how do i get that version im stuck with like 2.6.0
[Verizon Samsung Galaxy S 4] mcconvict:
If you're on vzw I'll send the link to dropbox
[Verizon Samsung Galaxy S 4] saul1991:
yeah im on verizon can you send some instructions to. dude im having some major issues with my s4 right now
[Verizon Samsung Galaxy S 4] mcconvict:
https://www.dropbox.com/s/24gce1eke35d1pq/i545-S4-VZW-TWRP-2.5.0.2-jfltevzw.zip

Just flash it in whatever recovery you have now.
[Verizon Samsung Galaxy S 4] saul1991:
im using TWRP just flash in there??
[Verizon Samsung Galaxy S 4] mcconvict:
Yep. That's it
[Verizon Samsung Galaxy S 4] saul1991:
any idea why i get this issue??
[Verizon Samsung Galaxy S 4] mcconvict:
Just click do not fix. Its actually not really an issue. I've had that pop up on occasion with no adverse reactions
[Verizon Samsung Galaxy S 4] saul1991:
thanks man got it everything up and working
[Verizon Samsung Galaxy S 4] mcconvict:
Happy to help. Glad you got it worked out
[Verizon Samsung Galaxy S 4] Thatguy4life:
thanks that worked perfectly
[Verizon Samsung Galaxy S 4] boogerboy72:
Im still getting hung up at the samsung unlocked screen about 50% of the time. was there ever a fix?
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
Is the newest build slow at all?
[Verizon Samsung Galaxy S 4] gadget!:
I've tried every build some 2.5.0.2 and every time I have been back within 24hrs.

I've been using this latest build since it came out and I won't be going back. This release has been stable and I have had zero issues with it.

Sent from a Galaxy S4... Far far away
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
Which release is it? Can it be downloaded straight from GooManager or do you have flashable zip?
[Verizon Samsung Galaxy S 4] gadget!:
2.6.3.1

I couldn't get GooManager to work so I downloaded it from the TWRP site and installed it with terminal emulator.

There are other ways to install it mentioned in this thread that are probably easier.

Actually there is a TWRP Manager app in the play store that is supposed to work but I haven't tried it.

Sent from a Galaxy S4... Far far away
[Verizon Samsung Galaxy S 4] t3project:
doesnt recognize 64gb sd card in 2.5.0.2 but a loki'd 2.5.0.1 did
[Verizon Samsung Galaxy S 4] SCDroid:
how do i get it to save my backups to my sdcard?
[Verizon Samsung Galaxy S 4] Cubs2008:
Make sure you select STORAGE and change it to your SD Card instead of the default (Internal Storage) when you're at the main screen in TWRP.

Worked great for me installed through GOO and was able to back up stock OS to the card (64GB SD.) The backup did take a bit (but my backup is 4.5 GB.)
[Verizon Samsung Galaxy S 4] abarthle:
Awesome! Thanks so much! worked like a charm.

---------- Post added at 01:22 PM ---------- Previous post was at 01:20 PM ----------

So, here's my ignorant question...

Once custom ROMs become available, will we just be able to use GooManager to install them or will we have to do it from TWR?

---------- Post added at 01:32 PM ---------- Previous post was at 01:22 PM ----------

Another question:

I just performed my first backup and after completing it told me I appeared to have lost root capability and gave me options to fix or just reboot.

I selected to fix.

Is this normal?
[Verizon Samsung Galaxy S 4] Eric214:
HAHA 3GB backup!? WOW wtf Samsung!? I'm going to get something to eat, this will take awhile.
[Verizon Samsung Galaxy S 4] brizey:
Yep...time to find a 64 GB sd card, lol. I am using my old 32 GB one from my previous phone.
[Verizon Samsung Galaxy S 4] trogdor3222:
so I REALLY want to try the AOSPA beta, but in case things don't go so well I wanna be able to get back to stock. anyone tried restoring a backup yet?
[Verizon Samsung Galaxy S 4] brizey:
Even if backups don't work, folks have odined back to stock, plus there is a rooted stock rom, too, with busybox etc. Flashing ROMs works for sure.
[Verizon Samsung Galaxy S 4] W00fah:
Installed through GooManager App and it worked perfectly.
[Verizon Samsung Galaxy S 4] chronoquestion:
Perhaps I missed something, but after wiping my device still only lists 9.57GB of total internal storage. Is there an option in TWRP to get back the missing storage?
[Verizon Samsung Galaxy S 4] JBeXX:
Not missing anything. Unfortunately our phones have over 6 gigs dedicated to system and os memory. So, our 16gb int is really only 10gb.
[Verizon Samsung Galaxy S 4] chronoquestion:
Even after installing AOSP rom?
[Verizon Samsung Galaxy S 4] JBeXX:
No, the dedicated system memory should be much smaller on aosp
[Verizon Samsung Galaxy S 4] mikeyinid:
There is 9.67gb available on aokp. Should be similar on most aosp roms
[Verizon Samsung Galaxy S 4] kenhunt:
If you go into storage settings, then miscellaneous, is there anything you can delete there? On the Note 2 I was able to recover 4gb or so by deleting some stuff after removing TW.
[Verizon Samsung Galaxy S 4] JBeXX:
Yeah, I'm curious about this too. I haven't tried aokp on the s4 but like you said. About 4gb could be recovered on the note 2
[Verizon Samsung Galaxy S 4] runhappy:
When trying to install OpenRecoveryScript, it says no recoveries were found for my device. Any way to fix that?
[Verizon Samsung Galaxy S 4] JBeXX:
You've already rooted correct?
[Verizon Samsung Galaxy S 4] runhappy:
Yeah, sorry forgot to update, rebooted a few times and it worked.
[Verizon Samsung Galaxy S 4] :
When making backup should I check all the backup options or are some not needed? I guess im confused as to what they all are
[Verizon Samsung Galaxy S 4] mochamoo:
Try twrp manager from the play store. Advanced->install recovery. Worked for me.
[Verizon Samsung Galaxy S 4] Alxoom33:
Agree, really like 2.6.3.1 downloaded TWRP Manager from play store. Works great!:cool:
[Verizon Samsung Galaxy S 4] gadget!:
I like the bigger font a lot, much easier to read.

Sent from a Galaxy S4... Far far away[/QUOTE]

Sent from a Galaxy S4... Far far away
[Verizon Samsung Galaxy S 4] Lizard King:
Cant get phone to boot into recovery... boots into download mode evertime... verified root etc... any ideas?
[Verizon Samsung Galaxy S 4] 32BitWhore:
What bootloader version are you on? TWRP/CWM only work on the MDK build. My guess is you're on MI1/ME7/MJ7.
[Verizon Samsung Galaxy S 4] Lizard King:
yea i am on me7... installed safestrap which worked, but i enjoy twrp and/or cwm... curious as to what others think... should i suck it up and use safestrap, or should i odin an older build?
[Verizon Samsung Galaxy S 4] 32BitWhore:
No way to Odin backwards unfortunately. You're stuck with safestrap. Don't upgrade further or you won't be able to use safestrap either.

Sent from my CM11/KT Powered Galaxy S4
[Verizon Samsung Galaxy S 4] Lizard King:
damn that sucks... i miss the good ol days
[Verizon Samsung Galaxy S 4] Nydalxy:
He is correct about not being able to Odin backwards but not about upgrading further. You can upgrade to mj7 or mk2 since Safestrap does support them now. That is also the only way you can flash a 4.3 Tw rom since you can't flash a 4.3 rom with an me7 base.

Or.... You can take the route I did and buy an MDK S4 on swappa and then sell yours. You break out even and get the MDK bootloader :)
[Verizon Samsung Galaxy S 4] 32BitWhore:
Ah, didn't realize hashcode had gotten SS running on MJ7. Apologies, I haven't messed with an MJ7 in a few months.

Sent from my CM11/KT Powered Galaxy S4
[Verizon Samsung Galaxy S 4] mrw1215:
So I've been on 2.6.3.0 and I'm trying to upgrade to 2.6.3.1. I don't really want to do it through my computer, but GooManager isn't installing it (it just hangs forever on the "installing" screen). I tried that TWRP Manager app, and it said it installed, but when I rebooted into recovery, I was still on 2.6.3.0.

In TWRP Manager, though, it did ask me to make sure the partition listed was correct (it said /dev/block/mmcblk0p21), and not knowing what that meant, I just pressed yes. I wonder if that has anything to do with why it didn't install correctly?

I also tried using the Terminal Emulator app, but couldn't figure out how to do anything in there. I typed in su and pressed the enter key, and nothing happened. I typed in the command for flashing recovery and pressed enter, and nothing happened. I don't know if I'm using it wrong, or what...?

Any other options for installing, besides using my computer?
[Verizon Samsung Galaxy S 4] brizey:
try Flashify
[Verizon Samsung Galaxy S 4] Bait-Fish:
Flashing from recovery should work. I've had trouble flashing radios using reboot to recovery and TWRP Manager, requiring doing it a specific way to make it work. Maybe it could help you flash the new recovery.

What works for me is the three finger salute. Turn the phone off, then hold volume up, home, and power. After the text shows booting to recovery, let go of the power button only. The phone will likely reboot but keep volume up and home pressed and it should go the second time. If the second time doesn't work, start over from phone off and do the power button on the second time too. Trial and error.

I can flash radios successfully when starting recovery this way. Not sure why the difference. Not every radio zip needs this either. Some work using reboot to recovery *shug*

This technique was not my find. I forget who to attribute it to unfortunately.
[Verizon Samsung Galaxy S 4] mrw1215:
When I open this app, it just hangs at "Reading recovery info...".
[Verizon Samsung Galaxy S 4] mrw1215:
So, if Goo Manager, TWRP Manager, and Flashify don't work for me for installing 2.6.3.1, what can I do to install it, at this point?
[Verizon Samsung Galaxy S 4] brizey:
Do you have one of the new KK ROMs installed? The CM ones have a setting in developer settings for root access. Toggle it back and forth at least once and leave it on apps and ADB. Then do something to make sure you have root, like rename a file in the system folder in root explorer. It almost sounds like you have a problem with superuser. All the methods you tried required root, and they may be silent failures for some reason. I think dd can fail silently, and they may be using it.

There are some binaries out there for flashing recovery via adb. There is also a way (easy in Linux) to make a tar.md5sum file of the recovery to flash via odin.
[Verizon Samsung Galaxy S 4] mrw1215:
I'm on the Euroskank builds of KitKat, yeah. I just tried toggling the root access setting to off, then back to "apps and ADB", and it doesn't seem to have helped the situation at all.
[Verizon Samsung Galaxy S 4] LasVegasRomeo:
Didnt see mentioned but is always zip installer. Know it says it paid on market butbif u go into goo and go to browse all..and the dev catagory..find and go to beerbong. Follow this path and u will find all the versions on there for free. Just throwing it out there.

dev/beerbong/apps/Zipinstaller
[Verizon Samsung Galaxy S 4] mrw1215:
Ah, yanno what? Apparently I figured it out. On the previous ROM I was on, I was used to having to flash SuperSU with it in order to have root access. When I switched to CM/ Euroskank, I just kept doing that, thinking nothing of it. I guess that was causing some kind of SU conflict...? I dunno. But when I flashed the newest nightly, I first wiped the cache, dalvik, and system, then flashed everything minus the SuperSU file I was flashing before, and everything seems to be working fine; used TWRP Manager to download and flash 2.6.3.1, then rebooted into recovery to verify, and it was good.
[Verizon Samsung Galaxy S 4] gteknet:
ON MK2

Does this will work on SHC-I545 MK2 ????? version.:fingers-crossed:
[Verizon Samsung Galaxy S 4] Mightycaptain:
No. Safestrap is your only option for recovery. There is a link in android development for it. I encourage you to read up on it.
[Verizon Samsung Galaxy S 4] vanberge:
I had some problems with Goo manager as well when running CM 11 nightly. I then switched to SuperSU for root and Goo manager was then able to flash the recovery properly. Strange to me, but I even flashed back to CWM to try again and recreated the results.
[Verizon Samsung Galaxy S 4] brizey:
Just read that 2.7 is on its way and it sounds like it will fix some of the issues we have been having.

Edit 3/8: just got posted, downloading now.
[Verizon Samsung Galaxy S 4] brizey:
Sorry for the self-bump, but I figured people may want to see my edited post above. 2.7.0.0 has been released. So far so good. I just used flashify--you can download it right from the app. Making a backup right now. We have full SELinux support...hopefully this cures the oddities with KK flashing (although I have had none since moving to the GE port).
[Verizon Samsung Galaxy S 4] brizey:
For 2.7.0.0 (for me at least):

Installs work

Wipes are weird--the recovery resets, but it seems like the work. I used the file manager and data was clear after i wiped even though it seems like it crashed

Backup did NOT work. I could not restore a backup.

Installing an older version via a zip file did NOT work.

Back to 2.6.3.1
[Verizon Samsung Galaxy S 4] bobbarker2:
Just tried to install 2.7 with dd and I got "unauthorized software on device" when booting. I assume this is because the img wasn't lokifyed. In odin mode now trying to fix..
[Verizon Samsung Galaxy S 4] gadget!:
I had the same problem, I was able to boot into download mode then from there reboot normally to get the phone to boot.

Then I installed goo manager and installed recovery from there and it brought me back to 2.6.3.1

Sent from a Galaxy S4... Far far away
[Verizon Samsung Galaxy S 4] brizey:
I used flashify. I am thinking maybe then that flashify knows to lokify the image? Any idea what happens if you double loki an image? I was thinking about dropping it in the automatic lokifying zip that runs the script to lokify when flashing a recovery.

Edit: Bullet #4 on the play store description for flashify says it loki patches if needed. So that's why mine booted ok. BUT...it doesn't really work, lol.

Edit 2: I PM'ed Troy. I am sure he is inundated now, but hopefully he will take a look at some point.
[Verizon Samsung Galaxy S 4] bobbarker2:
Ya, after reading your post I just said **** it and went back to the previous version. Not going to spend time lokifying the img if the recovery doesn't work properly. I sent an email to the dev's telling htem the jfltevzw variant isn't built properly so we'll see if they update it. Maybe some of the problems you had were from flashify? Who knows.
[Verizon Samsung Galaxy S 4] tkacer:
It will be interesting to see how 2.7 shakes out. Tried 2.6.3.1 and did like the bigger font, but had some intermittent flashing aborts. Went back to 2.5.0.2 and that's where I stay. The grass does look greener at times, but after trying just about all the different recoveries, I always seem to migrate back.....
[Verizon Samsung Galaxy S 4] brizey:
2.7.0.0 doesn't have the bigger font.
[Verizon Samsung Galaxy S 4] 32BitWhore:
Made the mistake of jumping in before reading and got the "unauthorized software" error. Was able to get it back up and running on 2.6.3.1, but based on some of the responses here, it looks like I'll wait until 2.7.0.1 to see what happens. I'm bummed because I'm unimpressed with the performance of 2.6 on the S4. It worked absolutely flawlessly on my S3, but on my Loki'd S4 it runs like crap. Was hoping 2.7 would fix those issues but it appears not. I refuse to use CWM, have always loved TWRP on all my devices but the more issues I have with it on this device, the more I'm considering switching.
[Verizon Samsung Galaxy S 4] brizey:
Actually, I am the only one so far that posted anything about 2.7.0.0 in terms of wiping, etc. I would really like to get some corroboration in case I was just being dumb somehow. I am pretty sure of the odd wiping behavior...I read the same thing on the Sprint forum, and the AT&T guys reported that it was not pre-lokied as well. But I would like someone else to see if they also have trouble restoring a back up and flashing a recovery zip, etc. Not that I want someone ending up odining back to stock, etc. I was able to flash a ROM, so I think its somewhat safe to test even if it is broken.
[Verizon Samsung Galaxy S 4] krypto1300:
I'd love to try it out myself, but 2.5.0.2 works flawlessly for me. I can't bring myself to try 2.7.
[Verizon Samsung Galaxy S 4] brizey:
I went over to the AT&T thread. They were posting the same thing about the backups not restoring.

I have been using 2.6.3.1 for a while now. Have not had any issues. For a while there I was having a lot of ROMs stick on the splash on boot, but I have not had that for some time.
[Verizon Samsung Galaxy S 4] bsimpson1:
I think that was actually a cm-related issue that they have finally fixed. I saw it mentioned in the change log a few months back

---------- Post added at 04:10 AM ---------- Previous post was at 04:08 AM ----------

The boot hangs, I mean. I'm not sure about the restoring issue.
[Verizon Samsung Galaxy S 4] brizey:
Make sense. I think I was popping around between the CM based ROMs at that point. Man was that annoying.
[Verizon Samsung Galaxy S 4] 32BitWhore:
Alright so I took the plunge and decided to try it using Flashify. Can confirm it does Loki properly. Performance is light years better than 2.6 for me - don't know if it's my phone specifically or if anyone else noticed the same. Only thing I have tried so far was a cache wipe and do get the "crash" that was talked about but it is confirmed working regardless. Will try a nandroid after work today and see what happens for me.