I have a Bell Vibrant. Voodoo Lagfix and rooted.
I unapplied the lagfix by creating a folder inside the Voodoo folder called "disable lagfix". Then rebooted the phone. After the lengthy disable process, the phone booted back up. I then went into settings and formatted the Internal SD card.
Then I rebooted the phone, went into 3 button recovery mode, and did a factory reset and cache wipe.
Now when the phone boots back up, it still detects the voodoo lagfix. Then boots up but all I get are constant force close. I can't do anything in the phone other than continually press the force close button.
In particular, it loops between com.google.process.gapps and android.process.media
What can I do to get my phone working again?
Thanks!
I had this same problem on monday, to fix it i used the REGEDIT trick on kies to make it think it was an older version of firmware, and reflash the latest firmware on kies. Now everything is fixed and working well.
How did you get Kies to recognize the phone, without being able to select Kies mode when attaching USB cable to the phone?
davanw said:
How did you get Kies to recognize the phone, without being able to select Kies mode when attaching USB cable to the phone?
Click to expand...
Click to collapse
I patiently went to do another factory reset through the privacy settings tab, took like 5 minutes of advancing when there was a short gap before another fc popped up. Once that was done, the force closes slowed down enough that I could connect it to kies. took patience but eventually I got it working
Same problem here. Re-flashed with Odin.
Sent from my GT-I9000 using XDA App
Related
Yesterday my phone started acting up:
- Applications started failing
- Couldn't uninstall apps (it acted like they uninstalled, but they were back after reboot)
I tried wiping from recovery mode, but all apps are still there
I've even tried using Odin to do a master clear and reflash to stock, yet all the apps are still there. All the startup apps crash when I restart the phone, including the launcher, so the phone is unusable.
I'm desperate here, as I'm without a phone... any help is greatly appreciated
Ok put the phone in download mode but don't reboot to download mode where you see the yellow droid. Make sure you are at the home screen. Then run Odin then plug the phone in and make sure odin recognizes it. Then hit master clear and the phone will be wiped. Then put it back to download mode, with the yellow droid and then flash back to stock.
That's exactly what I've already done, but I'll try it again
Actually, follow up question; how do I put it into download mode without going to the yellow screen?
Another edit: did you mean to say debugging mode?
Yeah sorry I keep referring to usb debugging as download mode sorry for that.
setting > applications > development > usb debugging
ok, completed the master clear. It stated everything was successful. After the reboot, the phone came back, all apps still installed, and all apps still trying to launch on startup and FC-ing immediately. Going to try the reflash to stock now
Same thing... after master clear and reflashing, everything is still there...
Do a facotry reset from the privacy menu and see how that works if not then reboot into recovery and clear data/cache and see if that does anything. Master clear completely wipes the phone there is nothing on it at all. Can you get into any program to uninstall stuff.
I would take it back and tell them its got a mind of its own.
I've tried all of those things multiple times. When using uninstall programs, the device acts like it's uninstalling, but does it way too quickly and says it's successful. They're still there, though, and after I reboot they show up again.
brookssw said:
I've tried all of those things multiple times. When using uninstall programs, the device acts like it's uninstalling, but does it way too quickly and says it's successful. They're still there, though, and after I reboot they show up again.
Click to expand...
Click to collapse
Ok here is what you do...Menu/settings/sd card and phone storage..scroll to internal storage and unmount sd card...then format sd card...Then reboot in to downlaod mode and reflash with odin 1 click...after it boots up reboot into recovery mode and clear cache and user data...then reboot and you will be good to go...You willl lose all your stuff on your internal storage so back up anything important...
Sadly this didn't do the trick either, and I unmounted/formatted the internal twice for good measure. It's like there's a hardware problem, or the storage is locked out somehow. I gave up earlier today and called in the warranty, so there's a refurb on the way now. I hate to give up, but I think it was the only remaining option
So basically, I registry hacked my PC so that I could update using the official 2.2 update in Kies for the Galaxy S.
Since I updated it, the phone has come unusable. Whenever it boots up I am plagued by force close messages (calendar storage, media, memo etc.).
I’ve tried getting into safe mode and hard resetting it. I can’t get either of these menus up. Tried holding down [vol down] key and pressing the power button, it just boots as normal when I do this.
Anyone have any ideas what’s wrong here?
I have the same problem as well, except that I am in a Scandinavian country. I did remove the lagfixes, and the only thing left was the rooting. I heard that the USB disconnected and reconnected in Windows under the firmware upgrade. When the smartphone was booted up, it still appeared to be 2.1-update1. So I did a hard reset, and that's where it begun to be softbricked with all the looping crash messages ("The process X has stopped unexpectedly. Please try again."), which are the following processes:
android.process.acore
com.sec.android.app.twlauncher
com.sec.android.provider.logsprovider
com.cooliris.media
com.android.calendar
com.sec.android.widgetapp.infoalarm
com.android.phone
alexdrans said:
Tried holding down [vol down] key and pressing the power button, it just boots as normal when I do this.
Click to expand...
Click to collapse
you have to hold down both [vol down] + [start] and then press the power button to start the phone in download mode. [vol up] + [start] and power to get into recovery mode. in all there are three buttons involved which have to be pressed all together. [start] is the big one on the front side of the Galaxy btw.
I had similar problems with the Kies update. So i wiped it clean, installed an old 2.1 version with odin and then installed on of the modifed 2.2 version from the development section here, also with odin. Now it works like a charm and with OCLF blazingly fast too.
I am experiencing the same problems...
how would i go about wiping the phone clear and back to the 2.1 version?
i only got the phone the other day and can barely use it now!
cheers
Guys i didnt wanted to open up a new thread so ill go ahead with my problem here.
The question is about the Kies Registry Patcher so i can force Kies to show me the 2.2 update.
My native country is Macedonia, and i can see two options to pick from with the Kies registry patcher for my country. One of them is the current versions i have on my phone and its representing the 2.1 update 1 android version.
To what 'Spoof Product Code As' i should set the registry patcher considering my location to get the proper update for my phone ?
alexdrans said:
So basically, I registry hacked my PC so that I could update using the official 2.2 update in Kies for the Galaxy S.
Since I updated it, the phone has come unusable. Whenever it boots up I am plagued by force close messages (calendar storage, media, memo etc.).
I’ve tried getting into safe mode and hard resetting it. I can’t get either of these menus up. Tried holding down [vol down] key and pressing the power button, it just boots as normal when I do this.
Anyone have any ideas what’s wrong here?
Click to expand...
Click to collapse
Have you tried click settings on your phone then privacy then factory reset that should solve it
Well, I had the same issue and here is what I did. I'm in Canada (not sure which thread my phone falls under as our Vibrant is not the same as the U.S. one) and my provider is Bell Canada. Well...what I did was this; I saw the update out there, so I connected through Kies, ran the update and waited nervously for it to boot. After it did boot, I got several Force Close errors, so I rebooted it. It came up more easily the second time. After it got done it's card scanning and crap, it was ready to go. BUT...I started getting random Force Close errors with different apps. I simply could not use ANY email app other than the GMAIL one itself, they just kept crashing. Handcent crashed too, but with a reboot would work. Well...this just didn't seem right as a college of mine did his at the same time and was working fine. So, today I did this; I copied ALL my useful data off the internal SD onto my external SD and then removed that external SD card. Then I formated the interal SD. Then I went and did a factory reset. After that, my phone worked perfectly! I put my external SD card back in and all is good now. Haven't had one error since. Now, before I did this, I'd get at least 1-2 Force closes per hour but I re-did my phone up about 3 hours ago now and like I said, no errors.
Maybe try this before you update:
1: Save old data off of Internal SD
2. Remove External SD card (just to be safe)
3: Format Internal SD card
4: Apply Froyo update
5: Reinsert External SD card upon completion and sucessfull reboots
6: Part-tay!!!!!
Just make sure you do a cache wipe and a user settings wipe.....you should have already backed up your stuff so worst case you will just have to reinstall everything. HOLD down Volume UP button, Home button and power button all at once, it will boot into recovery mode, use the volume rockers to select wipe cace and then use them to wipe the user settings, reboot and should be good.
Hi,
I want to say that everyone is very helpful in this forum and you all rock. I'm having some problems with my rooted samsung captivate. I installed the I9000 Full rom, and it was running fine for a few days then I notice it was very sluggish, so I did a factory restore, but data and apps didn't delete. So I then when in to recovery (R2) and deleted cache and all user data files, then it did a factory restore, and it went in boot up pass the att and samsung S i9000 screen and when to the lock screen, but once I unlock the phone, its just in the black screen, when I click and hold on to the home button it goes to recent, no recnet application and under Task Manager, I have 0 active applications. It won't load any programs or apps. I tried restoring the phone by holding the down volume key and power on button, it goes to R2 recovery and then reinstall package, but it can't find the package. I have it on the memory card, but I guess I deleted it from the internal memory when I did a factory restore. Am I screw, or can someone guide me through this and fix my fone. Thanks in advance. XDA Rules.
Odin one click back to stock, assuming you can get into download mode. Also do a master clear just to be sure. A fresh start might be just what your Captivate needs.
Sent from my SAMSUNG-SGH-I897 using XDA App
The same thing happened to me yesterday. Phone was on, battery fully charged. I got on my flight and left it on (forgot I guess) and when I got off the flight, the screen was black. I'll also add, that over the past 3 days the phone was starting to get extremely sluggish (for no reason that I can think of). But back to the rest of the story...
I couldn't get it to turn on, so I pulled the battery and tried again. This time I got the AT&T logo and the Samsung animation. Once the animation was completed the screen goes black.
The phone is still on. How do I know? If I touch any of the bottom buttons they light up.... and stay lit up until I do a battery pull.
Deleted/cleared everything, same behaviour.
I tried reflashing JI6, it works but fails to reinstall the packages, otherwise same behaviour.
I tried reflashing JF6, same behaviour.
The flashes always succeed, but always end up in failure.
Now for the interesting part. I went into recovery mode on JI6. I try to format the internal /sdcard, I get a message that it cannot mount /sdcard /dev... not found.
So to recap, phone not working, recovery mode available, download mode available. adb doesn't seem to be working, but if someone can tell me how to access the phone with "adb shell" while in recovery mode, I might be able to diagnose why /dev... is not mounting... Or at least how I could fix it using adb.
Any help would be appreciated. I'm traveling and needless to say, this is a huge inconvenience, I'm lucky I had my backup phone to at least be able to get online and be able to make calls.
HI,
thanks for quick response. I can get to the recovery mode, where the android holding the shovel. But when I load Odin one click, it don't seem to detect and do anything. o success 0 failed. I installed the samsung captivate windows 7 drivers, the funny thing is when I plug my brink phone in the usb port, it say unrecongize usb. Any other suggestions. Thanks
hksmr2 said:
HI,
thanks for quick response. I can get to the recovery mode, where the android holding the shovel. But when I load Odin one click, it don't seem to detect and do anything. o success 0 failed. I installed the samsung captivate windows 7 drivers, the funny thing is when I plug my brink phone in the usb port, it say unrecongize usb. Any other suggestions. Thanks
Click to expand...
Click to collapse
the shovel is NOT recovery mode, it is download mode.
have ODIN running BEFORE you get your phone in download mode
Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Titerepayaso said:
Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Click to expand...
Click to collapse
Sounds pretty accurate. You'll have to get a jig to get in download mode, flash stock Odin KK4 to fix w/e happened during your testing.
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Titerepayaso said:
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Click to expand...
Click to collapse
Make a backup with ADB.
Once that's done, push download mode with it and get Odin KK4 (without bootloaders). You'll have to start from there to fix w/e went wrong.
You don't have to wipe your sd doing so but you will lose your apps and such. If you backed up your phone with your Play Store account, it will re-download your apps as you're done booting up.
To get back up where you were, grab Corn Kernel, flash it with Odin 1.87 and then follow the full instructions of the ROM you wanna use.
Running a Captivate that I rooted and upgraded to 2.3 over a year ago. All was working well. This week it began freezing after it fully loaded after a reboot or power-on. It will go through the ATT, the Corn logo, and the S animation. It will scan the USB storage devides (internal and external) and then quietly freeze. It will sit there with the wallpaper moving around, but the first key stroke done after all has been loaded up will cause everything to freeze.
While it is starting up, I can enter my passcode, use all of the menu buttons and get to applications or settings. However, once the scanning is done, wherever I am will freeze. I can get all the way through the perform a factory reset procedure before the scanning is done, but it I will run out of time before the phone can start the reset.
Seems like something in 2.3 got corrupted and I need to reload the software without going through the boot-up (I went through Kies, but once the phone booted up, it disappeared from Kies and it told me the phone was disconnected).
Any step by step to either repair 2.3 or to install another droid system prior to the phone booting up? I'd appreciate the help.
ktvanhorne said:
Running a Captivate that I rooted and upgraded to 2.3 over a year ago. All was working well. This week it began freezing after it fully loaded after a reboot or power-on. It will go through the ATT, the Corn logo, and the S animation. It will scan the USB storage devides (internal and external) and then quietly freeze. It will sit there with the wallpaper moving around, but the first key stroke done after all has been loaded up will cause everything to freeze.
While it is starting up, I can enter my passcode, use all of the menu buttons and get to applications or settings. However, once the scanning is done, wherever I am will freeze. I can get all the way through the perform a factory reset procedure before the scanning is done, but it I will run out of time before the phone can start the reset.
Seems like something in 2.3 got corrupted and I need to reload the software without going through the boot-up (I went through Kies, but once the phone booted up, it disappeared from Kies and it told me the phone was disconnected).
Any step by step to either repair 2.3 or to install another droid system prior to the phone booting up? I'd appreciate the help.
Click to expand...
Click to collapse
You could grab Odin KK4 without bootloaders and flash it in download mode.
From there, use Odin 1.87 to flash Corn kernel if you wanna be rooted and have a custom recovery again.
Then it's your choice whether you wanna stay on 2.3 or look into 4.2 ROMs.
BWolf56 said:
You could grab Odin KK4 without bootloaders and flash it in download mode.
From there, use Odin 1.87 to flash Corn kernel if you wanna be rooted and have a custom recovery again.
Then it's your choice whether you wanna stay on 2.3 or look into 4.2 ROMs.
Click to expand...
Click to collapse
So, do you agree with me that it seems to be a software issue? Or is this something to try and see if all goes well with the new install? I have no problem if this is something to try since nothing else is working, but I am just curious if my diagnosis is correct.
Thanks for the quick respond.
KT
ktvanhorne said:
So, do you agree with me that it seems to be a software issue? Or is this something to try and see if all goes well with the new install? I have no problem if this is something to try since nothing else is working, but I am just curious if my diagnosis is correct.
Thanks for the quick respond.
KT
Click to expand...
Click to collapse
My guess is that something got corrupted, so yes, software issue. Find the required Odin and 2.3 kernel for the I9000 and flash them in download mode. It should run fine after that.
Got things resolved
Thanks for the help. I tried to follow your steps, but I could never get the phone connected to the PC. It would charge, but not connect to let Odin in. (It will connect to another PC without issues. I uninstalled and reinstalled the drivers, but no dice). However, in the process of putting the phone into download mode and rebooting it back somehow got me into the recovery screen. I did a factory reset through there and it worked.
Thanks for the help of all the contributers to the site.
K