Hey guys just received my n7 yesterday and am very pleased with this, however I have some questions.
Does rooting (only) removes your OTA updates access? I also own a Galaxy S4 (rooted) and I can't get OTA, it says it's modified, but I did flash a custom update on it and kernel. So if I just root my n7, and not flash anything, I will still get OTA's correct? I just want to use some apps which requires root access and not planning to flash a custom rooms or anything. Thanks for any help.
Sent from my Nexus 7 using Tapatalk 4
Mine is always rooted, and I get all OTAs.
Sent from my Nexus 7 using xda app-developers app
You just need to have the stock recovery to receive OTAs.
Username invalid said:
You just need to have the stock recovery to receive OTAs.
Click to expand...
Click to collapse
So if I have twrp installed, i won't receive them?
Sent from my Nexus 7 using Tapatalk 4
Takes 10 seconds to reflash the stock recovery.
UPDATE: SuperSU-v1.55 added the fix for the OTA update issue, so this post is no longer necessary unless you are using an older version of SuperSU
This post also applies to JSS15Q update.
I actually went through and tested JWR66N rooted with SuperSU and the JSS15J OTA update. I expected it to work but it exited with an error.
Ironically the JSS15J OTA actually did patch every single file successfully but near the end while setting permissions, it came up with an error, so after reboot you'll actually be running with all JSS15J rom files, except your build will still say JWR66N, you'll still be running the JWR66N recovery, and you'll still be running the 3.05 bootloader.
I tracked down the issue and put together a fix for it. If you want, it is attached to this post. You just run it after installing SuperSU, so basically:
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip (SuperSU v1.55 or greater incorporates the OTA fix)
install UPDATE-SuperSU-v1.55.zip
install UPDATE-SuperSU-ota.zip (can be chain installed, just make sure you choose to install it 2nd)
reboot
You'll need to redo these steps (both the installs) after you receive the OTA to preserve root and ability to receive future OTAs.
Also as others have mentioned it is best to be running stock recovery (which the above commands will allow you to do because twrp is never flashed on the tablet) I've attached the stock recovery for JSS15J in case someone needs it.
If you make ANY modifications or delete files from the stock ROM with your new root privileges, then you will greatly increase the chances of the OTA failing. Adding new files is normally fine.
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Sent from my Nexus 7 using xda app-developers app
rmm200 said:
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Click to expand...
Click to collapse
On some platforms, especially when flashing bootloaders and/or radios, the stock recovery pulls some funky maneuvers to get that done. Often custom recoveries are not privy to those maneuvers. Also sometimes custom recoveries will experiment with custom kernels which don't always have the bootloader and/or radio devices mapped the same as the stock kernel. This can lead to problems to.
Thus it is safest to use stock recovery to flash OTAs.
I have flashed the complete JSS15J OTA except for the bootloader part using TWRP and it works ok. All the ROM files are patched.
I just didn't feel like risking my tablet with the bootloader flash portion of JSS15J OTA using twrp. It might work fine. I just know from the past the potential for issues are higher in that section of the OTA flash.
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?
It was common on other platforms I've used, but I don't know about here.
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically). I have been installing OTA updates on rooted Nexus devices with custom recoveries since the Nexus One, and assuming the new Nexus 7 works the same way, the following applies:
If you are running stock ROM, your deivce will receive the notification and download the update, even if rooted
If you are running stock recovery, the update will install automatically as normal
If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
If you have modified files in /system, the OTA update is pretty much guaranteed to fail regardless of which recovery you use
If you successfully install the OTA update, you will no longer have root, so flash SuperSU using a custom recovery after the OTA update installs
Also:
You can always look for the OTA zip URLs on XDA and just download the update yourself to flash if you don't want to wait for it to come to your device (this is what I always do)
You can flash factory images instead of the update, without losing data (see other threads for how)
If you want to keep stock recovery installed, you can always use fastboot to boot a custom recovery without flashing it, in case you ever need it
The above is accurate and correct as far as I'm aware from my own experience over the years with Nexus devices. I'm sure someone will be happy to correct me if anything is wrong Hope this helps.
phazerorg said:
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically).
Click to expand...
Click to collapse
I thought the same about root not blocking the OTA update install from being successful, but that was with years of using superuser.
With SuperSU (I am not sure which version introduced it) they set the immutable flag on a file in almost every OTA. I believe this is to support some OTA survival mode. This causes the OTA to fail in the section where it sets permissions. All the files are patched at that point, but the build.prop hasn't been modified to reflect the new version # and the bootloader and recovery haven't been flash.
You'll essentially be running JSS15J but your software will report it is on JWR66N, your bootloader wouldn't have been patched, and you would be running JWR66N recovery.
TheAltruistic said:
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?
Click to expand...
Click to collapse
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2
nolook said:
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2
Click to expand...
Click to collapse
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
Titanium backup is an app, I assume with files he is targeting e. G. Config files.
Sent from my Nexus 7 (2013)
Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
It means don't modify or delete any files in /system
Don't remove a system app that shipped with the tablet. You can install a new version as that just hides the one in /system, but if you remove or modify the original, then the OTA will very likely fail (depending on how complex the OTA is)
Adding files is ok.
Alright, so here's my scenario. Hopefully someone can tell me what should happen:
I am running the stock ROM on my Nexus 7 (2013), but I have ClockWorkMod Recovery installed and I'm using Koush's Superuser app for root permissions. The only system file that I think I have changed is my hosts file because of Adaway. That is easily reverted, though.
So can I just download the OTA, install it manually from the custom recovery (flashing the update.zip file), and then re-flash Koush's superuser app back onto the device?
Will that go smoothly, and will the newer build number be accurately reflected in my About Phone afterward?
(that last part is just my OCD talking)
phazerorg said:
:
[*]If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
Click to expand...
Click to collapse
This was very helpful, and this is the category i fall in. However, i have installed a kernel. does that change anything?
So basically what you are saying is this, with my current set up:
1 - i will get the update, it will download, but wont install. I should boot into TWRP and install the file that way. Correct? Where is the downloaded file stores?
2 - I can just wait for the download to be posted on here, and just install via twrp.
3 - either way, after installing it, i will lose root. I should then boot into twrp and flash supersu.
Correct?
Theoretically it could work. I believe the flash has worked with twrp.
Personally I always put stock recovery back to flash ota's though especially if there is a bootloader (or radio if you have a mobile version) because on some platforms they involve special procedures that may not be in the custom recovery.
On nexus it looks like it will work with custom recovery but it takes so little effort to put stock recovery back I just do it automatically.
Having said that, I've seen one person post it worked on twrp but haven't read an experience on cwm. Not saying it will or won't work.
If we are running the stock ROM, but have it rooted with the custom recovery, why cant we just use Wegfresh's nexus toolkit to Unroot and image using the updated IMG file?
Then go through and use it to recreate the root\custom recovery again?
Related
Noticed a new build was released for OTA. Doing a little research I discovered it won't work while rooted.
Question being, what's the easiest way to update? Temporarily run custom recovery and flash it? I don't want to loss root access or any data. If needed I'll re-root again, but rather not.
Sent from my Nexus 7 using xda app-developers app
datallboy said:
Noticed a new build was released for OTA. Doing a little research I discovered it won't work while rooted.
Question being, what's the easiest way to update? Temporarily run custom recovery and flash it? I don't want to loss root access or any data. If needed I'll re-root again, but rather not.
Click to expand...
Click to collapse
There are many ways to accomplish the same end goal.
You can actually install the OTA while rooted. Just need to run the small fix in this post:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
Rerooting on this device is super simple.
There are also other options like flashing the factory images or one of the pre-rooted odexed/deodexed repackaged mostly stock ROMs. You can find them described here:
http://forum.xda-developers.com/showthread.php?t=2415497
So just temporarily run custom recovery then flash the update? but where can I download the latest OTA update?
Sent from my Nexus 7 using xda app-developers app
datallboy said:
So just temporarily run custom recovery then flash the update? but where can I download the latest OTA update?
Click to expand...
Click to collapse
You need to run the fix I mentioned above OR unroot BEFORE installing the OTA or the OTA will fail near the end.
You can find the OTA here:
http://forum.xda-developers.com/showthread.php?t=2415497
Don't quite understand the post, so better to just hold off on an attempt.. Would using the unroot option in SuperSU, allowing the OTA update to go through, then rerooting work fine without deleting data?
I'm know more about Nook Tablet than Nexus 7, didn't care what I did to my Nook because I could fix it. I'm more cautious with this.
Sent from my Nexus 7 using xda app-developers app
Super-Su unroot never help you if you delete something in the /system directory
1)you must flash fix after root
2)do not flash permanent custom recovery and relock bootloader (if your bricked you devices you can send to Warranty Service)
3)replace backup of /system directory before update
and after update clean Dalvik Cache before flash Root again (if superuser privilegies still anavalable for you)
Understand the fix now. Noticed the update went through, but got an error when it finished. Flash ota update in temporary recovery. Correct?
Sent from my Nexus 7 using xda app-developers app
I just downloaded the OTA to the device, unrooted, installed the OTA in TWRP, and then the latest superSU zip (still in recovery). Reboot and voila.
datallboy said:
I'm know more about Nook Tablet than Nexus 7, didn't care what I did to my Nook because I could fix it. I'm more cautious with this.
Click to expand...
Click to collapse
This is a Nexus device. There's almost no way to hard-brick it. Worst case, reboot into bootloader, and fastboot push the stock images.
The fix worked, and I'm still rooted. with all data. Temporarily booted into TWRP, flashed the fix and forced OTA update. Thank you!
ripelli part
Don't fear the ota update. There were no negative effects on my rom or kernel.
-cleanROM1.3
- 3.4.0 ElementalX1.1+
sfreemanoh said:
This is a Nexus device. There's almost no way to hard-brick it. Worst case, reboot into bootloader, and fastboot push the stock images.
Click to expand...
Click to collapse
LOL if you flash STOCK and then bootloader - you will get bootloop hardbrick without FASTBOOT and ADB !!! (only APX)
(my nexus 7 1 gen in this situation)
------------------------------------------------------
why you try new customs rom, when in few weeks would be android 5.0 ?
sambistt said:
LOL if you flash STOCK and then bootloader - you will get bootloop hardbrick without FASTBOOT and ADB !!! (only APX)
(my nexus 7 1 gen in this situation)
------------------------------------------------------
why you try new customs rom, when in few weeks would be android 5.0 ?
Click to expand...
Click to collapse
I'm not sure what you're saying in reference to my earlier comment...are you saying something I said was incorrect?
hello, i need to verify something with you guys.
Currently i'm using an HTC One M8 rooted and running on a stock rom, and TWRP as a recovery, can i still have OTA updates in my phone even if I'm on root and TWRP as a recovery. also one thing how can go remove TWRP recovery or revert to HTC recovery
many thanks
I also am curious about this topic
snap213 said:
hello, i need to verify something with you guys.
Currently i'm using an HTC One M8 rooted and running on a stock rom, and TWRP as a recovery, can i still have OTA updates in my phone even if I'm on root and TWRP as a recovery. also one thing how can go remove TWRP recovery or revert to HTC recovery
many thanks
Click to expand...
Click to collapse
1. Download the stock recovery for your device from the recovery thread
2. Flash it through fastboot (as you did TWRP)
3. Apply the OTA
4. Reflash TWRP
5. Re-root the phone
guess i'm stuck with my rooted phone then, i rooted my phone using Hansoon2000 All-In-One-Kit
and i can't find my stock rom, my software number is 1.54.707.7
snap213 said:
guess i'm stuck with my rooted phone then, i rooted my phone using Hansoon2000 All-In-One-Kit
and i can't find my stock rom, my software number is 1.54.707.7
Click to expand...
Click to collapse
Not stock rom...stock recovery
Look at the bottom of the first post of mr_hofs thread in the general section here: http://forum.xda-developers.com/showthread.php?t=2701376
You'll find your stock recovery there ?
Hope that helps.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 02:48 PM ---------- Previous post was at 02:46 PM ----------
spikeydoo2006 said:
Look at the bottom of the first post of mr_hofs thread in the general section here: http://forum.xda-developers.com/showthread.php?t=2701376 (under the nandroid backups section)
You'll find your stock recovery there ?
Hope that helps.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Remember (as said a million times already in multiple threads) - to flash an OTA you CANNOT have changed anything in the original system (fonts, Xposed mods, removing system apps, ANYTHING) otherwise the OTA WILL FAIL
i've browse mr.hofs thread and i've seen lots of stock recoveries. I don't know which stock recovery will I use.
I tried to match it using my software number 1.54.707.7 but there is none. or should i just try the closer to that version?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
thanks.
snap213 said:
i've browse mr.hofs thread and i've seen lots of stock recoveries. I don't know which stock recovery will I use.
I tried to match it using my software number 1.54.707.7 but there is none. or should i just try the closer to that version?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
thanks.
Click to expand...
Click to collapse
here is my recovery backup from 1.54.707.7. https://www.dropbox.com/s/p2ht9dxns3ggcyk/recovery.img
Can you backup your radio.img for me? I forgot to backup when i convert my phone to GPE.
to any Hasoons2000's users out there?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
---
or can anyone give me a much more detailed or step by step instructions, i know i' cant post in HTC development forum.
snap213 said:
to any Hasoons2000's users out there?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
---
or can anyone give me a much more detailed or step by step instructions, i know i' cant post in HTC development forum.
Click to expand...
Click to collapse
Yes, you can! I did it exactly that way - and after OTA update reflashed TWRP and rerouted that way. Its a 4 minute job.
snap213 said:
to any Hasoons2000's users out there?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
---
or can anyone give me a much more detailed or step by step instructions, i know i' cant post in HTC development forum.
Click to expand...
Click to collapse
Learn to do it yourself, relying on toolkits is a false economy as if anything goes wrong you'll have no idea how to fix it...
EddyOS said:
Remember (as said a million times already in multiple threads) - to flash an OTA you CANNOT have changed anything in the original system (fonts, Xposed mods, removing system apps, ANYTHING) otherwise the OTA WILL FAIL
Click to expand...
Click to collapse
Yes, that has been mentioned quite a few times in various threads..However one question that pops up now is:
Lets says I did make changes to the system files by removing a system app or using xposed mods (but not flashing any custom roms). But these changes were made AFTER taking a backup of (unchanged) stock recovery. Will OTA still fail if i now flash stock recovery and then ota update? I am guessing it should work as i am bringing the phone back to stock status.
Also what if i do not flash any custom recovery, I just boot into it to take a backup and remain in stock rom. In that case, for an OTA update, do i still need to first flash stock recovery if I have not made changes to sys files?
Finally when you say OTA fail, does that mean there is a chance I will brick/soft brick my phone?or is it just an error message. I ask because in case i make changes to sys and then forget about it or do not realise its consequence for an OTA update, its better I know now what I am getting into.
anjaan said:
Yes, that has been mentioned quite a few times in various threads..However one question that pops up now is:
Lets says I did make changes to the system files by removing a system app or using xposed mods (but not flashing any custom roms). But these changes were made AFTER taking a backup of (unchanged) stock recovery. Will OTA still fail if i now flash stock recovery and then ota update? I am guessing it should work as i am bringing the phone back to stock status.
Also what if i do not flash any custom recovery, I just boot into it to take a backup and remain in stock rom. In that case, for an OTA update, do i still need to first flash stock recovery if I have not made changes to sys files?
Finally when you say OTA fail, does that mean there is a chance I will brick/soft brick my phone?or is it just an error message. I ask because in case i make changes to sys and then forget about it or do not realise its consequence for an OTA update, its better I know now what I am getting into.
Click to expand...
Click to collapse
The OTA requires a 100% stock running Android build, so if you have removed any system apps it will just fail and reboot to the ROM you're running at the moment (so you should be safe). Basically, if the /system partition on the phone is ANY way different from how it was when you first bought it the OTA will fail
For example, other than S-OFF my phone is exactly how I received it, therefore the new OTA update installed successfully. If I had removed one system app (e.g. Hangouts), it would fail as it's looking for it and if it can't find it it'll just reboot
i still have my S-OFF here in my HTC, and i haven't removed any system apps. i'll try this later this week.
i just needed my root because of setCPU nothing else.
--- anyway, since we're all learning here.
we'll for example, OTA has been updated and all goes well. now that i have to reflash my recovery to TWRP.
big question again, how do i save my stock recovery using TWRP?
snap213 said:
i still have my S-OFF here in my HTC, and i haven't removed any system apps. i'll try this later this week.
i just needed my root because of setCPU nothing else.
--- anyway, since we're all learning here.
we'll for example, OTA has been updated and all goes well. now that i have to reflash my recovery to TWRP.
big question again, how do i save my stock recovery using TWRP?
Click to expand...
Click to collapse
If you're now on 1.54.401.10, you can manually extract it from the firmware package I uploaded HERE
I installed the OTA yesterday and had a different experience. I am with the stock rooted ROM, but I installed Xposed with some modules and the swipe to sleep and no write protection kernel modules. Also, unlocking the bootloader also ate my calculator and torch apps, and I reinstalled them as user apps instead of system apps.
Well, after flashing the stock recovery, the OTA worked like a charm. I applied it manually from the stock recovery, but I don't think this makes a difference. I had to re-root afterwards, but all the rest was preserved.
I am S-OFF though. Is that the reason why it bypassed some security checks?
Black Antitoon said:
I installed the OTA yesterday and had a different experience. I am with the stock rooted ROM, but I installed Xposed with some modules and the swipe to sleep and no write protection kernel modules. Also, unlocking the bootloader also ate my calculator and torch apps, and I reinstalled them as user apps instead of system apps.
Well, after flashing the stock recovery, the OTA worked like a charm. I applied it manually from the stock recovery, but I don't think this makes a difference. I had to re-root afterwards, but all the rest was preserved.
I am S-OFF though. Is that the reason why it bypassed some security checks?
Click to expand...
Click to collapse
I can see the apps that were removed during unlocking still working if installed as user apps as they're still on the /data partition. If they weren't there at all then it'd probably fail. Surprised that it worked with Xposed installed, but that's also a user app so it could very well work - logically it makes sense.
As a rule of thumb I'd only apply an OTA on a 100% stock system, that way you know it'll all be fine
Hi, I have a Nexus 5X with unlocked bootloader and with rooted. Since some days ago, I have a notification with a security update, but with the custom recovery it is not automatically installed.
Is there any way to install this OTA updates?
If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
martyfried said:
If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The updates will not install on a rooted phone. Updates check if your software is stock and if not it will not update, includes recovery partition. Your best bet is to just update the ROM you're on. The ROM developer typically updates his base on a regular basis especially if it's one of the more active ones like Pure Nexus or Chroma among others.
If you really need Google updates to happen then you must go back to stock image and updates will work then.
Edit #2: If you are rooted but stock w/ TWRP, just unroot and flash stock recovery and the updates will work or you can ADB sideload the update zip w/ TWRP.
Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The link I provided has explicit instructions. I remembered wrong, though. You don't need TWRP, you need to do it in Fastboot mode, so you need to find the latest Fastboot program, or install the Android SDK. Then follow step 10 in the link I provided.
Hi!
I had 2 nexus 5x phones. One rooting went fine, the other is stuck at the Welcome to Android cycle.
I unlocked the bootloader, and I used chainfire auto-root script from linux.
When the phone boots up it has the blue welcome screen. I setup wifi and then it forces me to install an android update. It downloads the update, reboots, tries to install it, fails, and then boots into android where it tries to force me into the update.
How can get out of the loop?
Just flash your favorite custom ROM from recovery (or stock if that pleases you) and ignore OTAs.
draggehn said:
Just flash your favorite custom ROM from recovery (or stock if that pleases you) and ignore OTAs.
Click to expand...
Click to collapse
not everyone is after custom roms, some people are more than happy with their (rooted) stock experience.
OP, the way googles OTAs work these days, is that they basically check your system partitions for any modification (e.g. root). if that check fails, so does the update. now what can you do about your little update trap?
if i recall correctly, chainfire includes ways to revert to unrooted. so there is you first possible option. use it, fire up your phone, let it take the OTA (make sure you're on the latest version after that) and attempt to root again.
if that is not an option, you could grab the newest factory image directly from google, flash the whole thing and then root again.
once your phone is up and running (and rooted ofc), it won't be able to apply future OTAs, but instead of forcing you to update, it will only show a notification.
Broken303 said:
not everyone is after custom roms, some people are more than happy with their (rooted) stock experience.
Click to expand...
Click to collapse
Which is why there was a parenthetical note that you can also flash stock.
I have 5.01 and I want to update to 6.01. I want to wipe it clean. Got factory image from Google site.
What's the difference between the OTA and factory downloads?
I can just flash the factory in TWRP right? Will I lose root, or will TWRP ask if I want to keep root?
I still have boot loader unlocked.I just can't remember for the life of me, haven't done flashing etc in a few years.
Thanks!
So...not a single person can tell me if I lose root, or if TWRP will re-root?
Please?
N7 is no longer supported by Google and there will be no more OTA.
You can't flash the entire factory image directly from TWRP (but it is doable).
When you flash the factory image, you will lose root, TWRP and all your data.
NRT can simplify flashing, rooting and restoring TWRP.
You have unlocked boot loader
Just fastboot flash all as yiu want clean install
After that fastboot flash twrp
After that flash superSU
Done.
No need for any toolkit's, try to stay away of them and do it manually.
Sent from my XT1565 using Tapatalk
k23m said:
N7 is no longer supported by Google and there will be no more OTA.
You can't flash the entire factory image directly from TWRP (but it is doable).
When you flash the factory image, you will lose root, TWRP and all your data.
NRT can simplify flashing, rooting and restoring TWRP.
Click to expand...
Click to collapse
I know it isn't supported anymore. They still have the image's though.
Im just confused... Long time ago when I was really into all this, I just went to Googles page, downloaded the .zip and flashed it in TWRP. Now, the Google page is different and there isn't just 1 anymore. Can I just open the factory image and unzip the update part and flash that in TWRP?
The OTA files are only for updating from version to version correct? Can't go from what I'm on, 5.01 to the current 6.1 right? That's what I talking about and why I'm so confused now
Googles page used to have the OTA zip to update from prior newest to newest(5.0 to 5.01 for example) but than they also had the full OTA so you could do a 4.0 to 5.1 or whatever. Why they change the site? Which one do I use now to go from my 5.01 to current 6.1?
atifsh said:
You have unlocked boot loader
Just fastboot flash all as yiu want clean install
After that fastboot flash twrp
After that flash superSU
Done.
No need for any toolkit's, try to stay away of them and do it manually.
Click to expand...
Click to collapse
That's the pronlem, normally yes I would do that no problem. I'm in the middle of upgrading my PC after had a surge or something and fried my ****.
That's why I want to do it via TWRP like I always did before. Every time TWRP asked if I wanted to retain root after updating also. So what in the world happened in the last year that It doesn't seem like I can now? Like I said above, I can't find a full update OTA on!y the incremental OTAs...
Syntax323 said:
I know it isn't supported anymore. They still have the image's though.
Im just confused... Long time ago when I was really into all this, I just went to Googles page, downloaded the .zip and flashed it in TWRP. Now, the Google page is different and there isn't just 1 anymore. Can I just open the factory image and unzip the update part and flash that in TWRP?
The OTA files are only for updating from version to version correct? Can't go from what I'm on, 5.01 to the current 6.1 right? That's what I talking about and why I'm so confused now
Googles page used to have the OTA zip to update from prior newest to newest(5.0 to 5.01 for example) but than they also had the full OTA so you could do a 4.0 to 5.1 or whatever. Why they change the site? Which one do I use now to go from my 5.01 to current 6.1?
That's the pronlem, normally yes I would do that no problem. I'm in the middle of upgrading my PC after had a surge or something and fried my ****.
That's why I want to do it via TWRP like I always did before. Every time TWRP asked if I wanted to retain root after updating also. So what in the world happened in the last year that It doesn't seem like I can now? Like I said above, I can't find a full update OTA on!y the incremental OTAs...
Click to expand...
Click to collapse
Ok yes that's possible
If you have twrp already
Check development forum and choose one of the ROM.
Download it to your tablet plus gapps
Wipe system, cache and data leaving internal storage.
Flash ROM reboot, come back to twrp and flash gapps. ( Can do ROM + Gapps in one go)
Download SuperSU and flash to get root.
You can't flash stock image / OTA via twrp.
While you're doing all this try the 7.0 ROM its good enough now.
atifsh said:
Ok yes that's possible
If you have twrp already
Check development forum and choose one of the ROM.
Download it to your tablet plus gapps
Wipe system, cache and data leaving internal storage.
Flash ROM reboot, come back to twrp and flash gapps. ( Can do ROM + Gapps in one go)
Download SuperSU and flash to get root.
You can't flash stock image / OTA via twrp.
While you're doing all this try the 7.0 ROM its good enough now.
Click to expand...
Click to collapse
Ahhh what happened??? Why can you not flash them with TWRP???
Thats what I used to do no problem. Not referring to custom roms either.
I am wanting stock rooted.
I used to download the update when one was released from Google's site, put the update.zip in main directory, go in recovery and flash update.zip. TWRP would ask me if I wanted to keep root, I say yes, reboot, update installs... than i'm on the new Android version still rooted.
How is that not possible now?
I am so annoyed... I never had to go through ADB or fastboot to update to latest. I did everything on my N7, it kept root for me and everything.
I feel so dumb right now its ridiculous lol
So than what way can I go about updating my N7 2013 Wifi, which I currently have 5.01. I am Rooted w/ unlocked bootloader.
What is the best way not using ADB, or a PC at all for that matter to update to the latest, 6.01. If possible, how can I keep root, if not i'm not worried about it, i'll just re-root myself.
I appreciate all the responses, sorry if i'm just being an idiot. I just know for a fact I never had to use ADB or my PC to update and keep root...
I'm not familiar with Stock OTA done with twrp (if that's even possible)
Already told you get a custom ROM, get the one mostly stock or if there's a stock ROM in zip format available.
In future you might need to update that bootloader of yours for newer ROMs
Sorry if this sounds harsh why are you so into keeping root as you can't do it again? It's simple as flashing SuperSU. Root method changed after 6 you cant have old methods with 6.
Best bet for you at the moment.
http://forum.xda-developers.com/showthread.php?t=3219148
Sent from my XT1565 using Tapatalk