• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Getting into Recovery

So Jedii, Frisco, et al are we able to definitively conclude that the lag fix prevents CWM from working properly?
 
saps said:
So Jedii, Frisco, et al are we able to definitively conclude that the lag fix prevents CWM from working properly?
Click to expand...

Well, i have tried it on 2 devices here and it has the error.

I will say that in the thread on XDA that all this is referring too, the OP highly recommends removing LagFix PRIOR to using clockwork.
 
Jedii said:
Well, i have tried it on 2 devices here and it has the error.

I will say that in the thread on XDA that all this is referring too, the OP highly recommends removing LagFix PRIOR to using clockwork.
Click to expand...
So we're leaning yes but not definitively
 
saps said:
So we're leaning yes but not definitively
Click to expand...

These things are too hard to pinpoint.

Because this all revolves around a rooted device, its hard to know if everything is in line.

But i will stand behind my statement. Yes, i believe these 2 are conflicting.

The real test will be if VooDoo conflicts.
 
I have the same issue as the OP, does the method in the XDA link wipe the memory? I don't wanna lose all my apps. Thanks!
 
dragonzsoul said:
I have the same issue as the OP, does the method in the XDA link wipe the memory? I don't wanna lose all my apps. Thanks!
Click to expand...

Nothing is wiped unless you choose that option in the recovery menu, and there is no reason to do that just to flash a battery zip.

If you ever flash a ROM, you'll likely need to perform the two wipe procedures offered there, maybe not, depending on what the ROM dev says.

Of course, prior to any flash we should always perform a nand backup.
 
Just to be clear, if you see:

--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

You are NOT in CWM and you haven't installed it fully/correctly.
 
oops.. i just read where if I needed to get into Clockwork recovery on a cold boot i would need to select "update.zip" after pressing both volume buttons along with the power.. if this is the case ( i wouldn't know as I have been using ROM manager) can someone upload a copy!? :D I was cleaning house on my SD card and saw this zip file and thought it was garbage... lol
 
So if you've had a Fascinate that has never had the Lag Fix installed, will you still have the same CW Recovery issues?

Brandon
 
Ok, so I went into ROM Manager, Flashed CWM Recovery, selected Galaxy Fascinate, then rebooted into stock recovery and tried to apply the update.zip posted over at XDA in the CWM thread. It still gives me the same error as the OP.

Any ideas?
 
Bearly said:
Ok, so I went into ROM Manager, Flashed CWM Recovery, selected Galaxy Fascinate, then rebooted into stock recovery and tried to apply the update.zip posted over at XDA in the CWM thread. It still gives me the same error as the OP.

Any ideas?
Click to expand...

The Odin method, as described here:

http://forum.xda-developers.com/showthread.php?t=788099

has yielded success for myself and other users posting in this thread about that issue.

Stock recovery cannot be updated with that zip, as it is intended for Clockworkmod Recovery when needed.
 
Yes precisely. Bearly, if you didnt flash the CWMrecovery.tar in Odin you're not quite there yet. Follow the instructions in the link by Frisco. The actual flash takes like 7 seconds once you DL the files
 
You must log in or register to reply here.
Back
Top Bottom