Database Develop

[Q] launcher crash after factory reset

Hello,
I have a SGS I9000 Gt from France I think.
Everything was running good. I installed a bunch of apps when I first got the phone, checking stuff out. After playing with it for a few months I now have a good idea of what apps I would like to keep.
I decided to do a factory reset so I could start fresh when froyo does come out.
I performed three button recovery and did factory reset and wipe cache partition.
Problem is when I reboot I constantly receive "The process "blank" has stopped unexpectedly. please try agian." message, and I hit force close and it just pops right back up. TwLauncher, Daily briefing, acore, and a google one.
I did notice that in the recovery mode menu I get some red text saying "multicsc : can not acces to /system/csc/XEF/system/" But when I go through the steps to reset and clear cache, it does it and gives me a message "wipe complete"
I removed battery and sim card No sd, and tried again with no luck, every time I boot now same thing, apps keep crashing.
I hope that makes sense I don't really know what to do.
So yea any help would be great!
Thank you so much for your time.

I almost have the same problem here.
I updated the firmware with Kies, using the default firware that was found by Kies.
I guess it has to be a custom made ROM made by/for my phone service provider (Bouygues, a French company).
Upon restarting, I get the same pop-up messages. Cannot close them fast enough to use anything. My phone is not usable, though not bricked.
Ps : formerly running off-the-factory custom Bouygues rom. Rooted and using OCLF or something lag fix.

I solved at least MY problem :
Do a factory reset and wipe cache AND user data. Simple as that
The answer was actually in the [Warning!!!] Do not flash... thread. I should slap myself for not looking into it first.
Hope it solves your problem too.

Thanks for the help, but how do you how did you wipe user data? Maybe I am blind but I don't see it?
I think I did that when I did the factory reset. When I do boot up however, my original unlock pattern is still set...so I don't know wtf is going on.
FIXED!!
I used Kies Registry Patcher v.1.6.0.0
then reset user data and cache WORKS GREAT AND I HAVE FROYO NOW!!

[Q] SGS issue force close on receive call

Hello
I just installed Darky's 5.2 ROM over my stock 2.1-update1 and everything works fine, but whenever I receive a call something (dialer?) gets a force close and the call is rejected together with a temp. loss of signal.
Then everything is back to normal...
Any steps I'd take? I'm pretty new to this.

have the exact same problem... can dial out no problem but only receiving calls. so thinking about whether I should flash another rom until this is fixed.....

I was wondering could I just do a factory reset and then flash the rom over again? Do I have to disable the voodo lagfix before? Not too sure how this works heh.

I don't have this problem. But whenever i am in the game "flick kick football," I get some random hangs, and is forced to close. I suspect that happens when I get incoming calls. Anyway to confirm this?

Jule1k said:
Hello
I just installed Darky's 5.2 ROM over my stock 2.1-update1 and everything works fine, but whenever I receive a call something (dialer?) gets a force close and the call is rejected together with a temp. loss of signal.
Then everything is back to normal...
Any steps I'd take? I'm pretty new to this.
Click to expand...
Click to collapse
I have the same problem. I recived a call, something force closed, the signal dropped and i lost the operator. I had similar problems with bluetooth and file manager before on this ROM, but I re-flashed it and everything worked again.

no problem here with Darky's 5.2 ROM and the Clean Guide Instruction, i just received a call without any problems

I used the easy guide and did not clean anything or do a factory reset, I just followed it like a dumbo. I came from 2.1-update1 stock JM5 kernel with a ton of apps installed, if that helps.

hey I think I found a solution to this. I went to recovery mode, wiped cache, wiped dalvik, did a factory reset and voila, receiving calls works without force closing.
phew.. was about to download another rom. anyhow, hope that works for you Jule!
still a few problems with the ROM that i encountered:
- my AT&T home button is not working.... not to sure whether there will ever be a fix for it
- media volume, even set to max, is not working when playing movies and youtube.

[Q] Galaxy S i9000 won't factory reset and force closes frequently - now with logcat

