No OTA When ROOT? [Magsik] - Google Pixel 4 XL Questions & Answers

Hi,
I'm on the latest Magisk, rooted, with Feb 2020 update
My Pixel4XL is carrier unlocked.
I can't seem to get the OTA to work, I clicked check for update, it gave me a prompt of preparing for update, then said my system is up to date.
I tried removing Magisk and restoring boot image in MManager
I can't access a computer for the time being so I can't sideload it
Help would be appreciated!

Cyshot said:
Hi,
I'm on the latest Magisk, rooted, with Feb 2020 update
My Pixel4XL is carrier unlocked.
I can't seem to get the OTA to work, I clicked check for update, it gave me a prompt of preparing for update, then said my system is up to date.
I can't access a computer for the time being so I can't sideload it
Help would be appreciated!
Click to expand...
Click to collapse
Try this: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md/

Homeboy76 said:
Try this: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md/
Click to expand...
Click to collapse
I did, that's what I followed in the first place

Hey, I have this issue too, I tried to click check for updates, then it said preparing system update, and went back to your system is up to date. Have you found a fix?

TY53 said:
Hey, I have this issue too, I tried to click check for updates, then it said preparing system update, and went back to your system is up to date. Have you found a fix?
Click to expand...
Click to collapse
I wish :/
Seems like checking for updates before uninstalling Magisk is a no-no.

Mine worked OK.
The February OTA never arrived, so side-loaded that last week.
Today I un-installed Magisk, checked for OTA, it was found, and completed, than re-installed Magisk.
Seems as so checking for OTA with Magisk installed is tripping something somewhere.

Need help.
I tried to search for the March security update after ... it was not there.. now I have this error. What should I do?

sam1374 said:
Need help.
I tried to search for the March security update after ... it was not there.. now I have this error. What should I do?
Click to expand...
Click to collapse
Reflash your patched boot.img

mushtafa said:
Reflash your patched boot.img
Click to expand...
Click to collapse
Thanks I'll try it

I had this problem too. I reflashed the magisk patched and now screen is not responding, can someone help me?

TY53 said:
I had this problem too. I reflashed the magisk patched and now screen is not responding, can someone help me?
Click to expand...
Click to collapse
Try rebooting the phone; however, if it is a soft brick situation then:
- Download the March stock factory image from Google
- Unzip and modify the flash-all.bat file and remove the "-w" from the script
- Plug phone into the computer with authorized USB debugging
- Reboot the phone into bootloader mode
- Run the flash-all file and wait for the updates to complete
- Let the phone reboot and then copy the boot.img (from March) file to your phone
- Run the Magisk Manager and patch your boot.img
- Copy the magisk_patched file to your computer and reboot into bootloader
- Flash the boot image with magisk_patched image, and reboot the phone
If it is still soft bricked, then add the "-w" back into the flash-all script and go through the process of rooting your phone again (above). Note: "-w" will erase the userdata on your phone (in other words, wipe and do a factory reset).

bb709394 said:
Try rebooting the phone; however, if it is a soft brick situation then:
- Download the March stock factory image from Google
- Unzip and modify the flash-all.bat file and remove the "-w" from the script
- Plug phone into the computer with authorized USB debugging
- Reboot the phone into bootloader mode
- Run the flash-all file and wait for the updates to complete
- Let the phone reboot and then copy the boot.img (from March) file to your phone
- Run the Magisk Manager and patch your boot.img
- Copy the magisk_patched file to your computer and reboot into bootloader
- Flash the boot image with magisk_patched image, and reboot the phone
If it is still soft bricked, then add the "-w" back into the flash-all script and go through the process of rooting your phone again (above). Note: "-w" will erase the userdata on your phone (in other words, wipe and do a factory reset).
Click to expand...
Click to collapse
Thank you so much! I was able to retrieve my phone with your help!

Related

[ROM] TMO Z2 Force 27.1.3 FlashAll (October 2018 Version)

