Originally Posted by frikisama
Well... that's weird xD. If it went 100% it means the script SHOULD have already put the bootloader where it should be. Anyway, try with stock recovery and system! If the little bastard is still ignoring you, then consider reflashing a complete stock image (!!! BACKUP !!!). I don't know what else could cause your problem, I'm more of a "standard" linux guy than an low-level embedded systems guru!
Edit: Plus I don't have the time to investigate these things anymore (I wish!!
Yeah, the bootloader issue is even crazier then the radio one.
During both the first and second OTA update attempt, the install process never indicated any issue with the bootloader update. It wrote it then moved on to radio, where it failed.
And prior to the second OTA update attempt, I did actually revert everything back to full 4.2.1 stock using the images from Google. I even flashed the stock recovery, though later overwrote that prior to do the 4.2.2 update. The only thing I didn't do was erase userdata. But when I rebooted bootloader, it said 4.13.
And after it rebooted after my second attempt, which again failed on radio, while the bootloader said 4.13, the baseband (in bootloader mode) said it upgraded! It was on the 1231_0.17 version. So it looked like it worked. But then when I booted into Android, the System Status showed 1231_0.10. This discrepancy might have something to do with the failed bootloader upgrade.
If CWM/TWRP doesn't have the bach_modem.update function, then that would certainly explain why the radio is failing. But if that's so, and I have to believe many others are using custom recoveries, why am I the only one reporting this issue?
I'll try installing stock 4.2.1 recovery back and sideloading the radio and bootloader again to see if that works. If so, great. If not, I'll probably have to wait until the full system images are released.