Hello all,
please forgive me first of all because I've had very little sleep due to this issue. And its a long thread, but more detail is better generally I believe.
First, some background, and unfortunately, it starts with my wifes phone.
My wife has a Galaxy S GT-i9000 on Orange in the UK. She has had it, probably about a year maybe at most. She has a few apps that she has downloaded but nothing major and on first looks when I got it nothing I expect would cause this issue, just facebook etc.
My wife came home and said, my phone keeps coming up with a message saying force close. Ahh, I thought, some apps gone nuts, but alas, it appeared to be many apps including Maps, Google Upload (I assume this is a system process), Facebook Katana and many more, probably about 20 Force Close messages pop up one after the other and it lags whilst trying.
Odd, I thought, I also noticed the icon for one of the apps on her homescreen had changed to the default White and Green one with the android on it.
I suspected something had gone wrong (obviously), I asked if she had rebooted it and she said she had. So, I rebooted it again, just incase. Same problem.
I then thought it might need an update, it was running official Kies 2.3.3 (or was it 2.3.4, I forget) so I plugged it into my netbook and ran Kies, had to update that as it didn't have the latest application update. I then started the firmware update, after backing up the phone using Kies.
Halfway through the update, Kies popped up a message saying something went wrong and that I had to unplug the phone, take out the battery and reboot. Odd, I thought as the phone was telling me to not doing anything. I waited a minute, nothing further happened, so I did this. Then I got the Black Screen of Death with the phone, the dots and the computer screen.
Crap!!! I thought, I managed to get into Download mode, and reflash it using what I believe was an official ROM using Odin. I then rebooted, and found that it STILL had the data on it and it STILL was doing the force close. At least I had it back to "working" though so I was mildly happy.
I then did a factory reset using the menu system, erased the USB storage (there is no external SD card in her phone) and rebooted, still force closing but prompting me to setup again. Weird. I went through the setup slowly, as every second or so a force close would popup, then when I completed the setup (which still had the wifi settings, account settings etc in it) the System Setup crashed with Force Close. I then rebooted and got to the Home Screen, but still crashing.
I rebooted and used the recovery screen to clear the cache and factory reset, despite the warnings I will lose everything, nothing was wiped.
I tried to update using Kies again but it tells me that the firmware/device is not supported. I am now trying to see if I can use Odin to install a Kies supported firmware. So that I can then try an update using that again.
Anyone got any suggestions, at present, my thoughts are, I was going well within the realms of warranty up until I reflashed it using Odin to try and get back in as I'd only used Kies to update and the issue "just started happening" without my missus doing anything.
There are no signs of damage on the phone and she tells me it was just sat on her desk all day.
So, my question is, what now? I'm of the opinion based on the above that if I can't reflash a warranty supported Kies update, then maybe a custom ROM will be worth a shot to see if its a hardware failure or if its software. I just have never had an issue like this with my HTC Desire and I've ran many custom ROMs and standard ROMs on it.
I do have the .tmp file of the update Kies downloaded, and I also have a Binary folder which has some file inside a couple more folders but its not a .tar or a .zip because when I try renaming it (after a copy) it won't open.
So, suggestions on a postcard, thanks if you got this far through this nightmare. All help massively appreciated.
Edit: it appears to be the same issue as this: http://forum.xda-developers.com/showthread.php?t=822238
I'll try some of their suggestions. Today I also did the *2767*3855# today which I found after a bit more searching. Same problem after a reboot. Force close and data still there.

I've tried and tried again to do various solutions for this, I've even ran a logcat using adb to see if I can see the problem. I suspect its a Dalvik Cache issue in that its unable to write to it for some weird reason.
I've downgraded it to Froyo following this guide: http://forum.xda-developers.com/showthread.php?t=1100906
It now detects in Kies and offers me a firmware upgrade. I suspect it will die again though if I try due to this Dalvik problem.
Wiping cache does not wipe the cache. Everything still appears to be there on reboot as mentioned above.
Here is a copy of the LogCat with Java errors all over it: http://leenukes.co.uk/downloads/logcat1.txt (its quite long)

I guess nobody knows. Today I will speak to Orange to try and get it fixed or replaced.
Sent from my HTC Desire using Tapatalk

We've been told it is beyond repair. We will see what they say when we go back into the shop. Its still in warranty so I don't see why they won't replace it.
Sent from my Galaxy Nexus using Tapatalk

I have a friend with a Galaxy S from Orange Romania and suddenly the phone kept showing Force Close on every App. He had 2.2.1 if I remember right. He whent with the phone to an Orange Shop and they only do a factory reset but data was not wiped.
So what i have done for him:
- start the phone in Download Mode
- start Odin with repartition check and XXJVT (2.3.5) firmware with 3 files (code, phone and CSC) + pit file .512
- after reflashing the phone does have all tha data, so i resarted in Recovery Mode and done a Factory Reset and a Cache Wipe
- i flashed Speedmonde Kernel k16.10 and do again from Recovery Mode a Factory Reset, Cache Wipe and Davlick Wipe.
On reboot the phone was CLEAN. No force closes for a week now.
Sorry for my English hope it helps!