UPDATE 11-9-18: I have updated the FlashAll with the October edition of version 27.1.3. Yes, they updated the ROM but kept the same version number lol.
This is a TMO Z2 Force 27.1.3 FlashAll. It does not wipe user data. I created it because the OTA update wouldn't complete, I think because I am rooted. Anyway I took the OTA from https://mirrors.lolinet.com (thank you!), unzipped it, used root junky's script to convert it (thank you!) and made a batch file to flash the partitions. The flashall includes ADB and Fastboot also. The Flashall is for windows. Your bootloader needs to be unlocked. You need to be on an OREO rom already.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south. If you don't know what a flashall is, or twrp, or fastboot, you may not be ready for this.
Downloads
1. Updated October Flashall https://drive.google.com/open?id=1PczvmaVv19c91iOGhpNmhmfKyvDkz-ob (download to your computer)
2. TWRP Installer (if you are rooted, download this to your phone) https://dl.twrp.me/nash/
3. Magisk (if you are rooted, download this to your phone) https://forum.xda-developers.com/apps/magisk
How To:
Unzip the Flashall into a folder called "TMO Moto z2 force 27.1.3 flashall" Open a command prompt in the folder it created. Connect your phone to your computer via ADB.
Not Rooted?
If you are NOT rooted, just run flashall.bat. It will automatically boot into fastboot mode, update the partitions, reboot, and profit. This does not wipe user data.
Rooted
If you are rooted:
1) run flashall_then_recovery.bat. It will automatically boot into fastboot mode, update the partitions, then automatically reboot into a temp twrp recovery.
2) In TWRP install the twrp installer you downloaded above (if you use recovery).
3) Reboot recovery
4) Install magisk that you downloaded above.
5) Reboot
Not Rooted and want to wipe everything?
Run flashall_erase.bat. It will boot into fastboot mode, update the partitions, and wipe everything.
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance.
texasaggie1 said:
This is a TMO Z2 Force 27.1.3 FlashAll. It does not wipe user data. I created it because the OTA update wouldn't complete, I think because I am rooted. Anyway I took the OTA from @xiyl (thank you!), unzipped it and made a batch file to flash the partitions. The flashall includes ADB and Fastboot also. The Flashall is for windows. Your bootloader needs to be unlocked. You need to be on an OREO rom already.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south.
Downloads
1. Flashall https://drive.google.com/open?id=1HK2zssCGlPTD5m2A_SAD-RjrQDfmZMTR (download to your computer)
2. TWRP Installer (if you are rooted, download this to your phone) https://dl.twrp.me/nash/
3. Magisk (if you are rooted, download this to your phone) https://forum.xda-developers.com/apps/magisk
How To:
Unzip the Flashall. It will create a folder called "NASH_TMO_27.1.3" Open a command prompt in the folder it created.
Not Rooted?
If you are NOT rooted, just run flashall.bat. It will automatically boot into fastboot mode, update the partitions, reboot, and profit.
Rooted
If you are rooted:
1) run flashall_then_recovery.bat. It will automatically boot into fastboot mode, update the partitions, then automatically reboot into a temp twrp recovery.
2) In TWRP install the twrp installer you downloaded above
3) Reboot recovery
4) Install magisk that you downloaded above.
5) Reboot
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance,
Click to expand...
Click to collapse
the "flashal link" contains only TWRP3.1.zip with boot.img and META-INF folder. it doesn't contain a flashall_then_recovery.bat nor NASH_TMO_27.1.3.
kendallgreen said:
the "flashal link" contains only TWRP3.1.zip with boot.img and META-INF folder. it doesn't contain a flashall_then_recovery.bat nor NASH_TMO_27.1.3.
Click to expand...
Click to collapse
Sorry! It was late and I linked to the wrong thing. ? Try it now please.
texasaggie1 said:
This is a TMO Z2 Force 27.1.3 FlashAll. It does not wipe user data. I created it because the OTA update wouldn't complete, I think because I am rooted. Anyway I took the OTA from @xiyl (thank you!), unzipped it and made a batch file to flash the partitions. The flashall includes ADB and Fastboot also. The Flashall is for windows. Your bootloader needs to be unlocked. You need to be on an OREO rom already.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south. If you don't know what a flashall is, or twrp, or fastboot, you may not be ready for this.
Downloads
1. Flashall https://drive.google.com/file/d/1JKu5S7xvy8xvyCodLEt7olr8czP_8FUm/view?usp=drivesdk (download to your computer)
2. TWRP Installer (if you are rooted, download this to your phone) https://dl.twrp.me/nash/
3. Magisk (if you are rooted, download this to your phone) https://forum.xda-developers.com/apps/magisk
How To:
Unzip the Flashall. It will create a folder called "NASH_TMO_27.1.3" Open a command prompt in the folder it created.
Not Rooted?
If you are NOT rooted, just run flashall.bat. It will automatically boot into fastboot mode, update the partitions, reboot, and profit.
Rooted
If you are rooted:
1) run flashall_then_recovery.bat. It will automatically boot into fastboot mode, update the partitions, then automatically reboot into a temp twrp recovery.
2) In TWRP install the twrp installer you downloaded above
3) Reboot recovery
4) Install magisk that you downloaded above.
5) Reboot
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance.
Click to expand...
Click to collapse
I downloaded and unzipped the new NASH_TMO_27.1..3. I added the AdbWinApi.dll and AdbWinUsbApi.dll and got the flashall_then_recovery.bat to run. I didn't install the TWRP installer or Magisk but rebooted to recovery and then system. After several restarts due to unlocked bootloader warning, it came back to build number OCXS27.1.2 kernel [email protected]#1 Fri Apr 20 09:21:27 CDT 2018. Android security level May 1, 2018. Android version 8.0.0 However, all of my apps were retained except Messaging .
kendallgreen said:
the "flashal link" contains only TWRP3.1.zip with boot.img and META-INF folder. it doesn't contain a flashall_then_recovery.bat nor NASH_TMO_27.1.3.
Click to expand...
Click to collapse
kendallgreen said:
I downloaded and unzipped the new NASH_TMO_27.1..3. I added the AdbWinApi.dll and AdbWinUsbApi.dll and got the flashall_then_recovery.bat to run. I didn't install the TWRP installer or Magisk but rebooted to recovery and then system. After several restarts due to unlocked bootloader warning, it came back to build number OCXS27.1.2 kernel [email protected]#1 Fri Apr 20 09:21:27 CDT 2018. Android security level May 1, 2018. Android version 8.0.0 However, all of my apps were retained except Messaging .
Click to expand...
Click to collapse
So try it again but this time just do the regular flashall.bat. it should work this time.
It sounds like you are installing this to slot a but your phone is running in slot b. If doing it this way doesn't fix it just look on here for the command to switch your phone from one slot to another.
success. I tried the flashall.bat and got the system updated to 27.1.3. I noticed that when I fastboot --set-active=_a, I had 27.1.2 and with --set-active=_b, I had to restart the phone because it was stuck at the unlocked bootloader warning. thanks.
kendallgreen said:
success. I tried the flashall.bat and got the system updated to 27.1.3. I noticed that when I fastboot --set-active=_a, I had 27.1.2 and with --set-active=_b, I had to restart the phone because it was stuck at the unlocked bootloader warning. thanks.
Click to expand...
Click to collapse
awesome! The whole a/b partition thing can be quite annoying
great job man glad someone did this i was about to try thanks
worked great but i reflashed remove encryption oreo also i didnt know if it was a necessary was being safe you made it easy no fastboot lol great work
My Fellow Texan.....
THANK YOU.
My phone has been in a weird limbo for months. I was on AOSIP ROM but it wasn't rooted, I couldn't use any moto mods and I couldn't install anything because TWRP wasn't installed and it wouldn't let me install it, either. I now have TWRP, but it's showing no baseband. So I'm gonna attempt to fix that but I'm already in a better place than I was. Thanks again, brother.
if you need baseband its easy to fix i had the same issues i was testing kernel its eas fix if you need i can help fix ive bricked and tried everything works easy check last post put on this https://forum.xda-developers.com/z2-force/development/pantheon-kernel-alpha-t3805977
My Tmo box is rooted, presently running the original 27.1 release.. I've been getting the OTA update notifications for 27.1.2.
Do we know if I can skip 27.1.2 and jump straight to the 27.1.3 release? I'd love to be able to do this flash-all and put the update notifications to bed for a while.
dismembered3po said:
My Tmo box is rooted, presently running the original 27.1 release.. I've been getting the OTA update notifications for 27.1.2.
Do we know if I can skip 27.1.2 and jump straight to the 27.1.3 release? I'd love to be able to do this flash-all and put the update notifications to bed for a while.
Click to expand...
Click to collapse
It should be fine to skip revisions.
StonedYoda said:
My Fellow Texan.....
THANK YOU.
My phone has been in a weird limbo for months. I was on AOSIP ROM but it wasn't rooted, I couldn't use any moto mods and I couldn't install anything because TWRP wasn't installed and it wouldn't let me install it, either. I now have TWRP, but it's showing no baseband. So I'm gonna attempt to fix that but I'm already in a better place than I was. Thanks again, brother.
Click to expand...
Click to collapse
If you are on tmobile, flashing the firmware flashall from the aosip thread to get baseband back.
mookiexl said:
If you are on tmobile, flashing the firmware flashall from the aosip thread to get baseband back.
Click to expand...
Click to collapse
If that doesn't work let me know. It should though. You may have to re-root after his suggestion
I'd been avoiding updates because I just didn't want to deal with rooting again and restoring data, etc. This was great!
(bootloader) slot: not found this is what I get with every fastboot command.
I was having the same issue... I was on 27.1.2 and kept getting notified to update, but it kept failing. I'm rooting with Magisk (16.0 initially but then up to 17.1) and it wouldn't update. Thanks to this thread, I ran the flashall_then_recovery.bat and it worked a treat!!! Thank you TexasAggie!
TWRP Installer link is down
The link to the TWRP installer is timing out when loading and comes up with an error message. Is it possible to install the 27.3 update using adb and then flash magisk in the temp twrp? Thanks for your work bro!
UPDATE:
I tried and now I'm stuck in bootloop. I can still get to twrp using adb and did a wipe but it's still stuck in loop land. Do I need to be rebooting in TWRP from slot A or B? This is my first phone that has dual partitions and I am a bit confused by it. Any suggestions? THANK YOU!!
UPDATE:
Tried your flashall update a second time and it worked with no bootloop issue, was able to flash magisk and obtain root again too.
climbhigh77 said:
The link to the TWRP installer is timing out when loading and comes up with an error message. Is it possible to install the 27.3 update using adb and then flash magisk in the temp twrp? Thanks for your work bro!
UPDATE:
I tried and now I'm stuck in bootloop. I can still get to twrp using adb and did a wipe but it's still stuck in loop land. Do I need to be rebooting in TWRP from slot A or B? This is my first phone that has dual partitions and I am a bit confused by it. Any suggestions? THANK YOU!!
UPDATE:
Tried your flashall update a second time and it worked with no bootloop issue, was able to flash magisk and obtain root again too.
Click to expand...
Click to collapse
Glad to hear that!

