Database Develop

Upgrade Nexus 7 wifi (nakasi) to Android 4.2.2 manually

Hi guys,
Android version 4.2.2 via OTA has been released. For folks like me who have not yet got it and are impatient here you go-
1.Upgrade Nexus 7 to 4.2.1 first [necessary].
2.Get the zip for 4.2.2 here.
Download
3.Boot Nexus 7 into bootloader.
[Power button + center of both volume buttons/volume down]
4.Select Recovery using volume up/down buttons.
5.Press Power button.
6.Wait till you get an android with a red exclamation.
7.Press power + volume up or any other combination till you get a menu.
8.Select update from ADB.
9.Open the folder where the downloaded zip is in the computer.
10.Right click with shift pressed and select open command window here.
11.Type without quotes "adb sideload 6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip"
12.The nexus will flash it.
13.When it is complete wipe cache and dalvik.
14.Reboot and enjoy.
15.Hit thanks.
If you really cant get it to work download 4.2.1 Stock Rom and extract system.img from the zip inside the .gz.
If it still gives an error flash the complete 4.2.1 stock rom.

what a long filename to type

bradputt said:
what a long filename to type
Click to expand...
Click to collapse
Sorry it was named by google.
U can rename it if you want

Is there a rooted version?

tenyrnote said:
Is there a rooted version?
Click to expand...
Click to collapse
Get any custom recovery CWM/TWRP and flash this
file.
:good:
Remember to just backup ur data first just in case.

I installed TWRP after the last update and now I can't seem to boot into it to flash 4.2.2. I hold the buttons and get into the boot menu, select recovery and ok, but then it gives message "No Command". Any ideas on how to get back to TWRP or reinstall TWRP to be able to flash?

Liquidretro said:
I installed TWRP after the last update and now I can't seem to boot into it to flash 4.2.2. I hold the buttons and get into the boot menu, select recovery and ok, but then it gives message "No Command". Any ideas on how to get back to TWRP or reinstall TWRP to be able to flash?
Click to expand...
Click to collapse
I am attaching the stock recovery for 4.2.1. You can flash it using "fastboot flash recovery recovery.img" after installing it upgrade to 4.2.2 and then reflash TWRP.
Or you can use the Nexus Root Toolkit to do it automatically.:good::good::good::good:

Thanks for this - I can't get past step 6. I can get to the android with the red exclamation but no matter what I do next I just get a black screen.
What am I doing wrong?

Here is another way:
Stock rom, rooted, cwm recovery, supersu, ota rootkeeper. I downloaded the update to my pc and copied it to the N7 internal memory. Booted into cwm recovery, chose to 'install zip from sdcard', 'choose zip from sdcard', '0/', (selected the update), update. After the update finished and I chose to restart and said 'Yes' to disable flashing stock recovery (thus keeping cwm), then said 'Yes' to restoring root. After bootup, and the upgrading android process, I have root and cwm recovery.
I don't think you get the options to disable flashing stock recovery and keeping root if you don't have ota rootkeeper and maybe supersu. Superuser may work the same. The update seems good and fast. I wasn't having any problems before, so I don't know exactly what changed. All in all the manual update worked out well for me.

Chimera2345 said:
Thanks for this - I can't get past step 6. I can get to the android with the red exclamation but no matter what I do next I just get a black screen.
What am I doing wrong?
Click to expand...
Click to collapse
The order is -
First press the power button and then the volume up button. If this does not work try volume down but remember power button first.
If all fails try the steps by Groid.

Once I get to the "red exclamation" it shows "no command", if I hold power then up it reboots into what I understand is APX mode (APX device shows up in device manager)? If I hold power then down it reboots back into recovery mode. I'm new to the Nexus 7/Android, the device is stock with 4.2.1.

bradputt said:
what a long filename to type
Click to expand...
Click to collapse
In windows you can start typing a filename and then hit tab and it will finish it, very handy.
Sent from my Nexus 7 using xda app-developers app

What about the updated bootloader? Is there a way to flash it? Thanks

