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.
ok.
I was on 2.5.x for a while with no issues. After installing SuperClean 2.8, I noticed Rom Manager was stating there was a newer version.
I read in the SC thread that after 2.8 is installed, using a 3.x CWR was ok. However, what wasn't clear until I tried to put on 2.9 was that in reality you should just not upgrade to 3.x if you want to continue flashing roms at all.
So, now I followed JT's thread and installed the red 2.5.x CWR. This is where I'm at now.
If I open Rom Manager, it says I'm still on CWR 3.0.0.8. If I use it to reboot to recovery, it simply doesn't work. Takes mins to load to recovery and is stuck on blue recovery with an "esignature" error when trying to run update.zip from that menu.
However, if I use the "Recovery" option in the power menu (available in SC 2.8), the phone reboots and quickly goes to the red 2.5.x recovery.
What do I do to get Rom Manager to recognize the new lower version of recovery and thus run correctly?
I have successfully been able to root and install everything on my Mytouch4G just fine, however, when I tried to install my wife's Vibrant, I am stuck. Here is what I have done:
1) I rooted successfully using superoneclickv1.9.1
2) I installed ROM Manager and also downloaded the Auxora ROM to get ready to install
3) When I flash CWM recovery, it says current and latest recover is 2.5.1.2 (concern here that my mytouch says 3.0.2.4 - do different phones install differently with CWM?). When I look at all CWM recoveries I also notice there is two seemingly more current versions available 2.5.1.3 and 2.5.1.4. I have left it at .2 but wondering why all the versions.
4) When I reboot into recovery, I always get the stock recovery and have not been able to get CWM recovery so I am unable to flash my Auxora ROM. I ran update packages numerous times, and get a signature verification error. I have tried a recovery 3e patch that does not work either. I also gave a try at downloading and SDK, but received temp root errors (phone is already rooted).
After reading many posts, I cannot seem to get a direct answer on what I should do to get CWM to actually boot properly, so I can flash a ROM. Someone said to flash the stock JDK rom, but if I can't boot into recovery, how can I flash anything.
Any help would be greatly appreciated.
You need to get a program for your pc called odin to get back to stock. you can find that and instructions on how to use it if you search for the daily updated vibrant bible its GREAT
http://forum.xda-developers.com/showthread.php?t=849028
going to stock eclair heres a a great guide
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Every once n a while I haft do the install packages thing twice before it gives me clockwork green
. Hope this helps.. o n btw u should look at some of the other roms in the bible before u try auxora
yes u should go back to stock eclair for every rom, in my opinion. Then after that do the 3 button combo and install packages and u will have to do it twice and then the green screen will kick in and ready to rock a new rom.
i hope this helps
What is your current firmware?
I see you posted over in the "NOOB GUIDE" thread, you should really try to root using the method posted there and not any one click root apps.
This should be the root method everyone uses:http://forum.xda-developers.com/showthread.php?t=723479
After root your phone recovery should be blue. Choose "reinstall packages" gives you green recovery(this may need to be repeated multiple times to work possibly including flashing CwMRecovery with ROM manager. I recently did it 5 times b4 i got green recovery)Once you access green recovery chose "apply sdcard:update.zip" go into advanced and choose "reboot recovery" This should give you red recovery. Do a nandroid backup and flash away. Good luck!
Another option you could do is to download SGS kernel flasher from the market and flash a voodoo injected kernel with that app. Then when you boot into recovery you will have red voodoo recovery and you can flash away.
Odin to stock the best way to flash a new rom
Sent from my SGH-T959 using XDA Premium App
jman531 said:
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Click to expand...
Click to collapse
The stock 2.2 that Samsung distributed with their Kies tool has a recovery that checks signatures. Everything earlier does not check signatures. So either use something earlier to get CWM running, or use a ROM that doesn't have the stock 2.2 recovery in the first place, or mod your recovery using the method described in http://forum.xda-developers.com/showthread.php?t=833423
Using Odin to go back to stock Eclair between your flashes of modded roms has the benefit of taking care of this, and also can clear up left over bits and pieces that may interfere with the proper function of your new ROM.
ok, i followed the instructions and am back to eclair, however, whenever I install packages, it just reboots the phone, not even back into stock recovery. I use the 3 key method and get into recovery, run install packages, and the phone just boots back up...its like it isn't running the update.zip file...
UPD: When i load rom manager and try to reboot into recovery, it says the application superuser permissions has stopped unexpectedly and keeps force closing now....titanium backup wont run now either, my root permissions seem whacked after going back to eclair?
UPD2: I followed instructions to unroot and reroot here: http://forum.xda-developers.com/showthread.php?t=739300
It removed superuser, then added it back again, but I still get the unexpected error and it appears my root is not in place. I am back to eclair, and now need a certain way to get my root fixed, so I can try and flash CWM recovery. Without root working, it is not letting me. My wife hates me now for doing this to her phone, so those of you that are married, I would appreciate your assistance to get back on her good side...before Mother's day...please? =)
Ok, thanks for all the help, however, I am really back where I started. I can only get stock recovery, and for the life of me, cannot get CW recovery to load. I used ODIN to go back to eclair on the vibrant, have a good root on the phone now, and no matter how many times i reinstall packages i cannot get clockworkmod recovery to load, ever. Any more thoughts out there?
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
thanks...It is rooted, but not sure about busybox...the stock recovery is 2e now since I went back to eclair, so not sure i should follow that link as it talks about modifying 3e and making it backwards compatable. I did use that process before I went back to eclair, and it didn't work for me. I have uninstalled rom manager, and reinstalled...and it is different in that it shows a flashed recovery 2.5.1.2, and never asks me for my phone type anymore...it used to ask me and i had to select vibrant....is the recovery supposed to be 2.5.1.2? when I show all recoveries it lists .1, .2, .3, .4 so wondering if I should use .3 or .4...why does it stay at .2?
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
OK>>> I GOT IT... Thanks to everyone who helped...Here is what was needed:
1) Install ODIN, install back to eclair
2) uninstall ROM Manager, reinstall
3) I needed to select the 2.5.1.2 recovery from the list again (this was important as it somehow knew of the previous load, but files were missing, or something was just wrong.) It finally loaded properly, and asked for phone type again, so selected vibrant
4) I rebooted into recovery, and instead of install packages, i rebooted once, as starkiller suggested
5) After reboot, went back into recovery from rom manager, and this time installed updates, and it showed that it replaced the recovery with CWM.
6) It rebooted into stock recovery however, so I once again selected install updates, and it went right into CWM recovery, and now I am flashing happy!!!
Thanks again everyone...this was soooooo different than my mytouch4g!
If you have the Kies update of Froyo, the 3e mod will sometimes not work. I've gotten to CWM though , but its best to downgrade then flash a ROM from there.
I just wanted to bump this thread because it really helped me.
I've messed around with numerous android phones, and I've never had thie issues I've had with this phone getting into recovery to flash ROMs
Thank you!
Here's the situation:
I recently s-off'd my Legend (Bell Canada variant) in order to try out ogo2's NewSense ROM and do some metamorph stuff. I also attempted in install ClockworkMod 3.0.2.8 via the fastboot method which seemed to work just fine.
I used ogo2's NewSense beta 2 without any difficulty, but decided to switch back to CM7 via a backup I made earlier. No problems so far.
Here's the problem:
Yesterday I tried to flash beta 4, and this is where things got a bit weird.
When I use Rom Manager to try flashing beta 4, it loads ClockworkMod 2.5.0.7. Likewise, if I reboot into recovery from ROM Manager, I end up in ClockworkMod 2.5.0.7.
If, however, I manually boot into recovery then I end up in ClockworkMod 3.0.2.8.
I've tried flashing beta 4 manually and through ROM Manager and each time the ROM seems to install just fine but I end up stuck at the splash image. Naturally, I try to manually boot into recovery so I can restore, but it often just reboots or gets stuck at the splash image before CWM can load. Not a problem anymore.
I have to do a couple of battery pulls before I can sucessfully enter recovery (when I do, it's CWM 3.x).
Since then I've restored to CM7, but I can't flash beta 4 and the CWM disparity doesn't seem right to me. In otherwords, my phone is completely usable but CWM doesn't seem right.
Does anyone have any insight into this problem or a possible solution?
The issue lies in the way ROM Manager deals with recoveries. When the Legend was first given ROM Manager support S-OFF was a thing of dreams, we had to use the fakeflash method to get to CWM, so Koush made ROM Manager use fakeflash with some phones. Ours was one of them. When you "flash" a recovery using ROM Manager a fakeflash .zip is downloaded to your phone and stored somewhere, then using a method I don't fully understand ROM Manager reboots to recovery and "flashes" the fakeflash .zip. Now, because S-OFF we can flash recoveries to the recovery partition, but Koush hasn't updated his app to allow us to make use of it, nor has he made an updated version of CWM in fakeflash format for it. If someone cared enough they could probably get support for the latter at least. Because Koush hasn't updated his stuff to make use of new developments for our phone, ROM Manager assumes S-ON and still uses the fakeflash method, hence CWM 2.0.5.1 when using ROM Manager.
Thanks for the info. I was beginning to suspect something along those lines but it's always nice when someone who actually knows something about it gives an explanation.
I've seen on the Cyanogen forum that there is a fake flash 3.0.2.8. Anyone who can confirm this? I can't manage to get it to work :S
Sent from my HTC Legend using Tapatalk
I installed VeganTab GE and the install was pretty successful using the nvflash method. The only thing that I wasnt able to do was install Pershoots latest rom (boot-cm_2632.41_gb-oc-uv-xtra-vfp_fp-060311.zip)
I made the mistake of installing Rom Manager and updating the CWM to 2.1.5.8. My question is that would there be problems if I upgrade the newer kernel using CWM2158 ? Has anyone tried to do this? According to some posts, it seems that CMW v.8 is the only version that plays nice with the gtablet.
Right now the tablet is functioning, but occasionaly just shuts down apps like the browser and maps. Hopefully a newer kernel fixes that.
Just re flash cwm .8 bekit and call it good. Rom manager does not play well even with .8 let alone the newest recovery you installed.
Don't waste your time and data nvflashing after it borks everything and you have to do a drastic recovery.
I originally downloaded cwm v.8 from the forums. This is the same as cwm .8 bekit ? The cwm v.8 is the version that got overwritten to 2.1.5.8, and for some reason, when I try to re-flash it into the recovery mode, it cant seem to find the update.zip and recovery folder even though its there
.8 bekit is the same as cwm .8 you flashed in the past. Bekit is the one who altered it for gtab. You can nvflash cwm which is the safest way or you can use the cwm you currently have to try and reflash .8 cwm and just cross your fingers.
Here you can find simple step by step instructions to nvflash cwm.
http://viewsonic-gtablet-for-dummies.webs.com/
Good luck
I will try to nvflash the cwm. Seems like the best option right now. Thanks !