yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] Mike:
Just restored a renamed backup a couple minutes ago after reading your post without issue...

You are the dev here, so I will trust you on this, but I did it all the time on my Skyrocket with cwm as well

Wasn't trying to steer you wrong and still don't think I truly did. Just texted a friend who devs on the S3 and he said it only breaks md5 when you place symbols or spaces in the rename.

Sorry if my post caused more harm than good. Was just trying to pass on what had worked for me. Didn't realize any adverse effects could be laying in wait for some users

Sent from my AT&T Galaxy S4 Running AOKP 4.2.2
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
interesting, everything ive ever used has broken the md5 sig. no worries overall man, i would rather someone stepped in to offer help regardless (i mean it worked for you) than he sat wondering if people were ignoring him :). still very odd it worked for ya
[AT&T Samsung Galaxy S 4 Android Development] Planktron:
I had spaces in the folder name. Like I said. No harm no foul on anyone. Just as much blame falls on me. If I would have verified the backup was actually restorable we wouldn't be having this chat in the first place.

I ODIN'd back to stock and am waiting for my ROM to download. It's all good.
[AT&T Samsung Galaxy S 4 Android Development] Mike:
I hadn't checked back in this thread since posting so I was unaware of his issue until tonight. I would have tried to help troubleshoot at the time if I had known there was a problem after following something I instructed him on. Maybe he can speak on if his backup contained symbols or spaces. I have multiple dashes in my backup names but nothing more.

http://db.tt/BGeIK4Ve

Anyway keep up the good work on the recovery. Just didn't want people to think I gave the wrong info and ran for the hills haha.

Glad to hear you got everything up and running again

Sent from my AT&T Galaxy S4 Running AOKP 4.2.2
[AT&T Samsung Galaxy S 4 Android Development] Planktron:
Fyi slightly off topic. After a fresh Odin I am running nottach's mint jelly with Faux's kernel via shabby's CWM. I thank everyone for their assistance and their hard development work. I owe many donations and beers.
[AT&T Samsung Galaxy S 4 Android Development] Sc4ryB3ar:
Can we use online nandroid with this recovery since it's partly cwm?
[AT&T Samsung Galaxy S 4 Android Development] rcklss1:
I see the 1.0.3.5 changelog but not the download... are the links for 1.0.3.5 just stil named 1.0.3.4?
[AT&T Samsung Galaxy S 4 Android Development] mattgyver:
www.shabbypenguin.com/OUDstuff/Samsung/ATT/jflteatt/Recovery/OUDHS-Recovery-jflteatt-1.0.3.5.zip

just change 1.0.3.4 to 1.0.3.5 ;)
[AT&T Samsung Galaxy S 4 Android Development] rcklss1:
lol figured that but just wanted to make sure.. thanks
[AT&T Samsung Galaxy S 4 Android Development] peatee:
I wouldn't do that. According to a previous post shabbypenguin saw an issue and reverted the links back to 1.0.3.4 for now. Also told everyone roll back.
[AT&T Samsung Galaxy S 4 Android Development] mattgyver:
good to know. rolling back now.... :-[ sorry...
[AT&T Samsung Galaxy S 4 Android Development] djmouse:
ohh man im glad i checked in here i had all my backups renamed via root explorer.guess ill have to make a back up now,no big deal tho,i like putting into rainbow mode and watching the backup anyway,one question tho what is the proper way to get into rainbow mode i usually just keep swiping up and down real fast untill it starts,im sure theres an exact gesture?

i think i found the way just scroll down two times?threw the list
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
thats exactly how :) im working on a toggle that will enable always, but its slow goings i still do a bit of work on the sgs3 :)
[AT&T Samsung Galaxy S 4 Android Development] slapdaddy:
I also want to know if this recovery will backup the EFS/IMEI partition??

Sent from my Galaxy S4.
[AT&T Samsung Galaxy S 4 Android Development] alcapone1130:
Thanks brother,And your work is deeply appreciated.
[AT&T Samsung Galaxy S 4 Android Development] chibixzero:
I found rainbow mode
[AT&T Samsung Galaxy S 4 Android Development] wdouglass:
Should we have the MDL ota installed for this lok file?
[AT&T Samsung Galaxy S 4 Android Development] nakedninja42:
I cant believe I am staring at a recovery right now!!! Thanks for getting this out quickly!
[AT&T Samsung Galaxy S 4 Android Development] StolenVW:
Yes you should be on MDL to use the .lok file
[AT&T Samsung Galaxy S 4 Android Development] shoman94:
Works great, Thanks
[AT&T Samsung Galaxy S 4 Android Development] rogersa2k:
Worked for me, too (on an AT&T SGS4 running MDL of course). Thanks!
[AT&T Samsung Galaxy S 4 Android Development] StolenVW:
working great thanks... and thanks for posting it so quick :)
[AT&T Samsung Galaxy S 4 Android Development] 21cdb:
For those that are not on a computer, you can just download the files in a browser and run the commands in terminal emulator. Works great. Thanks!
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
followed steps exactly and keep getting this...

