yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] sholsten:
I installed the OUDHS Recovery yesterday and now either one of these will install.I'd love to have Loki'd TWRP. My phone has the same UCUAMDL
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
If you use either of these please let me know if it works for you.
[AT&T Samsung Galaxy S 4 Android Development] pakxelaos:
Respond to sholsten

You mean Neither will work,

It didn't work on mine.
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Ill recheck script when I get home. Worked on test devices prior to posting. Please post error messages here. ^^^^ already have yours
[AT&T Samsung Galaxy S 4 Android Development] sholsten:
Neither seemed to have have installed on mine. It has the same one I installed in my above post yesterday.
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
What message did you get on tool after it ran
[AT&T Samsung Galaxy S 4 Android Development] ilanoraa:
Did uninstall the recovery.sh file?
[AT&T Samsung Galaxy S 4 Android Development] mostyle:
Fixed

On the line that issues the remount command there occurs 'Permission denied.'

In your batch file change line 25:

so that it reads:

Of course this assumes you are rooted.. :)

EDIT:

Still getting an error 'Failed to open aboot for reading'

I'm investigating.. Hang on.
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Will change and repost in a few
[AT&T Samsung Galaxy S 4 Android Development] MrPlNK:
You could just install goomanger and install twrp thats been lokified directly from your rooted s4
[AT&T Samsung Galaxy S 4 Android Development] sholsten:
Finished Rebooting into TWRP

Have a nice day!

adb is not recognized as an internal or external command, operable program or batch file.

Press any key to continue
[AT&T Samsung Galaxy S 4 Android Development] mostyle:
Here's the fixed script..

Just had to su -c all of your commands...

Hope that helps. Tested it here and it works fine.. :)
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Will update and repost in a few thx

EDIT

Ok updated script new links are up let me know if its working for you now
[AT&T Samsung Galaxy S 4 Android Development] kano45:
How do you find the correct TWRP?
[AT&T Samsung Galaxy S 4 Android Development] djoutrages:
Just tried this with TWRP worked beautifully, thank you very much!! :good:
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Make sure to thank mostyle for the script assist. Thanks bro
[AT&T Samsung Galaxy S 4 Android Development] rfb813:
So if I understand this will allow you to flash a Rom that has not been Loki'd and it will loki it and allow it to boot with either TWRP or CWM?
[AT&T Samsung Galaxy S 4 Android Development] fjr1300sgs2:
TWRP worked great for me. THANKS
[AT&T Samsung Galaxy S 4 Android Development] easybucketz:
Thanks a lot dude
[AT&T Samsung Galaxy S 4 Android Development] twcobra:
Worked llike a charm. I had my shinny new S4 rooted in under a minute.

Beer money sent bhp090808 XD. Confirmation number: 0P282098WE167102C
[AT&T Samsung Galaxy S 4 Android Development] chaplain:
+1. Once I got the unfortunate Win7 x64 problem figured out, this was by far the easiest root since I started w/Android with my Cappy in 2010.
[AT&T Samsung Galaxy S 4 Android Development] jrodsep:
Two questions:

Does this work with windows 8? I have the drivers and everything installed.

If I use the return to stock option via Odin, will it remove the custom padlock screen and return the status to official?

Thanks
[AT&T Samsung Galaxy S 4 Android Development] remf4i:
So this will not work and no root for MF3 ?
[AT&T Samsung Galaxy S 4 Android Development] Youngbloodx:
Hello, I just bought this phone yesterday and now I'm trying to root it. I've installed the drivers, set usb debug on and allowed unknown sources. This is what the script reads when I use this tool...

Pushing root tools...

pkg: data/local/tmp/Superuser.apk

Failure [INSTALL_FAILED_ALREADY_EXISTS]

Rooting phone...This may take a few minutes

Failure.

Cleaning up.. blah blah blah.

I'm using the cord that came with the phone. Any suggestions?
[AT&T Samsung Galaxy S 4 Android Development] PeartFan40:
Mines rooted l...mf3
[AT&T Samsung Galaxy S 4 Android Development] remf4i:
After i do step one to root I'm getting superuser binery can not be updated, so superuser isn't working so won't let it install the recovery
[AT&T Samsung Galaxy S 4 Android Development] dled1286:
i get stuck at "daemon started successfully". Ive enabled debugging, ive installed the drivers, ive wiped the phone several times and nothing.
[AT&T Samsung Galaxy S 4 Android Development] atawfikee:
UCUAMF3 help root

