ota updates with root and a linux host? - Google Pixel Questions & Answers

Ok,
I have fastboot and adb working on my linux mint host. Can someone explain to me how to install ota updates on a rooted pixel phone? I tried installing it via the zip using twrp and that didn't work. It just unrooted my phone so I had to reroot it. I tried using Flashfire and downloading the ota update and then using flashfire to detect the ota update and flash it and everytime it doesn't work... errors and then unroots my phone.

I never succeeded in OTA on my rooted pixel. I always download the full image then do upgrading via fastboot or flashfire.

bush911 said:
I never succeeded in OTA on my rooted pixel. I always download the full image then do upgrading via fastboot or flashfire.
Click to expand...
Click to collapse
Ok, I downloaded the ota update via Google's webiste. Flashed it with flashfire. It asked if I would like to overwrite the boot and recovery. (said it would most likely fail if I didn't.) I told it ok. It flashed for a while. Rerooted automatically. It booted back up. It didn't update. Still prompting me to update ota.

I just tried the second method in this article
https://www.howtogeek.com/192402/why-androids-ota-updates-remove-root-and-how-to-keep-it/
sailfish-n2g47e-factory-00a46e7e.zip
Then used flashfire to flash it like the article states. No error but my phone is still prompting and trying to update via Ota.

Which version of SuperSU are you trying to use? Both of the following links discuss verified boot, which is one possible item you could be running into with the latest Pixel updates.
SuperSU v2.82-SR1 is the latest version, and it added boot signing.
https://plus.google.com/+Chainfire/posts/XikxTkhHpiG
If you are using an older version of SuperSU, then you will need to sign the boot image. I installed the latest Pixel update before v2.82-SR1 was available, so I just had FlashFire install the OTA, and then I added the following zip to the list of FlashFire actions immediately after it was set to root the phone again. FlashFire worked without issue to update to the latest release for June by adding the following before rebooting when using a version before SuperSU v2.82-SR1.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

I am attempting to flash 2.79. but immediately after, I flash the verifiedbootsignerv3.zip

How to root my phone"
Sent from my itel it1408 using XDA Free mobile app

yared1212 said:
How to root my phone"
Sent from my itel it1408 using XDA Free mobile app
Click to expand...
Click to collapse
Not sure what you mean here...

dorlow said:
sailfish-n2g47e-factory-00a46e7e.zip
Then used flashfire to flash it like the article states. No error but my phone is still prompting and trying to update via Ota.
Click to expand...
Click to collapse
That looks like an April update, and there are newer versions, so I'm not surprised the phone would try to update.
https://developers.google.com/android/ota
Three months ago was the first time I tried FlashFire, and I couldn't get it to use the OTA to the phone at that time. Some of the FlashFire instructions made me think I might need to use the backup option to get the OTA to work, but I was actually able to take the May and June OTAs using FlashFire without the backup option. I'm not sure why FlashFire didn't work for an OTA in April, while it did work with an OTA on the phone the past couple months. I think I may have ended up using a download from the Google site with FlashFire in April, so my only guess was that either using the Google download or a newer version of FlashFire is why I was later able to use the phone OTA with FlashFire for May and June.
SuperSU v2.79 SR3 with either the VerifiedBootSigner v3 or v8 has worked for me in May and June, and then I've taken the Play Store SuperSU update to v2.82. I don't have TWRP installed, and I get the impression there could be some extra steps for FlashFire when TWRP is installed, so I don't have to deal with that. Of course the only reason I switched to using FlashFire is because it seems like the quickest method to just take an OTA and update with SuperSU. If FlashFire didn't work so easily, I'd just go back to sideloading, or using one of the other update methods.

Related

[Q]Cannot OTA updates after rooting