ZiDanRO said:
I have a friend with a Galaxy S from Orange Romania and suddenly the phone kept showing Force Close on every App. He had 2.2.1 if I remember right. He whent with the phone to an Orange Shop and they only do a factory reset but data was not wiped.
So what i have done for him:
- start the phone in Download Mode
- start Odin with repartition check and XXJVT (2.3.5) firmware with 3 files (code, phone and CSC) + pit file .512
- after reflashing the phone does have all tha data, so i resarted in Recovery Mode and done a Factory Reset and a Cache Wipe
- i flashed Speedmonde Kernel k16.10 and do again from Recovery Mode a Factory Reset, Cache Wipe and Davlick Wipe.
On reboot the phone was CLEAN. No force closes for a week now.
Sorry for my English hope it helps!
Click to expand...
Click to collapse
Sound advice there mate, other thing I would have done is in recovery mode before the ODIN flash I would have format sdcard, making sure you have removed BOTH the external sd and the sim card, as it can wipe them as well.Then flash through ODIN as per instructions above.
Using JVT I would flash either speedmod or semaphore 2.1.1 which I personally use.
Happy flashing!!

turns out it was water damage and some parts corroded.
Its going to be claimed for on insurance.
Sent from my Galaxy Nexus using Tapatalk

Hello all,
the phone came back from repair yesterday, yay!
the phone now however, doesn't appear to lock onto a mobile signal for very long. Boooo!!!
After sending off for repair using insurance, we got the phone back yesterday but it now appears to be broke in another way. It won't lock on to a mobile signal, wireless is fine but data network and sometimes just mobile signal is patchy and keeps dropping.
I've just reset it to factory defaults, same problem. What I did notice, which is odd is that since it came back from repair, its now unlocked and I can put another networks SIM card in it, same issue there too so I know its the phone now.
I'm going to scour the forums to see if anyone else had/has issues like this, it is running the latest firmware now and a full wipe really did fully wipe it this time, as opposed to last time with its issues due to water damage. One step forward, two steps back?

Its going back to the insurance company. Especially as Orange were suggesting that we pay £70 for a new handset.
Absolute fool I had on support today, yesterday I at least had someone sensible.
Sent from my Galaxy Nexus using Tapatalk

SGS force close problem
Hey guys i m facing a similar solution in my samsung galaxy s. After deleting all the contents and uninstalling the applications, I m getting them back after rebooting and all applications has to be force closed after rebooting.
Please help me to solve this problem

Signal issues
leenukes said:
Hello all,
the phone came back from repair yesterday, yay!
the phone now however, doesn't appear to lock onto a mobile signal for very long. Boooo!!!
After sending off for repair using insurance, we got the phone back yesterday but it now appears to be broke in another way. It won't lock on to a mobile signal, wireless is fine but data network and sometimes just mobile signal is patchy and keeps dropping.
I've just reset it to factory defaults, same problem. What I did notice, which is odd is that since it came back from repair, its now unlocked and I can put another networks SIM card in it, same issue there too so I know its the phone now.
I'm going to scour the forums to see if anyone else had/has issues like this, it is running the latest firmware now and a full wipe really did fully wipe it this time, as opposed to last time with its issues due to water damage. One step forward, two steps back?
Click to expand...
Click to collapse
Sounds like a modem issue, where the techs at Orange put in the wrong modem for your firmware. I did the same thing when I upgraded from Froyo to Gingerbread.
Alternately, it could be a broken external antenna connection as a result of the corrosion from the water damage. Google "no signal fix" and look for a site that ends in .uk
Just a thought for others who come across this problem.
I

[Q] Rooted for the first time, lost any cellular connection. I need a step by step.

