Database Users

Phone booting back to TWRP

Hi everyone,
I'm rooted. I flashed the Beta 3 rom and TWRP. Then, I rebooted into TWRP and flashed Magisk v18. Now, my phone spins on the boot animation screen for about a minute, then reboots into TWRP. Any ideas what I should do? I've tried wiping cache, but still the same issues.

ledvedder said:
Hi everyone,
I'm rooted. I flashed the Beta 3 rom and TWRP. Then, I rebooted into TWRP and flashed Magisk v18. Now, my phone spins on the boot animation screen for about a minute, then reboots into TWRP. Any ideas what I should do? I've tried wiping cache, but still the same issues.
Click to expand...
Click to collapse
Same happened to me a few days ago and had to reflash full rom. PC still recognized device so I placed os on root of device and flashed. Unfortunately it wiped the device but at least it worked.

PapaMag said:
Same happened to me a few days ago and had to reflash full rom. PC still recognized device so I placed os on root of device and flashed. Unfortunately it wiped the device but at least it worked.
Click to expand...
Click to collapse
So you had to wipe everything?

ledvedder said:
Hi everyone,
I'm rooted. I flashed the Beta 3 rom and TWRP. Then, I rebooted into TWRP and flashed Magisk v18. Now, my phone spins on the boot animation screen for about a minute, then reboots into TWRP. Any ideas what I should do? I've tried wiping cache, but still the same issues.
Click to expand...
Click to collapse
I don't recommend updating that way. For me I flashed a patched boot.img from TWRP and it worked.

ledvedder said:
So you had to wipe everything?
Click to expand...
Click to collapse
When I flashed 9.0.11 again it wiped the device yes.

_Masked_ said:
I don't recommend updating that way. For me I flashed a patched boot.img from TWRP and it worked.
Click to expand...
Click to collapse
Obviously you are smarter than me. Thanks for the tip

PapaMag said:
Obviously you are smarter than me. Thanks for the tip
Click to expand...
Click to collapse
No problem, happy to help. By patched boot.img I mean the boot.img that was patched by Magisk.

_Masked_ said:
No problem, happy to help. By patched boot.img I mean the boot.img that was patched by Magisk.
Click to expand...
Click to collapse
Where can I get that boot.img file?
Sent from my ONEPLUS A6013 using Tapatalk

ledvedder said:
Where can I get that boot.img file?
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
The stock boot.img file is extracted from OOS and the patched boot.img is after you patch it via Magisk.

_Masked_ said:
The stock boot.img file is extracted from OOS and the patched boot.img is after you patch it via Magisk.
Click to expand...
Click to collapse
How do I extract it?
Sent from my ONEPLUS A6013 using Tapatalk

Use this if you're on OOS 9.0.5/9.0.6/9.0.7, but if you are on a higher OOS then you need to grab your stock boot.img for 9.0.10 from here and 9.0.11 from here, and patch it yourself using the instructions below.
Connect your phone to your PC using the OnePlus Cable
Reboot to Bootloader using "adb reboot bootloader" on PC while your phone is in TWRP
Rename stock boot .img file to boot.img on PC
Use "fastboot boot boot.img" on PC while your phone is in Fastboot Mode / Bootloader
Follow this guide once you are done with the above steps to root your phone with Magisk and actually boot.

I am in the same situation.
1) Got the phone. Unlocked with out-of-the-box firmware. Put TWRP on it, Magisk. All worked like a dream.
2) Time passed, I tried to play Fortnite a bit, which kicked me out due to root. Had to use Magisk Canary. Still, NO issues, all superb!
3) New firmware. The December one. Kept postponing it, but after like 2 weeks, I was like, meh, why not. Big mistake.
From this point on, I cannot root no matter what I try. As soon as I flash Magisk, it will keep booting back to TWRP.
I have even tried to grab the Canary ZIP to flash. Nothing. Tried flashing back the full base update file from OnePlus, then root. Nothing.
It's like an endless loop.
To be fair, I only use root / magisk because I need call recording. Sadly, it's been killed in Android 9, but OnePlus has a hidden feature for this. Unfortunately you have to use either ADB on each boot, or use Magisk to enable it and save you time, hassle.
Anyone has any idea, shoot.
This is a 100% unbranded, OnePlus-store-bought 8GB/128GB 6T model.
Ps.: IF you ever get stuck in this loop - you can boot your phone by using the original "boot.img".
You can grab it here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
To boot it, simply:
1) Enter Bootloader where you can use fastboot (NOT TWRP!).
2) Use `fastboot boot boot.img`
3) Your phone now will boot up.

