Database Info

[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root

[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root
THIS GUIDE IS NOW DEPRECATED. THERE IS NO NEED ANYMORE TO GO THROUGH THE UPDATING PROCESS AS THERE IS A FULL NOUGAT FACTORY IMAGE AVAILABLE (Build NPH25.200-22). FIRMWARE AVAILABLE HERE: https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 BE SURE TO THANK @acejavelin FOR TRACKING DOWN THE FIRMWARE PACKAGE FOR US.
Notes:
-YOU ATTEMPT THIS AT YOUR OWN RISK IF YOU FLASHED ANY FIRMWARE PREVIOUSLY NOT FOR THE XT1575 US VERSION
-This guide will have 2 parts. 1 for those that kept their systems read only/systemless, and 1 for those that did not.
-Whether you live booted TWRP or Installed TWRP, if you chose to allow system modifications your OTA will likely fail (you'll need part 2).
-Restoring a TWRP backup will not work and will cause an OTA to fail due to having to allow system write access in TWRP - You Need Part 2.
-This guide assumes you have basic ADB knowledge and already know what fastboot is and how it works.
-Thanks to @gokart2 for the OTA and @acejavelin for the return to stock guides
Part 1: Those That Tweaked Systemlessly Currently On 24.49-18-16 (Will only work if you kept TWRP read only/used systemless root):
1: Disable & Remove systemless Xposed within Magisk Manager and all other Magisk modules. Reboot and wait for Art cache to rebuild.
2: Remove any adblock hosts within your adblock app if installed, or any other root level system altering apps like Greenify (don't worry, you'll get them back).
3: Remove Magisk by booting into TWRP and flashing the current Magisk Removal zip. Reboot.
4: For systemless SuperSu you need to consult their thread as I do not use it. (I'll update this if someone knows the correct process).
5: ADB reboot bootloader and fastboot flash the stock recovery. Latest MM recovery links at the bottom of this post. (rename file to recovery.img).
6: Move the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip to the root of your internal sd card (NOT in a folder). File links at the bottom of the post. Thanks @gokart2
7: ADB reboot recovery, when "no command" is listed, hold power + tap volume up then release to access recovery options. Choose "apply update from phone storage". Choose the file and wait for the flash. It's a large update so be patient (about 10-20min). Choose reboot manually in recovery after flash succeeds. Enjoy Nougat!
8: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly.
Part 2: Those That Have Done Everything - TWRP Write Access, Custom Roms, On Older Firmware, Etc (XT1572 Build Flashers Do This At Their Own Risk):
1: Flash the latest full factory image available (24.49-18-8) available here: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110. Thank @acejavelin for the thread while your at it. Follow the directions in that guide, it's well detailed and accurate - however read my notes just below first:
NOTES:
-Omit the "fastboot oem lock begin" & "fastboot oem lock" commands to remain bootloader unlocked.
-Omit the "fastboot erase userdata" command if you want to dirty flash and keep all of your data. I recommend clean, you can always root & restore each apps data with Titanium after the Playstore installs everything.
-The "fastboot oem fb_mode_set" instead of "fastboot oem lock begin" & "fastboot oem fb_mode_clear" instead of "fastboot oem lock" I've found to be unnecessary if staying unlocked. Your choice.
-The "fastboot flash partition gpt.bin" & "fastboot flash bootloader bootloader.img" commands will likely fail due to version mismatches. This is ok.
-The "fastboot flash modem NON-HLOS.bin" tends to fail too. For this, just run the command again until it succeeds.
2: After flashing 24.49-18-8 take the OTA to 24.49-18-16. Reboot. OTA zip provided below if you prefer to sideload.
3: Either install the 7.0 OTA the normal way via the update center or just side load it using the directions above. I recommend side loading due to the file size being very close to 1GB.
4: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly!
For Xposed, See My Guide Here: https://forum.xda-developers.com/showpost.php?p=74014516&postcount=96
Stock MM 24.49-18-16 Recovery: https://mega.nz/#!aZpC2RzQ!Fy3GTo_XYPjB1lwuHffCUUERuvnsyvON3kS8kMJ9Cm8
Stock MM 24.49-18-16 Recovery Mirror: https://drive.google.com/file/d/0BxxRfNko9QDKNS1NdnAyZVp6dVU/view?usp=sharing
24.49-18-8 OTA to 24.49-18-16: https://mega.nz/#!yZx2FLzR!cWfKIAYe5VyuadLI55UNHJvwWU98CXUi1g0DO1pDoKg
NPH25.200-22 OTA: https://mega.nz/#!HVhWWLxK!h-8G3vO3Sye_YwypyIJyWb2_79Ow34vNiDnMl2Q8uJg
NPH25.200-22 OTA Mirror: https://drive.google.com/file/d/0B3gPYUZ4nRLwOHJKQnNYczNEMHc/view?usp=sharing
MD5 for NPH25.200-22 OTA: 74d1a4b135200661cc4efd248f99ce33
Stock 7.0 NPH25.200-22 Recovery: https://mega.nz/#!TNoHQAjI!5U2w4p_G7pHlW6Mak7LqFR_PeWUDpSLc7S3OiUs_Qf8

Alrighty. I got back to stock 6.0 with the 18-16 update. I couldn't get the OTA via the system update, so I tried doing it via ADB. That threw up a "status 7 error". I then copied the file to my internal storage and selected update via SD Card in recovery. It hung on "Patching System Files" for a while, but in the end it moved on and worked fine. Thanks for the awesome guide!

Thread updated with downloads for the 24.49-18-8 OTA to 24.49-18-16 zip.
I exctracted the 7.0 Stock recovery to replace if you decide to flash TWRP and want to go back to the stock recovery for future updates (HAHAHA yeah right!). Download link in OP. The 7.0 Recovery is different than the MM recovery. They are not interchangeable. Don't flash the 7.0 recovery on MM.

Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?

Bwangster12 said:
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Click to expand...
Click to collapse
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.

annoyingduck said:
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
Click to expand...
Click to collapse
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?

hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?

Here's the recovery before the 7.0 one, just incase.. Was bored. Ok, I won't lie....didn't see u posted the 7.0 recovery....lol.:good::highfive:

Bwangster12 said:
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
Click to expand...
Click to collapse
Yup. TWRP flashes and works, magisk v14 works, and so far systemless xposed api24 is working.
EsteBandido4444 said:
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Click to expand...
Click to collapse
What is everyone's fascination with relocking the bootloader? You do not need to relock your bootloader. You cannot relock the bootloader unless all your system partitions match. Use my part 2 section. Read the notes, skip the bootloader lock commands. Leave your bootloader unlocked, get up and running on nougat, then you can issue the lock commands if you really want a locked bootloader.

How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
EDIT nevermind didn't read lol

Amp699435 said:
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
Click to expand...
Click to collapse
Copy the file to the root of your internal storage. Reboot into recovery. Hold power = volume up & release to access menu options. Choose apply update from storage. Select the OTA.zip package and let it install. (Directions are clearly written in OP.)

Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.

GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
Click to expand...
Click to collapse
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.

annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?

GrandAdmiral said:
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
Click to expand...
Click to collapse
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...

annoyingduck said:
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
Click to expand...
Click to collapse
Gotcha. I know I'm going to root again, but I've never used Magisk before so I wasn't sure of that piece.

annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
I am running Dirty Unicorns right now and when i looked up what I'm on in fastboot, it showed MPSH24.49-18-16. Would I just follow part 2 and use MPSH24.49-18-8 or something? I thought I had to use at least the version I'm on or newer.

GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.[/QUOTE
Your issue is that TWRP has modified your
System, any restoring of the stock rom will fail to update. So yes, you'll need to go through part 2 and downgrade and work your way back up.
Click to expand...
Click to collapse

I downloaded the zip (it took a while).
Restored to stock like 3 different ways but still hit a road block. I went the adb sideload route but got status error 7 because my build fingerprint wasn't correct. I tried searching for the right build I need, but I'm not an expert and couldn't find the right set of files that I was sure I knew how to restore. I ended up restoring my AICP backup.
If somebody could PM me and give me a hand (messaging through Hangouts or something) that would be AWESOME!
I'm planning trying to snag an XL 2 pre-order next week, but until then the less headache the better! Plus stock Nougat looks better on a Swappa listing

Trying to sideload via recovery 24.49-18-16 but I keep getting "("unexpected contents:EMMC:/dev/block/bootdevice/by-name/boot...". I've also tried installing from the phone but the same error appears in recovery. Any ideas?

Problems with updating to the newest OTA 1.24.709.8 TW version U11+

Hello there.
I unlocked my bootloader a long while ago, then flashed TWRP on my TW U11+. Now recently I have seen that there's an update and I get the popup from my updater.apk on my HTC U11+.
My phone is on 1.24.709.7 update. And it's I think most definitely the ASIA_TW version.
Mid - 2Q4D10000
Cid - HTC__621
So I try to update but of course fail because my recovery was TWRP so of course that it did not work. Then I hear that you need to have stock recovery, so what I do is I get stock recovery.img, go to download mode and flash it through the command "flashboot flash recovery recovery.img. I get the success command and I reboot and try download the OTA once again, then I try to update it. It does go to stock recovery but then it "updates" til 25% and then it's stuck. Then after like 10 seconds it just simply gives my this Red Triangle with an exclamation mark in the middle of it. So I press power button and vol down to get off that mode and that's it. It won't update to the newest OTA.
I flashed 1.24.709.7 recovery at first. It didn't work then I flashed 1.24.709.8 recovery but still no avail.
Can you guys please help me? I really don't know what I am doing wrong.
Thanks in advance

I am having the exact same problem. I wish I had the HTC__621 recovery, but I haven't been able to find the correct one.
Hopefully somebody will see this. Every link that looks like the right thing is dead.

Same problem
I had the same problem, too.
But I find a way to update to 1.24.709.8.
That is: I decide to flash the 1.24.709.8 version's RUU .
Hope this can help you.
U11+ All TW version's image and OTA :
//drive.google.com/drive/folders/1kNE8rN8yUBPo9vux9G3CMvUzg3cg0lQ3

Thanks for the link.
However the problem that I'm experiencing is that whenever I flash either 1.24.709.7 or 1.24.709.8 RUU. It just won't flash over fastboot. So what I do is I put it on my SD card then put the file and rename it to like 2Q4DIMG.zip and go to recovery and still won't flash it correctly.
I'll try it again today to see what error code I get from it.

Did you unlocked or rooted your u11+?

Sorry for the late reply man.
My HTC u11plus is unlocked and I also have rooted my phone via magisk.

You can't update with official ota if unlocked, you need to relock and have the stock recovery. Relock will wipe your data I think

You can OTA with unlock, but you must run pure stock ROM. I RUU my phone and successfully apply the OTA.
Magisk did modify /boot partition so OTA wont apply with Magisk. You have to restore stock boot, OTA, then patch the boot again to preserve Magisk. Also if you use 3rd party recovery you have to restore the stock one.
All partition image can be found in the RUU with https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928 but you must make sure you flash the version match your current system. If not the only way might be RUU your phone.

I have also had the exact same issue with updating the latest OTA update. I have TW model, it was unlocked and rooted with magisk. I relocked bootloader, stock boot img and still the update wouldn't install. I even tried flashing 1.24.709.7 RUU in downloader mode but failed remote: 22 RU_HEADER_ERROR.
Would love any ideas or help.
*UPDATE*
Finally was able to update to 1.24.709.8 OTA. I needed up unlocking the bootloader again, then downloaded the 1.24.709.7 full image from
drive.google.com/drive/folders/1kNE8rN8yUBPo9vux9G3CMvUzg3cg0lQ3
Extracted the rar file and manually installed the boot, recovery and system images separately and rebooted. Downloaded the update and installed, everything worked sweet!!

xymopen said:
You can OTA with unlock, but you must run pure stock ROM. I RUU my phone and successfully apply the OTA.
Magisk did modify /boot partition so OTA wont apply with Magisk. You have to restore stock boot, OTA, then patch the boot again to preserve Magisk. Also if you use 3rd party recovery you have to restore the stock one.
All partition image can be found in the RUU with https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928 but you must make sure you flash the version match your current system. If not the only way might be RUU your phone.
Click to expand...
Click to collapse
Thank you very much for this. I will try this tomorrow or something.
I will post my results here.

Btw is there any update for Emea region? They did one a month ago for TW models and since then no words about Europe and Middle East

Does anyone have a link to 1.24.401.7 9.0_CL1010171 ? I'm trying to find stock recovery that matches with stock rom and can't find it anywhere.
Magisk and TWRP installed at the moment.
I've got stock boot.img backed up before installing Magisk but there was no way to boot (without flashing) TWRP in order to backup stock recovery that came with U11+.
Cheers

HTC U11 firmware upgrade

Hello everyone,
First of all, sorry if i post it in the wrong section and if i am not always making sense.
So here is my situation :
i have a HTC U11 which i rooted a long time ago with TWRP & SU.
I then switch SU to Magisk (a year ago), because i needed to hide my root from few apps.
I wanted to update magisk Manager, but i lamely failed
(i went to recovery mode, installed the uninstaller ZIP for Magisk in order to put a version above 18 but then i had a boot.img missing error)
So i did restore an old backup that i had from 2017...
Currently i have :
Version android : 7.1.1
Firmware version : 1.27.400.8
Magisk version : 18.1
Magisk Manager Version : v7.1.1
TWRP Version : 3.3.0.0-ocn
My questions :
I want to update my firmware. I mean, my phone tells me there is an update. Is it what we call OTA ?
After i've downloaded the new firmware version (1.27.400.21), i select install now, and my phone reboots to Recovery mode, but asks me for a password (to decrypt data).
What the hell is that ?
Also, i would like to be able to still install this new version (and the futures ones).
How do i do that ?
Is it possible to upgrade the Android version too ?
I wish not to have to wipe or lose data.
What's the point to wipe data, dalvik, cache ?
When you do it do you lose your personnal data ?
Many thanks for your helps and support

toto_rigolo said:
Hello everyone,
First of all, sorry if i post it in the wrong section and if i am not always making sense.
So here is my situation :
i have a HTC U11 which i rooted a long time ago with TWRP & SU.
I then switch SU to Magisk (a year ago), because i needed to hide my root from few apps.
I wanted to update magisk Manager, but i lamely failed
(i went to recovery mode, installed the uninstaller ZIP for Magisk in order to put a version above 18 but then i had a boot.img missing error)
So i did restore an old backup that i had from 2017...
Currently i have :
Version android : 7.1.1
Firmware version : 1.27.400.8
Magisk version : 18.1
Magisk Manager Version : v7.1.1
TWRP Version : 3.3.0.0-ocn
My questions :
I want to update my firmware. I mean, my phone tells me there is an update. Is it what we call OTA ?
After i've downloaded the new firmware version (1.27.400.21), i select install now, and my phone reboots to Recovery mode, but asks me for a password (to decrypt data).
What the hell is that ?
Also, i would like to be able to still install this new version (and the futures ones).
How do i do that ?
Is it possible to upgrade the Android version too ?
I wish not to have to wipe or lose data.
What's the point to wipe data, dalvik, cache ?
When you do it do you lose your personnal data ?
Many thanks for your helps and support
Click to expand...
Click to collapse
aq
Find out your cid/mid
You will need to flash the appropriate ruu (nougot) for your phone from here (sd card method)
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/htmlview
in order to receive the ota updates. And yes you will lose everything. Backup as much as you can . And once you go to pie there is no going back unless s-off. ( There is another way but more involved) . hth

Thanks for your reply.
How do i find my cid/mid ?
I tried yesterday to use adb, but i could NOT find my device in download mode... The only way i was able to see it was to boot in recovery mode.
Can i still get my cid & mid if can find my device whilst it's in recovery mode ?
So i understood that i need to download the right file, rename it, put it on the root of the SD CARD and then boot my phone in bootlader mode.
Don't i have at some point specify the ZIP file to use ? Does it mean it will detect it automatically ?
Then why doesn't it work if i put it on the root of the internal sotrage of my phone ?
If i flash a RUU, will my phone still be rooted and unlocked ?

toto_rigolo said:
Thanks for your reply.
How do i find my cid/mid ?
I tried yesterday to use adb, but i could NOT find my device in download mode... The only way i was able to see it was to boot in recovery mode.
Can i still get my cid & mid if can find my device whilst it's in recovery mode ?
So i understood that i need to download the right file, rename it, put it on the root of the SD CARD and then boot my phone in bootlader mode.
Don't i have at some point specify the ZIP file to use ? Does it mean it will detect it automatically ?
Then why doesn't it work if i put it on the root of the internal sotrage of my phone ?
If i flash a RUU, will my phone still be rooted and unlocked ?
Click to expand...
Click to collapse
I believe the adb command is "getvar all" while in the download mode. get the cid/ mid number reboot then get matching nougot ruu zip. rename to 2pzcimg. zip place in the root of sd card boot to download mode not bootloader, it will detect automatically, hth

Thanks.
Will my phone still be rooted ?
Will i have to reinstall Magisk & Magisk Manager ?

toto_rigolo said:
Thanks.
Will my phone still be rooted ?
Will i have to reinstall Magisk & Magisk Manager ?
Click to expand...
Click to collapse
Oh no it won't be, you will have to reinstall twrp, Magisk,

fair enough.
but sadly, adb doesn't work on my computer. I can't see my phone.
I only get something when my phone is in recovery mode.
download more & bootloader mode, i can't find it.

toto_rigolo said:
fair enough.
but sadly, adb doesn't work on my computer. I can't see my phone.
I only get something when my phone is in recovery mode.
download more & bootloader mode, i can't find it.
Click to expand...
Click to collapse
Try installing htc sync manager then reboot and run adb. You just may need the right drivers

I have read more about it and you're right it should be something like that.
Also, once i have flashed the RUU, rooted again, installed TWRP & Magisk, will i still be able to update OTA ?
I don't understand when some people say they uninstalled Magisk, intall the OTA and install Magisk back on...
Is it really the way to do it ? To be able to install latest OTAs ?

toto_rigolo said:
I have read more about it and you're right it should be something like that.
Also, once i have flashed the RUU, rooted again, installed TWRP & Magisk, will i still be able to update OTA ?
I don't understand when some people say they uninstalled Magisk, intall the OTA and install Magisk back on...
Is it really the way to do it ? To be able to install latest OTAs ?
Click to expand...
Click to collapse
You will have to install ota before rooting , once rooted or twrp installed Ota will not install. This is my understanding, if someone has a different approach please chime in. Installing just the firmware is a different animal and requires more reading!! Hth

Okay so we are on the same page.
So my question is ow do you keep installing OTAs when your phone rooted or with TWRP ??
also i remember my cid is HTC__060 which i believe is india.
Is there anyway i can change it to Europe ? I mean, is there any interest for me to do so ?

toto_rigolo said:
Okay so we are on the same page.
So my question is ow do you keep installing OTAs when your phone rooted or with TWRP ??
also i remember my cid is HTC__060 which i believe is india.
Is there anyway i can change it to Europe ? I mean, is there any interest for me to do so ?
Click to expand...
Click to collapse
Ota will stop once twrp is installed, I really don't see a benefit changing cid, but that's up to u ?

To install an OTA with twrp you have to:
1. Download the OTA in zip format (search in this forum).
2. Copy it to mobile memory.
3. Reboot to twrp and apply manually the zip.
If you are going to change the Cid, change to Taiwan version (that region has received more updates than the rest of the world).

Update on unlocked U12+

I unlocked my U12 at the first day. Unfortunately I flashed a wrong boot.img to root it (TWRP was not out there).
Now I want to update it. My question: Can I OTA when I relock the bootloader, even with wrong boot.img? (It starts normally and I can use it).
Or is it not possible after root, so I have to use update.zip SD Card? And can I flash update.zip directly or should I relock the bootloader before?
And will relocking or update.zip delete my data?
Thanks

Do not re-lock your bootloader! Your device will be soft-bricked.
Just download a RUU (https://docs.google.com/spreadsheets/d/1wIRrVQawd5rD-t9VKPQ-SdRK20RcJVZhwD7lhmPIK8w/edit#gid=0) and flash it:
fastboot oem rebotRUU
fastboot flash zip RUU.zip
Click to expand...
Click to collapse
Maybe you need a few tries before its working.

mdxdave said:
Do not re-lock your bootloader! Your device will be soft-bricked.
Just download a RUU (https://docs.google.com/spreadsheets/d/1wIRrVQawd5rD-t9VKPQ-SdRK20RcJVZhwD7lhmPIK8w/edit#gid=0) and flash it:
Maybe you need a few tries before its working.
Click to expand...
Click to collapse
Ahh thx, I´ve alredy downloaded it but didn´t know the command
Will be anything deleted?
And whats after that? Can I lock the bootloader after flashing it? Or will OTA work again? Because I´m not shure if the OTA fails because of the unlocked bootloader or the boot.img.

After flashing the RUU, boot into bootloader an look the software status. It it says "Modified" you shouldn't lock the bootloader.
You can apply the OTAs afterwards by entering the stock recovery and choose "Apply update from ADB".
Than download the both OTA-Zips and flash (https://www.androidfilehost.com/?w=files&flid=297589).

mdxdave said:
After flashing the RUU, boot into bootloader an look the software status. It it says "Modified" you shouldn't lock the bootloader.
You can apply the OTAs afterwards by entering the stock recovery and choose "Apply update from ADB".
Than download the both OTA-Zips and flash (https://www.androidfilehost.com/?w=files&flid=297589).
Click to expand...
Click to collapse
I tried it some hours ago and it worked! Software Status is still modified, but I was able to install the next OTA normally in System Settings. I will try the next OTAs tomorrow, maybe I´am on Pie soon.
Thanks for your help.
A last question: Can I reroot it again (with TWRP this time), remove it when another OTA is out, install it and root again? It should work.

ASUS still blacklisting phones with unlocked&relocked bootloader (no OTA updates)?

ASUS still blacklisting phones with unlocked&relocked bootloader (no OTA updates)?
I read that was the case with previous iterations of ZenFones. Apparently phones that had their bootloader unlocked can't receive OTA updates, even if the bootloader has been relocked. But what about now? Is it the same for the Zenfone 7 series?
Also if anyone wants to relock their bootloader, for whatever reason, it's the same command as the one for the ROG Phone III. Big thanks to @THEHOLYG0D and @IDunnoLookatXDA https://forum.xda-developers.com/asus-rog-phone-3/help/relock-bootloader-t4152057
Code:
fastboot oem asus-lock
However... WARNING!
I did this command and my Zenfone 7 Pro was completely bricked, until I applied an update via SD card. That was the only thing that worked. "Apply update via ADB" just didn't work, neither did flashing boot.img, system.img and others one by one... So re-lock the bootloader, AT YOUR OWN RISK!

I think this is still the case. There was an OTA released 30th September and it still hasn't come through to my phone so I am now downloading it from the ASUS website.

What's the best procedure for applying an update downloaded from the Asus website?
- EDIT- Never mind, found the answer. Copy the .zip to the root of the phones internal storage and reboot

Minotaur said:
What's the best procedure for applying an update downloaded from the Asus website?
- EDIT- Never mind, found the answer. Copy the .zip to the root of the phones internal storage and reboot
Click to expand...
Click to collapse
Are you stock? Wouldn't recommend this process if you have TWRP & magisk installed.
Here is the process I followed:
Flash rom update from within TWRP, don't reboot.
Flash TWRP - both A & B slots.
Reboot recovery.
Flash Magisk.
Reboot system.

crumble6 said:
Are you stock? Wouldn't recommend this process if you have TWRP & magisk installed.
Here is the process I followed:
Flash rom update from within TWRP, don't reboot.
Flash TWRP - both A & B slots.
Reboot recovery.
Flash Magisk.
Reboot system.
Click to expand...
Click to collapse
Ahhhh so just flash the downloaded zip from twrp? Don't need to extract anything from it?

Minotaur said:
Ahhhh so just flash the downloaded zip from twrp? Don't need to extract anything from it?
Click to expand...
Click to collapse
Yep just flash it, no need to do anything else. Make sure you have latest version of TWRP if using an OTA, but for full zip from website any version should work.