yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] bstylz911:
so i had the recovery SS and tried flashing this recovery but never works. says the installation is good but when going into recovery its still the SS recovery.
[AT&T Samsung Galaxy S 4 Android Development] beast3300:
That's the only recovery you can use (SS)
[AT&T Samsung Galaxy S 4 Android Development] bstylz911:
but before i had ss recovery, i had oudhs recovery
[AT&T Samsung Galaxy S 4 Android Development] stl-soldier:
Did you take the OTA update to 4.3 or 4.4.2 from your carrier?
[AT&T Samsung Galaxy S 4 Android Development] mejakola:
bad mojo,

ok its really simple right?

download, put it on the sd card, recovery, apply update. done

was i supposed to have something else installed?

my phone got wiped all the way down to out of the box setup...

im trying to flash on of the kitkat roms, but i dont think thats going to happen today

i backed up everything on titanium backup just before, but now i cant restore.
[AT&T Samsung Galaxy S 4 Android Development] gorgy76:
what version of rom or firmware is your phone now? stock with ota update? What bootloader? Do you have a custom recovery already?
[AT&T Samsung Galaxy S 4 Android Development] mejakola:
mk2, stock ota 4.3

bootloader idk

i do now lol

GUESS WHO FORGOT TO INSTALL SAFESTRAP XD

that has been my biggest noob moment yet.

got it fixed
[AT&T Samsung Galaxy S 4 Android Development] jotade:
Hi everyone im tryying to install a Custom ROM on i337 ATT with rooted mk2 but there is no way i can go into the cwm is there a simple way? Thanks if you can help me let me know please
[AT&T Samsung Galaxy S 4 Android Development] ronnie498:
If you are using safe strap the answer is unfortunately no.
[AT&T Samsung Galaxy S 4 Android Development] jotade:
Im not using any of that. I just want to flash cm11 thats why i didnt install safe trap. But all methods are not working for me
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
You need to do a lot of reading. You can not install CM on MK2. The best you can do is use safestrap to install the tested and listed compatible TW Roms listed in the safestrap thread.
[AT&T Samsung Galaxy S 4 Android Development] jotade:
Ok thanks i will
[AT&T Samsung Galaxy S 4 Android Development] svs57:
I337 MDL BL

Am I correct that with this recover I can install any custom 9505 kernel?

I use LOKI KT kernel now. But want to try others.
[AT&T Samsung Galaxy S 4 Android Development] s8freak:
I'm on MDL as well and I flash i9505 kernels and Roms but I prefer T/W so I've used Adam, Alucard, and talexop. I'm on Adam now all 3 are very good stock kernels. Even though Shabby Penguins auto-loki's I guess I've made it a habit to flash the loki-doki zip as well its just to make sure.

"All we know is...He's called the Stig!"

Sent from my AT&T SGH-I337
[AT&T Samsung Galaxy S 4 Android Development] hamzer11:
I have been on OUDHS recovery from the beginning but am also finding issues at times with the nandroids. Especially since 4.3. Was now getting ready to flash Goldeneye 4.4 but need to update the recovery at this point. Does any other recovery auto-loki? What do most you guys do, just keep the loki-doki zip and flash after anything that isn't loki'd? Also curious if I go to CWM or Philz CWM variant, would my nandorids from OUDHS still be recoverable?
[AT&T Samsung Galaxy S 4 Android Development] Adizzzle:
Can I still use this Recovery even if I

don't need Loki Doki??

I read that it auto-loki's kernels, but I

have never needed to use loki seeing as

my bootloader is unlocked.
[AT&T Samsung Galaxy S 4 Android Development] highaltitude:
That I'm not sure. I do have USA AT&T SGH-i337 so I use loki so I like the recovery. It may not work for everyone.

Sent from my GT-I9505 converted SGH-i337 w/XDA Premium 4 mobile app
[AT&T Samsung Galaxy S 4 Android Development] Adizzzle:
Hmm I don't want bork my phone here

So hopefully someone else might know.
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
What device do you have? If you're looking for a touch cwm there's probably one for your device
[AT&T Samsung Galaxy S 4 Android Development] Adizzzle:
I have an I337M Canadian variant.

It has an unlocked bootloader

And I have tried CWM I was just curious

If I would be able to use this for a

certain ROM
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
Why would you need this for a certain rom and not cwm. If you use shabby's version it won't Bork your device. I'm not sure though if the rom would flash correctly for your device. I think it would, but not sure.
[AT&T Samsung Galaxy S 4 Android Development] Adizzzle:
I'm attempting to install the latest MIUI - jflte

