yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] Tattooed5150:
Correct. I didn't flash anything. I had been running the rom for a week or two and got a text message from someone that I was already talking to all day and this happened. Have no clue what it is or why.
[Samsung Epic 4G Touch] Sam Sung:
Any reason not to use this el29 one click on a rooted fi27 E4GT? What I want

to do is restore my latest el29 nandroid, but there's no cwm available for

fi27. Or is there a better way?

Thanks!
[Samsung Epic 4G Touch] rocket321:
Instead you can odin on the el26+cwm kernel and then restore your nandroid from there.
[Samsung Epic 4G Touch] Sam Sung:
Thanks, rocket321. All went well with this process. Could this also be done in phone with Mobile Odin?
[Samsung Epic 4G Touch] Mattix724:
You can use Mobile Odin to flash the EL26 kernel/recovery if that is what you are asking.

You can also flash the EL29 tar using Mobile Odin. Just not the one click files.
[Samsung Epic 4G Touch] Sam Sung:
Got it. Thanks!
[Samsung Epic 4G Touch] flipwilton:
Compatibility question.

Hi! I'm just getting familiar with this Odin I've been hearing about. While I understand which one I need to use (as far as keeping my data). I just want to know if my handset is compatible with this version or not. Here are my specs:

Android version: 4.0.4

Baseband version: S:D710.10 S.FI27

Kernel version:

3.0.15-1127689

Se.infra@SEP-98 #3

SMP PREEMPT Thu Sep 27 18:24:35 KST

2012

Build number: IMM76I.FI27

Thanks.
[Samsung Epic 4G Touch] garwynn:
Yes... but this would roll you back to GB.
[Samsung Epic 4G Touch] flipwilton:
I take it "GB" stands for Ginger Bread; so then after rooting will I keep root if there's an update?
[Samsung Epic 4G Touch] garwynn:
No... would need to re-root.

If you want there is a one click root for FI27... the current version. (This is from last Dec.)
[Samsung Epic 4G Touch] flipwilton:
Bummer...I'll check that one out or keep looking and hoping for another one click update for this one. Thanks!
[Samsung Epic 4G Touch] garwynn:
If you want to dump ICS and go back to GB this the recommended one. If not the FI27 rooted one click is a better choice IMHO.
[Samsung Epic 4G Touch] flipwilton:
Could this be SPH-D710_FI27_CL1127689_Rooted_Nodata.exe? I just stumbled on it. Appears to be the one.
[Samsung Epic 4G Touch] littlepr:
Flipwilton, that one is correct. It does not have a custom recovery but you can get one by installing agat's custom recovery kernal after having installed the rooted FI27.

Sent from my SPH-D710
[Samsung Epic 4G Touch] flipwilton:
I think I got it now. Thanks alot!
[Samsung Epic 4G Touch] toobz:
If I run this one-click, will my phone go back to complete stock, reset my flash count and get rid of the yellow triangle?
[Samsung Epic 4G Touch] TheDudeAbides:
Complete stock - yes

Reset flash count/yellow triangle - no. Look for an app on xda called Triangle Away, it's free.
[Samsung Epic 4G Touch] MoHoGalore:
Reminder - TA doesn't work with gb. Gotta use rooted ics to reset binary

count.

Sent from my SPH-D710 using Xparent ICS Tapatalk 2
[Samsung Epic 4G Touch] antman5435:
help???

i cant seem to download this
[Samsung Epic 4G Touch] Sam Sung:
A while back, I flashed up to Android 4.1.2 (GB27) and want to revert back to a Gingerbread nandroid. I'm thinking Odin back to EL26 or 29 and restore the nandroid. Should I wipe the phone 1st or can I just odin over GB27? And will the nandroid restore whatever CWM recovery I was using?

Thx.
[Samsung Epic 4G Touch] bilgerryan:
Odin will wipe over everything, the nandroid will restore your recovery.
[Samsung Epic 4G Touch] Sam Sung:
Thanks, bilgerryann. Worked great, but since odin didn't install cwm, I ran the autopkg using option c, then tried to restore my nandroid.

However, md5 sums don't match on my 2 most recent nandroids (I have many nan's furthere back as well). I'm not sure what build I was running before I went to GB27, but I think it may have been in the FB range. Is this my problem? Do I need to autorootpkg to a newer build so that I can restore the possibly newer build nandroid?

