yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] techjunkie860:
Help

Can I go from rooted EL29 to this without wiping my data? Do I have to do a full restore? Is it even possible to go from EL29 to this build? How so?
[Samsung Epic 4G Touch] Eric1985:
Hey guys I watched QB Kings youtube video last week how to install and you drag the downloaded file over to your card, I cant get my card to come up on the side. I just get Removable disk E and Removable Disk F. Just messing with my phone when I plug it in and click USB storage on my computer I have 2 windows that pop up, my card, and obviously phone. How can I get it back to 1 folder and get card to show up in My Computer folder.
[Samsung Epic 4G Touch] krazyflipj:
So I have a /data bricked device. I odined stock cwm and ran ADB. Got

MAG4FA

0x0

0x0
[Samsung Epic 4G Touch] sfhub:
Yes it is possible. If you are on stock Samsung provided ROM (ie not a custom ROM), you have a decent chance it will work fine, however be prepared with your backups in case it has issues. Issues are usually bootloop or random FCs, both are recoverable by flashing the Full version and restoring your user data (don't restore system data)
[Samsung Epic 4G Touch] sfhub:
Ok, that is good information. So either we are looking at the wrong field, misinterpreting what that field means, Samsung has been too aggressive in limiting the scope of their fix, or they are fixing something different than what we are seeing.
[Samsung Epic 4G Touch] sfhub:
If you are talking about MTP vs USB Mass Storage mode, use Auto Root.

Choose Option E - Extra Options

Then choose Enable ICS USB Mass Storage.

There is also an app you can download to your phone that will let you set the storage mode. It is in the faq section of this thread (2nd post). Look for mass storage.
[Samsung Epic 4G Touch] tmeader:
Okay, perhaps I'm missing something, but is there any way (using the oneclick packages) to get a fully up to date (FE07 for the build and kernel) install along with CWM installed? I did the NODATA ODIN method to go from FD26. Everything went fine with that, so I then proceeded to download the latest oneclick pakage and ran the option for the ICS builds... choosing to install the FD02+CWM on the next screen. This too seemed to work fine. Then, I was thinking that I could just install the CWM zip repack of the FE07 kernel via CWM and that would get everything up to date. That install seems to have worked just fine, however, now the recovery is back to stock. Am I missing something, or is there just no way to do it via this method? Thanks.
[Samsung Epic 4G Touch] dbman190:
I don't know if this is the desired behavior, but I used auto-root to enable USB-MS on FD24, and it kept through the NODATA package to FD26 and to FE07. USB-MS is still enabled. I assumed it would be reset when doing NODATA, but I guess not.
[Samsung Epic 4G Touch] sfhub:
FE07-Plus is not CWM. It is an unlocked stock recovery that will let you flash kernels, modems, themes, roms, etc. It doesn't do backups.

I could theoretically do the CWM repacks, but I'd have to ask Steady for permission to include his stuff and then the bigger issue is testing the recovery knowing what we do about the brick situation.

The latest Rogue CWM repack from Steady is FD02. I think Calk may have repacked one using FD26 in his ROM. If you want something more recent, you could pull that zImage and flash in Mobile Odin or use the Generic zImage option in Auto Root.
[Samsung Epic 4G Touch] sfhub:
You'd have to tell me if it is the desired behavior for you, but it is the "expected" behavior.

Whichever setting you do is persistently stored in your user data partition.

If you do not actively enable a setting, the default is pulled from the default.prop in the kernel when your android user data is first created. When some kernel repacks say they "enable usb mass storage by default" you actually won't see any effect if you flash that kernel onto an existing system, keeping your existing android user data, as the value for mass storage is already stored on your user data partition.

Only if you wipe /data factory reset will that "enable usb mass storage by default" setting in the kernel get used.
[Samsung Epic 4G Touch] JohnCorleone:
You may have just saved me from bricking some time in the near future. Thanks!

Sent from my SPH-D710 using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] sfhub:
I updated the original post with info we discovered on this thread. It is in RED

I think it is best for Garwynn and I to start a new thread in General to gather information and see if this bug is fixed or not by Samsung's checkin for the EMMC fix. I have some stuff to discuss with him, so probably something will show up tomorrow.
[Samsung Epic 4G Touch] JohnCorleone:
So sfhub, what are your initial thoughts on FE07? With all of this useful info you are providing, I may have missed your take on how it is compared to FD26
[Samsung Epic 4G Touch] darren.wlsn1:
think i saw his thoughts in second post, well first page. (hi)http://xdaforums.com/showpost.php?p=25826145&postcount=3

