yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] ddskier:
Luckily enough I used flashify and was able to go back down to 2.6.3.0. I think the loki doki patch isn't applied to the 2.7.0.0 recovery.

---------- Post added at 08:13 AM ---------- Previous post was at 08:11 AM ----------

How do you loki patch recovery? The loki patches that I have seen are for ROMs.
[AT&T Samsung Galaxy S 4 Android Development] jthrasher47:
Here flash recovery then flash this https://www.dropbox.com/s/cvbuddpu3khx89t/loki_recovery.zip
[AT&T Samsung Galaxy S 4 Android Development] RK:
Anyone wishing to update to 2.7.0.0

Flash this in the recovery:

Recovery Flashable TWRP 2.7.0.0

Then flash the zip I made based on Philz that loki's recoveries

Loki_recovery.zip

EDIT: Users report that there are bugs in this TWRP version.
[AT&T Samsung Galaxy S 4 Android Development] jerrychasta:
Thanks works great. Thumbs up.
[AT&T Samsung Galaxy S 4 Android Development] rav4kar:
Folks. ..share your experience with 2.7.x. is 2.7 compatible with 4.3 or 4.4.x only?

I am still sticking to 2.5.x for stability :D
[AT&T Samsung Galaxy S 4 Android Development] finneginsfast:
There's something funky about 2.7.0.0 for me. Whenever I wipe data or do factory reset I get a black screen and have to hit the power button to turn it on again. Doesn't seem like wipe are working either. Performed a full wipe and rebooted to see what happened, phone booted as normal.
[AT&T Samsung Galaxy S 4 Android Development] jerrychasta:
I'm using 4.4.2 tw rom right now. Just flashed it and boots up Fine and reboot system without hangups. Flash a few mods fine. Haven't tried to flash other roms yet but will get back on the feedback.
[AT&T Samsung Galaxy S 4 Android Development] Gordietm:
2.7 doesn't work yet. Back to 2.6.3.1

SGH-I337M jfltecan
[AT&T Samsung Galaxy S 4 Android Development] finneginsfast:
Could you elaborate as to what's not working for you?
[AT&T Samsung Galaxy S 4 Android Development] 78Staff:
Same occurs for me as well - reverted back to 2.6.3.1.
[AT&T Samsung Galaxy S 4 Android Development] Gordietm:
Cannot restore backups or wipe cache

SGH-I337M jfltecan
[AT&T Samsung Galaxy S 4 Android Development] RK:
Yes users in the i9505 section are also reporting the same..
[AT&T Samsung Galaxy S 4 Android Development] ddskier:
Thanks. After reading the other users experience with 2.7.0.0 I think I am going to hold off.

Sent using Tapatalk 4
[AT&T Samsung Galaxy S 4 Android Development] rav4kar:
Yup,TWRP is excellent tool when it works, I think the team needs more testing/testers.Once I was so reluctant to switch from CWM. I have been using 2.5.0.2 which is very stable and highly recommended by many as far as I know.
[AT&T Samsung Galaxy S 4 Android Development] brizey:
So you guys are having the same issues as us VZW folks. I love TWRP but there is a reason they need all those decimal points...0.0 never works, lol.
[AT&T Samsung Galaxy S 4 Android Development] byte9:
[MENTION=3550785]ddskier[/MENTION] thanks for mentioning Flashify. I was using mobile terminal to revert and oddly it would flash but not revert. Flashify did the trick. People saying to Odin and re-root.. Easy there guys. No need to scorch the earth. Flashify downloads ****ty 6.3.0.0(works but hangs often w external SD in).. Get that going then get a zip of 6.3.0.1
[AT&T Samsung Galaxy S 4 Android Development] stevey500:
Running MDL bootloader here, been rooted running CM for the past year.

Attempted install of TWRP 2.7 without reading what's already been posted here. I was too confident as I just barely flashed latest 2.7 TWRP to my buddy's s3 the night before and it all worked perfectly. On my S4, I flashed manually through terminal emulator as I've always flashed recoveries on the samsung devices successfully with the dd method. Rebooting into recovery to get the non-authorized software notice, secure kernel fail. For those of you stuck at this notice: Booting into Download mode (pwr+volume down) then pressing vol-down/cancel boots me back up into CM no problem.