does this method work on I337UCUAMF3 ? if it doesnt where is one that does work?
[AT&T Samsung Galaxy S 4 Android Development] remf4i:
I tried 4 times and superuser binary won't update so idk if I'm doing something wrong or if it just don't work ,I can't figure it out.
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
If your on mf3 this tool won't work. Have to use manual method
[AT&T Samsung Galaxy S 4 Android Development] jrodsep:
What's the correct way to install Super SU and delete superuser?
[AT&T Samsung Galaxy S 4 Android Development] chaplain:
You have a computer problem, not a phone problem. It's the same problem I had, running Win7 x64. If you can download the tool onto an XP machine, download Kies & install the drivers, the tool will root the phone in less than 30 seconds. I wasted almost a whole day before I googled "daemon started successfully". Moved from the Win7 laptop to the XP desktop, and everything was fine.
[AT&T Samsung Galaxy S 4 Android Development] mrnifty:
Works great. Thank You!
[AT&T Samsung Galaxy S 4 Android Development] jrodsep:
Rooted, Installed Custom Recovery, made a backup and flashed Kangabean in a little over 20 minutes. This tool rocks.
[AT&T Samsung Galaxy S 4 Android Development] HiDEFF:
Noob here.. I'm new to S4 and I'm about to use this tool/method but before I do, I have some quick question:

1. Can I flash

any

rom once I've used this tool?

2. The full version of this tool will allow me to return to stock in case I need to return the phone??

Thank you in advance for you help and patience with silly questions like these.
[AT&T Samsung Galaxy S 4 Android Development] HiDEFF:
Any chance you could answer my previous questions?

Again, thank you for taking the time.
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
If your on mdl or mdb then yes to your questions. If your on mf3. No to all your questions
[AT&T Samsung Galaxy S 4 Android Development] HiDEFF:
Thank you. about to try it out.
[AT&T Samsung Galaxy S 4 Android Development] sam.balia1012:
so there is no way to flash a custom recovery (cwm or twrp) for sgs4 i337 MF3 build?

i could use the help, want to surprise the wife with new phone & awesome rom:o
[AT&T Samsung Galaxy S 4 Android Development] hovax615@hotmail.com:
There's a recovery for mf3 build called safestrap look into that along with kingo one click root.
[AT&T Samsung Galaxy S 4 Android Development] sam.balia1012:
i already rooted it using Jortex exploit

safe-strap is a permanent recovery fix? should i wait

the phone is factory unlocked...does att still lock boatloader even if factory unlocked?
[AT&T Samsung Galaxy S 4 Android Development] remf4i:
Delete
[AT&T Samsung Galaxy S 4 Android Development] A_Mateen10:
Problem rooting phone

Hey guys, so i am having quiet the weird problem rooting my s4. Using this tool, i was able to root my phone 3 or so months back. Apparently after installing a custom rom or something, phone had issues and i had to clean it. Now the root is gone and all and i was trying to get the root again but this tool somehow is not working for me. Funny thing is other than the root, i tried to odin to stock as well but it would fail right away. Any idea what might be causing this? It goes to the rooting thing but near the end it says failure in root and when i reboot my phone, it doesn't say custom anymore and also root don't even work. What can i do? I really want to install a custom Rom. :/
[AT&T Samsung Galaxy S 4 Android Development] twcobra:
My guess is you may have used something like triangle away and killed the recovery and root. Or something else weird happened. In either case you will most likely have to odin back to stock then try rooting starting from scratch. Believe me I have been there before.
[AT&T Samsung Galaxy S 4 Android Development] A_Mateen10:
I understand that but remember i am also having problem with odin to stock thing. I tried 2 different versions of odin as well as downloaded the tar file from 2 different places but as soon as i hit start on odin, takes about 2 seconds and fails. That's what i don't understand. I have done the odin thing so many times before but apparently, it doesn't seem to work here
[AT&T Samsung Galaxy S 4 Android Development] MattMJB0188:
Jan 2, 2014 - Tool still works great with MDL firmware. :D
[AT&T Samsung Galaxy S 4 Android Development] tsmith154:
Hello everyone. This tool works great and I have the AT&T i337ucuamdl. I am just having that problem when the sim card is not recognized. I have read until I am blue. I am just going to use the AT&T warranty to get the phone fixed or replaced. Since I used this tool to get it rooted and have used multiple roms (Thank you for all your work) I thought I would use this tool to put my phone in a condition where when sent in the warranty is useful again.

