yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] jm1999:
Can anyone tell me what size the stock back ups will be before installing custom rom? I only have a 2 gig sd card at the moment and I am to broke to buy a new one. But I need this! Should I wait or is there a work around where I can store them some where else? Or do I even need to store it in my sd?
[AT&T Samsung Galaxy S 4 Android Development] Will822:
Backups will be between 2-4gb in size.
[AT&T Samsung Galaxy S 4 Android Development] mocsab:
No System/Etc/Install-Recovery File ???

I have a question that I thought you might help me with -

When I did the LOKI install the other day on a brand new phone for a friend who needed help - I searched for and could not locate the file "Install-Recovery.sh in System/Etc

So I went ahead and did the install using ADB - and it workded perfectly - He has flashed serveral roms since and all has gone well - no issues using your recovery.

I am wondering - why didn't the phone have that file in it? it was brand new phone - ? any ideas?
[AT&T Samsung Galaxy S 4 Android Development] ilanoraa:
Thank you, I did this the backdoor way. Emailed the two files to myself, moved to the folders above and flashed from the phone via terminal emulator. Doing a backup of stock system now. I have 64gb samsung memory card. I pretty sure you need to format the memory card (fat 32) to be able to save a CWM backup to the external hard drive. Nice work once again thanks. :D
[AT&T Samsung Galaxy S 4 Android Development] 8mileroad:
I have an AT&T i337, and am completely new to Android hacking other than installing a ROM on my HP Touchpad. Right now I find all of the instructions in every thread vague and confusing for someone like me. Once developer community towards the S4 gets settled in, will there be more user-friendly methods for flashing ROMs for the S4, or at least clearer instructions? Or does it tend to stay like how it is now? If in a month from now there will be clear directions and what not, then I'll wait until then until I try anything, that's why I'm asking.
[AT&T Samsung Galaxy S 4 Android Development] neo_styles:
[RECOVERY]SGH-I337 OUDHS Recovery - now with auto-loki

Instructions are pretty clear for flashing ROMs as they are now IMO. Follow the video instructions in the root thread, download and run the run.bat for this Loki-fied OUDHS recovery, download and copy any ROM of your choice from said recovery, and you're good to go. The ktoonsez kernel just improves some of the background work, but is not a requirement unless you are using a recovery that doesn't include the auto-Loki feature.

I would suggest searching YT for further instructions. Watch some vids on how to root and run a custom ROM for previous phones and it all should just click to you. If not, run stock and you'll still be fine.

What exactly are your reasons for wanting to run a custom ROM, if you don't mind me asking?

*edit* didn't realize the adb commands required for this recovery install. So long as you can copy/paste the commands in the OP, it's still just as easy.
[AT&T Samsung Galaxy S 4 Android Development] acruxksa:
This is the third device I've owned early in it's development, the other two also had locked boot loaders. (Nook Tablet and Atrix 4G). We're already well ahead of where both those devices were 1 month after their release. Things are moving very rapidly right now.

For clarity, we are not "hacking" android. The developers are. We are simply taking their work and applying it to our devices.

Confusing the issue for some users is the vast number of different model rom's (i337, T-Mo, i9505, and i1337m) we're now able to flash with OUDHS and auto-loki. If your new and absolutely feel the urge to flash, I would stick with the roms and kernels specifically designed for the ATT i337 until you become more familiar with the process. By sticking with these roms and kernels, you can follow the developers procedures exactly.

Also confusing the issue is the millions of new S4 owners (myself included) swarming XDA looking for a ROM that suits our needs and personalities.

With a phone as popular as the S4, I wouldn't expect development to slow down until the note 3 or S5 are released, however I do believe development will become more focused. Also, FAQ's will get more comprehensive as we learn what works and what doesn't.

Will things be clearer in a month? Absolutely.

Is there enough information out there to flash your new S4 now? Certainly. All I would say is that if you're new to android rom flashing, you shouldn't expect to pop onto XDA find a ROM and flash it minutes later. You NEED to spend some time reading and learning before you dive in. After researching you will have a better understanding of how the process works at the user level.

