yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] hotspace:
Darren, Heimdall is a command line interface.

This is from my terminal :

heimdall help
Usage: heimdall <action> <action arguments> <common arguments>

Common Arguments:
[--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]

Action: flash
Arguments:
--repartition --pit <filename> [--factoryfs <filename>]
[--cache <filename>] [--dbdata <filename>] [--primary-boot <filename>]
[--secondary-boot <filename>] [--param <filename>] [--kernel <filename>]
[--modem <filename>] [--normal-boot <filename>] [--system <filename>]
[--user-data <filename>] [--fota <filename>] [--hidden <filename>]
[--movinand <filename>] [--data <filename>] [--ums <filename>]
[--emmc <filename>] [--<partition identifier> <filename>]
or:
[--factoryfs <filename>] [--cache <filename>] [--dbdata <filename>]
[--primary-boot <filename>] [--secondary-boot <filename>]
[--secondary-boot-backup <filename>] [--param <filename>]
[--kernel <filename>] [--recovery <filename>] [--efs <filename>]
[--modem <filename>] [--normal-boot <filename>] [--system <filename>]
[--user-data <filename>] [--fota <filename>] [--hidden <filename>]
[--movinand <filename>] [--data <filename>] [--ums <filename>]
[--emmc <filename>] [--<partition identifier> <filename>]
Description: Flashes firmware files to your phone.
WARNING: If you're repartitioning it's strongly recommended you specify
all files at your disposal, including bootloaders.

Action: close-pc-screen
Description: Attempts to get rid off the "connect phone to PC" screen.

Action: download-pit
Arguments: --output <filename>
Description: Downloads the connected device's PIT file to the specified
output file.

Action: detect
Description: Indicates whether or not a download mode device can be detected.

Action: dump
Arguments: --chip-type <NAND | RAM> --chip-id <integer> --output <filename>
Description: Attempts to dump data from the phone corresponding to the
specified chip type and chip ID.
NOTE: Galaxy S phones don't appear to properly support this functionality.

Action: print-pit
Description: Dumps the PIT file from the connected device and prints it in
a human readable format.

Action: version
Description: Displays the version number of this binary.

Action: help
Description: Displays this dialogue.

Also, there's some really good step by step info here

http://xdaforums.com/showthread.php?t=1277000&highlight=heimdall
[Samsung Epic 4G Touch] Omar04:
@sfhub What this means?

When booting up first time after flashing a new Leak FULL RESTORE (started to happens on FE16 now the same on FE21) this message is displayed "Unfortunately, Internal has stop working"???

I panicked and went back to EL29 ASAP...
[Samsung Epic 4G Touch] wraith404:
Wipe Dalvik? Or maybe run Calks format all.
[Samsung Epic 4G Touch] neudof:
Since FF IV, FF VI, and FF VII are arguably the best FF games of all time my bet is on one of those to be the final :-)
[Samsung Epic 4G Touch] Omar04:
Stock recovery doesn't allow Dalvik Wipe.
[Samsung Epic 4G Touch] darren.wlsn1:
omg its kinda hard cause im nowhere near her but thanx guys. may try mobile odin
[Samsung Epic 4G Touch] sfhub:
I haven't seen that during normal operations.

If I wipe dalvik and try to keep running the system without rebooting, then I'll see that. If you do a NoData update and the versions aren't compatible with each other, then it might happen also.

I test the Full and NoData updates going from EL29 and didn't see what you are describing.

The only things I can think of is something on your sdcard is causing issues or you need to do a ##72786# reset.
[Samsung Epic 4G Touch] Omar04:
What could it be? So puzzled right now?

Edit: I did a Full Restore of FE21 form EL29 and it only happens on first boot, then no more..

I'm OTA updating to EL29 from EK02 right now, when that finishes, I will try and Flash EL26 Kernel.tar do a full wipe and Dalvik Wipe the boot, then turn it off and flash back to EL29 then go and try again FE21 to see if it happens again. < is that Safe??

Edit2: I will try ##72786# First thanks
[Samsung Epic 4G Touch] wraith404:
Would System settings/System Updates/Update Profile + update PRL maybe help?
[Samsung Epic 4G Touch] kevmo1965:
The last few builds, I've had really high Android O/S in the battery usage. How is it in this release? Any suggestions for getting rid of that bug?

Normally I flash to the EL26 kernel, wipe with CWM, flash calk's format all, then back to odin download mode to install the new ROM.

