Rom Manager Issues. - Vibrant Q&A, Help & Troubleshooting

Hy there,
Well I look in to my issue and looks like here some people have the same issue as me but none of there solutions work for me.
I have Rom Manager Pro and every time I need to do a backup I need to apply the update.zip it does not send me to ClockWorkMod recovery automatically as it suppose to. I want to apply a new ROM but I am affraid to because of this small issue.
Any ideas?
Info:
T-Mobile Vibrant Stock Froyo 2.2 With root and Modified 3e from here http://forum.xda-developers.com/showthread.php?t=833423
TIA.

wtf.now? said:
Hy there,
Well I look in to my issue and looks like here some people have the same issue as me but none of there solutions work for me.
I have Rom Manager Pro and every time I need to do a backup I need to apply the update.zip it does not send me to ClockWorkMod recovery automatically as it suppose to. I want to apply a new ROM but I am affraid to because of this small issue.
Any ideas?
Info:
T-Mobile Vibrant Stock Froyo 2.2 With root and Modified 3e from here http://forum.xda-developers.com/showthread.php?t=833423
TIA.
Click to expand...
Click to collapse
Try the toolbox
http://forum.xda-developers.com/showthread.php?t=954509

nomadrider123,
Thanks for the help and pointer. I am now just running a small experiment to see what happens. Hopefully I wont brick my vibrant. Basically I let it do an update of the kernel using rom manager. Its going now. Lets see what happens.
I am also on a bind with most of the user apps as they run in windows. I run Linux and Mac. I guess its time for VM

wtf?!? She talks! LOL.... WoW the damn thing just told me an estimated time. Nice.

ok so after a few min. My cell was back online with a new kernel. I am happy with Rom Manager. Issue solved.
Thanks!

well so far I have no complaints the voodoo kernel is working very well. I can for sure tell the difference.
For all the n00bs out there. This well worth the shoot.

Related

Any recommendations on Custom Roms?

