Database Info

Official OTA Files - Android One XT1900-1 Only

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.

Nokia8 NB1 OTA updates for flash via stock recovery

Hey here I will share OTA for our NB1 to flash with stock recovery and sdcard method.
If I'm right it will work.
Pls try and report.
Download zip file,
Copy to external sdcard
Reboot to recovery,
Choose update from SD and press power button.
I will start with June security patch.
https://drive.google.com/file/d/1G0qg1b0ZbWjvWi3_WnimY3oy0xexRyXh/view?usp=drivesdk
Powered by View 10

Will work with sideload too, right?

hi
2WildFirE will this update patch can use and support for Nokia 8 TA-1004 Dual sim, i'm from malaysia region...

Unluckily it errors when installing on an unlocked phone....I unrooted it fully, rebooted to recovery and it errors always. Should I relock the bootloader to install OTAs?

No, you do not need to block the boot loader. You need to flash the previous full update 4.88B. And then upgrade to OTA.

I am already on 4.88B (rooted with magisk). No modification has been made on /system partition. I uninstalled magisk and rebooted: in theory that should be enough but in practice it does not work....

Topogigi said:
I am already on 4.88B (rooted with magisk). No modification has been made on /system partition. I uninstalled magisk and rebooted: in theory that should be enough but in practice it does not work....
Click to expand...
Click to collapse
It won't if this is block-based OTA as Magisk modifies boot partition (with Android kernel and in A/B case recovery too). Quote from Android official documentation: "block OTA handles the entire partition as one file and computes a single binary patch".

Sure, but I uninstalled magisk thus restoring original boot partition before trying to apply OTA...

dark ghost1988 said:
2WildFirE will this update patch can use and support for Nokia 8 TA-1004 Dual sim, i'm from malaysia region...
Click to expand...
Click to collapse
Thanks for reporting [emoji1360]
Powered by View 10

support
does this firmware are support for Nokia 8 TA-1004 dual sim...??

End of the story: I reflashed the full 4.88B OTA update and immediately after the new june patch: it always gives an error. Tried to install the june patch by OTA, and it errors in the same way. I have the doubt that the new patch is allowed to check the bootloader and if it founds it unlocked, an error arises. Anyone confirming that?

Topogigi said:
End of the story: I reflashed the full 4.88B OTA update and immediately after the new june patch: it always gives an error. Tried to install the june patch by OTA, and it errors in the same way. I have the doubt that the new patch is allowed to check the bootloader and if it founds it unlocked, an error arises. Anyone confirming that?
Click to expand...
Click to collapse
Ok, I assume that noone had problems in updating to the june security patches with an unlocked bootloader, so there must be a problem with my device......

Ok I managed to update to june security patches with this file......Had to reflash both slots (A/B) with the full june camera update (4.88B), then I updated through recovery and it worked. Glad to tell that the system is fully tested and working.

No news about July security patch?

Topogigi said:
End of the story: I reflashed the full 4.88B OTA update and immediately after the new june patch: it always gives an error. Tried to install the june patch by OTA, and it errors in the same way. I have the doubt that the new patch is allowed to check the bootloader and if it founds it unlocked, an error arises. Anyone confirming that?
Click to expand...
Click to collapse
confirmed ..
thats what happened to me
after i unlocked my bootloader ,rooted mgdisk
after July's OTA
i cant fastboot to june stock firmware
i even tried to sideload the june OTA and it said
that i cant downgrade from July to june

Topogigi said:
Ok I managed to update to june security patches with this file......Had to reflash both slots (A/B) with the full june camera update (4.88B), then I updated through recovery and it worked. Glad to tell that the system is fully tested and working.
Click to expand...
Click to collapse
Thanks Topogigi
How did you do it ?
im kinda stuck here
im considering OST LA ?

Any Ideas ??:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:

why666me said:
Any Ideas ??:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
have you tried switching slots? it sure wont solve the issue stated but it may restore the usability of your expensive brick :laugh:
Code:
If you are currently on slot A, type this: fastboot --set-active=_b
Or on slot B type this: fastboot --set-active=_a