Every time I go to download the tool I get stuck on 70% or 80%. It never finishes the download. Any thoughts why?

One more question: When I run this tool do I still need to set the "thing" that tells how many times I flashed this phone to 0? or when I use this tool it will set everything back to stock with a 0 flash count.
[AT&T Samsung Galaxy S 4 Android Development] gotgame740:
same problem

I literally had the same exact problem with my s4. I'm pretty sure our build numbers are the same, too. I would check but I literally just started using the replacement phone that AT&T sent me. I guess using this tool or flashing one of these roms messed up the phone somehow :(.

Before I called AT&T about the warranty, I was having the same concerns as you about flashing the phone. But from everything I read all AT&T does is check for physical & liquid damage, then send the phone out to Samsung for repair. In this case, it wouldn't matter what you did to the phone software-wise since Samsung would just reflash it. I'm hoping this is the case, because I flashed it back to stock but I didn't unroot it. Also, the custom image was still showing at startup.

I'm about to mail this phone back tomorrow. I'll let you know if I run into any problems with the warranty. I even read multiple reports of people saying they even sent in bricked phones and had no warranty problems.

But reading this makes me not want to flash this new phone I have, because it looks like maybe this is the cause
[AT&T Samsung Galaxy S 4 Android Development] tsmith154:
Hey thanks for sharing your experience. I am very interested to see what happens with your situation. About 4 hrs. ago I just put a new sim card that AT&T mailed me into the phone. With in the first 30 min I had that problem again. I called and the rep. said to turn the phone off again and wait 2 or more minutes. So I did and it has been 6 hrs. since running this new card with no problems. I will post when the when the sim card is not recognized.
[AT&T Samsung Galaxy S 4 Android Development] tsmith154:
Well, this test did not last long. Just had the problem. Needed to reboot. Ok, I just finished returning this phone to 100% stock and at the moment I am updating using the stock AT&T update. I am sad to loose my flashing ability. Well, I will post to report if this fixed the problem. If not, I will have AT&T replace the phone. I do wonder if I need to reset the flash counter or if the full Odin version specific for this AT&T phone (only) phone took care of that for me.

Well it has been about 7 hrs. with the stock rom. I truly hate the stock rom. Slow, eats the battery, cram packed with bloat... It has not asked me to reboot yet...
[AT&T Samsung Galaxy S 4 Android Development] tsmith154:
Well, I had to replace the phone to get the problem to go away. I had no problems with AT&T with getting the new phone and now I have the new phone and I really see what have lost. Those custom roms compaired to the AT&T bloated rom, well "custom" rules. Stock rom: slow, bad battery life, so much bloat, oh did I say slow well I meant it...

I have been reading on how to root the: i337ucufnb1 phone. Yikes. I realize once I understand and do root my phone it would be easy to do again. But I read the instructions and complete forum over and over again but I still am shaky on what it all entails. It sounds like you are running a rom inside the stock rom. I am probably wrong but I am not sure. I hope there will be a direct root method for the nb1 phone soon.
[AT&T Samsung Galaxy S 4 Android Development] cutmylifein2:
my phone is android 4.2.2 and firmare version i337ucuamdl.. can i use this root and then flash asop roms?
[AT&T Samsung Galaxy S 4 Android Development] Reinaldo33897:
Yes you can it will root. My suggestion is also find the stock mdl image. I use this root to root my phone and Odin with mdl image to unroot when I screwed phone up. Whatever you do don't let att update your stock rom past mdl. The mdl s4 is Gold. Can screw it up and unroot and root as often as you want.

Read, learn, and flash away if you need to update modem look for RockRatts post of flashable modems.
[AT&T Samsung Galaxy S 4 Android Development] dmb219:
Good advice. I pull the sim card until I get rooted & get a ROM installed.
[AT&T Samsung Galaxy S 4 Android Development] Reinaldo33897:
No need to pull Sim card just shut down data and wifi
[AT&T Samsung Galaxy S 4 Android Development] kano45:
Confirmation - TWRP version working on i337 UCUAMDB

Completed a backup successfully. Haven't flashed a rom yet tho.
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
This is just a tool to install recovery. The cwm is the lokifyed version. The twrp is the original .lok posted might have to update it after installation. This is just an easy one click to help ppl install recovery

