Database Info

[Q] Huawei Ascend G6-L11 Unlocked. Error on system img flashing.

Hi, so I got this phone about a month ago, with stock rom and filled up with bloat and unnessecary crap. So being the fundamentalist I am, I rooted this phone too (5th android phone I've had), and started playing with it.
By default, the bootloader is locked, so I unlocked it using Huawei's website unlock helper and fastboot.
I have no memory card to go with this phone, so I've had to try out the fastboot/adb way of doing this, and so far it's been a hit and miss.
I've been testing with SlimStock KK, and with Ascend G6 Mod, and I'm able to flash the boot and recovery successfully, but when it comes to flashing the system, it fails. Here's the output of that:
Code:
Karls-MBP% fastboot devices
90587873 fastboot
Karls-MBP% fastboot flash system /Volumes/ODIN/karleirik/Downloads/Firefox/Huawei_Ascend_G6-L11_Modded_B370_ROM/SYSTEM.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.039s]
sending 'system' (1048576 KB)...
ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (Undefined error: 0))
finished. total time: 26.000s
So right now my device is softbricked. Does anyone know how to get around this problem ? Or have another approach to flashing it?
Edit: I might add that I've tried different system images, and different hardware USB ports on my laptop to no avail. I have also tried the flashall, which fails due to no product ID and adb sideload <zip> fails because of a timeout:
Code:
* failed to write data 'protocol fault (couldn't read status length): Connection reset by peer' *
- Phossk