ok #3
[Samsung Epic 4G Touch] sfhub:
I think if you are bothered by the flick sensitivity for auto scroll, you will still not like it. If you don't mind or like the flick sensitivity you will like this ROM.

Don't judge it right after the install. It seems to need some time to settle down, probably background stuff is happening right after the upgrade.

It seems to be an incremental upgrade with small fixes and it doesn't introduce a lot of new problems. A bit surprising going from 4.0.3 to 4.0.4.

Maybe after using it more often bugs will start appearing.

A lot of times one's opinion of a ROM is directly related to whether there is a bug that affects them, irrespective of how critical the general user would find that bug. So there may be bugs, but they aren't affecting my usage so I have a positive outlook on the release. Someone else might experience a less prevalent bug that, nevertheless, affects them all the time and feel this thing just isn't read for primetime.

The flick sensitivity is kind of like that. I actually like the way it is now. Even though I recognize it is different from GB, I just adjusted my behavior to work with it. Other folks just can't stand it.
[Samsung Epic 4G Touch] tmeader:
I see. So then currently there's no way to run a recovery that allows cache/dalvik wipes and backups, along with the latest kernel? Too bad. :(
[Samsung Epic 4G Touch] JohnCorleone:
I am definitely in the minority on this but once I got used to the new scrolling, I actually like it. I kind of have a feel for it now. It comes in handy on apps like Root Explorer where I have huge files to go through. It sounds like they stayed on the right path then. I was worried we might have to take a step back before taking two forward. I should probably get it on my phone now so I can do some low signal testing tomorrow. Actually, I will try to grab a video of these low signal area menu pop ups I get so I can shoot it your way. I think I am hoping against hope that I will see a fix especially since it doesn't seem to effect everyone. Thanks again for everything sfhub
[Samsung Epic 4G Touch] sfhub:
Well w/r/t cache/dalvik wipes, it would be trivial to put together an appropriately name update.zip that did that for you. Since the unlocked recovery will basically run anything, you could use that to do the cache/dalvik cache wipes.

BTW I added an option to Auto Root to wipe dalvik and reboot.
[Samsung Epic 4G Touch] geeksmurf:
Bug maybe maybe not? This is the first leaked build ive got around to using so I'm not fully sure. No matter how the homepage is set in the browser it always loads the last page viewed it seems. very annoying. :(
[Samsung Epic 4G Touch] Omar04:
Not a bug. It's the way it meant to be. As browser never close by itself you need to FC it on Task Manger that way when you open it again it will load the home page you set it up.
[Samsung Epic 4G Touch] daniel4653:
does anyone have the aosp/aokp mms and browser that can be pushed into this rom? :]
[Samsung Epic 4G Touch] geeksmurf:
Oddly I have a habbit of FC'ing it after every use always have. And that doesn't seem to do the trick.

well oddly it's working correct now.....
[Samsung Epic 4G Touch] metayoshi:
Well, looks like they fixed combined view in the Email app. No FC's so far. At least on my testing.
[Samsung Epic 4G Touch] madocs:
Market: Android 4 ICS calendar, Android 4 ICS messaging

Both free, easy, work well.

- sent from a thingy
[Samsung Epic 4G Touch] sfhub:
If you open the tab control and close the one window currently open, it will load your home page. Otherwise, as the previous poster said, you are basically continuing where your browser last left off because it never closed.
[Samsung Epic 4G Touch] CyberpodS2:
Wow, two free jems I never saw before. These are now added to my titanium apps backup for all my installs. Nice find!
[Samsung Epic 4G Touch] aaron130:
I got a question. If I Mobil Odin the FD02 CWM Kernal and flash sfhubs repacked kernals he posted can I flash roms and ect with that kernal? Or is it stock? Just a lil confused, been using the fd02 every time there's a new release. Also if I can flash roms with it is there a way to flash the kernal through Mobil Odin?
[Samsung Epic 4G Touch] sfhub:
It is stock recovery, but it will ignore signatures, which means it can run the install packages for modems, kernels, roms, themes, etc. You will see a signature verification failure, but it will continue with the install.

You can flash ROMs with it and I have done so during testing. However due to the nature of the /data emmc corruption problem not being completely known it is not possible to tell you there is no risk of that happening.

