I own a non-Verizon unlocked pixel and I am currently on the June security update with TWRP and Root. I found out how to update to the June update from this thread: https://forum.xda-developers.com/pixel/how-to/guide-how-to-install-june-security-t3617536. Is is safe to repeat the same process as the above thread for the August update or is there a different way to install the update? Has anyone tried to install the August update and retained root?
Yes that method works, but instead of doing this manually, download the factory image august, open the flash-all script and remove the "-w" from last line (so it will update everything automatically without wipe).
After may, the verified boot signer is useless, so you don't need it.
-flash factory
-boot to twrp
-install twrp
-flash root and/or kernel
-reboot
Everything works fine here.
Awesome, thanks!
Using
Code:
adb logcat
I was able to grab the url and download each OTA. I have uploaded to my Android File Host account here.
I own the Android One Moto X4 XT1900-1 purchased from Project Fi and these only work on stock via stock recovery adb sideload. This is the same as taking the official OTA from the notification.
Dec - Blur_Version.27.21.2.payton_fi.google_fi.en.US (initial upgrade to Oreo)
Jan - Blur_Version.27.221.3.payton_fi.google_fi.en.US
Feb - Blur_Version.27.231.6.payton_fi.google_fi.en.US
Mar - Blur_Version.27.251.10.payton_fi.google_fi.en.US
Apr - Blur_Version.28.11.15.payton_fi.google_fi.en.US (upgrade to Oreo 8.1)
How can I install these files on my Moto X4, do you know?
Awesome you rock bro
Thanx a lot bro
abrfilho said:
How can I install these files on my Moto X4, do you know?
Click to expand...
Click to collapse
Try to ADB sideload with stock recovery
Neffy27 said:
Try to ADB sideload with stock recovery
Click to expand...
Click to collapse
I tried, and no success. I done this :
"adb sideload nameoftheupdate.zip" and i've had this message : "E: failed to unmount /"
I tried to set "mount /System" and redid the previous command but with no success again... any help ?
My moto X4 is on Project Fi Oreo (previously on Stock Moto, XT1900-7) and the bootloader is unlocked of course.
That is unfortunate. I'm not sure what advice to give next. I uploaded them in hopes to that it may help towards more customizations. Seems Lenovo really doesn't want to be like Google.
I plan to stay stock till development gets further.
THANK YOU for uploading this!! I am on a completely stock, locked, Project Fi moto x4 and was stuck on the 7.1.1 November update. Flashing the Oreo update via adb sideload worked perfectly
skmpowdjy said:
THANK YOU for uploading this!! I am on a completely stock, locked, Project Fi moto x4 and was stuck on the 7.1.1 November update. Flashing the Oreo update via adb sideload worked perfectly
Click to expand...
Click to collapse
Glad this worked for you. :good: plan to do the same whenever I get March notification.
On my 5th attempt to sideload the 8.0 update. Tried different downloads, file paths, and PC. Same results.
Step 1/2Error applying update: 20 (ErrorCode: : kDownloadState InitializationError)E: Error in / sideload/package.zip ( Status 1)
Any ideas?
Downloaded the full 8.0 firmware file and flashed in fastboot. While setting up the phone, got prompt for Jan security update. Installed it and check for Feb update. Also downloaded and installed. Guess I had some kind of glitch in 7.1.1 that prevented me from receiving OTA's or sideloading with ADB. Figures.
Glad you got it working ?
jfalls63 said:
Downloaded the full 8.0 firmware file and flashed in fastboot. While setting up the phone, got prompt for Jan security update. Installed it and check for Feb update. Also downloaded and installed. Guess I had some kind of glitch in 7.1.1 that prevented me from receiving OTA's or sideloading with ADB. Figures.
Click to expand...
Click to collapse
I just saw your post in the other thread and was about to direct you here. I was in the same boat. My only guess is that the Oreo update isn't being sent to devices on Verizon's network, but security patches are? There's someone else who posted on these forums a while back with the same issue on Verizon.
I had even tried removing the Sim, rebooting, and checking over WiFi before manual flash. Still don't know what caused ADB sideload to fail.
Official March OTA added!
Official April OTA added!
I can't get adb sideload to work. Strange.... Anyone with an unlocked bootloader have success? TWRP won't do it either.
Unlocked BL
Slickademo said:
I can't get adb sideload to work. Strange.... Anyone with an unlocked bootloader have success? TWRP won't do it either.
Click to expand...
Click to collapse
Also can't get sideload to work with unlocked bootloader. TWRP didn't work for me either. Can't tell why exactly it isn't working. My next thought was to try with a MicroSD Card.
Nick1801 said:
Also can't get sideload to work with unlocked bootloader. TWRP didn't work for me either. Can't tell why exactly it isn't working. My next thought was to try with a MicroSD Card.
Click to expand...
Click to collapse
I tried micro SD card with stock recovery and it did not mount. I just read that the newest update kills USB connectivity (besides charging) so it's probably best not to update until they fix that
So has the OTA files actually helped anybody? I thought I had at least one verified successful adb sideload done on a previous OTA.
I have a verizon pixel 2.
I have unlocked the bootloader and root with Magisk.
There are a few threads with different methods using factory and OTA images but I haven't been able to get it to work.
I'd like to update to the March update. Currently on Jan 5 build OPM1.171019.013
a quick run through would be helpful
Thanks
Hi,
My Pixel 3a as an unlocked bootloader and is rooted.
Usually, when I update my system every month, I get the OTA update zip on google website to do the update and only patches the boot.img from the factory image with magisk to keep the root.
But this month, we get Android 12 and I saw on this thread : https://www.xda-developers.com/how-to-install-android-12/ that it was recommended not to use the OTA update for updating to Android 12 on unlocked bootloader.
As I don't know why, can you explain me if it is or not dangerous or impossible, and eventually why I have to use the factory image to install this new system ?
I know that every time i made a wipe data (even if i know there's a way to delete the -w in the bat file but it's not recommended) it made me a day to restore all my apps and configurations... So if i can avoid this, I'd prefer.
Thanks in advance
oldbear3 said:
But this month, we get Android 12 and I saw on this thread : https://www.xda-developers.com/how-to-install-android-12/ that it was recommended not to use the OTA update for updating to Android 12 on unlocked bootloader.
Click to expand...
Click to collapse
I don't see this warning on that page?
The point of the full OTA sideload is that works with both locked and unlocked bootloaders.
The factory image only works with unlocked bootloaders.
I have a 4a with unlocked bootloader and just upgraded using the OTA and it was fine. I normally use the factory image (removing the -w arg) but found warnings on the internet that this would break when upgrading to Android 12 so I did the OTA instead.
I was even able to re-root with Magisk 23 as normal, which is apparently not possible for newer devices (eg. Pixel 5 guide: https://forum.xda-developers.com/t/guide-update-to-and-re-root-android-12.4345627/).
a1291762 said:
I don't see this warning on that page?
The point of the full OTA sideload is that works with both locked and unlocked bootloaders.
The factory image only works with unlocked bootloaders.
I have a 4a with unlocked bootloader and just upgraded using the OTA and it was fine. I normally use the factory image (removing the -w arg) but found warnings on the internet that this would break when upgrading to Android 12 so I did the OTA instead.
I was even able to re-root with Magisk 23 as normal, which is apparently not possible for newer devices (eg. Pixel 5 guide: https://forum.xda-developers.com/t/guide-update-to-and-re-root-android-12.4345627/).
Click to expand...
Click to collapse
Great, thanks a lot. Made just right now and it works perfectly. The root also worked for me.
a1291762 said:
I don't see this warning on that page?
Click to expand...
Click to collapse
About this question, it's written for OTA Updates :
"To install the stable build, you need to sideload the appropriate OTA package for your device from Recovery through ADB. This method will also work for Google Pixel devices with a locked bootloader"(but as I re-read it, I see that it's written that it "also work" with locked bootloader"). For the full update, it's written "If you have an unlocked bootloader on a Google Pixel device, you need to flash the full factory image of the Android 12 via Fastboot"...so I thought it was the only option.
But you're right, it's not exactly what's written.
I have Huawei Y9 2019 with unlocked bootloader running Pixel Experince Plus 12.1 and I want to go back to EMUI 9.1 because I saw in some threads that I need to have EMUI 9.1 Firmware installed and kernel 4.9.148 to run Android 13 GSIs but I am worried because I heard that flashing EMUI will lead to relock bootloader (Whatever the method, official or unofficial). Is this true? if so, how can I go back to EMUI without relock bootloader?
Check wether phone is Project Treble ready - what is required to flash GSIs. BTW: Android 13 GSIs ( experimental ) are available since February 1, 2023.
jwoegerbauer said:
Check wether phone is Project Treble ready - what is required to flash GSIs. BTW: Android 13 GSIs ( experimental ) are available since February 1, 2023.
Click to expand...
Click to collapse
My phone is already supports Project Treble, I just want to go back to EMUI 9.1 (Last time was EMUI 9.0 before bootloader unlock). They say EMUI 9.1 with kernel 4.9.148 required to run Android 13 GSIs, Android 12 GSIs and below work well without any issues on my phone.