No Switch with locked bootloader ?
Nothing work on fastboot with locked bootloader....

issue solved using OST LA 6.0.4

[November 13th 2018] System Update 1.24.709.93 rolling out

Hey folks,
I just got the notification for a system update. TW Model, currently in Germany. However, I tried capturing the ota link for patching the boot.img, but it gives me an error. Anyone with more luck than me?
Greetings
Update:
I managed to get the OTA.zip off my phone, but the update itself fails at 24%. Restored stock boot.img before of course. Has someone already installed it?

Hong Kong variant still on 1.24.400.03, December 2017 security update [emoji23][emoji23][emoji23]
Sent from my HTC U11 plus using Tapatalk

September 2018 security on latest 1.24.709.93... Can't remember before that... And I couldn't spot any difference between the two, does anybody see anything new?
Inviato dal mio HTC_2Q4D100 utilizzando Tapatalk

I've got it too on my TW model in the Netherlands.
Besides the security patch going from June 1 to September 1 I don't see anything different yet. Then again, there weren't any bugs I'm aware of, that needed fixing. 700MB+ seems like a lot for 3 months of security patches though.
It's nice to get an update and be less behind in security patch date again.
Thanks, HTC!

U11+ from Europe...
Didn't get the june security patch, didn't get this one either...

Tw version in Malaysia. Already updated. Everything okay. Doesn't explore much because going to work. only feel different at the display color. Looked better

UK version, no update available so far and still on 1 December 2017 security patch. I'd settle for them fixing the notification issue.
Sent from my HTC U11 plus using Tapatalk

Some findings
Battery before i go to work, 75%, on airplane mode.
Come back home after 11 hours, 75%
Soooo happy.....

Hmm.... maybe I need to learn how to roll back to stock now

Received today in Belgium with TW version of the phone!

gortys said:
Received today in Belgium with TW version of the phone!
Click to expand...
Click to collapse
Very important question:
Where/in which precise folder is the OTA update saved in HTC U11+ after downloading (I cannot find it...)
Thx a lot!

marusia7 said:
Very important question:
Where/in which precise folder is the OTA update saved in HTC U11+ after downloading (I cannot find it...)
Thx a lot!
Click to expand...
Click to collapse
Ow, sorry, I don't know at all!

gortys said:
Ow, sorry, I don't know at all!
Click to expand...
Click to collapse
found it in root folder:
data/data/com.htc.updater/files/

