I installed 2.2 ota from verizion then I rooted
Root works
I then installed clockwork from the market and tried to install by flashing from the app.
After I reboot the phone it goes in to the default recovery app and says invalid signature.
How can I get clockwork recovery install with the 2.2 rooted ota update.
Right after you install cwm you have to boot into recovery right after and flash a non stock kernal or cwm wont stick.
Sent from my SCH-I500 using XDA Premium App
i havent done it personallly after an ota update( i hate vzw) but usually u have to install it through odin.. check noob thread in general
I did reboot in to recovery and thats when it tried to do an install and then told me it had and invalid signature.
Awesome development. Next time, post your question in Q&A.
To fix the problem, you need to flash CWM in Odin. "Flashing" it via ROM Manger only provides the update.zip on the SD Card. You need to flash a custom recovery kernel, as well as a modified regular kernel to be able to use CWM.
What kernel should I flash
I had similar trouble on 2 of our 3 phones. I had to Odin the file several times in a row before it stuck so I could boot into it and select my zip. It was like it wouldn't recognize it if you only did it once. I was probably doing something wrong, but lets just hope the end justifies the means.
Now have 3 phones running the Community Rom and we are hoping our batteries last more then a couple hours. They are certainly faster, my sons was almost unusable and my wife couldn't delete pictures after the OTA.
I still and at a loss for what kernel to flash Im fine with the stock rom. I eventually want to go to CyanogenMod when it it stable for the fascinate.
This might help.
http://forum.xda-developers.com/showthread.php?t=1053567
Try the OTB kernel
You can find it under the fascinate development forum. It's currently one of the first posts.
Sent from my SCH-I500 using XDA App
How do I flash that kernel to my phone?
Related
Im sorry if this has been covered, ive spent the last 2 days reading the Vibrant bible thread and also over on Cyanogen site and Android spin and im really frustrated with how often my device soft bricks.
i have 5 roms on my internal SD card and Rom manager running. i was able to use the option to install form SD card no problem for 4 roms and the 5th one was one called Hybrid R4 and when it rebooted into the clockwork recovery and performed the format and update then it rebooted into the Vibrant logo for 5 min. i removed the battery and rebooted so many times and same thing.
this is the 3rd time this has happened and its so annoying even more so because i know i have a good ROM on the internal SD card i can load up again but i cant get to it because i cant get into clockwork because i keep getting the stock samsung recovery screen with limited options resulting in having to use ODIN to flash the stock firmware and start over.
when i had my Mytouch i had a permanent recovery flashed to the device so i neve rhad to do this. are the Vibrants not able to have a alternate recovery console flashed to it?
which rom are you flashing over? It sounds like you are going from a 2.2 froyo rom. Hybrid R4 is from the time before the Devs started including Kernels with their roms. If you want to flash a 2.1 rom thats doesn't include the kernel over a 2.2 rom you need to flash a 2.1 kernel first. Search the bible for kingklicks kernel or Justanothercrowds kernels. Good luck.
Edit: also when you flash clockworkmod recovery in rom manager, it places a special update.zip in your root directory. leave it there. when you soft brick all you need to do in the samsung stock recovery is reinstall packages (sometimes needs to be done twice) and it will load clockworkmod recovery.
and they can have clockwork permanently flashed but it sometimes causes other problems. Eugene373 has a few kernels for 2.2 that have it permanently flashed, but it caused me issues when trying to flash another rom over it where i had no recovery at all, not even samsungs.
i am trying to root my phone for froyo and have done everything up to getting clockwork to install i tried odin no luck, i tried samsung flash update zip no luck any suggestions please. i was following instructions from jt's thread
Thanks
I've had trouble getting certain versions of clockwork to work on the initial flash. And using the Flash Clockwork option from the Clockwork app doesn't work intially for me in any version.
What version are you using?
Also, what version of OS are you running (DL09, EA28, etc.).
I believe adrynalyne mentioned this in one of his posts, but I read some of the new stock kernels don't allow CWM. If it detects this, it will overwrite the Recovery section and get rid of CWM.
If this is what's happening to you, once you install CWM, you have to turn on the phone and immediately go into recovery. You will need to install a custom kernel to allow CWM to stay on there.
Look in the development forum, and there's a thread in there that talks about this. It might just impact certain builds, though, so it might not be what you're seeing.
Yea you odin the cwm and then you load your rom when cwm boots up. Dont use rom manager as it can delete your cwm and you have to reodin it back
Sent from my SCH-I500 using XDA App
Hi,
I'm currently using Samsung Vibrant (t-mo version) running Firmware 2.2, Baseband version T959UVKB5, Kernel 2.6.32.9.
My problem is I can never boot into ClockWorks Recovery. I've CWR's update.zip downloaded using ROM Manager. Rooted the phone using SuperOneClick.
When I boot into recovery and select apply update.zip, it gives me an error half way thruogh about verification failed.
So I replaced Android Recovery 3e, with another Android Recovery 3e which skips the verification. It installs fine but restarts back in Android's recovery. On rebooting I get a phone with everything back to default!
What am I doing wrong?
Thanks.
PS: I want to upgrade to CM7. which I had at one point but reverted because my bluetooth failed to connect to my headset.
Are you reinstalling packages twice?
Honestly, why not just odin to jfd and rather than boot and flash cwr, just use the update.zip in the noob guide.
I'd encourage checking that route (noob guide is in my signature).
I'm certain we could find a way for yours to work, but if you are going to try a new rom, using ODIN may benefit you anyway. It will not format your internal or external.
cant get or find cwr for samsung vib s.. been looking all night
go to the noob guide.
I am on Samsung Vibrant Froyo 2.2 T959UVKB5.
I have seen your post and it provides 2 update.zip files for JFD.
I do not want to install custom ROM, I just want to root the phone.
will that update.zip work on my phone?
If all you're doing is rooting just for the root apps and not for a custom rom you should use zip A. However the easiest method for you to root would be superoneclick root. Look it up, it will have you rooted with the click of a button (hence the name)... The only thing is that it may stir up your anti-virus, even though it is safe...
Sent from my SGH-T959 (Samsung Vibrant)
Thanks you!
Ok, so long story short - I went through a lot of steps to restore my fascinate to stock, and then rooted it through recovery. It worked fine until I installed Rom Manager and now my phone won't boot into recovery again. My question is - did I do something wrong?
I restored my phone to stock using Heimdall
Updated it to the latest version
Rooted it using odin and flashing recovery
then installed Rom Manager
Thank you for all your help guys!!!
kuczynt said:
Ok, so long story short - I went through a lot of steps to restore my fascinate to stock, and then rooted it through recovery. It worked fine until I installed Rom Manager and now my phone won't boot into recovery again. My question is - did I do something wrong?
I restored my phone to stock using Heimdall
Updated it to the latest version
Rooted it using odin and flashing recovery
then installed Rom Manager
Thank you for all your help guys!!!
Click to expand...
Click to collapse
download odin (onto pc), a non stock kernel and the recovery.zip that you want to use.(both recovery.zip and non stock kernel on your sd card)
Put your phone in dl mode and flash recovery via odin...when odin is done, immediately three finger boot into recovery and flash non stock kernel, and reboot.
Unless your on cm7 rom manager is useless and will bring more hurt then help, and your recovery is being overwritten by the stock kernel every time you boot which is why you need the non stock kernel...I personally would recommend a rom that contains a kernel...you can find a list of all roms, kernels, and recoveries in the dev section stickies.
Do you know how to properly flash roms, and kernels? I ask because I don't want to get you stuck even worse...if you need step by step instructions I'll reply later when I'm at a pc
Sent from my SCH-I500 using XDA App
You can give me a few tips and hints. That would be appreciated. Also, I thought the easiest way was through Rom Manager.
On a side note - what would be the most stable ROM to flash to the fascinate?
EDIT: Ok, so I installed PowerWashed 1.2 ROM and can handle this on my own a little bit. I'm still a little unsure on which roms are most stable/trustworthy, but I might stick with this one for a while.
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.