After some vigorous searching I've found out that if you don't modify the boot loader then you should be okay receiving OTA updates. I'd like to root my nexus 7 so I can run some apps that require root access. I've looked at many methods on how to root the nexus 7, but from my noob understanding, the majority of these methods require unlocking the boot loader and getting TWRP recovery. Won't that mess up the OTA? I've searched a couple threads but I don't necessarily understand the difference between an unlocked boot loader and a rooted device. The reason I still want to have OTA updates is so that I can still update android and so on.
Thanks for taking the time to read this and help guys!
Pickle_Jr;4f86 said:
After some vigorous searching I've found out that if you don't modify the boot loader then you should be okay receiving OTA updates. I'd like to root my nexus 7 so I can run some apps that require root access. I've looked at many methods on how to root the nexus 7, but from my noob understanding, the majority of these methods require unlocking the boot loader and getting TWRP recovery. Won't that mess up the OTA? I've searched a couple threads but I don't necessarily understand the difference between an unlocked boot loader and a rooted device. The reason I still want to have OTA updates is so that I can still update android and so on.
Thanks for taking the time to read this and help guys!
Click to expand...
Click to collapse
On this platform, at this time, you need to unlock the bootloader to install root.
You don't need to flash/install twrp if you don't want to, but you need to boot into twrp temporarily to install the root files.
Even if you install twrp rather than boot into it temporarily, it won't cause your ota to fail.
The things that cause the ota to fail are
1) modifying or deleting any files with your root permissions
This includes root apps which do things you might not realize
2) installing custom kernel
3) installing earlier version of supersu
sfhub said:
On this platform, at this time, you need to unlock the bootloader to install root.
You don't need to flash/install twrp if you don't want to, but you need to boot into twrp temporarily to install the root files.
Even if you install twrp rather than boot into it temporarily, it won't cause your ota to fail.
The things that cause the ota to fail are
1) modifying or deleting any files with your root permissions
This includes root apps which do things you might not realize
2) installing custom kernel
3) installing earlier version of supersu
Click to expand...
Click to collapse
Awesome! Thanks! So if I understand correctly, as long as I be careful about what root apps I have as well as have a newer (newest) version of SuperSU installed I'll be okay? I'm assuming I'll lose root when I get an OTA update but hopefully when the time comes, there'll be a way to root android 4.4 when the n7 get's it as well. And if something goes wrong I guess I could just unroot, factory reset, and update OTA that way too. Thanks for the help!
Pickle_Jr said:
Awesome! Thanks! So if I understand correctly, as long as I be careful about what root apps I have as well as have a newer (newest) version of SuperSU installed I'll be okay?
Click to expand...
Click to collapse
Yes.
For example, if you freeze a stock app in titanium, that is ok, but if you remove a stock app, then an OTA will likely fail.
If you use stickmount, it modifies a system file and backs it up, then restores it when it is done, but sometimes that gets out of sync, in which case the OTA fails.
There are other examples.
Pickle_Jr said:
I'm assuming I'll lose root when I get an OTA update but hopefully when the time comes, there'll be a way to root android 4.4 when the n7 get's it as well. And if something goes wrong I guess I could just unroot, factory reset, and update OTA that way too. Thanks for the help!
Click to expand...
Click to collapse
If you install root through the stock recovery, you'll lose root permissions (but the files will still be there). Just re-root using the existing procedure.
If you want to save a step, boot into TWRP to install the OTA (which you download manually) and then "chain" install the OTA, then the root install files.
This way, you lose root for half a second until the 2nd install file in the chain runs. Essentially you won't lose root (or won't notice losing root) because the first time you boot into 4.4, you'll have root.
|Guide|How-To| Root & Install Custom Recovery for 4.3 / 4.4 Update |16 July 2014 |
Warning: Following any of these instructions will void your warranty, and could possibly cause irreparable harm to your device (i.e. bricked). If you do not understand these risks, stop here and do not proceed. If you do not know how to use Odin, stop here and do not proceed. I am not responsible for anything that happens to your device. YOU chose to follow this guide.
If you have not updated to 4.3, go here.
If you have not updated to 4.4, go here.
Finally, there is no guarantee that either method will work for you.
Root Method #1:
The first thing you should try is CF-Autoroot since this has worked for many users.
If you successfully root with this method, you can simply install Goo Manager or ROM Manager and install recovery.
This method failed for me after many attempts.
Edit:
Here is some potentially useful info for root method #1 from ansonantonym.
Root Method #2:
1) Reboot in to download mode
2) Flash TWRP with Odin via PDA
3) Reboot to recovery then flash SuperSu and the Knox Remover
4) Reboot
5) Download SuperSu from the Play Store
6) Open SuperSu and update the binary when prompted
7) Reboot
8) Enjoy rooted 4.3/4/4
Downloads:
Odin
TWRP (Odin flashable tar)
SuperSu (v1.65)
SuperSu (v2.01)
DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0
If you found another method that worked for you, please post here so that others may benefit.
If you are uncertain about any of the steps above, please ask your questions here before proceeding.
Please be sure to thank Chainfire, Dees_Troy, and Kaito95.
*****
Noob here, first off I unrooted a while ago, then took the ota 4.3, is the bootloader locked? Cause according to the cf auto root site if your bootloader is locked you'll probably brick your phone if you flash the auto root? Also do these steps have to be in order? I tried rooting by other means and installing supersu first, wouldn't work so I removed knox with the script, and then updated supersu in the play store and still nothing, can I try to flash cf auto root now and then update supersu in the play store? Thanks a million, need this thing rooted
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jeremyds45 said:
Noob here, first off I unrooted a while ago, then took the ota 4.3, is the bootloader locked? Cause according to the cf auto root site if your bootloader is locked you'll probably brick your phone if you flash the auto root? Also do these steps have to be in order? I tried rooting by other means and installing supersu first, wouldn't work so I removed knox with the script, and then updated supersu in the play store and still nothing, can I try to flash cf auto root now and then update supersu in the play store? Thanks a million, need this thing rooted
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Well, I'm not bricked, so I think that answers your question about the bootloader.
Do you have a custom recovery installed? I assume so since you say you flashed the Knox remover script. If you do have a custom recovery installed, just flash the SuperSu zip, then update in the Play Store.
upndwn4par said:
Well, I'm not bricked, so I think that answers your question about the bootloader.
Do you have a custom recovery installed? I assume so since you say you flashed the Knox remover script. If you do have a custom recovery installed, just flash the SuperSu zip, then update in the Play Store.
Click to expand...
Click to collapse
Ah it is so nice to have root again... Thank you so much for putting up with a noob.
Crazy events of a noob that lead me to root
Installed ota 4.3
Tried to root and install superuser by odin and then custom recovery to flash
Root didn't happen because of knox
Could only get to CWM custom recovery if it was right after odin and battery pull?...
Flashed the script to remove knox, which did remove knox
Tried the same root method as above and no root access
Tried supersu and then updating in play with no success
Changed security update settings etc nothing
Reset delvik, cache, permissions, etc nothing
Different root method and files for odin, and custom recovery stuck
Used files from this thread, went into custom recovery and flashed supersu
Installed supersu from play store...
Updated the binary using custom recovery
Rebooted...
ROOT access, all root applications work fine and root sticks even after reboots
I never messed with cf auto root method
THANK you guys for your time effort and sharing, helps noobs out like me a lot!
Sweet! I've missed root since I upgraded using the OTA file you provided. Looking forward to much other great things coming from you
Thank You
upndwn4par said:
Warning: Following any of these instructions will void your warranty, and could possibly cause irreparable harm to your device (i.e. bricked). If you do not understand these risks, stop here and do not proceed. If you do not know how to use Odin, stop here and do not proceed. I am not responsible for anything that happens to your device. YOU chose to follow this guide.
If you have not updated to 4.3, go here. Make sure you understand the risks and uncertainties described in the OP.
Finally, there is no guarantee that either method will work for you.
Root Method #1:
The first thing you should try is CF-Autoroot since this has worked for many users.
If you successfully root with this method, you can simply install Goo Manager or ROM Manager and install recovery.
This method failed for me after many attempts.
Root Method #2:
1) Reboot in to download mode
2) Flash TWRP with Odin via PDA
3) Reboot to recovery and flash SuperSu.
4) Flash the Knox Remover
5) Reboot
6) Download SuperSu from the Play Store
7) Update the binary when prompted
8) Reboot
8) Enjoy 4.3
Downloads:
Odin
TWRP (Odin flashable tar)
UpdateSuperSu
If you found another method that worked for you, please post here so that others may benefit.
If you are uncertain about any of the steps above, please ask your questions here before proceeding.
*****
Click to expand...
Click to collapse
Method two absolutely worked. Thank you so much. I was scared to flash TWRP but knowing you did it gave me the courage. Have full root and happy
questions about this root
Hi, I'm a little nervous with this root but I need the root as the phone is useless without it.
I have the [email protected] galaxy s3 I747 will all these files work with it im just double checking.
Also do you flash the knox remover the same way as you flash other things with the pda button?
Will I still be able to do factory restores?
Also I saw that knox remover removes a lot of apps, Can you install these deleted apps from the market if you need too?
THanks please let me know asap.
THANKS!!!! your a lifesaver didn't know how much longer i could take without root
Dunno where you guys got your 4.3 update from and how you got it working but I did the OTA and Root just does not want to stick. I used knox remover and Cf auto root but it loses root after a restart. SuperSu never opens and crashes as soon as you open it. I have a feeling Cf auto root is just not compatible for the ota 4.3 i747??
bkong said:
Dunno where you guys got your 4.3 update from and how you got it working but I did the OTA and Root just does not want to stick. I used knox remover and Cf auto root but it loses root after a restart. SuperSu never opens and crashes as soon as you open it. I have a feeling Cf auto root is just not compatible for the ota 4.3 i747??
Click to expand...
Click to collapse
use the TWRP method worked perfected for me
Thanks
PimpMyPC said:
Hi, I'm a little nervous with this root but I need the root as the phone is useless without it.
I have the [email protected] galaxy s3 I747 will all these files work with it im just double checking.
Also do you flash the knox remover the same way as you flash other things with the pda button?
Will I still be able to do factory restores?
Also I saw that knox remover removes a lot of apps, Can you install these deleted apps from the market if you need too?
THanks please let me know asap.
Click to expand...
Click to collapse
The second method worked great. I believe (and the way that worked for me) that you use your custom recovery to flash the knox script, not using Odin and pda. I don't think it removed anything other than knox, there is a different script for removing knox and att bloatware. Should still be able to factory reset... But can't guarantee that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Root & Knox
When you go to Settings/More tab/Security/Device Administrators, You have KNOX and Android Device Manage. Both are unchecked on mine. So does that mean Knox is not working if unchecked and safe to try to Root?????
tailgunner9 said:
When you go to Settings/More tab/Security/Device Administrators, You have KNOX and Android Device Manage. Both are unchecked on mine. So does that mean Knox is not working if unchecked and safe to try to Root?????
Click to expand...
Click to collapse
Those settings are just for granting device administrator privileges. If unchecked, Knox is still doing it's thing, just not at an administrative level.
Yes, it is safe to try and root.
I have Android Device Manager as admin. That way if I ever lose my device I can just log in to the Play Store and locate and / or wipe the device.
To do this just flash the recovery.img file using odin and clicking the pda button correct?
Is there a way to freeze Knox instead of deleting it in the event I would want to go back to full stock?
After you are rooted, use an app like Titanium Backup(pro) or My Backup pro. Both will freeze it.
Root
If some of you out there use Root Method #2 and it works well and No problems, Please post and let us all know. Thanks
tailgunner9 said:
If some of you out there use Root Method #2 and it works well and No problems, Please post and let us all know. Thanks
Click to expand...
Click to collapse
I tried method 1 and failed.
Then tried method 2, but using a CMW tar that was posted yesterday.
I seem to be rooted!
So far no issues.. Just need to get everything setup as I had it in the leak.
indymx said:
I tried method 1 and failed.
Then tried method 2, but using a CMW tar that was posted yesterday.
I seem to be rooted!
So far no issues.. Just need to get everything setup as I had it in the leak.
Click to expand...
Click to collapse
Thanks indymx, may get the nerve up to try it on my AT&T S3. Let me know if you run into any problems. Guess Rom Manager and other programs that require Root are working Ok and you have rebooted few times to be sure it keeps Root?? Have Happy Thanksgiving.
ok so when i root my g3 using one click root tool it seems to be a success but when i use root checkers they say the device is not rooted and supersu wont update the binaries. i have already tried doing a factory reset and re-root but it did not help. anyone know what i can do? please need help.
Reflash firmware via lgflashtool 2014 retry the process after applying one click root method dont restart cuz if u did u have to reflash rom again for root follow the process to flash twrp make backup 1st then flash supersu or other zips if ur a carrier varient
apparently the issue wasn't with the rooting but with supersu, I installed CM 13 now and just use the root option that comes with it, I also tried installing SuperSU on CM 13 and it just broke it and I has to do a factory reset and re-flash CM 13. not sure why
Super user is built into cm 13 and it wont allow to change root access.
I root my MI 10T Pro with TWRP and Magisk. Now i see there is a Firmware-Update. Anywhere know how can i do the Update without lost root?
You can't. You have to uninstall magisk completely, perform update (if you have TWRP installed it might fail), and after that reinstall magisk and modules
OK. Thank you. The Bootloader is after the Update closed? And when its fail because TWRP what can i do?
No, bootloader stays unlocked, you just boot twrp after and reinstall magisk.
If it fails because of twrp you can do 2 things:
1. restore stock recovery and redo installation
2. download full rom from internet and apply through fastboot.
In any case you'd have to reinstall magisk after...
OK. Thank you. I understand right? When i go back to Stock the Bootloader is open but root is away? So i can root the other one Method without TWRP?
WeWa2013 said:
OK. Thank you. I understand right? When i go back to Stock the Bootloader is open but root is away? So i can root the other one Method without TWRP?
Click to expand...
Click to collapse
Yeah. Basically whole boot partition gets overwritten and magisk goes away with stock update, you only have to reinstall it...
I was rooted and had magisk working, but after my first update its gone and my phone says it doesn't recognize root anymore. So I was wondering if there is a file I would be able to flash to obtain magisk root again? I would really really rather not wipe my phone in the process if I don't have to. Thank you for any help.
RighteousJoe said:
I was rooted and had magisk working, but after my first update its gone and my phone says it doesn't recognize root anymore. So I was wondering if there is a file I would be able to flash to obtain magisk root again? I would really really rather not wipe my phone in the process if I don't have to. Thank you for any help.
Click to expand...
Click to collapse
rename magisk.apk as .zip and sideload it via adb, once reboot just install magisk manager if missing - that's all
for upcoming updates, just follow instructions
Thank you!