h8Aramex said:
I am in the same situation.
1) Got the phone. Unlocked with out-of-the-box firmware. Put TWRP on it, Magisk. All worked like a dream.
2) Time passed, I tried to play Fortnite a bit, which kicked me out due to root. Had to use Magisk Canary. Still, NO issues, all superb!
3) New firmware. The December one. Kept postponing it, but after like 2 weeks, I was like, meh, why not. Big mistake.
From this point on, I cannot root no matter what I try. As soon as I flash Magisk, it will keep booting back to TWRP.
I have even tried to grab the Canary ZIP to flash. Nothing. Tried flashing back the full base update file from OnePlus, then root. Nothing.
It's like an endless loop.
To be fair, I only use root / magisk because I need call recording. Sadly, it's been killed in Android 9, but OnePlus has a hidden feature for this. Unfortunately you have to use either ADB on each boot, or use Magisk to enable it and save you time, hassle.
Anyone has any idea, shoot.
This is a 100% unbranded, OnePlus-store-bought 8GB/128GB 6T model.
Ps.: IF you ever get stuck in this loop - you can boot your phone by using the original "boot.img".
You can grab it here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
To boot it, simply:
1) Enter Bootloader where you can use fastboot (NOT TWRP!).
2) Use `fastboot boot boot.img`
3) Your phone now will boot up.
Click to expand...
Click to collapse
Try this.

ledvedder said:
How do I extract it?
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Plug your phone into your PC
Use this command in TWRP's Terminal and type this:
Code:
dd if=/dev/block/bootdevice/by-name/boot of=boot.img
Copy it from your phone to your PC (in the directory your command prompt is in) and use the command:
Code:
fastboot boot boot.img

TWRP doesn't work
Hi there,
Just like you I have installed twrp-3.2.3-x_blu_spark_v9.86_op6 TWRP recovery on my phone to flash custom ROM (as recommneded by this ROMs list), however, it doesn't work. Like, no matter whether you I to flash unofficial or official custom ROM, it says that 'Something isn't right'. I think there's some problem within this recovery. Hoping for good.

dgdeepak000 said:
Hi there,
Just like you I have installed twrp-3.2.3-x_blu_spark_v9.86_op6 TWRP recovery on my phone to flash custom ROM (as recommneded by this ROMs list), however, it doesn't work. Like, no matter whether you I to flash unofficial or official custom ROM, it says that 'Something isn't right'. I think there's some problem within this recovery. Hoping for good.
Click to expand...
Click to collapse
Flash the CORRECT one, for the OnePlus 6T. Not for the OnePlus 6.

Problem flashing stock image

I have UB and rooted with magisk 20.1. I rooted the October build by patching the boot image using magisk. I try to flash the new November stock image and it fails. It says
Writing boot
Failed (failed to write to partition Not found)
I think it may be connected to booting into slot a or b. Maybe?
Can anybody help?

You already took the November OTA or are you still on October?

ctfrommn said:
You already took the November OTA or are you still on October?
Click to expand...
Click to collapse
I'm on October trying to flash November

Pretty sure you cant flash the boot image alone. I always flash the stock boot for the build Im currently on then take the OTA. I think there is a new bootloader for November. Not 100% on that though.

I'm just trying to flash the full factory November stock image. I downloaded it, unzip it, plug in the phone in fastboot and double click the run me bat file.
This has always been fine before but I am new to pixel 3a and have only done this once before, on October build. But I came from an original pixel so I've spent 2 years updating that in this way.
I can't work out why the flash is failing.

Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.

ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
I've tried flashing October factory image and get the exact same result. Not sure what else to try.

ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
Sorry just reread your post. Will try and reflash boot IMG. I do that with fastboot flash boot.img?
Thanks

Yes.... fastboot flash boot boot.img