for my device, but everytime I flash it, I lose

Mobile Data and WiFI.

I can fix the WiFi with a kernel, however I can't

get Mobile Data to work at all, and I was trying

to see if it was my recovery causing the issue..

Anyways long story short: All the latest MIUI

builds have this issue on my device, however

the MIUI 4.4.11 build worked for me 100%!

Cheers
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
I haven't seen a miui rom that doesn't have issues. I doubt it's your recovery.
[AT&T Samsung Galaxy S 4 Android Development] Adizzzle:
It was indeed my recovery.

I installed the GT-I9505 CWM

Recovery, flashed MIUI and got

WiFi and Mobile Data to work!!!

Finally!
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
Cool glad you got it to work. And I learned something too
[AT&T Samsung Galaxy S 4 Android Development] svs57:
Can anybody create kernel with exFat support for this recovery?
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
Dont use this recovery, its old and outdated. Cwm has autoloki and all the other features
[AT&T Samsung Galaxy S 4 Android Development] robbinh00d:
Anyone ever have to fight with this?

Currently running:

Stock

Rooted using Kingo's method

Android 4.2.2

Baseband MDL

Recovery = OUDHS CWM Touch 1.0.3.4

So I'd love to backup directly to external SD but it's not seeing it....and cannot mount it.

Any ideas?

Just probing. Thanks in advance!!!
[AT&T Samsung Galaxy S 4 Android Development] jthrasher47:
As the creator of this recovery stated right above your post do not use this recovery switch to either clockworkmod or TWRP and you will not have any of those issues

This recovery is almost a year old and has not been updated
[AT&T Samsung Galaxy S 4 Android Development] Venom0642:
Question My friend just curious are you ever gonna update this Custom Recovery for KitKat just Curious, If this was asked already then i missed somewhere lol, Another Question since i am still on this recovery on KitKat i saw post above you say it's outdated which i already know this my question is where is this CWM Recovery that has Auto-loki never seen it got a link for this CWM Auto-Loki you mention that's for the AT&T Thanks! :good:
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
no, i stopped development on it months ago. regular cwm for this variant is built with auto loki already enabled.
[AT&T Samsung Galaxy S 4 Android Development] Venom0642:
I can't find regular cwm Auto Loki for AT&T can you direct me to it please thanks[emoji106]

Sent From My Galaxy S5 SAMSUNG-SM-G900A Running On New Deadly Venom v4.0.0 KitKat 4.4.2
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
http://clockworkmod.com/

or rom manager app.
[AT&T Samsung Galaxy S 4 Android Development] Venom0642:
Thanks i see it but how would i flash this if it's only Recovery Image Any Ideas Thanks!
[AT&T Samsung Galaxy S 4 Android Development] stl-soldier:
Edit. Too slow.

I still use this recovery and don't have any problems with it. The latest ROMs flash fine.

---------- Post added at 07:52 AM ---------- Previous post was at 07:46 AM ----------

Rename it to Recovery.img and replace the one in another recovery ZIP file with it.
[AT&T Samsung Galaxy S 4 Android Development] Haphim:
I originally used this recovery for CM 10.2, and it worked beautifully.

Is there any reason I shouldn't use it to flash KitKat (CM 11) or Lollipop (CM 12)?

Is there another recovery that I need to (or that's worth) changing over to?
[AT&T Samsung Galaxy S 4 Android Development] Night AoX:
Hi Shabby ;)
[AT&T Samsung Galaxy S 4 Android Development] AxAtAx:
Thats weird, I did mine and I am on MDB...worked perfect...what would be the consequence if I didn't have MDL?

Or am I to understand, to flash anything after this I would have to be on MDL and patch with .lok?
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
either will work, dan made it so both work currently :)
[AT&T Samsung Galaxy S 4 Android Development] stevehkim:
Woot woot i have recovery. Thank you.

ATT S4 Rooted. Beastin.

4.2.2
[AT&T Samsung Galaxy S 4 Android Development] cshort0982:
Flashed recovery and flash kernel We are cooking with gas now!
[AT&T Samsung Galaxy S 4 Android Development] Hippoman13:
Oh wow, I didn't see. Thanks!
[AT&T Samsung Galaxy S 4 Android Development] DJsCrIBbLe:
So do we extract both cwm.Loki zip and the Loki.flash.zip.. and where do the extracted files go for the terminal commands to work?
[AT&T Samsung Galaxy S 4 Android Development] stevehkim:
Put the extracted files in /data/local/tmp

