Android 4.2 - OTA/Information/Update/ETAs
- Thread starter the|gamer
- Start date
No need to lock again. Mine is on 4.1.2 with root and flashed successfully using cwm.
Heeeell yes, that one worked for me! Installing it right now. Thanks!
@Cyb3rGlitch: Are you on JZO54K? I am, and it works for me.
Yes that is same checksum I got
7bee9b220c20979763af563cad56af94
Sent from my SPH-D710 using Tapatalk 2
When I want to update it in cwm, the installation abords. There stands something with wallet.apk and verify check... Can someone help me please?
So yeah, ended up being the stock browser causing my issues. Need to reverse those chances if you've made them.
bobsie41
Senior Member
It's pretty awesome. Performance wise the entire system feels so much smoother. The fonts also render a bit bolder, which look better in my opinion. When you turn the screen off, there's a nice new fade-out animation. And yes, multi user support is enabled for us.
Last edited:
Try the SHA1 checksum … this should be the same as in the filename itself:
Code:
$ sha1sum e587de13bf8a.signed-takju-JOP40C-from-JZO54K.e587de13.zip
e587de13bf8adc21df8ca9b7b012fb60293c7035 e587de13bf8a.signed-takju-JOP40C-from-JZO54K.e587de13.zipConfirmed. It seems much smoother all around. And there are the lockscreen widgets as well!
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
6
Sure, but keep in mind I run Linux, so while the commands are pretty much the same, there might be some subtle differences between the two.
If you download that 4.2 image I gave the link for above, and extract the .tgz file, you will see the following files:
bootloader-grouper-4.13.img flash-all.bat flash-all.sh flash-base.sh image-nakasi-jop40c.zip
The first one is the 4.13 Bootloader image, which needs to be flashed to the "bootloader" via fastboot. The flash* files are simply scripts that can automate the process, but let's ignore those. Since we only want to do a partial upgrade (and not lose userdata) extract the image-nakasi-jop40c.zip file into that directory. You will now get the following files from that:
boot.img recovery.img system.img userdata.img android-info.txt
These are the STOCK images for 4.2, broken out across the different sections of the device. The filenames are pretty self-explanatory for where they go.
I should point out that you need to have downloaded and installed the Android Developer SDK to continue. This will include, among other things, adb and fastboot. If you've done that already, great. If you installed a toolkit, it probably comes with those files.
Now, connect your tablet to your PC. Make sure that USB debugging developer mode is enabled. Open up a command prompt (cmd) and go into the directory you extracted all those files to. You can verify that the device is connected properly by typing "adb devices". If you get some error about "adb" not being a recognized command, you'll probably have to include the full path to that program. If you get an empty list, your tablet isn't being recognized. If it shows the tablet, you're good to go.
Ok, so now we need to get into bootloader mode. You can either do this manually on the tablet (if you know how) or type "adb reboot-bootloader".
Once the device is in bootloader mode, and I assume you have already unlocked it, you will run the following commands:
fastboot flash bootloader bootloader-grouper-4.13.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot-bootloader
The bootloader should restart and reflect version 4.13.
At this point, you can either reboot the device into normal mode, or reboot into recovery. Your prior recovery (stock or custom) should be present. If you want to flash a new custom recovery, you can do that by typing:
fastboot flash recovery (path to the recovery.img file you want to use)
As I mentioned before, this will wipe and replace all of /system, so anything you had in there before (su, busybox, init.d scripts, etc.) is gone, and you will have to reinstall it again.
Hopefully that clarifies things. Again, I assume you are on Windows, so you might have to put the path to fastboot in the command. But the syntax should be identical.
---------- Post added at 12:11 PM ---------- Previous post was at 12:08 PM ----------
One last note. This will keep userdata/sdcard intact, and all your prior files and apps should be fine. DO NOT FLASH USERDATA.IMG. If you do, it will basically factory reset your tablet (unless that's what you want).
Once you reboot into normal android, you will be on 4.2. It will take a while to boot up the first time and say "upgrading applications", but then you should be good to go. If you go into custom recovery before rebooting, you may also want to wipe cache and wipe dalvik cache to clean things up.5a Google search could have found your answer Very Quickly.. Guys play nice..
It will come after the Launch of nov 13th... The announcement was 29th not the launch day. GO read the 29th announcement and read when the new phones will be out..
I have to say this forum is getting full of Common knowledge threads and post..
