Birgertime has done a great job getting EDT ROMs available via Rom Manager (I may have bugged him a couple of times). I was a bit shocked when I was reading the thread and saw people were having issues when they updated using Rom Manager. I think the consensus was that Rom Manager was not properly wiping.
This is what I did:
I was on Trigger 2.9.3 *I try every ROM and I just felt like being old school.
I opened Rom Manager and downloaded the latest Trigger 3.2,
I used the KB1 Modem, KB5 kernel, I selected a few of the apps I wanted (bloater, titanium, maybe a couple others)
I told Rom Manger to wipe and do a backup by clicking the two boxes.
Once the download was completed I proceeded.
It went into CWR and it did a backup... immediately it did a wipe (it showed the steps in CWR like normal)... and then it flashed the ROM and it rebooted perfectly. I have had NO issues with the ROM. It's perfect in my opinion.
What I want to know, for those who had issues... what was different?
Did you get rebooted into the red voodoo recovery (I was at the normal CWR)? I don't understand how it can work perfectly for me, and not others. I would like to know exactly what went wrong so we can go to @koush and try and get both Rom Manager and Clockwork Recovery working better for us.
Between this, Fix Permissions, Partitions F'ing people, stats not working (for the dev's) I think our phone needs this amazing app to be better, and I know koush can do it.
** If there are other things wrong with Rom Manager/CWR, please post... it would be nice to have a list of things to work on.
I can put up a test version on rom manager. The current Trigger 3.2 up there will wipe regardless of what you tell ROM manager.
PS: who rated it 1 star?
birgertime said:
PS: who rated it 1 star?
Click to expand...
Click to collapse
Team Whiskey
EDIT, were you going to fix the prop so it showed 3.2, not 3.1? =)
Im confused. You said you used CWR to wipe and flash the ROM. What exactly did you use ROM Manager for?
s15274n said:
Team Whiskey
EDIT, were you going to fix the prop so it showed 3.2, not 3.1? =)
Click to expand...
Click to collapse
I think I did when I uploaded the vvm fixed version
androidmonkey said:
Im confused. You said you used CWR to wipe and flash the ROM. What exactly did you use ROM Manager for?
Click to expand...
Click to collapse
To download it
Sent from my SGH-T959 using XDA App
duboi97 said:
To download it
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Ah, ok. I dont see why downloading it with RomManager would make a difference, unless its not completely downloading. The safest is like birgertime says in the Trigger thread, download on PC and check Hash.
androidmonkey said:
Ah, ok. I dont see why downloading it with RomManager would make a difference, unless its not completely downloading. The safest is like birgertime says in the Trigger thread, download on PC and check Hash.
Click to expand...
Click to collapse
Rom Manager is the most convenient way to do this. it also checks the MD5 before it flashes the ROM. Trust me when I say I know the process...
I just want to know from those who had issues with using Rom Manager to download/wipe/flash, what went wrong?
I flashed it using Rom manager.
I chose KB5 modem and KB5 Kernel.
along with things like Bloater and swype.
it rebooted into red recovery and seemed to go fine from there.
when it first booted up it seemed ok at first, I let it sit for a while like usual.
and then rom manager force closed.
from there it was just force close after force close.
So I rebooted back into recovery and wiped data and dalvik.
then I rebooted.
and everything works just fine, with the exception of it never installed any of the extras I chose (swype,Bloater, etc...)
but I had those in titanium backup just in case anyways so it wasn't a big deal.
Its been running beautifully ever since.
Pretty much same thing happened to me, it went to red recovery and seemed to flash just fine. then when it rebooted i kept getting force closes everywhere. rebooted to clear cahce, dalvik, and fix permissions and has been fine ever since. it didnt wipe my apps which i found a bit odd
Alright, so as I expected... it sounds like it was
THE RED VOODOO RECOVERY AS THE PROBLEM.
Anyone able to prove that wrong?
I mean, it makes sense, it's not the recovery Rom Manager expects to see.
So, how do we fix it? This would not be koush now, I do not think.
Where did the red voodoo recovery initiate? I remember it just showed up one day. was it supercurio?
Related
So the current iterations of cwm seem to have trouble working reliably with the newer froyo ROMs, and koush's recovery (although seeming to work correctly) is quite broken. So......
please find below a new recovery package that should work for any ROM for the fascinate, mesmerize, or showcase.
This is a "red" cwm recovery, and it will work with both voodoo and non-voodoo installations.
cwm-recovery-ALL.zip can be flashed via any cwm recovery.
if you are using odin, then use the cwm-recovery-ALL odin (.tar) package.
updated 3/29 - thanks to GizmoDroid for help with fixing fix_permissions script and root permissions typo that screwed up nandroid restores
updated 3/30 - fixed 'umount' typo - actually *fixed* fix_permissions this time - fixed odin/heimdall recovery attachment
Thanks, I just installed it. I'd rather not have a broken clockwork mod.
thanks, will give this a try!
ok, so I flashed this in the old cwm and it does come up red, but also says CwM Voodoo Lagfix Recovery, is that right?
In what ways is the old cm broken with froyo? I haven't noticed any problems.
Thanks! Good to have a fully working recovery again.
renf said:
In what ways is the old cm broken with froyo? I haven't noticed any problems.
Click to expand...
Click to collapse
Yeah, I'd like to 2nd this question. I have DL30 and CW worked for me in setting that up. Granted, I haven't tried anything else after that, but I'd like to know too.
Well I've had weird things happen when flashing stuff (I was using the "new-cwm.zip") , seemed like data being written where it shouldn't be? Just flashing theme files or own stuff I want to add, and I've had the following stuff happen:
Nuked my radio, had an unknown baseband and calls would never work, fortunately Radio Odin fixed it.
Had some /data apps disappear. Had some /data/data disappear. On reboot had Setup Wizard pop-up, even though I still had my Google account registered.
Hoping this new clockwork is completely safe. I suspected that clockwork was responsible for my weird happenings, so data-wiped and haven't flashed anything, so far fine functioning.
Using this is it easy to flash back to a prior set up, for me it would be back to dj05 w superdark and voodoo5?
Ive been holding off on froyo bc I need wireless tether, preferably unreported tether. But I really want to play around and see what the fuss is about. Ive downloaded every dl30 rom, havent installed one fearing I cant go back easily
Sent from my SCH-I500 using XDA App
/data on the fascinate is on /dev/block/mmcblk0p1
koush's recovery mounts /data as mmcblk0p2 (THIS IS OUR /DATA/FOTA. THAT'S BAAADDD)
under most circumstances this does not matter , because recovery.rc mounts data CORRECTLY before cwm gets to it, but there are circumstances where /data can be unmounted and then remounted, in which case cwm is gonna mount mmcblk0p2. If things get written there, at best you've got a **** load of FC's to deal with. At worst, a dead radio.
I've pointed this out to koush before, but was met with a "half-response", and to date it not been addressed (except for the recoveries that I've posted)
installed. When I go to do a backup, it gives the messages below. Backup seems to run fine though
E: missing bitmap progress_empty (code -1)
E: missing bitmap progress_fill (code -1)
Click to expand...
Click to collapse
Thanks, jt.
Copied to sdcard, booted into recovery, ran the program, keep coming back to green, no red.
ETA: Interesting. If I go to recovery from ROM mgr and try to load from sdcard, it does nothing, but if (while in ROM Mgr) I load from SDcard, it works. Got the blue screen, ran update, red appeared.
I likewise get the error message mentioned previously, but got it at install. Backup seemed to ahve run fine.
Installed like a charm, thanks jt!
sent from my fascinating XDA App
jackmei2 said:
thanks, will give this a try!
ok, so I flashed this in the old cwm and it does come up red, but also says CwM Voodoo Lagfix Recovery, is that right?
Click to expand...
Click to collapse
Yes, that is correct. It says in the OP. But it may have been edited since the time you posted and my response, so I'll let it slide
thank you JT!!!!! I thought it was just me, Ive had to start over again with my data about 6 times now becuase of Clockwork either not restoring my backups or my phone freaking out once I restored the backup. Thanks again!!!
beenz said:
Yes, that is correct. It says in the OP. But it may have been edited since the time you posted and my response, so I'll let it slide
Click to expand...
Click to collapse
haha thanks... but he said it will be red and that it is not for voodoo, so that's what I wanted to double check since it does have the voodoo menus and all.
superchunkwii said:
Yeah, I'd like to 2nd this question. I have DL30 and CW worked for me in setting that up. Granted, I haven't tried anything else after that, but I'd like to know too.
Click to expand...
Click to collapse
Lets see:
Broken mass storage function.
Broken data mounting function.
Couldn't wipe properly because of the above.
adrynalyne said:
Lets see:
Broken mass storage function.
Broken data mounting function.
Couldn't wipe properly because of the above.
Click to expand...
Click to collapse
The couldn't wipe properly bit me once already. Glad to have a proper recovery.
Sent from my SCH-I500 using XDA App
Thanks very much for addressing this issue.
For a while, I felt like a fresh n00blet, wondering what I was doing wrong. I tried flashing versions of supposedly compatible cwm's in different ways, always coming to the mounting errors.
Other than the errors from the missing graphics, this one works error free.
Scared to mess with this since i haven't experienced any problems with my current cwm stuff from pre dl09... Might just go ahead and do this tomorrow. For some reason I feel more comfortable using the odin method, so I can do all this over my Super Clean 1.0 with Neon GT theme and not have to do any data wiping or anything first?
So this makes no sense and I think its a weird coincident but as soon as I flashed this my beta version of swype started the force close loop..
EDIT: so weird, I had to uninstall the installer and swype itself using titanium backup and then download the installer and install again (had to do it all twice). Seems to be working again now tho..
Superclean 0.7.. aka Froyo.. Thanks devs!
I installed BAMF 1.6.3 remix and I noticed that I don't have some of the features that were listed in his OP.
For ex. I still have my location icon in my status bar, when I press on the themed rosie button on the right it still opens up the personalize settings no matter what icon I chose to put there. I don't have the 6 bar signal strength. I don't have the power control settings in my pull down menu, but I do have the power control settings apk in my drawer. Don't have widget picker, Don't have the extra power options when the power button is pressed, reboot, hibernate, etc.... Also when a call is missed it doesn't show the number in my pulldown menu only that I had 3 missed calles from*86 and something about CDMA on the missed call icon.
These are the few that I noticed in the couple hours of it being on my phone. I am just wondering if this is normal or what I may have did wrong and how to get these working as I thought they were part of the ROM itself.
Thanks
Did you flash the rom in rom manager??? If so, thats most likely what created the missing issues.
You have to flash the rom thru CWR for you to get everything up and running fully.
Yeah I downloaded from the forum then installed using ROM manager. I will re-install using CWR. I will post my results. Thanks for the quick response. Oh yeah I noticed my post was at like 1:34 am? It's only 8:47 where im at?
So I re-flashed the ROm and everything seems to be like it should. I wonder why the differnece from Rom Mgr? It's not like I downloaded the file through RM, And It flashed using CWM? Oh well, I will know from now on to flash manually. I don't have the paid version, but if you can't fully flash a rom then what's the point of having/paying for Rom Mgr?
MomentFreak said:
Yeah I downloaded from the forum then installed using ROM manager. I will re-install using CWR. I will post my results. Thanks for the quick response. Oh yeah I noticed my post was at like 1:34 am? It's only 8:47 where im at?
So I re-flashed the ROm and everything seems to be like it should. I wonder why the differnece from Rom Mgr? It's not like I downloaded the file through RM, And It flashed using CWM? Oh well, I will know from now on to flash manually. I don't have the paid version, but if you can't fully flash a rom then what's the point of having/paying for Rom Mgr?
Click to expand...
Click to collapse
Sometimes it works, sometimes it doesn't. Full blown roms I will always try to do in CWR from now on. If its something small like a theme or extra or add on, Rom Manager usually works well.
Glad the reflash worked well thru CWR.
New here , just wanted to ask under this post.
Kind of the same topic.
I came from the dx used droidx bootstrap and dx2 bootstrap.
New the the TB I seen some post saying Rom manager.
So I installed Bamf 1.6 and 1.6.3 remix from Rom manager.
But I hit the flash Rom manager button, success.
Then hit boot into recovery.
Is that what you guys mean when you type. CWR.
Checking to make sure I am doing it correct.
Thank you
tanium said:
New here , just wanted to ask under this post.
Kind of the same topic.
I came from the dx used droidx bootstrap and dx2 bootstrap.
New the the TB I seen some post saying Rom manager.
So I installed Bamf 1.6 and 1.6.3 remix from Rom manager.
But I hit the flash Rom manager button, success.
Then hit boot into recovery.
Is that what you guys mean when you type. CWR.
Checking to make sure I am doing it correct.
Thank you
Click to expand...
Click to collapse
Well you need Rom Manager to Install CWR which stands for ClockworkMod Recovery, Which is where you can make what they call Nandroid backups, which is a backup of your current system and setup including apps and data. So it's always good do backup before making any changes ex, flashing rom's. But there are many things you can do with it and to me is one of the most important parts of having a rooted phone is having recovery. Hope this clears some stuff up.
Yes thank you.
But this is all done from inside Rom manager correct.
I mean I open Rom manager and clicked boot into recovery.
This is how I flashed Bamf 1.6 remix.
I installed no other program or app to get recovery.
Yes I see now , went and looked.
I was following instructions before.
I had to hit flash clockworkrecovery.
That is what installed that I guess.
See learning all the time.
I used droidx bootstrap before never new Rom manager was so cool.
That guy rocks.
I also had this problem. Installing from Rom manager doesn't seem to be enough. You seem to need to boot into recovery and install it manually from cwr.
Sent from my Verizon Wireless 4G LTE Thunderbolt
Definitely noticed that things can come up missing unless you wipe all three Data/Davlik/Cache and use clockwork to do it all. For some reason just flashing and wiping using ROM manager doesnt cut it.
I don't know if you guys are aware of this but evertime I flash something its been with Rom manager. I got very sick of killing WiFi so I started all over again with BAMF beta 5 and flashed the few fixes and a new kernel. Same as I always did but this time I only used recovery and it worked. Haven't killed WiFi at all. Tried a bunch of times and still good to go. Also this only applies to GINGERBREAD ROMS!
Sent from a cellular telephone
You mean flash in recovery?
I had a similar experience but I think it was a coincidence.
Sent from my ADR6400L using XDA App
You should always flash through recovery... ROM manager likes to break things. Glad you got it working though.
yeah. Flash in recovery.. and I don't think its a coincidence. But who knows. Been working great this way
Sent from a cellular telephone
bking_soda said:
You should always flash through recovery... ROM manager likes to break things. Glad you got it working though.
Click to expand...
Click to collapse
Yeah. Ha. I guess so. I'm never using Rom manager again. Lol
Sent from a cellular telephone
I usually flash in recovery because my old OG Droid didn't like rebooting into recovery from ROM Manager. My T-bolt doesn't seem to have that issue and any time I have used Rom Manager to flash several zips at once, usually multiple patches or whatnot, I haven't had any issues. I have yet to flash an entire ROM in ROM Manager though.
So are you saying that ROM Manager is good for nothing but flashing the recovery image and getting CM7 Nightlies when they come out?
I knew I shouldn't have paid for it!
I flashed the bamf2 beta 5 update with ROM manager and my WiFi got messed up. I read this thread, rebooted into recovery, wiped cache and reflashed bamf2 beta 5. Wifi now works
Sent from my ADR6400L using XDA App
Uh ok lol
Sent from my ADR6400L using XDA Premium App
So has anyone let Koush know so he could look into this issue?
rom manager = junk for gingerbread roms i guess. it was amazing on froyo though, maybe they will update
RM updated to 4.2.2.0
CWR updated to 3.1.0.1
Had the same problem with flashing from rom manager. I do not use it anymore
ROM Manager
I was addicted to ROM Manager on my D1, even with Gingerbread ROMS (CM7). I haven't really used it for ROM installation on the Thunderbolt though. I paid for it on the Android Market and have absolutely no regrets, and as the ROMS mature for the Thunderbolt, so will the means for installing them.
Flash away I say.
Used it to flash BAMF 1.6.3 Remix, worked great.
i used it for das bamf 1.6.3 remix and had issues through rom manager. When i flashed through recovery everything went smoothe as butter. This time things were debloated.
tegan_ca said:
Used it to flash BAMF 1.6.3 Remix, worked great.
Click to expand...
Click to collapse
I had problems using it to flash remix, had to use recovery to get it to work correctly. It seemed like it wasn't fully wiping the cache/data before the flash, whereas recovery did.
Newb here, is it possible to download through RM but not trigger the auto-flash-sequence? Every time I d/l something through RM it tries to flash immediately after downloading.
tegan_ca said:
Used it to flash BAMF 1.6.3 Remix, worked great.
Click to expand...
Click to collapse
I had problems using it to flash remix, had to use recovery to get it to work correctly. It seemed like it wasn't fully wiping the cache/data before the flash, whereas recovery did.
My D1 never did like RM or CWM. And its nands were huge. I haven't rooted my Bolt yet... need to get around to that, I desperately miss Titanium and Root Explorer.
I'm running UnNamed 1.3.0 right now with no themes applied but I have everything setup the way I like it. I'd like to do a full 1.3.1 flash and try the Blue Monkey theme.
Is the best way to do this
A) backup apps with Titanium, backup with CWM, full wipe, flash 1.3.1 full, then flash blue monkey, restore apps with Titanium
B) backup with CWM, flash 1.3.1 over 1.3, then flash blue monkey theme
C) other
I'm unclear on whether I need to do a wipe going from 1.3 to 1.3.1 if it's a full flash and not the 1.3to1.3.1 update.
Thanks in advance for any help.
dont need to wipe. just flash it.
You can wipe cache and dalvik to clean up, but you don't need to wipe.
Alright, I did a backup then installed 1.3.1 and rebooted. Everything works fine and the phone looks exactly how I left it except in the about phone area it says I'm running 1.3.1 now.
Rebooted and backed up again.
Installed from zip the Blue Monkey theme and rebooted. I'm running Go Launcher Ex so I went in and cleared it as the default. Pressed the home button and chose TwLauncher. Everything looks fine but I'm not seeing the theme applied. I still have the same background live wallpaper and icons. The lock screen is still WidgetLocker.
Thoughts?
EDIT:
Apparently installing the theme a second time did the trick. I now see the new icons.
Knips178 said:
EDIT:
Apparently installing the theme a second time did the trick. I now see the new icons.
Click to expand...
Click to collapse
Right on. That's good advice for everyone. Sometimes things need more than one flash.
Sent from my páhhōniē
I had the same thing happen with that theme on 1.3.1. I knew something was up when it flashed really fast. A second flash took longer and worked properly.
Sent from my SAMSUNG-SGH-I777 using xda premium
Can anyone give a quick reply as to why that happens with flashing? Is it a problem with CWM, the zip files, or the process?
Knips178 said:
Can anyone give a quick reply as to why that happens with flashing? Is it a problem with CWM, the zip files, or the process?
Click to expand...
Click to collapse
Lol, I think alot of us wish we knew why. I don't think anyone has figured it out. It's not limited to our phone.
Sent from my páhhōniē
gr8hairy1 said:
Lol, I think alot of us wish we knew why. I don't think anyone has figured it out. It's not limited to our phone.
Sent from my páhhōniē
Click to expand...
Click to collapse
I think I have posted this twice today and the third time might...be the charm. You guys have to remember to check and mount your system and data in recovery before flashing ROM's or Themes. It should alleviate any re-flashing or multi-flash scenarios for you guys.
Additional: Also if some of you guys are having a bad or fast install you might want to re-download the Theme. I know in talking with Jivy26 (Blue Monkey Themer) the initial release of the update of 1.3 (For you quick and early adopters) had an issue and was pulled, repacked and posted again. Try a fresh copy.
hkeyman said:
I think I have posted this twice today and the third time might...be the charm. You guys have to remember to check and mount your system and data in recovery before flashing ROM's or Themes. It should alleviate any re-flashing or multi-flash scenarios for you guys.
Click to expand...
Click to collapse
Very true. But it's still only a 'should' not have to flash twice, not a certainty that it won't need the flash again.
It doesn't explain the times we do that and it still needs a reflash (usually cm7).
Sent from my páhhōniē
gr8hairy1 said:
Very true. But it's still only a 'should' not have to flash twice, not a certainty that it won't need the flash again.
It doesn't explain the times we do that and it still needs a reflash (usually cm7).
Sent from my páhhōniē
Click to expand...
Click to collapse
I used to see the same thing with flashing multiple times, thought it might have been a bad root install or something wrong with the ROM itself. Ever since implementing the mentioned procedure into my regimen of updates. I only flash once (Unless of course there is in fact something wrong with the package).
Hey, everyone. I've been having this problem a lot... when I was on CM7, about once a month everything would force close. First an app (xScope, Twicca, anything), then GApps, then my keyboard... the phone starts FCing everything within about an hour of being turned on. In the past, I've just fully wiped the phone... I'm on Pool Party now (the version before the newest one right now), and everything is FCing again. Is there a solution that isn't just "wipe everything?"
Did you make any drastic changes before it started force closing everything or has it been that way since you flashed the new ROM? Or was your ROM working fine in the past and it mystically started happening
Sent from my SCH-I500 using XDA App
This just mystically started today. It's been about a month and a half since the last time this happened, on CM7.
My phone got all screwed up one time when I installed either a bad gapps zip or the wrong one and I ended up having to wipe everything and start over to get out of that mess, although it's weird it randomly is happening to you.
I highly recommend the new ics roms
Sent from my SCH-I500 using XDA App
kadin.zimmerman said:
My phone got all screwed up one time when I installed either a bad gapps zip or the wrong one and I ended up having to wipe everything and start over to get out of that mess, although it's weird it randomly is happening to you.
I highly recommend the new ics roms
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
@OP... I installed TSM Pool Party, flashed gapps for CM7, [big mistake???] and then today everything FC. Couldn't load my browser, only ADWlauncher and perhaps a few other apps I tried worked.
I tried flashing the correct gapps, not sure if it fixed it, rebooting now. if not I will have to reflash tsm pool party.
@above poster, where is this new ICS fascinate rom? Is it stable?
GApps is GApps, man. Wondering if it's a sync issue...
mvmacd said:
@OP... I installed TSM Pool Party, flashed gapps for CM7, [big mistake???] and then today everything FC. Couldn't load my browser, only ADWlauncher and perhaps a few other apps I tried worked.
I tried flashing the correct gapps, not sure if it fixed it, rebooting now. if not I will have to reflash tsm pool party.
@above poster, where is this new ICS fascinate rom? Is it stable?
Click to expand...
Click to collapse
Yeah the ics ROM is very stable, I love it. Go to Google and type in "rootzwiki fascinate ics build 6" and you should find it on the rootzwiki website. Let me know if you end up using it and if you like it or even if you need help...I have encountered most problems people have had so I experienced them first hand lol
Sent from my SCH-I500 using XDA App
Gonna boot my phone up for the first time in 24 hours, maybe it's calmed down. I'd love to switch to ICS, but this isn't solving my "I don't want to wipe everything AGAIN" ordeal.
obsidianchao said:
Gonna boot my phone up for the first time in 24 hours, maybe it's calmed down. I'd love to switch to ICS, but this isn't solving my "I don't want to wipe everything AGAIN" ordeal.
Click to expand...
Click to collapse
Yeah I understand you on that...makes you sick to your stomach when you lose everything. Did you not have any backups of when your phone was in its working state? Backups are one of the most important things in my opinion. I learned the hard way
Sent from my SCH-I500 using XDA App
I haven't done a proper backup in a while. I should really start doing that, sigh.
obsidianchao said:
I haven't done a proper backup in a while. I should really start doing that, sigh.
Click to expand...
Click to collapse
boot into cwm and wipe cacnhe and dalvik. I normally do this once a week. Also if you have alot of apps downloaded to the internal memory this can happen. Check rootzwiki out for a thread about fixing the datadata force close issues.
http://rootzwiki.com/topic/5635-problems-with-datadata-causing-force-closes-for-google-apps/
Ahhh, thank you so much, this is perfect!
kadin.zimmerman said:
Yeah the ics ROM is very stable, I love it. Go to Google and type in "rootzwiki fascinate ics build 6" and you should find it on the rootzwiki website. Let me know if you end up using it and if you like it or even if you need help...I have encountered most problems people have had so I experienced them first hand lol
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Ah nice. I was hoping to see a stable ICS. So, it says there's no video hardware acceleration.. does that mean future updates will bring hardware acceleration for the fasciante? like h264 mkv's, or h264 mp4's, or even mpeg4 avi's? tsm/jt's rom doesn't have good video hardware support, MX video has to use SW almost all the time.
So I think I would like to check it out, but I wish I knew about it before I went through all the trouble last night to reflash and reinstall all my apps.. [was up till 3am working on it] lol
any major troubles with it? Also what CWM do I use? Perhaps the one on the CM7 fascinate wiki? [cwm4-bml-i500.tar] or the cwm 5.0.2.7 in vanilla gb?
Also do I need to odin it to anything? or can I go from what I've got now [tsm pool party]?
I've had no major troubles with the past 2 builds and definitely build 6 is the best. Not exactly sure what is meant by the hardware acceleration but everything about this ROM runs smooth. As for cwm version, just install any cwm and the ics ROM has its own that it will install. Once it installs it's own, it is recommended to not flash a new kernel once it does it's own because the one it puts on has stuff built in to make all the features work.
As for Odin, hmm....too be safe I would go back to stock and then throw a cwm kernel on. Then do a wipe data + cache and install build 5. Make sure it is running good then just clear cache and install build 6
Do a backup before you start all this just to be safe!!
Sent from my SCH-I500 using XDA App
kadin.zimmerman said:
As for Odin, hmm....too be safe I would go back to stock and then throw a cwm kernel on. Then do a wipe data + cache and install build 5. Make sure it is running good then just clear cache and install build 6
Do a backup before you start all this just to be safe!!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Ok so how come I should install build 5 first?
mvmacd said:
Ok so how come I should install build 5 first?
Click to expand...
Click to collapse
I'm not sure if you have to or not, probably don't actually I'm not sure why I said that lol...I guess in my situation I had troubles along the way so I started at build 3 and worked my way up.
just go straight to build 6 and in that case wipe data and cache. And I still would go to stock first because I read somewhere that it best to go from the bml based versions to mtd.
I would then update your radio to EH03 if it isn't already
Sent from my SCH-I500 using XDA App
kadin.zimmerman said:
I'm not sure if you have to or not, probably don't actually I'm not sure why I said that lol...I guess in my situation I had troubles along the way so I started at build 3 and worked my way up.
just go straight to build 6 and in that case wipe data and cache. And I still would go to stock first because I read somewhere that it best to go from the bml based versions to mtd.
I would then update your radio to EH03 if it isn't already
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
awesome... yes I was planning on Odin'ing again, because I've found it gives the rom you flash after it better chance of survival.
It is a inconvenience though because I have to boot up W7 [Dual boot Linux] every time I wanna Odin.. haha, same thing back when I used my ipod touch for iTunes.
So what radio does the ics build 6 have? can they not use the eh03 radio [I'm assuming is superior to whatever it has]? And I assume heimdall can flash the "modem.bin" radio that I untar from the "CI500_VZW_EH03_GB_CM.tar.md5" like so:
heimdall flash --modem modem.bin
right?
The ics builds don't have a specific radio, it doesnt mess with the radio you currently have, so whatever radio you have now is what you will have after the rom. I just didn't know what radio you had now, and the reason i recommend the EH03 is because it is the newest stock radio from verizon - meaning it is definitely reliable.
I'm not sure what you mean by untaring the .tar file. Odin uses the .tar file, so do not untar the file, just leave it the way it is. Unless you mean you can specifically take the radio.tar file out from the other tar file. I have the EH03_radio.tar file so if you wanted it i could upload it somewhere and give you the link. Odin back to any stock firmware, then load a cwm recovery as well as the EH03 radio.
EDIT: Here you go http://dl.dropbox.com/u/32493357/eh03_radio.tar.md5
kadin.zimmerman said:
The ics builds don't have a specific radio, it doesnt mess with the radio you currently have, so whatever radio you have now is what you will have after the rom. I just didn't know what radio you had now, and the reason i recommend the EH03 is because it is the newest stock radio from verizon - meaning it is definitely reliable.
I'm not sure what you mean by untaring the .tar file. Odin uses the .tar file, so do not untar the file, just leave it the way it is. Unless you mean you can specifically take the radio.tar file out from the other tar file. I have the EH03_radio.tar file so if you wanted it i could upload it somewhere and give you the link. Odin back to any stock firmware, then load a cwm recovery as well as the EH03 radio.
EDIT: Here you go http://dl.dropbox.com/u/32493357/eh03_radio.tar.md5
Click to expand...
Click to collapse
sorry... what I meant is, I know how to extract the EH03 modem.bin file out of the ".tar.md5" file for the stock Verizon eh03 firmware.
I know how to flash CWM with heimdall, but I guess I do not need to flash the radio [ right? ] because I just came from a fresh eh03, completely wiped, cache, dalvik, and..... urmm, it is showing the same animation I had back on "Eclipse ROM" for Droid X2... ew... For some reason I do not like that particular animation. I guess you can change the boot animation though?
mvmacd said:
sorry... what I meant is, I know how to extract the EH03 modem.bin file out of the ".tar.md5" file for the stock Verizon eh03 firmware.
I know how to flash CWM with heimdall, but I guess I do not need to flash the radio [ right? ] because I just came from a fresh eh03, completely wiped, cache, dalvik, and..... urmm, it is showing the same animation I had back on "Eclipse ROM" for Droid X2... ew... For some reason I do not like that particular animation. I guess you can change the boot animation though?
Click to expand...
Click to collapse
Use the program "odin" to flash all your .tar.md5 files. You don't extract those files, you leave them in the .tar format. I gave you the link to download specifically the eh03 radio, but if you have it already on your phone you dont need to worry about it. As for the boot animation, the ics rom will install its own boot animation so no worries there.
You know about odin right? It is definitely the easiest way to flash kernels, radios, and stock firmware.