Hi, all.
Here's my situation. I got the 16GB eight days ago. Since I can return it to Google, it's going back (already have the RMA and UPS shipping label). I got the 32GB today at Staples. My 16GB is totally stock. I've been reading up on how to root it, but as I'd like to use mskip's Google Nexus 7 TOOLKIT, I was forced to wait, as the 16GB is at 4.1.2 JZO54K.
I don't have a ton of stuff to back up, at least data wise. I can use ES File Explorer to dump the APKs, but it sure would be nice to be able to do a full backup using Titanium or some such. This leads me to wonder....
Should I wait for mskip to support JZO54K, then root the 16GB, back it up, and then unroot it, as I assume that's what Google expects? If I'm not mistaken, the Toolkit will allow me to unroot it. If it turns out I can't wait that long, as I'll need to ship it back, will the built-in backup suffice? I read it's just for Google apps. In the end I don't mind starting mostly from scratch, as I've only had it for eight days.
Moving to the 32GB, I definitely want to root it, as I really want to add CifsManager. I've got a couple NASes, and it would be nice to have apps access them natively, rather than going through ES File Explorer's SMB mounts. From what I've read, it should come with 4.1.1. Here's how I think I should proceed:
* Refuse the OTA update
* Use the Toolkit to root the 32GB
* Install OTA Rootkeeper app and use it to backup su
* Install the OTA update
* See if I still have root access; if not, use OTA Rootkeeper to correct that
* Install CifsManager
and restore whatever I manage to backup in whatever form that takes.
Is that plan sound? If not, how can it be improved?
I really appreciate any advice!
Cheers.
Here's my situation. I got the 16GB eight days ago. Since I can return it to Google, it's going back (already have the RMA and UPS shipping label). I got the 32GB today at Staples. My 16GB is totally stock. I've been reading up on how to root it, but as I'd like to use mskip's Google Nexus 7 TOOLKIT, I was forced to wait, as the 16GB is at 4.1.2 JZO54K.
I don't have a ton of stuff to back up, at least data wise. I can use ES File Explorer to dump the APKs, but it sure would be nice to be able to do a full backup using Titanium or some such. This leads me to wonder....
Should I wait for mskip to support JZO54K, then root the 16GB, back it up, and then unroot it, as I assume that's what Google expects? If I'm not mistaken, the Toolkit will allow me to unroot it. If it turns out I can't wait that long, as I'll need to ship it back, will the built-in backup suffice? I read it's just for Google apps. In the end I don't mind starting mostly from scratch, as I've only had it for eight days.
Moving to the 32GB, I definitely want to root it, as I really want to add CifsManager. I've got a couple NASes, and it would be nice to have apps access them natively, rather than going through ES File Explorer's SMB mounts. From what I've read, it should come with 4.1.1. Here's how I think I should proceed:
* Refuse the OTA update
* Use the Toolkit to root the 32GB
* Install OTA Rootkeeper app and use it to backup su
* Install the OTA update
* See if I still have root access; if not, use OTA Rootkeeper to correct that
* Install CifsManager
and restore whatever I manage to backup in whatever form that takes.
Is that plan sound? If not, how can it be improved?
I really appreciate any advice!
Cheers.
