Related
I did do a search for "November Security Update" but didn't find anything.
Specifically I just received the November Security Update from Google but cannot apply it.
I am running a modified boot image to allow me to root the phone.
Is it possible all I have to do is return to unrooted status (disable SuperSU) and apply this patch?
UPDATE: LOL, that would be a resounding NO. It does say "Error in Recovery" but now the Update is gone.... and the Security Patch level still says 10/1
You have to fastboot flash system.img from factory image. Any OTA is not possible unless you are full stock, unmodified.
Not sure if the security updates end up packaged into system.img or not. If not, you will have to flash stock recovery, system and boot, then accept the OTA then re-flash custom recovery and re-root.
danarama said:
You have to fastboot flash system.img from factory image. Any OTA is not possible unless you are full stock, unmodified.
Not sure if the security updates end up packaged into system.img or not. If not, you will have to flash stock recovery, system and boot, then accept the OTA then re-flash custom recovery and re-root.
Click to expand...
Click to collapse
That's probably what will be needed as the security update is pretty fresh and proabably not in the stock system I would think. And then, to get back to rooted status, I would have to revert to the modified image, thus undoing the application of the security update? Ehhh, not going unrooted, oh well.
And thanks btw
Can't you adb sideload? Isn't that possible when the boot image is modified?
Sent from my Nexus 6 using Tapatalk
swa100 said:
Can't you adb sideload? Isn't that possible when the boot image is modified?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
No.. OTA checks for stock recovery, boot and system. Any amendment it will fail. It's in the zip file regardless of how you apply that zip, it will always fail.
Sent from my Nexus 6 using Tapatalk
I'm lost...please help
So I bought my unlocked Nexus 6 from Amazon. I was probably stupid, and was to impatient to wait for the OTA to Android 6. So I followed the Andriod Central instructions on how to do the basic download adb tools, unlock phone, flashed. the stock Andriod 6 image (MRA58K). And everything went great. I failed to relock, but it didn't seem to be a big deal.
Then I noticed I didn't get the November Security update.
Then I thought I needed to relock the phone. So I booted into the recovery and ran fastboot oem lock.
So now I am back to a fresh phone and I am downloading my apps in Google Play.
But the November Updates didn't come through.
What did I do wrong?
http://forum.xda-developers.com/nexus-6/help/nexus-6-mra58k-n-r-forced-encryption-t3242664/page2
jgriesshaber said:
So I bought my unlocked Nexus 6 from Amazon. I was probably stupid, and was to impatient to wait for the OTA to Android 6. So I followed the Andriod Central instructions on how to do the basic download adb tools, unlock phone, flashed. the stock Andriod 6 image (MRA58K). And everything went great. I failed to relock, but it didn't seem to be a big deal.
Then I noticed I didn't get the November Security update.
Then I thought I needed to relock the phone. So I booted into the recovery and ran fastboot oem lock.
So now I am back to a fresh phone and I am downloading my apps in Google Play.
But the November Updates didn't come through.
What did I do wrong?
Click to expand...
Click to collapse
Locked bootloader has nothing to do with it.
I’m sure this is very simple and I’m just not getting it…
got new moto x4 XT1900-1 from b&h
unlocked boot loader with motorola code
using windows fast boot was able to follow the "How to : Moto X4 Root & TWRP Recovery" bu Munchy on youtube to install twrp using payton 3.2.1-1
then installed Magish 17.1 which seems to be what actually rooted the phone as per confirmation by Root Check app shows 8.1.0
now I am getting constant ota notices of a security update OPWS28.3.2 and I download it and it fails which is apparently normal for a rooted phone.
Can I disable the root and update???…can this be done by turning off magic…or uninstalling it…or is this done by tarp?
I believe I should back up the recover image using twrp…then what?…find and boot to a stock image?
???
any info appreciated
tia
PS…I just tried the "topjohnwu Update OTA tutorial for v17" method in tips and tricks on here and it also said update failed???
jojojones said:
I’m sure this is very simple and I’m just not getting it…
got new moto x4 XT1900-1 from b&h
unlocked boot loader with motorola code
using windows fast boot was able to follow the "How to : Moto X4 Root & TWRP Recovery" bu Munchy on youtube to install twrp using payton 3.2.1-1
then installed Magish 17.1 which seems to be what actually rooted the phone as per confirmation by Root Check app shows 8.1.0
now I am getting constant ota notices of a security update OPWS28.3.2 and I download it and it fails which is apparently normal for a rooted phone.
Can I disable the root and update???…can this be done by turning off magic…or uninstalling it…or is this done by tarp?
I believe I should back up the recover image using twrp…then what?…find and boot to a stock image?
???
any info appreciated
tia
PS…I just tried the "topjohnwu Update OTA tutorial for v17" method in tips and tricks on here and it also said update failed???
Click to expand...
Click to collapse
What I did (might be an easier way but this was fast and easy):
1) Uninstall/remove Magisk.
2) Re-flash firmware over current system but don't do 'fastboot erase userdata'
3) Boot into your system and take all the OTA's
4) Re-install Magisk via TWRP
Took about 10 minutes. Longest part was waiting for OTA's to install.
Sorry...I'm new to all this. How do I reflash firmware?....use twrp app that is installed?
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
jhedfors said:
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
Click to expand...
Click to collapse
Did not work for me. Nothing has so far.
jojojones said:
Sorry...I'm new to all this. How do I reflash firmware?....use twrp app that is installed?
Click to expand...
Click to collapse
Use this guide:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Remove command "fastboot erase userdata" from script flash-all.bat/flash-all.sh.
jhedfors said:
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
Click to expand...
Click to collapse
I've tried this, and it didn't work. Ended up having to boot into TWRP, uninstall Magisk, and then reboot. Haven't bothered trying to update since I attempted that.
jhedfors said:
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
Click to expand...
Click to collapse
I spent a little while trying to apply OTA with magisk. The only way I was able to do it was to flash the stock firmware like everyone says. I could only find 8.0, so I had to flash the firmware, install 3 OTA's, then reinstall twrp/magisk.
The only thing I didn't try was installing magisk without twrp, which I believe is supported but I'm not sure. I think that might be the secret sauce to fixing it, but I'm not sure, and I haven't wanted to reflash and go through the whole process again.
tjololo12 said:
I spent a little while trying to apply OTA with magisk. The only way I was able to do it was to flash the stock firmware like everyone says. I could only find 8.0, so I had to flash the firmware, install 3 OTA's, then reinstall twrp/magisk.
The only thing I didn't try was installing magisk without twrp, which I believe is supported but I'm not sure. I think that might be the secret sauce to fixing it, but I'm not sure, and I haven't wanted to reflash and go through the whole process again.
Click to expand...
Click to collapse
If you have the xt1900-1 retus you can flash the android one firmware which is 8.1 (currently on the Aug 2018 security patch).
ptn107 said:
If you have the xt1900-1 retus you can flash the android one firmware which is 8.1 (currently on the Aug 2018 security patch).
Click to expand...
Click to collapse
I have the android one variant. Do you know where I can get the firmware? There's a new security patch and I'd like to try installing it with stock bootloader + magisk (installed from a temporary twrp boot) to see if that works with the OTA. I'd like to get the method working since android 9 is coming at some point.
tjololo12 said:
I have the android one variant. Do you know where I can get the firmware? There's a new security patch and I'd like to try installing it with stock bootloader + magisk (installed from a temporary twrp boot) to see if that works with the OTA. I'd like to get the method working since android 9 is coming at some point.
Click to expand...
Click to collapse
September 2018 OTA for Android One (Oreo 8.1):
Blur_Version.28.251.17.payton_fi.google_fi.en.US
Click to "Download" and save as ZIP file.
Only way how to apply OTA update with magisk rooted X4 is flash ROM using fastboot (august 2018 ROM is on AFH), remove command 'fastboot erase userdata' from script 'flash-all.bat', install september OTA from adb sideload/SD card and root again.
Comby_sk said:
September 2018 OTA for Android One (Oreo 8.1):
Blur_Version.28.251.17.payton_fi.google_fi.en.US
Click to "Download" and save as ZIP file.
Only way how to apply OTA update with magisk rooted X4 is flash ROM using fastboot (august 2018 ROM is on AFH), remove command 'fastboot erase userdata' from script 'flash-all.bat', install september OTA from adb sideload/SD card and root again.
Click to expand...
Click to collapse
Thanks, the rom is exactly what I was looking for, I just wasn't sure which one to use. I'd hate to install the wrong rom and mess something up.
EDIT: I did get a chance to try it and you're correct, there is no way to install an OTA to this device without fully reflashing the stock rom, taking the OTA, then installing Magisk. I tried the following steps:
1. Flash ROM given from androidfilehost
2. Reboot, wait for OTA notification
3. Boot to bootloader
4. use fastboot to temporarily boot twrp
5. flash magisk 17.1 zipfile
6. reboot to system, verify that magisk/root is installed
7. Uninstall magisk using magisk manager "Restore Images" as given in the tips.md file
8. Take OTA
the OTA still failed, so even though TWRP wasn't installed and it was still the stock recovery, I was unable to install the OTA. Shame, it'd be nice if we could get this to work, but oh well.
Hi everyone;
I have a rooted and unlocked Nokia 8 TA-1004 (Security Patch 1 July 2018; 00WW_4_88B_SP02).
I followed the guides on this very forum on how to root and unlock (first) and then how to put TWRP (after I already had rooted and unlocked).
The problem I'm having is exactly what the title says:
I have the possibility to update to SP of August but I just can't; it gives me an installation error as soon as it finishes downloading.
I already tried to Factory Reset the phone and when that didn't solve anything I tried (and succeded) putting TWRP hoping it would solve (hope never dies) the problem but it didn't.
I'm at a loss here, can anyone help me?
Xayar said:
Hi everyone;
I have a rooted and unlocked Nokia 8 TA-1004 (Security Patch 1 July 2018; 00WW_4_88B_SP02).
I followed the guides on this very forum on how to root and unlock (first) and then how to put TWRP (after I already had rooted and unlocked).
The problem I'm having is exactly what the title says:
I have the possibility to update to SP of August but I just can't; it gives me an installation error as soon as it finishes downloading.
I already tried to Factory Reset the phone and when that didn't solve anything I tried (and succeded) putting TWRP hoping it would solve (hope never dies) the problem but it didn't.
I'm at a loss here, can anyone help me?
Click to expand...
Click to collapse
This "problem" happens because the Android OS only updates the other partition set (A/B) when it's all stock and to achieve root thru Magisk we must patch the bootloader, making it unsuitable for the process.
You need to revert back to the official bootloader and then you'll be able to get it updated. After that just apply the patched bootloader to regain root/twrp and unfortunately that's what you gotta do on every update.
So uhhh how and where do I get the stock bootloader?
If I flash the magisk uninstaller I should get the stock boot image back because Magisk backs it up but I don't thing that alone does the trick.
What else do I need and where do I get it?
That's not an issue related to bootloader but rather to the patched boot.img existing on both paritions A/B. You'll have to restore Magisk backup image or reflash official June OTA and start updating the system without Magisk.
So if I just flash the Magisk uninstaller I will regain the ability to update?
Xayar said:
So if I just flash the Magisk uninstaller I will regain the ability to update?
Click to expand...
Click to collapse
Either you'll have ability to update or soft brick 50/50 odds
I don't like those odds ?
I tried restoring the boot image using Magisk's tool (since the version 17 there's the option of restoring the boot.img without actually uninstalling everything but it says it doesn't have any boot.img backed up...
I guess I'm back to square one and need to downgrade to the June update... Can I just flash it?
My phone was rooted, so I thought it could be the problem. So I made a factory reset and uninstalled magisk.
Anyway, it keeps failing to install a new security patch. It keeps trying to install and always says there was a problem in the installation. What could be causing it?
I'm running the stock OTA with december security patch, since january and february had annoying bugs.
matheusgoes said:
My phone was rooted, so I thought it could be the problem. So I made a factory reset and uninstalled magisk.
Anyway, it keeps failing to install a new security patch. It keeps trying to install and always says there was a problem in the installation. What could be causing it?
I'm running the stock OTA with december security patch, since january and february had annoying bugs.
Click to expand...
Click to collapse
Try flashing stock ROM, it worked for me
Firexxe69 said:
Try flashing stock ROM, it worked for me
Click to expand...
Click to collapse
I've never flash any ROM. Do you have any tutorial I can follow?
matheusgoes said:
I've never flash any ROM. Do you have any tutorial I can follow?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445/page68 download the fastboot version, then flash it using fastboot commands
Firexxe69 said:
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445/page68 download the fastboot version, then flash it using fastboot commands
Click to expand...
Click to collapse
you directly flashed update?
i cant update since december security patch and now if i flash march s.p. with fastboot that will work?
Maharram said:
you directly flashed update?
i cant update since december security patch and now if i flash march s.p. with fastboot that will work?
Click to expand...
Click to collapse
I never tried it, but when i'm on december patch, i flashed the december patch, then update it from system update. Make sure to backup your data because it may erase your data.
I tried to flash december s.p.
Got the message "Flashing error bluetooth_a" mi flash tool. Do someone know how to solve it?
I've just installed Magisk on my device. I tried to update my phone via OTA with this tutorial https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation but the update fails.
I didn't flash the recovery image
I solved my problem.
I did few modifications on the system partition with Adaway, so that's why the OTA didn't work. So I reflash the firmware, and I followed the steps for OTA updates, and that works now!
I have that problem again : I tried to update from 7 to 13 and failed all the time. Before that, I installed the November 1st patch and lost the root. So I downgraded to 7 to get root again.
At Step 3, the update stops at 56% before the update fails.
FoxyLove33 said:
I've just installed Magisk on my device. I tried to update my phone via OTA with this tutorial https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation but the update fails.
I didn't flash the recovery image
Click to expand...
Click to collapse
Hey man, can you link a tutorial to update the z3 play with security patches? Mine has bootloader unlocked and no other modifications. All stock. Updated upto july patch. Can you link a tutorial? and link for the patches (RETUS)? Thx.
e4noob said:
Hey man, can you link a tutorial to update the z3 play with security patches? Mine has bootloader unlocked and no other modifications. All stock. Updated upto july patch. Can you link a tutorial? and link for the patches (RETUS)? Thx.
Click to expand...
Click to collapse
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
FoxyLove33 said:
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Thanks. I tried the instructions on the ota link, but am still getting Software Update unsuccessful?
FoxyLove33 said:
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Hi,
I'm having a similar issue with the OTA installation after getting magisk root using the Boot Image Patching method. The tutorial shows several different methods, but so far I haven't had luck with any of them. I tried the one for "Devices with A/B Partitions" and got as far as flashing the original boot image back but the OTA still wouldn't install. The flashfire method wouldn't work because flashfire says it isn't compatible with "20.1:MAGISKSU". I didn't touch the recovery partition and I am using the same file I used to create the patched magisk boot image (without the alteration) to try to get back to stock boot image. I'm not sure what else to do aside from using LMSA to reflash stock. My concern with that (aside from having to reconfigure everything) is that I don't have the latest boot.img from the 1-9 firmware to patch it in Magisk and I don't yet know if I can use the 1-6 firmware modified boot.img file.