Am I doing it wrong?
[Samsung Epic 4G Touch] wraith404:
Will the ##72786# reset also reset a modified slot index? Just curious, so that I know what things will cause me to need to go back into QPST.
[Samsung Epic 4G Touch] sfhub:
It was supposed to be fixed in 4.0.4. It ended up changing so that it shows less usage in certain circumstances, but it can end up being high again over time.

If you aren't actually seeing high battery drain, I wouldn't worry about it, as in many cases it is just cosmetic. If you are seeing high battery drain, then you should look into it further. Most likely there is some app that is causing the battery drain.
[Samsung Epic 4G Touch] sfhub:
It likely would, but I haven't looked at that particular entry to confirm that it does.
[Samsung Epic 4G Touch] darren.wlsn1:
op im sorry and not lazy but could you post what version of Heimdall i can practice with or look at for w7?
[Samsung Epic 4G Touch] tmeader:
If anyone is using the official Facebook app, try swiping it closed after you're done with it just in-case. Found that was consistently using ~25-30% of the CPU for long after I got out of the app. Just noticed the same with the Fox News App. That one WAS fine, but it updated yesterday. Fully wiping dalvik cache to see if that helps anything at all.
[Samsung Epic 4G Touch] starnostar:
everything with this build is great....except we are venturing back into LOS land....2 LOS in 2 hours :(
[Samsung Epic 4G Touch] Omar04:
@sfhub

This is what I did:

1. From EL29 > ##72786# Reset, entered MSL Code then went through Handsfree activation process successfuly and it rebooted automaticaly.

2. Formated Internal storage and SD card from Storage Menu just to be sure.

3. Power off device and flashed again FE21 everything went very well.

4. boot up first time and this time no more "Unfortunately, Internal has stop working". YAY!!

THANKS A LOT sfhub, you're a lifesaver! :D

Edit!: Did someone noticed on FE21 if you turn off display via power button, and wake it up there's no slide screen ??? have to select None then back to slide to make it work after second try weird... Maybe is due to ROM still settling up... who knows.
[Samsung Epic 4G Touch] lafester:
i don't think there is a version for windows? you can load up linux though and try it. I never did figure it out myself. best bet is mobile odin and flash the modem in recovery.
[Samsung Epic 4G Touch] darren.wlsn1:
ya i see one plus she needs to flash this leak not just modem.
[Samsung Epic 4G Touch] Callie_evo:
So if I'm running a ROM with el 29 do I have to do anything special to go to this ics. TIA
[Samsung Epic 4G Touch] jeffek:
forgive the ignorance but if you run calks format all from unlocked stock recovery it wipes the dalvik cache does it not
[Samsung Epic 4G Touch] cdss:
One other thing is for sure,they still have not fixed the GPS bug on this modem, no GPS lock here, hope they get it fixed on next release .
[Samsung Epic 4G Touch] RainMotorsports:
Mine works. FE10 fine. FE16 no gps, FE21 fine. CM9
[Samsung Epic 4G Touch] wraith404:
I did a full wipe with caulk format all from the el29+CWM repack, the flashed the full odin.

Mine locks to ~20meters within 15 seconds, indoors, 10 feet from any windows. Stupid question, but I have to ask it, are you sure you enabled all of the location services?

:confused:
[Samsung Epic 4G Touch] sfhub:
dalvik-cache is a subdirectory under /data

If you format /data (as format_all does) then dalvik-cache will be wiped.

Stock recovery allows you to wipe data/factory restore (so it will wipe dalvik-cache), it just doesn't allow you to selectively wipe dalvik-cache, while keeping /data. In any event I would

NOT

use any Wipe Data/Factory Restore on an ICS-kernel at this point, even with stock recovery, as we don't have the fix for the EMMC brick/lockup problem yet.
[Samsung Epic 4G Touch] rwright64:
This is the best my gps has worked in a couple of weeks.
[Samsung Epic 4G Touch] sfhub:
It is up to you, but doing format_all is redundant when doing the Full flash.

Format_all will format /cache /system and /data.

All these are overwritten with fresh images when you flash a Full ODIN OneClick.
[Samsung Epic 4G Touch] cdss:
Yes, all services are on, i know how to do the GB fix to get it working again, i just wanted to test if this new modem had a fix for few people whose GPS does not lock on right away like it does on previous modems, thanks .
[Samsung Epic 4G Touch] CyberpodS2:
I had a similar experience... I had great GPS lock on FE16, but lost it when I flashed FE21 modem. It does not even show 0/0 in the gps status app. I went back to FE16 but it is still boned. Gotta play some more I guess. :(
[Samsung Epic 4G Touch] Kebetz:
I concur, sir.

I've haven't had GPS issues at all. It seems weird to me that some people never have this problem and some always have it. Have you ever tried a reset? I don't mean a "factory reset" I mean an actual, phone thinks it just came off the shelf, reset.
[Samsung Epic 4G Touch] sfhub:
Rule of thumb, if some people have good GPS and others have bad GPS with a particular release, then likely there is some other factor involved (either besides or in addition to) the modem/kernel/ROM.
[Samsung Epic 4G Touch] cdss:
How do you do a 'off the shelf reset' ?
[Samsung Epic 4G Touch] Nevell:
Wow I upgraded to this modem and now my S Voice stopped working. Catching network errors. It was working flawlessly before I upgraded my modem.
[Samsung Epic 4G Touch] wraith404:
Doesn't format_all wipe dalvik too? Though, now that I think about it, dalvik is probably covered by /system.. I just wanted to be sure. Inconsistent issues are really odd in a case where the full system should be formatted and block overwritten to an identical image.

Strangely, I'm now having move to SD issues with the stock kernel, so I'm about to format USB and SDext again.

Now, On a good note, I'm seeing very good WiFi negotiation in this build. My home network consists of 3 WiFi routers on the same SSID/password, different channels of course. Previously, this phone has been VERY stubborn about renegotiating to a stronger signal as I move about the house, to the point of leaving me basically at 0 bars after crossing floors - insistent on hanging on to the distant router even though it was 10 feet from a new one. Now, it is very consistently reconnecting and staying at 3-4 bars.
[Samsung Epic 4G Touch] sfhub:
dalvik-cache is a subdirectory of /data

format_all formats /cache /system and /data, therfore it wipes dalvik.

Full ODIN OneClick writes an empty /cache, a fresh /system image and an empty /data, therefore it wipes dalvik.

Doing both is therefore redundant.
[Samsung Epic 4G Touch] wraith404:
deleted
[Samsung Epic 4G Touch] winfan:
How do you do a phone off the shelf reset? Or even ek02?
[Samsung Epic 4G Touch] wraith404:
deleted

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

He might be talking about the "##72786# reset" I've seen sfhub mention.. done from dialer.

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

Thanks. I've always sort of assumed that, but I see so many people adamant on performing pre-odin full wipes that I also gathered there might be some anomalous data left around. Perhaps it is just paranoia... :)
[Samsung Epic 4G Touch] MicrosoftBug:
Anyone running this know if the socialhub syncs facebook pics yet?

Sent from my SPH-D710 using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] pcmanager:
I had horrible GPS ISSUES from October when I purchased my SGS2ET4G. Usually long lock times and slow, stalling navigation. I used most of suggestions to help gps issues posted in these forums. I was frustrated but living with crappy gps. Finally my camera auto focus went out and I brought it to Sprint.. They were going to replace just camera, and I mentioned the GPS ISSUES. He ordered a replacement phone. I now get 2 to 5 second locks on any rom I flash, the GPS ISSUES ARE GONE! 2 months so far. Thanks Thanks Sprint :-P
[Samsung Epic 4G Touch] Kebetz:
My thinking exactly, would you recommend a GPS reset, sfhub? It couldn't hurt right?

From anycut, or Nova/Apex activities shortcut

com.android.sprintmenu/GPSCLRX

press yes

reboot.

There are several reset options built into your phone

FactoryReset (resets you)

##72786# (reset DSA, (Sprint Reset)

##786# (Samsung Reset)I thought this was a factory reset, but it is way more intensive)

Above mentioned GPS Reset... etc.. there are many

EDIT: A FRIENDLY WARNING, ##786# reset things that I had stop-gaps to prevent. My personal pre-load folder/externalSD are all that survived. (somehow my inti.d made it, even though it seemed to erase almost everything else)
[Samsung Epic 4G Touch] sfhub:
One could try getting rid of stale assistance data like you suggest. One could also try the GB GPS lock workaround. Also keep in mind some units have hardware antenna issues. I've seen units where you can press certain parts of the case and get fast locks, but when you release pressure, get no locks.
[Samsung Epic 4G Touch] sfhub:
A few weeks back, I got tired of not trusting wipe data/factory reset from any ICS-based kernel's recovery so I put together a small ODIN utility to wipe /cache and /data

Here it is if anyone is interested:

SPH-D710.ODIN_WIPE_CACHE_DATA.exe

You just double-click in windows, boot your phone to ODIN DL mode, and press Start.

No need to flash GB-based kernel/recovery just to do wipe data/factory reset then flash back to ICS-based kernel.
[Samsung Epic 4G Touch] Kebetz:
Or you could just trust the software that is made for such actions... I have tried all of these built in resets so i can map which stock options do what. They are my most trusted.

(next to you, of course)
[Samsung Epic 4G Touch] sfhub:
My trust issues weren't with which actions did what. My trust issues were with the EMMC lockup/brick bug (triggered in some cases by wipe data/factory reset from recovery), which hasn't been patched in our kernels yet, but is something they are supposed to have a fix for in an upcoming release.
[Samsung Epic 4G Touch] wraith404:
That rocks. ODIN is growing on me like a Norse god.. :cool:

---------- Post added at 08:47 PM ---------- Previous post was at 08:46 PM ----------

You're taking your life into you're own hands with all the documented brick issues related to factory reset/wipe from ICS... ;)
[Samsung Epic 4G Touch] Kebetz:
I already learned what is and is not safe when I full-bricked my last one. These options do not act the same as a factory reset from your kernel. They are built in to perform these functions, and they perform them seamlessly....unless you have found a post to suggest otherwise... :p