/data/local/tmp/loki_flash[1]: /MSM8960_lpm.rc: can't execute: Permission denied

/data/local/tmp/loki_flash[2]: MSM8960_lpm.rc: not found

/data/local/tmp/loki_flash[3]: MSM8960_lpm.rc: not found

/data/local/tmp/loki_flash[4]: MSM8960_lpm.rc: not found

/data/local/tmp/loki_flash[5]: MSM8960_lpm.rc: not found

/data/local/tmp/loki_flash[6]: syntax error: '(' unexpected
[AT&T Samsung Galaxy S 4 Android Development] mattdm:
So to do that, you would first move the loki_flash and the OUDHS-Recovery-jflteatt-1.0.3.3.lok files to the /data/local/tmp directory with a root file explorer? And then in the terminal emulator, type:

su
chmod 755 /data/local/tmp/loki_flash
/data/local/tmp/loki_flash recovery /data/local/tmp/OUDHS-Recovery-jflteatt-1.0.3.3.lok

Is that correct?
[AT&T Samsung Galaxy S 4 Android Development] 21cdb:
Yep, that's exactly how I did it!
[AT&T Samsung Galaxy S 4 Android Development] sulpher:
Awesome! Worked great~

Thanks a bunch penguin!
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
something is off then, i cant test loki since i have sprint. only things i can guess by teh permission denied, is you arent in a rooted shell, or you dindt chmod loki_flash.
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
****! i forgot to edit cm's source. ill recompile now :/
[AT&T Samsung Galaxy S 4 Android Development] blkghost22:
Thank you but one question. How do i know everything went as plannrd
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
I am in rooted shell and did chmod. Tried two different pcs and terminul emulator on phone. Also tried the twrp steps and get same message

Sent from my Nokia 5120. Rocking it oldschool
[AT&T Samsung Galaxy S 4 Android Development] 21cdb:
If you don't get any errors, just reboot into recovery. Hold volume up and the home button as the device starts to boot and you should get into recovery.
[AT&T Samsung Galaxy S 4 Android Development] goobieracing:
I shouldn't push this to my phone yet?
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
could it be you are trying it on a nokia 5120 and not a sgs4? youd have to find a recovery for your device :P

but in all seriousness then i have no idea man. wait til dees_troy updates twrp and flash from goo
[AT&T Samsung Galaxy S 4 Android Development] stevehkim:
Sorry for asking this but where is the twrp steps??
[AT&T Samsung Galaxy S 4 Android Development] mattdm:
Something's wrong...I notice the files I downloaded from this thread have .bin and .txt file extensions, respectively. Does that mean I need to instead do this:

su
chmod 755 /data/local/tmp/loki_flash.bin
/data/local/tmp/loki_flash recovery /data/local/tmp/OUDHS-Recovery-jflteatt-1.0.3.3.txt

Or should I remove the loki_flash file extension and change the OUDHS-Recovery-jflteatt-1.0.3.3 file extension to .lok?
[AT&T Samsung Galaxy S 4 Android Development] david.degraw54:
I'm getting "Failed to open recovery.lok for reading" when trying to flash on my phone using terminal emulator

Edit: Wow, never mind. Didn't realize I typed "/data/local/tmp/loki_flash recovery recovery.lok" instead of "/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok" lol whoops
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
at this time no it doesnt, i do plan on adding support to backup additional partitions. i have a big backlog oif work i need to get done. this whole autoloki business took me longer than expected and thus i fell behind :/
[AT&T Samsung Galaxy S 4 Android Development] Planktron:
Seriously not to pester you man, but do you know if copying the nv folder works on this device? I googled and searched my brains out and the only thing I came up with was copying some folder to your extsd, but it could break some permissions...
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
i have no idea, the last gsm device i had was the tmobile g2. so this efs business is all still too new for me :/
[AT&T Samsung Galaxy S 4 Android Development] Planktron:
Roger that... Thanks anyway man. If I figure it out I'll let you know :p
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
http://xdaforums.com/showthread.php?t=2283325