Thanks again.
[Samsung Epic 4G Touch] bilgerryan:
http://xdaforums.com/showthread.php?t=2390010- you do need to be on a JB kernel to restore a JB ROM as ICS & GB didn't have the preload partition.
[Samsung Epic 4G Touch] Sam Sung:
Thanks for that workaround. I'm not exactly sure which build I was on, but was using Tasker for Android 1.6+ rather than Tasker for Android 4.0+ (it's been several months since I updated to JB) I would guess I was either on Gingerbread or Honeycomb. I guess I could try flashing a few different builds and try to restore the nandroid (which build number would be for honeycomb?).

Does the workaround present any bricking dangers under the circumstances, or better, is there a way to determine the build version from the nandroid?
[Samsung Epic 4G Touch] bilgerryan:
No and no. Honeycomb is 3.0 and is only for tablets. Froyo=2.2, Gingerbread=2.3, Ice Cream Sandwich=4.0, Jelly Bean=4.1/4.2/4.3, KitKat=4.4
[Samsung Epic 4G Touch] Sam Sung:
Thanks for the additional info. I finally was able to restore a nandroid from an Odin'ed EL29 & Autopkg CWM. My two most recent nandroids (from 07-2013 and 05-2013) from Pre GB27 failed at System restore (seemed to restore the bootimg ok). The only difference seems to be that those two had an additional file: .android_secure.vfat.tar. I wound up restoring a nandroid from March of 2013, build# is EL29 (no editing of nandroid.md5 file necessary).

Does the presence of ".android_secure.vfat.tar" denote a later build version?
[Samsung Epic 4G Touch] NewShockerGuy:
This is a REALLY dumb question.

I have a stock OTA ICS FL24 rooted E4gt. I hate it, and want to go back to el29. Can I simply run this and it will do that or do I have to change other things?

I also can't seem to install CWM for FL24 as all the links are broken. I kinda wanted to try jelly bean but honestly I just want to go back to calkulian's 3,0 rom that I had on the other phone before it broke. (If I was running that and did backups, if I can get CWM installed ont he new phone could I restore an old backup onto the new phone so that it would be just like how my older s2 was?

Thanks,

-Nigel
[Samsung Epic 4G Touch] wikedone:
Yes this will wipe your phone and put you back to el29.
[Samsung Epic 4G Touch] NewShockerGuy:
This will also put the stock modem on and not use the newer one that was downloaded?

I want to be careful since I don't have any recovery mod on it yet, but plan to put on cwm as soon as I get it back to el29.

Thanks much,

-Nigel
[Samsung Epic 4G Touch] wikedone:
Yes it's essentially putting your phone back to stock except the addition of root
[Samsung Epic 4G Touch] NewShockerGuy:
now I'm super confused, hopefully some one can explain this to me. When I had the sprint ota /wire update to jelly bean, it was not rooted... I followed the how to and loaded via Odin the rooted patch for it. I then proceeded to install the recovery but not cwm. Everything was fine I just didn't like how it was. I took my memory card out of my other Samsung galaxy s2 which had many nauseous back upa of calkulians 3.0 room and all my settings. I used the recovery that I just loaded to do a back up of the current state and verified that it was there. I then used the same recovery to restore back to when I was running ginger bread. It worked, and everything is there minus some program files that aren't going to be here because its a new phone. However when I restarted the phone, I no longer have the recovery partition for the NW one with jelly bean, its back to rogue cwm.... And the back up of jelly bean is not listed? I'm confused as how this would happen?

I.e. have the FL modem not el29 which is fine but wondering how this works cause I'm totally at a loss....

Again it works but I thought id be able to switch back and forth is need be, but appears that my current clock work at version 5.x.x.x doesn't. I didn't think restoring would change the recovery software used our partition?

Thanks

Nigel
[Samsung Epic 4G Touch] Surj138:
The recovery is included with the kernel on this device. When you flashed your old backup, you restored the old kernel which came with the Rogue recovery.

As for the modem, all GB and ICS modems are interchangeable with any of those stock ROMs. The official jellybean update, along with custom jellybean ROMs based off it (TouchWiz) are the only ROMs that can (currently) use the JB modems.

Custom AOSP and Cyanogenmod-based ROMs (from ICS to KK) can run any GB or ICS modem, but not JB.

Trolling from my SPH-D710 using Tapatalk
[Samsung Epic 4G Touch] YourWorstPoison:
So this roots the phone and all? Does it install a different recovery?
[Samsung Epic 4G Touch] Drumrocker:
From the OP...

"The ONLY change was the addition of ROOT to the ROM"
[Samsung Epic 4G Touch] sfhub:
If you install a different recovery from ODIN you'll get the yellow triangle.

This package is designed to work with the Auto Root package in the stickies (if you decide you need more than root), which will install CWM w/o giving you the yellow triangle. From there you'll be rooted with CWM and you can do whatever you like.
[Samsung Epic 4G Touch] AestenD:
Like getting ahead of yourself and selecting yes to format in cwm, then realizing it was external sd. :(
[Samsung Epic 4G Touch] shiftr182:
Are there any good mirrors? The links in the OP are down, thanks megaupload.....
[Samsung Epic 4G Touch] sfhub:
Try the ones at the end of the list. They were working a few hours ago.
[Samsung Epic 4G Touch] nickf914:
Are you saying that I can use " [ROOT][NCIQ][EG30/EG31/EK02] Auto root your existing stock ROM (w/o ODIN/ROM Flash)" to enable NOCIQ on this ?! despite it saying no EL13 or newer? if not, how do I get NOCIQ on this EL29?
[Samsung Epic 4G Touch] nivron:
Newer leaked ROMs have CIQ already removed by Sprint, and there is no more reason to remove it.
[Samsung Epic 4G Touch] nickf914:
nice! thanks for the update! its about time they did something right!
[Samsung Epic 4G Touch] sfhub:
Couple of things:

1) only the "root" exploit doesn't work on EL13 or newer, the other functions work fine. By not "working" I mean the exploit won't successfully achieve root, but nothing "bad" will happen if you try.

2) the other functions like installing CWM or NOCIQ or OTA check work fine as long as you achieved root some other way (ie use the pre-rooted ODIN packages such as this one)

