View Single Post
  #51 (permalink)  
Old 04-27-2011, 11:21 AM
darren.wlsn1's Avatar
darren.wlsn1
acs tester
Offline
Location: pa
 
Join Date: May 2008
Posts: 24,870
Reputation: 51195
darren.wlsn1 can't get a higher reputation leveldarren.wlsn1 can't get a higher reputation leveldarren.wlsn1 can't get a higher reputation leveldarren.wlsn1 can't get a higher reputation leveldarren.wlsn1 can't get a higher reputation leveldarren.wlsn1 can't get a higher reputation leveldarren.wlsn1 can't get a higher reputation leveldarren.wlsn1 can't get a higher reputation leveldarren.wlsn1 can't get a higher reputation leveldarren.wlsn1 can't get a higher reputation leveldarren.wlsn1 can't get a higher reputation level
Mentioned: 14 Post(s)
Tagged: 0 Thread(s)
Send a message via AIM to darren.wlsn1 Send a message via MSN to darren.wlsn1 Send a message via Yahoo to darren.wlsn1 Send a message via Skype™ to darren.wlsn1
Re: [ROM][ACS] SyndicateROM Frozen 1.1.0 (Takiya) :: EC05/1.3ghz/NoCheckboarding :: 3

Quote:
Originally Posted by sweetpoet View Post
Thank you for the response! I actually did try odin and set both phones (as they died) back to stock (they were DI18 when we got them). Restarting the phones after this still had a dead radio and the Android errors (specifically Android.acore or something like that) My first thought had been data corruption and figured resetting to stock would fix it.

As for the journaling thing, I hadn't thought of that as I (shamefully) haven't researched what that is, exactly :P Would that cause the type of corruption that would completely break the radio? (Regular, non-phone apps still seemed to work just fine...just anything that accessed the radio or trying to access phone settings kicked up the numerous errors)

I'll definitely do some research into other kernels, as well! It was just odd that it ran perfectly for that short period of time then died.

As further info, when it did boot up after reflashing to stock, it showed "unknown" under the baseband and hardware versions.

I guess what my real question is...if I start flashing our new phones and it should happen again...has anyone had the same issue and is there a fix for it! ^_^

PS--According to the guy at the Sprint Store, they did have a few of the EC05 phones come back after the update....so it may have to do with that particular radio update.

Anyway, thanks for all the feedback! I may just have to reflash and see what happens! (Though I'd like to avoid another $40 replacement charge! :P )
probably the kernel and make sure your not trying to use any pre EC05 backups but im guessing its the kernel. i never had your issues with this rom but i still switched kernels to make sure i dont plus i turned journal back on.
Reply With Quote