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: CBers on November 13, 2012, 04:23:36 AM
-
According to the Android Police site, Google have started rolling out JB 4.20.
More information here (http://www.androidpolice.com/2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/).
If rooted and you're feeling brave (!), download is here (http://android.clients.google.com/packages/data/ota/google_nakasi/094f6629314a.signed-nakasi-JOP40C-from-JZO54K.094f6629.zip).
-
I've downloaded the update and installed on my rooted Nexus 7 without a hitch:
(https://dl.dropbox.com/u/8367652/Capture311.JPG)
-
The DEVELOPER OPTIONS menu seems to have been removed under JB 4.2 !!
Not sure how you enable USB DEBUGGING now.
I lost root when I updated, but VOODOO ROOT KEEPER added it back.
-
The DEVELOPER OPTIONS menu seems to have been removed under JB 4.2 !!
Not sure how you enable USB DEBUGGING now.
OK, seems it's fairly easy to enable DEVELOPER OPTIONS under JB 4.2:
1. As usual, goto Settings -> About Phone.
2. Goto “Build Number” at the end of the Scroll list.
3. Tap on “Build Number” for 7 times. While typing at the third times, you should see prompt message to indicate you that 4 more taps to go to developer options.
4. Continue 4 more taps.
5. You are now done and go back to the Setting page.
6. You should see Developer Option appear on your setting list now.
With Developer Option appeared, you can enable the USB debugging mode for future flashing and development work.
Thanks to theandroidrom.com (http://theandroidrom.com/how-to-enable-developer-options-on-android-4-2-jelly-bean/) for this.
-
Ok here's a question I've tried installing clock work mod using rom toolbox and it says installed successfully but when I try to boot it it isn't installed it goes to stock recovery now I've down this what seems like a million times on my galaxy nexus without issues and I don't have access to root toolkit on a pc right now
-
Thanks CBers,
I'm running 4.2 now!
-
Ok here's a question I've tried installing clock work mod using rom toolbox and it says installed successfully but when I try to boot it it isn't installed it goes to stock recovery now I've down this what seems like a million times on my galaxy nexus without issues and I don't have access to root toolkit on a pc right now
Are you rooted ??
If so, you only need to download the ZIP posted above and flash it via recovery. I use TWRP.
I used WUGFRESH's Nexus Root Toolkit (http://forum.xda-developers.com/showthread.php?t=1766475) to root mine.
If you are not rooted, then you need to wait for the OTA update.
-
Thanks CBers,
I'm running 4.2 now!
Cool 8)
Did you enable the DEVELOPERS OPTIONS menu OK ??
-
Ok here's a question I've tried installing clock work mod using rom toolbox and it says installed successfully but when I try to boot it it isn't installed it goes to stock recovery now I've down this what seems like a million times on my galaxy nexus without issues and I don't have access to root toolkit on a pc right now
Try using ROM Manager instead. The options at the very top let you install the latest CWM recovery and verify. Of you have any more questions or issues, let me know.
-
Yes, I was able to enable developer options. Now I need to restore root. I lost it, and OTA Rootkeeper isn't seeing Super SU (the only box checked is '/system supports root protection.' Super SU can't update successfully..
Did you have similar issues restoring root? How did you get it back?
-
I had VOODOO ROOT KEEPER installed beforehand and just re enabled afterwards.
-
Ok thanks for the help but I got rom toolbox to work and it even fixed it from flashing cwm touch even fixed root and kept it from flashing stock recovery now the first thing I noticed is I have no settings menu button anymore and the lock screen clock looks dumb as hell the main thing is how to i access the system settings menu
-
Yes, I was able to enable developer options. Now I need to restore root. I lost it, and OTA Rootkeeper isn't seeing Super SU (the only box checked is '/system supports root protection.' Super SU can't update successfully..
Did you have similar issues restoring root? How did you get it back?
Open Super SU and update the binaries and OTA Rootkeeper should see the Super SU app.
-
Wow I didn't realize that there's a separate drop down on the right side of the screen
-
Open Super SU and update the binaries and OTA Rootkeeper should see the Super SU app.
I get an 'Installation failed' message when trying to update the binaries.
-
Wow I didn't realize that there's a separate drop down on the right side of the screen
And multi user access.
-
Open Super SU and update the binaries and OTA Rootkeeper should see the Super SU app.
Where is that option? I have it installed but can't find where you update the binaries.
-
Did you check OTA RootKeeper before you ran the 4.2 update, to make sure all 4 boxes were checked and the Root was backed up?
-
Prime, yes I did, since I was expecting to lose root during the upgrade.
CBers, Super SU gave me a dialogue box asking if I wanted to update the binary when I tried to run it. When I tried the update, the installation failed - repeatedly.
I chose to clean the system to re-download Super SU from Google Play. It said it would take a few seconds, and would close the Super SU app if successful. It wasn't successful.
So I went to Google Play, and uninstalled Super SU. When that completed, instead of a choice to install the app, I got update and open options in GP. I chose update, which took me to the Super SU update binary dialogue box. Again, the installation failed. Now I have no rooted apps showing in the Super SU apps tab.
It looks like I'm going to have to re-root and restore, and/or reinstall apps manually.
-
Sorry to hear about your woes birdastrompgman.
I wonder if anyone else has tried.
-
Seems to be a DAYDREAM function under the DISPLAY settings.
Acts a bit like a screen saver on a PC.
Read here (http://support.google.com/nexus/bin/answer.py?hl=en-GB&p=settings_dreams&answer=2818748&rd=1) for more information.
-
Prime, yes I did, since I was expecting to lose root during the upgrade.
CBers, Super SU gave me a dialogue box asking if I wanted to update the binary when I tried to run it. When I tried the update, the installation failed - repeatedly.
I chose to clean the system to re-download Super SU from Google Play. It said it would take a few seconds, and would close the Super SU app if successful. It wasn't successful.
So I went to Google Play, and uninstalled Super SU. When that completed, instead of a choice to install the app, I got update and open options in GP. I chose update, which took me to the Super SU update binary dialogue box. Again, the installation failed. Now I have no rooted apps showing in the Super SU apps tab.
It looks like I'm going to have to re-root and restore, and/or reinstall apps manually.
Bird, weren't your running a custom ROM (Paranoid Android) and did you return to a stock ROM before the update? If not I suspect this is the source of your lost root.
S.Prime
-
The only problem I had when updating was that I had previously turned the Asus keyboard to a user app to stop it refreezing so I could try it, had changed it back to a system app and refrozen it but the update zip wouldn't take stating that the fail was because of XT9IME. apk (Asus keyboard) so I replaced the apk and all was good.
Great thread CBers, your a true part of the community. A thumbs up I think...
-
If it is at all relevant I installed the touch version of cwm available from rom toolbox pro and I noticed that when it was done and I hit reboot it went to another screen and informed me that root might be broken and would attempt to fix it I chose yes and it worked great for me... So for those still looking to upgrade if you haven't done so I recommend using that option if your worried about losing root
-
My tale of woe continues. Prime, I did return to stock Android 4.1.2 before flashing the 4.2 ROM. 4.2 is running fine (I like the new scrolling owner info message).
I've lost the CWM custom recovery during the re-rooting attempt.
I couldn't get rooted, because Wugfresh's toolkit doesn't unlock the bootloader. It flashes a quick message about that, but skips or fails the attempt. Instead of getting an unlock option in the bootloader, it simply goes to the bootloader and reboots. I had to grab a PrtScr capture of the message, and paste the screen capture into Paint, to be able to read the message.
(http://i1179.photobucket.com/albums/x397/BestmpgxB/2012/bootloaderwontunlock.jpg)
-
I've tried changing the device type to Nexus 7 other, and N7 4.1.2, but that didn't help. I've tried installing both the option #1 and option #2 device drivers, and that didn't help either.
-
You can unlock the bootloader manually. In order to do so, you must have the fastboot drivers installed. These are included in the toolkit folder typically. Open the toolkit folder and then open a command window. You should be able to type "fastboot" and hit enter to see a list of commands. If you do not get a response, you are missing the drivers. Maybe download an older version of the toolkit.
If you do get a response, boot the N7 into fastboot mode and type into the command window "fastboot oem unlock" hit enter. When the device finishes use the command "fastboot reboot"
-
Oh no. Not this again. Lol. I think I am going to wait for the OTA.
Unlock bootloader? So installing this update entails wiping your whole system? I'm lost again. I thought you could just flash it like a rom.
-
Great thread CBers, your a true part of the community. A thumbs up I think...
Thanks :)
-
By the way, losing custom recovery with the toolkit happened last time with WF. I thought there would be a fix by now but I believe he suggested flashing the older bootloader.
-
Here goes nothing. I'm just going to download and flash it.
-
Here goes nothing. I'm just going to download and flash it.
Fingers crossed for you :)
-
I'm all good . 4 checks on Root keeper and Super Su is updated. I downloaded using your link CBers and flashed using a Quick Boot and TWRP.
Cheers brother. TY
-
Glad it worked, enjoy 8)
-
I've had no issues. Smooth as silk. I'm trying to help Bird get to the bottom of his issue.
-
Bird. I know you run different ROMS so that adds variables to the mix. Hence the going back to stock. I never messed with any aftermarket Roms except with my phone. So davlik and such are kind of foreign to me. You mentioned problem with recovery WuG had suggested flashing the older bootloader .
-
There us an issue with manually installing a custom recovery on 4.0+. The stock recovery will reinstall after a reboot unless the command files for this action are removed. The toolkits do this for you. New versions of CWM will prompt for this after flashing an update that changes there bootloader. CWM will also prompt to restore root.
-
You talking about the build.prop file?
-
No there's a file that is completely deleted.
It is named:
recovery-from-boot.p
Located in the system folder.
-
You beat me to posting the name.
Had to delete it when going from 4.1.1 to 4.1.2, but not today.
Thought it was \system\recovery-from-boot.p though.
-
You're right, it is system folder. Post edited.
-
Thanks to all - Loocid, bjs, CBers, Prime, et al.
I had fastboot from Wugfresh's 1.5.2 toolkit, and ran it from a command prompt like Loocid suggested. It said "INPOBootloader is already unlocked." So I clicked on the Root button on the v. 1.5.5 toolkit, and it seemed to complete the process.
But I'm still stuck on the failure to update the Super SU binaries. Suggestions?
(http://i1179.photobucket.com/albums/x397/BestmpgxB/2012/rootsuccess.jpg)
-
I thought SuperSU updates the binaries automatically?
-
I thought SuperSU updates the binaries automatically?
When I went from 4.1.1 to 4.1.2 with WF 1.5.5 last week I had to uninstall and reinstall SuperSU to get the binary update offer. May help here. I am watching how this plays out in 4.2. Fair winds...
-
The only problem I had when updating was that I had previously turned the Asus keyboard to a user app to stop it refreezing so I could try it, had changed it back to a system app and refrozen it but the update zip wouldn't take stating that the fail was because of XT9IME. apk (Asus keyboard) so I replaced the apk and all was good.
Great thread CBers, your a true part of the community. A thumbs up I think...
Ran into the same problem. Can you detail exactly what you did?
-
Do you have OTA installed and giving you 4 checks? Rooted and backed up SU? If so super user will allow me to update the binaries.
-
Can't post pics. Damn.
-
Ran into the same problem. Can you detail exactly what you did?
I simply placed a copy of the Asus keyboard (XT9IME.apk) in the following file path...
/system/app
Booted into recovery and flashed the update, it flashed fine and I'm now running 4.2.
Here (http://db.tt/MdlWV153) is a copy of the XT9IME.apk in my Dropbox.
-
Ran into the same problem. Can you detail exactly what you did?
I simply placed a copy of the Asus keyboard (XT9IME.apk) in the following file path...
/system/app
Booted into recovery and flashed the update, it flashed fine and I'm now running 4.2.
Here ([url]http://db.tt/MdlWV153[/url]) is a copy of the XT9IME.apk in my Dropbox.
Thanks. Going to try it now.
Update. Got it to work. Thanks a lot.
-
To reiterate, Super SU asks if I want to update binaries when I open it, and the 'Installation failed!'
Voodoo OTA Rootkeeper show only the '/system supports root protection' box checked. The hangup is Super SU binaries not updating.
I tried Super SU's Reinstall option to clean for reinstallation from Google Play. It said it would exit the program if successful. It didn't and wasn't.
I uninstalled Super SU and reinstalled it. Instead of leaving me at an uninstall or open choice in Google Play, it left me at an update or open choice. Update failed.
-
I installed Superuser, since Super SU wouldn't update. That resulted in the first check box also being checked in Voodoo OTA Rootkeeper. Two attempts at rooting (using the Root button in the 1.5.5 toolkit) failed to gain root. I've tried running Busybox, but it fails since the system isn't rooted.
-
Go to www.skipsoft.net (http://www.skipsoft.net) and download the latest version of the "Nexus 7 Toolkit", it claims to support 4.2. The developer is actively supporting the Nexus 7 and I really like his approach.
-
Not rooted, the ota popped up and installed without a hitch, no problems.
-
Anyway to force update yet for us non-rooted folks ?
-
Did anyone else lose the camera app with the update?
-
Thumbs up, Prime! That Nexus 7 Toolkit did the job for me. Once I'd lost root, that's a cited reason for SuperSU failing to update its binary file(s). I'd also possibly created a conflict with Superuser and SuperSU binaries.
I rooted in bits and spurts, initially rooting with Superuser. Voodoo OTA Rootkeeper only protects with SuperSU, so even though I was rooted with Superuser, I only had three checked boxes in Rootkeeper, and Busybox (which was already installed) wouldn't install its apps. So, I cleared as many remnants of SuperSU as I could, removed Superuser and Busybox. The Nexus 7 Toolkit pushed SuperSU and Busybox on my N7, and i finally got rooted again.
Since my Bootloader was always unlocked, I didn't lose any data, pictures, etc.
-
Glad you're now sorted birdastrompgman.
-
Thanks. Going to try it now.
Update. Got it to work. Thanks a lot.
Glad it worked for you...
-
Thanks CBers,
I was confident I'd regain root, because the users here were my team. Thanks to you all for your support and suggestions.
-
@ bird
Glad it worked out. Skip has actively supported the evolution of the Nexus 7 with his toolkit. Also, I think your problem lay with the conflicts between superuser and super su, but notably I have used superuser successfully with OTA Rootkeeper on other devices.
-
Glad you are up and running again.
Prime thanks for that link. Nice to have another tried and true option.
-
Prime thanks for that link. Nice to have another tried and true option.
+1 for that.
Is skip on xda-developers forum?
-
Guys I really need your help
I updated to 4.2 via OTA, my N7 still unlock but lost my root
I re-rooted with NRT, it recognize my 32GB external flash drive but can not read any files (it shows 0 files). The flash drive was working fine BEFORE the OTA update
I decide to uninstall Stickmount and reinstall it
But when I go to Play Google website I can not download/install it, it keeps saying error from server.
I try to download/install some other apps and got the same error
Anyone encounter same problem ?
-
Prime thanks for that link. Nice to have another tried and true option.
+1 for that.
Is skip on xda-developers forum?
Yes it is Mark Skippen and this is the link at xda-developers Here. (http://forum.xda-developers.com/showthread.php?t=1809195)
-
Guys I really need your help
I updated to 4.2 via OTA, my N7 still unlock but lost my root
I re-rooted with NRT, it recognize my 32GB external flash drive but can not read any files (it shows 0 files). The flash drive was working fine BEFORE the OTA update
I decide to uninstall Stickmount and reinstall it
But when I go to Play Google website I can not download/install it, it keeps saying error from server.
I try to download/install some other apps and got the same error
Anyone encounter same problem ?
Goto Settings > Apps > swipe from left to All Apps > scroll to Google Play Store and tap to open > Tap "Force Close" then tap "Clear Data and Cache" > Open Play Store and enter requested information and try to download your app.
-
Thanks SPrime
I try and still get the error "Stickmount can not be downloaded due to an error. Error retrieving information from server (RPC:S-5:AEC-0)
-
Have you tried opening Play Store on a PC and selecting your Nexus 7 as the target for the install. Also, this the XCA-developers link for "Stickmount" Here. (http://forum.xda-developers.com/showthread.php?t=1400034)
-
I've flubbed up again... while playing a game the OTA came. So I started the update and it failed. :( Since the last update (4.1.2) I was careful NOT to delete any stock programs, thinking that maybe that would allow the next OTA to work for me; but alas, no such luck... I got Andy with the red exclamation point.
Can I force the update to come again with the same procedure that I used when 4.1.2 failed on me? Do I have to go back to locked un-rooted to have the update work??
Thanks for any clarification!
r
-
Have you tried opening Play Store on a PC and selecting your Nexus 7 as the target for the install. Also, this the XCA-developers link for "Stickmount" Here. ([url]http://forum.xda-developers.com/showthread.php?t=1400034[/url])
I was able to install (side loading) Stickmount. Google Play kept saying that this app is already installed and would not allow re-installing on N7
After installing stickmount , it recognize the flash drive (OTG) Fat32 but said that there is zero file. This flash drive is readable on the PC. Both the OTG & Flash drive were working fine before 4.2 OTA update
Thanks for your patience with this newbie
-
Is it possible that there is an option in the DEVELOPERS OPTION menu you need to enable?
-
Thank You for all of your help :-*
I got frustrated :'( and use NRT to re-install stock image 4.1.2 and restart all over from the scratch. What a pain but I do need to use my external flash drive for movies etc...
I now updated to 4.2 :)
Can I use NRT 1.5.5 to root and unlock ? since NRT has only 4.1.2 firmware ?
-
Re: Google Play, removing your Google account from /Settings/Accounts & Sync/ should fix it.
You should be able to use NRT 1.5.5 to root and unlock.
-
Stickmount is broken in 4.2, probably due to the virtual directory structure for multiple users. Let's hope Chainfire fixes it quickly. There are multiple reports at xda and I can verify that mine shows an empty usb drive.
IT Service Professional - I Just Want a Device to Be Productive
-
Re: Google Play, removing your Google account from /Settings/Accounts & Sync/ should fix it.
You should be able to use NRT 1.5.5 to root and unlock.
I was able to unlock with NRT 1.5.5 but can not root my N7 4.2.
It got stuck at the TRWP screen
-
Yeah, I tried using Ntool kit v1.5.5 and now I'm stuck on "Waiting for your device to finish booting back up..." which has been on my pc screen for 15 mins now. Also I'm on the "Start" screen with Andy on his back and his door open. How do I get out of this seeming lock-up?? Anyone??
radio
*Just now tried unplugging the pc from tab and nothing changed !(?) How to get back to normal??
r
-
Yeah, I tried using Ntool kit v1.5.5 and now I'm stuck on "Waiting for your device to finish booting back up..." which has been on my pc screen for 15 mins now. Also I'm on the "Start" screen with Andy on his back and his door open. How do I get out of this seeming lock-up?? Anyone??
radio
On my N7 I disconnect the usb cable, turn it off and restart.
-
Thanks, I'll try it...
* Ah, OK back to normal. Just can't shut down the tool kit on the pc now. Think I'll just be content with this version for a while... it works.
radio
-
Re: Stickmount. Try USB Mass Storage Watcher. I broke my USB-OTG cable, and can't test for USB flash drive R/W with 4.2.
Radio and Dominic, try the Nexus 7 Toolkit mentioned by Prime, above. That's how I got rooted again.
-
Thanks, I'll try it...
* Ah, OK back to normal. Just can't shut down the tool kit on the pc now. Think I'll just be content with this version for a while... it works.
radio
CTRL-ALT-DEL on the PC brings up Task Manager, and you can end the Toolkit tasks from Task Manager.
-
Re: Stickmount. Try USB Mass Storage Watcher. I broke my USB-OTG cable, and can't test for USB flash drive R/W with 4.2.
Radio and Dominic, try the Nexus , above. That's how I got rooted again.
I try the Nexus 7 Toolkit mentioned by Prime but I don't think I got it rooted. Is there anyway to check whether the N7 rooted or not ?
I install USB Mass Storage but unable to check it out because it requires rooted N7
-
Download RootChecker from Google Play.
Sent from my SCH-I535 using Tapatalk 2
-
I use Voodoo OTA Rootkeeper to check for root.
-
It has been confirmed that Stickmount is not working with this new update. Unless you over rode it in SU settings Superuser will give you a heads up when starting any root necessary app like Titanium, Goo, Root Explorer etc..
Sent from my Nexus 7 using Tapatalk 2
-
I use Voodoo OTA Rootkeeper to check for root.
The OTA Rootkeeper says that my N7 is rooted but the USB Mass Storage still not able to mount the OTA flash drive
Install USB Mass Storage Watcher and it says that the N7 not rooted
I also install USB Helper, it would not read the usb and said that the N7 is not rooted
So I suspect that the N7 is not rooted that is why both aaps can not read the usb drive
==========
Additional info
I install Nexus Media Importer and I was able to play movie on the USB drive.
-
I use Voodoo OTA Rootkeeper to check for root.
The OTA Rootkeeper says that my N7 is rooted but the USB Mass Storage still not able to mount the OTA flash drive
Install USB Mass Storage Watcher and it says that the N7 not rooted
I also install USB Helper, it would not read the usb and said that the N7 is not rooted
So I suspect that the N7 is not rooted that is why both aaps can not read the usb drive
==========
Additional info
I install Nexus Media Importer and I was able to play movie on the USB drive.
Stickmount/ usb mass storage does not work. Good news is it sounds like you are rooted
Sent from my Nexus 7 using Tapatalk 2
-
I think you're rooted, but the same 4.2 per mount issue affecting Stickmount is also affecting the other USB app.
Sent from my Nexus 7 @ 49.6 mpg
-
Hi bird
I've just noticed that you retired for 7 years, me 6.5 years and loving it too
;)
-
not happy at all with the new update 4.2 on my nexus 7, the quick setting is gone and i have to manually go to the menu and hit the setting, the photo spehere in camera is not working at all and says it's not supported on your device although i believe it's an stupid idea for such a tablet with no rear camera, the only change i realized so far is the clock widget which i am not interested in and about the performance and stability i have no idea yet, i am thinking about to downgrade to 4.1.2 if these weird problems persist and i couldn't get any help or solutions, here's my "thumb down" for Mr google for jelly bean 4.2
-
I agree, can you downgrade the nexus?
Sent from my GT-I9000 using Tapatalk 2
-
not happy at all with the new update 4.2 on my nexus 7, the quick setting is gone and i have to manually go to the menu and hit the setting, the photo spehere in camera is not working at all and says it's not supported on your device although i believe it's an stupid idea for such a tablet with no rear camera, the only change i realized so far is the clock widget which i am not interested in and about the performance and stability i have no idea yet, i am thinking about to downgrade to 4.1.2 if these weird problems persist and i couldn't get any help or solutions, here's my "thumb down" for Mr google for jelly bean 4.2
Do some more research before totally dismissing the improvements with 4.2
The quick setting is not gone. There are now two pulldown menus, a right and left. The quick settings is on the right
Sent from my DROID RAZR using Tapatalk 2
-
For me, part of the fun of having this device is upgrading and Discovering nuances and in some cases bugs. It can be annoying losing capabilities that you did have when upgrading but I try and take that with a grain of salt and a little patience. There are developers working hard right now trying to fix things and come up with new ideas and ways to enjoy your Nexus. I heard that their going to be making a new bulletproof glass model and one that you can actually remove all the critical system apps and folders and still get along with no errors.
Seriously speaking, If you choose to go back, I think you can flash back with one of the toolkits.
Sent from my Nexus 7
-
Anyway to force update yet for us non-rooted folks ?
Ditto on that !!!!
-
Anyway to force update yet for us non-rooted folks ?
Ditto on that !!!!
Yes. If you go into settings apps Google framework and clear data and force close Google framework. Then check system updates. It should get forced to you. BTW, messing with Google framework has been said to carry some risk although I never had any problems.
-
Yes. If you go into settings apps Google framework and clear data and force close Google framework. Then check system updates. It should get forced to you. BTW, messing with Google framework has been said to carry some risk although I never had any problems.
Damnation, you beat me to it...lol
-
Lol. Sorry.
-
Hi bird
I've just noticed that you retired for 7 years, me 6.5 years and loving it too
;)
Two more weeks, and I'll be starting my 8th year of retirement.
I got my replacement USB-OTG cables (3) today. I can't access my flash drive using 4.2 without Stickmount or the other USB mounting apps working due to the per-process mount issue. Couple that with the Nandroid restore issues caused by the directory emulation situation, and I'm going back to Paranoid Android based on 4.1.1.
Sorry, you non-rooted folks. I don't think you can go back/downgrade.
-
Anybody can downgrade by flashing a previous factory image...
Nexus 7 4.1.2 JZO54K factory image can be found here (https://developers.google.com/android/nexus/images).
-
I wasn't sure. Thanks for the clarification, JJ.
Sent from my Nexus 7 using Tapatalk 2
-
No problem mate, it's part of the beauty of a Nexus device.
-
Anybody can downgrade by flashing a previous factory image...
Nexus 7 4.1.2 JZO54K factory image can be found here (https://developers.google.com/android/nexus/images).
I downloaded this but TWRP doesn't show it in the folder. I was going to go back and try and fix my sound issue. I thought it was going to be the same process as downloading and installing the 4.2 update.
-
Factory images need to be flashed with NRT or using ADB...
-
Factory images need to be flashed with NRT or using ADB...
I see. I thought that the download of the recent upgrade was a factory image. I need to do some more reading. I guess I need to use rom tb.
-
No the recent update was an update zip, just do a batch backup on TB and backup your internal memory because flashing the factory image will completely wipe your N7...
-
Looks like there is a new version of TWRP for JB 4.2.
http://teamw.in/project/twrp2/103
Can be installed via GOO MANAGER.
I have installed it, but not yet tried it myself.
-
Thanks JJ
-
Wait, I'm not sure NRT can restore 4.1.2 from 4.2 because of the multiuser features and the new layout of the internal storage, I think it can be done with ADB but not the toolkit atm...
-
I just went from 4.2 to 4.1.2 using Mark Skippen's Nexus 7 Toolkit. I lost root, and had to go through the rooting process again, but I'm back to 4.1.2, and Stickmount sees my USB flash drive.
-
You got a link to that toolkit please bird?
Has your internal memory been restored to it's original format before 4.2??
-
Looks like there is a new version of TWRP for JB 4.2.
[url]http://teamw.in/project/twrp2/103[/url]
Can be installed via GOO MANAGER.
I have installed it, but not yet tried it myself.
thanks Cbers. Installed and backed up. I can see my Nandroids in folders as well. Cheers.
-
http://link.tapatalk.com/api/click?key=a7e5ffb24b9e84f4f4f6bbd88aa4e5b8&out=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1809195&loc=http%3A%2F%2Fwww.Nexus7Forum.com&subid=6d6fe678a03318543326709b1cc41bfd (http://link.tapatalk.com/api/click?key=a7e5ffb24b9e84f4f4f6bbd88aa4e5b8&out=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1809195&loc=http%3A%2F%2Fwww.Nexus7Forum.com&subid=6d6fe678a03318543326709b1cc41bfd)
M skippen Toolkit
-
Info at this link, (http://www.skipsoft.net) JJ. Yes, I was left with my OEM 5.92gb free storage, and the 4.1.2 directory structure.
-
Thanks guys...