Develop Bugs

Tried updating to O - think I'm screwed. Help please

So - I usually apply / sideload OTA updates to upgrade my Pixel XL (Google Store, Unlocked, rooted) and they usually go just fine. But for the O upgrade, I decided it would be a good idea to do a full clean flash for the major upgrade. I downloaded the full factory image, extracted, edited the "flash-all.bat" to remove the "-w" and executed. Everything seemed to be going fine. I saw the script flash the bootloader, then the radio successfully. However, when it attempted to flash the update image, it failed with a "too many links" error. I attempted to execute that last line in the flash-all.bat manually....
fastboot update image-marlin-opr6.170623.012.zip and receive:
target didn't report max-download-size
archive does not contain "'boot.sig'
archive does not contain 'recovery.img'
error cannot load system.img from flash
Am I bricked? Any suggestions? Right now my phone is sitting on the bootloader and I have fastboot connection (it seems)...fastboot devices yields the expected return...BUT if I issue fastboot reboot-bootloader
it fails....
I don't want to try a reboot and risk not being able to get back to the bootloader...any ideas?
Thanks!

sb1893 said:
So - I usually apply / sideload OTA updates to upgrade my Pixel XL (Google Store, Unlocked, rooted) and they usually go just fine. But for the O upgrade, I decided it would be a good idea to do a full clean flash for the major upgrade. I downloaded the full factory image, extracted, edited the "flash-all.bat" to remove the "-w" and executed. Everything seemed to be going fine. I saw the script flash the bootloader, then the radio successfully. However, when it attempted to flash the update image, it failed with a "too many links" error. I attempted to execute that last line in the flash-all.bat manually....
fastboot update image-marlin-opr6.170623.012.zip and receive:
target didn't report max-download-size
archive does not contain "'boot.sig'
archive does not contain 'recovery.img'
error cannot load system.img from flash
Am I bricked? Any suggestions? Right now my phone is sitting on the bootloader and I have fastboot connection (it seems)...fastboot devices yields the expected return...BUT if I issue fastboot reboot-bootloader
it fails....
I don't want to try a reboot and risk not being able to get back to the bootloader...any ideas?
Thanks!
Click to expand...
Click to collapse
Do you have the most current adb fastboot tools?
reminds of the error i had with the old tools and nougat.

parakleet said:
Do you have the most current adb fastboot tools?
reminds of the error i had with the old tools and nougat.
Click to expand...
Click to collapse
I believe so....same tools I used to perform the August security update on Nougat...fastboot is dates 12/19/2016.
Fastboot --version returns: fastboot version 0e9850346394-android

sb1893 said:
I believe so....same tools I used to perform the August security update on Nougat...fastboot is dates 12/19/2016.
Fastboot --version returns: fastboot version 0e9850346394-android
Click to expand...
Click to collapse
So - there are more current versions...I'm downloading now...but I'm afraid that by using the older versions, I may have messed up the update. What is my best method to recover at this point?

sb1893 said:
So - there are more current versions...I'm downloading now...but I'm afraid that by using the older versions, I may have messed up the update. What is my best method to recover at this point?
Click to expand...
Click to collapse
for me once i had the newer version i just ran the update and that was that.
at worst you might be hosed from a recovery standpoint.
most likely your user data is still there and you could do a fresh install with -w to avoid wiping user data.
you are definitely not bricked
---------- Post added at 05:41 PM ---------- Previous post was at 05:39 PM ----------
https://forum.xda-developers.com/pixel-xl/how-to/guide-android-8-oreo-root-stock-rooted-t3660591
this is a superb guide for accomplishing the task

parakleet said:
for me once i had the newer version i just ran the update and that was that.
at worst you might be hosed from a recovery standpoint.
most likely your user data is still there and you could do a fresh install with -w to avoid wiping user data.
you are definitely not bricked
---------- Post added at 05:41 PM ---------- Previous post was at 05:39 PM ----------
https://forum.xda-developers.com/pixel-xl/how-to/guide-android-8-oreo-root-stock-rooted-t3660591
this is a superb guide for accomplishing the task
Click to expand...
Click to collapse
Thank you so much! Once I installed the latest ADB/Fastboot tools, I was able to rerun the flash-all.bat (without the -w) and it seems to have completed succesfully. Rebooting now - hopefully it completes. I'm sitting on the white screen / G with some sort of progress meter cycling below the G...not sure I've seen that before - but might be new to "O"....
---and the reboot just completed...Looks like I am an Android o now. Really appreciated your quick assistance. Total lifesaver.

