I started the process of updating to Feb security patch. It fails just before it finishes installing. Is this because I have the bootloader and cridical bootloader unlocked? Would relocking them both fix this issue?
No I have a full unlocked bootloader, if it failed, more than likely you are not stock.
dratsablive said:
No I have a full unlocked bootloader, if it failed, more than likely you are not stock.
Click to expand...
Click to collapse
I do believe I am on stock. This happened last month. I ended up having to use the tool kit to flash the Jan factory image. Rather not do that again and start from scratch. Plus I do not want to do this every time there is an update.
How can i make sure I am 100% stock, or get myself back to 100% stock?
chadhoard said:
I do believe I am on stock. This happened last month. I ended up having to use the tool kit to flash the Jan factory image. Rather not do that again and start from scratch. Plus I do not want to do this every time there is an update.
How can i make sure I am 100% stock, or get myself back to 100% stock?
Click to expand...
Click to collapse
If your rooted or have twrp installed, the OTA will fail. Do you have either of those?
Badger50 said:
If your rooted or have twrp installed, the OTA will fail. Do you have either of those?
Click to expand...
Click to collapse
I was rooted with twrp, but when I flashed the factory image last month, I believe I removed twrp and went back to stock recovery. I have yet to re-root since all of that mess last month.
chadhoard said:
I was rooted with twrp, but when I flashed the factory image last month, I believe I removed twrp and went back to stock recovery. I have yet to re-root since all of that mess last month.
Click to expand...
Click to collapse
Ok. If you have run both bootloader unlock commands.....
fastboot flashing unlock
And
fastboot flashing unlock_critical
Then why not just fastboot the factory image? You can do it without wiping data :good:
Badger50 said:
Ok. If you have run both bootloader unlock commands.....
fastboot flashing unlock
And
fastboot flashing unlock_critical
Then why not just fastboot the factory image? You can do it without wiping data :good:
Click to expand...
Click to collapse
Sorry, don't remember why I did what I did last month. I just want to get up to date with Feb. and not have to deal with it failing next month. I am pretty certain I am not root and have stock recovery. I am debating if I should relock the bootloader.
chadhoard said:
Sorry, don't remember why I did what I did last month. I just want to get up to date with Feb. and not have to deal with it failing next month. I am pretty certain I am not root and have stock recovery. I am debating if I should relock the bootloader.
Click to expand...
Click to collapse
Relocking the bootloader will not help you. In fact, if you relock the bootloader, you are removing your ability to correct whatever is causing the update to fail. Also, unlike some older devices, relocking will wipe your data, so there's that. Based on what you've said so far, I'm not quite sure why the update is failing, so I echo the recommendation that has been made already to use the factory image to update. Just remove the -w flag in the batch file before using it to avoid wiping your data.
Anyone getting Bluetooth Audio issues of the FRb security patch? Not sure if it's the update or the EX Kernel but my bluetooth earbuds keep disconnecting the audio is staticky and "skips" My garmin watch seems to stay connected fine and the headphones connect fine to another phone.
chadhoard said:
I started the process of updating to Feb security patch. It fails just before it finishes installing. Is this because I have the bootloader and cridical bootloader unlocked? Would relocking them both fix this issue?
Click to expand...
Click to collapse
What is the exact error you are getting, and what are the exact steps you are taking?
uicnren said:
What is the exact error you are getting, and what are the exact steps you are taking?
Click to expand...
Click to collapse
It just stated that the install failed. It gave me the option to retry.
Last night I was able to ADB into recovery. Then ADB sideload the OTA.
chadhoard said:
It just stated that the install failed. It gave me the option to retry.
Last night I was able to ADB into recovery. Then ADB sideload the OTA.
Click to expand...
Click to collapse
Follow these steps, I've been using them since early 8.0 and never had an issue.
If you want to remain 100% stock, ONLY fastboot the Feb factory image and skip the rest of the steps.
If you want to be fully loaded' Feb update, TWRP, Cust Kernel, Root, follow all the steps
They're pretty detailed, and easy to follow.
Related
Hi hope someone can verify.
I'm running stock 3.2.7 unrooted with stock recovery. The bootloader is still unlocked as I tried out a few custom ROMs about a month back. I now want to wipe and sell the phone so need to lock the bootloader. Can I just do the standard OEM lock in adb or should I also sideload the full 3.2.7 update zip again?
Thanks
just oem lock it. but everything will be removed when you do that.
Playa82 said:
just oem lock it. but everything will be removed when you do that.
Click to expand...
Click to collapse
Thanks, I thought so but I had to check. Strange... after rooting phones and installing custom ROMs for maybe 8 years, I don't think I've ever relocked a bootloader.
It's safer to flash stock again then to relock bootloader, even if you think you are stock (including recovery) maybe you are not.
But except the booting screen, you won't gain anything from relocking bootloader, even the warranty will work with bootloader unlocked.
SpaceGooner said:
Hi hope someone can verify.
I'm running stock 3.2.7 unrooted with stock recovery. The bootloader is still unlocked as I tried out a few custom ROMs about a month back. I now want to wipe and sell the phone so need to lock the bootloader. Can I just do the standard OEM lock in adb or should I also sideload the full 3.2.7 update zip again?
Thanks
Click to expand...
Click to collapse
Deleted my comment for incorrect information
Le_Zouave said:
It's safer to flash stock again then to relock bootloader, even if you think you are stock (including recovery) maybe you are not.
But except the booting screen, you won't gain anything from relocking bootloader, even the warranty will work with bootloader unlocked.
Click to expand...
Click to collapse
Thanks, but I plan to sell my OP3 to a high street store that buys and sells second-hand phones and tablets. Although it's only 3 months old and in immaculate condition, I'm guessing they may be reluctant to buy it if the start up screen says 'this phone can't be trusted...'
No choice in this situation - I will need to relock the bootloader I guess.
If you lock the bootloader, everything will be wiped and phone won't boot till you flash OOS.
ungeeked said:
If you lock the bootloader, everything will be wiped and phone won't boot till you flash OOS.
Click to expand...
Click to collapse
Thank you. So after OEM lock, when you say flash OOS do you mean sideload a full update zip? That's what I was asking in my original post.
SpaceGooner said:
Thank you. So after OEM lock, when you say flash OOS do you mean sideload a full update zip? That's what I was asking in my original post.
Click to expand...
Click to collapse
Yup.
SpaceGooner said:
Thank you. So after OEM lock, when you say flash OOS do you mean sideload a full update zip? That's what I was asking in my original post.
Click to expand...
Click to collapse
Follow:
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
ritchiedrama said:
Follow:
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
Click to expand...
Click to collapse
Ta mate. I already saw that thread but as I'm running a clean sideloaded OOS that has never been rooted, I am already back to stock. Anyway, as opinion seems to be divided on whether OEM lock alone is enough, I will also sideload a full OOS update zip again to be sure.
Won't be doing it for a few days though so it's all academic at the moment.
ritchiedrama said:
Follow:
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
Click to expand...
Click to collapse
i did that guide too. i came from cm13. thiss guide works perfect if you follow all steps exactly.
I cannot update to Oreo on my Sprint variant. I was rooted with TWRP but did the flash all back to stock. I am unrooted, stock recovery, with unlocked bootloader. I have tried through update.zip, sideload, and the normal way through the settings and they all fail. I successfully updated the normal way with the last 2 updates that were released, but no luck with this one.
Comet1966 said:
I cannot update to Oreo on my Sprint variant. I was rooted with TWRP but did the flash all back to stock. I am unrooted, stock recovery, with unlocked bootloader. I have tried through update.zip, sideload, and the normal way through the settings and they all fail. I successfully updated the normal way with the last 2 updates that were released, but no luck with this one.
Click to expand...
Click to collapse
Very weird as I was in the same predicament as you with being rooted with twrp & having to use flash all to go back to stock, but I was able to take the Oreo ota with no problems afterwards.
Sent from my Moto Z (2) using Tapatalk
piscesjoey said:
Very weird as I was in the same predicament as you with being rooted with twrp & having to use flash all to go back to stock, but I was able to take the Oreo ota with no problems afterwards.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
It's like the system and recovery don't have access to the storage at all.
Which flash all did you use? mine updated just fine with that file doing adb sideload file/name/here when selecting the option for update via adb. How long did it take before the error. It takes awhile for the update to go through. (roughly the same time or longer than updating in android. my time was about 12mins.
Uzephi said:
Which flash all did you use? mine updated just fine with that file doing adb sideload file/name/here when selecting the option for update via adb. How long did it take before the error. It takes awhile for the update to go through. (roughly the same time or longer than updating in android. my time was about 12mins.
Click to expand...
Click to collapse
It got to 47% then started to flash and then the error that's for the sideload. As for the update.zip and applying it, it fails instantly.
I think I did this one: https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
Comet1966 said:
It got to 47% then started to flash and then the error that's for the sideload. As for the update.zip and applying it, it fails instantly.
I think I did this one: https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
Click to expand...
Click to collapse
So, you flashall and then it doesn't take Oreo but all others? Sounds like something is really messed up on your device then. Did you flash a modified logo bin?
Uzephi said:
So, you flashall and then it doesn't take Oreo but all others? Sounds like something is really messed up on your device then. Did you flash a modified logo bin?
Click to expand...
Click to collapse
I did the flashall and that's it. I have no idea what's up with it
Comet1966 said:
I did the flashall and that's it. I have no idea what's up with it
Click to expand...
Click to collapse
What is your current version? -11/November patch?
Uzephi said:
What is your current version? -11/November patch?
Click to expand...
Click to collapse
This
Comet1966 said:
This
Click to expand...
Click to collapse
That isn't one of the flash all's in the thread. You need to run the bat file. Depending on the one you use you should go to the August or September security patch.
Uzephi said:
That isn't one of the flash all's in the thread. You need to run the bat file. Depending on the one you use you should go to the August or September security patch.
Click to expand...
Click to collapse
I am trying that one again. Factory reset didn't help either.
I did the flashall to 122-59-8. Now I am updating to 122-59-8-6
Comet1966 said:
I did the flashall to 122-59-8. Now I am updating to 122-59-8-6
Click to expand...
Click to collapse
Which version of the bootloader? If the Oreo bootloader then perhaps this will result in an error.
If you installed Oreo Global or TMO after that, the bootloader will be upgraded to Oreo, perhaps this will lead to an error.
So I did the flashall, updated all the way through and it worked. It was the same flash all I did before because I already had it downloaded. Thanks for helping, sucks I had to wipe, but it is what it is.
Comet1966 said:
So I did the flashall, updated all the way through and it worked. It was the same flash all I did before because I already had it downloaded. Thanks for helping, sucks I had to wipe, but it is what it is.
Click to expand...
Click to collapse
Wow, must've been some kind of bad flash previously? Either way glad that you've finally joined the rest of us!
Sent from my Moto Z (2) using Tapatalk
Just unlocked, rooted (w/Magisk), and installed TWRP about a week ago. I'm on the stock ROM with the Feb security update. The March security update is pushing to my phone but fails install due to the previous mentioned items. I'm reading that a few problems are popping up that are contributed to the update so I'm holding off on installing it for now. How can I get it to quit trying to install it and showing the notification in the status bar? You can't dismiss the notification and if you reboot it tries to install the update again..
How did you install TWRP and keep it across updates?
Thanks for the response! I'm not 100% sure what you're asking, but I installed TWRP and magisk while on 8.1.0 and the Feb 2018 security update. A week or two later the March security update was released and pushed to my phone as an OTA but it fails install due to (and I'm guessing) the unlocked bootloader and root. Now I constantly have a failed install message in my notification bar and it won't go away. How can I keep the phone from attempting to install the OTA Update knowing it will fail?
the ota update is failing to install because your phone is rooted. the bootloader can be unlocked, but otas will fail to install if the os is not completely stock.
if you manually flash the march update, whether it's the ota or the full factory image, the notifications about an update being available or the failed install will go away.
altwu said:
the ota update is failing to install because your phone is rooted. the bootloader can be unlocked, but otas will fail to install if the os is not completely stock.
if you manually flash the march update, whether it's the ota or the full factory image, the notifications about an update being available or the failed install will go away.
Click to expand...
Click to collapse
I understand the reason it's failing. I don't really want to install the the OTA as I'm reading it has created additional problems. Is there anyway to keep the phone from checking for an update and subsequently failing and showing the notification?
Gulfstream 650 said:
I understand the reason it's failing. I don't really want to install the the OTA as I'm reading it has created additional problems. Is there anyway to keep the phone from checking for an update and subsequently failing and showing the notification?
Click to expand...
Click to collapse
When I got the notification to update, I just long pressed on it and hit the toggle to turn off notifications from whatever it was that it said it was coming from...Google play services I think?
Sent from my Pixel XL using XDA Labs
I flashed the full March Factory Image using the bat.all script (-w removed to keep data), then fastbooted into twrp 3.2.0.0 and flashed magisk. No additional problems or any issues at all.
kboya said:
I flashed the full March Factory Image using the flash-all.bat script (-w removed to keep data), then fastbooted into twrp 3.2.0.0 and flashed magisk. No additional problems or any issues at all.
Click to expand...
Click to collapse
Did you try turning off automatic update in Developer mode.
No, to me that is a no no especially if you have Flashfire installed
Gulfstream 650 said:
I understand the reason it's failing. I don't really want to install the the OTA as I'm reading it has created additional problems. Is there anyway to keep the phone from checking for an update and subsequently failing and showing the notification?
Click to expand...
Click to collapse
kboya said:
I flashed the full March Factory Image using the bat.all script (-w removed to keep data), then fastbooted into twrp 3.2.0.0 and flashed magisk. No additional problems or any issues at all.
Click to expand...
Click to collapse
same here. no problems with the march update + magisk. i've never updated using an ota. i always flash the full factory image.
Gulfstream 650 said:
Thanks for the response! I'm not 100% sure what you're asking, but I installed TWRP and magisk while on 8.1.0 and the Feb 2018 security update.
Click to expand...
Click to collapse
Let me elaborate:
Right now, if you install TWRP permanently, you don't get any OTAs. So you must install a full image. When you install the full image, TWRP get's wiped. So you always have to install TWRP using your computer. That's a real hassle for me.
Or is there any easy way how you can install a full image, while keeping TWRP or reinstalling TWRP on top without using a computer?
fiverings said:
Did you try turning off automatic update in Developer mode.
Click to expand...
Click to collapse
I'm not sure if this is a question to me or the OP!
Me? No, there's no need as once flashed any OTA notification is redundant and no longer displayed. Anyway, I usually dl and flash the new factory image when it's posted online. The whole process takes maybe 20 mins including the dl time. Also, if there are any "new issues" with a release, as the OP is suggesting, it's just as easy to go back a month with the previous factory image (easier as it's already dl'd)
kboya said:
I'm not sure if this is a question to me or the OP!
Me? No, there's no need as once flashed any OTA notification is redundant and no longer displayed. Anyway, I usually dl and flash the new factory image when it's posted online. The whole process takes maybe 20 mins including the dl time. Also, if there are any "new issues" with a release, as the OP is suggesting, it's just as easy to go back a month with the previous factory image (easier as it's already dl'd)
Click to expand...
Click to collapse
Good point, it's fairly easy to revert to the previous version if problems crop up. I'm going to go ahead and make the plunge. **edit** installed the March image and reinstalled TWRP and Magisk, so far so good.
Cool. Hope it stays that way.
Hi, I just tried to install the September OTA update based on the Magisk OTA installation tips however the installation of the update fails during step 1. At least I am still rooted on the August patch level. How can I update my phone without losing data? I thought about reflashing system and trying the steps again but I don't know where to get the factory images for 9.6.6.0 (August) or 9.6.8.0 (September). This is my first A/B phone by the way. Thanks in advance.
rfkd said:
Hi, I just tried to install the September OTA update based on the Magisk OTA installation tips however the installation of the update fails during step 1. At least I am still rooted on the August patch level. How can I update my phone without losing data? I thought about reflashing system and trying the steps again but I don't know where to get the factory images for 9.6.6.0 (August) or 9.6.8.0 (September). This is my first A/B phone by the way. Thanks in advance.
Click to expand...
Click to collapse
You can check @BubuXP's reply here it might help you out. :good:
On this page only the ROM for 9.6.4.0 (July) can be downloaded. Later versions are not available anywhere? If not I have to flash July with fastboot, root again and retry the OTA update?
rfkd said:
On this page only the ROM for 9.6.4.0 (July) can be downloaded. Later versions are not available anywhere? If not I have to flash July with fastboot, root again and retry the OTA update?
Click to expand...
Click to collapse
No, the only fastboot image at the moment is this. It should be not a problem downgrading, as long as the same Android version is involved (Oreo 8.1 in this case).
And yes, you can flash that fastboot image and then follow my guide to install Magisk, and then install the OTA update always following my guide, just to test that everything is working as intended.
This did not work. Seems like using flash_all_except_storage.bat was not the right choice, my unlock pattern during booting is not accepted.
rfkd said:
This did not work. Seems like using flash_all_except_storage.bat was not the right choice, my unlock pattern during booting is not accepted.
Click to expand...
Click to collapse
So you must use flash_all.bat, but you will lose your data. At the moment the data is in the phone memory, but is encrypted and you probably lost the decryption key when you flashed the other partitions, so not a great lose anyway.
I don't know if there is a way to get your data back.
Yes, I already did this. Had forgotten to disable the pattern.
Hello, I have pixel 2xl with unlocked boodloader, and my security patch is stack on 05. September... When I check for updates it says that my software is latest... But in security settings it says that security patch is old...should I lock bootloader? Will I receive OTA updates normaly etc
In CPY Z says that my device is not rooted, thanks in advance...
markokrstic0507 said:
Hello, I have pixel 2xl with unlocked boodloader, and my security patch is stack on 05. September... When I check for updates it says that my software is latest... But in security settings it says that security patch is old...should I lock bootloader? Will I receive OTA updates normaly etc
In CPY Z says that my device is not rooted, thanks in advance...
Click to expand...
Click to collapse
You have a few options. You could factory reset, then see if you get your OTA. You could also lock the bootloader, which wipes your device as well, then, yes, you will get normal OTA's. Or, you can adb side load the OTA zip from October, then November, then December to be up to date. Or, you can fastboot the factory images to get up to speed. Or, you can fastboot into twrp, then flash the OTA zips. And there ya go
Badger50 said:
You have a few options. You could factory reset, then see if you get your OTA. You could also lock the bootloader, which wipes your device as well, then, yes, you will get normal OTA's. Or, you can adb side load the OTA zip from October, then November, then December to be up to date. Or, you can fastboot the factory images to get up to speed. Or, you can fastboot into twrp, then flash the OTA zips. And there ya go
Click to expand...
Click to collapse
Tnx for fast reply
@Badger50: He doesn't have to install all three, but only the December OTA. Since the OTA zips Google makes available for download are full images they include all the patches from previous months.
Strephon Alkhalikoi said:
@Badger50: He doesn't have to install all three, but only the December OTA. Since the OTA zips Google makes available for download are full images they include all the patches from previous months.
Click to expand...
Click to collapse
Roger that my friend. I've just seen some folks have trouble when updating after a few months :good:
@Badger50: Understood there. I should have known there was a reason for you mentioning it.
I had the same problem when i buy my used pixel 2 xl, i solved the problem by this way
visit: https://www.google.com/android/beta
and unsubscribe my device from beta program. After some hours i receive ota
I have done factory data reset and there is an update, but it can't install, instalation problem... And its trying every few hours but it cant... Bootloader still unlocked
markokrstic0507 said:
I have done factory data reset and there is an update, but it can't install, instalation problem... And its trying every few hours but it cant... Bootloader still unlocked
Click to expand...
Click to collapse
Have you flashed TWRP? If so, you cannot update via OTA. This only works with the stock recovery.
You have to flash a full OTA via TWRP or flash the factory image with fastboot if you are using TWRP.
And if you don't use TWRP, you still can update manually. Why are you waiting for the automatic update in the first place?
I have unlocked bootloader, my phone is not rooted, when I try to update my phone tru settings and Sysrem update it starts and than stops (couldn't install update)
BabelHuber said:
Have you flashed TWRP? If so, you cannot update via OTA. This only works with the stock recovery.
You have to flash a full OTA via TWRP or flash the factory image with fastboot if you are using TWRP.
And if you don't use TWRP, you still can update manually. Why are you waiting for the automatic update in the first place?
Click to expand...
Click to collapse
I have unlocked bootloader, my phone is not rooted, when I try to update my phone tru settings and Sysrem update it starts and than stops (couldn't install update)
markokrstic0507 said:
I have unlocked bootloader, my phone is not rooted, when I try to update my phone tru settings and Sysrem update it starts and than stops (couldn't install update)
Click to expand...
Click to collapse
This has nothing to do with root, but with TWRP. Have you flashed it or not?
You can try to flash the boot.img again, too. Extract it from the factory image and flash it with fastboot. Of course this only helps if you have messed around with it.
If this doesn't work you can try a factory reset or flash the update manually. See https://developers.google.com/android/images for instructions.