Database Users

[Q] Flash any ROM = "android.process.acore has stopped" missing recovery/update.zip?

[Q] Flash any ROM = "android.process.acore has stopped" missing recovery/update.zip?
Former evo (power) user, running (almost) all the nightlies and then RC of CM6. (usb power port broke. Chose Epic rather than waiting a month for the (out of stock) evo. So far, I like the hardware much better on Epic).
I Rooted/Clockworked via the linux thread in the forums. (http://forum.xda-developers.com/showthread.php?t=792058)
SuperUser info: Superuser v2.3.6.1 - Added clear log to menu in log
Database version 5
Su binary v original (sometimes shows Su binary v%s)
ROM manager info:
Current Recovery: CWM 2.5.1.0
No Alternate Recovery available
Reboot into Recovery takes me to (blue) Samsung recovery page (exclamation point in triangle)
E:Failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
(click home button -- reboots phone).
Using QuickBoot, Recovery sends me to the Samsung blue screen (not clockwork) and BootLoader just reboots back to phone).
However, Power off. Camera + Vol Down + Power takes me to clockwork.
Successfully made (and restored) backup.
Yesterday I flashed Tha Boss. About a minute in, I get the following error: "android.process.acore has stopped unexpectedly. Please try again. - Force close".
Successfully restored to my backup (of stock)
This morning I flashed Bubby's Magic AOSP. Same deal. About a minute in, I get the following error: "android.process.acore has stopped unexpectedly. Please try again. - Force close".
Again, successfully restored to my backup (of stock).
I've "replaced" blur on my stock with widget locker, ADW and beautiful widgets, but am having terrible battery issues. I do not care for any of the samsung/sprint stuff.
Obviously I am missing something here. Am I missing some recovery file? update.zip?
Thanks for any help/suggestions.
Drew

I was encountering issues like this as well. I went back to the start and did it all from scratch.
Used odin to get back to stock no root no custom recovery.
Once stock I let the phone prompt me for the di07 update ( probably not necessary as there is now a .tar with the di07 update so u can use that in odin)
I installed root using the one click busybox 2.2.4
Then I used the clockworkmod 2.5.1.0 flasher in the Permanent Method! Thread
I then installed the premium rom manager and when I did a backup from it I noticed something different ... it went through some stuff that said "replacing stock recovery with custom" or something to that extent. In the past doing that from rom manager would just take me to the stock rec. Now I can even boot into custom rec from rom manager and since then I've had no fcs of that sort when installing backups or new roms.
Sent from my SPH-D700 using XDA App

From my understanding of this error, so far at least, it has something to do with contact sync. I'm working on developing a ROM right now and I'm experiencing the same issue.
If anyone has any insight into this "acore" error message, I'd like to know what I might be able to do to fix this for myself as well.