You can just pull the zImage out of the update.zip and flash using Mobile ODIN. You can also use the .tar.md5 7zip self-extractor posted a few posts back. Also Auto Root was updated to include it so you can install using that also.
[Samsung Epic 4G Touch] sfhub:
Yes, they first fixed that in FD26 and it is good to see it is still fixed and hasn't regressed.
[Samsung Epic 4G Touch] jase33:
I threw together a quick ICS theme for this rom. This is a lite theme and will give an ICS look to the status bar, settings menu, dialer and a few other things. Flash with one of sfhub's modded kernels or the cwm kernel of your choice.

DOWNLOAD HERE
[Samsung Epic 4G Touch] sfhub:
Thanks, added link to your post in the 3rd post.
[Samsung Epic 4G Touch] sfhub:
Please use the following thread for further discussion on the /data EMMC corruption and whether the fix Samsung put in this kernel addresses it.

Discussion thread for /data EMMC corruption bug
[Samsung Epic 4G Touch] weboide:
I ran

setprop persist.sys.usb.config mass_storage,adb

but now I cannot access adb shell:

$ adb shell
error: insufficient permissions for device

---------- Post added at 08:41 AM ---------- Previous post was at 08:35 AM ----------

I think i figured it out, running adb start-server as root...
[Samsung Epic 4G Touch] jimbobtexas:
Wake Lock

I'm seeing a pernicious wake lock issue with this build. Google+ seems to be the primary culprit. I was seeing almost %15/hr drain on the battery.

Just me, or anyone else seeing awake issues?
[Samsung Epic 4G Touch] RustedRoot:
Calk did a modified wipe zip that should serve that purpose? With his full wipe it has a permanent place on my SD card.

