I've seen the guides for rooting the Developer Previews--but has any of that changed?
I'm on Marshmallow, decrypted using Xceed and TWRP.
I want to flash the Factory images and then root afterwards. Best advice?
wait until the kernels are done and/or supersu has been updated to reflect new build
I had the update notice when I got home Monday. It downloaded the update, and then I used FlashFire to apply the OTA since I had twrp installed. FF updated the tablet and then re-rooted it. Still have twrp and root.
Sent from my Nexus 5X using Tapatalk
Hi,
Do you mean that with flashfire you can root your pixel c and get Ota update without loosing data or root???
Thanks for your help
n1ck0 said:
Hi,
Do you mean that with flashfire you can root your pixel c and get Ota update without loosing data or root???
Thanks for your help
Click to expand...
Click to collapse
I used FlashFire to install the OTA and kept data and root.
Related
Hi!
My Nexus 7 is rooted and bootloader unlocked, with TWRP custom recovery. If I accept the KitKat OTA update when I get it, will it brick my device? Will my device be wiped? Do I need to do anything special? Will anything break (I use Skype and the camera a lot)? Do I need to re-root?
Sorry for the noob question...
-Orange
Apparently it overwrites default recovery and you lose the root. But still it's not safe.
Instead
Download the ota and supersu to your tab.
Goto TWRP
Flash ota first. then immediately flash super su. You retain root with custom recovery.
That's it.
Follow this and nothing breaks.
littleromeo said:
Apparently it overwrites default recovery and you lose the root. But still it's not safe.
Instead
Download the ota and supersu to your tab.
Goto TWRP
Flash ota first. then immediately flash super su. You retain root with custom recovery.
That's it.
Follow this and nothing breaks.
Click to expand...
Click to collapse
Where do we download the ota zip?
Thanks.
poloruiz714 said:
Where do we download the ota zip?
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2524978
make sure you are on jss15r
Here's the OTA link
Code:
http://android.clients.google.com/packages/ota/google_razor/3a3951e8243c82bc01a620ab858f4454c8ebd65c.signed-razor-KRT16O-from-JSS15R.3a3951e8.zip
and super su just in case
Code:
http://download.chainfire.eu/supersu
littleromeo said:
make sure you are on jss15r
Actually I am on jss15j (rooted tablet as soon as I opened the box), clockworkmod recovery (latest build) so what files do I need? Also do I perform a full wipe or flash on top of current system? Sorry for the noon question. Thanks.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Root should not affect the OTA update.
I have a rooted Nexus 7 LTE which ran on 4.3.1 until yesterday. Last night I received the update message. So I updated to Kitkat 4.4.
It worked great especially since SuperSU managed to keep the root access. So after the update I had no additional work to get it rooted again
bama35453 said:
Root should not affect the OTA update.
I have a rooted Nexus 7 LTE which ran on 4.3.1 until yesterday. Last night I received the update message. So I updated to Kitkat 4.4.
It worked great especially since SuperSU managed to keep the root access. So after the update I had no additional work to get it rooted again
Click to expand...
Click to collapse
How about custom recovery?
Sent from my SPH-L710 using XDA Premium 4 mobile app
Hello
I've rooted my Nexus 5X and i left the recovery to stock recovery because i wanted to have the OTA updates normally without using a PC.
With ytsemless root I was hoping that this is no problem. But the febuary security OTA fails when I try to install.
Can someone explain to me why this could fail?
I have not much root apps installed. Just adaway, busybox, sd maid and supersu. No costum kernel.
So from my point of view I touched nothing that should have an impact to OTA.
So my question is: Why is there always an error when I try to update with OTA?
ChenZ86 said:
Hello
I've rooted my Nexus 5X and i left the recovery to stock recovery because i wanted to have the OTA updates normally without using a PC.
With ytsemless root I was hoping that this is no problem. But the febuary security OTA fails when I try to install.
Can someone explain to me why this could fail?
I have not much root apps installed. Just adaway, busybox, sd maid and supersu. No costum kernel.
So from my point of view I touched nothing that should have an impact to OTA.
So my question is: Why is there always an error when I try to update with OTA?
Click to expand...
Click to collapse
Because you have applied systemless root. Anything, ANYTHING different from completely stock will cause the normal OTA process to fail. These posts keep asking the same question and the answer never changes. It is what it is. There are a ton of posts here which will explain alternate flashing processes to update, then re-root your device.
Try using flashfire from Chainfire. It detects downloaded ota and ask you if you want to try and flash it. Also there is an option to re-root after updating. If the ota doesn't install then download the factory image for February and flash the whole thing. Make sure data is uncheked so that it doesn't wipe your data. It's a bigger download than ota but it will definitely work.
I had stock + root + xposed + layers. Managed to update to latest build with automatic re-root. Then I just flashed twrp-recovery using flashify and installed xposed through twrp. Took me 5 mins to flash everything (excluding time to download the factory image). All without using a PC!
Skickat från min Nexus 5X via Tapatalk
this all seems like a hassle compared to using a near-stock custom rom and updating it yourself.
2x4 said:
this all seems like a hassle compared to using a near-stock custom rom and updating it yourself.
Click to expand...
Click to collapse
[emoji106] Or even stock rom.
Sent from my Nexus 9 using Tapatalk
I haven't been offered it yet, but I know it's coming so wanted to ask, trying to stay on the official channel.
If you accept the update will I lose root and have to re-root?
I'm out of practice since the Nexus 6P tether worked out of the box.
Thanks in advance!
wonderrx said:
I haven't been offered it yet, but I know it's coming so wanted to ask, trying to stay on the official channel.
If you accept the update will I lose root and have to re-root?
I'm out of practice since the Nexus 6P tether worked out of the box.
Thanks in advance!
Click to expand...
Click to collapse
The OTA probably won't work because when you root with Magisk you flash a modified boot image. Process would be as follows before taking the OTA.
Flash stock boot image from the Image Version you are currently on (i.e. Flash the October Boot Image)
Reboot
Take OTA
Re-root using Magisk using the November Boot image to patch
add tethering line to build.prop or get the Magisk Module
Profit
You would need to repeat this for each monthly update to keep root.
I had always thought this was the best way to install OTAs. Someone correct me if I'm wrong?
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Cowbell_Guy said:
I had always thought this was the best way to install OTAs. Someone correct me if I'm wrong?
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Normally yes but I'm not sure if the partition structure is identical on the new Pixels but you could always try @topjohnwu 's method and report back.
I didn't think you could do an OTA with an unlocked bootloader, is that true? If so, topjohnwu's method wouldn't work anyway.
hi all
assuming that i've flashed TWRP + rooted the phone
will i still be able to update the phone via OTA updates?
as this does not work on samsung phones once KNOX is tripped
i was wondering if it would be the same on oneplus devices
your input is appreciated. thanks!
leongzxc said:
hi all
assuming that i've flashed TWRP + rooted the phone
will i still be able to update the phone via OTA updates?
as this does not work on samsung phones once KNOX is tripped
i was wondering if it would be the same on oneplus devices
your input is appreciated. thanks!
Click to expand...
Click to collapse
Short answer: No. Custom recovery can't process the OTA update. There's another thread talking about this topic here: https://forum.xda-developers.com/oneplus-5t/help/root-update-ota-t3712615
If you want the latest updates Funk Wizard usually posts their full zips (not small OTA zips) on XDA (just search in the 5T section) and OnePlus usually has them under the device support page.
I've not tried it myself but I heard once you root and go to software update section oneplus will detect your root and instead will download a full OTA zip which you can then dirty flash in your custom recovery (TWRP) without any issues. of course the flash will remove root and then you will need to flash root zip file to gain root again.
Well, actually I downloaded latest OTA (4.7.4) over wifi and then updated phone while rooted and with custom recovery (oficial 3.2.0 I think). And it worked! I lost root in the process (I rooted again later), but otherwise phone was updated and it was done via custom recovery. So far, I don't have any problems, but not sure if any problems will come later.
shadeau said:
Short answer: No. Custom recovery can't process the OTA update. There's another thread talking about this topic here: https://forum.xda-developers.com/oneplus-5t/help/root-update-ota-t3712615
If you want the latest updates Funk Wizard usually posts their full zips (not small OTA zips) on XDA (just search in the 5T section) and OnePlus usually has them under the device support page.
Click to expand...
Click to collapse
Revin said:
Well, actually I downloaded latest OTA (4.7.4) over wifi and then updated phone while rooted and with custom recovery (oficial 3.2.0 I think). And it worked! I lost root in the process (I rooted again later), but otherwise phone was updated and it was done via custom recovery. So far, I don't have any problems, but not sure if any problems will come later.
Click to expand...
Click to collapse
thanks for the response!
digitalmahdi said:
I've not tried it myself but I heard once you root and go to software update section oneplus will detect your root and instead will download a full OTA zip which you can then dirty flash in your custom recovery (TWRP) without any issues. of course the flash will remove root and then you will need to flash root zip file to gain root again.
Click to expand...
Click to collapse
wow for real?
so if you're rooted. it will not download small zips of OTA but instead the full sized OTA?
then we can choose to flash in TWRP instead?
Hi
I have a 2015 Shield (non pro) currently running rooted 5.2.0. I am looking to update it with the latest 8.0.1 dev image to keep root. Is there any precautions or extra steps I need to take over what is in the instructions in the download centre. From what I have read I will need to ADB sideload Magisk to get full root access after installing the dev image.
you'll need to patch the boot.img in magisk canary and then flash it
https://forum.xda-developers.com/shield-tv/general/guide-root-nvidia-shield-experience-t3882254
Do I need to unroot or factory reset the rooted 5.2.0 before flashing 8.0.1. Is there any benefit in flashing the dev image rather than the factory image before flashing the patched boot.img.
You should update the firmware OTA. Because you'll flash the OTA you'll need to patch then flash the dev image or this root boot image: https://forum.xda-developers.com/shield-tv/development/kernel-overclock-kernel-2-22-ghz-t3943079
But do I need to unroot etc to do an OTA.
g1dtf said:
But do I need to unroot etc to do an OTA.
Click to expand...
Click to collapse
yes unroot will happen automatically when you install the OTA. if you know how to use adb and follow my steps it's not a big deal though you can get it back quickly
I have just unfroze system upgrade (com.nvidia.ota) and it offers experience 6.3. I guess I have to incrementally install subsequent OTA's until I get to 8.0.1 then follow your guide to re-root using your guide, I am familiar with using ADB although its been quite a while since I last used it.
g1dtf said:
I have just unfroze system upgrade (com.nvidia.ota) and it offers experience 6.3. I guess I have to incrementally install subsequent OTA's until I get to 8.0.1 then follow your guide to re-root using your guide, I am familiar with using ADB although its been quite a while since I last used it.
Click to expand...
Click to collapse
yes correct you need to do it incrementally--it's totally worth it Nvidia has done some great upgrades!
Got it up to 8.0.0 installing the OTA's. However the next OTA offered is 8.0.2 rather than 8.0.1 which as far as I know has no root options yet as the 8.0.2 images have not been released by NV.
yes but you don't need dev images to root, you can just patch this boot.img and it should give you root (as long as you install the latest Magisk canary and then upgrade through that)
https://forum.xda-developers.com/sh...l-2-22-ghz-t3943079/post81708169#post81708169
False double post please ignore.
Just a little confused as to which boot.img I need to patch. Looked at the XDA link you posted but there are quite a few different ones mentioned in that thread. I am currently running stock 8.0.2 OTA on my 2015 16gb.
g1dtf said:
Just a little confused as to which boot.img I need to patch. Looked at the XDA link you posted but there are quite a few different ones mentioned in that thread. I am currently running stock 8.0.2 OTA on my 2015 16gb.
Click to expand...
Click to collapse
Just boot into twrp using this https://drive.google.com/file/d/1934405D1S0lv52jZMqS-Zny62RIzGWSi/view
Then flash magisk canary in there, and you are done
Thanks! Flashed the latest canary and now rooted on 8.0.2.