ATT S4 Rooted. Beastin.

4.2.2
[AT&T Samsung Galaxy S 4 Android Development] _eroz:
I think he is talking about the recovery.lok and loki_flash, I'm not sure either but I'm going to assume it is wherever adb is installed on your computer.

then when you run the adb terminal commands, they will get pushed to /data/local/tmp folder.
[AT&T Samsung Galaxy S 4 Android Development] StolenVW:
Volume up and power to get in recovery
[AT&T Samsung Galaxy S 4 Android Development] iSaint:
Rainbow mode does not disappoint :)
[AT&T Samsung Galaxy S 4 Android Development] mcmb03:
is it possible for you to fix where CWMR thinks the external sd is? it's kind of a pain to not be able to back up to by external sd :(

currently is looks at external_sd as the directory where in the TouchWiz system, it's located at ExtSdCard (i think that's the right name)
[AT&T Samsung Galaxy S 4 Android Development] StolenVW:
I made a nandroid to my external sdcard no problems
[AT&T Samsung Galaxy S 4 Android Development] mcmb03:
how? when I select backup to external sd, it says something along the lines of backup failed, then something about not being able to mount the sd, but I can confirm my external sd is working 100% and formatted correctly
[AT&T Samsung Galaxy S 4 Android Development] StolenVW:
Went to backup and restore then selected backup to external sdcard
[AT&T Samsung Galaxy S 4 Android Development] Phoneguy589:
Can someone post which extracted files to put where from my rooted phone. .. like a guide. Sorry I'm away from home and no computer. ... I'm impatient and don't want to wait until Saturday night. Lol. I appreciate any help. Thanks for everyone's help.
[AT&T Samsung Galaxy S 4 Android Development] jsmith8858:
you don't have time to read the OP?
[AT&T Samsung Galaxy S 4 Android Development] DJsCrIBbLe:
Never mind I noticed that when extracted you still have to grab the files from inside the folder. Placed em in data/local/tmp and used terminal on my phone and ran the command and it worked beautifully:D

Thanks op
[AT&T Samsung Galaxy S 4 Android Development] greekunit690:
Download loki flashable recovery and loki flashing utilities from op extract them, push to /data/local/temp. Open terminal emulator and past this...

su

chmod 755 /data/local/tmp/loki_flash

/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok
[AT&T Samsung Galaxy S 4 Android Development] evodon84:
Also if you don't have access to a computer, you can use a file manager to extract and then move the files to the correct folder listed above then use terminal emulator to run the commands

sent from tapatalk
[AT&T Samsung Galaxy S 4 Android Development] stevehkim:
How are you guys getting TWRP to work?
[AT&T Samsung Galaxy S 4 Android Development] Southrice:
You still need to delete recovery.sh using this method correct?
[AT&T Samsung Galaxy S 4 Android Development] Phoneguy589:
Sorry about that, I was looking at it but when I saw adb I figured I needed a pc. Thanks for pointing it out bro. :beer:
[AT&T Samsung Galaxy S 4 Android Development] evodon84:
Im not sure as I actually installed TWRP which did not require deleting stock recovery. Not sure if this method requires it or not. I did do it all from my phone though.
[AT&T Samsung Galaxy S 4 Android Development] titaneds73:
evodon84 if you dont mind me asking did you install twrp using goo. or another method?and if so did you do all the steps in the op fist before installing twrp? thanks for response in advance
[AT&T Samsung Galaxy S 4 Android Development] evodon84:
If you go over to the TWRP thread RomRacer made a post with a loki'd TWRP zip file just download that and follow his instructions in his post. PM me if you have questions about what I did.
[AT&T Samsung Galaxy S 4 Android Development] mcmb03:
that's strange, i tried another 3 times, to no avail. are you stock still?
[AT&T Samsung Galaxy S 4 Android Development] titaneds73:
thanks for the quick response i will check it out now
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
Oops, I flashed the Verizon recovery instead of the AT&T. Will that be okay?

It seems to be working okay so far. Doing a backup of my old ROM.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
excuse me? good, enjoy twrp *******
[AT&T Samsung Galaxy S 4 Android Development] jayharper08:
No worries Shabby. Being handled, sir.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
updated to 1.0.3.4

What does that mean? well when recovery exits i can have custom scripts per device run. in this instance i have a bash script that grabs your current aboot, current boot.img. uses a special loki binary to patch them on the device, then it flashes the boot.img back.

