yashsingh1/xdaforums huggingface dataset:
[Epic 4G Q&A, Help & Troubleshooting] rando991:
The stock Task Manager is not what I use to close running programs, but I do use a stock "task killer." You probably already know this, but just in case, go to Menu/Settings/ Applications/Manage Applications and select the "Running" tab. Even though you could kill off an autostarting app such as "Maps" in ATK, you will still find a remnant of it running here. Usually Force Closing it from the "running" tab, stops it from autostarting so frequently. I have found other apps "running" under this tab that weren't being reported in Advanced Task Killer as well. I never had any luck with Memory Booster or any auto task killing apps. The only thing that will definitely prevent apps from autostarting (assuming you don't delete them) is to freeze them with something like Titanium Pro (my favorite).

I do like the quick access of ATK, but I find I get a better control of those few apps with the stock task manager, so I don't use the ATK anymore. Oh, btw, I was thinking about using Dolphin Browser, because the stock one is a hog. What do you recommend on browsers?
[Epic 4G Q&A, Help & Troubleshooting] KennyG123:
I was using Miren for awhile but it won't download on EH17 ROMs for some reason. My Gf really likes skyfire.
[Epic 4G Q&A, Help & Troubleshooting] lilhgarcia1:
the task killer is gone I odin and re-flashed srf 1.2 with genocide kernal

I see my battery drop 1% every 3-5 minutes I left home at 7:20 am and its 10:39 am my battery is on 42% with only using playerpro

Google Voice is a killer but I used it before I never experience problems this much. Maybe, Just maybe its the honeycomb theme I'm going to do a reset. let my phone run with no apps see what happens and slowly add in the apps then apply the theme and scripts later.
[HTC Desire S] wax_addict:
Hi guys, a little background :

I S-Off'd my Desire S a few weeks ago and installed/clicked gingerbread which i gather roots it?

One day my screen went blank randomly with just the notification bar showing up top. No buttons worked, couldn't turn it off etc.. so I did a battery pull. It then got stuck on the HTC screen, so I googled, tried clicking recovery/factory reset etc.. all while not really knowing what i was doing, but in the end it randomly loaded after a long wait.

Phew, or so I thought.

Now it constantly crashes, turns itself off, the camera doesn't work, force closes galore.. it's a mess. Figured the battery pull messed something up.

Searched a bit more and figured i should try and flash a ROM which might fix it and get it stable again.

Tried installing using 'download ROM' in Rommanager, it did all the installing and whatnot, but when it rebooted nothing had changed. Tried three times, same deal. Figure I should install a ROM via the SD card instead.

Found this forum and a relatively simple/safe guide :

I'm using the guide here : How to flash a perfect ROM.

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

The Rom is MIUI.

However, I'm only on step 2 : Format data. (Formatting /system was fine)

Clockworkmod says Formatting /data for about 5 minutes, then : Error formatting /data.

Help! :confused:

A big thanks in advance.
[HTC Desire S] amidabuddha:
Spare yourself a lot of troubles - use RUU and start fresh...
[HTC Desire S] Lowery91:
Could be a faulty eMMC chip on the phones motherboard, these tend to break after a few bad battery pulls?

If installing a new ROM on the phone wont work and you get data format problems I would do as posted above. If this doesnt work I would suggest a faulty eMMC chip.
[HTC Desire S] wax_addict:
Is there a fairly easy to follow guide that includes every step on here?

According to the FAQ I might have a fried chip.. the e:Unable to mount errors.

Can I still save it with the RUU?

I'm clueless, and a fair few of the guides are not too noob friendly tbh, could you please point me in the direction of an easy to follow guide?

I wish I knew how deadly the battery pulls would be before hand, but when your phone is frozen and you can't power it off, it seems logical. Arrrghg.

Much appreciated.
[HTC Desire S] amidabuddha:
Since you still can boot into your system you are good.

Download the RUU that is right for you from here. Connect your phone to the PC and run the RUU.exe. It will hadle everything automatically. Then you will be back to Stock. To go back to custom ROM:

1) use Revolutionary

2) no need of Gingerbreak since you will flash a rooted ROM

