[Q] Flash with Repartition doesn't remove Force Close - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi,
I installed the speedmode and tried to use the lagfix and root on gingerbread. It obviously didn't work. After that I couldn't boot. After flashing different Android versions (2.1, 2.2, 2.2.1, 2.3) using repartition and three files I still get Force Closes after booting (for examplfe immediatly after booting by the Setup Assistant).
Browser Works. I can phone people. Gmail and Google Maps Force Close. Adding a Google Account leads to force close.
What could I have damaged that can not be undone by flashing with repartition and three files?

try to format the sd intrernal
and wipe/data cache
Sent from my GT-I9000 using Tapatalk

I made a Soft- and Hardreset several times. When I click on settings -> sd -> Format there doesn't seem to happen much. Takes a few seconds. Even most Data on my SD remains.

try boot into recovery and wipe data/cache and factory reset.... has solved the most amazing problems for me...

Related

Broken /data partition

Hi,
After playing around with CyanogenMod and MIUI, I'm getting a "Welcome to Milestone" screen loop: every-time I reboot, I get the "setup wizard" one usually gets when the phone is turned on for the first time.
So I get a factory reset on every reboot... And I just noticed that it's only working properly on first boot: if I reboot, I get a whole bunch of process errors about random processes including android.process.acore in addition to welcome screen.
To get rid of these, I have to do a factory reset from recovery.
Here are the different steps I tried to recover:
Wipe cache, dalvik, factory reset
Re-applying the CyanogenMod and MIUI update.zip (not at the same time obviously)
Format SDcard
Re-flash GOT's Froyo sbf (using RSD Lite)
Downgrade to Stock 2.1 (using RSD Lite)
Re-flash bootloader (90.78)
Downgrade to stock 2.01 (I modified the sbf file to replace the bootloader with my version, as I found out bootloader is not downgradable)
Apply 2.1update1 OTA update
Boot without SDcard
And I'm stuck at the same point and running out of ideas on how to fix this.
So basically my phone is usable, as long as it doesn't reboot.
Any help would be really appreciated!
Thanks in advance
EDIT: After some testing it appears that data partition may be messed up (root explorer can't access it, and every app using storage in /data forces close).
Is there a way to recover it?

[Q] Force Close on Startup. Flashing doesn't Help

Hi,
I had a gingerbread version on my sgs. I flashed with a speedmod version which is intended for 2.2.1
That was obviously stupid. After I did that i tried to activate the lagfix and played around in the "Recovery mode menu". I don't know exactly what I did there.
My device did't boot anymore so I flashed it several times including repartitioning. After flashing i could boot android but the startup manager and loads of other applications keep force closing. I don't know how to stop them do that. Flashing many different versions (jpu, etc.) didn't help.
What coul'd I have destroyed that is not recovered by flashing with repartition?
Im pretty desperate...
after flashing jpu try to flash speedmod kernel then get into recovery mode and activate lagfix again.
tell me it works or not,thanks.
The flash of the speedmode seemed to went fine. Afterwards I still get force closes on startup. So I went to:
Recover mode -> advanced features -> lagfix options -> Convert Data to Ext
After reboot it says: "New filesystem config detected. Convert? I choose yes. Then it converts some stuff and reboots. Then he it says the exact same thing: "New filesystem config detected. Convert? I choose yes again. It converts some stuff and reboots....Exact same thing....
I choose "No enter recovery mode". There I choose disable lagfix. After reboot it says "New filesystem config detected. Convert?" I choose yes. It converts some stuff. After reboot it doesn't ask again. Still get force closes.
In the system my browser works. Pressing home button produces force closes. Trying to sync my google account and many other things force close, too.
Next I try:
Recovery -> lagfix options -> convert system -> reboot
"System conversion requested Convert?"
I choose convert to ext4.
It says done but doesn't boot beyond the first Galaxy S Screen.
Had simmilar problem, at the end I had to flash a 2.1 version with pit-filen from samfirmwar.com. Past that I could upgrade again to 2.3
Tried a 2.1 version. Didn't work either.
paninomatic said:
Tried a 2.1 version. Didn't work either.
Click to expand...
Click to collapse
2.1 with pit 512 and repartition checked is my get out of a broken phone route .
jje
Which 2.1 do you use?
hlaube said:
Had simmilar problem, at the end I had to flash a 2.1 version with pit-filen from samfirmwar.com. Past that I could upgrade again to 2.3
Click to expand...
Click to collapse
Did you use Pit both times?
I did and flashed Gingerbread after Eclair. No effect. Isn't there something else I can do besides flashing tons of firmwares?
any 2.1 rom (eclair) maybe try something like JM1 or JM8 it think thats 2.1
I allready had tried JM1. After booting it I still got force close messages.
Since I tried allmost all firmwares from samfirmware.com and still got force closes for many programms including the setup assistant, is there anything I could try besides flashing tons of firmwares?

[Q] How do you flash a new ROM over cm7 or fix cm7?

Okay so I was a little too hyper with this ROM and I ended up installing everything from titanium backup onto cm7 which messed up a lot of things. I got the "com.android.phone unexpectedly stopped working" error and a few others. I tried wiping the davlik cache, wiping cache, and even a factory reset along with reinstalling cm7, yet com.android.phone is still gone (I have no contacts or dialer available in apps). I'm lost in what to do next. I would like to flash a new rom or if I could, flash a completely-back-to-normal cm7.
Thanks,
Eric
Go back into recovery and flash cm7 again, if you want to flash another rom flash back to stock jf6 and install a different rom.
I've tried to flash cm7 in recovery, sometimes it gets rid of the apps like a memory wipe but it won't reinstall the apps that are supposed to come with cm7 like dialer and contacts. How can I flash it to jh6? Master reset only got me to a memory wiped cm7.
You should not be running cm 7 if you do not know how to flash stock using odin one click.
Secondly, reflashing rom will reinstall all system apps. Make sure you are formatting system and cache then flash rom
Sent from my GT-I9000 using XDA Premium App
Just a thought but could they go in safe mode, then uninstall the apps that cuase a problem. And delete there data. (hold down menu button after at&t screen comes up)
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Just trying to get my 10 post so i can help people that need help dev section
You need to use the ONE-CLICK ODIN to STOCK
http://forum.xda-developers.com/showthread.php?t=731989
good luck!

[Q] Just rooted

Well I just rooted and here's the deal, every time I try to install an app from the market either the market force closes and i cant get to install it either my phone kind of restarts it shows the boot animation and then its back to the homescreeen.
Another thing is that market does not autoupdate but when I leave the phone in standby with the wifi on it shows the boot animation again and its back to the homescreen again I believe its the same thing that happens when try to install an app also.
I rooted my phone trough the SmartFlash methond by installing a firmware patched with CMWT.
Do you know what I should do in this situation?
Best regards.
Edit: I noticed this happens also when I try to install any kind of apk.
What I have tried until now: - fix permissions trough CWM (didn't work)
- dalvik wipe (didn't work by it's own, haven't tried it after factory reset as factory reset fixed the problem)
Firmware version: V20N - Germany
Solution: - wipe data/factory reset from CWM
Thank you for the help you gave me
What is your rom version btw?
Sent from derp-mobile
Best will be a factory reset + dalvic wipe from CWM. But make a backup before, so you can restore it

Phone freezes at Homescreen and goes into a reboot loop

Samsung Galaxy S i 9000 keeps rebooting after booting up to the homescreen. I don't know why this happened as this phone is in my brother's use, he says that it started happening right after he cleared the cache from Google Chorme. The phone is on 4.1 custom rom, TAJB something running Devil Kernel. What I have tried so far; *Rebooting phone without memory card. *Wiping Delvik cache *deleted Google Chrome files from the recovery file manager. Nothing has helped so far, I believe some data in the phone has corrupted which freezes the phone a couple seconds are booting up. Any help would be appreciated.
pakora said:
Samsung Galaxy S i 9000 keeps rebooting after booting up to the homescreen. I don't know why this happened as this phone is in my brother's use, he says that it started happening right after he cleared the cache from Google Chorme. The phone is on 4.1 custom rom, TAJB something running Devil Kernel. What I have tried so far; *Rebooting phone without memory card. *Wiping Delvik cache *deleted Google Chrome files from the recovery file manager. Nothing has helped so far, I believe some data in the phone has corrupted which freezes the phone a couple seconds are booting up. Any help would be appreciated.
Click to expand...
Click to collapse
Usually wipe data, wipe cache and wipe dalvik is the way to try and fix those problems. But if you do a "wipe data", you will loose all user data/apps/sms, which you should backup beforehand (with titanium backup, sms backup and restore etc). But since the phone doesn't boot, you can't do that. So i recommend only wiping cache and dalvik flashing another rom on top of it. If you can't find the old rom, you should at least stay within jelly bean (cm10.2 for example).

Categories

Resources