Can't update to 4.2.1

[regression]

I was rooted, but wanted to go back to stock. So I followed QBKing77's video here:

How to Unroot/Unbrick the Samsung Galaxy Nexus - Latest - YouTube

That got me back to 4.1.1. My bootloader is now locked and I am not rooted (I don't see super user). Also, I assume I have stock recovery. Not sure how to check. However, when I run the OTA to update to 4.2.1, I get the Android laying down with a red triangle. Any suggestions on what to do?

 

[llfloyd79]

I was getting the same thing. It act like it wanted to load but then the green android man wit the red triangle popped up. I tried everything. Finally had to take to Sprint to have them load it. Not sure what they did but they fixed it and downloaded 4.2.1 for me.

 

[Danf]

Wish i had had that problem I was a lot happier with 4.1.1

4.2.1 is flat out buggy.

 

[Mellimel22]

IMO 4.1.2 for the Gnex was more buggy than 4.2. But 4.2.2 is what jb should've been since day one.

Sent from my Sprint Galaxy Nexus rockin 4.2.2 using Tapatalk 2

 

[regression]

IMO 4.1.2 for the Gnex was more buggy than 4.2. But 4.2.2 is what jb should've been since day one.

Sent from my Sprint Galaxy Nexus rockin 4.2.2 using Tapatalk 2

Where did you get 4.2.2 for the Sprint Galaxy Nexus?

 

[Mellimel22]

Cm10.1

Sent from my Sprint Galaxy Nexus rockin 4.2.2 using Tapatalk 2

 

[regression]

Cm10.1

Sent from my Sprint Galaxy Nexus rockin 4.2.2 using Tapatalk 2

So you are on one of the nightly builds? If so, which one?

 

[Mellimel22]

The ones past Feb 15 is 4.2.2

Sent from my Sprint Galaxy Nexus rockin 4.2.2 using Tapatalk 2

 

[regression]

The ones past Feb 15 is 4.2.2

Sent from my Sprint Galaxy Nexus rockin 4.2.2 using Tapatalk 2

Thanks, I put the nightly from 2/21 on. It seems to be running good.

- - - Updated - - -

Oh, I and I think I found my original problem. I had a custom PRL (for Verizon) before I tried to go back to stock. I never put Sprint's version back on. I assume that was what was giving me issues with the OTA, but not sure.

 

[rstout76]

I was having the exact same problem. I re-flashed the LTE radio thru Odin and it fixed the problem.

Sent from my Galaxy Nexus using Android Central Forums