So I finally took the plunge today and rooted. I flashed the most recent Sprint version of ViperROM, and everything was going just fine and dandy, I was all giddy setting up my MoDaCo UI mods, etc, until I tried to send a text. Tried to send for 5 minutes, got the fail message. Well, that's weird. What about 3G data? Nope, nothing. Maybe the ROM is bad? I flashed the stock ROM by viperboy, also didn't work. Same problems. So now I'm stuck with no cellular connection and I need it soon. How do I fix it? (Note that I followed my tutorials step by step and everything works except cellular connection. Also note that it says I have service and that data is going in/out, but it's not actually sending/receiving anything. It seems that I need something called an RUU, but I have no idea what that is or where to get a correct one and how to flash it.
Please give me a step by step (I'm using TWRP if that matters), as this is my first time rooting or doing anything more advanced with my phone past advanced themes in Nova Launcher. I'll need links if you have them, or at least where to look. Please help me, because don't want to go back to stock after getting all my awesome tweaks already!
And yes, I have updated my PLR and Profile in the system updates menu, same results.
EDIT: I fixed it, yay! I tried clicking UICC unlock in the software update menu. It said no profile update available, and then it started working (it's actually faster than normal! ) It may have been the profile update that did it and it took a second to update, but it works now! Yay! I even rebooted to make sure it was going to stay after a shutdown, etc, and it did! I guess I should check all option before posting a thread next time... (If you can't tell I'm extremely happy it works!)
EDIT 2: It stopped working again :'(. Now I'm constantly losing the 3G connection that I "had" and messages and data only work about 10% of the time they say they're connected. Wifi still works. When I try updating the profile, it says it could not be updated and to try again later (this is after several tries and a reboot). I try to update the PLR and I get error code 1233. Apprently this is an HTC specific error with no know fix? I try to do the UICC unlock, and it gives me the same error as the profile message.
EDIT 3: It seems Sprint is having issues in my area, I will update again if they resolve it or reply to my tweet.
EDIT 4: They told me to go restart the booster thingy I have in my house, and now my connection is working for now...

After Binary Update - Cannot Make Outgoing Calls...???

Hello Everyone...
Posting here first rather than in the "Update Failure" thread because I'm not so sure I have a "failure" with the update....just an issue after the udpate.
I have 2 cloned HTC M9 phones. I say "cloned" as they are exactly the same make, model, ROM, etc (one business, one personal phone). They have the following information if needed:
Sprint HTC M9
SuperSU Free v2.65
Custom ROM ViperOneM9 3.5.0 with no custom kernal
Android 5.1
HTC Sense 7.0
Kernal (standard) 3.10.49-perf-g26c593c
[email protected] #1
SMP PREEMPT
I updated some apps this as I normally do through Google Play. A little while afterward I was prompted to update the SU Binary. I did so on one of my phones. I hit the TWRP option (on the right side of the prompt screen), nothing happened, phone did not reset so I rebooted into recovery. The update ran automatically and the phone rebooted.
I noticed two issues (perhaps there are more). The huge problem is that I cannot make OUTGOING calls. I use a custom dialer PixelPhone Pro. I click on a contact to dial and nothing happens. I type in number to dial, hit the green "send" button to make the call, nothing happens.
I also tried the stock Phone app....same thing, cannot dial out.
I attempted to update the Profile and PRL for the phone, however, as that appears to need to make a "special call" that function is not working either
The other problem I noticed is with an app I have called Quick Settings. The app is always accessible through the pull-down notifications on the phone. Although the app is still installed and functional, it no longer appears in the pull-down notifications. I tried to reset the option to show it there (turning the option off and back on) and it will not show up despite the proper setting chosen.
I still have full root access as I tried a couple root apps (such as Titanium Pro) and have full root access.
I have been prompted on my other phone to update the SU Binary and I am concerned with doing so. Any idea why this is happening and how I can troubleshoot and fit my outgoing call issue??
THANK YOU all very much!!
Scott

Hey guys....
Anyone else have this issue or similar?? So what are my options....how do I get my phone back to being able to make calls??
Thank you for your help....
Scott

Scudderb said:
Hey guys....
Anyone else have this issue or similar?? So what are my options....how do I get my phone back to being able to make calls??
Thank you for your help....
Scott
Click to expand...
Click to collapse
**UPDATE**
Still problems....
Right after I first updated the binary the "only" problem was that I could not make calls which I could use the other functions of the phone. I rebooted the phone and I cannot reach any function of the phone because I constantly get the message "...the process com.android.phone has stopped" obviously related to the previous problems.
I dirty-flashed the ROM...that did no help. I even tried to flash an older SuperSU version (I don't know what that would have done....I'm running on HOPE now ) and that didn't help. Re-dirty-flashed the ROM a second time. Again that didn't help.
I flashed an old backup and THAT WORKED fine. Problem is that the backup is 6 months old. I could quit and totally clean/wipe/install the ROM and start again from scratch but I reeeeeeallly don't have time for that at the moment.
Is there ANY way I can simply get my com.android.phone process back?? Why did all this happen in the first place??
ANY help is greatly appreciated!! THANK YOU!!!