For the I9505 Info starts at post 8.

I've never tried it.

also

http://xdaforums.com/showpost.php?p=41940944&postcount=2

Maybe this...

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

If you try something or find something that simply works for backup and restore like it is supposed to, please let us know.

Maybe the terminal emulator / ADB commands (in the above posts) can be applied to OUDHS without much trouble?
[AT&T Samsung Galaxy S 4 Android Development] Planktron:
That's the thread I was referring to. I don't have an I9505 but I have it's rom :p I'm not confident enough to try it.
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
NV / EFS partition data should be in the same place on the I9505 as it is on the I337. The ROM shouldn't matter.
[AT&T Samsung Galaxy S 4 Android Development] Fidelio_o:
You gotta port this to the #HTCOne man. Love the recovery lol
[AT&T Samsung Galaxy S 4 Android Development] mocsab:
I have been renaming my Backups every since I first flashed this recovery with no problems at all. I take that back - ONE backup I tried to restore a few weeks ago failed - but that was the exception - I have since downloaded Nadroid Manager and use it to manage all of my backups - so it is a non issue - but I have been able to rename up until now with no issues.

What I am trying to figure out now is - how to turn on Rainbow ? I have seen it once or twice, but don't know how I turned it on? I will read more to see if anyone has written about it here...
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
source is open so anyone can port freely, just shoot me a link to the thread when its posted :) id do it myself but i already cover a large number of devices to support/compile the recovery for :eek:

scroll up or down through the menu enough, when it loops it counts as a "Wrap". you can also cheat by just scrolling up one down one over teh reboot now etc :)
[AT&T Samsung Galaxy S 4 Android Development] mocsab:
Thanks I will give it a shot -

by the way - someone earlier posted about flashing the CWM recovery from ROM Manager. I assume that this is the official CWM (6.0 something) and that it does not include AUTO LOKI - so - if they end up flashing a kernel that does not have loki installed, they could end up having problems - is that correct? In other words, to avoid issues - don't use other recoveries when flashing NON LOKI Kernels or ROMS unless you plan to manually flash LOKI (or Loki-Doki) after you flash the ROM/Kernel - is that correct?
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
yes you are correct, anyone flashing from rom manager will have official cwm and thus are subject to how that recovery operates :)
[AT&T Samsung Galaxy S 4 Android Development] apatcas:
sorry for the noob question but what do i pick to flash from TWRP?
[AT&T Samsung Galaxy S 4 Android Development] mattgyver:
Shabby, quick question - when I did my initial backup and any therein, my backups give me a January 1970 date. I haven't been able to find anywhere to set it to the proper date. Known issue? I know CWM on my S2 gives me the correct date, just the S4 is giving me the issue.

Loving your work so far! Keep up the great work!
[AT&T Samsung Galaxy S 4 Android Development] Planktron:
Please see post #228
[AT&T Samsung Galaxy S 4 Android Development] neverends:
Can someone explain why the version here is 1.0.3.4 and some how I have 1.0.3.5... Thanks in advance
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
It has already been explained...

http://xdaforums.com/showpost.php?p=42440590&postcount=359
[AT&T Samsung Galaxy S 4 Android Development] freebee269:
i like this recovery a lot. i dont know know if this has already been asked, but are there any plans to enable backup of data only? right now it makes you backup everything and then in advanced restore you can do restore data only.
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
This is the biggest thing that I'm wanting to know also. Would absolutely love this feature.
[AT&T Samsung Galaxy S 4 Android Development] builtboosted:
When I reboot into recovery I get the Samsung screen with a unlock logo. Is this OK? I read all 41 pages and couldn't find an answer
[AT&T Samsung Galaxy S 4 Android Development] Sc4ryB3ar:
It is OK. If you want it gone make sure you have superSU installed with the most updated binary, and flash a radio, either amb or aml.
[AT&T Samsung Galaxy S 4 Android Development] builtboosted:
I don't mind it really. I'm using superuser as per mottochoppers unlock. Is their a conflict if I use superuser over superSU?
[AT&T Samsung Galaxy S 4 Android Development] Sc4ryB3ar:
No conflict per se. Install superSU, it'll ask permission from your regular superuser. Open superSU. Update binary per app request. Set you settings preferences. Uninstall original superuser if you want. Reboot to let superSU run again(I do this just to be safe) then boot into recovery and flash radio.
[AT&T Samsung Galaxy S 4 Android Development] builtboosted:
What radio? Is that really nessesary? Op says nothing about flashing a new radio
[AT&T Samsung Galaxy S 4 Android Development] Sc4ryB3ar:
Necessary... No, not really at all. But I was just letting you know how I got rid of my custom lock screen on boot.

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