sb1893 said:
Thank you so much! Once I installed the latest ADB/Fastboot tools, I was able to rerun the flash-all.bat (without the -w) and it seems to have completed succesfully. Rebooting now - hopefully it completes. I'm sitting on the white screen / G with some sort of progress meter cycling below the G...not sure I've seen that before - but might be new to "O"....
---and the reboot just completed...Looks like I am an Android o now. Really appreciated your quick assistance. Total lifesaver.
Click to expand...
Click to collapse
Experience builds on experience.
enjoy

I had the same "too many links" problem today as I was flashing the factory image using flash-all.bat.
I was on 7.1.2, rooted, TWRP recovery.
After getting the same problem multiple times, I changed to a different USB port on my laptop, and it worked.
Don't know why though, but no complaints.
Just adding my experience to the mix.
My next step to try would have been to update to the latest ADB/fastboot tools.

Mine wouldn't flash the image because I was getting the to many bytes error. I can flash every part of the package except the system.IMG after hours I rebooted and was on 8.0. I was on the Tmo build but the wrong baseband. I tried to flash the whole package again this morning and received the same error. My tools are updated. Anyone have any ideas? My device is fine, I just want to fix it for future flashing
Sent from my Pixel XL using Tapatalk

[guide] OTA update when rooted ( revert to non-rooted , update—>root again)