I may be relatively new to Android, but in the last 8 months I have spent more time fiddling than that kid from Deliverance... (even though he banjoed)
[Samsung Epic 4G Touch] Omar04:
OMG I'm so lucky cause I was performing several Factory Data Resets on every leak since FD19 not a single issue (Brick) LOL thank God.... I don't dare to do it even once anymore hehe... I don't wanna test my luck anymore...:D
[Samsung Epic 4G Touch] wraith404:
That sucks. But what built in option are you referring to then? The OS Settings/Privacy/Factory Reset? I'm asking because that has caused bricks too. Another consideration - if you have a replacement due to a brick, have to checked to see if you're replacement is still in the firmware range affected by the brick bug? There is a thread with the adb command to issue to check the version. If you know all this, my apologies. I've checked mine and I'm in the brick range, and exercising extreme caution.
[Samsung Epic 4G Touch] Kebetz:
No harm in playing it safe, but in order to test the resilience of my preloader exploit i had to see what it survives. I have reset more than a kid trying to beat Pac-Man...

And to answer, I am talking about every reset that there is an option for in hidden menus.. and my "new phone" was a refurb from insurance, before the fix was implemented.
[Samsung Epic 4G Touch] Omar04:
You can point me to that thread please, to check mine? Thanks
[Samsung Epic 4G Touch] sfhub:
We've confirmed that wipe data/factory reset from stock recovery and custom recovery CAN trigger the EMMC brick/lockup bug. The problem is likely in the wear-level firmware for the EMMC memory chip (not the same firmware as you run on your phone). It doesn't get triggered all the time, so some people can flash many times with no issues, but may eventually hit it. We believe it has to do with a specific EMMC command sent to the memory chip on wipe data/factory reset (and possibly other functions) GB-based kernels did the wipe data/factory reset slightly differently and didn't trigger the bug in the EMMC firmware.