Hey everyone.
I recently rooted my Hero GSM phone and tried to play around with some Custom Roms.. I'm currently running FroydVillain with a 691 kernel and I like it a lot, but want to know if there's any other Roms running smoother on the Hero packing Froyo..
I used to have the official eclair (2.1) with launcherpro installed, but wanted to try Froyo out because I heard that it runs 450 % faster than eclair. And since I went over to Custom Roms my batterytime has been lowered significantly..
Also if anyone could tell me what RADIO's are I would be very happy
Sorry for all the questions, but I have just one more..does updating the recovery software help on performance? I have an old version I think.. can anyone please link the newest?
I find the market of available Roms so large and wanted to know if anyone could recommend some Roms and include some links on where to get..
Froyo prefered since I just got used to how it works.
Thanks in advance
Sent from my HTC Hero using XDA App
Hammerbak said:
Hey everyone.
I recently rooted my Hero GSM phone and tried to play around with some Custom Roms.. I'm currently running FroydVillain with a 691 kernel and I like it a lot, but want to know if there's any other Roms running smoother on the Hero packing Froyo..
I used to have the official eclair (2.1) with launcherpro installed, but wanted to try Froyo out because I heard that it runs 450 % faster than eclair. And since I went over to Custom Roms my batterytime has been lowered significantly..
Also if anyone could tell me what RADIO's are I would be very happy
Sorry for all the questions, but I have just one more..does updating the recovery software help on performance? I have an old version I think.. can anyone please link the newest?
I find the market of available Roms so large and wanted to know if anyone could recommend some Roms and include some links on where to get..
Froyo prefered since I just got used to how it works.
Thanks in advance
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
Latest Recovery: http://forum.xda-developers.com/showthread.php?t=561124
The radio I recommend is the latest GSM one at http://www.villainrom.co.uk/forum/showthread.php?307-radio-roms-download-links
Are you using latest Froyd, as we've got reports of 2 full days of battery life.
But 450% is an exaggeration, as it's based on a nexus 1 without vs. with JIT. You should get > 5 Mflops though in linpack using froyo.
Regarding the question in the title. You could search around here a little on Q&A since it has been asked a lot of times But mostly you'll get the answer that it's different from person to person and everyone has their favourite ROM for instance my favourite ROM is Cronos (anything) but I'm guessing pulser_g2's would be VillainROM (LOL)
Lol. Yeah it depends on what you want. I mentioned Froyd as you're on it already, but sense 2.1 roms do still exist, though you might try disappointed with performance.
I used a sense rom recently and had to remove it as I couldn't bear the slowness, even with oc.
But yeah, search is your friend. Decide what you want, and you'll find it here.
Thanks for the links.
Yeah well, I spent almost an hour reading about different Roms here and there and I see that it's kinda up to one self what you like about the different Roms. I've been very happy with FroydVillain so far, but I guess I should go ahead and give some of the others a try.
I've just backed up my current phone settings with "Titanium Backup" but is this enough if I decide to try a new Rom and want to go back later on? or should I do a nandroid backup?
And again when I flash over the new recovery.img.. Do I need to backup anything beforehand?
My Froyd version is the latest and I've kept on updating whenever I saw new updates. And yeah, two days is in my opinion not much. Beforehand, on the official 2.1, I could easely tweak 4-5 days out of my standard Hero battery, but I guess this has something to do with the kernel?
Sorry.. I'm really a newbie on this
Hammerbak said:
Thanks for the links.
Yeah well, I spent almost an hour reading about different Roms here and there and I see that it's kinda up to one self what you like about the different Roms. I've been very happy with FroydVillain so far, but I guess I should go ahead and give some of the others a try.
I've just backed up my current phone settings with "Titanium Backup" but is this enough if I decide to try a new Rom and want to go back later on? or should I do a nandroid backup?
And again when I flash over the new recovery.img.. Do I need to backup anything beforehand?
My Froyd version is the latest and I've kept on updating whenever I saw new updates. And yeah, two days is in my opinion not much. Beforehand, on the official 2.1, I could easely tweak 4-5 days out of my standard Hero battery, but I guess this has something to do with the kernel?
Sorry.. I'm really a newbie on this
Click to expand...
Click to collapse
If you want to go back you need a nandroid backup yes. If your talking about updating your recovery image (lol I'm guessing) no you don't. Just flash it. And the battery has something (everything ) to do with the kernel but if you want better battery set you min freq of your CPU lower or you can lower the max freq.
I see..
Thank you very much for answering.
I have just one minor problem..
How the heck do I flash over the recovery image? Don't I use the FlashRec-thingy? Might have deleted it at some point :S
Hammerbak said:
I see..
Thank you very much for answering.
I have just one minor problem..
How the heck do I flash over the recovery image? Don't I use the FlashRec-thingy? Might have deleted it at some point :S
Click to expand...
Click to collapse
I reccomend you flashing Amon-RA. There is a guide in his thread on how to flash it But if you want the ultimate easy noob thing you can download ROM manager from the market which will alow you to download and flash a pretty descent recovery in one click
Yeah.. Flashing Amon-RA is what I'm trying to. It seems I have the 1.5.2 version installed and I just downloaded the 1.7.0 one..
The first time I flashed "Amon-RA" did it with the help of a program called FlashRec. I followed the guide on theunlockr.com and I now end up with a message: "Backup FAILED: Could not run command." when I try to "Backup Recovery Image" through that FlashRec program.
I have an idea of how to work around this but I'm not 100% sure this is what's needed..?
Could I run the phone into recovery mode (through that 1.5.2 Amon-RA thingy) and then flash the never version right onto it or is this the wrong procedure?
Hammerbak said:
Yeah.. Flashing Amon-RA is what I'm trying to. It seems I have the 1.5.2 version installed and I just downloaded the 1.7.0 one..
The first time I flashed "Amon-RA" did it with the help of a program called FlashRec. I followed the guide on theunlockr.com and I now end up with a message: "Backup FAILED: Could not run command." when I try to "Backup Recovery Image" through that FlashRec program.
I have an idea of how to work around this but I'm not 100% sure this is what's needed..?
Could I run the phone into recovery mode (through that 1.5.2 Amon-RA thingy) and then flash the never version right onto it or is this the wrong procedure?
Click to expand...
Click to collapse
Lol thats excatly how I rooted my phone too (same recovery and website even) Look in the thread it's described how you flash the new recovery via ADB
Yeah ehm... I'm kinda new to this so all his "code" or whatever it is doesn't give me a hell lot of clues..
Install
There are several ways to install a custom recovery, choose the one that suits you most (I probably forgot a few).
via adb -> Requires a custom recovery (with test-keys) like Cyanogen's v1.4 or my previous recovery
Code:
Copy recovery-RA-hero-v1.7.0.1.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img
Click to expand...
Click to collapse
I fixed the steps underlined but after that I kinda went cold on what the **** to do :S
I boot into my recovery and what I get from his "guide" is that I my Hero should do something when I plug in the USB cable.. but nothing happends.. anyone who can put it down in baby-steps for me? :O
There's another way to do this it seems (2nd guide in his thread) but it seems to involve even more "code" so I guess I'll settle with this if it's possible.. :S
Hammerbak said:
Yeah ehm... I'm kinda new to this so all his "code" or whatever it is doesn't give me a hell lot of clues..
I fixed the steps underlined but after that I kinda went cold on what the **** to do :S
I boot into my recovery and what I get from his "guide" is that I my Hero should do something when I plug in the USB cable.. but nothing happends.. anyone who can put it down in baby-steps for me? :O
There's another way to do this it seems (2nd guide in his thread) but it seems to involve even more "code" so I guess I'll settle with this if it's possible.. :S
Click to expand...
Click to collapse
For you I would just recommend installing "ROM manager" from the market and then let it install ClockworkMod recovery that should do for you
EDIT: There seems to be an issue with ROM manager at the moment. It wont flash...
Yeah.. Might as well try this out since no one wants to point out on how to it the "geeky"-way
EDIT:
I seem to get an error when trying to flash the ClorkworkMod Recovery.. Any idea why?
Nvm.. Some dude (erasmux) has made an update.zip and uploaded to the Amon-RA post.. it did the trick

[Q] Clockword Mod ROM Manager "Error Occured While Processing the ROM List!

For the past few weeks Ive been getting error message when using Clockwork Mod Rom Manager, under 'Download ROM" "Error Occured while processing the ROM List!" when trying to download a ROM under SonofSkywalker3. Im running Eugene's Ginger Clone now but also had that problem under NeroV3. I was running Macnut R14 a fews weeks ago and it worked fine. So I dont think its the ROM. Anyone else been having that problem? Is there a fix? See attached pic. Thanks.
Are you using voodoo?
Sent from my Nero powered Vibrant
I'm using Voodoo, and getting the same error
Are your trying to flash a rom or mod? If so, why don't your just put the .zip in the root of you're SD card to flash from there with cwr?
I've never used the option that you're trying to use.
Sent from my SGH-T959 using XDA App
Gopena said:
I'm using Voodoo, and getting the same error
Click to expand...
Click to collapse
If you have the recovery option in the power menu use that.
Sent from my Nero powered Vibrant
I think you guys are missing the point. Skywalker has a bunch of stuff to download thru rom manager. But its been showing an error for a few weeks. Not sure what's up with it. He uploaded it to rom manager so it could all be in one place.
Powered by Axura with a dash of Voodoo
GreggoryD502 said:
I think you guys are missing the point. Skywalker has a bunch of stuff to download thru rom manager. But its been showing an error for a few weeks. Not sure what's up with it. He uploaded it to rom manager so it could all be in one place.
Powered by Axura with a dash of Voodoo
Click to expand...
Click to collapse
I guess this question should be raised to the developer.
Not using Voodoo with Gingerclone but did use it with Nero. Anyways, Voodoo is disabled.
Im not flashing a ROM, but pieces from the ROM. I just want to get some of the goodies that Sonofskywalker has like Widgets and Wallpapers. Skywalker offers Ala Carte options instead of downloading an entire ROM.
I'm having the exact same problem. I been looking everwhere to fix this problem,but so far found nothing. I'm running Axura 2.2.5.7 rom. I'm not sure if its the roms. I odin back to stock and downloaded Skywalker Black hole 1.2 beta and some other goodies download went fine at frist. I trying going back in rom manager to get some more goodies and got an error "Error while processing rom list" I am a rom manager premuim user. Help Please!!!
I have the same problem. Trying to pull up any ROM list will result in the same error.
Sent from my SGH-T959 using XDA App
To Clarify, this feature worked in Nero Beta 3, and Nero V1.
Going to try reinstalling Rom Manager
Running Nero V3 with SBGB and Voodoo
Been having the same issue with Nero v3. And I can confirm that for the first several days of v3 it was working fine, and then it went kuput. I know I'm only adding to list of people looking for a fix, but at the very least want to let the OP know they're not alone with this issue. I don't believe it is ROM specific.
I do have a few things i've picked up over the past week, because i'm aware of the problem, but not how to fix it.
1. Some people have reported that by using odin to revert to stock they can then get rom manager working.
2. rom manager does successfully download my manifest, but it errors out while trying to process it.
3. it's nothing wrong with my manifest, because i have changed all the entries for the vibrant over to fascinate and the fascinate reads it fine
4. I have tried contacting koush, but haven't gotten any help.
This info leads me to two possible conclusions:
1. It's a problem with something in some custom roms (including Blackhole) that prevents rom manager from using something it needs to read the javascript on the vibrant
2. It's a problem with the rom manager software, either the version you have, or just on the vibrant in general.
some info that might help me fix this:
1. if anyone can get me a logcat of while the problem happens, i may be able to see what the issue is
2. if someone can tell me the rom manager version, it may be an older one and i can post the latest from the fascinate, which might help.
also i'm going to try to release a 2.0 beta based on JL5 later this week which may or may not fix these issue. and i'm going to continue to hope for help from koush.
Thanks SonofSkywalker. Really appreciate it. Love your work. I'm busy right now but hopefully I can find time to do a logcat in a couple days.
quest4fire said:
Thanks SonofSkywalker. Really appreciate it. Love your work. I'm busy right now but hopefully I can find time to do a logcat in a couple days.
Click to expand...
Click to collapse
Update: I read the logcat and it was showing my Vibrant as a Fascinate in CWM and it there was definitely an error with downloading. So I decided to restore my backups I had of Macnut R14 and Nero to see if I could download your ROM and was unable to, same error message. Then my phone got corrupted because of restoring the backups. I Odin back to stock 2.1 JFD and now I am able to download your ROM in CWM. So I dont think its a CWM issue. Unfortunately I lost my logcat because i had it inside my phone, was using a Logcat app from the market because I was having trouble getting my ADB server starting.
quest4fire said:
Update: I read the logcat and it was showing my Vibrant as a Fascinate in CWM and it there was definitely an error with downloading. So I decided to restore my backups I had of Macnut R14 and Nero to see if I could download your ROM and was unable to, same error message. Then my phone got corrupted because of restoring the backups. I Odin back to stock 2.1 JFD and now I am able to download your ROM in CWM. So I dont think its a CWM issue. Unfortunately I lost my logcat because i had it inside my phone, was using a Logcat app from the market because I was having trouble getting my ADB server starting.
Click to expand...
Click to collapse
sonofskywalker3 said:
I do have a few things i've picked up over the past week, because i'm aware of the problem, but not how to fix it.
1. Some people have reported that by using odin to revert to stock they can then get rom manager working.
2. rom manager does successfully download my manifest, but it errors out while trying to process it.
3. it's nothing wrong with my manifest, because i have changed all the entries for the vibrant over to fascinate and the fascinate reads it fine
4. I have tried contacting koush, but haven't gotten any help.
This info leads me to two possible conclusions:
1. It's a problem with something in some custom roms (including Blackhole) that prevents rom manager from using something it needs to read the javascript on the vibrant
2. It's a problem with the rom manager software, either the version you have, or just on the vibrant in general.
some info that might help me fix this:
1. if anyone can get me a logcat of while the problem happens, i may be able to see what the issue is
2. if someone can tell me the rom manager version, it may be an older one and i can post the latest from the fascinate, which might help.
also i'm going to try to release a 2.0 beta based on JL5 later this week which may or may not fix these issue. and i'm going to continue to hope for help from koush.
Click to expand...
Click to collapse
I'm using Rom Manager 3.0.0.7 and can't get into any roms. Not sure how to get a logcat, but once I figure it out, I will send it your way
I had the same issue and I was able to get Rom Manager working again by performing the following steps:
1) Clear the cache from the Rom Manager app (under Settings/Applications/Manage Applications)
2) From within Rom Manager run "Fix Permissions"
3) Reboot (which you're prompted to do when the "Fix Permissions" step is completed anyway)
This has worked for me twice.
Good Luck

[Q] Samsung vibrant 2.2 lag fix

plzzzz help does anyone know how to get a lag fix for samsung vibrant with official froyo. t959uvka6
kernel 2.6.32.9
i tried using ryan's oclf and it said i dont have enough space and that i at least need 1 mb of memory. I searched this up and it said that some phone sofwares take up all the memory in some areas so it can't work.
Can someone plz help and tell me if they got lag fix on their smasung vibrant and i dont want to install a custom rom on my phone just a lag fix.
godfathermzq said:
plzzzz help does anyone know how to get a lag fix for samsung vibrant with official froyo. t959uvka6
kernel 2.6.32.9
i tried using ryan's oclf and it said i dont have enough space and that i at least need 1 mb of memory. I searched this up and it said that some phone sofwares take up all the memory in some areas so it can't work.
Can someone plz help and tell me if they got lag fix on their smasung vibrant and i dont want to install a custom rom on my phone just a lag fix.
Click to expand...
Click to collapse
Voodoo where it's at bro. One click lag fix only gives good quadrant score ,voodoo makes your phone feel lag-less but has a little smaller quadrant + amplifys the headphone Jack. It's your decision.
Sent from my SGH-T959 using XDA App
You need root to get any lagfix. If your on the stock OTA 2.2 you need to odin back to stock, re root and then flash a voodoo kernel.
can someone plz tell me how to install the voodoo lag fix on my phone plz i already rooted it i need to know how to get the kernel and put it on my phone. can you guys plz give me step by step instructions of what to do. plzz help i have been trying forever to get a lag fix i cant do nothing works. i am already rooted using super one click root
godfathermzq said:
can someone plz tell me how to install the voodoo lag fix on my phone plz i already rooted it i need to know how to get the kernel and put it on my phone. can you guys plz give me step by step instructions of what to do. plzz help i have been trying forever to get a lag fix i cant do nothing works. i am already rooted using super one click root
Click to expand...
Click to collapse
First you need to install rom manager from the market. The free one will suffice. Then open it and flash clockwork recovery. Next find the voodoo kernel thread by supercurio in the development section. Pick your kernel id go with the one closest to your baseband. Download and place on the internal sd card. The using rom manager reboot into recovery. If that takes you to the blue recovery then click on reinstall packages. You may have to click that twice. You should end up at a green recovery menu. Select install zip from sd card then select choose zip. Then scroll down and find the kernel and click it. It will ask if your sure. Select yes. After a bit another menu will show up. Select go back then reboot system. Wait till its done. It will take 10 minutes or so. A robotic female voice will let you k ow when its done.
Powered by my Triggerized Vibrant
My problem is similar to yours godfathermzq. I am new to all this and I was scared that I will brick my phone while installing unofficial froyo 2.2. So I waited loooong enough and now I have installed the official froyo 2.2 from samsung’s website.
My phone is slow and I want to get a lag fix. I am using Samsung Vibrant (love it) and I don’t even have tons of app running. I have Launcher Pro + Fancy Widget + few apps.
I have few set of questions and would really appreciate some help.
1. Did anyone try Greggory’s method? Were you successful?
2. Should I try Ryan’s One click lag fix considering there haven’t been any major updates with it since August 2010- http://forum.xda-developers.com/showthread.php?t=760571
If I brick my phone, if there a way to fix it to run again?
3. Anything possibly I can do to speed up my phone?
4. Any other alternative way I can follow? Please help!
Thank you very much for your input! Your help is really appreciated!
My advice is get Clockwork recovery installed and then flash a custom rom like Bionix or Trigger. Stock is better with 2.2 but it's amazing how much they can optimize the rom.
I've been running Bionix roms for months and they are fantastic. Team Whiskey FTW.
"Greggory's Method" is how just about everyone does this. He laid it out as clear and concise as I've seen it though. Read it again, then read this: the Vibrant Bible and then do it. It’s the only way to get what you guys want.
Yeah it’s a little scary at first but, if you follow each step and don’t rush anything, (Like: do it on a full battery; don’t freak out if a screen in the middle of it seems to be “stuck” for 3 minutes; don’t touch a button for 15-20 minutes after the first reboot - then reboot again) you will be fine. The instructions all start to click once you begin the actual process.
And, yeah, you can mess up your phone. If you’re not down with that, stop here and be happy with the pretty great device you have now. But I agree with Radio, just go right for a new ROM like Bionix v1.3.1 and you will be ready for prime time. I'm telling you guys: the risk is minimal and the payoff is substantial.
I had this same problem when I got my vibrant, then I learned that no matter HOW bad you **** up, ODIN will save your ass almost everytime.
Go to the android dev. section for the vibrant, and follow the noob guide that is stickied. This will help you A TON.
http://forum.xda-developers.com/showthread.php?t=849028
There's the link for the thread.
Detailed instrucions on Rooting Froyo 2.2 Vibrant (Vibrant updated from Kies Mini)
12345678910

Questions from a Vibrant newb

Hello, all!
I've purchased a vibrant for my wife over the weekend (i'm on sensation), and have several questions.
The guy i bought it from did a hard-reset supposedly, and said that it reverted it back to the stock android build. Seemed weird, but the first thing i did was update it via kies mini to the froyo build. It's been working fine, except for the camera started messing up last night. Going into black screens, showing "camera failed" errors. It also takes some time (2-3 secs of black screen) to process a picture after it has been taken. I don't remember it doing that on the stock build. I did update it to the latest firmware.
Should i root the phone and flash a different rom? (which rom would you recommend?) A short google search revealed a lot of people having slow-downs after the froyo update.
Appreciate your help!
just to follow-up. wife's been having problems with the music player app hanging, then the phone shut down while she was installing something.... i'm going to wipe everything first to see if it helps any, but will end up rooting it and flashing something else, most likely.
Before rooting make sure you odin back to stock 2.1. That should het rid of the problems
Sent from my SGH-T959 using xda premium
Definitely do what the above poster suggested. Go to the development section and get the AIO toolbox. It has everything you need to get back to stock and get you rooted. If your looking for a good stable rom I'd recommend bi-winning v3. Good luck.
thank you, guys! ended up using the aio toolbox, like suggested. smooth sailing
i've put ultimate rom on it for now, see how she likes it. i'll check the bi-winning (lol) one also. anything else that you'd recommend for now? thank you!
WORD OF IMPORTANT CAUTION!!!!
DON'T EVER USE KIES AGAIN OR YOU WILL BRICK THE PHONE!!! THIS IS A GIVEN, YOU JUST GOT LUCKY, BUT ITS LIKE PLAYING RUSSIAN ROULETTE!! And when it corrupts the Primary and Secondary Boot loader files you'll be bricked hard for sure!!!
KIES IS NOTORIOUS FOR BRICKING VIBRANTS, IT DID IT TO MY PHONE AND MANY OTHERS HERE!! I WAS NOT AWARE OF THIS UNTIL IT WAS TOO LATE FOR ME!!
Odin or Heimdal are the only programs I would use to do restores other than Baywolfs AIO which is very friendly and has the JFD Rom in it and the Mapping Pit file known as the 512.
You could also use Eugenes No brick Froyo using Odin which has the 2E update file in it, so when you root it and Flash CW recovery, and then re-install packages it will give you the 2E green recovery menu you'll need to successfully flash other ROMS in the future you want.
RussianBear said:
thank you, guys! ended up using the aio toolbox, like suggested. smooth sailing
i've put ultimate rom on it for now, see how she likes it. i'll check the bi-winning (lol) one also. anything else that you'd recommend for now? thank you!
Click to expand...
Click to collapse
Theres a GB ROM out by Hercules that is a Galaxy S II port...its pretty sweet
dseldown said:
WORD OF IMPORTANT CAUTION!!!!
DON'T EVER USE KIES AGAIN OR YOU WILL BRICK THE PHONE!!! THIS IS A GIVEN, YOU JUST GOT LUCKY, BUT ITS LIKE PLAYING RUSSIAN ROULETTE!! And when it corrupts the Primary and Secondary Boot loader files you'll be bricked hard for sure!!!
KIES IS NOTORIOUS FOR BRICKING VIBRANTS, IT DID IT TO MY PHONE AND MANY OTHERS HERE!! I WAS NOT AWARE OF THIS UNTIL IT WAS TOO LATE FOR ME!!
Odin or Heimdal are the only programs I would use to do restores other than Baywolfs AIO which is very friendly and has the JFD Rom in it and the Mapping Pit file known as the 512.
You could also use Eugenes No brick Froyo using Odin which has the 2E update file in it, so when you root it and Flash CW recovery, and then re-install packages it will give you the 2E green recovery menu you'll need to successfully flash other ROMS in the future you want.
Click to expand...
Click to collapse
Wow, didn't know this. Will delete kies asap. btw, this rom that i've flashed has a custom kernel (bionix? + voodoo). i did a backup of the stock rom via recovery. do i need to flash the stock kernel first before rolling back to stock?
hereeny said:
Theres a GB ROM out by Hercules that is a Galaxy S II port...its pretty sweet
Click to expand...
Click to collapse
thank you, will check it out!
Project-V is a Great 2.2 ROM, I made a few themes for it too: Blar and WP7 Style