[MODEM] Complete Modem List for I337 & I337M

I flashed amdl found in this thread for the I337
[AT&T Samsung Galaxy S 4 Android Development] builtboosted:
If I want to use twrp recovery should I remove the two files I copied into the temp folder?
[AT&T Samsung Galaxy S 4 Android Development] thacounty:
Is there any way to add the ability to name backups? This is something about TWRP that I love, but OUDHS is the way to go.
[AT&T Samsung Galaxy S 4 Android Development] djmouse:
read back, nandriod manager.About 4 pages back it was talked about for probably 3 pages
[AT&T Samsung Galaxy S 4 Android Development] thacounty:
I understand that they can be renamed after the fact. It's really nice to be able to do it in recovery. Sometimes I forget or do multiple backups when trying roms.
[AT&T Samsung Galaxy S 4 Android Development] godofwar762:
so do we just flash the flashable cwm through recovery and its done or do i still need to push other files via adb?
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
You should read the thread. It has been mentioned / explained many times including in the First few posts. Here is one of the many times it has been mentioned...

http://xdaforums.com/showpost.php?p=41819906&postcount=108
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
unfortunately its just not possible. i would have to completely rewrite the touch code which would basically be then copying twrp. as there is no way to have a keyboard for you to type in cwm for teh names etc.
[AT&T Samsung Galaxy S 4 Android Development] mocsab:
Honestly - with Nandroid Manager - I haven't missed the keyboard in Recovery at all - in fact, I tried using twrp and the Touch CWM recently - and I have gotten so use to the 'swipe' we use in OUDHS recovery - I really missed it - in fact on the Touch CWM the vibration I felt each time I made a selection freaked me out - maybe it was set too high - but regardless, I couldn't wait to get back to this recovery.

You did an awesome Job and at least for me - I love it just as it is.

Thanks!
[AT&T Samsung Galaxy S 4 Android Development] Planktron:
TWRP is nice, but in a way I feel it's over complicating a process that needs to be simple. Recovery should be get in, do work, get out. I do not wish to spend any extra time tweaking my phone while it is in an unchargable state.

And rainbow mode FTW.
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
Question for op

I am confused.. I am on a stock rooted phone....I want to try this recovery. I currently have TWRP but evidently we all need a LOKI patched this and that... so I read this recovery will auto loki.

In the OP, it lists the 1st two as one for people with CWM and the other just says LOKI flashable, I presume need the one that says LOKI flashable, correct??

Also, do basebands require a LOKI'd patch?
[AT&T Samsung Galaxy S 4 Android Development] Planktron:
If you are already using twrp, flash the first one through twrp like flashing a rom.
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
So the 1st line on the below (taken from OP) really means its for phones that already have TWRP or CWM, not just phones with CWM ?

"

CWM Flashable - OUDHS CWM-based Recovery 1.0.3.4 (need to already have a recovery for this)

Loki flashable - OUDHS CWM-based Recovery 1.0.3.4

Loki Flashing Utility

Drivers"

---------- Post added 24th June 2013 at 12:12 AM ---------- Previous post was 23rd June 2013 at 11:50 PM ----------

OK...im down to flash this recovery, since I need auto loki .

However, I just read on Google Play that as of version 5.5.2.6, CWM recovery now supports Loki patch. And, prior to that version 5.5.2.0 it also supports TWRP.

So if anyone, OP, can please explain the differences between OUDHS and the latest CWM 5.5.2.8 I would greatly appreciate it.

Thanks :D
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
oudhs is a cwm based recovery i forked based off cwm 6.0.3.0 and started to tweak it to how i liked it, i removed some things i thought were useless to the average rooter (adb sideload) and changed some stuff around. i added support for an exit script and use that script to loki whatever is currently flashed to your device.

rom manager was updated to add support for detecting you have a loki requiring device. so when it downloads the recovery it patches it then flashes it. then you end up with official cwm. you will have to use loki-doki or a compatible kernel :)