Sf, is it kosher to flash a kernel with CWM that's from a deodexed ROM (e.g. Calk's FD26) over an odexed ROM (e.g. Agat's)? I'm reading that no, it isn't, but I know one who did it without problems? Just lucky?

Hopefully this is moot if a final OTA is near, but are there any disadvantages in terms of delay and use to produce your initial one-click ROM with a repacked kernel? Just modifying the kernel to unlock signature verification would seem not to affect its functionality, but...that's why I'm asking.

Once again, I have to commend you for the clarity of your threads and posts. Never have I had to say "huh?" when reading them. My brain cells thank you.
[Samsung Epic 4G Touch] rrmzr1:
Anyone know how to revert to ics lockscreen
[Samsung Epic 4G Touch] sfhub:
Probably. If point me at the script I can tell you (or you can look for yourself) what it is doing and whether it meets your needs.

Yes, that is fine. odex/deodex is a concept introduced at the Android-level. The linux kernel has no concept of odex/deodex files. I guess theoretically someone could cook up some init.d scripts that did distinguish between odex/deodex, but I am no aware of any. The times when swapping kernels becomes an issue is if they start making changes to mount points or moving dalvik-caches around. Often those implementations make assumptions which only hold true if that modified kernel is running and if you swap in a different kernel it breaks those assumptions causing failure here or there. Something as simple as the wrong path name to a critical startup file could cause a bootloop.

Not sure about the question. None of the ICS leaks will allow you to install an OTA for ICS on top, because the final OTA will based off of EL29. *IF* there was an OTA based on an ICS leak, then the ODIN OneClicks would be compatible with that OTA because they do not modify or remove any stock files, however that OTA needs to be based on that particular release. The minute you make even a one byte change in a kernel, that kernel is no longer able to be patched by an OTA release. If the OTA release for some reason shipped a complete kernel rather than a patch for the kernl, then the OTA would not care if you made changes to the kernel, as it would just overwrite it.

The reason I don't include any modified kernels in the initial OneClick install is because it would trigger the yellow triangle and increase the flash count. This can be addressed using a USB jig or triangle away, but some people just don't like to have it show up at all. Also I try and stay consistent by not modifying or removing any files from the release so people are assured they are getting exactly what Samsung provided.
[Samsung Epic 4G Touch] sfhub:
When you do that setprop, it will reset the usb mode on the phone. Often you'll need to reboot or restart something to get things working again. After you restart or reboot once, then everything should be back to normal.
[Samsung Epic 4G Touch] someguyatx:
Theme looks great I want to try

So its safe to flash this with the stock repack FE07 kernel? I thought I needed to have a cwm kernel for flashing theme for some reason.
[Samsung Epic 4G Touch] guirae:
i'm told that i can just erase some sound files on the camera app and get rid of all and any camera noise.

i've also been told that'll crash the camera.

any suggestions on how to get the camera to be quiet?
[Samsung Epic 4G Touch] Esoteric68:
Looks great!
[Samsung Epic 4G Touch] PanchoPlanet:
You forgot the clock! How about some blue for the clock, it would totally put the ics on the cake.

Great job with the theme.

Pp.

sent from my Comadore 750X/V8 supercharger.
[Samsung Epic 4G Touch] JsVerbal:
I can't seem to get an md5 match on the FE07 Kernel (Plus). Ive dl'd a dozen times from 3 different browsers. Any ideas?
[Samsung Epic 4G Touch] stevetrooper:
Still seeing high Android OS usage after moving to FE07 NODATA.
[Samsung Epic 4G Touch] RustedRoot:
Calk's modified zip is attached. I mentioned it because you were speaking of doing an update.zip for someone else and I wanted to spare you from reinventing the wheel

Thanks for taking me up the kernel learning curve.

Didn't mean to drag OTA into the equation. Sorry. You did answer my question in the last paragraph. I was never bothered by triangle (after my initial freak out) but I use Triangle Away now, so its appearance is rare.
[Samsung Epic 4G Touch] odub303:
That's because you haven't used your phone for anything. If you aren't using your phone, of course the time battery user is going to be the operating system. Use the phone for a while, download apps over wifi, play some games, make some calls. Come back when you have about 8 hours of usage and an hour or more of screen on time, then see what it looks like.
[Samsung Epic 4G Touch] sfhub:
Sorry, my bad, the downloads are fine, I just included the FD26 MD5s by mistake. I updated the original post with the correct MD5s (and file sizes)
[Samsung Epic 4G Touch] sfhub:
Thanks.

Basically calk's format_all script does

format /cache

format /system

format /data

The modified script does

format /cache

format /system

Wipe dalvik would be

delete_recursive /data/dalvik-cache

Wipe cache would be

format /cache
[Samsung Epic 4G Touch] sfhub:
Just providing a point of reference.

When I just let my phone sit there, Android OS didn't even show up at all. I only had Android system showing up in single digits.
[Samsung Epic 4G Touch] tmeader:
Yeah, after the initial NODATA wipe, the "Android OS" was staying around 5% for several hours. After my attempts to install FD02+CWM, and then flash the CWM version of the FE07 kernel, Android OS is showing ~25%. This is despite the phone stating that it's on kernel FE07 and Android build FE07. I think I might just rerun the ODIN NODATA again tonight and zero everything back out.

sfhub, would those commands be sufficient to run from Terminal in order to clear out the dalvik and cache partitions? Or will that only be possible from a recovery?

Thanks.
[Samsung Epic 4G Touch] stevetrooper:
I might try a reboot. I now have over an hour of screen time (33%) and Android OS is still at 41%.
[Samsung Epic 4G Touch] brian_hoffman:
Wii Motes Work!

Guys,

Just thought I would let everyone know you can use Wiimote Control to play your favorate emulators on this build.

Woo Hoo!
[Samsung Epic 4G Touch] odub303:
When you are leaving it sit there, are you on wifi or are you on 3g? To dig a little further, do you have wifi set to keep awake either "only when plugged in" or "never"? The AOS usage seems to be triggered by wifi being active.
[Samsung Epic 4G Touch] flamebeats:
Where's the zip?
[Samsung Epic 4G Touch] stevetrooper:
I had wifi set to always on, so I have turned it off. I will see what my Android OS reports later this evening.

---------- Post added at 08:31 PM ---------- Previous post was at 08:13 PM ----------

Sfhub, sorry for the delaying in testing this. I pulled down your new FE07 Plus Kernel and flashed it to my phone using Mobile Odin as you suggested. All the apps that I had installed on my SD card are greyed out. If I try to move an app to the SD card it fails.

---------- Post added at 08:38 PM ---------- Previous post was at 08:31 PM ----------

Put the Stock FE07 kernel from post #2 back and my apps on SD are available again. Going to test the Unlocked kernel now.
[Samsung Epic 4G Touch] Kenny987654321:
I agree it does this for me too. I have reverted back to the stock kernel and have no issues. I do believe it is a problem with all repacked kernels for ICS.
[Samsung Epic 4G Touch] stevetrooper:
The Unlocked Kernel does not cause my apps on SD to be greyed out. And I can move apps to the SD and back without any errors. So only the PLUS kernel is causing my apps to be unavailable on SD.
[Samsung Epic 4G Touch] edlee:
yeah, i have same issue with PLUS kernel, I guess I will try the Unlocked kernel instead.
[Samsung Epic 4G Touch] donsh00tmesanta:
Does Odin automatically wipe all?

Sent from unnamed 2.0.1 powered galaxy s2 brought to you by sprint
[Samsung Epic 4G Touch] daniel4653:
Only if you use reset data one click. If you use no data version it won't wipe data.
[Samsung Epic 4G Touch] okantomi:
OK, I used mobile odin and extracted the no data one click exe as per instructions (I know I should have used the full restore...DAM!) flashed fine but now I keep rebooting into android recovery. I factory reset, and wiped cache and still no luck. I'm not at home now but will be in a couple of hours. What do I do now. I'm staring at the recovery screen.

Update: I got into download mode and it says:

ODIN MODE

Product Name: SPH-D710

Custom Binary Download: No

Current Binary: Samsung Official

and then a green android

Downloading...

Do not turn off target!!

This has been going on for a while. Am I OK? Am I bricked?
[Samsung Epic 4G Touch] locoboi187:
You're not bricked but I suggest flashing through Odin via computer and this time the full restore
[Samsung Epic 4G Touch] okantomi:
Do I just plug it in with this message on the screen? Will the phone be recognized by my pc?

Update: Resolved--I pc-odin'd the FE07 Full Restore. Thanks for your help!
[Samsung Epic 4G Touch] daniel4653:
Not a good idea to do no data coming from codename?
[Samsung Epic 4G Touch] sfhub:
I actually specifically tested that this time around. I installed an app on the stock kernel, moved it to sd, then installed plus, rebooted, and ran the app. It worked fine.

Obviously there is something going on but it probably involves more than just app moved to sd and the plus kernel. Maybe the type of app you move over might have some additional requirements and that along with the plus kernel is causing issue. There are only a couple of settings it could be. Obviously it isn't recovery as they both have it. I doubt it is adb. So that leaves init.d, which can't be a factor if you don't have the init.d directory, and the default.prop changes (usb mass storage and ro.secure) It is probably one of those two.

I will create a couple of test kernels to figure out which one. It'll be a about an hour. Thanks for your patience.
[Samsung Epic 4G Touch] sfhub:
If you are going from a custom rom back to stock odex, I would suggest full flashes.
[Samsung Epic 4G Touch] daniel4653:
okay thanks for the fast response sfhub. at school right now and too lazy to back everything up then have to restore all apps etc. lol
[Samsung Epic 4G Touch] sfhub:
Yes, as long you didn't flash an intl ICS release, it should be recognized by ODIN.

Start ODIN or ODIN OneClick first. Then, while your phone is on that download screen, plug it into the PC. You should hear a USB ding sound and a yellow com port should show up in ODIN. Then you can start the flash (or select the PDA button and tar file, then start the flash for traditional ODIN)

I am a little confused though that Mobile ODIN and factory reset wouldn't have cured your issue. That shouldn't have been the case. Mobile ODIN can flash the ODIN OneClick fine, including the NoData version. It only won't flash the modem. The system and kernel should have flashed.

If there is some conflict in the install, a factory reset should have cleared it up. The only reason I can think of, off the top of my head, why it wouldn't is if that factory reset cause the /data corruption. Anyway, just go back and flash the full version. If it goes through, then everything is good. If it hangs on data.img then /data probably got corrupted by the reset.
[Samsung Epic 4G Touch] sfhub:
You can use equivalent shell commands. I just listed that in pseudo-edify scripting language (which is the scripting language used in update.zip)

You could probably just do

su

rm -r /data/dalvik-cache

rm -r /cache

reboot
[Samsung Epic 4G Touch] cdss:
Hey sfhub, sorry to bother you right when you are busy trying to figure out the current issue with the plus kernel,when you have the time to answer will be just fine with me.

What is the best way to flash the theme by "jase33" ? can i odin this : SPH-D710.FE07_CL519197_ROOTED-oc-sfx.exe, reset data and then flash this : [CWM] Repack - FE07 Kernel (Unlocked Recovery) to have CWM to use to flash the theme ? thanks for your time ...
[Samsung Epic 4G Touch] JohnCorleone:
Man, I have been dying to get home from the moment I saw this posted! I am dying to run a true themed stock with init.d and tweak what I want on my own!

This leads me to my next question and it has probably been answered already so I apologize in advance. After I flash the theme I want to run stock kernel with only init.d. Is Autoroot updated to handle that or is one of the existing kernels already that way? Sorry, only had 3 hours of sleep last night..lol
[Samsung Epic 4G Touch] cdss:
You actually sleep John ? :)
[Samsung Epic 4G Touch] TheDudeAbides:
How woud you go about flashing that ICS theme? Got the unlocked recovery kernel. Just flash .zip from recovery? Sorry, never flashed a theme before.