Question soft bricked oneplus 10 pro that worked great with lineage os

Search This thread

yedashare

Member
Dec 7, 2022
11
6
I successfully flashed my European oneplus 10 pro using the instructions - see link below.

Everything worked VERY WELL, except texts/sms I could'nt receive but could send.
I spend hours and hours making it perfect.
I had the perfect phone.
So if someone wants to know how to use lineageos with full GAPS, just follow the link below.

Then being so STUPID, for no need and no reason I continued following the same instructions and tried to root the phone.
And then this disaster happened that boot is looping and I cannot run: fastboot reboot fastboot.
Meaning that I cannot repair my phone.

All I can do is push the volume down and go to recovery mode. That's all.
My PC can send fastboot commands but I cannot go to the menu where it's chinese and english and from which I could run commands to flash my phone properly back to where it was.
I don't care loosing the data and loosing so many hours of effort, but I REALLY need my phone back to work.

This is the link from this forum to the instructions that really helped me with my Oneplus 10 pro (that I bought by mistake).
LINK THAT WORKS WITH ONEPLUS 10 PRO AND LINEAGE 19.

and this is where I CRUSHED down by running this:

The rooting

get you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot

Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.

THANK YOU FOR YOUR HELP !!!
 

Savio Dantes

Member
Apr 14, 2010
22
12
The Phoenician Ruins
This should work for you
Note: You are already in FastbootD (Recovery).

Follow the steps on this site to Flash A stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool

  • Feel free to download Fastboot Enhance Tool.zip (backup location)

  • I successfully flashed my European oneplus 10 pro using the instructions - see link below.

    Everything worked VERY WELL, except texts/sms I could'nt receive but could send.
    I spend hours and hours making it perfect.
    I had the perfect phone.
    So if someone wants to know how to use lineageos with full GAPS, just follow the link below.

    Then being so STUPID, for no need and no reason I continued following the same instructions and tried to root the phone.
    And then this disaster happened that boot is looping and I cannot run: fastboot reboot fastboot.
    Meaning that I cannot repair my phone.

    All I can do is push the volume down and go to recovery mode. That's all.
    My PC can send fastboot commands but I cannot go to the menu where it's chinese and english and from which I could run commands to flash my phone properly back to where it was.
    I don't care loosing the data and loosing so many hours of effort, but I REALLY need my phone back to work.

    This is the link from this forum to the instructions that really helped me with my Oneplus 10 pro (that I bought by mistake).
    LINK THAT WORKS WITH ONEPLUS 10 PRO AND LINEAGE 19.

    and this is where I CRUSHED down by running this:

    The rooting

    get you latest magisk here
    Install it on your phone
    transfer the boot.img you extracted to your phone
    open magisk and install it on the boot.img
    the patched boot img will be in the download folder move it to your pc
    open the fastboot tools folder and open a terminal
    adb reboot bootloader fastboot flash boot magisk_patched.img
    when your booted open magisk and direct install magisk.
    than just reboot

    Modules you'll need
    BootloopSaver
    safetynet-fix
    Shamiko
    and enable zygisk in the magisk settings.

    THANK YOU FOR YOUR HELP !!!
 

yedashare

Member
Dec 7, 2022
11
6
This should work for you
Note: You are already in FastbootD (Recovery).

Follow the steps on this site to Flash A stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool

Thank you Savio, but this is my main issue, I cannot enter fastbootD.
Whether using the tool "fastboot enhance" or using the command line. I cannot reach FastboodD.
When I try to reach this using the tool, it's looping with no error log.
And when I try from CMS:
C:\Users\me\Downloads\from dumper> fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
 

Savio Dantes

Member
Apr 14, 2010
22
12
The Phoenician Ruins
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot

This list should help you navigate things a bit better:



-- Find & Validate Device Post Startup--
adb devices

-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader

-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img

-- Reboot to system --
fastboot reboot



-- Flash Recovery --
fastboot flash recovery twrp.img

-- Reboot to system --
fastboot reboot


-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery

-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
 

beatbreakee

Senior Member
Aug 10, 2015
269
329
Frisco
Samsung Galaxy S10
and this is where I CRUSHED down by running this:

The rooting

get you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
This is where your fatal mistake was.... the red line above is incorrect !

It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"

you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.

The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.

Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.

When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.

hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.

cheers
 

metrixx02

Senior Member
May 27, 2013
512
266
Izmir
OnePlus 10 Pro
  • Like
Reactions: ectoplasma22

yedashare

Member
Dec 7, 2022
11
6
This is where your fatal mistake was.... the red line above is incorrect !

It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"

you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.

The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.

Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.

When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.

hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.

cheers
Thank you, BB, for the clear explanations about respecting the structure of the partitions and not messing directly with the boot partition using a modified img.
Do I need to reach the conclusion that my phone is broken forever and there is nothing I can do to fix it?
I thought that as long as I reach the recovery mode, I can still fix it.
If you have a brilliant solution just as brilliant as your teaching, could you please help me restoring my phone to a functional state?
And BTW, it was a TRIPLE FLAW, because I had a wonderful lineageos 19 working like a charm with GAPS and I just wanted to root it for no reason.
Many thanks for your efforts.
 
  • Like