I opened up terminal emulator and manually flashed my last known-good copy of twrp 2.6 xx img and things seem to be fine, TWRP recovery loads up and it boots up into cyanogenmod normally no problem...

It did change my boot-splash logo though. It went from the Samsung Galaxy S4 logo to the small Samsung with the padlock-unlock logo on all the boot splashes. Do those of us that flashed TWRP 2.7 need to do anything as far as restoring the bootloader exploits? Everything stills seems to be root. Re-flashed previous TWRP no problem, re-flashed latest CM11 for just-in-casies.

Thanks for reading.
[AT&T Samsung Galaxy S 4 Android Development] RK:
The boot splash screen just indicates the you had unauthorized software on your phone at some point. It does not affect any functionality.

If you want to get rid of it, you can always reset the flash counter using chainfire's app "triangle away"
[AT&T Samsung Galaxy S 4 Android Development] jerrychasta:
Tried wiping system and it just reboots.

---------- Post added at 07:03 PM ---------- Previous post was at 06:53 PM ----------

Anyone has 2.5.0.2 twrp image. Need file for flashify.
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
Here's a zip you can flash in recovery http://xdaforums.com/showthread.php?t=2441196
[AT&T Samsung Galaxy S 4 Android Development] jerrychasta:
Can't use a zip my recovery is down need .img.
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
Google i337 twrp image
[AT&T Samsung Galaxy S 4 Android Development] jerrychasta:
I thought I had to Odin back or use terminal emulator. But easiest way is to use flashify.
[AT&T Samsung Galaxy S 4 Android Development] byte9:
2.6.0.1 is stable. No need to go back to 2.5 --- 2.6.0.0 is the garbage. Use flashify and insrall , also--- flashify downloads its own images. You don't need them
[AT&T Samsung Galaxy S 4 Android Development] finneginsfast:
I think Troy will be putting an update out sooner than later. I did a test run with 2.7.0.1 and it's all sorted, just a matter of when he posts it.
[AT&T Samsung Galaxy S 4 Android Development] RK:
Flashable 2.7.0.1

Flashable 2.7.0.1

This one came pre-loki'd.

DOWNLOAD
[AT&T Samsung Galaxy S 4 Android Development] ChaosMinionX:
Credit to RK for the original post, I just added the 2.7.0.1 image file, flash in recovery and you are good to go!

http://d-h.st/yij
[AT&T Samsung Galaxy S 4 Android Development] sloanster:
Reports of bugs on this latest recovery would be extremely helpful... (I337 user) :cool:
[AT&T Samsung Galaxy S 4 Android Development] twcobra:
Just installed. So far a zip install and a cache and delvik wipe are working ok. I will try a back up later. So far nothing to report. :good:
[AT&T Samsung Galaxy S 4 Android Development] sloanster:
Hey those that have not tried the TWRP app is missing out!

Get the pro version!:cool:
[AT&T Samsung Galaxy S 4 Android Development] Gordietm:
Backups are working fine now.