Realistically, NONE of this stuff should be posted in a development thread. Thankfully, shabbypenguin seems to recognize that this early in the S4's release, things are a bit hectic and there are a lot of questions.
[AT&T Samsung Galaxy S 4 Android Development] 8mileroad:
My apologies, I was considering making a Q&A thread but thought it would be unnecessary. I'll refrain from posting any more questions like these in development threads. I'll do my reading, of course. Thanks for the info.

I like the hybrid mode like on Paranoid Android, I want to get rid of Samsung bloat really badly, and I would like better battery life. Basically, I miss the stock jellybean from my Galaxy Nexus. Thanks for the response, I'll check out the videos.
[AT&T Samsung Galaxy S 4 Android Development] ilanoraa:
Reformat your card, this happened on my Note 8.
[AT&T Samsung Galaxy S 4 Android Development] sabre31:
Most likely your card if formated as exfat and that is your issue. How big is your card? Most newer cards come as exfat and formating to fat32 will allow recovery and countless other roms that are not samsung based to be able to see your card fine.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
i bolded that block of text because it truly is amazing how much you can really learn if you dedicate some time to reading up on stuff :) back on teh hero-cdma on sprint (my first android phone) i spent days reading which roms worked, what root was, what to do etc til i finally started to flash each and every rom finding the one i liked best. :)

but actually i dont mind questions etc in here, i try to make sure each release is as bug free as possible (sometimes i mess up too :eek: ) but i feel like im teh minority when i dont mind answering questions inside teh thread, any and all updates will be put in the OP and following posts as best as i can manage. i feel as though having multiple threads just clutters things up when instead myself or a helpful member (such as yourself) can answer a question just as quickly in here :)

my answer above isnt for every person on this forum, but everyone is always welcome in my threads :)

also wanted to thank everyone again for helping out with some of the other members. its great to a community thrive off being helpful :D
[AT&T Samsung Galaxy S 4 Android Development] Dallenn:
flashed from twrp, worked perfect. made a backup, all went well. gonna try a touchwiz rom maybe now, knowing i have a good backup to fall on.

thank you
[AT&T Samsung Galaxy S 4 Android Development] fix-this!:
thanks for this recovery, i didn't like twrp.
[AT&T Samsung Galaxy S 4 Android Development] Monsi:
its ok now
[AT&T Samsung Galaxy S 4 Android Development] Dallenn:
So i flashed this recovery from TWRP, all went perfect. Made a backup of Slim Bean without a hitch...

went to try the TW rom & kernel in the dev section here, got that all booted, set up, and backed that up so i could have a backup of each. Both backed up to external SD by the way.

Went to restore the Slim Bean from external SD, and MD5 Mismatch error kept happening. How can i fix that?
[AT&T Samsung Galaxy S 4 Android Development] dxwilliams40:
If you have a 2gb sd card it's not going to work for you. My backup is almost 5gb.
[AT&T Samsung Galaxy S 4 Android Development] fix-this!:
somethings not right with this recovery. i flashed it and now after i flash the omega rom when i boot that samsung custom isnt there anymore and i get sent into a bootloop. gonna odin back to stock and try twrp again see what happens.
[AT&T Samsung Galaxy S 4 Android Development] tdevaughn:
recovery is working fine here.. where did you get the Omega rom from?

did you install a kernel afterward, assuming the rom isnt for the at&T version
[AT&T Samsung Galaxy S 4 Android Development] fix-this!:
its an international based rom. never had issues flashing it on twrp.

---------- Post added at 03:09 PM ---------- Previous post was at 02:30 PM ----------

yes i flashed a at&t loki kernel, faux.