I have had an issue where I cannot receive OTA updates. Whenever I check for updates the reply is: Software up to date as of <date,time>
I have rooted my tablet using the fastboot method however I originally accidentally flashed the OS to blank and softbricked my tablet. After installing the 5.0.1 factory image and installing it using fastboot, I then used CWM recovery to install SuperSU.zip to root the device, after doing this I could receive OTA updates. When I went to install them CWM aborted the update. I booted normally and selected "Clear update data", rebooted and now it always says that the device is up to date despite being on the 5.0.1 factory image.
My question is how can I go about getting OTA updates again? Also, will this involve further tweaking of files which may be risky as I have already messed everything up once.
Thank you.
EDIT: I have only just realised the grammatical error in the title but I can't change it now.
Just for clarification, are you trying to flash/sideload the OTA or are you attempting to use the tablet's built-in updater?
Nvidia pulled the 5.1 update. 5.0.1 is up to date.
Sent from my SHIELD Tablet using XDA Free mobile app
You can't get an OTA while rooted .. This is a very basic principle/consequence of rooting. There is no new 5.1 update since it was pulled a few months ago. I'm still waiting for it to get fixed but we might just get M at this rate. Rooting isn't risky if you understand what you are doing and what you shouldn't do. If you are responsible with the "power" of having a rooted device then I wouldn't worry about it.
I am waiting for the ability to flash the new OTA that was pushed on 29th. But yeah cannot pull and download the OTA while rooted.
Good evening, look nere: https://youtu.be/bT82lX40fuc
I just downloaded and installed while rooted with TWRP installed, no problem. I did have to re-flash TWRP and root, but TWRP had no trouble with the auto update.
Sent from my SHIELD Tablet using XDA Free mobile app

SuperSU Update Available in Playstore

In January I installed SuperSU 2.6.2-3 in accordance with this forum. Interestingly, today I received notification from the Playstore to update SuperSU to 2.65 (dtd Feb 01, 2016). I don't know why I received this notification from the Playstore since I did not install from there and did not receive this notification much earlier. Also, I assume updating to 2.65 through the Playstore would not be a good idea.
Chainfire has recently decided that SuperSU 2.65 was Stable. Only Stable versions get pushed to the Play Store, so that's why you got an update. I believe it will be safe to install, but be sure to make a backup via TWRP first.
Funcionando en Moto g 2015 xt1543 México [MM]
Probé la actualización y todo bien ? OK
TVD1903 said:
Chainfire has recently decided that SuperSU 2.65 was Stable. Only Stable versions get pushed to the Play Store, so that's why you got an update. I believe it will be safe to install, but be sure to make a backup via TWRP first.
Click to expand...
Click to collapse
But my first SuperSU flash was 2.65. And like many others on this forum who did the same, this version soft bricked my phone (stuck on unlocked boot loader screen). Are you saying 2.65 is safe to install on top of 2.6.2-3 but not safe as an initial install?
MrTooPhone said:
But my first SuperSU flash was 2.65. And like many others on this forum who did the same, this version soft bricked my phone (stuck on unlocked boot loader screen). Are you saying 2.65 is safe to install on top of 2.6.2-3 but not safe as an initial install?
Click to expand...
Click to collapse
I think so yes, as the new version was designed as a version to be compatible with every version of Android an to be installed over older versions. Do make a backup though, and if you are afraid, just don't do it. It won't hurt to stay on an older version for a while. You can install the update to the app because that will not immediately install the actual SuperSU update. Do not accept the prompt when opening the app for updating the binary in that case though.
TVD1903 said:
I think so yes, as the new version was designed as a version to be compatible with every version of Android an to be installed over older versions. Do make a backup though, and if you are afraid, just don't do it. It won't hurt to stay on an older version for a while. You can install the update to the app because that will not immediately install the actual SuperSU update. Do not accept the prompt when opening the app for updating the binary in that case though.
Click to expand...
Click to collapse
So what version of SuperSU do you have installed? How did you install that version? On top of a previous version or a fresh TWRP flash?
MrTooPhone said:
So what version of SuperSU do you have installed? How did you install that version? On top of a previous version or a fresh TWRP flash?
Click to expand...
Click to collapse
I am using a Custom ROM with SuperSU built-in. I have however also used the Stock ROM with SuperSU v2.65, installed using TWRP.
Got the same notification, updated fine, updated also su binaries (asked by the app) and - everything works fine. Stock 6.0.
Well I was reluctant to try based on my first experience flashing 2.65. But I accepted the update via Playstore, SuperSU updated the binaries, rebooted, and all is still good.
I would assume all those rooting the G3 MM for the first time should use 2.62-3 then upgrade to 2.65.
MrTooPhone said:
I would assume all those rooting the G3 MM for the first time should use 2.62-3 then upgrade to 2.65.
Click to expand...
Click to collapse
This is how I did mine when following the thread :
[GUIDE] [OSPREY] [MM] Install TWRP, Root and Xposed successfully on 6.0
Installed 2.62-3, then just received the 2.65 from the app store. No problems here either. Not sure about the TWRP update from 2.8.7 r7 to the 3.x.x versions though, but I am getting the impression that due to extensive changes it is not a good idea.
pjc123 said:
This is how I did mine when following the thread :
[GUIDE] [OSPREY] [MM] Install TWRP, Root and Xposed successfully on 6.0
Installed 2.62-3, then just received the 2.65 from the app store. No problems here either. Not sure about the TWRP update from 2.8.7 r7 to the 3.x.x versions though, but I am getting the impression that due to extensive changes it is not a good idea.
Click to expand...
Click to collapse
I have had no issues backing up with twrp-osprey-3.0.0-r2.img. I have not tried restoring yet.
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
pjc123 said:
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
Click to expand...
Click to collapse
don'tn worry ... the update works perfectly ...
..::Matr!x::.. said:
don'tn worry ... the update works perfectly ...
Click to expand...
Click to collapse
Thanks.
pjc123 said:
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
Click to expand...
Click to collapse
I have received several updates since 2.62-3. All have installed from playstore just fine including 2.79. As an initial installation, I think 2.62-3 was the only one that installed as systemless without forcing a systemless installation. Once you have a successful installation, all updates should be as well.
Sorry I'm not able to help you but you can help me. I soft brick my Moto g xt2541 twice due to different super su and wrong recoveries . Can you please provide me links u used to root. My issue is listed here. http://forum.xda-developers.com/2015-moto-g/help/unable-to-root-moto-g-2015-1-gb-model-t3523471 your help is much appriciated
Sent from my MotoG3 using Tapatalk
mirpuri said:
Sorry I'm not able to help you but you can help me. I soft brick my Moto g xt2541 twice due to different super su and wrong recoveries . Can you please provide me links u used to root. My issue is listed here. http://forum.xda-developers.com/2015-moto-g/help/unable-to-root-moto-g-2015-1-gb-model-t3523471 your help is much appriciated
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I followed these directions eleven months ago for the initial unlock bootloader, TWRP recovery and root, using the versions of SuperSU and TWRP listed, however I did not install Xposed.
http://forum.xda-developers.com/201...twrp-root-xposed-t3294588:confused::confused:
I have since updated to:
SuperSU 2.79
TWRP 3.0.2-r1
Caveat: My phone is a XT1540.