SGH-I337M jfltecan
[AT&T Samsung Galaxy S 4 Android Development] Adizzzle:
Gonna be making a green version of 2.7.0.1 I suppose, seems like its working pretty darn good! ?
[AT&T Samsung Galaxy S 4 Android Development] bigal1542:
So are all the bugs that were in the 2.7.0.0 release fixed in the 2.7.0.1 release?
[AT&T Samsung Galaxy S 4 Android Development] finneginsfast:
Yup
[AT&T Samsung Galaxy S 4 Android Development] PapaMag:
Thank you this one is working great, pulled a boner with the 2.7.0.0 and flashed the wrong loki file, did loki doki instead of the loki recovery and it was back to odin stock start over time
[AT&T Samsung Galaxy S 4 Android Development] byte9:
Just FYI, although probably won't happen again. You do not have to go back to stock. Just reboot, boot into DL mode. From DL mode select to reboot and the pending recovery boot that TWRP has will clear and the phone will boot into your ROM. From there use Flashify and you can fix your recovery from an actively booted phone. Takes all of 2min and saves all the old school Odin drudge.
[AT&T Samsung Galaxy S 4 Android Development] PapaMag:
Thanks I'll give it a go, well I hope never to. I do believe I tried booting into download and reboot but got the triangle back. Maybe not I forgot already the events or at least blocked them out of my mind.
[AT&T Samsung Galaxy S 4 Android Development] byte9:
Nope, I can tell you for sure you didn't reboot from DL mode. The triangle comes from the no Loki recovery as you know. So just keep calm if it happens again after flashing recovery and boot into DL and then reboot it normally. But also, here's to never needing to to it ever ever because seriously releasing a non auto-loki recovery without warning is soo 2013 :)
[AT&T Samsung Galaxy S 4 Android Development] rymanh:
I flashed twrp 2.7.0.1 jftltecan galaxy s4 that I obtained from the twrp website onto my Telus galaxy s4.. but when I try to do a nandroid backup it fails. ..

And when I rebooted and went to my backup folder there was a nandroid there but it only contained a backup of my system and not my data..

Has anyone else had this happen ..

I guess until there is a fix or solution I'm gonna go back to an older version
[AT&T Samsung Galaxy S 4 Android Development] Gordietm:
I'm on a jfltecan and haven't had any problems since flashing 2.7.0.1. 2.7.0.0 was a disaster. Try downing Flashify and use it to download 2.7.0.1 and flash it. That worked great for me.

SGH-I337M jfltecan
[AT&T Samsung Galaxy S 4 Android Development] rymanh:
Hmm no dice for me.. but ill still give ya a thanks cause you tried to help
[AT&T Samsung Galaxy S 4 Android Development] sloanster:
Got it going thanks Dees...
[AT&T Samsung Galaxy S 4 Android Development] XGhozt:
I'm sorry if this is a stupid question. The play store app is prompting me to verify the device name, (jflteatt) I was able to google that. Then is asked me to verify the partition (/dev/block/mmcblk0p21) before installing, how would I verify that? Trying to upgrade here.
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
That is the right info. Your partition is 0p21 on the jflteatt. If you want a flashable zip there's one here http://xdaforums.com/showthread.php?p=51025402

Sent from my SAMSUNG-SGH-I727
[AT&T Samsung Galaxy S 4 Android Development] XGhozt:
Thank you, I appreciate the quick response. Is there an index somewhere which notates this information or do you know it from experience? I guess my question is, without posting here how would one verify this? I was poking around the system files, does that partition not get mounted until you boot into it (recovery)? Thank you again (and for the flashable zip).
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
I know it from experience but you can also Google i337 partitions xda

Edit, you're right to be cautious, if you flash something to the wrong partition you will brick your device

Sent from my SAMSUNG-SGH-I727
[AT&T Samsung Galaxy S 4 Android Development] XGhozt:
Got it, thank you very much.

:highfive:
[AT&T Samsung Galaxy S 4 Android Development] CPA Poke:
The only bug I have to report is a freeze when flashing more than 4 or 5 files at once. The first 3 or 4 flash fine, but then it froze during the next zip. It doesn't happen every time, but it's happened twice out of five multiple-zip flashes.
[AT&T Samsung Galaxy S 4 Android Development] twcobra:
I just had something interesting. I did an advance wipe. With cache, delvik and data. I wanted to see if I could resolve an issue. But when I tried to reboot it said I did not have a ROM installed. I ignored it and tried to reboot and it just sat there. I had to go back into recovery and re-install my ROM.
[AT&T Samsung Galaxy S 4 Android Development] ozziedog:
I had the same thing happen to me with 2.6.3.1 when I wiped "data" in advanced. Wiping just "cache and delvik" everything worked fine. I'm holding off on 2.7 little while longer.
[AT&T Samsung Galaxy S 4 Android Development] Cusa:
Worth it to update from 2.5.2?
[AT&T Samsung Galaxy S 4 Android Development] Gordietm:
Yes