as in when you leave recovery if you didnt have a loki enabled kernel you will. if its already patched? no worries loki handles that already. that means more options for you as now you can flash roms without having loki kernels much easier. keep in mind this runs at the end of recovery so your nandroid of stock will end up getting loki'd :P. i decided to use loki_flash instead of dd to prevent bad flashes if/when loki gets patched.

im leaving the thread open, i dont care if you guys prefer twrp (its an amazing recovery, go donate to dees_troy, seriously.. i have :P ), just keep this thread about this recovery. if rumors are true twp has its own thread :P

please keep in mind canadian users this is for the i337, if there is a want/need for a oudhs recovery that doesnt auto-loki i can make one for yall
[AT&T Samsung Galaxy S 4 Android Development] Phoneguy589:
You are awesome. . Thank You.
[AT&T Samsung Galaxy S 4 Android Development] kasper67:
Quick question cause I'm a little confused. Do I have to install Loki's flash and then run this recovery in adb or is it all taken care of when flashing this recovery? Sorry if I sound a little dumb asking. Thanks
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
with this recovery, you basically pretend as if you have an unlocked bootloader. it handles loki all for you :)
[AT&T Samsung Galaxy S 4 Android Development] kasper67:
Thanks for the quick reply.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
please keep in mind canadian users this is for the i337, if there is a want/need for a oudhs recovery that doesnt auto-loki i can make one for yall
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
shabbypenguin, thank you for your hard work and bringing this to the AT&T forum.

I installed the latest zip and it works fine, but when I choose "Reboot Now", I got a message that basically said, 'Rom may flash custom recovery on boot, Fix? and it gave "No", "Yes", "No". I looked around the forum about this and other threads said to say "Yes" so it will keep CWM upon boot, so I did. I then got a message that said, "root access possibly lost. Fix? I swipe left and it reboots fine and I still have root when it boots back up. I was wondering if you know why it is giving me these messages and what is the correct actions to take.

On a side note, the phone is showing the "Samsung Custom" unlock icon upon boot after I flashed this recovery and this is the first time I have seen it on this phone. It's not a big deal to me, but it is the only thing I done to the phone that would have caused it.

Any guidance will be greatly appreciated. Thanks.

***Edit***

I used to Mr. Q's method to originally root, which means I never actually has "Superuser" installed, instead I directly downloaded SuperSU from the play market (per method) and then updated binaries. I wonder if this version of CWM is checking to see if "Superuser is installed instead of SuperSU and that why it thinks I might not be rooted? I also wonder if I select "Yes" to CWM fixing root if it would mess the phone up? I'm going to keep looking.

***Edit #2***

I noticed the SuperSU Apk on my phone was ready for an update so I took the update. I then opened SuperSU and updated the binaries. The Apk asked me if I wanted to update the binaries manually or if I wanted my custom recovery to handle it. I chose to take the binary update manually. I then booted into recovery (CWM) to find that it did not display the "root access lost" message when I chose to reboot the phone. I am just guessing here, but I think CWM was looking for the updated binaries for SuperSU that I had not installed yet. It is all still strange because I came from The GS2 Skyrocket and CWM on that phone worked differently...none of the messages I got on this. If anything changes I will be sure to report it back here. If anyone has issues similar to this, please direct them to this post to see if their situation is the same as mine has been.
[AT&T Samsung Galaxy S 4 Android Development] Phoneguy589:
What if I go from touch wiz to aokp or vice versa? I'm guessing it takes it from just before reboot just figured I'd make absolutely sure. Thanks again.
[AT&T Samsung Galaxy S 4 Android Development] killer5000:
It works with tmobile rom thx
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
sorry i missed your initial issue, but yes cwm will detect if something is "wrong" with su and a few other things in an effort to try and make things a bit easier for ya. as it stands with 1.0.3.4 i also added an autoroot feature yanked from wil wheaton recovery that if it cant find su at all will offer to install koush's binary so you dont have to worry about it :)

correct, whatever kernel you have before you go to reboot will be the one hat gets loki'd up :)
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Thank you. Everything appears to be working well now. (Samsung custom went away, I guess it was SuperSU doing it?) I do think I owe you a beverage or 5. Incoming as soon as I remember how to log into my Paypal.
[AT&T Samsung Galaxy S 4 Android Development] Relys:
Nice job with the new update. I was on TWRP but auto-loki got me to try this out. Does this mean I can flash CM ROM directly from the nightly builds for the unlocked bootloaders?