3) NOCIQ is not necessary for EL13 and newer as Sprint had Samsung remove CIQ from the stock software. It won't actually hurt to run it. It just stores configuration information to say "don't run CIQ stuff" which will not have any effect if CIQ isn't present.
[Samsung Epic 4G Touch] nickf914:
wtf?!

I can't get my S2 to recognize the plug!? any ideas? (not just odin, it doesnt even recognize my charger)
[Samsung Epic 4G Touch] sfhub:
If you can't get it to charge, I can only think of a couple of things:

1) bad cable

2) bad port on phone

3) bad charger

Try swapping things out to see if it makes a difference.
[Samsung Epic 4G Touch] nickf914:
tried all of the above...i just got this thing (new white model)...think I need a replacement bc of bad port? between yesterday and today it had a couple of spazz out moments where it detected it was charging, but it wasnt...
[Samsung Epic 4G Touch] sfhub:
It would be odd to have a bad port out of the box, but not unheard of.

Charging is a pretty fundamental function. If it is not working, something is definitely wrong. It would be best if you could isolate under what circumstances it works or doesn't work. Understand it could be an intermittent problem.

The other problems with the port being recognized in ODIN might be software, but if it isn't charging that is more likely hardware.

Does it behave differently when plugged into the computer's USB port vs plugged into the charger?
[Samsung Epic 4G Touch] nickf914:
To answer your questions, it's not working at all. Within the past 24 hours, it happened about 5 times where the phone would uncontrollably beep as if a plug were being inserted and pulled out repeatedly; and the driving mode/docking homescreen would be opened and closed....I turned phone off and rebooted to stop the error.

Now today, righhhhhhhht before going to Odin in this package, the phone wasn't acknowledged by my PC...so I tested with the wall charger, and same deal. Its dead to the world...I am now dealing with Wirefly Associates whom barely know the language. YES! Just the welcoming I was hoping for coming to the E4GT from the old Epic...lol..o well
[Samsung Epic 4G Touch] sfhub:
The only thing other than an exchange I could suggest looking into is try and run an air blower (like the keyboard compressed air cleaners) through the micro-usb port on the phone in case some physical particles are causing issues.
[Samsung Epic 4G Touch] nickf914:
Car mode, charging, and voice control sporadically occuring during normal unplugged usage. Problem is reported in "galaxy s ii"" forum on xda. Im returning this lemon asap....glad it started happeni..h during first week after purchase. Super weird stuff. Thanks for ROM package

Update. after reading most of the forum sayin that it was probably dirt in the connector, I decided to try blowing into the charger connector next time that "ghost charging and driving mode" happened and sure enough after I blew into it, the "ghost chargin and driving mode" ceased at that monent. Def a hardware issue, id have to assume.
[Samsung Epic 4G Touch] wraith404:
Yeah, mine did that a couple weeks after I got too, rather irritating. In my case I had to poke around in the port with one of those plastic flossing picks, and pry it (the tongue) upward (away from the closest wall) just a bit. This was by suggestion from another post somewhere here on XDA. I've read that there have been many problems with the SGSII USB port in general.
[Samsung Epic 4G Touch] leaderbuilder:
Thanks again for the work here sfhub! I have been using this leak since you put it up and it has been pretty rock solid. I have a question regarding the OTA Sprint is currently pushing out now; it looks like it might be slightly different than this original leak. Do you have any plans to update this package or knowlege of the differences? Not a big deal really, like I said mine seems to be rock solid except for and issue with the market (but the market people seem to have a lot of people with the same issue).
[Samsung Epic 4G Touch] sfhub:
If there are differences i will refresh. I'll take a look once my phone gets chosen or someone posts the update.zip. From what was posted earlier, i am not sure if there are actually any differences. I've noticed sprint refers to the same radio 2 different ways, specifically in the way that was posted.
[Samsung Epic 4G Touch] mmark27:
You guys rock for doing this!