Edit: flashed omega on twrp no issues. Didnt mean to offend the op either. Just reporting my findings.
[AT&T Samsung Galaxy S 4 Android Development] mocsab:
I have flashed several I9505 ROMs - after a while, when you go into recovery and start to reboot I got an error message saying something about the ROM is going to attempt to flash recovery - yes or no -I learned that if you say YES - you will get stuck in a boot loop - if you say no, nothing bad happens. This happened to me in TWRP and in OUDHS recovery - I am not sure why it happens - but I know it does - the first time it happened to me _ I said yes (I was using TWRP at the time) and I got the same BOOT LOOP that guy mentioned - I went back to stock - re-rooted and installed OUHDS recovery - and eventually tried flashing the OMEGA ROM - and it happened again. (THe first time it happened to me I was on WANNALITE I9505 ROM - the next time it happened I was on OMEGA - so I think it can happen on any of the I9505 ROMS -but if you just say NO - and don't let it flash the recovery like it says it is going to - you should be fine. I have been in and out of recovery three or four times when I have seen that error - and I said no every time and the phone rebooted fine.

HOpe this helps you or anyone else having that problem - whatever you do - don't blame this recovery - and don't blame TWRP - I think it has something to do with the I9505 ROM. (for what it's worth, I have never seen this come up on a TMOBILE ROM or an ATT ROM - only on the I9505 ROms)

FYI - as I recall, this error message about flashing recovery doesn't happen right away - It usually happened to me after I had made at least one backup - then when I went to reboot - The error message popped up -

Good luck -
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Did you remove install-recovery. sh from system/etc as stated in op? I did and have flashed every i9505 rom with zero errors
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
This has been discussed a little bit earlier in this thread. When I encountered the message a had just flashed the recovery and was on stock ROM (I am still on stock). I chose "yes" to the message because I had read that you should choose "yes" if you want to keep the custom recovery and not reflash the stock recovery upon the next boot. It appears that some ROMs (and obviously the stock ROM) have the recovery included. Like I said, I chose "yes" and haven't had a single issue, however, your situation is different because you encountered the message after flashing a custom ROM, which means the ROM(s) you have flashed included recovery of their own. Choosing "yes" should let the CWM recovery know that you don't want the ROM you installed to flash the recovery that came with it upon the next boot. Choosing "no" should potentially let the ROMs flash their own included recovery upon the next boot. I am guessing that something is not working right in the process for it to throw anyone into a boot loop when selecting "yes"?

I guess the best option was given by shabbypenguin earlier:

Or maybe it wouldn't be to hard for the user to remove it themselves before they flash? Of course, I am not sure what kind of effect it will have on the ROM but it might be worth trying?
[AT&T Samsung Galaxy S 4 Android Development] highaltitude:
It may have been covered, but how to fix the date on the backups. ? Mine say like 1970-1-28 (and im not talking about just renaming the backup, they usually have a default date from when you make the backup)
[AT&T Samsung Galaxy S 4 Android Development] RabanJr:
I have currently have the cwm recovery but I never*removed /system/etc/install-recovery.sh

Is it safe to delete now or is it something that needs to be done before you install the cwm recovery?

I already have made a recovery of my current stock rom. Would I have to back it up again if I were to delete the

/system/etc/install-recovery.sh

Thanks!
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
I'm on the stock ROM and I didn't remove it either. I flashed the CWM zip with TWRP that I got through GooManager, so I never bothered removing it. That is why I got the message we are talking about in the first place. I chose "Yes" when prompted to keep it and haven't had an issue yet, but choosing "yes" on a custom ROM may not work the same way (as reported). The safest thing to do is just remove install-recovery.sh before you flash anything or ask the ROMs Dev to do so.

So, if it isn't giving you ongoing issues, I see no reason you would need to delete it from your current ROM. However, I copied /system/etc/install-recovery.sh and have a backup of it available in case I decide to delete it from my current ROM (if it ever causes issues) so I can always put it back if for some reason I need to.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
its a bug with recovery, its been going on for a lot of devices for a while now. recovery boots its own kernel so it cant get teh correct time and thus reverts to baseline unix date
[AT&T Samsung Galaxy S 4 Android Development] shoman94:
Any chance in adding usb mounting while in cwm. This would allow me to connect and transfer files while in cwm.

Thanks
[AT&T Samsung Galaxy S 4 Android Development] bostonirishguy13:
After flashing the first file via TWRP, what did you do then? Maybe it's me :o, but I find it unclear as to what the next steps are...
[AT&T Samsung Galaxy S 4 Android Development] Dallenn:
After you flash the first file you have the new recovery. All you have to do is reboot into recovery and you'll be in the new one.
[AT&T Samsung Galaxy S 4 Android Development] bostonirishguy13:
Via TWRP? Or Should CWM be set up?
[AT&T Samsung Galaxy S 4 Android Development] Dallenn:
The first file in the OP is CWM, if you flashed that in TWRP, reboot and you will be in CWM.
[AT&T Samsung Galaxy S 4 Android Development] bostonirishguy13:
Ah, thanks. I just rebooted into recovery (via TWRP), and I am now in the OUDHS CWM recovery. I didn't expect to reboot into this CWM recovery via TWRP, that's why I was asking about the set up via ROM Manager.
[AT&T Samsung Galaxy S 4 Android Development] paleman27:
Can you still reboot to recovery manually (vol up + power) after rebooting to CWM thru Twrp? I can't anymore...
[AT&T Samsung Galaxy S 4 Android Development] DIXZ06:
Try Vol Up + Power + Home.
[AT&T Samsung Galaxy S 4 Android Development] howtomen:
Adb push and pull works Bud :cool: :D
[AT&T Samsung Galaxy S 4 Android Development] Cali3350:
Worked great, many thanks!

I must use "adb reboot recovery" to boot into CWM. When I hold Vol Up + power and reboot I get the blue "recovery" text in the top left, but then it just power cycles again and boots normally. Only adb reboot recovery seems to make it stick.

This is such a ridiculously minor complaint I dont even care about though. Many thanks for getting this working!
[AT&T Samsung Galaxy S 4 Android Development] alacrify:
Somebody in another thread just said they were holding the button(s) too long - try releasing as soon as the blue text shows up? I know it's touchy...
[AT&T Samsung Galaxy S 4 Android Development] jeboo:
I would release once the first splash screen pops up..if you hold home too long, recovery will interpret as a selection on 1st menu item, which is reboot!
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Release the "power" button immediately after the phone vibrates, but continue to hold the other button(s) until the first splash screen appears and then let go of it / them.
[AT&T Samsung Galaxy S 4 Android Development] alcapone1130:
noob questions

i have a question that is probably pretty stupid but here we go.I have the i337 which i live in TN not in canada so im wondering why i have this model?Ok next,I have twrp on my gs4 now,can i flash the top download on your list like i would a rom?Or is this not for my model?And with this will i be able to download all the at&t roms without worrying about it being loki or not?Sorry for all the noob questions.Thanks for your help and work.
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
http://xdaforums.com/showpost.php?p=41878805&postcount=213

You need to read as much about this phone as you can. If you have questions, the "search" function will help you find the answers. A good start would be to read the rest of the thread you are posting in. I feel that if you don't even know why you have an AT&T S4 in TN, you will do terrible things to your poor phone ;)
[AT&T Samsung Galaxy S 4 Android Development] RiNo808:
Those trying to boot into recovery mode, dl quick reboot from the play store. That's what I use and it works great.
[AT&T Samsung Galaxy S 4 Android Development] shoman94:
Oh really. ..I had no idea. :rolleyes:
[AT&T Samsung Galaxy S 4 Android Development] howtomen:
well then why do u need the usb mount?
[AT&T Samsung Galaxy S 4 Android Development] shoman94:
I like being able to drag and drop things. Much easier....
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
twrp is a recovery that has far greater minds than mine working on it.

"Unfortunately at this time, MTP isn't available in recovery, so if you have no other option, you will have to use adb to push and pull files to/from your device."

http://teamw.in/DataMedia

if they cant get it, neither would i
[AT&T Samsung Galaxy S 4 Android Development] DJsCrIBbLe:
Sorry ot but you can drag n drop in twrp
[AT&T Samsung Galaxy S 4 Android Development] alcapone1130:
i think you read me wrong

i said why do i have a Canadian s4 in TN,not why do i have an s4 period.2ND i have been rooting and roming phones since it was a possibility,im running slim rom on my gs4 now.Just trying to see if this works on the i334. And i read the thread.For this site to be so helpful for people and everybody says oh go to xda they will help you blah blah blah,every time i have ever posted anything its a problem or i get a smirk cocky answer.Why?If you dont want to help people than why are you in here.To try to be superior know it all. I think i will do a little Google plus blog about my track record on here and about how people are treated like idiots on this site. I mean every tread there is somebody getting the same type comment or attitude i just received. WOW! One last thing,its making modifications to a cell phone you are not breaking the code of nuclear science here so get off your high horse.
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
OoooooKkkkkkk. Good luck with your Canadian i334?
[AT&T Samsung Galaxy S 4 Android Development] azz72:
I don't have a recovery rite now somehow I really screwed up. So how can I get this recovery to stick without having another recovery installed. Plz help.
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
I think the simplest thing for you to do would be to use GooManager to install TWRP and then use TWRP to install this OUDHS CWM. If that doesn't work you can try to use ADB to install CWM via the instructions in the OP.

If non of that works you can do a factory reinstall via ODIN, then do a factory reset via your phone and see if you can start from scratch.
[AT&T Samsung Galaxy S 4 Android Development] azz72:
I tried too manager and it doesn't work , I've tried to do it from scratch using dans method and nothing. I will try to push it wit ADB... Thanks
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Also there are a couple of tools that install recovery for you, it might not be what you are looking for but I feel they might be worth looking at to see if they can help you...

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

http://xdaforums.com/showthread.php?t=2297900
[AT&T Samsung Galaxy S 4 Android Development] azz72:
The casual thread I've tried that and didnt work and Loki I've been DL its taking a long time.
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
Dude, relax. He was just trying to encourage you to read a bit more. If you had, you'd realize a Recovery thread isn't the best place to ask your question, and more importantly that Canadian S4's bootloaders aren't locked (if you indeed have a Canadian S4.) Trust me, I've seen rude posts around here, and that wasn't one of them.

You asked "why do i have a Canadian s4 in TN?" Well the simple answer is, you don't... at least not if you bought it from AT&T. The Canadian model is i334m, the AT&T model is the i334 - easy to confuse. Now if you didn't buy it from AT&T, or you're absolutely certain it's not an i334 (you can check in Settings > About Phone) create a new thread in the General or Q&A sub-forum and post a screenshot with any other related information.

Sent from my Inspire 4G w/CM10.1
[AT&T Samsung Galaxy S 4 Android Development] shoman94:
The at&t version is i337 which is what this is for. The Canadian version is i337m and has an unlocked bootloader so this is not needed. So if you have an i337 and you already have a custom recovery then all you need to do is flash the first file in the op like you would a ROM.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
Version 1.0.3.5

Improved exit script, now it checks for working bootloaders and will skip otherwise. as well as avoids writing to your nand if you dont need the auto loki (as in the boot.img is already patched :) )

what this should mean is any canadians who feel so compelled to want to flash this recovery it now should check your bootloader and verify you dont need to loki and work like a regular cwm recovery :)

