Guest inf Posted December 17, 2011 Report Share Posted December 17, 2011 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. Link to comment Share on other sites More sharing options...
Guest Drawde40599 Posted December 17, 2011 Report Share Posted December 17, 2011 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 Link to comment Share on other sites More sharing options...
Guest inf Posted December 17, 2011 Report Share Posted December 17, 2011 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? Link to comment Share on other sites More sharing options...
Guest Drawde40599 Posted December 17, 2011 Report Share Posted December 17, 2011 Ya really. Y u think u have no reply s; ) k bye Link to comment Share on other sites More sharing options...
Guest jmagee Posted December 18, 2011 Report Share Posted December 18, 2011 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. Link to comment Share on other sites More sharing options...
Guest EddyOS Posted December 18, 2011 Report Share Posted December 18, 2011 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 Link to comment Share on other sites More sharing options...
Guest Drawde40599 Posted December 18, 2011 Report Share Posted December 18, 2011 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 Link to comment Share on other sites More sharing options...
Guest inf Posted December 18, 2011 Report Share Posted December 18, 2011 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 attachedlogcat.txt Link to comment Share on other sites More sharing options...
Guest wardy Posted December 18, 2011 Report Share Posted December 18, 2011 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 ? Link to comment Share on other sites More sharing options...
Guest wardy Posted December 18, 2011 Report Share Posted December 18, 2011 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 Link to comment Share on other sites More sharing options...
Guest inf Posted December 19, 2011 Report Share Posted December 19, 2011 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 :( Link to comment Share on other sites More sharing options...
Guest wardy Posted December 19, 2011 Report Share Posted December 19, 2011 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 Link to comment Share on other sites More sharing options...
Guest inf Posted December 19, 2011 Report Share Posted December 19, 2011 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. Link to comment Share on other sites More sharing options...
Guest Paul Posted December 19, 2011 Report Share Posted December 19, 2011 Does it do it with the SIM out or with a different SIM? P Link to comment Share on other sites More sharing options...
Guest inf Posted December 19, 2011 Report Share Posted December 19, 2011 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? Link to comment Share on other sites More sharing options...
Guest Paul Posted December 19, 2011 Report Share Posted December 19, 2011 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 Link to comment Share on other sites More sharing options...
Guest inf Posted December 19, 2011 Report Share Posted December 19, 2011 Not necessarily, but it rules out one possible cause! P Well i'll test it without sim when i get home Link to comment Share on other sites More sharing options...
Guest inf Posted December 19, 2011 Report Share Posted December 19, 2011 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. Link to comment Share on other sites More sharing options...
Guest EddyOS Posted December 19, 2011 Report Share Posted December 19, 2011 How old is your SIM card? Might be worth getting a new one Link to comment Share on other sites More sharing options...
Guest inf Posted December 19, 2011 Report Share Posted December 19, 2011 I booted without the sim card...and no error...now to test with the sim card. With the sim card...the error returns... Link to comment Share on other sites More sharing options...
Guest wardy Posted December 19, 2011 Report Share Posted December 19, 2011 With the sim card...the error returns... Ahh ok, When you flashed via fastboot did you flash the image first or the radio? Link to comment Share on other sites More sharing options...
Guest EddyOS Posted December 19, 2011 Report Share Posted December 19, 2011 Shouldn't make a difference should it? I reckon a new SIM card is in order Link to comment Share on other sites More sharing options...
Guest inf Posted December 19, 2011 Report Share Posted December 19, 2011 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. Link to comment Share on other sites More sharing options...
Guest wardy Posted December 19, 2011 Report Share Posted December 19, 2011 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 . Link to comment Share on other sites More sharing options...
Guest wardy Posted December 19, 2011 Report Share Posted December 19, 2011 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 . Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now