Performing the wipe data/factory reset from ODIN avoids the problem because it doesn't issue the same EMMC command and instead is writing a clean image.

This is the issue that Sprint/Samsung has recently been made aware of and they are supposed to have a fix for it.

I am not saying you are definitely going to hit the EMMC lockup/superbrick issue if you wipe data/factory reset, just that you are exposed to the issue.
[Samsung Epic 4G Touch] sfhub:
The "fix" is still not in our releases as of FE21, so effectively from our perspective, it hasn't been implemented.

We thought there was a fix for a separate 32KB zero corruption issue, but that code was for a different EMMC corruption problem and also was not in our kernels.
[Samsung Epic 4G Touch] sfhub:
http://xdaforums.com/showthread.php?t=1644364
[Samsung Epic 4G Touch] wraith404:
Thanks sf, I had closed it and digging for it was going to take some time.

So I was thinking. You should change your name to Loki... The one who ****s with Odin most. ;)
[Samsung Epic 4G Touch] Kebetz:
Yeah, I haven't paid all that much attention to the details (of the fix) and certainly don't want to be responsible for any bricks...but you have confirmation that people have hard-bricked from using ##786#? I'd like to read more if you can point me in the direction. A Sprint tech told me that this method was sound and I'll email him to let him know if he was mistaken, so he doesn't get people bricked with this advice.
[Samsung Epic 4G Touch] CyberpodS2:
Omar, I just noticed your sig... You and Daz are my heroes! LOL
[Samsung Epic 4G Touch] sfhub:
The likely culprit is a particular command or combination of EMMC commands (MMC_CAP_ERASE) issued to the EMMC chip. We know for sure it is issued for wipe data/factory reset from stock recovery (as well as custom recovery) as we have confirmation of bricks. Since the EMMC firmware bug is likely in the wear-level firmware, there probably is an additional factor where if you have lots of writes to the EMMC prior to the wipe data/factory reset, it could help trigger the bug.

