Related
I get "Failed to find entry META-INF" when I try to flash an updated Android image from developers.google.com/android/images with TWRP. Does anyone know what I'm doing wrong?
You cant flash official image in twrp. If you want latest stock flash factory images.
Where can I find the regular Android images to flash via TWRP? I can't update OTA with TWRP installed, right?
xdadevelopersrocks said:
Where can I find the regular Android images to flash via TWRP? I can't update OTA with TWRP installed, right?
Click to expand...
Click to collapse
you cant flash anything official with twrp, if you want stock. You can flash factory images from google site, or flash FakeNexus rom, wich is basically stock 7.1.2 from google pixel. I highly recomend it. You can flash it using twrp, here's the link https://www.androidfilehost.com/?fid=673368273298962272
flash it in twrp, in aroma choose what do you want, for kernel i recomend stock kernel (choose it in aroma)
---------- Post added at 20:07 ---------- Previous post was at 20:05 ----------
actually, i think you downloaded factory images, lol. Decompress the zip and flash files in fastboot like
fastboot -w update <drag the zip that was inside first zip>
fastboot reboot
You can use the Nexus root toolkit (nrt) to flash a stock image.
[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?
Current Firmware: MHA-L09C346B136
I would like to apply the OTA firmware update but I can't since I had flashed TWRP and superuser a long time ago.
I've been googling around for the last 2 hours but I'm not still not sure what to do. The most relevant thread I found was: https://forum.xda-developers.com/mate-9/help/upgrade-firmware-due-to-twrp-root-t3591428
- "Flash original recovery.img from your firmware file via fastboot then upgrade your firmware via ota"
I've been searching around for my firmware but I can't seem to find it anywhere. Would any MHA-L09 firmware work?
And once I do find the firmware file, what other steps are there?
Do I need to extract recovery.img from the firmware using HuaweiUpdateExtractor or something like that?
Do I run the command fastboot flash recovery recovery.img after I find the recovery image?
triplemonitor said:
Current Firmware: MHA-L09C346B136
I would like to apply the OTA firmware update but I can't since I had flashed TWRP and superuser a long time ago.
I've been googling around for the last 2 hours but I'm not still not sure what to do. The most relevant thread I found was: https://forum.xda-developers.com/mate-9/help/upgrade-firmware-due-to-twrp-root-t3591428
- "Flash original recovery.img from your firmware file via fastboot then upgrade your firmware via ota"
I've been searching around for my firmware but I can't seem to find it anywhere. Would any MHA-L09 firmware work?
And once I do find the firmware file, what other steps are there?
Do I need to extract recovery.img from the firmware using HuaweiUpdateExtractor or something like that?
Do I run the command fastboot flash recovery recovery.img after I find the recovery image?
Click to expand...
Click to collapse
You could probably use L09C33B136 and extract recovery.img from that, then flash using fastboot as you said. Worst case you have to flash back TWRP if recovery doesn't work.
Do you know if you've modified /system, /product or /vendor? If you have you won't be able to install OTA, it will fail when checking if those partitions are modified.
If you want to update using full firmware you will have to rebrand.
ante0 said:
You could probably use L09C33B136 and extract recovery.img from that, then flash using fastboot as you said. Worst case you have to flash back TWRP if recovery doesn't work.
Click to expand...
Click to collapse
Thanks! I flashed the recovery.img file from that firmware as you suggested and now I have the latest firmware.
I noticed that the incremental firmware update that was already downloaded to my phone failed halfway though. Upon rebooting, I checked for updates again and this time round, it decided to download the full firmware instead which ended up being applied successfully.
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
First off I'm not responsible for anything that happens to your device
Attached below is the patched image for OnePlus 9 global 11.2.6.6
Flash via fastboot
For support and faster answer look here
Thank you for this! Since Magisk removed the option for OTA install, I was forced to do it the harder way... But you my friend made it much easier on me ! Thank you!!
Sorry for newbie's question, what's the difference between the two files? one is stock and one is patched?
Yes. Stock has to be flashed to take next ota. And patched is for root on current rom. Since op9 now uses google ota if any partitions are modified including the boot image ,it will fail.
Jg1234 said:
Thank you for this! Since Magisk removed the option for OTA install, I was forced to do it the harder way... But you my friend made it much easier on me ! Thank you!!
Click to expand...
Click to collapse
When did they remove OTA install? Mine still has it....
illusiveairforce said:
When did they remove OTA install? Mine still has it....
Click to expand...
Click to collapse
Mine still there as well. But I like to flash stock boot image back. Take ota. Then fastboot boot patched.img. Dump current boot image to sd through shell. Then direct install in magisk. I've seen many users have issues taking ota's using the other method. As in not even being able to boot or booting back into old build . So I prefer this way. Wanna avoid the msm tool and not loose data on device/have to factory reset.
mattie_49 said:
Mine still there as well. But I like to flash stock boot image back. Take ota. Then fastboot boot patched.img. Dump current boot image to sd through shell. Then direct install in magisk. I've seen many users have issues taking ota's using the other method. As in not even being able to boot or booting back into old build . So I prefer this way. Wanna avoid the msm tool and not loose data on device/have to factory reset.
Click to expand...
Click to collapse
What are the shell commands to extract the stock boot?
Amd4life said:
What are the shell commands to extract the stock boot?
Click to expand...
Click to collapse
we are making a group for global only and help can be found there
Amd4life said:
What are the shell commands to extract the stock boot?
Click to expand...
Click to collapse
'dd' command in Linux - GeeksforGeeks
Edit- I got it, I had to flash original images and then updates showed up. Thanks for posting these images.
Hi, thanks for posting the images. I assume global as in the US AA model since that is the only model with OTA from googles server right? The reason I was asking is I am on 11.0.4.4 and never received the notification for the update yet, but using oxygen updater, when I go in settings and check advanced mode, it shows a incremental update. My system under local file of course can't see it or will not show the update. I figured I could fastboot boot the stock image and then maybe it system could see the update, but when I try, the device just hangs on the fastboot screen(right before normally booting). I tried with my image and it booted. Do you have any suggestions? Thanks
Steps as follows if on rooted 11.2.5.5
1. flash stock 11.2.6.6.img
2. install OTA
3. flash patched 11.2.6.6.img
4. profit
TheBurgh said:
Steps as follows if on rooted 11.2.5.5
1. flash stock 11.2.6.6.img
2. install OTA
3. flash patched 11.2.6.6.img
4. profit
Click to expand...
Click to collapse
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
netgar said:
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
Click to expand...
Click to collapse
netgar said:
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
Click to expand...
Click to collapse
You are correct my friend. One needs stock untouched boot image to be able to take next update. If your on 11.2.5.5 you need that boot image to get ota to install correctly. This 11.2.6.6 img if for next round of updates. Here is 11.2.5.5 for anyone that might still be on older build.
Stock 11.2.5.5.img
drive.google.com
netgar said:
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
Click to expand...
Click to collapse
mattie_49 said:
You are correct my friend. One needs stock untouched boot image to be able to take next update. If your on 11.2.5.5 you need that boot image to get ota to install correctly. This 11.2.6.6 img if for next round of updates. Here is 11.2.5.5 for anyone that might still be on older build.
Stock 11.2.5.5.img
drive.google.com
Click to expand...
Click to collapse
Appreciate the input. I have been out of the game since the 6t so I am still trying to catch up
UPDATED POST
Alternatively, you could:
1. Go to Magisk manager, and tap Uninstall to unroot. And then regular reboot.*
2. Download and install partial OTA, reboot and confirm update. Reboot to bootloader.
3. Fastboot boot patched boot img**
4. Go to Magisk Manager and direct install for permanent root.
5. Reboot and profit.
*this step presupposes that Magisk has a STOCK boot.img to restore for the unroot procedure. If it does not have that, you're obligated to use the process described in post #11.
**you could actually use a recent previous version of patched boot img (like patched 11244) if the update's patched boot img is still unavailable, and then use Magisk manager to patch the update with a direct install
reaper000 said:
Alternatively, you could:
1. Go to Magisk manager, and tap Uninstall to unroot. And then regular reboot.
2. Download and install partial OTA, reboot and confirm update. Reboot to bootloader.
3. Fastboot boot patched boot img*
4. Go to Magisk Manager and direct install for permanent root.
5. Reboot and profit.
*you could actually use a recent previous version of patched boot img (like patched 11244) if the update's patched boot img is still unavailable, and then use Magisk manager to patch the update with a direct install
Click to expand...
Click to collapse
So doing it this method backs up stock untouched current boot image and reflashes during uninstall of magisk to allow ota to go through.? Since the op9 uses google ota all partitions have to be stock including boot image. Or it fails
reaper000 said:
Alternatively, you could:
1. Go to Magisk manager, and tap Uninstall to unroot. And then regular reboot.
2. Download and install partial OTA, reboot and confirm update. Reboot to bootloader.
3. Fastboot boot patched boot img*
4. Go to Magisk Manager and direct install for permanent root.
5. Reboot and profit.
*you could actually use a recent previous version of patched boot img (like patched 11244) if the update's patched boot img is still unavailable, and then use Magisk manager to patch the update with a direct install
Click to expand...
Click to collapse
this will fail
FizzyAps said:
this will fail
Click to expand...
Click to collapse
What's the command to flash the stock 11.2.5.5 boot.img? I tried renaming the boot_a.img the mattie_49 posted to boot.img but it would not flash.
TheBurgh said:
What's the command to flash the stock 11.2.5.5 boot.img? I tried renaming the boot_a.img the mattie_49 posted to boot.img but it would not flash.
Click to expand...
Click to collapse
Fastboot flash boot boot.img
mattie_49 said:
Fastboot flash boot boot.img
Click to expand...
Click to collapse
Thanks. Got the command to work this time. Tried a few times yesterday but had no luck