No touch screen after March factory image update

Anyone else having this issue after fastboot the March factory image, I was rooted with Magisk on the January firmware.
tatico28 said:
Anyone else having this issue after fastboot the March factory image, I was rooted with Magisk on the January firmware.
Click to expand...
Click to collapse
Did you uninstall Magisk or disable the magisk modules before you flashed the March 2020 factory image?
Homeboy76 said:
Did you uninstall Magisk or disable the magisk modules before you flashed the March 2020 factory image?
Click to expand...
Click to collapse
No, I did not, is there a workaround?
tatico28 said:
No, I did not, is there a workaround?
Click to expand...
Click to collapse
No it is not a workaround, strange things happen when you don't at least disable all magisk modules before you flash a Factory update. Why some modules must be updated to work with the March Factory image. Use this Guide: Do #4 'keep data' then do #9 to root.
Homeboy76 said:
No it is not a workaround, strange things happen when you don't at least disable all magisk modules before you flash a Factory update. Why some modules must be updated to work with the March Factory image. Use this Guide: Do #4 'keep data' then do #9 to root.
Click to expand...
Click to collapse
Thanks for your response, updating the Tools module made the difference, since I`ve tried to fastboot flash the factory image twice with the old tools version, I did not know that the March update came with this bag of treats lol.
tatico28 said:
Thanks for your response, updating the Tools module made the difference, since I`ve tried to fastboot flash the factory image twice with the old tools version, I did not know that the March update came with this bag of treats lol.
Click to expand...
Click to collapse
Hi, what do you mean updating the tools module? tnks
davidvd102dvd said:
Hi, what do you mean updating the tools module? tnks
Click to expand...
Click to collapse
I think he's referring to SDK platform-tools.
Homeboy76 said:
I think he's referring to SDK platform-tools.
Click to expand...
Click to collapse
i though the same but tried without success
davidvd102dvd said:
i though the same but tried without success
Click to expand...
Click to collapse
Ok, then this must be what he is talking about: https://pixelrepair.withgoogle.com/carrier_selection
Yes the SDK Platform- tools, also I had to fastboot flash the boot.img to both a,b slots.
Homeboy76 said:
No it is not a workaround, strange things happen when you don't at least disable all magisk modules before you flash a Factory update. Why some modules must be updated to work with the March Factory image. Use this Guide: Do #4 'keep data' then do #9 to root.
Click to expand...
Click to collapse
bro just disable the modules is enough or do we have to flash the stock boot too? @tatico28
alwynjoshy said:
bro just disable the modules is enough or do we have to flash the stock boot too? @tatico28
Click to expand...
Click to collapse
If you are going to do #4 and you are rooted, do this first:
- Open Magisk Manager
- Tap modules uncheck all the modules that have a checkmark (tap the ✓).
- Reboot to deactivate the modules
- Open Magisk Manager
- Tap Uninstall
- Tap Restore images (unroots your phone by restoring/flashing stock boot images).
- Do #4 'keep data'
Homeboy76 said:
If you are going to do #4 and you are rooted, do this first:
- Open Magisk Manager
- Tap modules uncheck all the modules that have a checkmark (tap the ✓).
- Reboot to deactivate the modules
- Open Magisk Manager
- Tap Uninstall
- Tap Restore images (unroots your phone by restoring/flashing stock boot images).
- Do #4 'keep data'
Click to expand...
Click to collapse
Restore images failed says no image found. So i disabled all modules and rebooted then flashed stock image booted up. The i went bootloader and flashed march OTA. Booted up But still touch is not responsive
alwynjoshy said:
Restore images failed says no image found. So i disabled all modules and rebooted then flashed stock image booted up. The i went bootloader and flashed march OTA. Booted up But still touch is not responsive
Click to expand...
Click to collapse
A factory reset may be your only option then. Have you tried switching your slots and then fastboot the factory image without the -w so as not to loose data?
Badger50 said:
A factory reset may be your only option then. Have you tried switching your slots and then fastboot the factory image without the -w so as not to loose data?
Click to expand...
Click to collapse
I only use a slot only, didn't try swift slots but i try to go recovery mode to sideload the zip. A error state "NO COMMAND FOUND" AND SHOWS A DEAD ANDROID WITH STOMACH OPENED
alwynjoshy said:
I only use a slot only, didn't try swift slots but i try to go recovery mode to sideload the zip. A error state "NO COMMAND FOUND" AND SHOWS A DEAD ANDROID WITH STOMACH OPENED
Click to expand...
Click to collapse
Update the SDK Platform Tools, flash March factory img. without -w if you don`t want to erase your data, extract boot.img from image.zip, fastboot flash boot.img to both slots and you should be ok.
tatico28 said:
Update the SDK Platform Tools, flash March factory img. without -w if you don`t want to erase your data, extract boot.img from image.zip, fastboot flash boot.img to both slots and you should be ok.
Click to expand...
Click to collapse
I tried the way you said but same result. The only thing i didn't do is i flashed only slot A only. But my active slot is A so i think that is not the issue
alwynjoshy said:
I only use a slot only, didn't try swift slots but i try to go recovery mode to sideload the zip. A error state "NO COMMAND FOUND" AND SHOWS A DEAD ANDROID WITH STOMACH OPENED
Click to expand...
Click to collapse
Thats just the stock recovery screen. Hold the power button down, and then tap the volume up button once. Then you'll be stock recovery :good:
Badger50 said:
Thats just the stock recovery screen. Hold the power button down, and then tap the volume up button once. Then you'll be stock recovery :good:
Click to expand...
Click to collapse
Is both sideload and run flash-all.bat give the same functionality to flash or it will be different way to flash the OTA
alwynjoshy said:
Is both sideload and run flash-all.bat give the same functionality to flash or it will be different way to flash the OTA
Click to expand...
Click to collapse
It's a matter of choice really. Many, like myself, like to fastboot the factory images every month to update. Others like the OTA. Functionality is pretty much the same as far as I've seen. However, you can't fastboot an OTA, likewise you can't side load a factory image, and of course, you have to be bootloader unlocked to fastboot the factory images, so keep that in mind as well. I also like using fastboot because you can switch slots to sometimes get rid of errors that occasionally pop up. Good luck with finding your solution whichever way you choose to go. :good:

HELP! My device is corrupt

I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?
features99 said:
I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?
Click to expand...
Click to collapse
Need more specific details, like specific method of rooting, version of Magisk, updating to what?, etc...
Unfortunately you may have to flash the factory image and start all over again if no one else can help you with it. At least you have the option. Sucks when that happens.
I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat
jljtgr said:
I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat
Click to expand...
Click to collapse
I agree. Flashing the factory image without the -w would likely allow him to boot up again. But it would be helpful for that person to tell us exactly what they did so we can help them avoid it in the future, e.g. maybe they flashed the stable version of Magisk instead of Beta or Canary, or maybe they tried a direct install instead of patching the boot image, etc...
Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
Also I didnt modify my own boot image, but one I downloaded from a matching build.
I really appreciate the help
features99 said:
Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
I really appreciate the help
Click to expand...
Click to collapse
I would try fastboot flashing the stock boot image first.
If Magisk says you're on a version before 21.0, the patched image won't work for Android 11. Stable is currently 20.4 released in March.
Lughnasadh said:
I would try fastboot flashing the stock boot image first.
Click to expand...
Click to collapse
tried that..it didnt work
features99 said:
tried that..it didnt work
Click to expand...
Click to collapse
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.
Lughnasadh said:
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.
Click to expand...
Click to collapse
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!
features99 said:
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!
Click to expand...
Click to collapse
No problem. Glad you got it going. As I see you've already found out, Magisk Beta 21.1 is a good way to go. Canary as well but then you may run into problems in the future when Canary gets updated since those are "cutting edge" builds.