also im curious apparently there are reports of this recovery wiping imei's? im a bit confused as i dont recall seeing anyone post in here about it or in irc.
[AT&T Samsung Galaxy S 4 Android Development] Will822:
Can we just flash over version 1.0.3.4?
[AT&T Samsung Galaxy S 4 Android Development] brosenz:
After installing this updated Recovery (before I had TWRP) I get the following message trying to get into Recovery:

"System software not authorized by AT&T has been found on your phone"
[AT&T Samsung Galaxy S 4 Android Development] flinttownbrown:
Tried to flash the Loki one and I get "Input file is not a Loki image."
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
odd, mind re-downloading and testing again please?
[AT&T Samsung Galaxy S 4 Android Development] brosenz:
I cannot, I am stuck trying to go into Recovery or Boot with the Yellow Triangle and message, I cannot do anything. :confused::confused::confused:
[AT&T Samsung Galaxy S 4 Android Development] flinttownbrown:
Just did, same result.
[AT&T Samsung Galaxy S 4 Android Development] chrisc93:
I can confirm the "System software not authorized by AT&T has been found on your phone" message
[AT&T Samsung Galaxy S 4 Android Development] flinttownbrown:
Update: it works. Using the file tine stamped 13.41.26
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
Here is version 1.0.3.4 of the recovery.

Is there a way for users to revert back down to this recovery if they can't get into their recovery to flash it?
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
ok so its working fine now?

no they will need to odin flash teh stock recovery
[AT&T Samsung Galaxy S 4 Android Development] brosenz:
Flash ODIN this one?

http://xdaforums.com/showthread.php?t=2261573
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
Ouch... :/

---------- Post added at 10:55 AM ---------- Previous post was at 10:54 AM ----------

Yes.