3) flash custom ROM from recovery
[HTC Desire S] wax_addict:
Ok, I have the RUU downloaded.

Should I just connect the USB cable to the phone while it's in ClockworkMod, HBOOT, or does it not matter?

Soooo.. plug in USB cable, run the RUU file in Windows.. should work?

Cheers again.
[HTC Desire S] amidabuddha:
Yep. If by any chance the RUU installer says that it cannot detect your device go to Settings -> Development - > enable USB Debugging on your phone
[HTC Desire S] wax_addict:
Cheers. Yep, I got no phone detected, check your USB cable etc.. / ERROR [170] USB CONNECTION ERROR

I can't get into the phone to go into settings and turn USB debugging on though :confused: As soon as I get it functioning to that degree I'm not using it for anything other than calls in case I break it again. :p sadly, I could have earlier before I tried flashing a new ROM. Hindsight eh?

All I can get is HBOOT/ClockworkMod.

Tried RUU with the HTC white screen on and also while in Clockwork Mod.

Anything else I could try?

Thanks.
[HTC Desire S] Tectas:
Are you using windows?

If yes download HTC sync and instal it, could be a missing driver.

Swyped from my Desire S
[HTC Desire S] amidabuddha:
From the power menu in ClockworkMod reboot to bootloader (hboot) and with the volume key go to FASBOOT (then you should see "FASTBOOT USB"). Then run the RUU again. Let me know is it working please because I will leave my PC soon :)
[HTC Desire S] wax_addict:
:D

It worked, can't thank you enough!!

Cheers all.
[HTC Desire S] amidabuddha:
Good to know :)

Congratulations!
[HTC Desire S] wax_addict:
Limited to 5 thanks a day but I'll come back, this definitely helped I'm sure, fairly certain the drivers were needed. :)
[HTC Desire S] ben_pyett:
If your intending on re-running revolutionary to S-OFF your device again then you must first de-install the program HTC SYNC from your PC, don't worry the drivers are left behind and there are all that you need.
[HTC Desire S] amidabuddha:
This is already the 4th case that the "E: cannot open...." error is successfully solved. I am keeping track on all such posts constantly and in my opinion if we have some more evidences for solved errors of this kind it will be good to remove the "[solved]BRICKed: inside eMMC's dead..." thread to avoid stressing the users...

I think this is a mistake of a service technician that was too lazy to diagnose and just replaced the chip...and started a great panic in this forum
[HTC Desire S] Tectas:
Could be true.

I personally think there where a few devices out there with an chip failure, but most of the reported faults where wrong classified and could have been solved other ways.

Maybe it would be good to write the conclusion at the overall section down, cause our device isn't the only affected.

Swyped from my Desire S
[HTC Desire S] amidabuddha:
I will write a "calming" thread besides the Guide that is in my signature or as a part of it, just waiting for more confirmations that generally the chip is not affected when there is an error. But it seems not much people are reading the guides they prefer to start a new thread...Anyway I have a friend that is working at a centre of a Mobile Operator for my country and according to him among the hundreds (!) Nokia's, Samsung's, etc., he got only one faulty HTC for repair for the last 2 years (and there is a practice to replace rather than repair as well)
[HTC Desire S] ben_pyett:
Good point although hopefully any new user experiencing this problem for the first time will create a post in this forum and can get pointed in the right direction, or better still there's always the hope that they will look at the INDEX/GUIDES themselves and read some of the resources that have been made available for them to use.

Possibly create a list of most likely resolution strategies in a new thread so that they can be tried in order and I'll refer users to that in the section on eMMC issues at the bottom of the INDEX thread, where I've tried not to scare users into thinking that its all too late and its game over in the textual intro bit!
[HTC Desire S] amidabuddha:
Yep. My "[GUIDE] Read this before going for eMMC replacement" is updated with the solutions that worked so far..
[HTC Desire S] amidabuddha:
Minutes ago I "bricked" my phone again by downgrading the Radio. Hboot Factory reset sucks.

I managed to fix with Solution No.2 im my Guide
[Android Apps and Games] jeffrimerman:
Anyone know of an app that lets us input multiple address into our google nav or is there another program to input multiple addresses and have it optimize the route?:confused:
[Galaxy S II Q&A, Help & Troubleshooting] OperationIvy85:
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.