EDIT:

Ive updated these to a 3 in one tool. Tool can now root or install recoveries all in one place. Might add more features down the line.

Double Edit:

Twrp updated to 2.5.0.2 auto loki. Updated tool link is in OP. So now both recoveries are auto loki.:cool:
[AT&T Samsung Galaxy S 4 Android Development] BIGSx420:
how can i switch to the auto loki recovery? i used the tool before it was updated with the auto loki versions
[AT&T Samsung Galaxy S 4 Android Development] iKat:
Phew. This was a lifesaver, thanks man.
[AT&T Samsung Galaxy S 4 Android Development] mrwhsskers:
unable to root

i have been trying to root my s4 for 3 days now to no avail. i did not try to root at all until after the att ota update was installed on phone, version ending in mdl. the latest samsung drivers on on computer and computer recognizes phone in device manager as an adb interface. I make sure usb debugging is on. when I run the bat file all the command lines read: adb is not recognized as an internal or external command, operable program or batch file.

Do I need to delete samsung drivers and reinstall, odin back to the original firmware that was not updated???

I am at a loss and any guidance is appreciated.
[AT&T Samsung Galaxy S 4 Android Development] Tckwhaley:
about to flash cwm lokifyed was wondering if i could just flash task650 aokp rom with this recovery?

Im a sorta noob. so please dont bash.
[AT&T Samsung Galaxy S 4 Android Development] rfb813:
Don't see the updated Twrp 2.5.0.2 in the OP, just the 3 way tool. Opened the three way tool and didn't find Twrp. I am already rooted and have the loki'd Twrp installed via goo manager. What do I do next?
[AT&T Samsung Galaxy S 4 Android Development] sumnerm1:
F ing awesome! Been waitng for an easy method for CWM, and this is it!

Making a nandroid now, flashing will now commence :laugh:
[AT&T Samsung Galaxy S 4 Android Development] kleeman7:
If you are using twrp you can use goo manager to update open recovery script (twrp).
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Or just download updated tool choose option 4 and viola
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Yes you can
[AT&T Samsung Galaxy S 4 Android Development] cantwin:
Has anyone from Canada tried to use this tool? Im on MDJ, would prefer not to brick my brand new phone :)
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
For at&t i337 only. Root would work recovery will brick
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Your not pulling the bat file out of the folder are you? If you are put it back in and try again from there
[AT&T Samsung Galaxy S 4 Android Development] rfb813:
OK I when I unzipped I didn't see TWRP so I thought it was missing. When I ran the tool I gave me the options. Ran option 4 and Twrp installed. Had to watch the phone since it asked for permissions. So I will test the new Twrp with auto Loki. The OP is much clearer now on how to install.

Thanks
[AT&T Samsung Galaxy S 4 Android Development] cantwin:
My phone is SGH-I337M. Can i do both root & recovery? Is there an option to do one without the other?
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Just choose option 2 to root. recoveries are for att only im working on a canadian compatible tool will release soon
[AT&T Samsung Galaxy S 4 Android Development] cantwin:
Understood, appreciate the quick response!
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Need some canadian variant testers pm me if interested
[AT&T Samsung Galaxy S 4 Android Development] mrwhsskers:
nope, just opening folder and clicking on run_me bat file.

as an aside, not related to any of this, I would like to express my gratitude to all the US armed forces past and present for the freedoms they have allowed us all to have.

now back to reality, thanks for your response. I am wondering if i should odin back to the original firmware or not, this is baffling.
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Try reinstalling samsung drivers and or using a different usb cord or port. Those are always common problems
[AT&T Samsung Galaxy S 4 Android Development] mrwhsskers:
ok, will delete current drivers and reinstall . have been using usb cord that came with phone and connecting directly to computer usb port, not thru a hub.
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Uploading next update now added option to odin back to stock
[AT&T Samsung Galaxy S 4 Android Development] mrwhsskers:
finally got root and able to install cwm. left phone connected to computer then rebooted computer after reinstalling samsung drivers. all worked after that. many thanks, now the fun starts...
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Tool and OP updated:cool:
[AT&T Samsung Galaxy S 4 Android Development] rfb813:
Installed Twrp with auto Loki with the tool. Whenever I flash a Rom I get a screen with a yellow triangle and the statement that an unauthorized software is trying to install and the Rom will not boot. When I go back into twrp and install a loki'd Kernel and reboot it boots fine. It appears I am not auto lokied. I had Twrp installed before but used the tool to update it. I have tried to flash tmo and i9505 Roms.

