ichi Posted April 15, 2015 Share Posted April 15, 2015 Just though I'd share this here. I decided today to sideload the 5.1 OTA on my N4, same as I did when the 5.0.1 was released, so I installed the SDK, downloaded the OTA image, conected and rebooted the phone to recovery and ran the adb sideload command to upload the image. And here things go weird, because short after selecting the "apply update from ADB" option the phone had already verified the update and started to apply the update... all while the upload process hadn't gone over the 10%. So I has there like "whaaaaat the f*ck are you doing, Android". And just to make things worse it seemed to get stuck forever at "patching system files". The upload process also slowed down to almost a halt. An eternity later the update process finished, and seconds later so did the upload. And for some reason when presented with the Restore menu again I thought "what the hell" and selected again "apply update from ADB" and launched the adb sideload command again. And same thing happened, for only stupids expect repeating the same thing to get different results When it finished updating again (or whatever the hell it was doing) and I could verify that the phone booted I thought "screw it", I'd leave it as it is. To my surprise I just checked the Android version and it reads 5.1. Maybe I'm wrong about this, but my rationalization of the whole thing is that the first time it must have picked up the OTA file from the previous sideload, while the second time it would have picked the OTA file that I had just uploaded while the old OTA was being installed. Could that be it? Link to comment Share on other sites More sharing options...
Recommended Posts