[ROM][5.07.2011][ED01]Community Rom V1.3

[iLogikk]

ComRom is voodoo, but will do the lagfix for you. The newest CWM can be found right here:

[RECOVERY][ODIN][ZIP][4.22.11]Voodoo CWM 3.x UPDATED 5.8.11 - xda-developers

It's a version newer Than the cwm recovery all, which is the one you were referring to and have in that list you sent me. (so you can get rid of that one too...)

I actually downloaded the first file on that page (CWM3_Voodoo.tar.md5). I flashed it via odin but it only boots into CWM once. Is this correct? The other version of "all" that I had would always boot into CWM. Is this intentionally done (not booting into it each time)?

 

[Landshark]

I actually downloaded the first file on that page (CWM3_Voodoo.tar.md5). I flashed it via odin but it only boots into CWM once. Is this correct? The other version of "all" that I had would always boot into CWM. Is this intentionally done (not booting into it each time)?

which ROM are you running and which kernel do you have? If you have a stock kernel at all it doesn't matter which recovery you flash, it will not stick once you boot into the ROM with a stock kernel. Also, how are you booting into recovery that you are not booting directly to CWM?

 

[iLogikk]

which ROM are you running and which kernel do you have? If you have a stock kernel at all it doesn't matter which recovery you flash, it will not stick once you boot into the ROM with a stock kernel. Also, how are you booting into recovery that you are not booting directly to CWM?

Ohhh...nevermind. I think I realize why. I booted to cwm and wiped both cache and delv. Then I realized I didn't have 1.3 comrom on my sdcard so I had to power up and add it. Then when I got ready to boot back into cwm it wasn't there. So the file is now on my sdcard so I'm about to flash cwm-voodoo then the 1.3 comrom. Then from then on I figure the cwm will be there.

 

[Landshark]

Ohhh...nevermind. I think I realize why. I booted to cwm and wiped both cache and delv. Then I realized I didn't have 1.3 comrom on my sdcard so I had to power up and add it. Then when I got ready to boot back into cwm it wasn't there. So the file is now on my sdcard so I'm about to flash cwm-voodoo then the 1.3 comrom. Then from then on I figure the cwm will be there.

Yep, you will be good to go at that point.

 

[Sabban]

Why is it when u try to paste a web address in the comm rom 1.3 browser it only gives me the 'share or copy url' option? I loaded tge browser patch but that didnt help? Any thoughts, other wise it gonna try flaxging the browser from 1.0/1.2 comm rom
Thanks

 

[Lttlwing16]

I got myself to CR 1.3 after flashing EC01 via Odin - did a full factory wipe - wiped caches - flashed CR 1.3 and for the most part I am thrilled. However, I have been having intermittent FCs and crash/reboots.

I did restore my apps + app data via Titanium - is this likely the cause of my problems? If so I'll back out and start over and wipe and restore no app data. In fact it's probably what I'll do just to be safe. I guess I'm just in denial, but stability is worth losing saved games and having to set every app up again ..

Out of curiosity I've heard some have had issues with Launcher Pro+ and the 1.3 browser. I have the patch, but afaik the crashes are not browser related. What are the symptoms of the LP+/Browser issue? (I read about the person who had issues with the bookmarks widget, but I don't use that). Thanks.

You've got the right idea ICU...for me, restoring app data was a FC circus.. I went back and repeated the process sans app data and BOOM.. no problems.

If you do repeat the process let us know if it clears up your ills.

As far as LP+ I would not restore from backup, but redownload from the market.

Something else to consider is not restoring apps2sd from backup, if your using that...it begins wanting to store the apps2sd as the restore is in process and can cause problems. I always just re-download from the market to avoid that problem.

let us know how it goes!

 

[BrokenLinux]

So going from 1.2 to 1.3, is it reccomended to do a full data wipe, or just a cache and dalvik clear?

 

[Lttlwing16]

So going from 1.2 to 1.3, is it reccomended to do a full data wipe, or just a cache and dalvik clear?

The safest bet is to wipe cache's, wipe data, flash rom, wipe data..reboot.

 

[Heath276]

Hey can y'all look at this and tell me if it is right I'm on 1.3

Hardware version
I500.04

Model number
SCH.I500

Firmware version
2.2.1

Baseband version
S:i500.04 V ED01

Kernal version
2.6.32.9

Build number
SCH-I500.ED01

Sent from my SCH-I500 using Tapatalk

 

[wyllic]

Hey can y'all look at this and tell me if it is right I'm on 1.3

Hardware version
I500.04

Model number
SCH.I500

