Related
Hi
I really need help to go stock on my device.
I unlocked my bootloader, flashed TWRP and Magisk on stock rom and installed the ViperU Magisk Module.
I also made a NANDROID of the stock ROM before, unfortunately there is no Recovery in it, since i had TWRP already installed.
Then an OTA (oktober 17 security patch) was available for my device and i startet the install process, but it didn't install.
TWRP open recovery would run not even 1 second then exit.
In order to get the OTA I restored stock recovery (which i had to extract from OTA, since i forgot to back it up) and started OTA.
--> Red Triangle!
Even after restoring stock NANDroid the OTA wouldn't install.
My mistake i think was that i didn't kept the stock system read only when i did the backup in twrp and swiped to allow modifications.
According to some threads here, even mounting the system r/w would break OTA functionality.
So since i also have no RUU for my device, i don't have the chance either to go back to stock. Maybe you did that mistake too.
The only way i can think of now, is to go temporary S-OFF, change CID and MID (to 401 international for example), flash Firmware and run the RUU for it.
But i'm not sure it'll still work after flashing the firmware.
Can anyone maybe confirm this way would work?
And is there an other way available?
Thanks!
Quick Specs:
-Unlocked Bootloader
-S-ON
-Firmware: 1.27.166.7
-CID: VODAP110
-MID: 2PZC10000
Nightmare
Quick Specs:
-Unlocked Bootloader
-S-ON
-Firmware: 1.27.166.7
-CID: VODAP110
-MID: 2PZC10000[/QUOTE said:
Hello, Have you looked at this list to see if you could take one from here?
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
michaelbsheldon said:
Hello, Have you looked at this list to see if you could take one from here?
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
Hi
Yes, unfortunately there's nothing available for my device.
Does the phone boot into os?
You cannot take an OTA with TWRP. You need an untouched system image to take the OTA. Easiest way is to RUU to your current firmware. Let the system update.
schmeggy929 said:
You cannot take an OTA with TWRP. You need an untouched system image to take the OTA. Easiest way is to RUU to your current firmware. Let the system update.
Click to expand...
Click to collapse
Actually that's not true, TWRP appareantly has a open recovery which works with OTA.
Also the RUU doesn't have to match your Firmware.
What i did was following:
-Had TWRP and a running ROM, rootet with magisk
-Downloded a RUU for my MID (picked the 401 one for international unlocked, i think you can take any)
-Installed sunshine and went temp s-off
-Went into download mode and changed cid to a matching one (HTC__034 -> Europe for me, there are other compatibles)
-Renamed the RUU (2PZCIMG.zip) and put it in the root of my SD-Card
-Inserted the SD-Card and rebootet to download (there's an option in download mode for that)
-pressed volume up to start installation
-Done, phone reboots with stock system, stock recovery and right firmware
Also I installed TWRP right back and magisk and tried to take the OTA. It installed without problems through TWRP.
Afaik, it will work, but replace TWRP in the end, so you will have to reflash twrp after every OTA, or you just take the recovery out of the
OTA and flash it through SD-Card (you have to rename it).
So that's the way to go if you have to go stock and there's nothing in the collection for your version.
Hope this helps.
Edit: Please remember to keep TWRP in read only! you will still be able to flash zips like magisk for example.
Hey,
after you had flashed the 004 Ruu, did you change S-off back to S-On?
2eli0 said:
Hey,
after you had flashed the 004 Ruu, did you change S-off back to S-On?
Click to expand...
Click to collapse
since s-off is still temporary it will go back to s-on as soon as you boot into recovery or rom.
also, i flashed the 1.27.401.5 ruu, since i wanted to see if the update to 1.27.401.12 ota works with twrp and magisk installed.
it does, just remember to keep recovery read only!
What do you mean by "read only"? Is there a setting where I can do that?
2eli0 said:
What do you mean by "read only"? Is there a setting where I can do that?
Click to expand...
Click to collapse
If you take a bone stock phone (when you buy it for example, or after running a ruu), the first time you flash twrp and
boot into it, it will ask you if you want to keep the system in read only, in order not to break the OTA functionality.
But you won't be able to restore backups or install zip which changes system partition (Custom ROMs, xposed, etc.).
If you want to keep OTA functionality, you can keep it read only and still be able to flash zips like magisk and so on.
Once you swipe to allow modifications doe, there is no way back, so keep that in mind!
Mounting the system partition once in rw (read/write) will break OTA permanently.
If you ever decide that you want to modify the system partition anyway (going custom ROM) you can change the setting:
TWRP-->Mount-->"Mount system partition read only"-->uncheck it
Correct me if i'm wrong.
Nightmare[ITA said:
;75529278]If you take a bone stock phone (when you buy it for example, or after running a ruu), the first time you flash twrp and
boot into it, it will ask you if you want to keep the system in read only, in order not to break the OTA functionality.
But you won't be able to restore backups or install zip which changes system partition (Custom ROMs, xposed, etc.).
If you want to keep OTA functionality, you can keep it read only and still be able to flash zips like magisk and so on.
Once you swipe to allow modifications doe, there is no way back, so keep that in mind!
Mounting the system partition once in rw (read/write) will break OTA permanently.
If you ever decide that you want to modify the system partition anyway (going custom ROM) you can change the setting:
TWRP-->Mount-->"Mount system partition read only"-->uncheck it
Correct me if i'm wrong.
Click to expand...
Click to collapse
Ah ok, got it.
I would want to keep the OTA functionality, since I want to keep it stock with root privileges. That's all.
I won't try custom roms anytime soon. Thanks for the tip.
If I had known that before I flashed twrp I would have been able to update OTA now, right?
2eli0 said:
Ah ok, got it.
I would want to keep the OTA functionality, since I want to keep it stock with root privileges. That's all.
I won't try custom roms anytime soon. Thanks for the tip.
If I had known that before I flashed twrp I would have been able to update OTA now, right?
Click to expand...
Click to collapse
Pretty much, ya. I missed that part the first time too
Nightmare[ITA said:
;75529808]Pretty much, ya. I missed that part the first time too
Click to expand...
Click to collapse
Ahh, dang it. Well, I'd say we learn by mistakes.
Thanks for the hint.
I will try the version you tried. It's still downloading.
Btw. did the download take like ages for you?
During the day I get like 100-200 KB/s and sometimes even less. In the evening like 11 pm it's 3 MB/s...
My connection is fine.
2eli0 said:
Ahh, dang it. Well, I'd say we learn by mistakes.
Thanks for the hint.
I will try the version you tried. It's still downloading.
Btw. did the download take like ages for you?
During the day I get like 100-200 KB/s and sometimes even less. In the evening like 11 pm it's 3 MB/s...
My connection is fine.
Click to expand...
Click to collapse
Yes, over the last few months AFH has been extremely slow.
Ok I will state it in another way. The easiest way to take the OTA is on an Untouched System and Recovery Image lol. You can with TWRP however the firmware will not flash. Hence probably your problem. You do know there is an RUU for 2.33.166.6 for your carrier. https://www.htcdev.com/devcenter/downloads
I have already seen that, but its like 400 mb big, if I remember correctly, hence not the entire files, right?
schmeggy929 said:
Ok I will state it in another way. The easiest way to take the OTA is on an Untouched System and Recovery Image lol. You can with TWRP however the firmware will not flash. Hence probably your problem. You do know there is an RUU for 2.33.166.6 for your carrier. https://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
lol. That's the site i was searching for.
But since it's the source code, you would have to compile it first, right?
Anyway, are you sure? Cause from what i can see the firmware got updated too.
In fact, in this post under point 4. it states, that it's working.
The htcdev stuff is source only. No good. Also, once you flash twrp you can't take ota. You must be stock to take ota (s-off and bootloader remain untouched and do not matter for flashing, there is no need to s-on nor relock the bootloader ever).
To achieve stock just flash the same firmware you currently use as a zip from the external sdcard. The only things lost is root and twrp.
Nightmare[ITA] said:
lol. That's the site i was searching for.
But since it's the source code, you would have to compile it first, right?
Anyway, are you sure? Cause from what i can see the firmware got updated too.
In fact, in this post under point 4. it states, that it's working.
Click to expand...
Click to collapse
Yeah i guess you are right it is the source code. Even with TWRP stills seems like a lot of work to update. Ya'll need some custom ROMs installed. Flash signed firmware.zip, reflash TWRP and flash updated ROM. All done. If by chance you ever needed to return to stock, flash your system image backup. Ya'll make things so complicated when they really aren't. lol
Nightmare[ITA said:
]Actually that's not true, TWRP appareantly has a open recovery which works with OTA.
Also the RUU doesn't have to match your Firmware.
What i did was following:
-Had TWRP and a running ROM, rootet with magisk
-Downloded a RUU for my MID (picked the 401 one for international unlocked, i think you can take any)
-Installed sunshine and went temp s-off
-Went into download mode and changed cid to a matching one (HTC__034 -> Europe for me, there are other compatibles)
-Renamed the RUU (2PZCIMG.zip) and put it in the root of my SD-Card
-Inserted the SD-Card and rebootet to download (there's an option in download mode for that)
-pressed volume up to start installation
-Done, phone reboots with stock system, stock recovery and right firmware
Also I installed TWRP right back and magisk and tried to take the OTA. It installed without problems through TWRP.
Afaik, it will work, but replace TWRP in the end, so you will have to reflash twrp after every OTA, or you just take the recovery out of the
OTA and flash it through SD-Card (you have to rename it).
So that's the way to go if you have to go stock and there's nothing in the collection for your version.
Hope this helps.
Edit: Please remember to keep TWRP in read only! you will still be able to flash zips like magisk for example.
Click to expand...
Click to collapse
Well, I managed to do it exactly the way you did.
Everything worked just fine. I changed the CID to HTC__034 and flashed the ruu file updated to Oreo and flashed TWRP kept it at read only and rooted the phone.
Thanks for that :good:
I rooted following Maxwell's tutorial (OnePlus 7 Pro - How to Unlock the Bootloader, Install TWRP, and Root with Magisk
).
Now that all is said and done, and my phone is rooted, I noticed that:
1) The wifi does not work. It will not let me enable wifi. Just keeps switching back to off.
2) The speakers don't work.
I need to know how to fix it. What do I do?
I am new to android so I am not sure the steps needed to fix this botched install/operating system/root whatever
U prob flashed the wrong boot.img, make sure to flash the correct model and OS version.
What model and OS version do you have?
download
Bradl79 said:
U prob flashed the wrong boot.img, make sure to flash the correct model and OS version.
What model and OS version do you have?
Click to expand...
Click to collapse
This is probably an error on my end then. I chose "Global 1917 1911" but my about phone page says "1913", however, my phone also says 9.5.1 and there is no 9.5.1 (under 1913) in the link you provided. Do I need to upgrade my OS first before retrying?
jfny100 said:
This is probably an error on my end then. I chose "Global 1917 1911" but my about phone page says "1913", however, my phone also says 9.5.1 and there is no 9.5.1 (under 1913) in the link you provided. Do I need to upgrade my OS first before retrying?
Click to expand...
Click to collapse
yes you will need to upgrade, there was no 9.5.1 full zip released for us to have patched the boot.img. So update and then patch the correct OS and Model version you update to. Let us know if you have any other issues.
I swear nobody reads the threads before starting. Your wifi is disabled because your rooted boot image does not match the version you should have.
Just flash one of the kernels in the roms section, I'm using ElementalX 1.10, wifi will come back up.
Bradl79 said:
yes you will need to upgrade, there was no 9.5.1 full zip released for us to have patched the boot.img. So update and then patch the correct OS and Model version you update to. Let us know if you have any other issues.
Click to expand...
Click to collapse
Okay. That was it (flashing the wrong boot.img) It's working now - I upgraded to latest OS. Downloaded correct boot.img. Redid the root process with correct files this time, and it worked. Wifi is good. Speakers are good. Everything is good. Thanks for the help. Also, I removed any criticism of the tutorial creators in my post since it turns out I was the idiot. I'm brand new to android though so go easy on me.
djsubterrain said:
I swear nobody reads the threads before starting. Your wifi is disabled because your rooted boot image does not match the version you should have.
Just flash one of the kernels in the roms section, I'm using ElementalX 1.10, wifi will come back up.
Click to expand...
Click to collapse
I didn't read the post until after I encountered errors. I was going off of the video. One problem I had was that the video assumed I had a basic knowledge of some steps, so they didn't mention them. I did not have this knowledge since I am brand new to android. Anyways. I was able to fix these errors via the steps discussed in earlier comments. Everything is working now. I removed any criticism of the tutorial creators from this post since it turns out I'm the idiot.
Glad you got it working
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
JedixJarf said:
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
Click to expand...
Click to collapse
BC that is just an extra step not really needed, I haven't even flashed twrp on my device yet, if I need it I will just boot to it, it's so much easier doing this.
I always thought the same thing u did, until I just flashed the patched boot and updating is so much easier too.
JedixJarf said:
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
Click to expand...
Click to collapse
Because I'm just following along with the tutorial xda put on YouTube and that's what they say to do
I've always wanted to post one of these
https://developers.google.com/android/images
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
I was looking thru that post and didnt wanna risk wiping the device. I just had to wipe a few days ago due to Edxposed bootloop issue lol
Ha, yeah, I feel your pain there, wiping is way too much of a pain to do that frequently
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
You can also flash the OTA file in stock recovery and not lose data.
spotmark said:
You can also flash the OTA file in stock recovery and not lose data.
Click to expand...
Click to collapse
Will it retain root or do you mean - https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Androider4Life said:
Retain root or have to re-root
Click to expand...
Click to collapse
Have to re-root using the Magisk method. Put stock boot on phone, patch boot with Magisk, put modded boot back on computer, and flash in fastboot. AFAIK, there is no way to retain root. Every time you flash the latest monthly patch, it flashes a new stock boot. Therefore, no root.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
There's a way with taking the ota through settings I found out how from a user on here which is:
Once received the ota , go to magisk first uninstall/restore images then download/install ota then DONT REBOOT, go back to magisk install magisk to inactive slot from the app then reboot and all should work with new ota update and have root still.
What is this update 4.3mb
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
gettinwicked said:
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
Click to expand...
Click to collapse
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
gm007 said:
What is this update 4.3mb
Click to expand...
Click to collapse
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Jiggs82 said:
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Click to expand...
Click to collapse
You missed the part where I did try flashing the image. I've done this a hundred times, so, I did it right.
Anyway, I got it. I didn't realize my work computer had a USB-C port, so, I grabbed one and tried flashing the image with that. Worked! Thank God... I guess sdk tools doesn't like a USB 1 to C cable, and my phone doesn't like going into recovery...
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Homeboy76 said:
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Click to expand...
Click to collapse
I am starting to feel more and more like a lot of the bootloop issues are being caused by OTAs swapping slots on install. Besides the --slot all patched boot, it might help to run the OTA twice to get it to install to both slots completely. Preferably though, quit using OTAs and work with -w removed flash-all installer (and even then possibly installing to both slots with an active slot swap in between and before rooting). The double install is common when installing custom ROMs, and the process for OTA sideloads is pretty similar.
Performance improvement, feels smooth and responsive. Glad i dont need to root this phone, ppl are having so many problems.
boe323 said:
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Click to expand...
Click to collapse
My download was 1.3 gb and took forever to install. That's more than just the security patch.. Build number is different too.
Sent from my Pixel 3 XL using Tapatalk
Worked exactly the same as the 10 and .C3 builds for me. Flash-all (minus -w) and patched boot in Magisk. No issues. It was not just security this month. See the functional patches in the bulletin.
https://source.android.com/security/bulletin/pixel/2019-10-01
is there new platform tools too?
So I messed up while flashing 10.0.1 just now.
I mean, it worked, technically. But I'm on the AA rom, and flashed a patched boot image from 10.0 to get magisk and TWRP.
But now I can't turn on WiFi and I have no audio.
Volume is maxed out, slider switch is in the ring position, but I have no audio at all.
I'm guessing it's due to the incorrect boot image being used, but I couldn't find a patched 10.0.1 image to use.
I know, I goofed.
Any way to fix things without having to wipe and start over?
Reflash 10.0.1 with the system Updater in settings using local upgrade option. Use Oxygen Updater to re-download if you removed the file. Then through fastboot, boot up twrp (fastboot boot twrp.img) and flash magisk. Unofficial TWRP for Android Q is available in the development forum.
Thank you!
Did exactly what you said and now I have WiFi and sounds again!
E30Nova said:
Thank you!
Did exactly what you said and now I have WiFi and sounds again!
Click to expand...
Click to collapse
No problem. This was due to boot.img mismatch with system. I'd recommend staying away from downloading and flashing patched images.
There's a thread here that explains how to update without losing root, always follow those steps.
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414
To summarise:
- Download the zip through Oxygen Updater.
- Settings > System > System Update > Cog icon > Local upgrade.
- Select zip. Don't reboot after flashing.
- Open magisk & click install.
- Select after OTA option and then reboot.
If you want to keep TWRP, I would suggest re-downloading the installer and flashing it from magisk instead of using the retention script. After reinstalling magisk (after OTA) and rebooting, you should flash the twrp installer through magisk and then reinstall magisk with the direct install option.
Yeah, I knew it was going to screw stuff up, but I did it anyway.
It's not the first time I knew I shouldn't do something but did it anyway, lol.
At least it was a simple fix, and I didn't lose any data. Maybe my stupidity will hopefully be a lesson to others. If it seems like a bad idea or common sense says not to do it, don't do it, lol.
Thanks again.
E30Nova said:
So I messed up while flashing 10.0.1 just now.
I mean, it worked, technically. But I'm on the AA rom, and flashed a patched boot image from 10.0 to get magisk and TWRP.
But now I can't turn on WiFi and I have no audio.
Volume is maxed out, slider switch is in the ring position, but I have no audio at all.
I'm guessing it's due to the incorrect boot image being used, but I couldn't find a patched 10.0.1 image to use.
I know, I goofed.
Any way to fix things without having to wipe and start over?
Click to expand...
Click to collapse
I just tried to post the rooted boot img for 10.1 for your but it says the file is too large, if you send me your email address i can send it to you.
---------- Post added at 09:45 AM ---------- Previous post was at 09:42 AM ----------
disbeyad999989 said:
I just tried to post the rooted boot img for 10.1 for your but it says the file is too large, if you send me your email address i can send it to you.
Click to expand...
Click to collapse
Just remember that you should only flash this if you are trying to root without twrp otherwise follow the instructions in the thread the other guy a few posts up showed you.
disbeyad999989 said:
Just remember that you should only flash this if you are trying to root without twrp otherwise follow the instructions in the thread the other guy a few posts up showed you.
Click to expand...
Click to collapse
You can always simply boot twrp.img without flashing. (Just make sure you use the right image matching the currently installed android version) I would consider it much safer to flash magisk with twrp and let it patch the boot image rather than downloading a boot image that someone else patched since it might not match with your system.
EDIT: This user has solved his problem though. Only commenting for posterity.
kgs1992 said:
You can always simply boot twrp.img without flashing. I would consider it much safer to flash magisk with twrp and let it patch the boot image rather than downloading a boot image that someone else patched since it might not match with your system.
Click to expand...
Click to collapse
That's very true i didn't think about that also, go that route better
*Note* Some people have had success with this, while some others have not. You do this at your own risk.
Prerequisites:
Magisk Manager might need to be unhidden based on reports from some users.
Magisk needs to have a backup of stock boot.img.
Preserve AVB 2.0/dm-verity must be enabled. (Have gotten mixed reports on this it might or might not be needed)
Check the following post if you don't meet the prerequisites
https://forum.xda-developers.com/showpost.php?p=81186247&postcount=73
Update Process
When phone detects update
1. Disable any desired Magisk modules, ex. Edxposed (I usually disable all modules just to be safe)
2. Reboot
3. In Magisk, select Uninstall, press Restore Images
4. Do NOT Reboot
5. Install OTA Update via Settings -> System -> System Updates
6. When prompted to reboot, Do NOT Reboot
7. In Magisk Manager press Install
8. Select Install to Inactive Slot
9. Reboot
10. Enable the Magisk modules one by one
In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.
One requires ADB
While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.
adb wait-for-device shell magisk --remove-modules
adb reboot
This will remove all modules and you should be able to boot.
The second way is via fastboot. More information in this thread.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
Some information that might help some people.
eg1122 said:
I know some users flash patched boot.img that someone else patched, thus bypassing the creation of a backup. I think choosing or not choosing to preserve avb 2.0/dm-verity also affects if phone will take OTA. I always preserve mine and always patch my own boot.img so I haven't ran into any issues. I'll just have to wait and see what happens on my end once I get the update. This reminds me of some issues some people where getting early on when rooting. Some people had to flash the patched boot.img to both a/b slots and some people didn't. Having both slots with a patched boot will also break the restoring of stock boot.img as Magisk only restores the active slot.
Click to expand...
Click to collapse
If you do it this way you'll be using the patched boot image from the previous update and not the current one.
airmaxx23 said:
If you do it this way you'll be using the patched boot image from the previous update and not the current one.
Click to expand...
Click to collapse
No it doesn't. When you select install to inactive slot it patches the newly installed boot.img that has been installed to the inactive slot. Only reason phone promts you to reboot after an update is to switch slots.
For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.
pdfruth said:
For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.
Click to expand...
Click to collapse
Yeah, there needs to be a backed up stock boot img for this to work. Being able to restore images the way stated in the issue would solve this as you could just restore a stock boot.img then continue doing the steps.
So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!
DemonicMurderer said:
So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!
Click to expand...
Click to collapse
Yes, it has worked for me all the time. These are the exact steps recommended by topjohnwu, I just made them more readibly available to users. Here is a link to his tutorial.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
This work for the Verizon Pixel 4 XL???
SAMCR02018 said:
This work for the Verizon Pixel 4 XL???
Click to expand...
Click to collapse
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.
Badger50 said:
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.
Click to expand...
Click to collapse
Ok the can the Verizon version get the BL unlocked?
SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
Nope. Unless you got lucky and they sold you a google version by mistake.
SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
There is a write up for that.
Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?
Donric13 said:
Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?
Click to expand...
Click to collapse
Yes this method works with custom kernel. Magisk removed custom kernel when it restores stock boot.img
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
I wouldn't do it until the Dec ota comes out and that may be later today or sometime this week. Which is weird since all the other Pixels got it but hey it's Google
in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
Since it's not out yet, just do a direct install in Magisk to re-install it
Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.
mkpansare said:
Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.
Click to expand...
Click to collapse
The other way I update is using full factory images. Once you download the zip, extract it and find and open (via Notepad++ or similar advanced text editor) the flash-all.bat or flash-all.sh (depends on your system), find this line
fastboot -w update
replace with
fastboot update
Basically remove the -w, this will prevent a factory reset (wipe) on your device. Once it is done you will need to patch new boot.img via magisk and flash the newly patched boot.img via fastboot.
Hope this helps!
ps. I recommend to always disable Magisk Modules before updating as they could cause FC
eg1122 said:
Since it's not out yet, just do a direct install in Magisk to re-install it
Click to expand...
Click to collapse
Thanks that worked perfect... Was gonna be a long week without adblocker and lmt pie lol