The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.

No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).

Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.

Things I have tried:

-Different USB port

-Kies "Resolution connection errors" button, which seems to reinstall the drivers

-Reboot computer after above step

-Remove battery from phone and replace

After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
[Galaxy S II Q&A, Help & Troubleshooting] JJEgan:
Remove Kies and reinstall see if it picks the phone up and installs the drivers .

jje
[Galaxy S II Q&A, Help & Troubleshooting] jhernand1102:
That kernel is for the Epic touch 4g is that your phone or do you have the international version? If you flashed the wrong kernel it could cause problems.
[Galaxy S II Q&A, Help & Troubleshooting] OperationIvy85:
Yes it's an Epic touch 4g from sprint.

EDIT: Uninstalled Kies, reinstalled Kies, restarted computer, still no kind of recognition of my phone in any state (powered off, at "Firmware upgrade encountered" screen it boots into, or in download mode). Starting to get nervous, I used to at least hear a sound when plugging my phone into my comp. It is like there is nothing on the other end of the USB cable.
[Galaxy S II Q&A, Help & Troubleshooting] OperationIvy85:
More things I have tried:

-All of the above steps on a different computer

-Sweet talking it

-Talking dirty to it

Am I brick'd? I figure not, since I can at least get into download mode. Not sure what else I can do though. I'd go see what the Sprint store can do for me, but on the download mode screen it lists my custom binary download count as 5, I understand they will see that and tell me I'm out of luck?
[Galaxy S II Q&A, Help & Troubleshooting] jhernand1102:
Try to reset your binary counter with a usb jig.
[Galaxy S II Q&A, Help & Troubleshooting] cooza:
you could try and download the drivers again from here and see if it then connects

http://modem-techno.blogspot.com/2010/09/epic-4g-usb-driver-download.html

I also had a similar problem once with an old i9000 and what worked was doing this and then connecting the phone first and then opening Odin.For some reason opening Odin first and connecting wouldnt find the phone.If nothing else works try wipeing the bin counter with the jig and send it back.Youll have to say that kies crashed while updating on Win7 64bits.Samsung know that before the September 30th kies update kies wasnt fully functional with 64bit drivers and they had a few phones replaced under warranty because of crashing kies updates on Win7 64bits.
[Galaxy S II Q&A, Help & Troubleshooting] OperationIvy85:
Thanks for the replies everyone.

I made a USB jig but it had no result. I checked the resistance with a multimeter and I am connected across pins 4 and 5 of the usb dongle I bought. I plug it in and nothing happens.

I can still get into download mode by the usual means, just no recognition from my computer, odin, or kies. Very frustrating. Am I going to have to buy a new one or is there another way to reset the bin counter?

EDIT: Got the USB jig to work! I was using a bad diagram and was on pins 1/2 instead of 4/5. Now I can't boot, can't get to recovery, can't get any PC to recognize my phone in download mode.. but at least my download screen says "Custom binary download: NO." So if nothing else works before tomorrow evening I'm gonna bring this thing back to the Sprint store and tell them what cooza said about kies crashing on win7 64 bit. Thanks everyone! Also I just realized there is a specific forum for Epic 4G touch.. sorry >.>
[Galaxy S II Q&A, Help & Troubleshooting] cooza:
The good thing is that your bin counter is at "0" again.The Kies thing is the real deal as there are also posts here on XDA of the same thing happening.I also know its true from first hand experience as it has happened to me and when i told them about the Win7 64bit driver problem (this happened to me a couple of months back too) they had no option but to accept it cos they know its true.Also i offered to e-mail links from forums with other complaints from users on 64bit PCs but they didnt even dought my storey and in 4 days it was back in my hand.I told them that when the update finalized the programe froze and the phone rebooted to a black screen.Had to pull the battery cos it appeared to be dead and refused to reboot again.Important to say that you where on Kies prior to the update I mentioned.Ived update to the latest Kies and it works fine now on my Win7 64bit so be carefull there:D that date is important:cool:
[Galaxy S II Q&A, Help & Troubleshooting] OperationIvy85:
Thanks cooza I really appreciate your help. I do have a couple questions though.