Chimera2345 said:
Once I get to the "red exclamation" it shows "no command", if I hold power then up it reboots into what I understand is APX mode (APX device shows up in device manager)? If I hold power then down it reboots back into recovery mode. I'm new to the Nexus 7/Android, the device is stock with 4.2.1.
Click to expand...
Click to collapse
Got mine working, it was all down to timing on the power+up buttons. Flashed to 4.2.2 now, thanks for the help.

hi all
when i flash the zip file to upgrade to 4.2.2 i've got error7
assert failed: apply_path_check ("/system/vendor/lib/hw/power.grouper.so
i've tried to put the original file from the factory image but no working the permission i've set is rw-r-r what is wrong ?
my bootloader is on the 4.13 version
and using TWRP
tanks all
EDIT: i've found a tool to extract the file from factory image and chmod 755 and is okay

ok so this is a weird one.
i am stock 4.2.1, rooted, stock recovery and had Beats audio installer from the play store installed and that was it.
i found the script from the beats audio thread that removes the files and then i uninstalled.
then I unrooted, copied the new ZIP ffile over to my internal SD card and temp booted into TWRP and flashed it.
it came back and said assertion error
and the file it failed on is:
/system/lib/SR_AudioIn.SO
i was missing this file (not sure why)
went to my Nexus 4 and found that file and copied it into dropbox and then coped it into my system folder and set the proper permissions on it and rebooted.
tried to flash again and iot keeps failing on this file even though it is present and set properly.
is it possible this file is different for the N4 than the N7 and i need the N7 specific one?

I'm getting assert failed on /system/app/CalendarGoogle.apk.... any clues what to do?

dalanik said:
I'm getting assert failed on /system/app/CalendarGoogle.apk.... any clues what to do?
Click to expand...
Click to collapse
supposedly if it assert fails that means either its missing or its damaged/modified.
you would want to use Root Explorer if you are rooted and browse out to /system/app and see if it exists and if not then replace it, set permissions and reboot and try again to flash.

nextelbuddy said:
supposedly if it assert fails that means either its missing or its damaged/modified.
you would want to use Root Explorer if you are rooted and browse out to /system/app and see if it exists and if not then replace it, set permissions and reboot and try again to flash.
Click to expand...
Click to collapse
It exists. But how to get that specific APK? Download whole ROM and extract somehow? And where?

dalanik said:
It exists. But how to get that specific APK? Download whole ROM and extract somehow? And where?
Click to expand...
Click to collapse
if yours exists then i guess you are in the same boat as me where mine says another file doesn't pass yet it exists.
im waiting to find out what to do on that one as well.
if you have the entire stock rom then you would extract the contents of that rom and then extract just the file and push it to your device either with ADB or root explorer copy/paste.

[Q] Htc Rooting Issue

So i was following this tutorial on youtube which showed me how to flash a custom image however, i have tried it but i keep getting this message pop up. Naturally, i followed everything the guy did and it got to: fastboot devices, fastboot flash recovery.img (the img name) and got this error. Please help me.

ChiefMustardo said:
So i was following this tutorial on youtube which showed me how to flash a custom image however, i have tried it but i keep getting this message pop up. Naturally, i followed everything the guy did and it got to: fastboot devices, fastboot flash recovery.img (the img name) and got this error. Please help me.
Click to expand...
Click to collapse
Right click the recovery image, click on rename. Name it recovery for simplicity. Put it in the folder where fastboot, adb etc. is.
Open cmd, direct it to your working folder. Type fastboot flash recovery recovery.img Not recovery .img.img

What next?
James L said:
Right click the recovery image, click on rename. Name it recovery for simplicity. Put it in the folder where fastboot, adb etc. is.
Open cmd, direct it to your working folder. Type fastboot flash recovery recovery.img Not recovery .img.img
Click to expand...
Click to collapse
So i have followed these steps and it came to the attachment below. How do i get supersu onto my htc and is it definately rooted now?

ChiefMustardo said:
So i have followed these steps and it came to the attachment below. How do i get supersu onto my htc and is it definately rooted now?
Click to expand...
Click to collapse
It seems you are still typing the wrong thing. Type in:
Code:
fastboot flash recovery recovery.img
Just copy/paste the above code in your command prompt.
That is just to get the custom recovery TWRP on your phone.
Next download the SuperSU app and you will see a # symbol in your notifications to let you know you need to download the su binaries.
Choose the TWRP option and it will reboot the phone to TWRP recovery.
It may restart after it is done or you will have to press Back and choose Reboot then System. I just did this and I received an error in TWRP. I simply rebooted and SuperSU is working perfect and I have root access.

blaqueknight said:
It seems you are still typing the wrong thing. Type in:
Code:
fastboot flash recovery recovery.img
Just copy/paste the above code in your command prompt.
That is just to get the custom recovery TWRP on your phone.
Next download the SuperSU app and you will see a # symbol in your notifications to let you know you need to download the su binaries.
Choose the TWRP option and it will reboot the phone to TWRP recovery.
It may restart after it is done or you will have to press Back and choose Reboot then System. I just did this and I received an error in TWRP. I simply rebooted and SuperSU is working perfect and I have root access.
Click to expand...
Click to collapse
The custom image worked but ... I do not have a twrp option. I have:
HBOOT <-------- i chose this then recovery and the phone loaded. I then installed supersu and launched it but it said there is no su binary installed, and supersu cannot install it. this is a problem!
if you just upgraded to android 4.3, you need to manually re-root - consult the relevant forums for your device. <---- I have not upgraded. Please Help
RAMDUMP
REBOOT
REBOOT FASTBOOT <-------- I am guessing it is this one?
POWER DOWN

ChiefMustardo said:
The custom image worked but ... I do not have a twrp option. I have:
HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT <-------- I am guessing it is this one?
POWER DOWN
Click to expand...
Click to collapse
No, that will just reboot back into fastboot mode.
You have two options:
1. Press the Power button from that screen you just mentioned and click on the RECOVERY option
2. When you are in the OS type in the code below
Code:
adb reboot recovery

blaqueknight said:
No, that will just reboot back into fastboot mode.
You have two options:
1. Press the Power button from that screen you just mentioned and click on the RECOVERY option
2. When you are in the OS type in the code below
Code:
adb reboot recovery
Click to expand...
Click to collapse
Sorry to be so stupid but how do i get into the os?

ChiefMustardo said:
Sorry to be so stupid but how do i get into the os?
Click to expand...
Click to collapse
No, it's not stupid. I shouldn't have said it like that. Just turn the phone on, basically. I'm referring to the Android OS where you can use adb.

blaqueknight said:
No, it's not stupid. I shouldn't have said it like that. Just turn the phone on, basically. I'm referring to the Android OS where you can use adb.
Click to expand...
Click to collapse
So once i have turned the phone back on i input the code you gave me into cmd? <------ Did this and got this.

ChiefMustardo said:
So once i have turned the phone back on i input the code you gave me into cmd? <------ Did this and got this.
Click to expand...
Click to collapse
This is what i got

ChiefMustardo said:
This is what i got
Click to expand...
Click to collapse
I've seen that before. It usually means you have more than one adb.exe or it could really just be out of date. HTC Sync Manager and WinDroid both come with their own adb. I got rid of those two and the problem went away.
Type in the command prompt, in the same folder as adb.exe
Code:
adb version
The newest one is 1.0.32, just to rule out you don't have an older version.

blaqueknight said:
I've seen that before. It usually means you have more than one adb.exe or it could really just be out of date. HTC Sync Manager and WinDroid both come with their own adb. I got rid of those two and the problem went away.
Type in the command prompt, in the same folder as adb.exe
Code:
adb version
The newest one is 1.0.32, just to rule out you don't have an older version.
Click to expand...
Click to collapse
Yup i have that version. Shall i delete htc sync manager?

ChiefMustardo said:
Yup i have that version. Shall i delete htc sync manager?
Click to expand...
Click to collapse
If you don't use it, yes.

blaqueknight said:
If you don't use it, yes.
Click to expand...
Click to collapse
I have deleted now how do i sort it out because
adb reboot recovery didn't work last time. I have done adb reboot recovery and it started up the daemon rebooted the device. Now what do i do?

ChiefMustardo said:
I have deleted now how do i sort it out because
adb reboot recovery didn't work last time. I have done adb reboot recovery and it started up the daemon rebooted the device. Now what do i do?
Click to expand...
Click to collapse
I told you what to do in post #4.
I just said reboot into recovery to make sure you have TWRP installed
Next download the SuperSU app and you will see a # symbol in your notifications to let you know you need to download the su binaries.
Choose the TWRP option and it will reboot the phone to TWRP recovery.
It may restart after it is done or you will have to press Back and choose Reboot then System. I just did this and I received an error in TWRP. I simply rebooted and SuperSU is working perfect and I have root access.

blaqueknight said:
I told you what to do in post #4.
I just said reboot into recovery to make sure you have TWRP installed
Next download the SuperSU app and you will see a # symbol in your notifications to let you know you need to download the su binaries.
Choose the TWRP option and it will reboot the phone to TWRP recovery.
It may restart after it is done or you will have to press Back and choose Reboot then System. I just did this and I received an error in TWRP. I simply rebooted and SuperSU is working perfect and I have root access.
Click to expand...
Click to collapse
Sorry about the hassle. The reason why supersu isn't working is because bellend here has a phone running 4.4.3. How do i go about sorting out that issue?

ChiefMustardo said:
Sorry about the hassle. The reason why supersu isn't working is because bellend here has a phone running 4.4.3. How do i go about sorting out that issue?
Click to expand...
Click to collapse
It's no hassle, I just wanted to point that out to you.
Are you sure it is 4.4.3 or are you referring to an error message? Our phone should be 4.4.2. Even though one of the custom ROMs says 4.4.4.

blaqueknight said:
It's no hassle, I just wanted to point that out to you.
Are you sure it is 4.4.3 or are you referring to an error message?
Click to expand...
Click to collapse
It is i checked. I followed this guide instead http://forum.xda-developers.com/desire-510/general/guide-how-to-unlock-install-recovery-t2988292 and i launched it and it said this version is a development build and it ran. Now should it be rooted or is there another step i have to do? I just did root checker and it said that the root has been installed correctly

Thank you all. You have been a great help and i am hugely beyond belief grateful. The root has worked.

[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!

Anyone got OTA update for February update? I did not received one (root)

Is it only me who not receive OTA till now?

tanipat said:
Is it only me who not receive OTA till now?
Click to expand...
Click to collapse
Same here, always got day 1 in the past.

Me too, so i had manully sideload it

FlatOutRU said:
Me too, so i had manully sideload it
Click to expand...
Click to collapse
Where can you get it to sideload? Any thread with instructions?

swear0730 said:
Where can you get it to sideload? Any thread with instructions?
Click to expand...
Click to collapse
Lol, google it ?
https://developers.google.com/android/ota

FlatOutRU said:
Lol, google it
https://developers.google.com/android/ota
Click to expand...
Click to collapse
lolol I did google it and downloaded it a couple of days ago. That file is 1.5gb and from what I've read the update size is 9.3mb.
Maybe I've misunderstood the description on the download for the full OTA:
"This page contains full OTA update packages that allow you torestore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, [but without the need to wipe the device or unlock the bootloader./I]"
Maybe I'm tripping over the two italicized parts as it doesn't say whether it will wipe or whether it will retain my installed programs and data. Perhaps, "without the need to wipe the device" could mean that it will do it automatically.
Without an available nandroid backup I am reluctant to flash anything that is described as "Full".
Are you saying that flashing the Full OTA image at 1.5gb will not wipe installed programs and data?
At this point I'm pretty sure that is what you're implying. Can you confirm so I can proceed confidently?
TIA

swear0730 said:
lolol I did google it and downloaded it a couple of days ago. That file is 1.5gb and from what I've read the update size is 9.3mb.
Maybe I've misunderstood the description on the download for the full OTA:
"This page contains full OTA update packages that allow you torestore your Nexus or Pixel device's original factory firmware. ou will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, [but without the need to wipe the device or unlock the bootloader./I]"
Maybe I'm tripping over the two italicized parts as it doesn't say whether it will wipe or whether it will retain my installed programs and data. Perhaps, "without the need to wipe the device" could mean that it will do it automatically.
Without an available nandroid backup I am reluctant to flash anything that is described as "Full".
Are you saying that flashing the Full OTA image at 1.5gb will not wipe installed programs and data?
At this point I'm pretty sure that is what you're implying. Can you confirm so I can proceed confidently?
TIA
Click to expand...
Click to collapse
Yeah just follow instructions from that link and nothing will be erased
I was also confused about the 1.5gb file vut everything went ok

FlatOutRU said:
Yeah just follow instructions from that link and nothing will be erased
I was also confused about the 1.5gb file vut everything went ok
Click to expand...
Click to collapse
Did you retain root? Or did you have to re-patch the boot.img?

troymz1 said:
Did you retain root? Or did you have to re-patch the boot.img?
Click to expand...
Click to collapse
I don't know the proper way. Just to be sure i flashed stock boot/dtbo ans then sideloaded. Then did root thing again

troymz1 said:
Did you retain root? Or did you have to re-patch the boot.img?
Click to expand...
Click to collapse
This is the full ota file. Because you sideload it you can't retain root (you have to enter recovery - ota file is installed to the other slot). In the ota file you find also the boot.img to patch it and reapply root by flashing the patched boot.img through fastboot. Also i didn't receive the ota through air (even deinstalled magisk before checking for ota). Maybe Google changed something.... Gonna see what happens next month.

I did on Jan. 31. ATT pixel 4XL

I've always had very spotty success receiving and completing OTA updates from Google when on a rooted phone. On my 3a XL, I've been successful taking an OTA update probably 2 out of 8 months. So I have become an expert in sideloading the update. (My family's two other 3a XLs receive updates immediately and have no trouble completing them, so it definitely related to the fact that I'm rooted - even though I uninstall Magisk prior to attempting an update).
I created a thread in the Pixel 3a forum with directions on how to sideload and root your phone, but I will simply post that information here.
To sideload an update, follow these instructions. - This will not factory reset your phone and you will not loose any data or files.
Optional Step 1 - Uninstall Magisk (so that it restores the stock boot.img). If you find yourself unable to boot into recovery, you will have to restore the stock boot.img. I've run into this issue on some Android 10 images, but not all.
Step 2 - Download to your computer the correct OTA image from here
Step 3 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 4 - Boot your phone into recovery (type the command "adb reboot recovery").
Step 5 - The phone will have a green android robot with a red sign over it's open access panel. Press the power button and then the volume up button while still holding down the power button.
Step 6 - Select "Apply update from ADB" using the volume buttons to highlight the choice and the power button to select it to enter the sideload mode.
Step 7 - Using your computer, type "adb sideload ota_file.zip" where ota_file.zip is the name of the OTA file you downloaded in step 2.
Step 8 - Once the update finishes, reboot the phone to complete the update process. (The initial reboot can take some time as it has to optimize the apps behind the scenes, but it does so without the normal "Optimizing Apps" splash screen normally seen when taking an OTA update. Please be patient and let the phone finish the process. The more apps you have, the longer it may take. Do not force a reboot or turn it off during this initial boot).
After sideloading the OTA, you will have to reroot your phone using the magisk boot image patch installation method.
Step 1 - Obtain a stock boot.img file for the OS version/update that you are currently on. The easiest method is probably to download the applicable full stock image directly from Google. Unzip the files and unzip the second folder and you should find the boot.img file inside.
Step 2 - Copy the stock boot.img file to your phone's storage - probably to /sdcard or to /sdcard/downloads
Step 3 - Download and install the Magisk manager app on your phone. (link to the latest version can be found here). At one time early in the Android 10 cycle, users had to use the "Canary" Magisk builds. This is no longer true and you can use the stable version builds as long as it is version 20 or later. Of course users are still able to use the beta or Canary builds if they desire, but it is no longer a requirement.
Step 4 - Using the Magisk manager app, press "Install --> Install --> Select and Patch a File" - select the stock boot.img file that you put on your phone in step 2.
Step 5 - Magisk will modify the stock boot.img file and create a patched boot image file. It will save this modified file at "sdcard/Download/magisk_patched.img"
Step 6 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 7 - Copy the patched boot image from your device to your PC and the adb folder. If you can’t find the file on your phone via MTP or Windows Explorer, you can pull the file by typing the command "adb pull /sdcard/Download/magisk_patched.img"
Step 8 - Boot your phone into the bootloader (type the command "adb reboot bootloader").
Step 9 - Flash the patched boot image to your device using this command, "fastboot flash boot magisk_patched.img"
Step 10 - Reboot (using command "fastboot reboot").
I hope that helps.

I haven't gotten the update on mine (generic Google 4 XL, not carrier tied) yet either for this month. A few days ago if I pressed the "Check for update" button, about every dozen or so tries it would flash for a second or two 'Preparing system update' and then go back to "Your system is up to date", of which it's not since it's on the Jan 2020 update. Is there a particular file or set of files that the local phone and it's OS compares to the 'big updater in the sky' and then if different (local date/time stamp older type thing) the update starts? I'm looking for a way to manipulate a local file to force the OTA so I don't have to mess with the downloading and sideloading of the OTA and rerooting, it's just so nice to have Magisk do all that for me. I've done the sideload plenty of times, I'd just rather not have to do it.
Any ideas or suggestions?

YDBB said:
I haven't gotten the update on mine (generic Google 4 XL, not carrier tied) yet either for this month. A few days ago if I pressed the "Check for update" button, about every dozen or so tries it would flash for a second or two 'Preparing system update' and then go back to "Your system is up to date", of which it's not since it's on the Jan 2020 update. Is there a particular file or set of files that the local phone and it's OS compares to the 'big updater in the sky' and then if different (local date/time stamp older type thing) the update starts? I'm looking for a way to manipulate a local file to force the OTA so I don't have to mess with the downloading and sideloading of the OTA and rerooting, it's just so nice to have Magisk do all that for me. I've done the sideload plenty of times, I'd just rather not have to do it.
Any ideas or suggestions?
Click to expand...
Click to collapse
If your rooted, the system OTA will fail. Your only options are to side load the OTA, try the magisk OTA update method, or fastboot the factory image.

Badger50 said:
If your rooted, the system OTA will fail. Your only options are to side load the OTA, try the magisk OTA update method, or fastboot the factory image.
Click to expand...
Click to collapse
That's not what I've experienced. I had been using an Essential PH-1 (actually have two of them) and Magisk and every month Essential would put out the update as soon as, or frequently even a day or two sooner than google, and I simply did the 'Release Images' in Magisk, did the OTA and then the 'install Magisk to inactive slot' and reboot and I always stayed rooted and up to date. I got the Pixel 4 XL in November sometime and for the first two monthly updates (-> Dec 2019 and Jan 2020) the same process worked fine. Only now with the Feb 2020 update out there it's not taking / recognizing that it's there.
I did about a week ago see there was a Google Play system update that was pending and did it, and did the required reboot after. That didn't 'unroot' me. I'm wondering if that Google Play system update messed something up?

YDBB said:
That's not what I've experienced. I had been using an Essential PH-1 (actually have two of them) and Magisk and every month Essential would put out the update as soon as, or frequently even a day or two sooner than google, and I simply did the 'Release Images' in Magisk, did the OTA and then the 'install Magisk to inactive slot' and reboot and I always stayed rooted and up to date. I got the Pixel 4 XL in November sometime and for the first two monthly updates (-> Dec 2019 and Jan 2020) the same process worked fine. Only now with the Feb 2020 update out there it's not taking / recognizing that it's there.
I did about a week ago see there was a Google Play system update that was pending and did it, and did the required reboot after. That didn't 'unroot' me. I'm wondering if that Google Play system update messed something up?
Click to expand...
Click to collapse
GPS system updtae usually doesn't mess with anything root At least it didn't on my P2XL & 4XL.. Monthly security updates are a diffent story though on pixel devices where root is concerned.

Still no OTA eithers. Don't want to side load either. I'm on QQ1B.200105.004. Anybody on this build get it?

MicroMod777 said:
Still no OTA eithers. Don't want to side load either. I'm on QQ1B.200105.004. Anybody on this build get it?
Click to expand...
Click to collapse
Me neither

I'm currently on the same QQ1B.200105.004 build. They (google) did the same thing (a long delay into the month) this past month, hopefully not a recurring theme.

MicroMod777 said:
Still no OTA eithers. Don't want to side load either. I'm on QQ1B.200105.004. Anybody on this build get it?
Click to expand...
Click to collapse
Same build, no OTA may be this could force me to do sideload update which terrible

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.