I feel bad asking people to test ##786# reset over and over again under various scenarios to see if they can confirm the EMMC brick happens with that reset, so on our testing thread, it was enough to know that the problem is low-level enough that it could be affect various forms of reset. Not wanting to risk any more phones, we stopped there and tried to investigate the source of the problem. It is all detailed in the thread linked above.

If the problem can happen with stock kernel and stock recovery performing wipe data/factory reset, it is likely the same exposure is there for ##786# reset, which is privacy reset + nvram reset.
[Samsung Epic 4G Touch] Kebetz:
Good to know. My experience is obviously limited to my device, and i have read a lot of the discussion thread, i guess i missed the mention of the ## reset. I guess a seemingly knowledgeable sprint tech combined with a lack of hearing about it caused me to make a premature assumption. (not my first)
[Samsung Epic 4G Touch] wraith404:
I doubt many Sprint techs know about it definitively yet, as it's just started bricking stock Notes from settings/Factory Reset after the OTA to the note, and they just started testing for it this week in our builds. We apparently share the same bugged controller with the Note. Sprint techs aren't Sprint testers, so it's not really expected of them to know about all bugs in the latest leaks of a new release still being tested.
[Samsung Epic 4G Touch] Omar04:
thanks sfhub but really not sure, I've performed several factory data resets from recovery and Privacy option no brick so far since FD19 till FE16 don't want to test my luck anymore here is my result

Mine it mean something or I have been lucky enough?:

MAG4FA

0x0

0x0

0x000015

0x0100

02/2012

MMC

0xe21213bd

1501004d414734464119e21213bd2f7b
[Samsung Epic 4G Touch] sfhub:
If you have TEP and/or can deal with bricks, and you haven't been having issues in the past then it is a reasonable convenience vs safety tradeoff to keep doing what you are doing. If you really can't deal with bricks and want as little exposure as possible, just avoid anything that might do a complete erase of a partition using an ICS-based kernel.

Just giving the information we have so far so people can make their own decisions to fit their own situations.
[Samsung Epic 4G Touch] Omar04:
Thanks sfhub but I will stay on the safe side. :D

yes on 0x19 then I have been VERY lucky so far.. Ouch!!
[Samsung Epic 4G Touch] wraith404:
By "fix" I was actually referring to the fact that a newer unit might have had an EMMC version of 25 or later, i.e. fixed in the firmware. Might be a stretch but worth considering.
[Samsung Epic 4G Touch] sfhub:
We haven't seen any E4GT owners posting PRV/fwrev newer than 0x19. Only a few other phones have 0x25.
[Samsung Epic 4G Touch] Omar04:
Oh! I will do my homework on the subject. Thanks for everything.
[Samsung Epic 4G Touch] Kebetz:
Off topic, so feel free to ignore, but I get more answers here than searching or asking in other threads....

We are all aware of "fast charge", right? If I understand correctly this disables data transfer capabilities and instead charges through that part of the cable, correct?

My question is: would disabling the USB Charging result in faster data transfer? I can't think of any other use this option would have.
[Samsung Epic 4G Touch] locoboi187:
I have no idea what you're talking about but the answer to your question is def no
[Samsung Epic 4G Touch] jamesey:
Sfhub,

I'm not sure if it's been addressed or not, but does running calks format all in lieu of factory reset avoid the chance of bricking? Any time there is an ICS build on my partitions I refuse to factory reset and stick to the format all zip. I will occasional wipe cache and davlik too as I don't feel risk in that. I've yet to read about any bricks when ICS data wasn't wiped in recovery either by factory reset or wipe data. Haven't seen a brick thread or comment yet using the format all zip.

Please state your thoughts on this a I've been sharing this info for 2-3 months now and like everything else falls on deaf ears ;)
[Samsung Epic 4G Touch] Kebetz:
I am going to take a moment to appropriately appreciate the irony in this response.

Edit: Now that I am done laughing I'll request that somebody who does at least know what I am talking about answer. Or just clarify your "def no"
[Samsung Epic 4G Touch] wraith404:
:D Now THAT was funny.

I do believe that what sfhub is answering based upon, is that USB data bandwidth cannot utilize the voltage pins, even though voltage transfer may sometimes be able to utilize the data pins as voltage. I actually do not know how to put a computer in high voltage mode, even though I know some power bricks can. The USB 2.0 spec however does not define data over the voltage pins.

USB 3, though it has a much more complicated pin out (and port), might be able to do this, but it is radically different. Just look at the damn plug, it looks like someone soldered a micro to a mini.