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

Just an update to issues I had with my g/f's fascinate. If your phone is stuck at the samsung screen, flash a different kernel in CWM. I flashed OTB TW v1.3 (one version older than the included) it booted finally. I have no idea why it wouldn't work.
 
I noticed a new Swype theme in 1.3, and though its new and different, I'm not totally thrilled about it. I found that the 1.2 patch had a good Swype theme. Could anyone point me in the direction of finding the .zip file for that theme?

Extract the comrom1.0.zip and find the Swype.apk.

Copy and paste to your system/ app folder using root explorer.

If you hit snags.

Follow the directions here..

http://forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/82298-how-changing-out-themed-swype-apk.html
 
Downloading 1.3 now, hoping for the best after hearing the mixed bag of results on here...
 
It's working fine for me so far, no issues at all. If you have problems with it, redownload the zip and reflash it, cus I'm not seeing any problems with the file itself
 
Just an update to issues I had with my g/f's fascinate. If your phone is stuck at the samsung screen, flash a different kernel in CWM. I flashed OTB TW v1.3 (one version older than the included) it booted finally. I have no idea why it wouldn't work.

I came here to give that exact advice :) . My guess is its a voltage control issue. But thats purely guess.

Sent from my SCH-I500 using Tapatalk
 
Just a note that the OP was updated a bit ago by Adrynalyne, he added a couple more things to the 1.3 changelog, I don't know if he changed the download at all, it appears to still be of the same size so I'm guessing not. Just thought I'd let everyone know.
 
  • Like
Reactions: Lttlwing16
so is 1.3 not a final build since it has test in the file name (community_rom_1.3_test2.zip)
 
so is 1.3 not a final build since it has test in the file name (community_rom_1.3_test2.zip)

I think it's intended to be a final build release, guessing the test2 portion of the file name was when they were doing testing on it and just didn't change the file name. If this wasn't a final build I think Adryn would of stated it in the OP.
 
I came here to give that exact advice :) . My guess is its a voltage control issue. But thats purely guess.

Sent from my SCH-I500 using Tapatalk

Not sure if it is related.. got a random reboot - dropping back to OTB 1.3.

Thanks for the help gunnermike53.
 
I think it's intended to be a final build release, guessing the test2 portion of the file name was when they were doing testing on it and just didn't change the file name. If this wasn't a final build I think Adryn would of stated it in the OP.

i dunno, i started getting constant acore process force closes the moment it booted up with 1.3. it was a full 170mb download.
 
i dunno, i started getting constant acore process force closes the moment it booted up with 1.3. it was a full 170mb download.

I had that happen the first time I booted up the original 1.0, what I did was went back into cwm, wiped data again, wiped both caches again, fixed permissions. Then I reflashed the rom, booted up perfectly, not a single FC. Not saying that will work for you, but it may.. It's your choice to try if you'd like.
 
i dunno, i started getting constant acore process force closes the moment it booted up with 1.3. it was a full 170mb download.

Thats the modem. Reflash ec01 modem or go through all the steps to get ed01.

Sent from my SCH-I500 using Tapatalk
 
i dunno, i started getting constant acore process force closes the moment it booted up with 1.3. it was a full 170mb download.

If this was not intended to be a final build, Adrynalyne would not have posted it. He and the other devs may tweak it based on problems people are having as long as everyone can provide logcats. But this is definitely a complete, final build otherwise.
 
On hardware v I500.04 I'm running SC2.9.2, fw v 2.2.1, baseband v S:i500.04 V.DL09, kernel v 2.6.32.9, SCH-599.EB01. I have red recovery 2.5.1.x. What is best way to get to Comm Rom v 1.3? Prefer to avoid Odin, just flash from recovery if possible. I'm sure specific answers are already here somewhere but I get lost looking.

Thanks to all.
 
On hardware v I500.04 I'm running SC2.9.2, fw v 2.2.1, baseband v S:i500.04 V.DL09, kernel v 2.6.32.9, SCH-599.EB01. I have red recovery 2.5.1.x. What is best way to get to Comm Rom v 1.3? Prefer to avoid Odin, just flash from recovery if possible. I'm sure specific answers are already here somewhere but I get lost looking.

Thanks to all.

Well, the community rom is indeed flashed within cwm. However I see you're currently on the DL09 radio (that's the baseband v S:i500.04 V DL09) It's highly recommended to update at least to the EC01 radio, but as far as I know the only way to do that is within Odin, it's pretty simple tho. Here is that radio: EC01 Radio But other than that you wouldn't need to use Odin to flash the Rom itself. Just be sure to AT LEAST wipe cache partitions and dalvik cache in cwm. It's highly recommended to do a data wipe tho. But may not be necessary unless you find yourself having force closes and other problems upon booting up.
 
  • Like
Reactions: anub
so i recent when thru the process of getting the ED01 radio. everything went good. got the offical ed01. flashed CWM, wiped cache/dalvik cache and data. then flashed comm rom 1.0. once it booted up it said my sd card was blank?

but when i booted to recovery i could see everything on the sd card
 
thanks

Well, the community rom is indeed flashed within cwm. However I see you're currently on the DL09 radio (that's the baseband v S:i500.04 V DL09) It's highly recommended to update at least to the EC01 radio, but as far as I know the only way to do that is within Odin, it's pretty simple tho. Here is that radio: EC01 Radio But other than that you wouldn't need to use Odin to flash the Rom itself. Just be sure to AT LEAST wipe cache partitions and dalvik cache in cwm. It's highly recommended to do a data wipe tho. But may not be necessary unless you find yourself having force closes and other problems upon booting up.

Being lazy and 'Doze averse I just wiped cache parts & dalvik, flashed Com Rom v1.3 from CWM all red and wiped caches again. Reboot got the "ANDROID" with light going back and forth for about 2 min then all good. Everything I've tested so far is faster. Only change in About Phone is it now says Build # SCH-I500.ED01. So what may the drawbacks of staying with DL09 radio be? No way to upgrade radio without Odin-ing?

Thanks again.
 
Being lazy and 'Doze averse I just wiped cache parts & dalvik, flashed Com Rom v1.3 from CWM all red and wiped caches again. Reboot got the "ANDROID" with light going back and forth for about 2 min then all good. Everything I've tested so far is faster. Only change in About Phone is it now says Build # SCH-I500.ED01. So what may the drawbacks of staying with DL09 radio be? No way to upgrade radio without Odin-ing?

Thanks again.

You may have issues with phone calls and SMS messaging, or you may not at all. If things are going fine the way the are for you now, by all means, stick with it. If you notice problems then I would definitely consider updating the radio/modem. As far as I know Odin is the only way to apply the radio, but there's the chance I could be mistaken, their may be a way to do it in cwm, if someone else knows I hope they chime in.
 
  • Like
Reactions: anub

Trending Posts

Forum statistics

Threads
957,273
Messages
6,972,173
Members
3,163,750
Latest member
Ayomide