1. Is the update you are referring to an update to Kies software.. or an update to the Galaxy S2? Reason I ask is because my phone is the Epic 4G Touch (accidentally posted in this forum >.>), will they still believe my story?

2. Not sure if you will know the answer to this one, but should I go through Samsung tech support or can I take it back to the Sprint store where I bought it?

3. Just trying to get clear on the story I should tell them. I was using Kies to update my phone on a Win7 64bit computer, but I accidentally used the version of Kies from before the Sept. 30 update? And then the phone crashed resulting in it's current state. Correct? Anything else I should watch out for?

4. With the problem you are describing with Win7 x64, does the phone go into a soft brick where it won't boot up?

Thanks again.. you've been very helpful :)
[Galaxy S II Q&A, Help & Troubleshooting] cooza:
Kies via to its Sep 30th update was not fully compatable with 64bits and gave a lot of problems to a lot of people.I had a few problems with it when I got a new laptop (HP Win7 64bit) so started searching the web for solutions and found that kies was designed mainly to support the windowsXP versions 32bit and had caused Samsung to accept various repairs under warranty because of crashing Kies updates mainly on android running phones.For some reason Bada didnt seam to affected.Maybe cos there arnt to many around like android.In the 4G forum there is post from someone who has bricked their phone using Kies to update and a reply from another with the same problem.Take it into where you bought it to start with and if its not there problem then they might send it back to Samsung for you.All you need to say is that you where updating your firmware via kies and on completion it froze and the phone booted to a black screen like mine did.You had to pull the battery and restart your PC to close Kies cos it wouldnt close or minimize or anything.Tell them that you searched on the net for possible causes and found what i told you about Kies and since you have a Win7 64bits PC then thats most likely to have been the cause.Your bin counter is at 0 so there is no way they can counter-attack your story.
[Galaxy S II Q&A, Help & Troubleshooting] bajaber:
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.

Is there anyway I can do anything to save my phone?
[Galaxy S II Q&A, Help & Troubleshooting] IA-32e:
Who told you that the exclamation point means you voided your warranty?
[Galaxy S II Q&A, Help & Troubleshooting] OperationIvy85:
The exclamation point on a normal boot up screen (Galaxy S II splash screen) means there is a custom rom installed. This can be removed with a USB jig, which will also reset your custom binary counter.