lillypad_33 said:
Hmm.... maybe I need to learn how to roll back to stock now
Click to expand...
Click to collapse
did you manage to update?
same situation here: although I flashed back to original boot.img (included in the last OTA update end of July 2018 which was later patched by Magisk), the update stucks at 24% with red error. Luckily the phone boots normally without applied update.
Anybody any idea how to proceed? I already tried to flash back the original boot.img from the stock RUU and also to use the boot.img provided in the latest OTA: with both boot.img (although both have very same size) the phone stucks at HTC logo but does not continue to boot.
Currently the HTC U11+ boots only from the boot.img provided with 709.8 OTA, (also booting with the patched_boot.img done by Magisk derived from the same).
I am a bit stuck here: Magisk should not touch the system (so no idea why the OTA stops at 24%) and only 1 out of 3 boot images are working (although all with same size), so currently I am not able to apply the OTA update...
I have read that for OTA updates the integrity (?) of the recovery.img is important ( (although Magisk should also not touch the recovery.img (?)
Any ideas?
best regards, Marusia

Looks like htc forgot people are still buying their phones outside Taiwan, or they don't have enough money to hire a translator!! I am an old loyal customer for 8 years, but here they are doing everything to let us get another brand, it's like they stabbed themselves and slowly turning the knife to feel more pain

marusia7 said:
did you manage to update?
same situation here: although I flashed back to original boot.img (included in the last OTA update end of July 2018 which was later patched by Magisk), the update stucks at 24% with red error. Luckily the phone boots normally without applied update.
Anybody any idea how to proceed? I already tried to flash back the original boot.img from the stock RUU and also to use the boot.img provided in the latest OTA: with both boot.img (although both have very same size) the phone stucks at HTC logo but does not continue to boot.
Currently the HTC U11+ boots only from the boot.img provided with 709.8 OTA, (also booting with the patched_boot.img done by Magisk derived from the same).
I am a bit stuck here: Magisk should not touch the system (so no idea why the OTA stops at 24%) and only 1 out of 3 boot images are working (although all with same size), so currently I am not able to apply the OTA update...
I have read that for OTA updates the integrity (?) of the recovery.img is important ( (although Magisk should also not touch the recovery.img (?)
Any ideas?
best regards, Marusia
Click to expand...
Click to collapse
I also flashed the recovery.img from the latest OTA, but still the red triangle.
Is it possible to flash the whole OTA via fastboot? Maybe thats a possibility.

metaxuss said:
I also flashed the recovery.img from the latest OTA, but still the red triangle.
Is it possible to flash the whole OTA via fastboot? Maybe thats a possibility.
Click to expand...
Click to collapse
I also flashed latest OTA recovery,same result...
I guess the only way is to flash back to stock RUU (which will lead to unrooted phone), install latest OTA via WLAN, then unlock bootloader (via HTCdev website) and root again with Magisk. I never did RUU flashing, so currently backing up everything with Titanium, if I proceed I will let you know the result...
Flashing the latest OTA might brick the phone (the red triangle already indicates that something went seriously wrong, although I have no clue what it could be: never touched the system, Magisk only patches the boot.img), instructions should be in the forum.

Tried another thing: disabling the systemless Xposed (installed via Magisk), reboot, restoring boot.img via Magisk, OTA download & trying to install --> red triangle...
I cannot remember if I disabled Xposed before the last OTA update few months ago. I had there some issues too (after successful OTA install the phone stuck at boot so I had to reflash the OTA-boot.img again via fastboot), maybe this procedure broke the possibility to install current OTA.
Will maybe try to flash selectively restored stock RUU images (without applying first the whole stock RUU) on the weekend (I have been informed by PM that this procedure should be harmless), so reverting to whole stock RUU is still not the last option.

I downloaded OTA from the following link and flash "system.img" with fastboot command. I am now on 1.24.709.93
https://drive.google.com/drive/folders/1wccnIY0NaoelhZQS4uhgP8ZGIn1iXhNX
Link Credit to : nene bear

kenosis said:
I downloaded OTA from the following link and flash "system.img" with fastboot command. I am now on 1.24.709.93
https://drive.google.com/drive/folders/1wccnIY0NaoelhZQS4uhgP8ZGIn1iXhNX
Link Credit to : nene bear
Click to expand...
Click to collapse
These OTA files dont contain system.img (the system.img file should be >4Gb).
1) Did you experience also OTA update issue (red triangle) as described in this thread?
2) Just to clarify: you flashed 1st the system.img derived from the stock RUU and afterwards applied the 709.93 OTA update?

[Q]How to change root from phh.superuser to Magisk and upgrade firmware?

Hi Guys, I've been an active user of XDA in the past but didn't have time to follow in the last couple of years so my memory about flashing and tinkering is quite blank.
Here is my situation:
Mate 9 MHA-L29C636B158 (very old ROM)
Bootloader unlocked with paid code from dc-unlocker
Rooted with PHH's Superuser (the only root that was available for our device back in March 2017)
EMUI 5.0 and Android 7.0 (that was obvious from my Build number but I just wanted to state it again)
TWRP 3.0.2-2 is installed with system kept read-only. Internal SD seems to be encrypted
I never took any OTAs as I was afraid that they would break something
In the last month's many of my banking or financial apps have stopped working because I'm rooted so I read that Magisk would be able to circumvent this safetynet thing and would allow me to continue using these apps. Google Pay would be a nice addition also.
At this point I would like to upgrade my firmware and get rid of PHH's Superuser switching to Magisk instead
Could someone please write a detailed guide how to do that? It might be interesting for other users also that are in my same situation. I'm willing to donate a few bucks for a complete and foolproof guide.
Thanks a lot

itenos said:
Hi Guys, I've been an active user of XDA in the past but didn't have time to follow in the last couple of years so my memory about flashing and tinkering is quite blank.
Here is my situation:
Mate 9 MHA-L29C636B158 (very old ROM)
Bootloader unlocked with paid code from dc-unlocker
Rooted with PHH's Superuser (the only root that was available for our device back in March 2017)
EMUI 5.0 and Android 7.0 (that was obvious from my Build number but I just wanted to state it again)
TWRP 3.0.2-2 is installed with system kept read-only. Internal SD seems to be encrypted
I never took any OTAs as I was afraid that they would break something
In the last month's many of my banking or financial apps have stopped working because I'm rooted so I read that Magisk would be able to circumvent this safetynet thing and would allow me to continue using these apps. Google Pay would be a nice addition also.
At this point I would like to upgrade my firmware and get rid of PHH's Superuser switching to Magisk instead
Could someone please write a detailed guide how to do that? It might be interesting for other users also that are in my same situation. I'm willing to donate a few bucks for a complete and foolproof guide.
Thanks a lot
Click to expand...
Click to collapse
Do you still have the unlock code? You'll want it, as the update from EMUI 5 to EMUI 8, on every device I've got, has relocked the bootloader.
With that said:
If you want to keep your data, make a backup using Hisuite.
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
If you modified other partitions on the device using TWRP or su in general, it wouldn't be a bad idea to use a nocheck recovery or HuRupdater to flash the entire system, to leave everything in a pristine state, since there are partitions you can't flash with fastboot, even with an unlocked bootloader. The instructions for HuR can be found elsewhere on XDA, as can details about nocheck recoveries, though the latter I'd be careful with - using HWOTA7 on Oreo, for example, WILL cause a brick. You've been warned.
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically. When Oreo is installed, it'll automatically relock your bootloader; you can continue updating here, though if you've got a particular target you want to go to, you might want to unlock and use HuR again to flash that specific one now that you're on Oreo. (The latest firmwares can't be rolled back to Nougat.) If you have no intention of going back to Nougat, you have your unlock code, and you aren't planning to do any other modifications like rebranding, then update away, though you may want to hold off of the Pie update if offered. (Shouldn't be, yet, but it could have been approved for your device already; it changes the boot partitions yet again.)
Now that you're on Oreo and presumably unlocked again, make sure you've got the FullOTA image downloaded for that firmware to your PC. (Always a good idea, anyway.)
Magisk can be installed by:
1) Flashing TWRP with fastboot, then flashing a suitable Magisk zip
2) Using Magisk Manager to patch a boot image and flashing that.
For TWRP:
Get a copy of TWRP from the forum here. When I use one, it's the 3.2.1-0 from @Pretoriano80, you'll find it in the development section. Any 3.2.x for Oreo should work though - a Nougat TWRP will not work.
Flash TWRP to recovery_ramdisk in fastboot. Boot to TWRP, flash Magisk.
For Magisk Manager:
Extract "ramdisk" from your FullOTA firmware. Place it in internal storage on your device. Use Magisk Manager to patch the image (install / patch boot image). Transfer the patched_boot.img created by Magisk back to your PC and flash that to the "ramdisk" partition in fastboot.

