THIS THREAD IS NO LONGER RELEVANT AS IT IS FOR A DIFFERENT ISSUE FROM THE PAST... IT GOT BROUGHT BACK TO THE TOP. DONT CONFUSE THIS WITH THE 3E RECOVERY "ISSUE"
THE BELOW ISSUE HAS BEEN ADDRESSED BY KOUSH. YOU SHOULD BE ABLE TO FLASH CWR VIA ROM MANAGER LIKE NORMAL NOW. IF YOU STILL HAVE ISSUES, THERE IS A FIX POSTED BELOW, THANKS!
Update from koush:
@clockworkmod Hey all, flashing recoveries through ROM Manager is busted. We hit a bandwidth/CPU quota on Google App engine.
If you are trying to flash Clockwork Recovery for the first time, it appears that a lot of users are having issues over the past 24 hours.
Normally, you would:
download Rom Manager
Click Flash Clockwork Recovery
it will ask for root privelages
you would select the Vibrant as your phone
after it downloaded CWR you would get a successful pop-up....
you could then click on reboot into recovery (and since it was the first time you would go to the stock recovery, click reinstall packages, and THEN you would go to Clockwork Recovery)....
well.... people can't seem to get there now. I am NOT having issues as I already have CWR. However, if you are, please download this file on your phones browser (just so you dont have to mount your phone to your pc.... which you can do if you prefer)
FILE DOWNLOAD HERE: View attachment update.zip
Move this file to the root of your internal memory. If you have any other update.zip file you can just overwrite it, or delete it prior to moving this file over, your choice....
NOW, go back to your stock recovery and press reintall packages.... you should go to CWR, if not, press to reinstall again... still no luck? blasphemy.
With all of that said, I need someone to post that this successfully works (it should, and you really can't lose anything)
I am contacting koush for an explanation of what's wrong....
i will check this out
everytime i boot into recovery and press reinstall packages my just restarts phone and i can't get into clockwork.
You generally have to tell it to reinstall packages twice.
^ that has not been the case for me.. but try it twice if if doesn't work the first time!
Yeah, it may depend on the ROM being run or something, but I've noticed it quite a bit.
yeah, something happened when rom manager updated in the last day where flashing recovery isnt compatable with galaxy s devices anymore. drove me freakin crazy cuz i just dl'ed nero and went to install and couldnt.
thank you again. +10 internets to u.
I started having an issue after flashing eugenes super kernel. I did a.clean install of axura and problem went away.
Powered by Axura
^ the rom would have nothing to do with it.
Koush has fixed this, it was server related.
THE BELOW ISSUE HAS BEEN ADDRESSED BY KOUSH. YOU SHOULD BE ABLE TO FLASH CWR VIA ROM MANAGER LIKE NORMAL NOW (NORMAL STEPS STILL INCLUDED BELOW). I KNEW THIS WOULD BE A QUICK FIX FOR KOUSH!
As of 10mins ago i was having this problem.
But thanks to this post and installing the downloaded update I'm back up!
Rom manager gave me errors when flashing the clockwork recovery
so had to go to the update.zip and i'm now back!
Dont think rom manager in the market has been updated
[i was coming from a odin[ed] JFD stock.
hope this helps someone else!
Thanks... this works for me :\
I flashed to JL4 and had a freaking wifi boot loop and gotta go back to Eugene's does not brick ROM and found out can't install CWM via ROM manager
I don't know if its supposed to fix it, but even after flashing this Im still having issues with ROM manager. Get an error every time I try to update the recovery. Also, I can't remember the last time fix permissions actually worked (eclair maybe?).
Anyone else feel my pain?
This is a fix, and you trying to update the recovery is no different than those who have issues not even using my .zip....
I updated the op with a tweet from koush. He has a fix on his site too (might as well download it from here though?
I downloaded the new update, still can't get into clock work. When I hit reinstall packages it says ... E: error /cache/update.zip
(bad)
Installation aborted
Sent from my SGH-T959 using XDA App
^^^ I'm having the same problem as well right now.
reinstall off market and it works
I thought I was sunk until an hour of searching found this post. Thank you all so much!
I have after upgrade to K6 the error messeage:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
I've try the update.zip from the 1st post,
reinstalled via market
update und select the Vibrant modell
everytime the same...
the phone is rooted via SuperOneClickv1.5.5-ShortFuse
Any help ?
None of this works because none of it addresses the real problem ,3E signature. Way to much trouble to go thru.
^ This thread was created when the Clockwork servers were down... it has absolutely nothing to do with 3e recovery... as that didnt even exist when this thread was created... hopefully others are not confused now that it was brought back to the top.
I didn't update it yet, because the thread was dead.
And to be fair the OP did have this:
THE BELOW ISSUE HAS BEEN ADDRESSED BY KOUSH. YOU SHOULD BE ABLE TO FLASH CWR VIA ROM MANAGER LIKE NORMAL NOW. IF YOU STILL HAVE ISSUES, THERE IS A FIX POSTED BELOW, THANKS!
Click to expand...
Click to collapse
Related
Something went wrong during an ODIN revert to stock, and now when I plug in the phone to the computer or wall it shows the battery charge image for a few seconds, then it says the "Samsung Vibrant" splash and goes straight into recovery mode. I've tried holding down the volume keys, adb doesn't recognize the device. IDK wtf to do. Any help would be so appreciated I'll paypal the person a six pack that can help me fix this.
When it goes into recovery mode it says...
Movi_check Start...!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
Movi_check already executed!!...
Movi_checking done!..
E:Can't mount /dev/block/stl11
(invalid argument)
E:Can't mount /dev/block/stl11
(invalid argument)
did you try holding down volume up/down, and just plugging it into your computer?( so you can get into download mode)
So I just got off the phone with Tech Support, luckily I'm still under warranty and my recovery screen says "Android System Recovery" and not ClockworkMod Recovery. They went through the "Master Reset" and that didn't work, obviously, because I tried that. I also tried every other thread to get into download mode and Odin the original rom/kernel/recovery to no avail. They agreed to send me a new phone free of charge, added on the insurance and shipping is now free. Luckily my girlfriend didn't tell them what really went down haha. "Oh well he rooted his phone and then tried to un-root it and ended up turning it into a paper weight." So now I just sit and wait. Next time I'm not using any other outside write ups to try and reflash a recovery on the vibrant. After I get the OTA (if it ever comes) I'll root it again just to remove the bloatware like I did the first time. But with Clockwork you can't get the OTA, or so it said, so I'll just be patient and wait it out. To anyone else who is stuck in recovery and can't get it into download mode, or flashed the euro version, just call T-Mo tech support and say you downloaded an app and rebooted and voila stuck in recovery. On the downside, I have to wait 5-7 business days (not including weekends or holidays though) for my new one in the mail. So let this be a lesson learned to everyone, read read read and if all else fails, lie.
Its not as easy doing things on the Vibrant as it was with the good old Gangster 1 (G1).
Also, I only tried this because Rom Manager said I still had ClockworkMod Recovery instead of the stock recovery after I did the proper forum.xda-developers.com/showthread.php?t=734475, You don't need to flash the root update as the CSC, I guess there could be a non-root update.zip to use, but There was a guide I followed the first time that only used the PIT and PDA files, which put it back to stock but still had ClockworkMod Recovery on it. If it didn't, Rom Manager was lying to me.
red96turbols said:
So I just got off the phone with Tech Support, luckily I'm still under warranty and my recovery screen says "Android System Recovery" and not ClockworkMod Recovery. They went through the "Master Reset" and that didn't work, obviously, because I tried that. I also tried every other thread to get into download mode and Odin the original rom/kernel/recovery to no avail. They agreed to send me a new phone free of charge, added on the insurance and shipping is now free. Luckily my girlfriend didn't tell them what really went down haha. "Oh well he rooted his phone and then tried to un-root it and ended up turning it into a paper weight." So now I just sit and wait. Next time I'm not using any other outside write ups to try and reflash a recovery on the vibrant. After I get the OTA (if it ever comes) I'll root it again just to remove the bloatware like I did the first time. But with Clockwork you can't get the OTA, or so it said, so I'll just be patient and wait it out. To anyone else who is stuck in recovery and can't get it into download mode, or flashed the euro version, just call T-Mo tech support and say you downloaded an app and rebooted and voila stuck in recovery. On the downside, I have to wait 5-7 business days (not including weekends or holidays though) for my new one in the mail. So let this be a lesson learned to everyone, read read read and if all else fails, lie.
Its not as easy doing things on the Vibrant as it was with the good old Gangster 1 (G1).
Also, I only tried this because Rom Manager said I still had ClockworkMod Recovery instead of the stock recovery after I did the proper forum.xda-developers.com/showthread.php?t=734475, You don't need to flash the root update as the CSC, I guess there could be a non-root update.zip to use, but There was a guide I followed the first time that only used the PIT and PDA files, which put it back to stock but still had ClockworkMod Recovery on it. If it didn't, Rom Manager was lying to me.
Click to expand...
Click to collapse
Rom manager doesnt replace samsungs recovery. There is an update.zip that is placed in your root that allows you to get to clockwork recovery by simply reinstalling packages in samsung recovery. Clockwork recovery may still be flashed, but if you remove or replace that update.zip, the only way otherwise to get to it would be through rom manager. Which obviously isnt an option for you.
Sent from my SGH-T959 using XDA App
wildklymr said:
Rom manager doesnt replace samsungs recovery. There is an update.zip that is placed in your root that allows you to get to clockwork recovery by simply reinstalling packages in samsung recovery. Clockwork recovery may still be flashed, but if you remove or replace that update.zip, the only way otherwise to get to it would be through rom manager. Which obviously isnt an option for you.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Dang. Because when I opened CW it said "Current Recovery: ClockworkMod Recover 4.x.x.x, last version: ClockworkMod Recovery x.x.x." So I guess CW wasn't even on there, so I bricked it for no reason. If I just removed the update.zip it would have just been fine? Because it kept saying "You can't receive the OTA with your current ROM, please contact ROM author." Which is why I decided to reflash to stock un-rooted rom. I had also had a 6 pack and 2 jager bombs so hahaha fsck it. I'm getting a new one and will read when I'm un-ability impaired. Thanks for the note though.... but I also renamed the update.zip to 2.1rootupdate.zip, would that matter to CW or not? Because it kept saying no matter how I reflashed that CWR was still on there...
Did you try to flash 2.2 by any chance? Easy way to fox your problem is just adb reboot. It will boot up your phone past the recovery screen, and then you can use odin to get back to stock.
Sent from my Samsung Vibrant
red96turbols said:
Dang. Because when I opened CW it said "Current Recovery: ClockworkMod Recover 4.x.x.x, last version: ClockworkMod Recovery x.x.x." So I guess CW wasn't even on there, so I bricked it for no reason. If I just removed the update.zip it would have just been fine? Because it kept saying "You can't receive the OTA with your current ROM, please contact ROM author." Which is why I decided to reflash to stock un-rooted rom. I had also had a 6 pack and 2 jager bombs so hahaha fsck it. I'm getting a new one and will read when I'm un-ability impaired. Thanks for the note though.... but I also renamed the update.zip to 2.1rootupdate.zip, would that matter to CW or not? Because it kept saying no matter how I reflashed that CWR was still on there...
Click to expand...
Click to collapse
There is no updated rom available. That function of rom manager is currently unused by vibrant devs. It allows them to make updates to roms and streamline the process, but they simply move on to the next rom. Renaming the update.zip that is used to root to whatever it is is ok for cw recovery, but once you have clockwork recovery flashed since it doesnt replace samsung recovery. When something goes wrong you need its update.zip it puts in root to stay right where it is. By reinstalling packages in samsung recovery is the only way to get to clockwork recovery when you cant load up the phone. If that update.zip is gone or renamed, you're s.o.l.
Sent from my SGH-T959 using XDA App
So if I had kept that update.zip file that CW put on, chances are I could have fixed it? Since I clicked the "Repartition" check box on Odin, would it have even mattered? I used the 512.pit file and the Phone file from the "Unroot" thread by Koush I believe. That worked wonderful, and then I did it a second time and I think something went wrong.
I have a SF running on DI01. It is rooted using Z4. I installed Rom Manager and then flashed latest Clockwork Mod Recovery. When I reboot the phone into recovery, and then select update.zip to get into Clockwork, I am met with the following:
E: failed to verify whole-life signature
E: signature verification failed
Installation aborted
When I originally got this phone this worked fine. The issues started AFTER I did a factory reset. I did the factory reset because I was unsatisfied how the phoen operated after doing a recovery with Titanium Backup and wanted to start fresh again.
I made sure to delete all traces of every file and folder prior, I even used a brand new formatted SD card and I am still getting this problem. I have been through 2 factory resets trying to get the recovery to work.
Anyone with any ideas would be much appreciated. Thanks in advance!
--JD
jfigura said:
I have a SF running on DI01. It is rooted using Z4. I installed Rom Manager and then flashed latest Clockwork Mod Recovery. When I reboot the phone into recovery, and then select update.zip to get into Clockwork, I am met with the following:
E: failed to verify whole-life signature
E: signature verification failed
Installation aborted
When I originally got this phone this worked fine. The issues started AFTER I did a factory reset. I did the factory reset because I was unsatisfied how the phoen operated after doing a recovery with Titanium Backup and wanted to start fresh again.
I made sure to delete all traces of every file and folder prior, I even used a brand new formatted SD card and I am still getting this problem. I have been through 2 factory resets trying to get the recovery to work.
Anyone with any ideas would be much appreciated. Thanks in advance!
--JD
Click to expand...
Click to collapse
You cant flash clockwork recovery from the phone it has to be pushed in odin then you can flash it in rom manager
The thread is in the development section
Do a little searching around and you ll find all the info you need
Yet another reason not to use z4 root as you learn nothing about your phone
And really it aint hard to do things the" right" way
Actually it sounds like you did read.
My best guess is you went wrong when you installed the SD card and have the wrong update.zip on it, but it's just as likely you need to prime CWM again in odin. You'll be fine!
I do agree that the guides should give manual roots, not one clicks. The slow way is pretty quick:
http://forum.xda-developers.com/showthread.php?p=9443125
I don't think rooting was your issue in this case though. I think you may have missed how clockwork installs and works. It is persisting but not permanent.
In brief, you pave the way with the cwm odin flash, then use rom manager to place a current version of CWM recovery on your SD card in the form of update.zip, then 'install' that every time you need to run CWM.
Read post #179, then build a little shrine in the corner of your house for angel12:
http://forum.xda-developers.com/showthread.php?t=788099&page=18
Swyped from my i500.04 (bh &1129) using XDA App
Soba - Once I repushed from Odin it came back. Scratching my head a little but hey it's back. I used Z4 on this phone because I got caught by Verizon when I manually rooted the first model which went bellyup after having it for a week. I wanted to make sure I could quickly get rid of the root if I needed to go back into the store.
To the other responder, sorry for not being specifically "clear".
I've been tinkering with 6 different phones from this one to two Motos and 3 different HTC's. All the methods are beginning to run together sometimes.
I appreciate the assist and I thank you both.
soba49 said:
Actually it sounds like you did read.
My best guess is you went wrong when you installed the SD card and have the wrong update.zip on it, but it's just as likely you need to prime CWM again in odin. You'll be fine!
I do agree that the guides should give manual roots, not one clicks. The slow way is pretty quick:
http://forum.xda-developers.com/showthread.php?p=9443125
I don't think rooting was your issue in this case though. I think you may have missed how clockwork installs and works. It is persisting but not permanent.
In brief, you pave the way with the cwm odin flash, then use rom manager to place a current version of CWM recovery on your SD card in the form of update.zip, then 'install' that every time you need to run CWM.
Read post #179, then build a little shrine in the corner of your house for angel12:
http://forum.xda-developers.com/showthread.php?t=788099&page=18
Swyped from my i500.04 (bh &1129) using XDA App
Click to expand...
Click to collapse
So I'm getting stuck at the same place. I'm new, so could you explain how to pave the way with Odin? I think I understand the concept, but I'm looking for a detailed list of flashing things (such as the update.zip from cwm) in Odin to my phone.
Thank you for any input!
woodaresick said:
So I'm getting stuck at the same place. I'm new, so could you explain how to pave the way with Odin? I think I understand the concept, but I'm looking for a detailed list of flashing things (such as the update.zip from cwm) in Odin to my phone.
Thank you for any input!
Click to expand...
Click to collapse
Here's Update.Zip file for CWM
Direct Link, I uploaded it by myself, couldn't find decent one
http://www.4shared.com/file/ReRrCtwV/update.html
Make Sure to thank me if it works
If it doesn't let me know.
post no longer relevant
If you want to update this, My modified cwm thread has the RED clockwork odin package.
adrynalyne said:
If you want to update this, My modified cwm thread has the RED clockwork odin package.
Click to expand...
Click to collapse
i think omj is going to change his op on af...ill copy that over when he does
When I get in Odin and select CWMRecovery_DJ05_DL09.tar.md5, it fails.
I did not touch any settings in Odin, just clicked PDA and selected that file.
Edit: Redownloaded that file and got it to work. I am now having an issue when applying update.zip... it starts but then comes up with an exclamation point inside of a triangle and the little Android guy... phone reboots fine.
Did you get this solved? Check out the thread at AF I had the same problem
worked like a charm..thanks!
SoCalSpecialist said:
worked like a charm..thanks!
Click to expand...
Click to collapse
ok so i havent been able to find a full answer..but does this leave the device in DI01 or 05 or 09?
just by looking at the files it seems as if it goes from 05 to 09 but once in about phone>build number it reads : DI01
so im just looking for a little clarification here..just rooted my Facinate minutes ago so im still stuck in the whole mindset of the Incredible.
I tried this. Have EA28. Not sure how. Didn't install. Saw install screen on phone last night and hit cancel.
Anyway, Ran Odin, CWMRecovery_DJ05_DL09.tar.md5, reboot, blue text, apply sdcard:update.zip, switched to red text, install zip from sd card, choose zip from sd card, su-2.3.6.1+busybox1.19.zip, choose zip from sd card, DJ05_DL09_kernel.zip (plain kernel due to dl09), ran titanium backup, could not acquire root priv.
Startup screen has sound, but not animation anymore. Installed superuser and it shows titanium backup under "allow". When I run TB, I get the error screen and below in another small screen says, "Titanium Backup has been granted superuser permissions". But can't get anywhere to backup apps. Says Root Access: Failed.
ideas?
Another thing that confused me was the red cwm says voodoo lagfix recovery v2.5.1.x. I thought you weren't supposed to use any voodoo for DL30? Not that I've made it that far due to titanium backup issue, but....
Can anyone confirm whether or not this to sure does or doesn't work with ea28? My wife updated he phone and now she wants it rooted.
Edit this does work for EA28. Everything went smoothly. Thanks nitsuj.
Sent from my SCH-I500 using XDA App
mdisaac said:
When I get in Odin and select CWMRecovery_DJ05_DL09.tar.md5, it fails.
I did not touch any settings in Odin, just clicked PDA and selected that file.
Edit: Redownloaded that file and got it to work. I am now having an issue when applying update.zip... it starts but then comes up with an exclamation point inside of a triangle and the little Android guy... phone reboots fine.
Click to expand...
Click to collapse
I also got stuck at the same screen. what did you do to resolve it????
Here is the link to my guide for rooting with a MAC. I do not have a PC and used these steps to successfully root my phone. After completing last step in guide and getting blue cwm on your phone, DL new red cwm and install
http://forum.xda-developers.com/showthread.php?t=967641
Sent from my SCH-I500 using XDA Premium App
EA28 going to DL09?
Hello..
I am just getting around to rooting my fascinate now. I have EA28. From the instructions, it appears you are going back to DL09. Is that correct? What is the significance of that? Should I care?
Thanks in advance!
This thread is old and should be deprecated. The directions still work, but you need to use the Odin package of ClockworkMod in this thread (it's the very first item linked) instead of the md5 file (DL05_DJ09) above.
However, if you're going custom the thing you should *really* do is Odin in one of the full-Froyo packages. This will include both root and recovery.
s44 said:
This thread is old and should be deprecated. The directions still work, but you need to use the Odin package of ClockworkMod in this thread (it's the very first item linked) instead of the md5 file (DL05_DJ09) above.
However, if you're going custom the thing you should *really* do is Odin in one of the full-Froyo packages. This will include both root and recovery.
Click to expand...
Click to collapse
Thanks S44. My goal is to go froyo, but I need to be rooted first in order to do that.
I have been reading all the threads but many of them are very long. The DL30 thread is over 50 pages long.
So should I:
1) follow the instructions in this thread but use the new ClockworkMod then
2) update to froyo.
What is the most current thread for updating to froyo on the fascinate while after I am rooted?
Appreciate it.
TheTinRam said:
Thanks S44. My goal is to go froyo, but I need to be rooted first in order to do that.
Click to expand...
Click to collapse
Actually, no you don't. Download mode is magic. You *do* need to be rooted to back up apps with Titanium, if you want to do that. In that case, follow the directions above (with the new recovery). Then back up your user apps + app data.
Whether or not you do this, you should move to Froyo with a full-Odin package. Download the ROM you want (either Nameless, Super Clean, or whatever) in zip form to your SD card. Follow the directions here (under "Most Thorough Method of Fixing Every Problem You Might Have") using the first two files here and the recovery I mentioned in my previous post. Yes, this is sort of overkill, but better to avoid stuff like corrupted dbdata from the beginning and not have to fix it later.
You might want to wait a day or so because it looks like jt is finally fixing up Clockwork.
EDIT: I read almost all of the 52 pages of the DL30 thread to realize that DL30 is out of date . I guess Its going to be EB01 or Superclean. Do you know if Superclean has the audio out via USB working for the docks?
I have some questions in regards to picking ROMs:
I am a little confused in where to find the latest versions. For example in the "most thorough me..." thread, there is a link to super clean version form 3/30/2011 yet wiki has super clean from last year. Where can I look at all the ROMs and descriptions?
Which froyo ROM would you recommend? I love Google's stock froyo, but I also want to use the fascinate's USB audio out on the car and desktop dock. I also would like to wifi tether.
Thanks again!
This post had a link to download ODIN but it was removed. Could you please provide that link again. It also had a link to "Samsung Drivers", don't I need that too?
I am going to take a shot at following the ""Most Thorough Method..." steps tomorrow morning and install superclean on my Facinate. Quick Q: In step one, it simply says to ODIN EB01. I can just do this without being rooted?
Also, you said jt is fixing up clockwork. What do you mean by this, what exactly does not work?
I know these are noob questions, but I am just starting out with this.
Thanks
Driver links are here. Odin is here.
Yes, download mode lets you Odin in complete firmware packages without root.
Most people are using Super Clean, so that has the most support (and themes), but there are some odd issues floating around with it. My guess is that a lot of those issues have to do with not cleaning up in the super-thorough way I'm suggesting, and with the permissions bug after flashing a theme (below). There's also navendrob's EC10-based "Nameless" ROM, and ahmgsk's DL30-based "TrulyFascinating" ROM. Nameless is good but he's about to drop a version 4 with a lot of fixes, so you might wait a day or so for that. TrulyFascinating seemed to be pretty good (heavily stability-tested), but he hasn't updated it in a while (busy with more recent Epic leaks, I guess). You might try running it with one of the state-of-the-art EC10 Voodoo kernels.
There are a couple of Clockwork bugs, but the one causing the most current problems is that the old one couldn't fix permissions properly. This causes issues after making a change to the /system after the initial ROM flash, generally when you flash a theme on top of it. The new one I linked above *can* fix permissions, but still requires you to manually mount /dbdata beforehand (actually, go to the "mounts and storage" submenu and make sure /system /dbdata and /data are all mounted -- that is, the option referring to them says "unmount", which will happen when they're mounted -- before you go to the "advanced" submenu and run the fix permissions script). The new new one coming soon will just fix it without a problem, and do other stuff too.
Once again thanks. I have everything I need....or so I thought.
I restored my phone to factory, loaded the drivers, fired up ODIN and added the PDA and PIT. I hit start.... nothing happens. "All threads complete, succeed 0 / failed 0"
Looks like I am missing something. Do I need to somehow tell ODIN where the phone is? I don't see a way to do that.
PS in step 4 its states "ODIN the CWM Recovery package ROM from this post". Does CWM bin file go into PDA or phone in ODIN?
I one again apologize for my noobiness.
The Clockwork step comes after you do the full package and boot with that.
Make sure you have Odin open *before* you connect the phone in download mode.
Guys,
I have tried several roms and decided to odin back to 2.1, updated to 2.2 and just clean it up a bit and leave it as is for a while.
Everything went just fine, but yet again this damn clockwork recovery issue which I knew I would get but thought maybe it would be solved by now on rom managers side.
So, in rom manager, it shows that current recovery is 2.5.1.2 which matches the latest, however, when I reboot into recovery, I am still getting the standard 2.2 recovery console.
I tried searching but not sure what the issue is, of course I get the signature issue when I try to update package.
It's wierd that it's showing it's installed but it's not actually booting into the correct recovery console.
Thanks.
kero4 said:
Guys,
I have tried several roms and decided to odin back to 2.1, updated to 2.2 and just clean it up a bit and leave it as is for a while.
Everything went just fine, but yet again this damn clockwork recovery issue which I knew I would get but thought maybe it would be solved by now on rom managers side.
So, in rom manager, it shows that current recovery is 2.5.1.2 which matches the latest, however, when I reboot into recovery, I am still getting the standard 2.2 recovery console.
I tried searching but not sure what the issue is, of course I get the signature issue when I try to update package.
It's wierd that it's showing it's installed but it's not actually booting into the correct recovery console.
Thanks.
Click to expand...
Click to collapse
delete whatever update.zip you
http://forum.xda-developers.com/showthread.php?t=849028
get the 1 from there, reinstall packages twice and it should go to clockwork recovery
Okay, obviously option b would be better, however, will I have to reroot after if I use option B?
Nadda, same results, it's okay though, I'll live with it for now since I'll keep 2.2 with all the crud removed for now.
Please read that guide. You've missed some key points. I'd explain more, but I'm hanging with my kid.. Read the guide.
had the same problem i used this method and it worked for me
http://forum.xda-developers.com/showthread.php?t=833423&highlight=recovery
Here's the deal:
I rooted my phone a long time ago, and have been using CM since ICS. Mostly nightlies.
A few weeks ago I decided installing a Carbon nightly (4.3), and everything went smooth as usual.
Then new nightly came, so I decided flashing it. (Dirty flash, but it's that way from what I read in the Carbon thread)
The thing is, my phone boots up correctly, but I can't get into recovery mode. Whenever I try booting recovery mode, the logo appears, then the screen flashes gray. I have tried both the advanced reboot menu, the button combo, and ROM Man...jk
I think something might be wrong with the recovery included in the kernel. If that's the case, would it be OK to flash just a new kernel or do I have to reflash the whole thing?
I have already seen some guides on flashing kernels with mobile ODIN, but they're either ancient or for another model. Also, I don't know if that's the right thing to do under this situation.
I'd appreciate if someone pointed me in the right direction. I don't wanna frak up my phone.
You can install a kernel to see if that will solve the issue, but as far as I can see, the Carbon devs do not provide a stand alone kernel for their rom. You could use AJK or one of the other kernels though. Or you could just reinstall the rom to see if it would clear up the problem.
Or, you could extract the zImage from the full rom and use Mobile Odin.
I didnt want to create a new thread for this and get yelled at.. so I am asking the question here:
I had to do the ODIN method and returned my phone from ShoStock 3 to Stock Gingerbread, because for some reason my phone was getting stuck at the "samsung galaxy s2" boot screen.
So I am back on Stock Gingerbreak Rom and trying to install ClockWork Mod Recovery, so that I can restore the backup of ShoStock that I had created.
I am doing the Mobile Odin Lite method and I downloaded the i777 kernel. When I try to install it, I boot in the Android System Recovery (3e) and get the following errors:
Installing package...
Finding Package...
Verifying Update Package...
E: failed to verify whole-file signature
E: signature verification failed.
Before I get yelled at, I searched google and came up with the solution -- all of which say that the issue can be easily fixed by toggling the setting in ClockWork Mod Recovery Mode, but I have to install it first, and whenever I try to install it, I get the above error.
Can someone help please?
jjack0310 said:
I didnt want to create a new thread for this and get yelled at.. so I am asking the question here:
I had to do the ODIN method and returned my phone from ShoStock 3 to Stock Gingerbread, because for some reason my phone was getting stuck at the "samsung galaxy s2" boot screen.
So I am back on Stock Gingerbreak Rom and trying to install ClockWork Mod Recovery, so that I can restore the backup of ShoStock that I had created.
I am doing the Mobile Odin Lite method and I downloaded the i777 kernel. When I try to install it, I boot in the Android System Recovery (3e) and get the following errors:
Installing package...
Finding Package...
Verifying Update Package...
E: failed to verify whole-file signature
E: signature verification failed.
Before I get yelled at, I searched google and came up with the solution -- all of which say that the issue can be easily fixed by toggling the setting in ClockWork Mod Recovery Mode, but I have to install it first, and whenever I try to install it, I get the above error.
Can someone help please?
Click to expand...
Click to collapse
3e recovery is the stock recovery. It means you have not installed a custom kernel yet. Please look at the links in my signature and use the guide information there, which will help you understand what you need to do to install mobile odin lite and then install a custom kernel.
Also, remember that you will need to have the correct version of ClockworkMod Recovery to restore your backup. If the backup and the version of CWM recovery are not compatible, it will not restore.
If you have questions, ask them here, but be aware, I only come on line usually two or three times a day to check the forums.
creepyncrawly said:
3e recovery is the stock recovery. It means you have not installed a custom kernel yet. Please look at the links in my signature and use the guide information there, which will help you understand what you need to do to install mobile odin lite and then install a custom kernel.
Also, remember that you will need to have the correct version of ClockworkMod Recovery to restore your backup. If the backup and the version of CWM recovery are not compatible, it will not restore.
If you have questions, ask them here, but be aware, I only come on line usually two or three times a day to check the forums.
Click to expand...
Click to collapse
I followed Step 3a on this post: http://forum.xda-developers.com/showthread.php?p=18576627#post18576627
Unfortunately, for some reason, ODIN Lite was not recognizing DD_03042012.zip file. So I went with Siyah and downloaded the TAR file used ODIN to get the clockwork mod. It worked.
Now the problem is I cant restore my backup. I know the same backup has worked before, not it is giving me an error "Error while restoring /system". wth!
I dont remember what version of Clockwork Mod I had. I know it was an older version, becuase it didnt have touch.
How do I get a previous version of CWM?
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Actually,
Creepyncrawly, thanks for your help.
I downloaded ShoStock 3 and flashed it to get the previous version of CWM, and then was able to do a restore.
Sigh.. no harm done.
You can have your thread back... good luck!!
Mighty_Rearranger said:
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Click to expand...
Click to collapse
Yes, as stated by creepyncrawly, u can use mobile odin or regular odin to flash a kernel.
But i would suggest doing a MD5 check on the Rom u downloaded, because the Rom u flashed may be that of a corrupted download. If MD5 doesn't match then redownload, check MD5 and if good, reflash the Rom.
.....or maybe the nightly is messed up.
Sent from my SAMSUNG-SGH-I747 using xda premium
Mighty_Rearranger said:
Here's the deal:
I rooted my phone a long time ago, and have been using CM since ICS. Mostly nightlies.
A few weeks ago I decided installing a Carbon nightly (4.3), and everything went smooth as usual.
Then new nightly came, so I decided flashing it. (Dirty flash, but it's that way from what I read in the Carbon thread)
The thing is, my phone boots up correctly, but I can't get into recovery mode. Whenever I try booting recovery mode, the logo appears, then the screen flashes gray. I have tried both the advanced reboot menu, the button combo, and ROM Man...jk
I think something might be wrong with the recovery included in the kernel. If that's the case, would it be OK to flash just a new kernel or do I have to reflash the whole thing?
I have already seen some guides on flashing kernels with mobile ODIN, but they're either ancient or for another model. Also, I don't know if that's the right thing to do under this situation.
I'd appreciate if someone pointed me in the right direction. I don't wanna frak up my phone.
Click to expand...
Click to collapse
Mighty_Rearranger said:
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Click to expand...
Click to collapse
I can see why you could be upset that someone hijacked your thread.
I only see one question in your original post, which I believe I answered. You also requested assistance which I thought I provided.
Let me be a little more specific for you. Yes, you can flash just a kernel without re-flashing the system. However, you will need either an Odin flashable tar of the kernel, or you will need to install Mobile Odin and then you can flash a kernel directly from a zImage file.
However, I think 4-2ndtwin has the right of it. It was probably a bad flash, even though the phone booted normally. You should consider re-flashing the entire rom.
If you are not clear about anything, please ask questions.
Never mind.
I concluded it wasn't worth it just because I was lazy backing up stuff.
I used this: http://forum.xda-developers.com/showthread.php?t=1525821, then flashed a clean ROM.
Thanks for the help, you guys are awesome.