rmartinez2 said:
I was encountering issues like this as well. I went back to the start and did it all from scratch.
Used odin to get back to stock no root no custom recovery.
Once stock I let the phone prompt me for the di07 update ( probably not necessary as there is now a .tar with the di07 update so u can use that in odin)
I installed root using the one click busybox 2.2.4
Then I used the clockworkmod 2.5.1.0 flasher in the Permanent Method! Thread
I then installed the premium rom manager and when I did a backup from it I noticed something different ... it went through some stuff that said "replacing stock recovery with custom" or something to that extent. In the past doing that from rom manager would just take me to the stock rec. Now I can even boot into custom rec from rom manager and since then I've had no fcs of that sort when installing backups or new roms.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
So, should I use Whosdaman's DIO7 tar (http://forum.xda-developers.com/showthread.php?t=794138) instead of the DG27?
Also, does that pit file (Aridon's 'How to return to stock' (http://forum.xda-developers.com/showthread.php?t=773032) work with DIO7?
Thanks for this info, btw

I need that DIO7 file but Megaupload isn't working, would one of you be nice enough to upload it to Mediafire for me?

if your running adw launcher, go into adwsettings > system preferences and make sure that you have wallpaper hack unchecked, this was causing the acore force close issue on my phone
for your clockwork issue, make sure your running a kernel that supports it and also after flashing clockwork recovery (the final version) an update.zip file should have gotten installed on your sd card, dont remove it has it is needed.
the only way to reboot into clockwork recovery is to do it through rom manager, every other way will send you back to the stock recovery.
hope that helps

aim1126 said:
if your running adw launcher, go into adwsettings > system preferences and make sure that you have wallpaper hack unchecked, this was causing the acore force close issue on my phone
for your clockwork issue, make sure your running a kernel that supports it and also after flashing clockwork recovery (the final version) an update.zip file should have gotten installed on your sd card, dont remove it has it is needed.
the only way to reboot into clockwork recovery is to do it through rom manager, every other way will send you back to the stock recovery.
hope that helps
Click to expand...
Click to collapse
Odin'd back to stock. Rerooted using 1-click. Rom Manager (paid version) still takes me to that blue samsung.
Don't seem to have update.zip from root, tho i *do* have root.
Still getting the
E:Failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
message, including the update.zip file not found...
****Goes away for 30 mins****
Ok. I re-re-odined. Then tried noobini's permanent method (http://forum.xda-developers.com/showthread.php?t=782300)
Try-first would not run. Try-last did not give me su permissions.
What am I missing here?
Maybe I should just re-root the 1-click? If I do, where can I pick up the update.zip and flash it manually?
Thanks,
Drew

SwimDrewid said:
Odin'd back to stock. Rerooted using 1-click. Rom Manager (paid version) still takes me to that blue samsung.
Don't seem to have update.zip from root, tho i *do* have root.
Still getting the
E:Failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
message, including the update.zip file not found...
****Goes away for 30 mins****
Ok. I re-re-odined. Then tried noobini's permanent method (http://forum.xda-developers.com/showthread.php?t=782300)
Try-first would not run. Try-last did not give me su permissions.
What am I missing here?
Maybe I should just re-root the 1-click? If I do, where can I pick up the update.zip and flash it manually?
Thanks,
Drew
Click to expand...
Click to collapse
Ran the Noobini permanent method over the linux 1-click -- still unsure what I'm missing in way of CWM.
No update.zip on sd card (not in any's the one-click zips i've seen either.
Still can't get to recovery via Rom Manager -- only via Vol Down + Camera + Power,
So, to reiterate, I'm rooted, ROM Manager shows 2.5.0.2, but Flash Alternate Recovery is unavailable.
Back Up Current Rom takes me to the blue samsung recovery (not cwm recovery) with following messages/errors:
--Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Hit the home screen to fastboot back to phone.
Power off
Vol Down + Camera + Power,
make a back up that way
So. Anybody want to lend me their update.zip??
Thx,
Drew.

Looks like I *do* have update.zip on sd card. I copied to my desktop and was able to extract it (meaning the compression didnt get corrupted).
It has all the nandroid files in /sbin.
Just thought of something. This is the same sd card i had in the evo -- has a bunch'a stuff on it (including old cwm backups)
Maybe tomorrow I'll (backup then) format card, odin, reroot?

Have you tried wiping cache and data on each ROM Install? Sometimes crap is left over and you end up with old application data/caches that interfere with the way they interact. Backup what you need, then wipe data/cache. Then install Zip from sdcard, after it finishes, wipe data/cache once more and reboot into Android.
Hope this fixes your issues.

schizopunk said:
I need that DIO7 file but Megaupload isn't working, would one of you be nice enough to upload it to Mediafire for me?
Click to expand...
Click to collapse
It's been uploaded 2 other mirrors now. Check the thread again.
http://forum.xda-developers.com/showthread.php?t=794138

Yeah. Always. Didn't have the clockwork kernel. Do now and everything is clockworked willy.
Thanks to all you xda people!
Sent from my (rooted) SPH-D700 using XDA App

Just an fyi on this acore issue. I was having the same problem after flashing tha boss. went back to andromeda and same thing. Aosp and same thing. Flashed the Andromeda kernel and the problem was solved. During it all clockwork was still working so I'm thinking that aim1126 was right earlier when he said that the kernel must support clockwork.

I sell and activate these phones and i had the acore force close on freshly activated epic the other day

One thing I found is that if you remove the TouchWiz launcher from any ROM then you will get this.

schizopunk said:
One thing I found is that if you remove the TouchWiz launcher from any ROM then you will get this.
Click to expand...
Click to collapse
I just installed LauncherPro on Apophis, removed the TouchWiz launcher and deleted it's folder in /data/data/. It's only been about a minute, but I haven't seen any errors yet. Is there any specific way to trigger it?

schizopunk said:
One thing I found is that if you remove the TouchWiz launcher from any ROM then you will get this.
Click to expand...
Click to collapse
Same thing happened to me every time I deleted TW but then I didn't delete its folder from /data/data so I don't know?
Sent from my SPH-D700 using XDA App

illogic6 said:
I just installed LauncherPro on Apophis, removed the TouchWiz launcher and deleted it's folder in /data/data/. It's only been about a minute, but I haven't seen any errors yet. Is there any specific way to trigger it?
Click to expand...
Click to collapse
Try syncing your contacts with TouchWiz's facebook feature... it most likely won't sync.

smoothone said:
Same thing happened to me every time I deleted TW but then I didn't delete its folder from /data/data so I don't know?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I just delete that folder because I'm OCD about unneeded files.
Here's how I setup my phone.
1) Odin to DI18
2) Flash clockwork recovery with this method: http://forum.xda-developers.com/showthread.php?t=782300 (Don't worry about rooting. This runs an exploit that gives you temp root and flashes clockwork.)
3) Power off, reboot into clockwork recovery
4) Wipe data
5) Flash ROM (Try my ROM if all else fails. I haven't seen one acore force close.)
6) Flash kernel if needed
That method SHOULD eliminate any possible variation between installs. I'm running the most recent version of Apophis, Phoenix kernel, no TouchWiz, still no errors. If you follow this method and get acore force closes, I will be baffled.

