Related
For those of us that have not installed a custom recovery, will be below method work of restoring stock boot image for installing updates to the o t a? I see that a few people have already gotten the December OTA.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
is the dec update already 8.1 or just the security update?
pa.pn2 said:
is the dec update already 8.1 or just the security update?
Click to expand...
Click to collapse
8.1
Factory images are up as well.
Cowbell_Guy said:
For those of us that have not installed a custom recovery, will be below method work of restoring stock boot image for installing updates to the o t a? I see that a few people have already gotten the December OTA.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
I've been asking this question since the November OTA and have yet to get a confirmation either way whether it works or fails.
I'd love to try myself but I'm currently traveling for work and I can't risk bootlooping my phone or being without WiFi tethering.
Jexx11 said:
I've been asking this question since the November OTA and have yet to get a confirmation either way whether it works or fails.
I'd love to try myself but I'm currently traveling for work and I can't risk bootlooping my phone or being without WiFi tethering.
Click to expand...
Click to collapse
What worked for me was,
Download Nov factory image
Unzip
Edit flash-all. Bat and remove the - w at the end
Reboot into bootloader
Run flash-all
Reboot
Download Dec ota zip
Reboot recovery
Update from adb
Choose Dec ota zip
Reboot
From there i installed twrp and magisk everything working fine on 8.1
Has anyone tried this yet?
I just went to try this method, and it's getting hung up?
Its not working for me. I flashed stock Dec 2017 build, and then I install Magisk Manager and told it to "install," patched the boot file from the Dec 2017 factory build, copied it to computer, then fastboot flash boot patched_boot.img. On boot, magisk manager says "Magisk not installed," safetynet is failing, and root checker says I have no root.
Anyone having any luck? What are ya'll doing differently?
Jdban said:
Its not working for me. I flashed stock Dec 2017 build, and then I install Magisk Manager and told it to "install," patched the boot file from the Dec 2017 factory build, copied it to computer, then fastboot flash boot patched_boot.img. On boot, magisk manager says "Magisk not installed," safetynet is failing, and root checker says I have no root.
Anyone having any luck? What are ya'll doing differently?
Click to expand...
Click to collapse
did you enable the beta channel within magisk? That will get you the newest version?
CyberpodS2 said:
did you enable the beta channel within magisk? That will get you the newest version?
Click to expand...
Click to collapse
Thanks! That did it!
CyberpodS2 said:
did you enable the beta channel within magisk? That will get you the newest version?
Click to expand...
Click to collapse
I didn't do that initially but will try now
Jdban said:
Thanks! That did it!
Click to expand...
Click to collapse
Really? Nice. Mind positing your exact steps? (
Jdban said:
Thanks! That did it!
Click to expand...
Click to collapse
Really? Nice. Mind positing your exact steps? (
Cowbell_Guy said:
Really? Nice. Mind positing your exact steps? (
Click to expand...
Click to collapse
What I did:
Install Dec 2017 factory build (without the -w flag so it doesn't wipe)
Install latest Magisk Manager
Enable beta channel in Magisk Manager
Copy the boot.img file from the factory build onto the phone
In Magisk, click install -> Patch boot image file
Copy patched boot file from phone to computer
reboot to bootloader
flash patched boot.mg via
Code:
fastboot flash boot patched_boot.img
Jdban said:
What I did:
Install Dec 2017 factory build (without the -w flag so it doesn't wipe)
Install latest Magisk Manager
Enable beta channel in Magisk Manager
Copy the boot.img file from the factory build onto the phone
In Magisk, click install -> Patch boot image file
Copy patched boot file from phone to computer
reboot to bootloader
flash patched boot.mg via
Click to expand...
Click to collapse
Ah, okay. Thanks for sharing I take it though you didn't use the Top John Woo method, Lincoln the original post oh, that supposedly doesn't require the use of a computer.
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.
Anyone have issues doing ota updates after relocking bootloader? I unlocked my bootloader. Installed magisk for root. Did modifications to by pass wifi hot spot authentication. Installed squeeze gesture for different actions. And now I want to revert back. Was still on stock.
Uninstalled magisk. Factory reset. Relocked boot loader. Then tried to install ota which would sit at 0% downloading and eventually fail.
My method, because I can't wait for OTA notifications:
1. Tap on the Complete Uninstall of Magisk and reboot.
2. Download OTA full image and install it using adb sideload.
3. Reinstall Magisk and patch the boot image (Need to download new factory image and unzip file).
4. Use fastboot to flash patched boot image and reboot.
5. Finished.
I would flash the factory image (of course you have to unlock the bootloader again) before locking it
y2whisper said:
I would flash the factory image (of course you have to unlock the bootloader again) before locking it
Click to expand...
Click to collapse
Thanks. Noob question. Keep seeing people say its very easy to brick my phone when I try to relock bootloader.. Does factory image mean the very first version released? Pixel 3 xl -9.0.0 (PD1A.180720.030, Sep 2018). Then after I will be able to ota update to current version? Or are all crosshatched files considered factory image. So any image will work?
Nevermind, I got it to go through. First time I actually used the newest feb 05 2019 file to flash. After I relocked my boot loader, I loaded a backup from my google account. That seems to kick me back down to jan 05 2019 security update version. This first time the ota would get stuck @ 0% and not do anything. I redid the whole thing using a dec 2018 file. After I relocked my boot loader and reloaded my backup from my google account. I was back at jan 05 2019.. prob due to reloading a backup. Now the ota feb 05 2019 is actually installing. Might've been a fluke. Thanks.
ychongy13 said:
Thanks. Noob question. Keep seeing people say its very easy to brick my phone when I try to relock bootloader.. Does factory image mean the very first version released? Pixel 3 xl -9.0.0 (PD1A.180720.030, Sep 2018). Then after I will be able to ota update to current version? Or are all crosshatched files considered factory image. So any image will work?
Click to expand...
Click to collapse
...very easy to brick my phone...
It means if you relock the bootloader and you are not 100% stock (No Custom ROM, Custom Kernel, T.W.R.P, Magisk, etc., residual files remain on your phone). You run the risk of bricking your phone.
Two ways to return the phone to stock:
- flash-all with the -w
- Settings > System > Advanced > Reset options > Erase all data (factory reset)
Just got the march security update. 490mb.
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
swieder711 said:
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
Click to expand...
Click to collapse
My phone went into bootloop today after updating Magisk (magisk update prompt), BEFORE march update. That was a bit odd. Maybe your bootloop has nothing to do with March update, but with the new magisk version being flashed is incompatible to certain modules.
Well hell, I am failing.....and understand the message, but dont understand why or what transpired....and not sure what bootloader the message refers to.....this is a factory flash....
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'slider-1.0-8062051'.
Update requires 'slider-1.1-8118264'.
fastboot: error: requirements not met!
Hmm, now not exactly sure what to do....8062051 is the bootloader from the 2nd February image, so not sure where to get 8118264 so I can update.......very odd.
***EDIT: OK I see thats the bootloader from A12L not from A12.......wtf!!!!
****RE-EDIT: PEBCAK here on my end.....doh! Working now
Same here, just checked and it showed up.
I was running into issues flashing the Factory image via Fastboot so I decided to try the FLASH method from the Android Flash Tool. That worked. But when I try to install the Magisk patch file, it fails and then I get stuck in a bootloop. So there you have it. I'm going to have to deal with no root until someone figures out what's going on.
swieder711 said:
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
Click to expand...
Click to collapse
Once I disabled the Typhus ROM Control module in Magisk then my phone booted with root enabled with 24.304. Magisk stable probably works too.
TimFlex said:
Just got the march security update. 490mb.
Click to expand...
Click to collapse
This in more in line with the following thread which is where you need to bring this discussion. We really don't need another misleading thread that is merely a Magisc "how do I...?"
April 10, 2023 TQ2A.230405.003.E1 Global - Root Pixel 6 Pro [Raven] / all relevant links
Pixel 6 Pro [Raven] March 9, 2023 I recommend sticking with 33.0.3. Note that two users in my Pixel 7 Pro thread have said that 34.0.1 did not work correctly for them. Someone reported it to Google (added a comment about 34.0.1 to the existing...
forum.xda-developers.com
Same issue here. Flashed March factory image. No wipe flag. Flashed Magisk patched file. Stuck in bootloop.
Reflashed factory image and didn't flash boot image and I can boot up. I guess no root until this is fixed.
I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to Platform TooIs Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. Now on March build with no data loss I then fastboot flashed the patched boot.img and have root
I had the same problem with Feb v2 OTA sideload (Maybe because I had a custom kernel?) anyway, I think the Android Flash Tool will be my go to for future updates
jcp2 said:
I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to Platform TooIs Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. Now on March build with no data loss I then fastboot flashed the patched boot.img and have root
I had the same problem with Feb v2 OTA sideload (Maybe because I had a custom kernel?) anyway, I think the Android Flash Tool will be my go to for future updates
Click to expand...
Click to collapse
Can you upload your patched file by any chance?
tonyfiore75 said:
Can you upload your patched file by any chance?
Click to expand...
Click to collapse
This is for Magisk Stable - Not Canary!!
Thesis so much @jcp2 !
Does the uninstall Magisk, OTA, and then reinstall Magisk work with this update? If so, what version of Magisk do we know that works?
Last time I lost everything on my phone. Not trying to do that again.
mkhcb said:
Does the uninstall Magisk, OTA, and then reinstall Magisk work with this update? If so, what version of Magisk do we know that works?
Last time I lost everything on my phone. Not trying to do that again.
Click to expand...
Click to collapse
Edit>>>> As long as you're on stock kernel, Canary is fine.
jcp2 said:
IDK but 100% sure to stay on Magisk Stable and not Canary --- Canary will cause bootloops!
Click to expand...
Click to collapse
I rolled back to Stable and still cannot gain back root....
I sideloaded the March OTA then rooted successfully with 24.3, but I didn't do the magisk uninstall.
jcp2 said:
IDK but 100% sure to stay on Magisk Stable and not Canary --- Canary will cause bootloops!
Click to expand...
Click to collapse
Not accurate. Using latest Canary (24304) and updated fine. Sideloaded ota in recovery, reboot to let system update complete, reboot to bootloader and flashed patched boot.img. All is fine.
did you try the patched boot.img I uploaded a few posts back? Make sure you're on March update with Magisk 24.3 stable before flashing.
I installed the October update in the settings app on my pixel 6 pro, and updated to android 13 the same way. Are both my slots on Android 13 or do I still need to flash the October OTA via adb?
w_tapper said:
I installed the October update in the settings app on my pixel 6 pro, and updated to android 13 the same way. Are both my slots on Android 13 or do I still need to flash the October OTA via adb?
Click to expand...
Click to collapse
If you mean you updated to A13 (September) via OTA through System Update in settings and then updated to October the same way, then you should have A13 on both slots.
so does that mean that the bricked thing and having to send to google has no chance of happening now?
Lughnasadh said:
If you mean you updated to A13 (September) via OTA through System Update in settings and then updated to October the same way, then you should have A13 on both slots.
Click to expand...
Click to collapse
w_tapper said:
so does that mean that the bricked thing and having to send to google has no chance of happening now?
Click to expand...
Click to collapse
If that is how you updated, then correct. Each time you update via OTA it updates to the opposite slot you are on. Since you updated twice like this, both slots should have A13 on them and you should be fine.