Just stumbled over your reply, didn't get an email notification from XDA. Thank you so much. Let's see if I can follow your instructions.
irony_delerium said:
Do you still have the unlock code? You'll want it, as the update from EMUI 5 to EMUI 8, on every device I've got, has relocked the bootloader.
Click to expand...
Click to collapse
Yes, I still have the code
irony_delerium said:
With that said:
If you want to keep your data, make a backup using Hisuite.
Click to expand...
Click to collapse
Done
irony_delerium said:
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
Click to expand...
Click to collapse
I downloaded the FullOTA with the FirmwareFinder app on my phone and transferred it to my laptop. Extracted the update.app with WinRAR and extracted system, boot, recovery and recovery2 using the Huawei Update Extractor 0.9.9.3.
Just to make no mistake, could you please confirm the order of flashing these 4 files? And maybe the correct command to use in fastboot?
irony_delerium said:
If you modified other partitions on the device using TWRP or su in general, it wouldn't be a bad idea to use a nocheck recovery or HuRupdater to flash the entire system, to leave everything in a pristine state, since there are partitions you can't flash with fastboot, even with an unlocked bootloader. The instructions for HuR can be found elsewhere on XDA, as can details about nocheck recoveries, though the latter I'd be careful with - using HWOTA7 on Oreo, for example, WILL cause a brick. You've been warned.
Click to expand...
Click to collapse
I don't think that I modified any other partitions, at least not willingly. I even left the system in read-only state. Don't know if phh.su did something by itself?
irony_delerium said:
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically. When Oreo is installed, it'll automatically relock your bootloader; you can continue updating here, though if you've got a particular target you want to go to, you might want to unlock and use HuR again to flash that specific one now that you're on Oreo. (The latest firmwares can't be rolled back to Nougat.) If you have no intention of going back to Nougat, you have your unlock code, and you aren't planning to do any other modifications like rebranding, then update away, though you may want to hold off of the Pie update if offered. (Shouldn't be, yet, but it could have been approved for your device already; it changes the boot partitions yet again.)
Now that you're on Oreo and presumably unlocked again, make sure you've got the FullOTA image downloaded for that firmware to your PC. (Always a good idea, anyway.)
Magisk can be installed by:
1) Flashing TWRP with fastboot, then flashing a suitable Magisk zip
2) Using Magisk Manager to patch a boot image and flashing that.
For TWRP:
Get a copy of TWRP from the forum here. When I use one, it's the 3.2.1-0 from @Pretoriano80, you'll find it in the development section. Any 3.2.x for Oreo should work though - a Nougat TWRP will not work.
Flash TWRP to recovery_ramdisk in fastboot. Boot to TWRP, flash Magisk.
For Magisk Manager:
Extract "ramdisk" from your FullOTA firmware. Place it in internal storage on your device. Use Magisk Manager to patch the image (install / patch boot image). Transfer the patched_boot.img created by Magisk back to your PC and flash that to the "ramdisk" partition in fastboot.
Click to expand...
Click to collapse
Will continue to do the above after your kind confirmation of my last questions. Thanks again