schizopunk said:
Try syncing your contacts with TouchWiz's facebook feature... it most likely won't sync.
Click to expand...
Click to collapse
Ah, that might be it. I don't use facebook.
EDIT: I just created a dummy account, opened the contacts app and signed in. It synced without force close. Might be due to a lack of friends. Any other ideas?

[Q] How to Fix my Droid? Compilation of errors

So I have a compilation of three issues that I've found on the forums but after two days, of researching and troubleshooting, no luck so hoping someone out there has had a chance to fix this and can share their knowledge.
Here's what I've done so far:
Ran Super One Click to root and worked
Flashed bootloader 30.04
Booted to "critical error 1337 510b"
RSD flashed to VRZ_MB810_2.3.32_1FF_01.sbf (Happy_Holidays_From_TBH.zip) using RSD Lite 4.8
RSD flashed to SHADO_X6_2.3.34_SYSTEM-ONLY.sbf (SHADO_X6_2.3.34_SYSTEM-ONLY.zip)
Lost root so tried Super One Click - wouldn't work
Installed Koush Bootstrap recovery
Installed and successfully rooted with z4root
Tried installing to C_01.43.01P.zip from Peter Alfonso and fails with error in list below
So here are the three errors I'm getting now and haven't been able to find a fix to any of them. I'm thinking it's possible permission issues on my device. I ran the Fix Permissions options from ROM Manager but it didn't help.
When I reboot into recovery mode, get error: "e: can't open /cache/recovery/command"
When try to install baseband update and says"Writing RDL/BP image... E:Error in /sdcard/update.zip (Status 0) Installation Aborted"
Tried flashing a few other SBF's and about 10 seconds into each, DX shows error "critical error 1337 510b" and flash never moves ahead
Here are some of the items I've tried and none of them have helped:
Rename to update.zip
Install using built in recovery
Installed ROM Manager
Installed ClockWork
Battery pull
Wipe cache (several times)
Install package with DroidExplorer
This list could go on and on an on - I've been working on this for two days
EDIT: Realized I hadn't upgraded the kernel from TBH so I just installed it and it worked properly, but still doesn't fix above issue when trying to update my baseband.
The good news is that I took a backup using ClockWork and I've restored it a half dozen times over past few days (so that I could actually leave the house and use my phone) so my phone is working, I just can't do any more flashing
Any suggestions? Thanks in advance!
EDIT: Been a few days and no replies. Very uncommon for this forum. Did I post in the wrong area? or not follow forum rules? Or I'm just an idiot? I've tried formatting all partitions (except for sdcard) and get "Error formatting boot partition". All other partitions format correctly but still can't install the latest baseband. The only thing that still works is flashing sbf of VRZ_MB810_2.3.32_1FF_01.sbf and SHADO_X6_2.3.34_SYSTEM-ONLY.sbf to get back to stock and restore my latest backup. Please help, I would really like to get the latest baseband installed.