Phone rooted - How about the monthly security patches ?

I was wondering, I have rooted my phone using Chainfire's CF-Autoroot.
Normally this will disable OTA updates, I'm aware of that.
But is there some way to manually flash the monthly security updates that Samsung releases each month ?
(or at least they say they are going to release them each month).
Is there a source somewhere where we can download them and flash then using Odin or TWRP ?
No you didnt root. There isnt full root for s7 yet
vipercoyote said:
No you didnt root. There isnt full root for s7 yet
Click to expand...
Click to collapse
Are you sure ? Because when I check manually for updates, I get the message stating that my phone has changed (root) and so updates cannot be downloaded and installed. It says that I need to try to download it via a PC tool from Samsung.
vipercoyote said:
No you didnt root. There isnt full root for s7 yet
Click to expand...
Click to collapse
There is for the International version.
vipercoyote said:
No you didnt root. There isnt full root for s7 yet
Click to expand...
Click to collapse
There very well is for the Exynos version/type and the reason I'm tempted to get it after prices have dropped a bit :
Check it here: http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Ok guys, now that we have established that root is available and working for the European version (which I have)...
Anyone know if the monthly patches from Samsung/Google will be available for download somewhere, so we can flash it manually and still be up-to-date ?
I would like to know this as well. I would guess they could be flashed with Odin?
I would like to know this. I am on the W8 variant rooted with autoroot and wondering how will I go about updating to new patches.
Sent from my SM-G930W8 using Tapatalk
I love Android.
you should flash your firmware via Odin to unroot, apply OTA, root again with auto root.
exploreresp said:
you should flash your firmware via Odin to unroot, apply OTA, root again with auto root.
Click to expand...
Click to collapse
Yes, I am aware of this possibility.
I was just hoping in applying the monthly patch without full flash (which completely wipes the phone).
Indeed, flashing will reset the phone...I found that the hard way last night.
There is a topic on S7edge forum about Chainfire's FlashFire app. It claims that can flash without resetting the phone.
Did not try it but I will follow the discussions there. Would be perfect to flash a new f/w and not have the phone reset. ( like good old times
Maybe it is possible to prevent the userdata and internal storage to be wiped by flashing the official firmware ?
Anyone has succeeded to do so ?
I managed to download the complete new firmware G935FXXU1APD3 from Sammobile and flashed it with ODIN with the phone in download mode.
It did not overwrite any of my personal data or apps and the phone worked as before however you will need to root again afterwards, but that doesn't take long anyway.
The only other thing I had to do was copy the mixer_paths and mixer_gain files to the SD card then replace them as the new firmware overrides the volume hack if you have it in place.
Keith
I guess that's what Chainfire trying to achieve with Flashfire. To be able to directly flash the Updates without having to manually backup/restore anything. Let's see how this goes. As of today you could flash the full oding images within flashfire.
Will definitely try when the next update for my phone variant comes.
I did take a TWRP backup just in case but was pleasantly surprised when the phone booted back to where it was.
I can confirm that the Flashfire method can be used for updates. Grab the update package, flash it through flashfire, and even select the "ever root" option to maintain root. Works great!
databoy2k said:
I can confirm that the Flashfire method can be used for updates. Grab the update package, flash it through flashfire, and even select the "ever root" option to maintain root. Works great!
Click to expand...
Click to collapse
How did you get the update package? When trying to search for an update on the phone it says I modified it.
Or did you load an full stock rom?
brotbuexe said:
How did you get the update package? When trying to search for an update on the phone it says I modified it.
Or did you load an full stock rom?
Click to expand...
Click to collapse
Grabbed a full stock rom, extracted the modem and system packages, and flashed them specifically through flashfire. A link to the full stock rom was posted on the Canadian S7 thread in the discussion forum.

LG G5 H830 10a will not update

So I'm having an issue with updating my phone.
I have tried reading all of the threads, but so many things are still a mystery and are confusing. I haven't been able to get a full understanding of all of this.
I have a LG G5 H830 10a T-Mobile variant.
I am running Android 6.0.1
I have a custom recovery of TWRP
My phone is rooted with SuperSU also.
All I want to do, is to update my phone to Nougat. What is the process I have to go through? After reading all about it, here is my assumption:
I download Flashfire and use DisableService to disable my root and SuperSu, then I run the OTA Nougat update...
That didn't work. I got an error from TWRP that said:
"unable to flash update.zip from cache/update.zip, update is meant for "h1" device, your device is an H830"
Or something along those lines.
I have a Nandroid backup, so I'm not worried if I brick or soft brick it.
Any help please?
Thanks!
technocrat7 said:
So I'm having an issue with updating my phone.
I have tried reading all of the threads, but so many things are still a mystery and are confusing. I haven't been able to get a full understanding of all of this.
I have a LG G5 H830 10a T-Mobile variant.
I am running Android 6.0.1
I have a custom recovery of TWRP
My phone is rooted with SuperSU also.
All I want to do, is to update my phone to Nougat. What is the process I have to go through? After reading all about it, here is my assumption:
I download Flashfire and use DisableService to disable my root and SuperSu, then I run the OTA Nougat update...
That didn't work. I got an error from TWRP that said:
"unable to flash update.zip from cache/update.zip, update is meant for "h1" device, your device is an H830"
Or something along those lines.
I have a Nandroid backup, so I'm not worried if I brick or soft brick it.
Any help please?
Thanks!
Click to expand...
Click to collapse
You're not going to be able to update to Android N yet if you want to keep twrp and root. Only way to do it currently is if you have 100% stock phone and update via ota or using the zip file that was posted. If you don't care about root or twrp, update to 10j using the complete zip that autoprime posted and don't install SuperSU or dm-verity and let boot. You will have 100% stock and can take ota or use zip method. *** There is no current way to get root or twrp for t mobile version once on official android N yet *** So if root and twrp are important just wait until autoprime gets a chance to upload the flashable zip files for N to flash in twrp. You could also use cm or cm based Roms if you want android N, plus those are 7.1 stock is only 7.0, but if you want stock rooted just have to wait until it's released.
jeffsga88 said:
You're not going to be able to update to Android N yet if you want to keep twrp and root. Only way to do it currently is if you have 100% stock phone and update via ota or using the zip file that was posted. If you don't care about root or twrp, update to 10j using the complete zip that autoprime posted and don't install SuperSU or dm-verity and let boot. You will have 100% stock and can take ota or use zip method. *** There is no current way to get root or twrp for t mobile version once on official android N yet *** So if root and twrp are important just wait until autoprime gets a chance to upload the flashable zip files for N to flash in twrp. You could also use cm or cm based Roms if you want android N, plus those are 7.1 stock is only 7.0, but if you want stock rooted just have to wait until it's released.
Click to expand...
Click to collapse
Ohh okay, perfect thank you!
With that in mind, I had another question..
I have an LG V20 as well.
One thing I was thinking of doing was the following:
Unlocking the bootloader, putting a custom recovery like TWRP on it.
Make a Nandroid backup.
Then root it, and then go about my business. If something like this happens again and I want to update, I can simply do a Titanium Backup go to my Nandroid backup, restore it. Then update OTA, then reroot, run titanium backup restore, and then I'll be back where I left off.
will that work?
And one last question:
How would I go back to factory settings on my LG G5?
technocrat7 said:
Ohh okay, perfect thank you!
With that in mind, I had another question..
I have an LG V20 as well.
One thing I was thinking of doing was the following:
Unlocking the bootloader, putting a custom recovery like TWRP on it.
Make a Nandroid backup.
Then root it, and then go about my business. If something like this happens again and I want to update, I can simply do a Titanium Backup go to my Nandroid backup, restore it. Then update OTA, then reroot, run titanium backup restore, and then I'll be back where I left off.
will that work?
And one last question:
How would I go back to factory settings on my LG G5?
Click to expand...
Click to collapse
I'm not 100% sure but I don't think that would work as once you install twrp it modifies the recovery. IMG which would cause ota to fail. But on the other hand, you could most likely do the same method as the g5 to go back to official and take ota. Flashing the complete zip (if those are being created for the v20, haven't checked that thread as I don't own that device) and not re-installing the dm-verity or SuperSU will always reinstall the original boot.img and recovery.img and be 100% official stock. Hope this helps.
jeffsga88 said:
I'm not 100% sure but I don't think that would work as once you install twrp it modifies the recovery. IMG which would cause ota to fail. But on the other hand, you could most likely do the same method as the g5 to go back to official and take ota. Flashing the complete zip (if those are being created for the v20, haven't checked that thread as I don't own that device) and not re-installing the dm-verity or SuperSU will always reinstall the original boot.img and recovery.img and be 100% official stock. Hope this helps.
Click to expand...
Click to collapse
Thanks!
That helps a ton.
What is dm-verity though?
technocrat7 said:
Thanks!
That helps a ton.
What is dm-verity though?
Click to expand...
Click to collapse
The zip file we flash to disable force encryption (now this is part of the latest SuperSU zips).
jeffsga88 said:
The zip file we flash to disable force encryption (now this is part of the latest SuperSU zips).
Click to expand...
Click to collapse
Can you link to the latest superuser? Just wanna have it on hand for when the H830 N zip drops
carnivalrejectq said:
Can you link to the latest superuser? Just wanna have it on hand for when the H830 N zip drops
Click to expand...
Click to collapse
Here's the link to chainfires thread which will always have the latest beta supersu versions:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Something weird with Root.

Hello.
I have a Pixel with stock Android that was rooted with Chainfire SuperSU 2.78SR3
Last night I've noticed that the phone isn't rooted anymore and has installed the Feb security update OTA. (I only had the Nov update installed).
I've tried rerooting using the same method (Fastboot boot) and got stuck in a bootloop.
I had to flash a clean stock rom to get it out of the bootloop.
Next I installed TWRP. That worked.
Next I tried installing a ZIP version of SuperSU 2.78SR4. The Zip installs but when I boot into Android SuperSU says that the phone isn't rooted.
Anyone had anything similar happen to them?
Borrisl said:
Hello.
I have a Pixel with stock Android that was rooted with Chainfire SuperSU 2.78SR3
Last night I've noticed that the phone isn't rooted anymore and has installed the Feb security update OTA. (I only had the Nov update installed).
I've tried rerooting using the same method (Fastboot boot) and got stuck in a bootloop.
I had to flash a clean stock rom to get it out of the bootloop.
Next I installed TWRP. That worked.
Next I tried installing a ZIP version of SuperSU 2.78SR4. The Zip installs but when I boot into Android SuperSU says that the phone isn't rooted.
Anyone had anything similar happen to them?
Click to expand...
Click to collapse
You might need to flash back to stock to fix this. If you do let us know so we can help you save your data and apps.
You used the wrong SU. You need 2.79 SR3. Note the 9 on there, you used 2.78.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Copy it to your phone and boot to TWRP. Then INSTALL it from TWRP.

Categories

Resources