itenos said:
I downloaded the FullOTA with the FirmwareFinder app on my phone and transferred it to my laptop. Extracted the update.app with WinRAR and extracted system, boot, recovery and recovery2 using the Huawei Update Extractor 0.9.9.3.
Just to make no mistake, could you please confirm the order of flashing these 4 files? And maybe the correct command to use in fastboot?
Click to expand...
Click to collapse
The order shouldn't be particularly relevant, just that it's safest to reflash all of them:
- boot because phhsu may have modified the boot image to add su to it
- recovery and recovery2 because you loaded TWRP. recovery2 is specified because it's used to be recommended to flash to erecovery as well as normal recovery.
- system because I'm pretty sure that's the biggest thing modified Hy phhsu, and any other system changes you may have made.
Theoretically, other modified partitions won't matter since the upgrade to 8.0 replaces most (all, I think) of them anyway, but if you have to go through update steps through EMUI 5 first before it'll give you 8, then it's safest that they aren't modified. I mentioned other partitions because, with root & TWRP, you technically could have modified any and all of them.

irony_delerium said:
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically.
Click to expand...
Click to collapse
Flashing of 158 (original ROM version) went fine. Phone rebooted and titanium reported no root access, so it looks good.
After that I started the OTA update to 172 that waited already long time in my settings and it downloaded it. After downloading it gave me an error during the validation process of the file and asked to download it again.
Unfortunately now both the phone updater and the HiSuite app on my laptop say that 158 is the latest available firmware and no update is available.
I guess that I can download directly the newer firmware but I'm not exactly sure how to flash the whole package and what I should do with the other 2 files that come with it besides the update.zip