I've been told that C_01.43.01P is only for original Droid, not the X - which is why it wouldn't work.

Go to the Droid X Android Development subforum and look at my thread for the update zip. Its a zip you download and flash through clockwork to upgrade and /or fix issues with the latest OTA. That should fix you right.

Failed to verify whole-file signiture

Hi all, I screwed up running an update to my ROM, recovered through Odin (again ha), flashed back to stock, rooted successfully, and installed Clockwork, but whenever I try flashing my ROM through ROM Manager, the phone reboots right, then gives me the "E: failed to verify whole-file signiture E: Signiture verification failed"
I just want to get back on BlackHole :\ I searched around but either people figured it out and didnt explain, or the problems variables were too far apart from mine. I have tried removing and reinstalling clockwork, and I have tried redoing the entire process to the same result.
Any insight?
I want to add that I'm not flashing Clockwork through Odin, because the files aren't available on the forum anymore. Is this the error?

You need to flash the cwrecovery.tar file, which enables you to flash zips signed with test keys. Look in the thread about flashing clockwork on win/*nix.
Sent from my SCH-I500 using XDA App

You're doing it right, just missing one step. Installing clockwork mod through rom manager only downloads the update.zip file for it to your sdcard, you have to flash the cwm compatible stock recovery through odin. the file can be found here:
www.androiddoes.net/sonofskywalker3/CWMrecovery.tar

sonofskywalker3 said:
You're doing it right, just missing one step. Installing clockwork mod through rom manager only downloads the update.zip file for it to your sdcard, you have to flash the cwm compatible stock recovery through odin. the file can be found here:
www.androiddoes.net/sonofskywalker3/CWMrecovery.tar
Click to expand...
Click to collapse
Excellent, I figured as much but since I couldn't find it anywhere I assumed it had been changed.
BEAUTIFUL. Thank you. Looking forward to running your 3.0. I was on 1.4 or something.

CWM not working

I have been having issues with CWM on my Fascinate for about 2 weeks now. Whenever I try to flash anything via CWM I get this message:
Samsung Recovery Utils
- for BML -
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
The "reboot system now" is highlighted and I cannot do anything to select apply update.zip
On the bottom part of the screen it says:
Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Now I have flashed back to D101 and did the ota update to DL09, and flashed the CWM via odin posted on a thread from the android central forum, it is basically a version of CWM for DL05 and DL09. (can't post outside links so I havent posted enough in this forum).
I have tried to apply the update.zip but whenever I do that, after about 25% of the way through it goes back to the error.
I have completely run out of ideas and the people at the android central forums have as well. I have tried everything that I can think of but obviously I am not doing something right.
Can anyone give me some suggestions as to what I can do to try to resolve this issue? Or if there is a way to flash a rom and kernel without CWM. I really do not want to be stuck with stock Fascinate so anything would be appreciated.
Thank you

You have to go into CWM immediately after flashing in Odin, before booting up, and flash a new kernel. DL09 breaks CWM on the stock kernel
Sent from my SCH-I500 using XDA App

I had that same issue until a user on another forum informed me that right after flashing cwm, replace battery and go immediately into recovery mode, do not let the phone boot normally.
Now I am able to add kernels and roms to my hearts content.

I'm in a similar situation except my error comes while trying to back up my ROM.
I did root via pushing rage.bin via ADB
Then I used ODIN to put CWMrecovery.tar on the phone.
Flashed CWM via ROM Manager.
At this point I did a full backup with TiBu and did a ROM Backup via ROM Manager.
After that I froze bloatware, 'upgraded' to the Sywpe Beta and De-binged.
At about this point I realized that I had lost Haptic so I flashed the DL09 stock Kernel and that problem was solved. I thought I was good to go until I tried to do another backup via ROM Manager.
When I ran the backup I got the same error as the OP. I ended up in 2e recovery. Since I'm new to this I just chose reboot phone. I did some searching last night but all the posts I found dealt with people flashing custom ROMs and I was getting tired I called it a night with the plans to do more searching today but then I came across this post.
I reviewed my notes and saw the other thread about CWM Recover mode and I checked and I can't reboot into CWM Recovery (via ROM Man) either. I end up in Android (2e) recovery.
I saw the post above me and I need to search on these instructions so I understand this step better.
"I had that same issue until a user on another forum informed me that right after flashing cwm, replace battery and go immediately into recovery mode, do not let the phone boot normally."
I don't seem to be able to boot (up and down key = Power buttong) into any recovery.
It seems like I need to repush CWM via Odin and then reflash via Rom Man but I'm leaving for a trip tomorrow so I'll wait for some input before trying anything since the phone is functionally working.
I'm new to rooting phones so some help with this error would be appreciated.

ezas said:
I'm in a similar situation except my error comes while trying to back up my ROM.
My phone is updated OTA DL09. Then rooted via ADB. I installed ROM Manager and flashed CWM. Since then I've done the usual root stuff. I noticed that haptic was not working and I fixed that by flashing a stock DL09 kernel. I have not flashed a custom ROM.
After de binging yesterday I went todo a back up via ROM Manager and got the same error as the OP. I ended up in 2e recovery. I didn't want to really screw up my phone guessing so I just chose reboot phone.
I was going to do more searching tonight but came across this post first.
I have done two successful back ups via ROM Manager, so after reading this post I assume it's flashing the kernel that got me to this error.
I'm new to rooting phones so some help with this error would be appreciated.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I don't use custom roms on my phone but from what I'm gathering on this...
You will need to put it back to DL09 stock...
Flash CWM via Odin..
http://forum.androidcentral.com/ver...s-hacks/54659-how-rooting-your-fascinate.html
Post 4 here will tell you how to do it.
After flashing CWM you will need to put your phone into recovery right away instead of letting the normal rom load. You will then flash over another kernel using CWM and that is it.
List of kernels can be found here:
http://www.samsungfascinateforum.com/custom-roms/list-of-custom-dj05-kernels-for-verizon-fascinate/
I have never put a new kernel or rom on my phone but from what i've read this is the jist of it.

You shouldn't have to flash back to stock...
1. Download all necessary files and place on root of your SD card (nonstock kernel, update.zip)
Edit: also add in the superuser and busybox zips, and flash those after kernel (step 5) and this will give you root back if you lost it updating
2. Flash modified CWM .tar with Odin
3. Replace battery and boot directly into recovery by holding both volume buttons down while powering on
4. Once in recovery, apply update.zip to get into CWM
5. Flash new kernel
6. Reboot, enjoy

Kevin and Rob
I followed the instructions to the letter over at AndroidCentral (including flashing busybox_su) and I'm back up and running with Haptic feedback and I'm watching a ROM backup via ROM Manager as I type this. I have not done a lot of testing yet but everything seems to be working fine.
Thanks for all the help.

Kevin Gossett said:
You have to go into CWM immediately after flashing in Odin, before booting up, and flash a new kernel. DL09 breaks CWM on the stock kernel
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Just did that and after I select Install zip from SD car, the screen goes black. When I press the home button it goes back to the green list but when I select anything from there, the screen goes black again.
I have tried flashing back to stock, updating to DL09 and flashing cwm again, but same issue.

OK I am getting really tired of dealing with this. Nothing I try works. I am just going to give up on the idea of installing roms and kernels on my fascinate. I have no idea what the problem is and nobody knows either.
Thanks for all those that helped.

When in CWM the home button turns the screen off. Use the back button or power button to select

Kevin Gossett said:
When in CWM the home button turns the screen off. Use the back button or power button to select
Click to expand...
Click to collapse
Shh, I had no idea about that. I assumed since in order to get to cement recovery you had to press home key that that is what you use while in recovery. Everything works now, thank you.

ok, I'm ready to sell this damn Fascinate on Craigslist for a peanut butter sandwich. I'm miffed with getting CWM working. I have pushed the updated version onto the phone via ODIN, immediately booted into recovery (got the red recovery), and it won't mount my SD card. I had a similar problem in green recovery - it could see my SD card, but wouldn't show me all the files - including the download folder. So I couldn't flash anything. I've tried this 100 different ways. There's nothing wrong with the SD card. It reads fine in the phone, files working other than CWM. Please help. I'm stuck on stock. Have mercy.

gadgetmom88 said:
ok, I'm ready to sell this damn Fascinate on Craigslist for a peanut butter sandwich. I'm miffed with getting CWM working. I have pushed the updated version onto the phone via ODIN, immediately booted into recovery (got the red recovery), and it won't mount my SD card. I had a similar problem in green recovery - it could see my SD card, but wouldn't show me all the files - including the download folder. So I couldn't flash anything. I've tried this 100 different ways. There's nothing wrong with the SD card. It reads fine in the phone, files working other than CWM. Please help. I'm stuck on stock. Have mercy.
Click to expand...
Click to collapse
Download updated CWM at this post: http://forum.xda-developers.com/showthread.php?t=942021
Fixed my CWM problems.

That is the file I used. Relief
Tried both through Odin and loading onto phone. No dice.

That is the file I used. Relief
Tried both through Odin and loading onto phone. No dice.

the home key always turns the screen off, u have to hit search button to turn on and go back

OK, just to make sure I'm not crazy, I tried again. First I downloaded the SuperClean 2.2 update to my SD card. I re-downloaded the updated update.zip file and put it at the root of my SD card. I flashed DL09.tar.md5 via Odin to get back to stock. That completed with no problem. I flashed the EB01 radio, no problem. Flashed the updated CWM. Immediately booted into recovery (red). Attempted to Apply update.zip. Errored out. Attempted to apply update from SD card. Here's the error I'm getting:
-- Install from SDcard...
Finding update package...
E:Can't mount/dev/block/mmcblk1p1 (or dev/block/mmcblk0)
(Invalid Argument)
E: Can't mount SDCard:Update.zip
Installation aborted

gadgetmom88 said:
OK, just to make sure I'm not crazy, I tried again. First I downloaded the SuperClean 2.2 update to my SD card. I re-downloaded the updated update.zip file and put it at the root of my SD card. I flashed DL09.tar.md5 via Odin to get back to stock. That completed with no problem. I flashed the EB01 radio, no problem. Flashed the updated CWM. Immediately booted into recovery (red). Attempted to Apply update.zip. Errored out. Attempted to apply update from SD card. Here's the error I'm getting:
-- Install from SDcard...
Finding update package...
E:Can't mount/dev/block/mmcblk1p1 (or dev/block/mmcblk0)
(Invalid Argument)
E: Can't mount SDCard:Update.zip
Installation aborted
Click to expand...
Click to collapse
I think I see what your issue is. The red CWM that you loaded via ODIN installs onto the phone itself. You no longer need an update.zip file containing CWM on your sdcard. As long as you have successfully booted into red CWM, your next step is to do a full wipe, and then choose the "install zip from sdcard" option. You should then be able browse your sdcard and select the zip file containing the rom.
DO NOT rename the zip file containing the rom to update.zip and then select the "apply update.zip" option, as that will definitely not work. That option expects to find the CWM recovery app in the update.zip file, and errors out if it's anything else.
Posted from my EB01 SuperClean Fascinate with Voodoo

Oh, and make sure you have the most recent new CWM file from jt1134. The post from him that had the first fixed CWM I think may have required an update.zip file, but the current, updated files in it do not. If you're not sure, download the latest one from that post for Odin, and flash it from Odin again. You will them no longer need update.zip for sure.
Posted from my EB01 SuperClean Fascinate with Voodoo

Roblovesbox said:
I don't use custom roms on my phone but from what I'm gathering on this...
You will need to put it back to DL09 stock...
Flash CWM via Odin..
http://forum.androidcentral.com/ver...s-hacks/54659-how-rooting-your-fascinate.html
Post 4 here will tell you how to do it.
After flashing CWM you will need to put your phone into recovery right away instead of letting the normal rom load. You will then flash over another kernel using CWM and that is it.
List of kernels can be found here:
http://www.samsungfascinateforum.com/custom-roms/list-of-custom-dj05-kernels-for-verizon-fascinate/
I have never put a new kernel or rom on my phone but from what i've read this is the jist of it.
Click to expand...
Click to collapse
Awesome, thanks for the links.

Getting ClockWorkMod to work

Hi Folks,
I'm trying to get clockwork installed on a rooted stock firmware vibrant for a friend. Using ROM manager i've tried to install CWM and it says it is successful, however after trying to reboot into recovery and choosing re-install packages I get these errors:
E:Failed to verify Whole File Signature
E:signature verification failed
Installtion aborted
I tried flashing Vibrant (MTD) Clockwork Recover 3.x from ROM manager but it does the same thing.
Also tried the AIO tool from the sticky in the dev section and it doesn't work either. I chose the custom ROM but it doesn't push it to the phone or reboot it into recovery. (The install drivers option gave me a windows unhandled exception error)
I downloaded Heimdall but am not sure how it's used, can it flash any ROM or only specially formatted ones?
I've been searching these forums for a few days now and finding so much new and old processes to do things and I'm not very familiar with Samsung phones so any help is appreciated. Thank-you.

Re-Root it
Re-root the phone using One-click, when Baywolfs fails, one click always does it because it push's it through using ADB
CWM wont work unless the phone is proper ROOTED, youll know when its done right, cause youll see the super=user App after your done
Link: http://forum.xda-developers.com/showthread.php?t=739300
After that, un-install Rom manager, then re-install it, then while your connected to WIFI or provider, make sure you flash CWM recovery,
Re- download the ROM again, but dont open it!!
Then when you are ready to flash that ROM as a zipped file, DO NOT open it [ meaning UNZIP] or you'll continue to get the signature error.
Then either flash using reboot into recovery or install using CWM option of sd card install, either or works!! .

Are you having trouble getting past the stock 3e recovery? I've been trying to get past it for a few days but have been poking around learning the in/outs of this. I have not yet gotten Rom Manager to properly flash CWM Recovery... the stock 3e is stubborn. Once CWM recovery is done, your options open up for backups, restores and installing some custom roms.
I don't know what the solution is but I'm still looking around.
Hope this was on track...

Its stuborn in the sense its picky about free space. You'll need to free up some room in order to use CWM. Reference this thread for guidance -
http://forum.xda-developers.com/showthread.php?t=925400