Phossk said:
Hi, so I got this phone about a month ago, with stock rom and filled up with bloat and unnessecary crap. So being the fundamentalist I am, I rooted this phone too (5th android phone I've had), and started playing with it.
By default, the bootloader is locked, so I unlocked it using Huawei's website unlock helper and fastboot.
I have no memory card to go with this phone, so I've had to try out the fastboot/adb way of doing this, and so far it's been a hit and miss.
I've been testing with SlimStock KK, and with Ascend G6 Mod, and I'm able to flash the boot and recovery successfully, but when it comes to flashing the system, it fails. Here's the output of that:
So right now my device is softbricked. Does anyone know how to get around this problem ? Or have another approach to flashing it?
Edit: I might add that I've tried different system images, and different hardware USB ports on my laptop to no avail. I have also tried the flashall, which fails due to no product ID and adb sideload <zip> fails because of a timeout:
- Phossk
Click to expand...
Click to collapse
Try putting the .zip file inside your adb and fastboot files and just type the .zip file name when flashing instead of the whole path to the .zip
Hope this will solve your problem.

My OnePlus 7 Pro is bricked.

My OnePlus 7 Pro keep booting into fastboot mode. Neither I can access recovery nor can start the phone. It's always comes back to recovery.
Please help me getting it done.
Bootloader is unlocked.

You haven't given enough info, tell us step by step how your "Bootloader is unlocked".
We would need to know if you did it properly, you probably need to go into the recovery and perform a "Full wipe". Unlocking the bootloader usually does that anyway.
The normal method is:
Enabled developer settings by pressing the version number in the about section 7 times and entering your pin
Copy the adb developer folder from the mounted OnePlus driver partition you usually get on your computer when attaching the phone, into a folder on your hard drive, and enable adb in developer settings.
In developer settings enable "OEM unlocking"
Reboot into fastboot mode
Open a command window (with admin privileges) in the folder you copied to your hard drive (In Windows, hold down shift and right click inside the folder, then click "Open Command Window..."
Run the command "fastboot oem unlock"
Accept the prompt shown on the phone
This will wipe the phone back to factory reset so ensure you have backed up your data, although you should be doing that before you even start.
Flash the appropriate TWRP recovery partition (which afaik isn't even available yet so I'm not sure why you would unlock the bootloader so soon to be honest
If you didn't perform those steps or performed them in the wrong order then you've done it wrong.
Performing a factory reset in the recovery partition may get it booting again but it's hard to know with the minimal information you've provided.
Although again, why are you unlocking the bootloader when there hasn't been a TWRP version released yet? You won't be able to flash anything, not even Magisk.

I've unlocked bootloader by command of OEM unlocking.
After than the unlock, I rebooted it's again And installed some Magisk file, which made it stuck at fastboot.
I can't access the Recovery nor can restart Phone.
All I can do is switched it off And get back into fastboot again after.

Yeah, you can't flash things with the default recovery (That's just made for flashing the default builds), that's most likely why. Magisk was made to be flashed with TWRP.
Did you use the test TWRP here? If so, then go to that thread for help.
If you can get into the OnePlus recovery you could maybe grab a build from here and flash the default rom back, then start again using the guide I showed you but, tbh, I would wait until a good TWRP build is established and Magisk is confirmed to be working.
That thread also looks like it has the default recovery image too so you can flash that back on the phone with :
fastboot flash recovery filename (Just put the recovery image into the same folder as your adb.exe and fastboot.exe
Then see if you can reboot into it and flash the stock rom back on from the same thread.

How can I get things done back, all I've is fastboot.
It's a New set, please help (

dmishra639 said:
How can I get things done back, all I've is fastboot.
It's a New set, please help (
Click to expand...
Click to collapse
If you have fastboot, I've just told you how to get the default recovery back in above.
---------- Post added at 05:45 PM ---------- Previous post was at 05:28 PM ----------
Reading that thread again, flashing recovery is not as simple as it used to be due to the A/B partition model used now, so you'll need to read the instructions shown for recovery. My guess is that you didn't read them properly and flashed the recovery to the wrong partition. If you have flashed that TWRP then you need to seek support in that thread.

It's not gonna work with me,
Even if I'll download the zip file it's only flashable with a Twrp or Stock recovery. As stock recovery is not working.
Even if I'll try to flash a Twrp recovery it's showing up an error to me :
PS C:\adb> fastboot devices
420bdc60 fastboot
PS C:\adb> fastboot boot C:\adb\recovery.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.636s
PS C:\adb> fastboot flash recovery C:\adb\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (18828 KB)...
OKAY [ 0.575s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.580s
PS C:\adb>

dmishra639 said:
It's not gonna work with me,
Even if I'll download the zip file it's only flashable with a Twrp or Stock recovery. As stock recovery is not working.
Even if I'll try to flash a Twrp recovery it's showing up an error to me :
PS C:\adb> fastboot devices
420bdc60 fastboot
PS C:\adb> fastboot boot C:\adb\recovery.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.636s
PS C:\adb> fastboot flash recovery C:\adb\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (18828 KB)...
OKAY [ 0.575s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.580s
PS C:\adb>
Click to expand...
Click to collapse
This will sound stupid, but I had similar issues with the pixel and it was due to drivers and the port. Tried from a different machine and worked. Do you have the luxury to do so ?

Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.

dmishra639 said:
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
Click to expand...
Click to collapse
Grab this fastboot rom and flash...
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424

Why are you trying to flash recovery partitions when they don't exist on this device? Recovery is on the boot partition.

dmishra639 said:
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
Click to expand...
Click to collapse
Since you are familiar with custom rom,unlocked bootloader etc you should had known already that you must NOT flash any kind Magisk staff without having proper and functional twrp.
Even if it flashed successful that doesn't mean will work after reboot and normal restart.
That why you've brick your device.
And on the other hand with A/B partition things has changed dramatically evolving all custom made staff and how they works.
Oneplus device not work the same way as Xiaomi you've described.
Sent from my iPad using Tapatalk Pro

LLStarks said:
Why are you trying to flash recovery partitions when they don't exist on this device? Recovery is on the boot partition.
Click to expand...
Click to collapse
paatha13 said:
Since you are familiar with custom rom,unlocked bootloader etc you should had known already that you must NOT flash any kind Magisk staff without having proper and functional twrp.
Even if it flashed successful that doesn't mean will work after reboot and normal restart.
That why you've brick your device.
And on the other hand with A/B partition things has changed dramatically evolving all custom made staff and how they works.
Oneplus device not work the same way as Xiaomi you've described.
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
Any post that describe exactly what changed? I havent flashed custom roms/kernels in close to two years due to OOS being satisfying enough. What I have done is fastboot into twrp and flash magisk(I believe). Will I still be able to do that with OP7 Pro?

dmishra639 said:
My OnePlus 7 Pro keep booting into fastboot mode. Neither I can access recovery nor can start the phone. It's always comes back to recovery.
Please help me getting it done.
Bootloader is unlocked.
Click to expand...
Click to collapse
I forget the command, but change the boot slot and try to reboot.

tech_head said:
I forget the command, but change the boot slot and try to reboot.
Click to expand...
Click to collapse
Fastboot flash boot C://path/to/recovery.img

SysAdmNj said:
Any post that describe exactly what changed? I havent flashed custom roms/kernels in close to two years due to OOS being satisfying enough. What I have done is fastboot into twrp and flash magisk(I believe). Will I still be able to do that with OP7 Pro?
Click to expand...
Click to collapse
You can read over here on 6T device details of how thing work with A/B partition.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
https://twrp.me/oneplus/oneplus6t.html
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Also follow this thread about 7 Pro situation and how well work over time
[RECOVERY][3.3.1-2][guacamole]Unofficial TWRP recovery for OnePlus 7 Pro(Testing)
Sent from my iPad using Tapatalk Pro

joemossjr said:
Fastboot flash boot C://path/to/recovery.img
Click to expand...
Click to collapse
Man, thank you so much
You literally made my day,
Wht I've did wrong in a flow was I had given the command: fastboot flash boot and the magisk location.
That was a stupidity, all I forgot was the command.
Now I used the same command and then used oxygen os fastboot flashable all bat file, as suggested by a member.
And here's my phone back. )
Thanks

In case, I'm completely New to OnePlus
It someone suggest me how to Root OnePlus 7 Pro normally, cuz I've to edit the build prop due to some reason.
My bootloader is unlocked but can't flash custom recovery.

dmishra639 said:
In case, I'm completely New to OnePlus
It someone suggest me how to Root OnePlus 7 Pro normally, cuz I've to edit the build prop due to some reason.
My bootloader is unlocked but can't flash custom recovery.
Click to expand...
Click to collapse
I remember when I edit the buildi prob on my v20 to be recognized as a pixel so google assistant can work and that bricked my device.

Robert235 said:
I remember when I edit the buildi prob on my v20 to be recognized as a pixel so google assistant can work and that bricked my device.
Click to expand...
Click to collapse
Man I've a 2gb daily add on (for 3 months), which will only gonna work with my previous device (Redmi note 5 pro).
So, I've to change OnePlus as Note 5 Pro as same.
I've did that tons of time on my past phone,it never did a brick TBH.

[SOLVED]Oneplus 7 stuck in fastbootmode after trying to restore a backup from TWRP

My bootloader is unlocked, I was rooted with Magisk and i had twrp recovery installed as well. A few modules were installed and i had made a backup about 3 weeks ago. Yesterday i tried restoring the backup in twrp and it seemed to restore properly without errors . When i pressed reboot in the end the phone went to the fastboot mode screen and has since been there. All i can do is turn it off and regardless of what i pick, (START, Restart Bootloader, Recovery mode) it just starts into fastboot mode. Confused as to what i should do now and why this happened in the first place. All the threads i found were only for the 7 pro so i didnt want to risk anything by following those. Please advice on what i should do.
Edit : The problem was solved by flashing the STOCK ROM for android 9 which is what i was on when the device was softbricked.

hi
Hi, download adb fastboot and twrp recovery image for guacamoleb. then open a new command prompt (CMD) in the same location and run the following commands:
Code:
fastboot flash recovery (file name of twrp that you download).img
after that by holding volume up + power reboot to twrp recovery that you just installed via adb fastboot command.
when you enter on twrp recovery, install twrp recovery zip, and magisk 19.3 zip (download and copy on phone storage first, after you enter on twrp when reboot, you can connect your phone with computer or USB that contain twrp recovery zip and magisk or copy to phone storage) after this step install twrp zip first than magisk and then reboot.
i hope i helped.
sorry for my english , is not my native language.

klediY said:
Hi, download adb fastboot and twrp recovery image for guacamoleb. then open a new command prompt (CMD) in the same location and run the following commands:
Code:
fastboot flash recovery (file name of twrp that you download).img
after that by holding volume up + power reboot to twrp recovery that you just installed via adb fastboot command.
when you enter on twrp recovery, install twrp recovery zip, and magisk 19.3 zip (download and copy on phone storage first, after you enter on twrp when reboot, you can connect your phone with computer or USB that contain twrp recovery zip and magisk or copy to phone storage) after this step install twrp zip first than magisk and then reboot.
i hope i helped.
sorry for my english , is not my native language.
Click to expand...
Click to collapse
Thank you for the reply. Unfortunately i am stuck in the very first step. After typing C:\adb\Oneplus 7>fastboot flash recovery twrp-3.3.1-1-guacamoleb.img in cmd the following happens
target reported max download size of 805306368 bytes
sending 'recovery' (56612 KB)...
OKAY [ 1.220s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.228s
I have tried using fastboot boot recovery instead in cmd. The following error comes up
cannot load 'recovery': No such file or directory.
I have checked whether the device is connected by typing in fastboot devices and it shows as connected. Any other suggestions will be helpful.

wolfsbane169 said:
Thank you for the reply. Unfortunately i am stuck in the very first step. After typing C:\adb\Oneplus 7>fastboot flash recovery twrp-3.3.1-1-guacamoleb.img in cmd the following happens
target reported max download size of 805306368 bytes
sending 'recovery' (56612 KB)...
OKAY [ 1.220s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.228s
I have tried using fastboot boot recovery instead in cmd. The following error comes up
cannot load 'recovery': No such file or directory.
I have checked whether the device is connected by typing in fastboot devices and it shows as connected. Any other suggestions will be helpful.
Click to expand...
Click to collapse
Something similar happened to me, I was on OOS 10 stable and wiping the system and data from TWRP got in fastboot mode without being possible to do anything else. The way that I solved was flashing from fastboot the OOS 10 stable posted rom here: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478 This will erase all your data but you will unbrick your phone.
One important thing, if you are on android 10 you can't flash TWRP via fasboot, maybe that's the problem you are having right now.
Hope this helps

ryupunk said:
Something similar happened to me, I was on OOS 10 stable and wiping the system and data from TWRP got in fastboot mode without being possible to do anything else. The way that I solved was flashing from fastboot the OOS 10 stable posted rom here: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478 This will erase all your data but you will unbrick your phone.
One important thing, if you are on android 10 you can't flash TWRP via fasboot, maybe that's the problem you are having right now.
Hope this helps
Click to expand...
Click to collapse
Ok so thank you for the help and you were right. Now i have an all new different problem. In a nutshell i flashed the stock ROM for android 9 while i was in android 10. I completely forgot you aren't supposed to do that. As a result i cant even access fastboot mode now. Can you please tell me how i can fix this problem?

wolfsbane169 said:
Ok so thank you for the help and you were right. Now i have an all new different problem. In a nutshell i flashed the stock ROM for android 9 while i was in android 10. I completely forgot you aren't supposed to do that. As a result i cant even access fastboot mode now. Can you please tell me how i can fix this problem?
Click to expand...
Click to collapse
I think that you will need to use the MSM tool, it looks like you have a hard brick, the good news is that oneplus devices can be revived in almost all cases. I have never used the tool but I found some posts that might help you. Best of luck!
XDA Oneplus 7 thread
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
XDA Oneplus 7 pro thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Oneplus forum guide
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/

ryupunk said:
I think that you will need to use the MSM tool, it looks like you have a hard brick, the good news is that oneplus devices can be revived in almost all cases. I have never used the tool but I found some posts that might help you. Best of luck!
XDA Oneplus 7 thread
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
XDA Oneplus 7 pro thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Oneplus forum guide
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/
Click to expand...
Click to collapse
I have tried using it but the problem is that MSM download tool does not detect my phone. i have uninstalled and let windows automatically update qualcomm drivers. I have also made windows manually install them after uninstalling.

Flash TWRP via fastboot android 10

Hello guys, as we known that it is unable to use command in fastboot to boot into TWRP if we are on Android 10 (both OOS and Custom rom) at the moment, so here is the simple command allow us to do that if you want to roll back android 9 or any rom by TWRP
fastboot flash boot_a <twrp name.img>
fastboot flash boot_b <twrp name.img>
fastboot reboot
Your phone will automatically boot into TWRP, so you can flash another rom

Can anyone confirm this works?
I tried something similar when I first installed OOS 10, and I successfully booted TWRP, but I ended up getting a bootloop (stuck at the g.co/ABH warning thing) when I rebooted to system. I don't know if I did something wrong, or flashing twrp to both boot partitions caused it.
I would try again, but I'm on a critical work trip until the end of the month, so my phone's uptime is expected to be 100% until then.

worked for me while anything else didnt

LazerH said:
worked for me while anything else didnt
Click to expand...
Click to collapse
Does it wipe your data?

Didn't work for me. My boot image was patched already this is probably why.

ok, I tried this, but as reported above, now also stuck on this same: "I tried something similar when I first installed OOS 10, and I successfully booted TWRP, but I ended up getting a bootloop (stuck at the g.co/ABH warning thing) when I rebooted to system. I don't know if I did something wrong, or flashing twrp to both boot partitions caused it."
How do I resrore operation for my phone? (help?)

Well, I met this issue before, and ended up with using this method to successfully boot into twrp.
This issue seems to appear on OOS, when I using `fastboot boot xxx.img` on other ROM like omni, I'm able to boot into twrp, thanks!

can someone help me please. my phone is stuck in a fastboot bootloop. everything I try doesn't work.
fastboot boot TWRP.img NOTHING
tried your solution above and still nothing
Still stuck in fastboot this is what I get:
PS C:\Users\Les Brown\Desktop\OnePlus 6> fastboot boot twrp-3.3.1-17-enchilada-Q-mauronofrio.img
downloading 'boot.img'...
OKAY [ 0.617s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.655s

@killathenoob Download DECRYPTED OOS 10.3.0 with this help if you don't really know what to do with this.
For others people (and you if you want to root or just install TWRP after fresh OOS10 Decrypted install) don't forget to OEM unlock before doing anything.
Download this
Copy "twrp-3.3.1-17-enchilada-installer-mauronofrio.zip" into internal storage of your OP6
Power it OFF
Power it ON in fastboot mode
Launch "Boot TWRP.bat"
Connect your OP6 to your PC and wait for TWRP to boot
Install twrp-3.3.1-17-enchilada-installer-mauronofrio.zip
Reboot to recovery and install magisk if you need to.
Source
Hope I helped a bit.

OP 7 Pro fully bricked after OOS 12 update

Hi, up until recently I had crDroid on my phone, after not touching for a while and the rom being a bit corrupt, I decided to rollback to OOS.
To do this, I used some files I had of the OOS version that was on the phone before crDroid, went into fastbootd mode through the custom recovery of the crDroid ROM and became flashing images, it's a bit janky but I only wanted to get OOS working and booting to install a fresh OTA version of OOS through the settings. I ended up using the Oxygen updater app (or something like that, got it off the playstore) to have the OOS file to copy it to my PC where I would dump the payload into a folder to get the boot image and patch it with magisk.
Everything worked perfectly, I had root, OOS was running with no apparent big problems, but I wanted to try and flash TWRP, that's when crap hit the fan.
I was a bit worried about the process because I know TWRP can behave unpredictably but after I saw some posts of users who have android 12 OOS and TWRP I decided to try.
I downloaded the TWRP image from the official website on Oneplus 7 pro, chose the version for stock rom, Europe (I am from Israel, pretty sure I need EU image), opened up fastboot, typed:
Code:
fastboot boot <image file location>
, it was sending, the phone began booting, and nothing, it didnt boot up, stuck on the loading LOGO of Oneplus, so I tried a different version.
I tried the American version, still didnt work, and then tried the custom ROM > Europe version, and the phone booted to twrp, I wanted to check everything was alright, so I rebooted from the custom recovery to system, it reboot to recovery. I wasnt so surprised, had a few issues with TWRP in the past, so I went into TWRP and did the "flash current TWRP image" thing, and the phone still wouldnt boot to system, only the custom recovery. At that point, I gave up on a custom recovery, and tried to flash the boot image again, as from what I remember usually this fixes the custom recovery problems, got a bootloop, tried flashing the Magisk patched boot image, got a bootloop, tried flashing all the images I could (not critical partitions), of the OOS I had installed on the phone and still got a bootloop.
thought that maybe I need to flash everything, flashed all the images I could of crDroid to get to its custom recovery and enter fastbootd, flashed all of the OOS images except "reserve.img" which gave me:
"fastboot flash reserve '/run/media/android/2E5CD91E5CD8E21F/Utilities/notroot/payload_dumper-win64/payload_output/reserve.img'
Invalid sparse file format at header magic
Sending sparse 'reserve' 1/11 (262124 KB) OKAY [ 8.115s]
Writing 'reserve' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed"
and Im still in a bootloop, never had a problem like this before, and I would love some help.
PS: Sorry for the long story, thought it would be essential for a real pro who would like to help me understand my poor phones situation.
Also, English isn't my first language so forgive me for a painful read.
Thanks in advance for any help.

Forgot to add, while trying to get to fastbootd, I read on the forum that you can do that with running in fastboot the following command:
fastboot reboot fastboot
after doing it the phone bootlooped again, and I got this message:
Code:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

Hello,
I think you need to use the MSMDownloadTool to entirely reset your phone and restart from a fresh phone.
You will find informations here : https://forum.xda-developers.com/t/...a-gm21ba-collection-of-unbrick-tools.3956595/

Shalom and Happy Rosh Chodesh. Hebrew is not my first language, I believe you are better at inglet than I am at ivrit.
I agree with the above post, probably your only way out now. I think it started with your usage of the custom crDroid features as I am always wary of those 'custom' features on such a finicky device (as you found) as this. Compounded when trying to flash TWRP. So many have luck, but . . . . I have flashed more phones than I can count and for me the One Plus 7 Pro just does not like not being stock.