Android 4.1.2 is here!
- Thread starter rockvoid
- Start date
Will having the tablet UI cause any problems? Will the tablet UI survive the update?
Sent from my Nook Tablet using XDA Premium
Sent from my Nook Tablet using XDA Premium
So far Flipboard loaded updates in like 10 seconds and I flipped through one section really fast, no lag, no stuttering. Of course I just booted the system, but in the past, Flipboard would lag terribly and take 30-45s to load updates.
Crossing fingers this fixed the IO lag problems..
Crossing fingers this fixed the IO lag problems..
What about the all in 1 toolkit that a lot of us used to root and get recovery in 4.1.1?
In it, you can restore the tablet to stock using the latest release from Google. Could we not use that to restore it, take the OTA and then use it again to re-root it and all that?
Anybody have a link to stock kernel and modules for JR003D?
Sent from my Nexus 7 using Tapatalk 2
Sent from my Nexus 7 using Tapatalk 2
Just use rootkeeper before updating if you are worried about root, worked fine here
and yes changing of the build.prop (changing dpi, etc) will cause the update to fail
and yes changing of the build.prop (changing dpi, etc) will cause the update to fail
Getting same thing but I'm running custom kernel so I think that's what it is
Sent from my Nexus 7 using Tapatalk 2
If you're completely stock you can use this procedure to update:
- Download the update file from Google: http://android.clients.google.com/p...signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
- Download ClockworkMod recovery: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-grouper.img
- Enable USB debug on your Nexus 7 and plug it in to your PC.
- On your PC transfer the OTA zip file to your Nexus 7 /sdcard partition with the following command: "adb push 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip /sdcard/" and wait for it to complete.
- On your PC, type in "adb reboot bootloader"
- On your PC, type in "fastboot boot recovery-clockwork-touch-6.0.1.0-grouper.img". This step temporarily pushes CWM to your Nexus 7 and boots from it. This step is not permanent so you retain stock recovery.
- Your Nexus 7 will load up CWM recovery. Use the on screen menus to find the OTA zip file and flash it.
- Your Nexus 7 will prompt to reboot when completed.
Good luck!
Last edited:
Just finished updating, system is much smoother and screen sharper. I haven't lost root nor relocked bootloader. I was on Stock d ROM and with r binary drivers. Thanks a million for all the devas for the great Work.
Sent from my Nexus 7 using xda app-developers app
Sent from my Nexus 7 using xda app-developers app
Any idea what the fix for this is ? (to enable the OTA update)
Sent from my Nexus 7 using xda premium
To cause it not to fail? Be on stock JRO03D, no changes to build.prop or /system , flash back to the factory image if you need to
Last edited:
I didn't use that toolkit, I used another one and I just used it to restore to stock, am now awaiting the OTA and then I will try to re-root it and report back.
--Installing: /sdcard/package.zip
Finding update package...
Opening update package...
Installing update...
Verifying current system...
Removing unneeded files...
Patching system files...
Patching boot image...
Unpacking new files...
Unpacking new recovery...
Symlinks and permissions...
Writing bootloader...
Patching remaining system files...
Install from sdcard complete.
JRO03D successfully updated using CWM 6.0.1.0
Finding update package...
Opening update package...
Installing update...
Verifying current system...
Removing unneeded files...
Patching system files...
Patching boot image...
Unpacking new files...
Unpacking new recovery...
Symlinks and permissions...
Writing bootloader...
Patching remaining system files...
Install from sdcard complete.
JRO03D successfully updated using CWM 6.0.1.0
Last edited:
So, I failed to flash the first time via CWM 6.0.1.0.
Read the threads and found out that the modded build_prop can cause the failure.
I removed the build_prop and restored to stock build_prop (simply renamed the build_prop.bak to build_prop after deleting the modded build_prop).
It seems to be updating successfully now.
Booting now and it seems bootloader is still unlocked (open lock icon).
Updaing the apps now. Will see if it retained the root...
Thanks
edit. looks like I have lost root...
Read the threads and found out that the modded build_prop can cause the failure.
I removed the build_prop and restored to stock build_prop (simply renamed the build_prop.bak to build_prop after deleting the modded build_prop).
It seems to be updating successfully now.
Booting now and it seems bootloader is still unlocked (open lock icon).
Updaing the apps now. Will see if it retained the root...
Thanks
edit. looks like I have lost root...
Last edited:
I'm on cm10 ROM with 161 trinity kernel... is there a point I'm attempting to update or will they just be merged..?
Sent from my Nexus 7 using xda premium
Sent from my Nexus 7 using xda premium
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