Can anyone tell me if the method to delete the camera shutter sounds still works after these updates?

Thanks!!!!
[Samsung Epic 4G Touch] sfhub:
It should work since the change was deodexed.
[Samsung Epic 4G Touch] mmark27:
thanks for the quick reply. follow up question for me a nooooob:

#1. Will changing the camera sounds not allow me to get any future OTA updates (you mention that if you don't change anything else, with the rooted EL29 we would still be able to get updates OTA....just curious, I'll probably always come back to you for this.

#2. IF I install some different ROM, kernel, etc. and I don't like it and things are fubar, can I always use this tool through ODIN to get back to this exact state?

Thanks again, I'm successfully running on EL29 rooted. Also, for those that might have hang issues, I did too during the install. I unplugged the cable, held down the power button until it went off, rebooted back into ODIN -> restarted ODIN tool on my computer, then reconnect my phone. Then it worked.
[Samsung Epic 4G Touch] musclehead84:
You can u Odin at any time to restore u back to complete stock. That's what its used for. As far as your first question I'm not famaliar with the mod but if u mess with anything in the /system partition then updates will fail. Hope that helps. So remember Odin is your friend and can be used at any time no matter what your setup.
[Samsung Epic 4G Touch] juggalo483:
Is there any way to get a single .tar file of EL29 (unrooted) for ODIN
[Samsung Epic 4G Touch] sfhub:
The "leaked" EL29 in resource A is a single tar of EL29, unrooted. However it also includes a new bootloader that disables some of the USB jigs capabilities.

If you are worried about the "rooted" part, just run Option B (unroot) of the Auto Root thread after installing and it will leave you with a completely stock ROM. Optionally I included a .tar of the stock ROM only (with nothing else, no modem, no kernel, etc) It is is the 2nd post along with all the other individual stock components.

My thinking was it is pretty harmless to have root on the system as it is dormant unless you run it and since EL29 is not directly rootable through an exploit, better to have a ROM with root than one without. Most people would want it rooted and the few that didn't could just use Option B in Auto Root to unroot it.

BTW "Rooted" just means the addition of 3 files that for the most part are dormant unless being actively used. With the exception of adding those 3 files, everything else is exactly stock.
[Samsung Epic 4G Touch] Slatter39:
Since [ODIN][TAR] SPH-D710.EL29_CL852097 (EL29 Modem/Kernel/ROM - Full Restore - Rooted) is as stock as possible san the root files, i am assuming it is odex not deodex, right?
[Samsung Epic 4G Touch] DevalB:
I've done that before too...now I always remove my card before flashing, root, doing anything, just to be on the safe side.

---------- Post added at 10:20 AM ---------- Previous post was at 10:18 AM ----------

Interesting, mine failed the OTA update, with the EK02 ODIN TAR, and I have a feeling it has to do with me having CWM installed. I'm curious if I use the Auto-Root menu option to go back to stock stock, would it work?