SGH-I337M jfltecan
[AT&T Samsung Galaxy S 4 Android Development] Cusa:
But I keep seeing people reporting problems with each version of twrp.
[AT&T Samsung Galaxy S 4 Android Development] bigal1542:
Just curious, but when does Goomanager update to newer builds? I am not getting the option to download the newest version.

EDIT: Well I just saw that there is a TWRP manager out there. That the go to now for installing?
[AT&T Samsung Galaxy S 4 Android Development] :
Just try it and see. Keep 2.5.0.2 on phone and reflash if needed. I have NEVER had an issue on ANY rom with 2.5.0.2. ☺
[AT&T Samsung Galaxy S 4 Android Development] Cusa:
I just flashed it and forgot to make a backup of 2.5.2. Oh well
[AT&T Samsung Galaxy S 4 Android Development] :
I have one but at work. Try this and thank jd :)

http://xdaforums.com/showthread.php?t=2441196
[AT&T Samsung Galaxy S 4 Android Development] Miyamato:
Just a quick question, I1337m user here currently on 2.7, i want to use flashify to flash twrp 2.7.0.1 , I just want to be sure that it is going to the right location, it states: /storage/emulated/0/flashify/recoveries/twrp, is that fine?
[AT&T Samsung Galaxy S 4 Android Development] truckmann:
On your recommendation I'm trying out the TWRP app. I was going to update to the latest TWRP using it but it only download version 2.6.3.1 for install. Also I noticed it doesn't see my external SD card. Attempting to switch between internal and external just shows the same stuff. :(
[AT&T Samsung Galaxy S 4 Android Development] kamikazees:
[resolved]
[AT&T Samsung Galaxy S 4 Android Development] rymanh:
That happened to me too .. The twrp app couldn't see my SD card.. Probably due to the limitations of 4.4.2 and the lost ability of apps to write to external storage. .

It's too bad because the twrp app has a lot of potential
[AT&T Samsung Galaxy S 4 Android Development] SelfElevated2:
People always get all pissy when I say it but dag why doesn't he just upload zips for us. Goo sucks. Can never find what I'm looking for on it. And when I do Im not certain it's for my phone so I just don't mess with it
[AT&T Samsung Galaxy S 4 Android Development] :
We are of a very few that can't use Fastboot to flash this and DT provides these images across many variants. I use to use Fastboot on my other other phones and prefer that method.

You can generally find the zip--

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

DT may have other reasons, but would guess this is one of them--:)
[AT&T Samsung Galaxy S 4 Android Development] SelfElevated2:
Thanks
[AT&T Samsung Galaxy S 4 Android Development] :
:good: :)
[AT&T Samsung Galaxy S 4 Android Development] Cusa:
Went back to 2.5.0.2 and all my problems went away. 2.7.0.1 was the culprit to all my problems.
[AT&T Samsung Galaxy S 4 Android Development] :
2.5.0.2 perfect for me too. :)
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
Download the img file you want from goo.im then use flashify from the play store to flash it.

Sent from my Nexus 5
[AT&T Samsung Galaxy S 4 Android Development] 78Staff:
So no issues with 2.5.0.2 and the format data bug? That's the only thing that worried me about that version, was soft-bricking after formating data. Thought there were a bunch of complaints abou that...
[AT&T Samsung Galaxy S 4 Android Development] :
I never format data. Just wipe all including System 3x thru Advanced Menu. Never an issue on any ROM. :)
[AT&T Samsung Galaxy S 4 Android Development] 78Staff:
I did it often when switching roms, esp when moving between TW and ASOP/AOKP and back, etc. Not so much anymore as I am pretty set on the one I use.

I agree, take out that aspect and 2.5.0.2 is pretty much rock solid - I may go back to it. No real issues yet with 2.7.0.1 as of yet though.
[AT&T Samsung Galaxy S 4 Android Development] bigal1542:
Hey guys,