you only need to loki something if the developer didnt already handle it for you, in teh case of this recovery it does the loking for everything, with the others you need to be mindful of it all :)
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
Ahhhhhhh, I see said the blind man. Thanks for the response. Looks like I will be flashing a new recovery today, and, my S4's 1st new rom! :victory:

Thanks for the love bro.

Peace

Buying all y'all a beer this friday. Feels good to be back in the XDA scene again....R.I.P. Evo 4G :eek:
[AT&T Samsung Galaxy S 4 Android Development] bigblue95z:
So not really sure what my issue is, but the gesture controls stopped working. Did a quick search and didn't find any complaints. Been on the same ROM for over a week and have been in recovery to wipe cache/dalvik when I moved some stuff into system/app. So it has worked recently. The volume rocker and home button still work just fine. Prob just plan on fashing the recovery again unless there is a desire for any type of log....
[AT&T Samsung Galaxy S 4 Android Development] Obartuckc:
Wow..."Rainbow Mode"! LoL!

Sent from my AT&T Samsung Galaxy S4 Badass
[AT&T Samsung Galaxy S 4 Android Development] SysAdmNj:
Where is Version 1.0.3.5?
[AT&T Samsung Galaxy S 4 Android Development] Ker~Man:
Where have you been? LoL! ;)
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
Hey thats a fair question..where is the link for it?

CWM Flashable - OUDHS CWM-based Recovery 1.0.3.5 ????:p
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
Google "CWM Flashable - OUDHS CWM-based Recovery 1.0.3.5 xda" bet you find it
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
Cool, I will google it.

Thanks:good:

---------- Post added at 07:39 PM ---------- Previous post was at 07:33 PM ----------

I found this link to the CRICKET S4..

http://www.cricketusers.com/s4-root...[recovery]-sch-r970c-oudhs-recovery-root.html

But I do not see a real xda post w/ it for the at&t S4....the xda forum I found is not an official thread.:confused:

---------- Post added at 07:56 PM ---------- Previous post was at 07:39 PM ----------

Did u find it?

---------- Post added at 08:19 PM ---------- Previous post was at 07:56 PM ----------

I bought a Samsung Pro Extreme Speed 64GB SDXC card, just salivating to use exFAT, and we can't??? No matter what who when where???? DAMN!!!!
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
no exfat was added to custom kernels and worked around, at this time i just dont have the time to work on everything. im the only one on my team putting any effort in the recovery, then i have my sgs3 work i still do, and family time plus any time i take for playing some xbox. it will come just prolly not as quick as i was hoping for. im truly surprised no one else has added auto loki into their recoveries yet though :/
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
Appreciate the response..I feel you on the time juggling thing, especially the family involvement. :good:
[AT&T Samsung Galaxy S 4 Android Development] SysAdmNj:
Nope, and I've been checking here every week for a link lol.

Where is shabbypenguin?
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
Post #359 in this thread is the last mention.
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
I spoke with him, and he stated that there were some issues in that version, so for now we have to wait..

Funny how some people swear it was still available, but its not.
[AT&T Samsung Galaxy S 4 Android Development] chibixzero:
I have it on my phone, It was install via LOKIFYED_3WAY_TOOL found in these forums. But I will say there is something wrong. At least for me When I try to install roms that need to be loki they wont work, It says phone has sofware not compatible with ATT and so on.

my recovery says 1.0.3.5
[AT&T Samsung Galaxy S 4 Android Development] mg2195:
That's why he took it down...he said multiple times that something went wrong with the Loki script in 1.0.3.5, anyways why does it matter? 1.0.3.4 is working flawless :D
[AT&T Samsung Galaxy S 4 Android Development] chibixzero:
because I'm to lazy to reinstall 1.0.3.4 >.<
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
:silly:
[AT&T Samsung Galaxy S 4 Android Development] robstunner:
Both my nandroid backups have failed saying "error restoring data. Had to start fresh. Any idea what's going on? I've been having problems with twrp as well, even after an Odin back to stock
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
I'm going to guess a bad sd card. Do you have any problems with other files on the card?
[AT&T Samsung Galaxy S 4 Android Development] robstunner:
I dont have any problems with whats on my microSD card ( or microSD). Just recently I tried to install a backup that failed, So i wiped data, cache and dalvik, flashed a rom and it stuck on bootscreen. Only way i got it to work was to format data, system, cache, and data/media and then it would finally boot. Once the ROM loads its all good and I dont have any problems. It's when I try installing new roms or restoring backups.