Reactions: Prant

Prant

Senior Member
Jan 23, 2017
100
67
OnePlus 7 Pro
Damn. Nice to know Lineage works well on this phone with extensive tweaking. GSI's can be pretty unstable from what I've seen, missing cell reception and the like.

Yeah, flashing that image killed the phone. I've seen some people recover by flipping their boot slot to the other one and forcing the phone to boot the stock boot there. But if you've flashed to both slots, you're most likely SOL and need a MSM flash. In which case, you could try flashing the complete stock boot image for your OOS version you were on before moving to GSI to both slots as sort of a last resort, but even then I've only seen minimal success.
 

yedashare

Member
Dec 7, 2022
11
6
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot

This list should help you navigate things a bit better:



-- Find & Validate Device Post Startup--
adb devices

-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader

-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img

-- Reboot to system --
fastboot reboot



-- Flash Recovery --
fastboot flash recovery twrp.img

-- Reboot to system --
fastboot reboot


-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery

-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
I appreciate your help a lot.
I tried all the commands you showed, but I keep going back to this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I guess it is like a computer. The BIOS move to the Master Boot Record and it moves to the operating system.
It my case, the boot record or boot loader is broken.
Someone suggested to use
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot

This list should help you navigate things a bit better:



-- Find & Validate Device Post Startup--
adb devices

-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader

-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img

-- Reboot to system --
fastboot reboot



-- Flash Recovery --
fastboot flash recovery twrp.img

-- Reboot to system --
fastboot reboot


-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery

-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
I appreciate your help a lot.
I tried all the commands you showed, but I keep going back to this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I guess it is like a computer. The BIOS move to the Master Boot Record and it moves to the operating system.
It my case, the boot record or boot loader is broken.
Someone suggested to use MSM.
I understand that MSM is no longer available.
Any other direction how I can just fix the booting process?
And this is another error I received which gets closer to the source of the problem:
FAILED (remote: 'Failed to load/authenticate boot image: Bad Buffer
 
Last edited:

TuLy2702

Member
Oct 4, 2022
35
8
why don't we get boot_debug and vendor_boot_debug images to debug and then boot into fastbootd and flash it again, why waste time researching these unrelated things.
 

yedashare

Member
Dec 7, 2022
11
6
I SAVED MY PHONE 🎉🎉🎉
BACK ONLINE
THANKS TO THIS POST:
WHICH BROUGHT ME BACK TO FASTBOOTD
AND FROM THERE I USED FASTBOOT ENHANCED AND FLASHED PAYLOAD.BIN
AND MY PHONE IS BACK EXACTLY AS IT WAS WHEN I PURCHASED IT
YES!!!!!!!!!!!!!!!!!

One of the reasons why I decided to wipe this stupid oxygen os is because they limited my notifications to 5 seconds WTF ?!!
I didn't mention that I have previously bricked my first OnePlus 10 pro completely, so much so that I received a new one from the provider.
I flashed it successfully using Lineageos 19 and brickED it again trying to root it.
Now, I'll be looking for a solution to remove this stupid f%#$%# limit for Whatsapp notification. Any suggestion?
And I'll wait for an advanced modified ROM for OnePlus 10 PRO.
That's true that it worked very well using Lineageos 19, but text/sms didn't work and I saw that ROAMING was greyed out, so I cannot say if it works or not.

A BIG THANK TO ANYBODY WHO TRIED TO HELP ME.
BOTTOM LINE, ALWAYS HELP YOURSELF FIRST AND NEVER GIVE UP.
I spent over 100 hours on this phone, and here I am back from scratch, but at least with a WORKING PHONE.
 

yedashare

Member
Dec 7, 2022
11
6
I SAVED MY PHONE 🎉🎉🎉
BACK ONLINE
THANKS TO THIS POST:
WHICH BROUGHT ME BACK TO FASTBOOTD
AND FROM THERE I USED FASTBOOT ENHANCED AND FLASHED PAYLOAD.BIN
AND MY PHONE IS BACK EXACTLY AS IT WAS WHEN I PURCHASED IT
YES!!!!!!!!!!!!!!!!!

One of the reasons why I decided to wipe this stupid oxygen os is because they limited my notifications to 5 seconds WTF ?!!
I didn't mention that I have previously bricked my first OnePlus 10 pro completely, so much so that I received a new one from the provider.
I flashed it successfully using Lineageos 19 and brickED it again trying to root it.
Now, I'll be looking for a solution to remove this stupid f%#$%# limit for Whatsapp notification. Any suggestion?
And I'll wait for an advanced modified ROM for OnePlus 10 PRO.
That's true that it worked very well using Lineageos 19, but text/sms didn't work and I saw that ROAMING was greyed out, so I cannot say if it works or not.

A BIG THANK TO ANYBODY WHO TRIED TO HELP ME.
BOTTOM LINE, ALWAYS HELP YOURSELF FIRST AND NEVER GIVE UP.
I spent over 100 hours on this phone, and here I am back from scratch, but at least with a WORKING PHONE.
THIS WAS TOO GOOD TO BE TRUE !
After I thought everything was back, I noticed that the battery stopped charging.
I flashed again Lineageos and it worked but yet the battery didn't charge.
I re run the python script but this time using another OFP and it showed successful.
And yet it successfully killed my phone. Completely dead for the second time.
Hundreds of $ and of hours for a F^&& phone.
Huge lesson to learn here about choices.
EoS
 
  • Sad
  • Angry
Reactions: aieromon and Prant

TuLy2702

Member
Oct 4, 2022
35
8
THIS WAS TOO GOOD TO BE TRUE !
After I thought everything was back, I noticed that the battery stopped charging.
I flashed again Lineageos and it worked but yet the battery didn't charge.
I re run the python script but this time using another OFP and it showed successful.
And yet it successfully killed my phone. Completely dead for the second time.
Hundreds of $ and of hours for a F^&& phone.
Huge lesson to learn here about choices.
EoS
you make me laugh 😂
 
  • Like
  • Haha
Reactions: yedashare and Prant

TuLy2702

Member
Oct 4, 2022
35
8
Damn. I think what happened is you lost your persist.img when initially flaahing the first ofp, that thing controls low level stuff like fingerprint unlock and charger cable auth I've seen on these forums. I'm not sure there's a way to get it back either outside of a MSM Flash, certainly haven't seen one here.
It's okay to spend a little money. It's very risky to do it yourself
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    I SAVED MY PHONE 🎉🎉🎉
    BACK ONLINE
    THANKS TO THIS POST:
    WHICH BROUGHT ME BACK TO FASTBOOTD
    AND FROM THERE I USED FASTBOOT ENHANCED AND FLASHED PAYLOAD.BIN
    AND MY PHONE IS BACK EXACTLY AS IT WAS WHEN I PURCHASED IT
    YES!!!!!!!!!!!!!!!!!

    One of the reasons why I decided to wipe this stupid oxygen os is because they limited my notifications to 5 seconds WTF ?!!
    I didn't mention that I have previously bricked my first OnePlus 10 pro completely, so much so that I received a new one from the provider.
    I flashed it successfully using Lineageos 19 and brickED it again trying to root it.
    Now, I'll be looking for a solution to remove this stupid f%#$%# limit for Whatsapp notification. Any suggestion?
    And I'll wait for an advanced modified ROM for OnePlus 10 PRO.
    That's true that it worked very well using Lineageos 19, but text/sms didn't work and I saw that ROAMING was greyed out, so I cannot say if it works or not.

    A BIG THANK TO ANYBODY WHO TRIED TO HELP ME.
    BOTTOM LINE, ALWAYS HELP YOURSELF FIRST AND NEVER GIVE UP.
    I spent over 100 hours on this phone, and here I am back from scratch, but at least with a WORKING PHONE.
    3
    and this is where I CRUSHED down by running this:

    The rooting

    get you latest magisk here
    Install it on your phone
    transfer the boot.img you extracted to your phone
    open magisk and install it on the boot.img
    the patched boot img will be in the download folder move it to your pc
    open the fastboot tools folder and open a terminal
    adb reboot bootloader fastboot flash boot magisk_patched.img
    when your booted open magisk and direct install magisk.
    than just reboot
    This is where your fatal mistake was.... the red line above is incorrect !

    It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"

    you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.

    The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.

    Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.

    When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.

    hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.

    cheers
    2
    THIS WAS TOO GOOD TO BE TRUE !
    After I thought everything was back, I noticed that the battery stopped charging.
    I flashed again Lineageos and it worked but yet the battery didn't charge.
    I re run the python script but this time using another OFP and it showed successful.
    And yet it successfully killed my phone. Completely dead for the second time.
    Hundreds of $ and of hours for a F^&& phone.
    Huge lesson to learn here about choices.
    EoS
    you make me laugh 😂
    1
    u can try to fix sms mms problem using this thread
    @yedashare

    @dladz maybe we can share it groups ?
    1
    This is where your fatal mistake was.... the red line above is incorrect !

    It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"

    you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.

    The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.

    Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.

    When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.

    hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.

    cheers
    Thank you, BB, for the clear explanations about respecting the structure of the partitions and not messing directly with the boot partition using a modified img.
    Do I need to reach the conclusion that my phone is broken forever and there is nothing I can do to fix it?
    I thought that as long as I reach the recovery mode, I can still fix it.
    If you have a brilliant solution just as brilliant as your teaching, could you please help me restoring my phone to a functional state?
    And BTW, it was a TRIPLE FLAW, because I had a wonderful lineageos 19 working like a charm with GAPS and I just wanted to root it for no reason.
    Many thanks for your efforts.