I'd love to upgrade to the newest recovery, but definitely don't want to brick my device. I've always updated through goomanager, but that won't show the newest version. What's the safest/easiest way to flash the new version? Thanks for dealing with the newb!
[AT&T Samsung Galaxy S 4 Android Development] finneginsfast:
Search the Playstore for Flashify, it'll give you lots of options.
[AT&T Samsung Galaxy S 4 Android Development] bigal1542:
Thank you so much! I didn't even know the app existed. It's a life saver! Thank you!
[AT&T Samsung Galaxy S 4 Android Development] TLK3:
About 50% of the time I try to boot into recovery with TWRP, the splash screen hangs. I have to power cycle and try again. This has been going on to some degree with every version of TWRP over the past 8-10 months. Essentially, it's been an issue since I got my S4 and flashed a custom recovery. Recently switched to Philz and so far have not experienced this problem. Any ideas?
[AT&T Samsung Galaxy S 4 Android Development] numbere:
There's no need to be passive aggressive.

This problem is due to the recovery and rom not working well together. TWRP 2.6.3. and Slimbean would hang half of the boots into recovery. TWRP 2.6.3 and Slimkat work flawlessly.
[AT&T Samsung Galaxy S 4 Android Development] TLK3:
Passive aggressive? Want trying to be at all. Just stating the facts. Simply looking for suggestions or anyone who has experienced and resolved this issue.
[AT&T Samsung Galaxy S 4 Android Development] WarlockW:
Use 2.5.0.2 is pretty much rock solid.
[AT&T Samsung Galaxy S 4 Android Development] sk8trix:
I've been using the above 5.0.2 or whatever the number is for ever and never have had an issue. I want to upgrade to the newest but idk how bad that might mess my device up...
[AT&T Samsung Galaxy S 4 Android Development] finneginsfast:
I've been on the latest release from day one and not had a single issue at all personally.
[AT&T Samsung Galaxy S 4 Android Development] number16:
hey guys I need a bit of help.

I've used TWRP on my S2LTE, my S3, and now my S4, and never had this problem before. Not sure if it's because of 2.7 or not ...

Anyways, when I go into recovery now, if I wipe dalvik cache, it wipes no problem. But if I want to wipe cache, TWRP recovery crashes and reboots.

I can do system wipe, backup, restore but when I try to wipe cache it reboots every single time.

I managed to flash new ROMs by doing 'factory reset' (which I thought would also wipe cache but somehow it works)

same thing if I try to 'fix permission' ... recovery crashes and reboots.

My phone (and ROM) works perfectly fine otherwise.

Anyone had the same problem?
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
People seen to have fewer problems with this version http://xdaforums.com/showthread.php?t=2441196

Sent from my Nexus 5
[AT&T Samsung Galaxy S 4 Android Development] C13v3r0n3:
Yo, is the loki_flash file supposed to stay in txt format or should it be changed to .c ?
[AT&T Samsung Galaxy S 4 Android Development] :
Yo... ? lol really the Loki_flash file isnt in text format to begin with?
[AT&T Samsung Galaxy S 4 Android Development] rsmolen:
Working great for me! So excited for TWRP on the AT&T S4!
[AT&T Samsung Galaxy S 4 Android Development] _eroz:
When you download it from the link provided by romracer, it downloads to a windows computer as a .txt file.
[AT&T Samsung Galaxy S 4 Android Development] C13v3r0n3:
^ what he said, im guessing because im on windows it changed the file extension.
[AT&T Samsung Galaxy S 4 Android Development] romracer:
No, it should be "loki_flash". This is your browser and Windows defaulting to a .txt extension for a file with no extension. Technically it doesn't matter, but if you leave it as "loki_flash.txt" make sure you use that same name in the other steps. Or rename the file.
[AT&T Samsung Galaxy S 4 Android Development] :
Thanks all done!

or not....