Since you are rooted, you probably found out the OTA update won’t install.
after 3 % it crashes, and no update is installed.
So this is what I did to get the latest update:
step 1: remove root access;
- reboot and hold volume down to get into fastboot mode
- connect to pc, and load original boot.img , I checked if that was the proper one by using “fastboot boot
boot.img” ( I checked if magisk was no longer installed, this was merely to find out if I used the proper boot.img, I knew
chances the update would install were slim, I tried… but no luck as expected…. )
- I connected to LMSA, to make a backup, and download the new rom.
- I went to fastboot mode again and flashed the boot by using the command “fastboot flash boot boot.img ( the “old/current” one, not the one from the downloaded new image”
“fastboot reboot”
Step 2:
so the phone booted, and I ran the update again. This time I had no issues installing it.
Step 3:
i extracted the new Boot.img from the rom downloaded by LMSA
I re patched the new boot.img with magisk, rebooted again, and and the update was complete.
this was done on the eu g8 power , for update qpe30.79.124 , but i guess this will work on all versions since the process is the same ...
for people reading this, and don’t have root / want root, just read this thread:

Confirming success with this. I downloaded the whole ZIP, extracted boot.img and used Magisk App's built-in feature to mod the boot img. Afterward, I reflashed boot partition via fastboot. Thanks, all!

Success on Sophia RETUS 80-51-5. Flashed 80-51-3 stock boot with fastboot, took update, extracted BOOT from 80-51-5, modified with Magisk and flashed the mod with fastboot. Back up and running.

I have twrp installed. Will this work?

No, I don't believe so.
3dekstron said:
I have twrp installed. Will this work?
Click to expand...
Click to collapse
As far as I know you will also have to flash the stock recovery before updating... not sure if the recovery has to match the stock rom build, like the boot.img does. You could also flash the entire latest stock rom using LMSA to update.

pjottrr said:
Since you are rooted, you probably found out the OTA update won’t install.
after 3 % it crashes, and no update is installed.
So this is what I did to get the latest update:
step 1: remove root access;
- reboot and hold volume down to get into fastboot mode
- connect to pc, and load original boot.img , I checked if that was the proper one by using “fastboot boot
boot.img” ( I checked if magisk was no longer installed, this was merely to find out if I used the proper boot.img, I knew
chances the update would install were slim, I tried… but no luck as expected…. )
- I connected to LMSA, to make a backup, and download the new rom.
- I went to fastboot mode again and flashed the boot by using the command “fastboot flash boot boot.img ( the “old/current” one, not the one from the downloaded new image”
“fastboot reboot”
Click to expand...
Click to collapse
What does this mean (from above) and what results are to be expected?
I checked if that was the proper one by using “fastboot boot
boot.img” ( I checked if magisk was no longer installed, this was merely to find out if I used the proper boot.img, I knew
chances the update would install were slim, I tried… but no luck as expected…. )
Click to expand...
Click to collapse
I'm guessing that a fail is expected since original boot.img is no longer installed (ie, rather the patched version is installed). Hopefully someone can elaborate

Also in the case of the Magisk systemless root method, will OTA announcements occur even though they can't be installed without first unrooting?

I wonder if there is not a few steps that could be cut off and streamlined this method, for example why isnt uninstalling magisk enough, since magisk restores the boot.img, also it backs up the original boot.img so instead of going through the whole LMSA thing it can be just copied to storage and flashed in fastboot, right?

TaZeR369 said:
I wonder if there is not a few steps that could be cut off and streamlined this method, for example why isnt uninstalling magisk enough, since magisk restores the boot.img, also it backs up the original boot.img so instead of going through the whole LMSA thing it can be just copied to storage and flashed in fastboot, right?
Click to expand...
Click to collapse
I just did that with a sofia retus phone on Android 11 for the new security update.
RPM31.Q1-54-13 to RPMS31.Q1-54-13-2.
1. Uninstall all Magisk modules and reboot
2. Uninstall Magisk and hit restore image
3. Uninstall Magisk completely and phone reboots
4. Accept OTA update (nervously)
5. Patch boot image with Magisk
6. Flash patched image with minimal adb and fastboot
7. Success!
this process does replace vanced youtube with factory youtube and youtube music, but it's easy to just replace them again in vanced manager.

[OP7T][Stock/Magisk] OxygenOS 11.0.0.2.HD65AA boot.img

OnePlus 7T OxygenOS 11.0.0.2.HD65AA Global boot.img
Stock:
https://srv-file9.gofile.io/download/bd96d73a-fd81-4a5b-8d71-9dd283fa44c2/boot.img
Magisk v22.0 Patched:
https://srv-store6.gofile.io/download/4c5fdaa3-b752-4ab6-88f5-0b2e08308a8e/magisk_patched-22100.img

Where can I find the global 11.0.0.2 download?

Thanks! That's exactly what I needed. I have root again!

MuddyGeek said:
Thanks! That's exactly what I needed. I have root again!
Click to expand...
Click to collapse
How did you root again, because for me since the update, I cant root anymore and the is encrypted.

LastLeg said:
Where can I find the global 11.0.0.2 download?
Click to expand...
Click to collapse
I used the OOS Updates tracker telegram channel: https://t.me/OPUpdatesTracker and pulled the full-update from there.
If you want to manipulate it on your own after that you can clone this: https://github.com/vm03/payload_dumper to decrypt the payload.bin into workable partition images. That's what I do after a major update and/or when I need to patch a boot.img manually or just need a clean copy of the current boot.img.

Thank you very much!!! You saved my day. I exported the new boot.img but I forgot to patch and already made the update.

o muerte said:
I used the OOS Updates tracker telegram channel: https://t.me/OPUpdatesTracker and pulled the full-update from there.
If you want to manipulate it on your own after that you can clone this: https://github.com/vm03/payload_dumper to decrypt the payload.bin into workable partition images. That's what I do after a major update and/or when I need to patch a boot.img manually or just need a clean copy of the current boot.img.
Click to expand...
Click to collapse
https://www.droidwin.com/extract-stock-boot-img-oneplus-oxygenos-stock-rom/
This is a nice step by step guide.

thank you i did it ok
fastboot boot magisk_patched.img
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot

Don't know what I'm missing, but booting gets stuck at the animation after fastboot flash boot magisk_patched.img. Did the same to boot_a, stuck. Did to boot_b, stuck.
To get my phone working again, had to fastboot flash boot boot.img with unpatched. Now I'm running unrooted until this gets figured out.
Even tried patching the working boot.img with Magisk to use but same issue. This morning, GPay told me no more NFC payments.
Maybe the problem is this, at the end of the log from patching boot.img:
Code:
cp: can't preserve ownership of 'busybox': Operation not permitted
cp: can't preserve ownership of 'magisk32': Operation not permitted
cp: can't preserve ownership of 'magisk64': Operation not permitted
cp: can't preserve ownership of 'magiskboot': Operation not permitted
cp: can't preserve ownership of 'magiskinit': Operation not permitted
- All done!

OGIGA said:
Don't know what I'm missing, but booting gets stuck at the animation after fastboot flash boot magisk_patched.img. Did the same to boot_a, stuck. Did to boot_b, stuck.
To get my phone working again, had to fastboot flash boot boot.img with unpatched. Now I'm running unrooted until this gets figured out.
Click to expand...
Click to collapse
same issue would rly like someone to figure this out
I used both the provided modded image and patched my own and both did not boot. only the unpatched one works
(ik people hate it when others comment like this but I want ppl to know this is an issue)

Updated to 11.0.0.2 but keep getting safetynet fails with both this patched image, as well as when I extract boot.img from payload.bin and patch it myself via Magisk.
Magisk 22.1, MagiskHide is on
basicIntegrity (-)
cstProfile (-)
evalType N/A
Tried unistalling magisk, recovering images, flushing Google Play cache, flushing Magisk cache but no dice.
Any help is appreciated.
Seem to have an issue with a new Magisk quirk after every major update, now sorry that I attempted an update to 11 so soon.

GroovyGeek said:
Updated to 11.0.0.2 but keep getting safetynet fails with both this patched image, as well as when I extract boot.img from payload.bin and patch it myself via Magisk.
Magisk 22.1, MagiskHide is on
basicIntegrity (-)
cstProfile (-)
evalType N/A
Tried unistalling magisk, recovering images, flushing Google Play cache, flushing Magisk cache but no dice.
Any help is appreciated.
Seem to have an issue with a new Magisk quirk after every major update, now sorry that I attempted an update to 11 so soon.
Click to expand...
Click to collapse
Does it say safetynet API error? Or just failed with the red prompt?

nagi_007pk said:
Does it say safetynet API error? Or just failed with the red prompt?
Click to expand...
Click to collapse
Failed with red prompt. Everything seems to work as expected, Microsoft Company Portal has not detected root yet.

GroovyGeek said:
Updated to 11.0.0.2 but keep getting safetynet fails with both this patched image, as well as when I extract boot.img from payload.bin and patch it myself via Magisk.
Magisk 22.1, MagiskHide is on
basicIntegrity (-)
cstProfile (-)
evalType N/A
Tried unistalling magisk, recovering images, flushing Google Play cache, flushing Magisk cache but no dice.
Any help is appreciated.
Seem to have an issue with a new Magisk quirk after every major update, now sorry that I attempted an update to 11 so soon.
Click to expand...
Click to collapse
Pls install canary build of Magisk, and the problem will go away

OGIGA said:
Don't know what I'm missing, but booting gets stuck at the animation after fastboot flash boot magisk_patched.img. Did the same to boot_a, stuck. Did to boot_b, stuck.
To get my phone working again, had to fastboot flash boot boot.img with unpatched. Now I'm running unrooted until this gets figured out.
Even tried patching the working boot.img with Magisk to use but same issue. This morning, GPay told me no more NFC payments.
Click to expand...
Click to collapse
An update. Found out that if I downgrade (if even possible), I would have to wipe /data. Therefore, I gave OOS11 another chance: flashed patchedboot.img, wiped /data, and it booted! Also able to Magisk root, EdXposed, and used GPay NFC twice today. Pretty happy despite the bugs.

OGIGA said:
An update. Found out that if I downgrade (if even possible), I would have to wipe /data. Therefore, I gave OOS11 another chance: flashed patchedboot.img, wiped /data, and it booted! Also able to Magisk root, EdXposed, and used GPay NFC twice today. Pretty happy despite the bugs.
Click to expand...
Click to collapse
how do you wipe /data?

thexile said:
OnePlus 7T OxygenOS 11.0.0.2.HD65AA Global boot.img
Stock:
Gofile - Free file sharing and storage platform
Gofile is a free file sharing and storage platform. You can store and share data of all types. There is no limit and everything is free.
srv-store6.gofile.io
Magisk Patched:
Gofile - Free file sharing and storage platform
Gofile is a free file sharing and storage platform. You can store and share data of all types. There is no limit and everything is free.
srv-store6.gofile.io
Click to expand...
Click to collapse
Is this compatible to HD1900 Variant?

unelx said:
Is this compatible to HD1900 Variant?
Click to expand...
Click to collapse
It is for HD1900 model.

How To Guide [GUIDE] Magisk on LineageOS

I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently done it myself to help anyone else running into trouble. I did this on a Poco F3 global version with 12.5.4 firmware.
Prerequisites:
- LineageOS recovery + LOS already installed (so you can use Magisk app to patch recovery.img)
- working adb, fastboot, and so on
- download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0
- download lineage-18.1-*-recovery-alioth.img from https://download.lineageos.org/alioth
Basing steps on https://topjohnwu.github.io/Magisk/install.html
1. Copy recovery-alioth.img to phone; I used 'adb push lineage-18.1-20211127-recovery-alioth.img /sdcard/Download/alioth.img' to do this
2. Open Magisk app and select Install for Magisk near the top
3. Use 'Select and Patch a File' method, finding and selecting the alioth.img file
4. Click LET'S GO and let it finish.
5. Retrieve the image from the phone; I used 'adb pull /sdcard/Download/magisk_patched-[random-strings].img ~/patchedboot.img'
6. Reboot phone to bootloader by running 'adb reboot bootloader'
7. Flash patched image via 'fastboot flash boot ~/patchedboot.img'
8. Reboot into system via 'fastboot reboot'
9. Proceed to installing modules.
I was able to install Magisk hide and props config and set device fingerprint to OnePlus 6T on Android 11, hiding root from almost all apps, and then pass safetynet. Any questions or input is appreciated, I hope this helps someone!

I just flashed Lineage, rebooted, set up the phone, rebooted into recovery and then flashed Magisk.apk after renaming it to Magisk.zip. After a reboot I opened the Magisk app (which was automatically installed when flashing Magisk) for the first time and it prompted me to do some additional operations. It survived an OTA update so it should keep working in the future.

The firts mentioned method does not seem to work with the new Magisk 24.1
Does anyone have a solution to this?
(Never mind ..you need to uninstall the earlier version,then it will work)

sburry said:
I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently done it myself to help anyone else running into trouble. I did this on a Poco F3 global version with 12.5.4 firmware.
Prerequisites:
- LineageOS recovery + LOS already installed (so you can use Magisk app to patch recovery.img)
- working adb, fastboot, and so on
- download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0
- download lineage-18.1-*-recovery-alioth.img from https://download.lineageos.org/alioth
Basing steps on https://topjohnwu.github.io/Magisk/install.html
1. Copy recovery-alioth.img to phone; I used 'adb push lineage-18.1-20211127-recovery-alioth.img /sdcard/Download/alioth.img' to do this
2. Open Magisk app and select Install for Magisk near the top
3. Use 'Select and Patch a File' method, finding and selecting the alioth.img file
4. Click LET'S GO and let it finish.
5. Retrieve the image from the phone; I used 'adb pull /sdcard/Download/magisk_patched-[random-strings].img ~/patchedboot.img'
6. Reboot phone to bootloader by running 'adb reboot bootloader'
7. Flash patched image via 'fastboot flash boot ~/patchedboot.img'
8. Reboot into system via 'fastboot reboot'
9. Proceed to installing modules.
I was able to install Magisk hide and props config and set device fingerprint to OnePlus 6T on Android 11, hiding root from almost all apps, and then pass safetynet. Any questions or input is appreciated, I hope this helps someone!
Click to expand...
Click to collapse
Has anyone had issues with this? Some days ago this worked fine, but now Magisk does not let me access the "Modules" tab and Zygisk is not in the options in Settings anymore. I have a POCO F3 on Android 12, set the Fingerprint to a Redmi Note 10 to pass the CTS test (which worked and still works)
Any help would be much appreciated!

ldm21 said:
Has anyone had issues with this? Some days ago this worked fine, but now Magisk does not let me access the "Modules" tab and Zygisk is not in the options in Settings anymore. I have a POCO F3 on Android 12, set the Fingerprint to a Redmi Note 10 to pass the CTS test (which worked and still works)
Any help would be much appreciated!
Click to expand...
Click to collapse
You had update yesterday I think. Your magisk is no longer there - boot image is overwritten after ota update.
Open magisk and check, it'll likely say not installed

Rstment ^m^ said:
You had update yesterday I think. Your magisk is no longer there - boot image is overwritten after ota update.
Open magisk and check, it'll likely say not installed
Click to expand...
Click to collapse
Thanks for your reply. I'm quite new at this so I'm not sure what's going on: the latest Magisk release is still v25.2 and after following again these instructions but for v25.2, I still have the same issue. What should I do to fix this?
EDIT: you're right that it does say that it's not installed, but I followed the procedure from some days ago and it doesn't seem to fix it.
Many thanks again!

ldm21 said:
Thanks for your reply. I'm quite new at this so I'm not sure what's going on: the latest Magisk release is still v25.2 and after following again these instructions but for v25.2, I still have the same issue. What should I do to fix this?
EDIT: you're right that it does say that it's not installed, but I followed the procedure from some days ago and it doesn't seem to fix it.
Many thanks again!
Click to expand...
Click to collapse
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything

Rstment ^m^ said:
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Click to expand...
Click to collapse
I think this is the equivalent of flashing the apk as zip in custom recovery, which is deprecated.
I compared the official one with the first post and I think the following is missing in the first post:
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
From:
Installation
The Magic Mask for Android
topjohnwu.github.io
Poco has a vbmeta but i never executed this step. The instructions say that it is optional but they don't specify it.
I used the first post since LOS18.1 and no problems. Since LOS19.1 updates give me bootloops so after some repair tries (and failed twrp restore) I did a fresh install and did not take the updates anymore. No idea if it has something to do with magisk or patching vbmeta. Soon gonna try to update LOS with magisk disabled.

Rstment ^m^ said:
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Click to expand...
Click to collapse
Does this still apply to LOS20 and Magisk 25.2? After doing this, do I still need to extract the patched image?

Hi,
I run the Amazing Evo-X 7.4, that comes with it`s own built in Recovery, it`s OK but i prefer Orangefox or TWRP, as these have more features than Evo-X STOCK.
I use a program called "Temporary Recovery" and is installed using FASTBOOT and a PC, it doesn`t overwrite the original Recovery, in case you need stock for OTA Updates.
Once in Temporary Recovery i can install all my goodies, including Magisk v25.2 as you would with normal recovery,
once your finished installing your programs you have the option to make either OrangeFox or TWRP (temporary recovery) permanent.
Example below:
I install Evo-X and it overwrites my permanent recovery ,
i Re-boot my F3 into Fastboot mode and connect it to my PC,
I run "RUN_TWRP-Orange Fox FIXED.bat", i then have a choice of either TWRP or OrangeFox, once installed my F3 reboots into Temporary recovery, i then make Recovery permanent, Re-install "Magisk-v25.2.apk" from with-in recovery and carry on where i left off.
If your interested and would like to try it out, you can find
"Temporary Recovery" on the Evo-X thread page 1, post 20,
I hope you find this useful

[deleted]

johnr64 said:
Hi,
I run the Amazing Evo-X 7.4, that comes with it`s own built in Recovery, it`s OK but i prefer Orangefox or TWRP, as these have more features than Evo-X STOCK.
I use a program called "Temporary Recovery" and is installed using FASTBOOT and a PC, it doesn`t overwrite the original Recovery, in case you need stock for OTA Updates.
Once in Temporary Recovery i can install all my goodies, including Magisk v25.2 as you would with normal recovery,
once your finished installing your programs you have the option to make either OrangeFox or TWRP (temporary recovery) permanent.
Example below:
I install Evo-X and it overwrites my permanent recovery ,
i Re-boot my F3 into Fastboot mode and connect it to my PC,
I run "RUN_TWRP-Orange Fox FIXED.bat", i then have a choice of either TWRP or OrangeFox, once installed my F3 reboots into Temporary recovery, i then make Recovery permanent, Re-install "Magisk-v25.2.apk" from with-in recovery and carry on where i left off.
If your interested and would like to try it out, you can find
"Temporary Recovery" on the Evo-X thread page 1, post 20,
I hope you find this useful
Click to expand...
Click to collapse
Not sure this is going to fit my particular needs. I'm looking to use LineageOS' recovery and stock, along with Magisk.
I had previously tried patching LineageOS' recovery with Magisk, pulling the patched .img to my desktop, then tried to fastboot flash boot <Magisk-patched>, but when I went to reboot to the system, it looped back to recovery, so I ended up going back a few steps to redo LOS recovery and LOS properly flashed.
At this point, I have a working LineageOS and recovery. I booted to the system, installed Magisk-v25.2, opened it, and did a direct install -which, if I remember correctly- is the temporary root I need in order to get root in whatever the next step is.
I just don't know what to do next.

dangerousnerdrays said:
Not sure this is going to fit my particular needs. I'm looking to use LineageOS' recovery and stock, along with Magisk.
I had previously tried patching LineageOS' recovery with Magisk, pulling the patched .img to my desktop, then tried to fastboot flash boot <Magisk-patched>, but when I went to reboot to the system, it looped back to recovery, so I ended up going back a few steps to redo LOS recovery and LOS properly flashed.
At this point, I have a working LineageOS and recovery. I booted to the system, installed Magisk-v25.2, opened it, and did a direct install -which, if I remember correctly- is the temporary root I need in order to get root in whatever the next step is.
I just don't know what to do next.
Click to expand...
Click to collapse
lol... flashing patched image is all you need to do
Either via adb sideloading magisk.apk or manually flashing image both will suffice.
Just look at magisk app, if it doesn't say not installed then it is working

Question Help!!!!!! Boot failure / stuck in fastboot

Need help. I used AFT to flash April - good, I rebooted and flashed magisk patched image made with stable 25.2 - good, flashed Kirisakura Raviantha Kernel v1.0.2 - good. Magisk said update to 26.1 so I did. I did direct install to update to 26.1. My P6P rebooted ok. power off and now stuck in fastboot mode showing device state= unlocked, boot slot: a, Enter reason: boot failure. I've tried to flash stock boot.img to both slots and the new april bootloader.img to both slots....the phone won't boot past fastboot screen. It won't go into recovery mode either. Please help!!!!!!!!
PS platform tools v33.0.3

jcp2 said:
Need help. I used AFT to flash April - good, I rebooted and flashed magisk patched image made with stable 25.2 - good, flashed Kirisakura Raviantha Kernel v1.0.2 - good. Magisk said update to 26.1 so I did. I did direct install to update to 26.1. My P6P rebooted ok. power off and now stuck in fastboot mode showing device state= unlocked, boot slot: a, Enter reason: boot failure. I've tried to flash stock boot.img to both slots and the new april bootloader.img to both slots....the phone won't boot past fastboot screen. It won't go into recovery mode either. Please help!!!!!!!!
PS platform tools v33.0.3
Click to expand...
Click to collapse
Try using Android Flash Tool to get back to stock.

I tried. it failed.
Flash Failed​Device failed to boot into userspace fastboot. This usually indicates that the build you are flashing does not boot. Device serial logs can be helpful to determine the root cause of the failure

jcp2 said:
I tried. it failed.
Flash Failed​Device failed to boot into userspace fastboot. This usually indicates that the build you are flashing does not boot. Device serial logs can be helpful to determine the root cause of the failure
Click to expand...
Click to collapse
Then just manually flash ROM files in fastboot

jamescable said:
Then just manually flash ROM files in fastboot
Click to expand...
Click to collapse
is there a write up somewhere with adb commands?

Use PixelFlasher and the latest full update.

AlDollaz said:
Use PixelFlasher and the latest full update.
Click to expand...
Click to collapse
tried that as well
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

I'm not sure of the commands. Fastboot flash recovery "recovery.img" , same with the other files inside the zip inside the stock rom zip file
If i ran into this issue I'd try fastboot -w and fastboot update a custom rom.

jcp2 said:
is there a write up somewhere with adb commands?
Click to expand...
Click to collapse
Most need to be flashed in fastbootd I think. So to get there, fastboot reboot fastboot. You can flash recovery( boot, dtbo and vendor boot) in regular fastboot. That should fix everything because it will fully get rid of magisk

I used AFT and forced flashed partitions / wiped (kept bootloader unlock) and it's alive again!

Simply out of curiosity - what made you update magisk? Are there "must have" features in the new release?

StanWiz said:
Simply out of curiosity - what made you update magisk? Are there "must have" features in the new release?
Click to expand...
Click to collapse
Release Magisk v26.1 · topjohnwu/Magisk
Changes from v26.0 [App] Fix crashing when revoking root permissions [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition [General] Restore module files' cont...
github.com
See for yourself, but the sepolicy and Zygisk updates I would consider "must haves". Of course, if you're still running an Android 5 device you won't be happy: Magisk 26.1 dropped Android 5 support.

Strephon Alkhalikoi said:
Release Magisk v26.1 · topjohnwu/Magisk
Changes from v26.0 [App] Fix crashing when revoking root permissions [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition [General] Restore module files' cont...
github.com
See for yourself, but the sepolicy and Zygisk updates I would consider "must haves". Of course, if you're still running an Android 5 device you won't be happy: Magisk 26.1 dropped Android 5 support.
Click to expand...
Click to collapse
I'm all for change but I don't enjoy being a guinea pig .lol
If I have an application ( magisk 25.2) that works flawlessly I will hold off a few days prior to jumping on the band wagon ( unless the new version has something I really need) - more often than not there are issues. I prefer to read about them rather than experiencing on my own skin. Hence my question.

StanWiz said:
I'm all for change but I don't enjoy being a guinea pig .lol
If I have an application ( magisk 25.2) that works flawlessly I will hold off a few days prior to jumping on the band wagon ( unless the new version has something I really need) - more often than not there are issues. I prefer to read about them rather than experiencing on my own skin. Hence my question.
Click to expand...
Click to collapse
Not everyone thinks as you do. I update as soon as a new version is released, but I also know what I'm doing.

Strephon Alkhalikoi said:
Not everyone thinks as you do. I update as soon as a new version is released, but I also know what I'm doing.
Click to expand...
Click to collapse
It's not a question of knowledge but rather the things that are beyond ones control - possibility of bugs in the code. For example look what happened recently with platform tools.

@jcp2 With all the things you flash, you should also know what that is. Then it would be much easier for you to figure it out why your device is in an unbootable state.
Magisk, Kernel, fastbootd... have one thing in common: your boot.img!
It doesn't make sense to let Magisk patch your boot.img and installing a custom kernel without Magisk installed afterwards. In that case Magisk gets overwritten.
Your fastbootd is only a binary and located in the recovery's /sbin folder. Due to the fact that your P6P is an A/B slot device, your recovery is part of the boot.img.
Flash your stock boot.img from the image-raven-BUILD_NO.zip that you'll find inside your firmware download.

I had already tried flashing stock boot image to both slots. I had to use AFT and force flash all partions. I'm up and running/ rooted. I just have to reinstall apps .

Android flash tool is by far the easiest way to go for sure. Happy you got it fixed

{Mod edit: Quoted post has been deleted. Oswald Boelcke}
6. fast boot flash
That ADB Command does nothing.
The correct command is:
fastboot flash boot boot.img if you want to flash the boot.img

{Mod edit: Quoted post has been deleted. Oswald Boelcke}
You should give us the correct command. The syntax is (see fastboot -h):
Code:
flash PARTITION [FILENAME] Flash given partition, using the image from
$ANDROID_PRODUCT_OUT if no filename is given.
you can't use "fast boot" for a binary that's called "fastboot(.exe)".