Help w/ updating and Magisk

I'm asking for help because this has happened for two months now, and I'm wondering if the process has changed with the new unified Magisk.
The March Android 11 update has been posted, so -- just as I did in February::
1. On my computer, I
1a. Downloaded the factory image;
1b. Extracted the boot.img; and
1c. Sent it to my phone's Download folder.
2. On my phone, I
2a. Had Magisk "patch (the) selected file";
2b. Transferred the new patched boot image, magisk_patched_FKPSk.img, back to the computer; and
2c. Put the phone into fastboot mode.
3. Back on my computer, in adb, performed the "fastboot flash boot magisk_patched_FKPSk.img."
adb successfully flashed to boot_a, then I rebooted the phone. It rebooted surprisingly quickly.
Going into "System / Advanced / System Update," it still says
Android security update: January 5, 2021
So, what am I doing wrong? Should I force adb to flash to boot_b instead?
Thanks for any ideas!
NickEspo said:
I'm asking for help because this has happened for two months now, and I'm wondering if the process has changed with the new unified Magisk.
The March Android 11 update has been posted, so -- just as I did in February::
1. On my computer, I
1a. Downloaded the factory image;
1b. Extracted the boot.img; and
1c. Sent it to my phone's Download folder.
2. On my phone, I
2a. Had Magisk "patch (the) selected file";
2b. Transferred the new patched boot image, magisk_patched_FKPSk.img, back to the computer; and
2c. Put the phone into fastboot mode.
3. Back on my computer, in adb, performed the "fastboot flash boot magisk_patched_FKPSk.img."
adb successfully flashed to boot_a, then I rebooted the phone. It rebooted surprisingly quickly.
Going into "System / Advanced / System Update," it still says
Android security update: January 5, 2021
So, what am I doing wrong? Should I force adb to flash to boot_b instead?
Thanks for any ideas!
Click to expand...
Click to collapse
That doesn't have anything to do with Magisk. That's the firmware update you are on. If you want on a newer one you will to flash it. Then follow your previous steps. Magisk doesn't update your firmware for you.
Tulsadiver said:
That doesn't have anything to do with Magisk. That's the firmware update you are on. If you want on a newer one you will to flash it. Then follow your previous steps. Magisk doesn't update your firmware for you.
Click to expand...
Click to collapse
Ah. So then, if I understand correctly, the process is to unroot, sideload the OTA image (not just flash the factory image's boot.img file) via adb, and then perform the above steps to re-root?
NickEspo said:
Ah. So then, if I understand correctly, the process is to unroot, sideload the OTA image (not just flash the factory image's boot.img file) via adb, and then perform the above steps to re-root?
Click to expand...
Click to collapse
Yes, though I normally fastboot the factory images rather than sideload an ota. That update process will lose root, then you patch the boot.img and fastboot it to regain root. I would recommend removing all modules prior to updating as they will survive the update process (unless you wipe) and if not compatible with your update, will bootloop you once you root again.

Rooted 4a 5G still on January version, how do I update?

I have a rooted 4a 5G that's still on the January 5, 2021 version. Whenever I go to the phone's settings to check for updates, it keeps saying that the device is up to date. I went to https://developers.google.com/android/images#bramble but I am unsure how to update my device. Am I supposed to use Factory Image, or Full OTA Image?
WhiteAsIce said:
I have a rooted 4a 5G that's still on the January 5, 2021 version. Whenever I go to the phone's settings to check for updates, it keeps saying that the device is up to date. I went to https://developers.google.com/android/images#bramble but I am unsure how to update my device. Am I supposed to use Factory Image, or Full OTA Image?
Click to expand...
Click to collapse
I always use factory images. Just remember to remove the -w from the flash all .bat or .sh
Edit: See below.
Tulsadiver said:
I always use factory images. Just remember to remove the -w from the flash all .bat or .sh
Click to expand...
Click to collapse
So I removed the -w lines from the flash-all files, flashed the June OTA, then flashed the Magisk patched boot img. My phone cannot boot past the fastboot screen, meaning I don't have a phone until I fix this. Any help?
WhiteAsIce said:
So I removed the -w lines from the flash-all files, flashed the June OTA, then flashed the Magisk patched boot img. My phone cannot boot past the fastboot screen, meaning I don't have a phone until I fix this. Any help?
Click to expand...
Click to collapse
Did you leave any modules on your phone?
Tulsadiver said:
Did you leave any modules on your phone?
Click to expand...
Click to collapse
What are modules?
Anyway, it's too late, I ran the flash-all file with the -w lines to try to recover my phone, but it ended up WIPING my entire phone. Everything is gone, downloads and pictures and all.
WhiteAsIce said:
What are modules?
Anyway, it's too late, I ran the flash-all file with the -w lines to try to recover my phone, but it ended up WIPING my entire phone. Everything is gone, downloads and pictures and all.
Click to expand...
Click to collapse
You are rooted with magisk but don't know what magisk modules are?
Tulsadiver said:
You are rooted with magisk but don't know what magisk modules are?
Click to expand...
Click to collapse
The only one I had was a mod to allow safetynet to pass.
My phone is rooted with magisk, so I need to do the monthly updates manually. In order to do this, I download both the OTA and the factory image. I update the phone using the OTA. I extract the boot.img file from the factory image, put it on the pixel after updating and patch it with magisk. Then I copy it to my computer and flash it to the active boot slot as described below.
Too late to help now, but the issue was probably that the pixel has two boot slots, boot_a and boot_b, and it was booting from the wrong one. The -w you used finally is the wipe option and it's done by default unless you remove it, so that's why the phone was wiped.
In my case, I used the following commands to make sure that I flashed to the correct slot and/or booted from the correct slot that had the magisk patched kernel:
fastboot getvar current-slot
fastboot flash boot_a magisk_patched.img
If it's ever necessary, you can manually change the active boot slot: fastboot --set-active=a
If you flash the correct magisk-patched kernel to either slot and set the phone to boot from that slot, your phone will boot up. I learned about this the hard way and now, every month, I just make sure that I flash to the currently active slot and have not had a problem since. One of the nicest things about having a pixel is that they are just about impossible to brick - it's just a matter of redoing things properly.

Categories

Resources