inf

Strange problem after OTA update

Recommended Posts

inf    1

I put my Nexus back to the official stock images last night (going to give it to my wife, I'll get a new one :D). The flashing of the stock images went fine and I was on android 4.0.1 41d for a while. Then came the OTA update, and I of course flashed it.

Now I'm on ICL53F, but everytime i start/boot the phone I get a FC from com.android.phone process.

Anyone here could help? I can't seem to be able to find the culprit here.

Share this post


Link to post
Share on other sites
inf    1

Just my opinion, but if ur now running a stock rom and not pauls ,u should head over to Samsung website for help with stock rom. Probably get the help u need

LOL really?

Share this post


Link to post
Share on other sites
jmagee    19

If your not wanting to reflash maybe worth wiping Dalvik or trying a factory reset see if that solves it assuming you haven't tried these already.

Share this post


Link to post
Share on other sites
EddyOS    8

Ya really. Y u think u have no reply s; ) k bye

You do know this is a general forum for the GN, not just Paul's ROM? Your reply was not helpful in the slightest.

As said, I'd do a hard reset again and see what happens

Share this post


Link to post
Share on other sites
Drawde40599    0

You do know this is a general forum for the GN, not just Paul's ROM? Your reply was not helpful in the slightest.

As said, I'd do a hard reset again and see what happens

K, sorry but me personally wouldnt be asking stock rom questions in this type of. Forum. Agn sorry

Share this post


Link to post
Share on other sites
inf    1

If your not wanting to reflash maybe worth wiping Dalvik or trying a factory reset see if that solves it assuming you haven't tried these already.

Tried pretty much everything, but the problem still persists.

It is so strange because everything works fine with ITL41D an ITL41F, but after I update to the ICL53F, this problem starts.

Tried to get a logcat for the error, it's attached

logcat.txt

Share this post


Link to post
Share on other sites
wardy    1

Tried pretty much everything, but the problem still persists.

It is so strange because everything works fine with ITL41D an ITL41F, but after I update to the ICL53F, this problem starts.

Tried to get a logcat for the error, it's attached

Did you clear cache etc before you went bak to stock ?

Share this post


Link to post
Share on other sites
wardy    1

Did you clear cache etc before you went bak to stock ?

To be more helpful , re root the phone , head over to XDA and download super wipe from the hd rom . Run that then go back to stock . This should cure the problem

Share this post


Link to post
Share on other sites
inf    1

To be more helpful , re root the phone , head over to XDA and download super wipe from the hd rom . Run that then go back to stock . This should cure the problem

Thanks for the tip, but it didn't help. Same problem still :(

Share this post


Link to post
Share on other sites
wardy    1

Thanks for the tip, but it didn't help. Same problem still :(

Ok do the same again but this time don't let Google send you the update , apply the ROM from here using ADB. Do not let Google apply a back up on its servers to you . Do a complete fresh install .

http://code.google.com/android/nexus/images.html

On the assumption that you are letting google send you the update

Share this post


Link to post
Share on other sites
inf    1

Ok do the same again but this time don't let Google send you the update , apply the ROM from here using ADB. Do not let Google apply a back up on its servers to you . Do a complete fresh install .

http://code.google.c...xus/images.html

On the assumption that you are letting google send you the update

This is so strange...i tried with those images too couple of days ago. Im now on stock images (ITL41F) from google. But If I use the OTA this error comes. But If I use the googles factory images and flash them with fastboot...same thing. So pretty stranges thing. The error comes straight away when the phone loads the OS (haven't even started the setup).

I'm now on ITL41F and everything is fine...though google doesn't even give me the ota update at the moment. Might be ofcourse that they are already beginning to roll out the 4.0.3 update.

Share this post


Link to post
Share on other sites
inf    1

Does it do it with the SIM out or with a different SIM?

P

hmm actually I haven't tested without sim...could that somehow be the problem? Google has changed something in the 4.0.2 update then?

Share this post


Link to post
Share on other sites
PaulOBrien    1,450

hmm actually I haven't tested without sim...could that somehow be the problem? Google has changed something in the 4.0.2 update then?

Not necessarily, but it rules out one possible cause!

P

Share this post


Link to post
Share on other sites
inf    1

Not necessarily, but it rules out one possible cause!

P

Well i'll test it without sim when i get home

Share this post


Link to post
Share on other sites
inf    1

Well i'll test it without sim when i get home

I booted without the sim card...and no error...now to test with the sim card.

Share this post


Link to post
Share on other sites
inf    1

I booted without the sim card...and no error...now to test with the sim card.

With the sim card...the error returns...

Share this post


Link to post
Share on other sites
wardy    1

With the sim card...the error returns...

Ahh ok,

When you flashed via fastboot did you flash the image first or the radio?

Share this post


Link to post
Share on other sites
inf    1

I first fastbooted the bootloader, then radio and after that, just the image.

It sounds pretty strange that it would be in the sim card. It has worked with custom roms without an error. And it works with ITL41F (official firmware) fine without errors.

Does Paul have something what could make it behave like this.

Share this post


Link to post
Share on other sites
wardy    1

I first fastbooted the bootloader, then radio and after that, just the image.

It sounds pretty strange that it would be in the sim card. It has worked with custom roms without an error. And it works with ITL41F (official firmware) fine without errors.

Does Paul have something what could make it behave like this.

Not sure but I remember this happening before and the cur was img first then radio. Not sur where I read this now , was a while back .Ill give it a google .

Share this post


Link to post
Share on other sites
wardy    1

I first fastbooted the bootloader, then radio and after that, just the image.

It sounds pretty strange that it would be in the sim card. It has worked with custom roms without an error. And it works with ITL41F (official firmware) fine without errors.

Does Paul have something what could make it behave like this.

Not sure but I remember this happening before and the cur was img first then radio. Not sur where I read this now , was a while back .Ill give it a google .

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.