I asked the same question after my update failed. I was told that I need to be on full stock w stock kernel.
Sent from my Nexus 7 using xda app-developers app
Sent from my Nexus 7 using xda app-developers app
Android 4.1.2 is here!
- Thread starter rockvoid
- Start date
Not true, I'm 100% stock and the update failed because I'm on S and update is for D.
Sent from my HTC Sensation using xda app-developers app
thephantom
Senior Member
That's not exactly an apples to apples comparison. The update file does indicate it is for the 4.1.1 D to 4.1.2 so using it on the S build would really generate an error
Sent from my Nexus 7 using Tapatalk 2
People, sometimes it can take over a week for the OTA update to roll out to everyone. Either be patient or flash it manually. You can flash it manually using stock recovery and ADB. You don't need to be unlocked, rooted, or anything else. You won't lose any data by flashing manually, and it's the exact same update file your device will download when the OTA reaches you. You're just triggering the update yourself.
All you need is the Android SDK installed, and your USB cable. If you can't be bothered to flash manually, then just be patient. The OTA will get to you.
NOTE: The above rant only applies to people running JRO03D. If you're on JRO03S, you have no choice but to wait (unless you want to unlock your bootloader and wipe your device) since nobody has posted a link for that OTA file, and we're not even sure Google has started rolling it out yet.
All you need is the Android SDK installed, and your USB cable. If you can't be bothered to flash manually, then just be patient. The OTA will get to you.
NOTE: The above rant only applies to people running JRO03D. If you're on JRO03S, you have no choice but to wait (unless you want to unlock your bootloader and wipe your device) since nobody has posted a link for that OTA file, and we're not even sure Google has started rolling it out yet.
Last edited:
Be sure your build.prop is in the original state. If it was changed you'll get this message. I roll back my build.prop from 160 to 213 and it works!
Regards,
Regards,
Well I'm guessing for some reason my Chrome got modified by something because if you look at this:
DepressingCode:-- Install /sdcard/Download/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip ... Finding update package... I:Update location: /sdcard/Download/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip Opening update package... Installing update... mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP at /system: Device or resource busy Verifying current system... file "/system/app/Chrome.apk" doesn't have any of expected sha1 sums; checking cache failed to stat "/cache/saved.file": No such file or directory failed to load cache file script aborted: assert failed: apply_patch_check("/system/app/Chrome.apk", "819b34b66335c6faec86404d736a002bd8871600", "9d6b55e63b0bf20bea433fb1ee7089f88ab73fb6") assert failed: apply_patch_check("/system/app/Chrome.apk", "819b34b66335c6faec86404d736a002bd8871600", "9d6b55e63b0bf20bea433fb1ee7089f88ab73fb6") E:Error in /sdcard/Download/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip (Status 7)
Sent from my Nexus 7 using Tapatalk 2
Just got my update 11:13Am CST
Just got my update 11:13Am CST I am in Illinois
Took 5 minutes start to finish and it works fine, so far.
Except I notice that the WiFi icon is no longer showing the levels in white, it is greyed out although my wifi connection is still rock solid
Just got my update 11:13Am CST I am in Illinois
Took 5 minutes start to finish and it works fine, so far.
Except I notice that the WiFi icon is no longer showing the levels in white, it is greyed out although my wifi connection is still rock solid
thephantom
Senior Member
Happened to me on the first boot. After a few minutes everything went back to normal
Sent from my Nexus 7 using Tapatalk 2
My update just hit. I'm now running build JZ054K, in Raleigh NC.
But it seems I lost root. I am using CHAINSDD's superuser elite. I checked the OTA survival before I applied the update. The su binary is there, but everytime I run it, it does nothing. Just errors with return code 1 (tested via adb shell). :\
But it seems I lost root. I am using CHAINSDD's superuser elite. I checked the OTA survival before I applied the update. The su binary is there, but everytime I run it, it does nothing. Just errors with return code 1 (tested via adb shell). :\
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
22
Thats all I need
Enjoy kids: http://android.clients.google.com/p...signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip7
Er, so it was released what, a day or so ago and you're raged because you don't have it yet? Really?
Call me crazy, but if I were Google rolling out an update to millions of devices, I would THINK I'd have to handle it in some sort of distributed manner so my servers don't get slammed at once. Think of elementary school at lunch time. "Tables 1 and 2 are dismissed..."64