[Q] rom manager not recognizing fascinate

This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
lucash312 said:
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
rom manager is useless for the fascinate...
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
MultipleMonomials said:
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
Click to expand...
Click to collapse
if the op would of followed the guides instructions correctly, he would not of ran into that issue in the first place...
droidstyle said:
rom manager is useless for the fascinate...
Click to expand...
Click to collapse
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
You can flash any .zip ROM with CWM. There's no need for ROM Manager. BTW, you can post a link if you uncheck "parse links in text automatically."
Nymblz said:
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
Click to expand...
Click to collapse
all you need to do is boot into cwm recovery via the power menu and flash away. the problem with rom manager on the fascinate is getting into the right recovery...causes more problems than its worth on this device. make sense yet? probably not since you have not been down this road yet, but many of us have. so take the advice given or dont and learn the hard way.
Honestly, I am trying to take the advice given but not all of it fit my situation.
I'm definitely something of a noob to Android (Not to linux or IT though). I've had my phone for all of a month and rooted it only days ago.
It's all starting to come together, finally. It's tricky for a noob because there are so many different versions of the phone hardware, versions of Android, this or that kernel that only works with these ROMs, old/newer versions of those, old posts and advice, newer posts with adjusted advice.. etc.. It's been a week long crash course!
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
So you see, I was in a catch-22; I needed CWM to flash CWM? Odin was my only option at that point.
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Nymblz said:
It's tricky for a noob because there are so many different versions of the phone hardware
Click to expand...
Click to collapse
You are on the Samsung Fascinate. If it is Verizon then it is model number i500. If it doesnt say Fascinate or i500 it isn't for your device and you don't need to worry about it. If you flash something that isn't stated as being for the i500 or VERIZON Fascinate then you will have a lovely new temporary paper weight.
Nymblz said:
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
Click to expand...
Click to collapse
You couldn't have followed it to the letter because it is a well known fact that if you boot up with a stock kernel still flashed it will replace your recovery. Droidstyle certainly knows this and certainly accounted for it in his guide. So, you need to either boot directly into CWM or flash a non-stock kernel prior to rebooting the phone.
Nymblz said:
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Click to expand...
Click to collapse
Yeah it sounds like that will work...not the most elegant way to take care of it...but it sounds like it would be okay.
Nymblz said:
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
Click to expand...
Click to collapse
We already talked about the kernel situation. Consider Geewiz if you want something thats all-in-one and pretty much impossible to mess up. KGB is good. Leankernel always gave me the best battery life but YMMV.
Nymblz said:
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Click to expand...
Click to collapse
He showed no interest in helping the devs here get ROM manager working (again) on the phone. If you gave him money, blame him for not providing the support and resources to get it working on this phone. Some people are umm...."lacking in people skills."
Oh, and as great as the Gingerbread ROMs are...the mtd ICS roms blow them out of the water

Categories

Resources