The #1 Nexus 7 News, Discussion and Fan Site!
2012 Nexus 7 Discussion Forums (1st Generation) => Nexus 7 Android OS (Jelly Bean) => Topic started by: S.Prime on October 14, 2012, 03:00:22 PM
-
The Forum Guide to Installing OTA 4.1.2 With and Without Root by S.Prime
(http://i1254.photobucket.com/albums/hh618/Prime_N7/Photobucket%20Desktop%20-%20DELL-XPS/screen_20121014_1644_zpsb41bc594.png)
Forcing the OTA Update (Over The Air)
You can wait for the update to be pushed to your device or you can force it by this process:
Swipe down from the top of the screen and tap the three horizontal sliders and you will be at Settings > Tap Apps > Swipe left until you reach “All” > Scroll down and tap “Google Services Framework” > Tap “Force Stop” and “Clear Data” > Tap Back twice to return to the “Settings” screen > Scroll down and tap “About tablet” > Tap “System updates” (Note your date will show Dec 1969) > Tap “Check now”
If the system shows “Up to date” return to “Google Services Framework” and repeat the stop and clear data and check for updates process again. Note the process may have to be repeated 4 times to force the update.
When the update appears you have the options to “Save for later” or “Install Now”. If you select later, returning to “About tablet” > “System updates” will display the install option again.
Note, if have previously received the OTA update notification and the install failed you can force the download of the update again with the above procedure.
Stock Nexus 7 (Not Rooted)
Wait for the OTA notification to appear or use the “Force Procedure” above and select “Install Now” and your tablet will reboot and you will note a series of text line messages describing the process and once finished you be returned to your home screen. After reboot go to Settings > About Tablet and you can verify Android version 4.1.2.
Rooted Nexus 7
Step 1
Install Voodoo OTA RootKeeper from Google Play Here (https://play.google.com/store/search?q=voodoo+root+keeper) and run the App to protect your root as the OTA 4.1.2 will remove root. Optionally install RootCheck Basic from Google Play Here. (https://play.google.com/store/search?q=root+check+basic)
Step 2
If you modified your build.prop with RomToolBox goto /sdcard/romtoolbox/build.prop-backups or wherever you have your backup located and copy the backup to \system and rename the current build.prop to build.prop[mod] and then rename the backup to build.prop. If you do not have a backup of the build.prop file, it has been reported that you can edit your current build.prop file and remove the last line “launcher.force_enable_rotation=true”. But I have not tried it, so I am asking someone to verify that removing the line will work.
Step 3
Return to “Settings” > “About tablet” > “system updates” and select “Install Now” and your tablet will reboot and you will note a series of text line messages describing the process and once finished you be returned to your home screen.
Step 4
Open VooDoo RootKeeper and select restore root. Open your SuperUser app and update the binaries or you will not have super user privileges. If you installed RootCheck Basic you can then verify root.
Then go to Settings > About Tablet and you can verify Android version 4.1.2.
Step 5 (Custom recovery option)
TWRP Recovery
Download GooManager from Google Play Here (https://play.google.com/store/search?q=goomanager) and tap the three dots in the upper right corner and tap "Install OpenRecoveryScript"
ClockworkMod Recovery
Download RomManager from Google Play Here (https://play.google.com/store/search?q=rom+manager) and tap "Flash CloclworkMod Recovery"
Note that you can use either TWRP or ClockworkMod Recovery, both of which allow you to create and restore nandroid backups, but you cannot install both, as running the install for one recovery option with the other already installed will simply replace the previously installed recovery option.
-
This looks very good S.Prime! Now I can force the update with no problem. However when I tried to install it, the same thing happened; I got the red exclamation point and no new version.
Now do I have to 'unroot' before I can run the update? Is this what step one is about? I did use Voodoo to make a copy but it was still rooted. And I did not modify the build prop. Any ideas and where to go next??
r
-
You do not need to unroot, you do needed to protect root. Unroot adds an extra layer of caution as it saves a backup of the root.
-
Correct, you do not need to unroot, but you need to look at your history and recognize if you have un-installed any pre-installed apps, if you did the OTA may be looking for those files and fail. Remember, that root gives you the ability to expand your device as well as restrict it. You may be at the point that you need to ask JayJ to guide you through a full rom reload.
-
Removing the last line/ rotation true in the build.prop worked for me.
I also temporarily unrooted with RootKeeper until the update rebooted.
I have frozen Pinyin and Magazines but never removed any system apps with Titanium.
-
Yup, I did uninstall some stock apps. I'll never be able to remember which ones though. Yes, if JayJ could walk me through loading a stock rom that would be cool. Could I just do a back up and then a factory reset?? Wouldn't that do it?
r
-
Yes backup with Titanium Backup, but you will need a full ROM reload and JayJ will be your best source. Be patient and let JayJ supply some input.
-
Got it...
-
Radio, would you be willing to try out a very close to stock custom ROM until we put together a walkthrough on getting back to stock?
-
A guide to stock recovery is an excellent idea.
-
Sure thing loocid... Now, mine is running fine mind you (except for no camdamera) but I just thought I should be able to update. 'Cuz what if 4.2 comes along some day and I can't update...??!
-
Radio. I would backup apps with Titanium and then use Wugfresh new toolbox to flash back to the factory rom and go from there. I believe it was updated a couple of days ago. Next time I would try and freeze factory apps instead of removing them because of such problems down the road.
http://forum.xda-developers.com/showthread.php?t=1766475 (http://forum.xda-developers.com/showthread.php?t=1766475)
-
If anyone has experience with the RAZR prior to Ice Cream Sandwich, then you understand the importance of "the path." In the weeks preceding the upgrade to ICS, there were "leaks" of test build floating all over the place. These leaks would allow a rooted user to prematurely upgrade to ICS before the OTA. Some of the leaks were full ROMs; others were updates to previous builds. Once a leak has been installed past a certain point in the upgrade path, there was no turning back because of the locked bootloader. We don't have that problem, but we are similar in that to install an update, you have to be on a specific build. This current update will only install on the JRO03D build. Those on the JRO03S build will most likely receive a different update package. When the time comes for the next upgrade, it will only install on build JZ054K completely unaltered. This means no frozen, disabled, or uninstalled apps. No changes can be made to the build.prop. I advise everyone to make a Nandroid backup immediately after receiving a successful update. This backup can be restored to avoid any issues with the upgrade path regardless of the changes made or what custom ROM you have installed.
-
Radio. I would backup apps with Titanium and then use Wugfresh new toolbox to flash back to the factory rom and go from there. I believe it was updated a couple of days ago. Next time I would try and freeze factory apps instead of removing them because of such problems down the road.
[url]http://forum.xda-developers.com/showthread.php?t=1766475[/url] ([url]http://forum.xda-developers.com/showthread.php?t=1766475[/url])
Ah, very good bjs... yes now I know. Next time I will freeze rather than delete. I did see that caution but chose to ignore it at the time; live and learn!
-
I am a little stuck now. If I try and reboot recovery I get the android with the red exclamation. One of the choices is to update.. I am already updated to 4.2.1 so I am not sure what it will do. I can't get into TWRP.. Any ideas?
-
You lost your custom recovery, this is the stock recovery screen. I think I'm going to make a tool for restoring recovery since this seems to be a trend.
-
You lost your custom recovery, this is the stock recovery screen. I think I'm going to make a tool for restoring recovery since this seems to be a trend.
Sounds good.
Should I get rid of my twrp folder on the Nexus now? I have the backup on my pc. Does it serve a purpose on the Nexus still if I can't access it? I I am going to try the toolbox and reflash custom recovery see what happens.
-
Yes, reflash custom recovery. The stock recovery is still buggy. I used ROM Manager to flash Clockworkmod 6.0.1.0, and use its recovery.
-
I couldn't get any of the custom recoveries to stick after trying to install with Rom toolbox. It would go thru the process of installing but then boot back into the bad bootloader screen. I followed the WUG thread and he said there is a problem with the new Bootloader and to flash the old one. I did that and then installed TWRP thru RTBOX without a problem. For not knowing what I am doing I am getting pretty good at this. LOL
-
My unrooted Nexus 7 has not yet updated. In reading the instructions for forcing an update, I do not understand the statement that the date will show Dec 1969, as I do not see any date anywhere on the indicated screen. I also do not understand what can be repeated 4 times-- perhaps there is an unstated instruction to turn the N7 off and turn it back on?
-
My unrooted Nexus 7 has not yet updated. In reading the instructions for forcing an update, I do not understand the statement that the date will show Dec 1969, as I do not see any date anywhere on the indicated screen. I also do not understand what can be repeated 4 times-- perhaps there is an unstated instruction to turn the N7 off and turn it back on?
Did you force stop Google framework in Apps / all? 4 times meaning you might have to force stop and clear data several times @ Google Framework. The date you are looking for is in the About Tablet / System Updates at the bottom of the menu screen in Settings.
-
Re Step 4: How do you update SuperSU binaries, which app?
-
SuperSU now automatically updates binaries. If you are using superuser swipe right from the main screen and you will see the update option.
-
I have added the custom recovery option to the Guide.
S.Prime
-
I couldn't get any of the custom recoveries to stick after trying to install with Rom toolbox. It would go thru the process of installing but then boot back into the bad bootloader screen. I followed the WUG thread and he said there is a problem with the new Bootloader and to flash the old one. I did that and then installed TWRP thru RTBOX without a problem. For not knowing what I am doing I am getting pretty good at this. LOL
There it's a file that needs to be deleted before installing ClockworkMod recovery. This file prevents the bootloader from rewriting the recovery each time you turn it on.
-
I have added the custom recovery option to the Guide.
S.Prime
Thanks Prime.
-
Well, I finally ended up just using Wug's tool kit (V1.5.4) and going back to stock. It worked great and it'll be an interesting process getting it back to the way I want it. The only thing that didn't go as planned was it would not 'unlock' when I tried. I'll give it another try later today. I gave him a good donation for such an excellent program. So now I have 1.2 and a nice clean machine again. I bet my camera will even work now; I won't be uninstalling any factory apps though, maybe just freezing a few. Good learning experience! I didn't back up data so that will just be gone, but that's OK. I figure 90% of my apps are from GP so should be easy to just download them again. I got time... it's a toy.
Thanks for all the suggestions, one and all!
radio
-
My unrooted Nexus 7 has not yet updated. In reading the instructions for forcing an update, I do not understand the statement that the date will show Dec 1969, as I do not see any date anywhere on the indicated screen. I also do not understand what can be repeated 4 times-- perhaps there is an unstated instruction to turn the N7 off and turn it back on?
Did you force stop Google framework in Apps / all? 4 times meaning you might have to force stop and clear data several times @ Google Framework. The date you are looking for is in the About Tablet / System Updates at the bottom of the menu screen in Settings.
Thank you. The date shows up as "last checked for update" after you force stop Google Framework. The update arrived on my first attempt.
-
Glad to hear you succeeded, radio. Let us know if you now have a functional camera. For my own curiosity, let me know if you're able to boot into recovery, and if it's stock or custom.
-
Yeah tnx bird. Well yes, the camdamera does work now :) But, as I said in another post, I can's seem to unlock it with the toolkit. It is just the stock rom. Haven't tried any recovery... kinda scared to as I've never tried that....
r
-
My unrooted Nexus 7 has not yet updated. In reading the instructions for forcing an update, I do not understand the statement that the date will show Dec 1969, as I do not see any date anywhere on the indicated screen. I also do not understand what can be repeated 4 times-- perhaps there is an unstated instruction to turn the N7 off and turn it back on?
Did you force stop Google framework in Apps / all? 4 times meaning you might have to force stop and clear data several times @ Google Framework. The date you are looking for is in the About Tablet / System Updates at the bottom of the menu screen in Settings.
Thank you. The date shows up as "last checked for update" after you force stop Google Framework. The update arrived on my first attempt.
Nice!
-
Yeah tnx bird. Well yes, the camdamera does work now :) But, as I said in another post, I can's seem to unlock it with the toolkit. It is just the stock rom. Haven't tried any recovery... kinda scared to as I've never tried that....
r
When you say you can't unlock it. What do you mean exactly? Are you getting error messages or when you go thru the process the bootloader shows a Locked padlock.
-
That's right, it shows a locked lock.
-
The closed lock signifies that your bootloader is locked. If you restore the stock rom you will restore your device to factory state, therefore you will have to use the Toolkit to unlock the bootloader and root your tablet again.
-
Yes, that's what I attempted to do several times, but the lock shows up unlocked briefly, then when it finishes rebooting it turns up locked. That's what I tried with the toolkit. Seems like it should work...
r
-
Are you positive that the lock is locked? The padlock when unlocked only shows a little open space where the shackle locks into the body. I haven't read many posts about using the toolbox and not being able to unlock.
-
SuperSU now automatically updates binaries. If you are using superuser swipe right from the main screen and you will see the update option.
I have SuperSU PRO installed.
Any way of seeing if binaries have been updated?
-
Yes, that's what I attempted to do several times, but the lock shows up unlocked briefly, then when it finishes rebooting it turns up locked. That's what I tried with the toolkit. Seems like it should work...
r
I thought when locked there was no lock displayed.
I.E. The lock only shows on an unlocked device.
-
Yes, that's what I attempted to do several times, but the lock shows up unlocked briefly, then when it finishes rebooting it turns up locked. That's what I tried with the toolkit. Seems like it should work...
r
I thought when locked there was no lock displayed.
I.E. The lock only shows on an unlocked device.
CBers is correct, there is no lock on a locked device. Check again radio, it must be unlocked if there's a padlock on the Google splash screen.
-
Honestly, I rooted mine basically out of the box, so I have never seen it without the lock screen with the padlock open. So if the lock screen only shows on an unlocked bootloader, at this point radio should be able to install a super user app and updating the binaries should restore root.
-
SuperSU now automatically updates binaries. If you are using superuser swipe right from the main screen and you will see the update option.
I have SuperSU PRO installed.
Any way of seeing if binaries have been updated?
I will look at it on my tablet and see if there is. I have superuser on my Slll, which I am using now.
-
I got it after only doing the clear data force close twice only glitch I see is the clock on the lock screen is partially cut off
-
Yes, that's what I attempted to do several times, but the lock shows up unlocked briefly, then when it finishes rebooting it turns up locked. That's what I tried with the toolkit. Seems like it should work...
r
I thought when locked there was no lock displayed.
I.E. The lock only shows on an unlocked device.
That's why I was asking radio if he was sure that the lock was actually locked. I never saw that before.
-
Unlocking a device refers to enabling permissions to make changes to the bootloader. This includes the recovery. If you are able to enter Clockworkmod or TWRP, then you are most likely unlocked. A custom recovery cannot be installed on a locked device. This is our only concern with a locked device of you are running the stock ROM.
-
I'm sure he is mistaking the locked padlock on the security screen for his actually unlocked boot loader.
-
(http://i725.photobucket.com/albums/ww256/JayJ-1974/Nexus%207%20Forum/Nexus-7-Unlocked-500x323.jpg)
-
Yes, yes, yes, that's what it was. I'm very sorry to have started such a useless topic taking up everyone's time :-[
I'll try and think first, next time....
radio
-
We've all done equally embarrassing things, radio.
-
This is how we all learn. I learned a lot from this topic.