It says booting into recovery then restarts and boots up the phone -_-
[AT&T Samsung Galaxy S 4 Android Development] MrPlNK:
Rooting now then going to run this! Twrp ftw!
[AT&T Samsung Galaxy S 4 Android Development] C13v3r0n3:
Working, thanks rom.

---------- Post added at 11:08 AM ---------- Previous post was at 10:52 AM ----------

Are you rooted and on the most recent ota?
[AT&T Samsung Galaxy S 4 Android Development] CPA Poke:
Worked perfectly!!! First thing on my to-do was to make a Nandroid backup...and it also worked flawlessly.

Thanks for being so on top of this once [MENTION=4229979]djrbliss[/MENTION] dropped the exploit!
[AT&T Samsung Galaxy S 4 Android Development] MrPlNK:
Worked perfectly!

Thanks so much!

Now we play the waiting game for the roms :)
[AT&T Samsung Galaxy S 4 Android Development] C13v3r0n3:
Mine did this too,i was just pushing the wrong key combo.

turned the phone off> held volume up and home> held power> phone turned on> let go of power but continue to hole vol up and home and it should work for you.
[AT&T Samsung Galaxy S 4 Android Development] StolenVW:
You only need vol up and power to get into recovery
[AT&T Samsung Galaxy S 4 Android Development] c0ldburn3r:
Yea don't try to flash the att faux kernel, like a noob I did and you just get the triangle of death saying its not authorized att software.
[AT&T Samsung Galaxy S 4 Android Development] :
Lol he has to edit it and put the .lok file in it in order for it to work (to my understanding)
[AT&T Samsung Galaxy S 4 Android Development] c0ldburn3r:
:D I figured but hey I like to live on the edge and just be plain stupid. :eek:
[AT&T Samsung Galaxy S 4 Android Development] evodon84:
Moved the files to my phone and ran the commands in Terminal Emulator. Have recovery on my phone now :highfive:
[AT&T Samsung Galaxy S 4 Android Development] geoldr:
Worked! Thanks!!

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

Edit, can you somehow make the console in TWRP not output every time I use the touchscreen?
[AT&T Samsung Galaxy S 4 Android Development] burningembers:
shell@android:/data/local/tmp # ./loki_flash.c recovery openrecovery-twpr-2.50.1
.-jfleatt.lok
openrecovery-twpr-2.50.1.-jfleatt.lok <
./loki_flash.c[1]: /MSM8960_lpm.rc: can't execute: Permission denied
./loki_flash.c[2]: init.rc: not found
./loki_flash.c[3]: init.rc: not found
./loki_flash.c[4]: init.rc: not found
./loki_flash.c[5]: init.rc: not found
./loki_flash.c[6]: syntax error: '(' unexpected

It worked the first time, but when I rebooted to recovery it was the regular Android Recovery, so I went back to try again and now it does this :(

edit: Just tried "# mount -o rw,remount -t yaffs2 /dev/block/platform/msm_sdcc.1/by-name/system /system", which worked to remount rw, but still no go... T_T
[AT&T Samsung Galaxy S 4 Android Development] evodon84:
Well unless you changed your filename you've got some spelling mistakes up there

you have "twpr-2.50.1" when it should be twrp-2.5.0.1

also should be just ./loki_flash not ./loki_flash.c as you have above

that might be your problem
[AT&T Samsung Galaxy S 4 Android Development] twcobra:
2.7.0.0 had some issues make sure you are on 2.7.0.1. Everything has been working for me.
[AT&T Samsung Galaxy S 4 Android Development] number16:
Hmm now I'm having the weirdest problem!!!

I flashed twrp 2.5.0.2, and after I reboot into recovery somehow I end up in download mode. Tried a few times and I can't reboot my phone in system, recovery, always end up in download mode.

Scared the heck out of me, so I flashed the recovery again via ODIN, and afterwards I could boot my phone normally. I thought I just had a bad flash.

Reboot into recovery, and all of a sudden I end up in download again!!!!

Any advice??
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
What firmware are you on? I'm assuming you have an i337 and are on mdl.

Sent from my Nexus 5