ctfrommn said:
Yes.... fastboot flash boot boot.img
Click to expand...
Click to collapse
Have tried reflashing boot.img and still won't update ota and same result trying to flash factory image. Any other ideas? And thanks very much for your help

ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
Do I need to flash boot.img to both slots a and b? If so how do I do that?

I only ever flash the one in use.
Just fastboot flash boot boot.img is all you need.
Your can also always just clean flash the OTA. Just download it, factory reset, adb sideload the OTA in recovery.
I've done that a few times now.

ctfrommn said:
I only ever flash the one in use.
Just fastboot flash boot boot.img is all you need.
Your can also always just clean flash the OTA. Just download it, factory reset, adb sideload the OTA in recovery.
I've done that a few times now.
Click to expand...
Click to collapse
Thanks. Will try things tomorrow. It's late here in London. But I can't get a twrp.img to work. It doesn't seem to mount the system and I can't flash anything. Have you got twrp to work? I'll come back to you in about 18hrs if that's ok?

TWRP doesn't work with Q. Just use stock recovery to sideload.

ctfrommn said:
TWRP doesn't work with Q. Just use stock recovery to sideload.
Click to expand...
Click to collapse
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much

Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
Yes, OTA and factory images are essentially the same thing just packaged differently.
And the easiest way to reroot is to just download and repatch the new stock image, or flash a custom pre patched kernel.

Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
The OTA zip is packaged differently and does not include a boot.img file that we can use. (I'm sure it must be in there somewhere, but not in a usable form). Therefore you must download the "Factory Image" from Google. Unzip it, open it where you will find another zip file inside. Open that second zip file and you will find the boot.img file there. Move that boot.img file to your phone so that Magisk can access it and to modify it.
https://developers.google.com/android/images

Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
FYI here are the steps I took to update my rooted 3a this morning:
1. in Magisk Manager select Uninstall and select restore images (I did this because I kept getting a 'installation error' on the OTA page)
2. Like an idiot I rebooted my phone, do not reboot! So I had to reinstall magisk
2a. copy the boot.img of Oct to my phone to have it patched by magisk
2b. fastboot flash boot boot_patched.img
3. the OTA downloaded while I was on the stock boot.img so I just followed the magisk instructions to install the OTA in the other partition
Next month I'll just jump from step 1 to 3 and carry on being rooted.

The simplest way to update when youre rooted is to......
Reflash the stock boot from the current build youre on
Take the OTA directly on the phone
Download stock image from new build and move it to phone
Patch with Magisk and move to your PC
Fastboot flash boot boot.img
Ive done this for the last 3 updates and it works perfectly every time......I obviously substitute my kernel for the patched boot but the process is the same. I find this far simpler than messing with Magisk

Thanks for all the suggestions but I still cannot update.
I have tried restoring boot.img
data reset from recovery
relocking bl - ota fails
Unlocking bl again - won't flash using ADB
There is no problem with the phone being recognised on ADB, the flash Just fails as the screen shot in my opening post. I'm thinking it may be connected to needing to flash to the inactive slot.
Anyone got any ideas?

[Q] Magisk 20.1 breaks Wifi after install on 6t Android 10

Anyone have a resolution for this? I have searched, but can't find an answer.

you could reset your network in settings/system

ecompton59 said:
you could reset your network in settings/system
Click to expand...
Click to collapse
Sorry I should have done a better job clarifying. It WiFi does not turn on, on my phone with Magisk installed. It does with it removed. The icon goes through the process but never turns on.

jivy26 said:
Sorry I should have done a better job clarifying. It WiFi does not turn on, on my phone with Magisk installed. It does with it removed. The icon goes through the process but never turns on.
Click to expand...
Click to collapse
TWRP is the culprit, reflash the factory rom and it will work.

qbanlinxx said:
TWRP is the culprit, reflash the factory rom and it will work.
Click to expand...
Click to collapse
Dirty flash of the rom fixed it thank you

jivy26 said:
Dirty flash of the rom fixed it thank you
Click to expand...
Click to collapse
Did you flash it through TWRP or stock installer?
Thanks

bigjailerman said:
Did you flash it through TWRP or sick installer?
Thanks
Click to expand...
Click to collapse
Twrp but what he recommends hear overwrites my rom removing magisk. When I reflash magisk it's the same issue.
I'll look into sick installer.

Dont know the exact reason but custom kernal installation fixing it.

I fixed it by running the update through the local upgrade again. It fixed it after one local upgrade with standard magisk upgrade steps.

jivy26 said:
Twrp but what he recommends hear overwrites my rom removing magisk. When I reflash magisk it's the same issue.
I'll look into sick installer.
Click to expand...
Click to collapse
What Magisk version you use?
look this https://forum.xda-developers.com/on...nofficial-twrp-touch-recovery-t3860815/page24

Flash you're boot img after twrp.

Mervingio said:
What Magisk version you use?
look this https://forum.xda-developers.com/on...nofficial-twrp-touch-recovery-t3860815/page24
Click to expand...
Click to collapse
10.1 flashing a custom kernel then Magisk and I have no WiFi issues. It is some conflict with standard OnePlus 6t kernel.

https://forum.xda-developers.com/oneplus-6t/how-to/ultimateguide-t4004367
Take a look at this...

Payload dumper
You have to use payload dumper. Extract Payload dumper after You downloaded it in a folder. Download the lastest 6t Stock Android zip file 10.0.1, extract it and take out the payload.bin file,
put it in the input folder of payload dumper and start payload dumper. Wait some time. Now in the Output folder take out the boot.img and send it trough Your phone, install Magisk in Your phone. It is still uninstalled now and it will remain unistalled now. Tap on install where Magisk is uninstalled and still Red, again tap on install and choose patch a file, it will open Your Filemanager on Your phone, choose the destination of Your boot.img. and tap on Your boot.img file.
Now magisk will flash it. After that look in Your download folder, there You will find the file magisk_patched.img, save it on Your PC. Start Your phone in to the fastboot mode and flash in minimal-adb-or-fastboot the magisk_patched.img.
You have to write fastboot flash boot. Now drag and drop the magisk_patched.img in to the window, so it will look like this:
fastboot flash boot "C:\Users\(Your Username)\Downloads\magisk_patched.img"
Hit enter, just some seconds and it is done. Now write fastboot reboot and hit enter. The phone reboots and Wifi also appears and the sound is working. You have to do it again when the next update appears. Maybe Android Oxygen OS 10.0.2
I am wondering about the next updates from android 11 (R), 12 (S), 13 (T). If it will work the same till Fuchsia OS is coming out and we will say good bye to Android and maybe goodbye to custom ROMs.
But PC Games on the Phone would be a tasty thing because Fuchsia OS is supporting APKs and EXEs too.
Have Fun.

KitsuneUK said:
I fixed it by running the update through the local upgrade again. It fixed it after one local upgrade with standard magisk upgrade steps.
Click to expand...
Click to collapse
Did you have to go all the steps again...?
full rom through local updater dont reboot
flash twrp installer dont reboot
flash magisk on inactive sloth through magisk manager
or did you just flash the rom through updater and reboot?
Thanks

bigjailerman said:
Did you have to go all the steps again...?
full rom through local updater dont reboot
flash twrp installer dont reboot
flash magisk on inactive sloth through magisk manager
or did you just flash the rom through updater and reboot?
Thanks
Click to expand...
Click to collapse
I ran through the standard upgrade process for root.
Uninstall Magisk and restore original images
update through settings > local upgrade with the full ota zip
install magisk to inactive slot. That keeps magisk installed and should let you reinstall the update.

Root for P-SMR7-RC003-RZR 210107.3225

Here is the patched Magisk boot.img and the stock one incase you need to flash back. No TWRP, just root.

thanks for this.. i was looking everywhere for boot extraction tools

Hi. I am looking for some method to flash a recovery or rooted boot for Razer 2 since the USB port on it is messed up.
Not sure if it is the software or the hardware, but the only way I can charge it at all (slowly) if I use an USB A to C cable and the device is off (well, not really since it flashes the logo, vibrates, and now complains about the unlocked boot-loader)
The stock recovery has the option "apply update from SD card" Are there any signed images in update.zip form I could just throw on the sd card?

By the way, where can I get a link to
P-SMR7-RC003-RZR 210107.3225 images? The official factory image page does not have it.​

There isn't one. Once booted you can use ADB over WiFi. But Fastboot only works with USB.

You're far better off updating to the newest firmware and patching via magisk than ever using downloaded pre-patched boot images

That would be true if we could get Magisk to patch a un-rooted phone. All I've done here is extract the latest stock firmware and patch it with Magisk so others can flash it. I believe the first time you boot after, it askes you to updated to the latest version.

hackthis02 said:
Here is the patched Magisk boot.img and the stock one incase you need to flash back. No TWRP, just root.
Click to expand...
Click to collapse
Do you have a recommended guide on how to use these? I have RP2 and not sure where to begin since it's stock.

kylster said:
Do you have a recommended guide on how to use these? I have RP2 and not sure where to begin since it's stock.
Click to expand...
Click to collapse
Take the patched one and flash it like you would any boot.img
Flash w/ Fastboot

pensive said:
By the way, where can I get a link to
P-SMR7-RC003-RZR 210107.3225 images? The official factory image page does not have it.​
Click to expand...
Click to collapse
not sure if i can paste here, but here we go...
Spoiler
https://www.reddit.com/r/razerphone/comments/iyb47z
im not sure why in razer webpage is incorrect, but is the same server AWS
P-SMR7-RC003-RZR 210107.3225Security Maintenance Release / Over The Air (OTA) UpgradeGlobal (Aura)9.0 Pie2021 February 05
https://s3.amazonaws.com/cheryl-factory-images/aura-p-release-3225-user-full.zip

Hey I recognize that post

OnePlus 8 [IN2015]-[A13-F15]-Stock Boot-Recovery & Patched Boot vs Modded Recovery with ADB Enabled

OnePlus 8 series has just got F15 Update with Dec Security Patch and few improvements. Since it's Incremental Update so it'll be little annoying to extract stock images from payload.bin. So attached to this post are :
+ Stock boot image of IN2105-F15
+ Magisk patched boot image of IN2105-F15
+ Stock recovery image of IN2105-F15 ( in case )
+ Modded recovery image of IN2105-F15 with ADB Enabled, Allow-mock-location and Debuggable are both enabled.
How :
Just simply flashing the images u want using fastboot command.
Cheers! [And Happy New Year Yall]

Hi, I just bought this phone with this F15 update. Should I root it and flash your version ? I'm looking to have the full cam back. thanks

LinhBT said:
OnePlus 8 series has just got F15 Update with Dec Security Patch and few improvements. Since it's Incremental Update so it'll be little annoying to extract stock images from payload.bin. So attached to this post are :
+ Stock boot image of IN2105-F15
+ Magisk patched boot image of IN2105-F15
+ Stock recovery image of IN2105-F15 ( in case )
+ Modded recovery image of IN2105-F15 with ADB Enabled, Allow-mock-location and Debuggable are both enabled.
How :
Just simply flashing the images u want using fastboot command.
Cheers! [And Happy New Year Yall]
Click to expand...
Click to collapse
Thank you so much man! May I ask how do you extract boot.img from incremental updates?

karib97 said:
Hi, I just bought this phone with this F15 update. Should I root it and flash your version ? I'm looking to have the full cam back. thanks
Click to expand...
Click to collapse
Yes, if your bootloader is unlocked.

LinkinLover2013 said:
Thank you so much man! May I ask how do you extract boot.img from incremental updates?
Click to expand...
Click to collapse
I used modified payload_dumper script bro. But in fact, if you're already rooted, you can do it easily since our device is A/B

LinhBT said:
I used modified payload_dumper script bro. But in fact, if you're already rooted, you can do it easily since our device is A/B
Click to expand...
Click to collapse
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?

LinkinLover2013 said:
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
Click to expand...
Click to collapse
You sure that ur device's IN2015? Cuz this happened means smt wrong with the kernel ( which inside boot.img and sometimes in dtbo.img too ). And I can only give out 1 guess that is ur device is not In2015

LinkinLover2013 said:
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
Click to expand...
Click to collapse
About the OTA update without lossing root, just don't reboot when System update finished its job and ask to reboot. Instead, Open Magisk, disable all modules, then choose to install to Inactive Slot. After finish, reboot like normal and u'll still have root!

LinhBT said:
You sure that ur device's IN2015? Cuz this happened means smt wrong with the kernel ( which inside boot.img and sometimes in dtbo.img too ). And I can only give out 1 guess that is ur device is not In2015
Click to expand...
Click to collapse
Ye I have IN2015.

LinhBT said:
About the OTA update without lossing root, just don't reboot when System update finished its job and ask to reboot. Instead, Open Magisk, disable all modules, then choose to install to Inactive Slot. After finish, reboot like normal and u'll still have root!
Click to expand...
Click to collapse
Well the problem is that If I try to install update it won´t install when I´m rooted. Always saying error and only thing that helps is to flash stock boot.

LinkinLover2013 said:
Well the problem is that If I try to install update it won´t install when I´m rooted. Always saying error and only thing that helps is to flash stock boot.
Click to expand...
Click to collapse
Use Oxygen Updater to download the update build! Btw, did u fix the wifi?

LinhBT said:
I used modified payload_dumper script bro. But in fact, if you're already rooted, you can do it easily since our device is A/B
Click to expand...
Click to collapse
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
LinhBT said:
Use Oxygen Updater to download the update build! Btw, did u fix the wifi?
Click to expand...
Click to collapse
Nah I tried flashing stock boot.img back from the files u provided but it didn't do anything. Guess I'll need to do fresh install od F13...

LinkinLover2013 said:
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
Nah I tried flashing stock boot.img back from the files u provided but it didn't do anything. Guess I'll need to do fresh install od F13...
Click to expand...
Click to collapse
Strange! How did u flash the magisk patched image? And did u do the disable verity with vbmeta?

LinhBT said:
Strange! How did u flash the magisk patched image? And did u do the disable verity with vbmeta?
Click to expand...
Click to collapse
I got your stock boot.img; patched with magisk app; flashed through PC fastboot (fastboot flash boot boot.img) and that´s all. I wasn´t disabling any verity; what´s that? Also do you have an app that works for updating with oxygen updater pls? I downloaded a zip but can´t find an working updater app that install zips...

LinkinLover2013 said:
I got your stock boot.img; patched with magisk app; flashed through PC fastboot (fastboot flash boot boot.img) and that´s all. I wasn´t disabling any verity; what´s that?
Click to expand...
Click to collapse
When flash non-stock images into stock firmware, we'll have to disable AVB ( Android verified boot ) by flashing vbmeta image ( fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img ) ( OOS13 on 1+ devices may need to flash vbmeta_system too )

LinhBT said:
When flash non-stock images into stock firmware, we'll have to disable AVB ( Android verified boot ) by flashing vbmeta image ( fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img ) ( OOS13 on 1+ devices may need to flash vbmeta_system too )
Click to expand...
Click to collapse
Well. Where can I find Vbmeta.img for F15 pls?

LinkinLover2013 said:
Well. Where can I find Vbmeta.img for F15 pls?
Click to expand...
Click to collapse
I used these files!

LinhBT said:
Use Oxygen Updater to download the update build! Btw, did u fix the wifi?
Click to expand...
Click to collapse
Well. I don't quite understand how to use oxygen updater to update since when I download incremental in oxygenupdater and try to install it through OPocalupdate it fails after like 20% installing same like if i try to install it through classic updater. In oxygenupdater it recommends to switch to full but when you switch to full it doesn't show incrementals, just big system updates like from OOS12.1 to OOS13.

LinkinLover2013 said:
Well. I don't quite understand how to use oxygen updater to update since when I download incremental in oxygenupdater and try to install it through OPocalupdate it fails after like 20% installing same like if i try to install it through classic updater. In oxygenupdater it recommends to switch to full but when you switch to full it doesn't show incrementals, just big system updates like from OOS12.1 to OOS13.
Click to expand...
Click to collapse
I always do the Magisk flash to Inactive slot and never failed. May be there's smt wrong from ur side?

LinhBT said:
I always do the Magisk flash to Inactive slot and never failed. May be there's smt wrong from ur side?
Click to expand...
Click to collapse
So you do it in this order: Go to magisk and select flash to inactive slot -> do OTA update through OPlocalupdate app -> restart phone? Does it have any effect to select flashing magisk to inactive slot before I start OTA udpate? Because it seems like the incremental OTA udpates can install only on unrooted phone with Stock boot.img if I leave it rooted it always stops due to error.