Edit: Tried this: I was initially installing from the MOAB Deodexed MDL Rom, I went back and restored the Stock Rom. In the stock Rom I still had install-recovery.sh. I removed it and rebooted and reran the tool. Will see what happens.

Edit 2: Tried to install a tmo Rom and got the same screen. The note at the top said kernel failed.
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
First ive heard of this pulled image directly from goo manager which is advertised auto loki. Ill look into it and get back. Until then run cwm it is tested and confirmed auto loki

EDIT:

Just confirmed that Twrp does not auto loki patch roms and kernels at flash. Sorry was initially misinformed. You will have to flash a loki patched kernel after each flash. There are many available. If and when a twrp that does auto patch comes available I will add it. Or just use cwm it does auto patch
[AT&T Samsung Galaxy S 4 Android Development] hamzer11:
I haven't run the tool yet but does using the back to stock feature take it to MDL or MDB? Also, does that wipe data or will all settings, apps, and data stay in tact?
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
MDB and will not wipe data
[AT&T Samsung Galaxy S 4 Android Development] BigE:
Twrp does not auto loki patch roms and kernels at flash

+1.

Had issues replacing a kernel. CWM is the better solution, even if not eye candy.
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
attn1 posted this in the Loki thread it seems it might help. Its not quite "Auto" but its pretty close. I have not tried it, but it looks promising. All credit goes to attn1. Maybe someone can try and see if it helps.

http://tau.shadowchild.nl/attn1/?p=483
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
This does work fine but is still that one extra step. With it built into cwm it feels like the device is truly unlocked. Is another great option along wit flashing a patched kernel after each rom flash
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
I agree with you and use CWM myself, but I think for people that just want to keep TWRP (for whatever reason), this might be the closest thing to "auto" TWRP they are going to get.
[AT&T Samsung Galaxy S 4 Android Development] desilva79:
Noob here , we must remove the install-recover.sh in system/etc before running the updated tool ?

Thanks...
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Yes. Eliminates future problems with recovery flashing issues
[AT&T Samsung Galaxy S 4 Android Development] desilva79:
Thanks bhp090808. I just checked it with Root Browser and I don't find it on my system>etc>install-recover.sh . The only thing I did with this phone was root it with Motochopper exploit.
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Then you should be good
[AT&T Samsung Galaxy S 4 Android Development] mrwhsskers:
I too am looking for the Install-recovery.sh file in system/etc. I was able to root and install cwm. i am using es file explorer and even using the search tool in it, i can not find the file to delete. if i can not find and delete file will this prevent me from installing future roms and performing backups and recoveries?? ok found file,but when i go to delete says file can not be deleted. Finally got it, had to enable root explorer and set system folder to r/w. file now gone.

thanks again for all the help
[AT&T Samsung Galaxy S 4 Android Development] odinfire:
OH NOOOOOO!!!!! This worked, and I have CWM on my S4! Now the never ending flashing will begin. Thanks a lot. /sarcasm /sorta :)
[AT&T Samsung Galaxy S 4 Android Development] desilva79:
Where did you find it ? I've been looking for it but I cannot find it. I know I didn't delete it.
[AT&T Samsung Galaxy S 4 Android Development] ryanshapiro44:
May be a noon question but I installed twrp and now wanna move to cwm for the rom I'm going to use how can I go about this? Tried just doing option 3 but doesn't seem to flash anything. Thanks in advance for any help
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Just download the recovery flashable cwm zip from shabbypenguins thread and flash in recovery
[AT&T Samsung Galaxy S 4 Android Development] mrwhsskers:
it is in the system/etc folder.
[AT&T Samsung Galaxy S 4 Android Development] Monsterfox50:
Hey guys. I haven't really been scouring the threads lately just been waiting for a nice one-click. Question is has this been confirmed to work on UCUAMDL yet?
[AT&T Samsung Galaxy S 4 Android Development] azz72:
Hello need help !!!! I had twrp then switched to cwm, then I flashed twrp again now I have no recovery on my phone and I get this yellow triangle when I try to go to recovery mode. Do you think this will work????????
[AT&T Samsung Galaxy S 4 Android Development] desilva79:
Thanks , that's was the first place I search , don't have it in there. I hope I'm okay.