itenos said:
Flashing of 158 (original ROM version) went fine. Phone rebooted and titanium reported no root access, so it looks good.
After that I started the OTA update to 172 that waited already long time in my settings and it downloaded it. After downloading it gave me an error during the validation process of the file and asked to download it again.
Unfortunately now both the phone updater and the HiSuite app on my laptop say that 158 is the latest available firmware and no update is available.
I guess that I can download directly the newer firmware but I'm not exactly sure how to flash the whole package and what I should do with the other 2 files that come with it besides the update.zip
Click to expand...
Click to collapse
It might be tweaking out about the fact that you'd previously modified system.
I'd grab the last Nougat release (looks like 191; there are 2 of them, be sure it's not the rollback one you grab) and use hurupdater in TWRP to install it, then let the system try running OTA again.

irony_delerium said:
It might be tweaking out about the fact that you'd previously modified system.
I'd grab the last Nougat release (looks like 191; there are 2 of them, be sure it's not the rollback one you grab) and use hurupdater in TWRP to install it, then let the system try running OTA again.
Click to expand...
Click to collapse
I had to insert the SIM card of the country I bought my phone in to get the OTAs coming. Luckily I still had it with a few $ credit on it. It used just a few cents in data roaming for finding the new firmware, then I downloaded through wifi.
After 4 updates now I'm on 378 and no sign of Pie yet so this afternoon if I find some time I'll continue with rooting.

itenos said:
I had to insert the SIM card of the country I bought my phone in to get the OTAs coming. Luckily I still had it with a few $ credit on it. It used just a few cents in data roaming for finding the new firmware, then I downloaded through wifi.
After 4 updates now I'm on 378 and no sign of Pie yet so this afternoon if I find some time I'll continue with rooting.
Click to expand...
Click to collapse
Easy way:
Unlock phone, if you haven't yet again.
Download and flash TWRP from here: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353 (has decryption support) (flash to recovery_ramdisk as Huawei decided to split recovery partition into different parts)
Boot to TWRP, input pin (if you set a pin, else it will decrypt automatically)
Download Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Transfer Magisk to phone.
Flash Magisk zip in TWRP.
Reboot and you're done.
You might have to tinker around with Magisk Hide and hide apps if your banking apps still detect root.

As the Huawei Backup took over 4 hours to finish and i can't use Titanium, which is much faster, because I'm not rooted at the moment, I thought it's a good idea to first upgrade to Pie before unlocking my bootloader and losing all data. If I need to stay a few days without root it's ok.
Is there any way to get to Pie without being rooted? I tried the erecovery method on firmware finder. It says that my IMEI is now registered to download the update but when I enter erecovery it starts downloading the 378 oreo package.
I would like to avoid backing up and restoring twice this lengthy process, probably 16 hours all in all