Not that it matters, now that you have the EL29 file, it's perfect.
[Samsung Epic 4G Touch] sfhub:
Yes, installing CWM would definitely cause the EL29 OTA to fail because CWM is packed into the kernel and that would cause the MD5 of the kernel to not match what the OTA is expecting. All you would need to do is use Option C of Auto Root to install stock EK02 before doing the EL29 OTA update and it would work fine (assuming you made no other changes other than root, ie didn't remove system apps, modify/delete system files, etc.)

CWM didn't come from the EK02 ODIN TAR so if you had just flashed the EK02 ODIN TAR (and nothing else) then the EL29 OTA update would have worked (at least in the many tests I have done it did)

For fun, you can run Option D of the Auto Root package and use the OTA Compliance Check (EK02->EL29) feature. It will tell you exactly why the EL29 OTA update will fail ahead of time. It is doing the exact same comparison that the OTA update does, except it tells you every issue and what file the issue is with, rather than just crapping out at the first sign of trouble.
[Samsung Epic 4G Touch] sfhub:
For the FAQ section:

I looked into this and figured out what was going on. It took some digging because the MD5 checksums for all the relevant files matched exactly so it wasn't anything obvious.

Contrary to what was suggested in the posts I read, it actually isn't anything I'm doing in my package causing the issue. Ironically it is because my package is behaving *closer* to stock that the AIO isn't working with it.

The AIO actually does NOT work with the stock untouched ROM, flashed with ODIN direct from Samsung's leaked tar file. I discovered this because my first step was to flash the untouched leaked Samsung ROM (just the ROM) then apply the AIO. That basically results in lots of FCs.

The reason for the FCs is because the AIO is signed with a generic cert (while the rest of the system is signed by a Samsung cert) and if things aren't done in a very specific way, it'll result in signature failures which then deny permission to some basic functions needed by the system. That causes a cascade of failures and an unusable system that keeps trying to restart.

So the reason it was working with Calkulin's EL29 update.zip wasn't because the files are different or anything "special" being done. The relevant files are actually exactly the same as can be seen by a MD5 checksum comparison.

The reason it worked is because the AIO (the odexed one, when used with an otherwise stock system signed by Samsung), either by design or by accident, depends on some caching of signature checks, based on file timestamps, to work. If the file timestamps are done in a certain way, it works. If the timestamps are the "stock" ones, as provided by the EL29 ODIN tar leak from samfirmware, it doesn't work.

Since my stuff is as close as possible to the EL29 leak with just root added, it has the same behavior as the stock Samsung EL29 leak, namely it doesn't work with the AIO mod.

Using this knowledge I was able to get the AIO working with stock leaked EL29 (and consequently my ODIN One-Clicks). To get it working, every app and framework file that the AIO package *modifies* needs to first have its timestamp reset prior to flashing the AIO.

I created an update.zip to do this for you.

So the process basically goes like this:

1) flash pre-rooted EL29 ODIN One-Click

AND

install CWM

2) boot into CWM

3) flash the EL29 AIO Pre-Flash [update-el29-AIO-preflash.zip]

AND

boot into Android

4) boot into CWM

5) flash the EL29 AIO update.zip

AND

boot into Android

There, done, EL29 AIO works.
[Samsung Epic 4G Touch] locoboi187:
Oh i just saw this post now. Sorry, disregard PM! Thanks dude! Quick question, how can i update my bootloaders?
[Samsung Epic 4G Touch] sfhub:
Are you sure you want to flash the bootloader? Every bootloader, since the ones that came with the phone in EG30/EG31, gives you no advantages but instead disables some of the USB jig functionality that lets you reset the triangle and flash count.

I don't provide the new ones because there is no advantage and significant disadvantages and I know if I provide them some people will flash out of curiosity. If you really want the new ones, flash the raw leaked ROMs from samfirmware.com
[Samsung Epic 4G Touch] locoboi187:
I extracted the EL29 stock bootloader, and now my odin is stuck at:

<ID:0/011> boot.bin

<ID:0/011> NAND Write Start!!

<ID:0/011> Transmission Complete..

<ID:0/011> Now Writing.. Please wait about 2 minutes
[Samsung Epic 4G Touch] sfhub:
It usually doesn't take that long.

I usually flash everything out of tar files in the PDA slot instead of trying to remember which other slot needs to be used and possibly making mistakes.

Hopefully it comes back. Individually flashing bootloaders is not really something you want to experiment with if you don't know what you are doing as a wrong flash can brick your phone.
[Samsung Epic 4G Touch] locoboi187:
It wont let me flast the .bin files from PDA. If i attach the bootloaders can you make a tar out of it?
[Samsung Epic 4G Touch] sfhub:
I have all the files, I just prefer not to provide stuff that might cause issues with your phone with no obvious benefit.

What are you trying to accomplish?

If you told me you have insurance and aren't really worried if something goes wrong, I might be more willing to provide what you are asking.
[Samsung Epic 4G Touch] locoboi187:
I just want the latest bootloaders. idc if it stops jig functionality. i remember flashing bootloaders before from the Phone option, and it always worked. o.O

oh i do have insurance btw. but i plan to be careful
[Samsung Epic 4G Touch] nghiemcpa:
I have the same problem after rooting from EK02 and installing CWM. I am not clear how to install stock EK02 from option C from the auto root menu. Thx
[Samsung Epic 4G Touch] sfhub:
In Auto Root, choose Option C, then Option F.

In case you are considering running the stock EL29 OTA update you should consider running the rooted EL29 OTA update from here:

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

It actually does NOT require you to have stock kernel nor stock modem. (ie if you are running that, you can ignore the SHA1FAIL for kernel/zImage)