I have absolutely no idea still what [phone]....!....[computer] means though. I ended up taking my phone back to the Sprint store and they replaced it for a small service charge while telling me next time I won't be so lucky. My next step was going to be to try calling Samsung with the story cooza suggested. I told that same story to the people at Sprint but they definitely didn't buy it, but you may have better luck with Samsung. If you get this resolved I'd be curious to hear how, but I am not optimistic for you :(
[Galaxy S II Q&A, Help & Troubleshooting] cooza:
The sign you see means that your phone is semi-bricked and that you needed a jig to force the phone to boot into download mode.You can buy one on ebay for a couple of bucks.Best you do cos it could may mean that your warranty is void.Let me explain,no one can actually say that your warranty is void because of this sign but being only "semi-bricked" the service centre are still able to enter the phone and see the bin counter.So if you semi-bricked flashing a non official firmware or you have done so earlier and your bin counter is not at 0 then YES your warranty is void.Semi-brick is not so bad as you can normally fix it yourself but Hard-brick is a dead phone and you gotta pay for a jtag:( .In your case buy a jig force the phone into download mode and re-flash it yourself.You shouldnt need to go anywhere.Semi-bricking is something you save yourself.Just wait till the jig arrives in the mail.

EDIT:there have been posts of people pulling the battery for 10min and re-trying and it has booted to download.They say they have had to do so 4 or 5 times for it to finally work but if youve got time on your hands then give it a try.

---------- Post added at 04:48 PM ---------- Previous post was at 04:22 PM ----------

Well at least you got a phone now:D hope they didnt charge to much!!!!Good on ya mate:D
[Galaxy S II Q&A, Help & Troubleshooting] bajaber:
Update on my issue....

It turns out the problem is because I tried to flash an I1900 firmware while my phone is a G variant (I900G).

After using the right firmware, it worked.
[Galaxy S II Q&A, Help & Troubleshooting] sfoksn:
Hi, I'm having an exactly same problem with you and I just got a USB jig in mail, but even though I am following the instructions for the USB jig the counter is still not going back to 0 :/

This is the instruction I followed: take battery out for like a minute -> put the battery in but don't turn phone on -> put the usb jig in -> it's supposed to boot up with 0 flash count?

Mine still says 4... :( Can anyone please help?
[Galaxy S II Q&A, Help & Troubleshooting] aceofclubs:
Is yours a i9100? If so is your firmware the latest 2.3.5 KI3 or KI8?

Could be your device has the new bootloader. If so check intratechs original firmware thread in original development section and install his old bootloader via Odin. Have a read while your there to get the latest info.

Good luck
[Galaxy S II Q&A, Help & Troubleshooting] sfoksn:
Yeah, I got stuck while flashing 2.3.5 Gingerbread... Yeah I think it has a new bootloader, as I remember Odin updating the bootloader section before messing up.

Is there any way I can get the USB jig to work? My phone is no longer recognized by the USB anymore so I can't even flash another bootloader or anything.

Is there anythign I could do to make the USB jig work without connecting it to the computer?
[Galaxy S II Q&A, Help & Troubleshooting] aceofclubs:
Can you get into download mode using the buttons?

Volume down+home+power

If so try and flash another Rom from intratechs thread to get back to stock.

If that works you can try again.
[Galaxy S II Q&A, Help & Troubleshooting] sfoksn:
Yes I can access download mode no problem but the problem is that I can't get it to become recognized by the Odin. The driver doesn't recognize the phone at all. I tried reinstalling KIES/driver but still no go. It's as if there's nothing connected to the USB or something. I dont hear any sound when I connect the phone. Any ideas? :(
[Galaxy S II Q&A, Help & Troubleshooting] aceofclubs:
Make sure kies is not running before connecting.
[Galaxy S II Q&A, Help & Troubleshooting] sfoksn:
Yes, KIES is definitely off. I have checked through task manager to make sure that it was off... Is there a way to make the phone become recognized through the USB? Any advanced users?
[Galaxy S II Q&A, Help & Troubleshooting] aceofclubs:
I would try another computer that hasn't had USB drivers installed and see if device is recognized just to eliminate that side of things.
[Galaxy S II Q&A, Help & Troubleshooting] LarryLars:
I have had this issue a few times! (i9100), Kies and or odin is a pain in the ass!

In the past I have reinstalled the drivers a few times until you can see the usb driver in device manager on your PC. As for Odin make sure you connect the phone first then launch it.
[Galaxy S II Q&A, Help & Troubleshooting] rembrandtlnx:
try on another computer, pref a 32bit, kies sometimes gives problems on 64bit systems
[Galaxy S II Q&A, Help & Troubleshooting] cooza:
If you have the new bootloader then the jig is worthless no matter what you do.Thats what Samsung want.As for not connecting i can only suggest uninstalling and reinstalling Kies and if you have a mate with an S2 then plug it into you PC to get the S2 drivers recognized atleast and do it in all the com ports of your PC as not all recieve the same amount of power.Another thing you can try which has worked for me in the past is plug in the phone first and open Odin second.I had a phone once which never connected when i opened Odin and tried to connect.Not sure why but it only worked that way.If it works then try and download 2.3.5 with the old bootloader where the jig still works.If all else fails then id jtag cos your warranty is gone if your bin counter isnt at 0:(

EDIT: true.try another computor as kies was designed for winXP 32bit and has problems with 64bit drivers.if you can get your hands on a fresh 32bit PC your luck just might change.Read on another thread that some dude had a heap of the same problems and fixed them on his girlfriends vista 32bit PC first try!!.
[Galaxy S II Q&A, Help & Troubleshooting] dheerpat:
hi..

which firmware/kernel u flashed since iam also having same variant(G) and after odin facing the same problem that i can get into download mode but phone boots in logo and big yello triangle,,

pls help