itenos said:
As the Huawei Backup took over 4 hours to finish and i can't use Titanium, which is much faster, because I'm not rooted at the moment, I thought it's a good idea to first upgrade to Pie before unlocking my bootloader and losing all data. If I need to stay a few days without root it's ok.
Is there any way to get to Pie without being rooted? I tried the erecovery method on firmware finder. It says that my IMEI is now registered to download the update but when I enter erecovery it starts downloading the 378 oreo package.
I would like to avoid backing up and restoring twice this lengthy process, probably 16 hours all in all
Click to expand...
Click to collapse
The erecovery method won't work unless you can change the DNS settings on the network being used - it hijacks some of the requests to Huawei's servers to force the update. (And even then it's a bit finicky; I have yet to successfully use it, all things considered.)

Yesterday I finally received 9.0.1.159 with EMUI 9.0.1 by OTA. It installed fine and it's amazing how fast my phone became and how much screen on time I have now with my 2 year old device (8 full hours!). Good job Google and Huawei.
Being on Pie now I suppose that the instructions to root from you and ante0 are not valid anymore as they were meant for Oreo.
Could you please modify the instructions for Pie? And further, as I see that since yesterday in FirmwareFinder a new Pie update 9.0.1.178 popped up, could you please also add instructions how to take this OTA being rooted with Magisk once it arrives?
I've read a bit in the Magisk thread but I did not really understand the part of having to boot to recovery everytime I switch on the phone. Further they are talking there about EMUI 9 but I have already 9.0.1, is there maybe a difference I have to take care about?
Last but not least, I didn't forget my initial promise to donate a few bucks for the detailed instructions so please drop me your email in PM and I'll sent you a few through PayPal or in alternative, if you have some paid apps on the Playstore I could buy them so they might get more visibility.

itenos said:
Yesterday I finally received 9.0.1.159 with EMUI 9.0.1 by OTA. It installed fine and it's amazing how fast my phone became and how much screen on time I have now with my 2 year old device (8 full hours!). Good job Google and Huawei.
Being on Pie now I suppose that the instructions to root from you and ante0 are not valid anymore as they were meant for Oreo.
Could you please modify the instructions for Pie? And further, as I see that since yesterday in FirmwareFinder a new Pie update 9.0.1.178 popped up, could you please also add instructions how to take this OTA being rooted with Magisk once it arrives?
I've read a bit in the Magisk thread but I did not really understand the part of having to boot to recovery everytime I switch on the phone. Further they are talking there about EMUI 9 but I have already 9.0.1, is there maybe a difference I have to take care about?
Last but not least, I didn't forget my initial promise to donate a few bucks for the detailed instructions so please drop me your email in PM and I'll sent you a few through PayPal or in alternative, if you have some paid apps on the Playstore I could buy them so they might get more visibility.
Click to expand...
Click to collapse
The reason recovery boot is needed for Pie is because Huawei removed the ramdisk - in Pie, it's system as root with no way of forcing a ramdisk except by a recovery boot. So as a workaround, Magisk takes over recovery.
The installation instructions for it on Pie are pretty much the same as Oreo, except:
* Patch recovery_ramdisk, not ramdisk. Latest stable Magisk should work (18.1, iirc, has the patches to support recovery boot.)
* When booting, go to recovery. Magisk will start from there and take over the startup process.

irony_delerium said:
The installation instructions for it on Pie are pretty much the same as Oreo, except:
Click to expand...
Click to collapse
Hmm, where do I find the TWRP for Pie in order to flash?
And most importantly how do I have to behave in case of new OTAs coming?

itenos said:
Hmm, where do I find the TWRP for Pie in order to flash?
And most importantly how do I have to behave in case of new OTAs coming?
Click to expand...
Click to collapse
TWRP on this case, don't bother.
Extract your stock recovery from your firmware's update.app file, patch with Magisk Manager, and flash the patched image. When you want to flash an ota, put the stock recovery back.

Stop receving OTA updates for Pixel 3 after Root

2 months ago I decided to root my Pixel 3(to improve Camera Performance). While rooting I mistakenly download Factory Image of Pixel3 XL(crosshatch) and patch it with magisk after that phone went into boot loop . After some period of time I recognized my childish mistake and downloaded the latest factory image for pixel 3(blueline) first flash the stock image to get phone out of boot loop after then I rooted without any problem. But since that day I am not being able to receive any OTA updates for my device, is it because I removed the stock OS and flashed Factory Image of my own , and also If i want to sideload OTA updates with magisk what are the procedure for that.
P.S Thanks in Advance....much needed help

Rahul_Yf said:
2 months ago I decided to root my Pixel 3(to improve Camera Performance). While rooting I mistakenly download Factory Image of Pixel3 XL(crosshatch) and patch it with magisk after that phone went into boot loop . After some period of time I recognized my childish mistake and downloaded the latest factory image for pixel 3(blueline) first flash the stock image to get phone out of boot loop after then I rooted without any problem. But since that day I am not being able to receive any OTA updates for my device, is it because I removed the stock OS and flashed Factory Image of my own , and also If i want to sideload OTA updates with magisk what are the procedure for that.
P.S Thanks in Advance....much needed help
Click to expand...
Click to collapse
If you're rooted you can't take an ota directly. But follow this guide and you can get the ota, apply it, and root again. Pay attention to when you can reboot. https://topjohnwu.github.io/Magisk/tutorials.html

Rahul_Yf said:
2 months ago I decided to root my Pixel 3(to improve Camera Performance). While rooting I mistakenly download Factory Image of Pixel3 XL(crosshatch) and patch it with magisk after that phone went into boot loop . After some period of time I recognized my childish mistake and downloaded the latest factory image for pixel 3(blueline) first flash the stock image to get phone out of boot loop after then I rooted without any problem. But since that day I am not being able to receive any OTA updates for my device, is it because I removed the stock OS and flashed Factory Image of my own , and also If i want to sideload OTA updates with magisk what are the procedure for that.
P.S Thanks in Advance....much needed help
Click to expand...
Click to collapse
That was discussed in several posts here recently: https://forum.xda-developers.com/app...32382/page3857
Apparently it has been going on for 3 years now. Some people are impacted, others are not. Luckily, I have not been impacted so far.
You can sideload the OTA. Instructions are at https://developers.google.com/android/ota You must re-root after sideloading.

Hi,
Same problem here.
But the link https://topjohnwu.github.io/Magisk/tutorials.html doesn't work, neither this one : https://forum.xda-developers.com/app...32382/page3857
Can someone tell me how make the OTA update ?
Thanks

Nik0LaAs said:
Hi,
Same problem here.
But the link https://topjohnwu.github.io/Magisk/tutorials.html doesn't work, neither this one : https://forum.xda-developers.com/app...32382/page3857
Can someone tell me how make the OTA update ?
Thanks
Click to expand...
Click to collapse
The new link is https://topjohnwu.github.io/Magisk/
The Magisk forum on XDA has shutdown. Use Github instead.

dcarvil said:
The new link is https://topjohnwu.github.io/Magisk/
The Magisk forum on XDA has shutdown. Use Github instead.
Click to expand...
Click to collapse
Thanks for the link.
But if I follow the guide, it says:
After restoring stock images, apply OTAs as you normally would (Settings → System → System Update).
But the problem is my phone doesn't receive OTA updates
I'm stuck in November security update, and my phone doesn't see any update. So what can I do ?

Nik0LaAs said:
Thanks for the link.
But if I follow the guide, it says:
After restoring stock images, apply OTAs as you normally would (Settings → System → System Update).
But the problem is my phone doesn't receive OTA updates
I'm stuck in November security update, and my phone doesn't see any update. So what can I do ?
Click to expand...
Click to collapse
I don't get update notifications, but I see the update when I do Settings → System → System Update. If you don't even see them, you'll have to download the image from https://developers.google.com/android/ota, then sideload it and reroot. You may be able to patch the downloaded image before sideloading, but that opens the door for more potential problems. I wouldn't recommend it.

dcarvil said:
I don't get update notifications, but I see the update when I do Settings → System → System Update. If you don't even see them, you'll have to download the image from https://developers.google.com/android/ota, then sideload it and reroot. You may be able to patch the downloaded image before sideloading, but that opens the door for more potential problems. I wouldn't recommend it.
Click to expand...
Click to collapse
Unfortunately, when I do Settings → System → System Update, my phone doesn't see any update. It stucks in November
So I cannot keep my root ? There is no other way to update ?

Nik0LaAs said:
Unfortunately, when I do Settings → System → System Update, my phone doesn't see any update. It stucks in November
So I cannot keep my root ? There is no other way to update ?
Click to expand...
Click to collapse
No other way to my knowledge. You can re-root after the update.