Thanks again.
[AT&T Samsung Galaxy S 4 Android Development] jrollercoasters:
It means you can flash any rom you want! Its like being permeantly unlocked.. but your not lol
[AT&T Samsung Galaxy S 4 Android Development] acruxksa:
Anyone test this with an aroma installed ROM yet? Looking at the i9505 Omega Rom. Haven't decided if I will try it though because CM10.1 is working quite well at the moment.

I know the i9505 Omega Rom works if you install it and then install a loki'd kernel meaning auto loki should work, just not sure if the aroma installer would confuse the issue or not.

Thoughts on this Shabby?

Downloading Omega v3.0 for i9505 now, but it's 1.5Gb so it'll be a bit before I can test it.

The i9505 rom booted to setup just fine, will report back if I have any issues.

***Update***

Well, It's booting as I type this. I was mistaken though, the Omega v3.0 for i9505 does not use the aroma installer. I just assumed from it's size that it did.

Still a good question though, can auto loki deal with a rom if it uses the Aroma Installer.

***Update***

Omega v3.0 for i9505 requires a different baseband version than MDL so after it booted, I had hsdpa but no lte (there was no pta apn) I also didn't have wifi. However, I rebooted into recovery and installed KT's TW kernel for our phones and everything seems to be operating correctly. I did have to manually enter the apn settings for lte though, but that's not really a big deal.

Now back to CM10.1 ;D
[AT&T Samsung Galaxy S 4 Android Development] carlospr21:
i only need to flash CWM Flashable - OUDHS CWM-based Recovery 1.0.3.4

&

Loki flashable - OUDHS CWM-based Recovery 1.0.3.4

and im loki'd or just (CWM Flashable - OUDHS CWM-based Recovery 1.0.3.4)
[AT&T Samsung Galaxy S 4 Android Development] paleman27:
Flashed with twrp. Works great. So know when I hit reboot recovery in goomanager I get CWM.

I asume I can't use twrp recovery to do a nandroid backup anymore, right?
[AT&T Samsung Galaxy S 4 Android Development] tdevaughn:
twrp is working just fine for me.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
glad you got it all sorted :) unfortunately i have heard things of aroma not playing well with my recovery since i have touch input that clashes with aroma's i have yet to test it out myself but its on my todo fix list (auto loki was priority one for me :P )

if youve got recovery already flash teh cwm zip, if you dont i suggest flashing twrp in goo manager and then flashing the cwm flashable zip :)

not unless you flash it back to twrp
[AT&T Samsung Galaxy S 4 Android Development] mocsab:
(Man, it would be so nice if there was a way to use One Recovery like CWM - and be able to restore backups made in TWRP)

I have checked - and it doesn't appear that TWRP has been updated with "Auto Loki" as of yet - but I would imagine it is only a matter of time....
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
dees_troy has no intentions of adding it in, nor will it be going to regular cwm. both of them want a flashable zip for users after they flash a rom that patches.
[AT&T Samsung Galaxy S 4 Android Development] lilmikey201:
so does mean i can install any rom? with the loki kernel
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
within reason. i dont suggest flashing i9500 roms :P

this means you can flash things without worrying about loki, so tmobile roms no longer need to be unzipped patched and put back together.
[AT&T Samsung Galaxy S 4 Android Development] lilmikey201:
alright soo wen i install a rom do i have to flash a kernel everytime like i did with the htc vivid?
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
all depends i assume, you dont have to flash a loki kernel if you dont want to. but idk how close the att variant is to other variants, soon enough i imagine people will figure out what roms/kernels can be safely flashed to the att version. all this recovery does is make sure whatever kernel does get flashed it will be patched :)
[AT&T Samsung Galaxy S 4 Android Development] poofyhairguy:
Thank you for this. Now hopefully us AT&Ters and Canadians can stick together like originally intended.
[AT&T Samsung Galaxy S 4 Android Development] tokoam:
is it at all possible to completely disable the notification or feature all together at the end of installing a ROM it will ask you "ROM may flash stock recovery on boot" I mean i don't plan to change this recovery img anytime soon scince it auto patches and some custom roms alter this can we have it so its just on (yes- disable recovery flash) just so that no isnt accidentally selected.
[AT&T Samsung Galaxy S 4 Android Development] killer5000:
Do you think you with your next update you csn include automatically reflash recovery after it done installing a ROM. Don't get me wrong I love this recovery. I just would like to have that feature in the future when and if it can be put in it.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
ask the rom dev to remove system/etc/install-recovery.sh from tehir rom and you wont have that prompt :)

i dont understand what you mean by reflash recovery?