Firmware version
2.2.1

Baseband version
S:i500.04 V ED01

Kernal version
2.6.32.9

Build number
SCH-I500.ED01

Sent from my SCH-I500 using Tapatalk

Looks fine to me, what are you curious about exactly?

Sent from my SCH-I500 using Tapatalk

 

[Heath276]

Looks fine to me, what are you curious about exactly?

Sent from my SCH-I500 using Tapatalk

The firmware only says 2.2.1 I see others put after that com Rom 1.3 or something

Sent from my SCH-I500 using Tapatalk

 

[Kevin Gossett]

The build.prop (which is what you're showing there) will only show basic information about your device (SCH-i500), firmware (2.2.1), kernal (2.6.32.9), baseband (ED01), and build (ED01). the build.prop can be edited to show almost anything, but wasn't done so on the ComROM

 

[Heath276]

The build.prop (which is what you're showing there) will only show basic information about your device (SCH-i500), firmware (2.2.1), kernal (2.6.32.9), baseband (ED01), and build (ED01). the build.prop can be edited to show almost anything, but wasn't done so on the ComROM

Ok thanks it all works good just wanted to make sure I was up to date with it all.

Sent from my SCH-I500 using Tapatalk

 

[wyllic]

The firmware only says 2.2.1 I see others put after that com Rom 1.3 or something

Sent from my SCH-I500 using Tapatalk

Well the comrom is running on the 2.2.1 firmware, so what you have is correct

Sent from my SCH-I500 using Tapatalk

 

[wyllic]

The build.prop (which is what you're showing there) will only show basic information about your device (SCH-i500), firmware (2.2.1), kernal (2.6.32.9), baseband (ED01), and build (ED01). the build.prop can be edited to show almost anything, but wasn't done so on the ComROM

I totally want to edit it to show a bunch of random stuff, that would be amusing

Sent from my SCH-I500 using Tapatalk

 

[semibru]

Modem issues persist

I'm thinking re-installing touchdown data is what did you in my friend..

try uninstalling touchdown, go into cwm and wipe cache's then reboot. See what happens..

An update here... went back to stock, then OTA to 2.2.1 (with ED03!). Unfortunately, my 3G issues persist. I notice that the 3G icon often dissappears and frequently getting "page not found" in browser or network errors in Market. BTW, this is before restoring any apps or anything.

I'm wondering what the chances are that it's a hardware issue. Since I'm back to stock, I suppose I can take back to VZ for a replacement. Suggestions on where to go from here? (Happy to post to a new thread for that matter... figured I'd close the loop here first and thanks again for the help.)

 

[Landshark]

An update here... went back to stock, then OTA to 2.2.1 (with ED03!). Unfortunately, my 3G issues persist. I notice that the 3G icon often dissappears and frequently getting "page not found" in browser or network errors in Market. BTW, this is before restoring any apps or anything.

I'm wondering what the chances are that it's a hardware issue. Since I'm back to stock, I suppose I can take back to VZ for a replacement. Suggestions on where to go from here? (Happy to post to a new thread for that matter... figured I'd close the loop here first and thanks again for the help.)

If it's a 3g data connection problem, this may be part of the known issue. Call vzw support and ask to speak to a tier 2 tech support. Have them to a ESN swap and that should bring back your 3g connectivity.

 

[tekhead2004]

ok n00b question everybody. I actually changed my bootanimation.zip to a pretty cool looking superman. I also want to add the superman theme song to my boot animation. I had it working before I flashed to community rom. Is the android_audio.mp3 file somehwere different on this build?

 

[Lttlwing16]

An update here... went back to stock, then OTA to 2.2.1 (with ED03!). Unfortunately, my 3G issues persist. I notice that the 3G icon often dissappears and frequently getting "page not found" in browser or network errors in Market. BTW, this is before restoring any apps or anything.

I'm wondering what the chances are that it's a hardware issue. Since I'm back to stock, I suppose I can take back to VZ for a replacement. Suggestions on where to go from here? (Happy to post to a new thread for that matter... figured I'd close the loop here first and thanks again for the help.)

there is a thread already committed to this..you may find some answers there:

http://forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/83838-3g-cutting-out.html

hope you get it worked out.

 

[wyllic]

If it's a 3g data connection problem, this may be part of the known issue. Call vzw support and ask to speak to a tier 2 tech support. Have them to a ESN swap and that should bring back your 3g connectivity.

Lvl 1 can do an ESN swap for you, if you ask for lvl 2 make them do a DMU reset followed with a sync with billing lcc and esn checked