Develop Bugs

Phone Bricked?

I tried flashing the CWM 3.1.0.1 PURPLE bzImage directly to /dev/block/bml8 using redbend_ua. It seemed to flash I think and then the phone soft rebooted. I tried to enter the recover menu by going to ROM Manger and selecting 'reboot into recovery. Which I think was where I may have messed up beyond repair. When booting the phone now gets stuck at the Samsung logo and won't go any further. I'm guessing since i didn't use the button shortcut for endering recovery mode now every time the phone boots it tries to boot the recovery partition which is now foobared it seems. Is there any way to make the phone boot normally or am I boned?

I don't think that works for us. Power off phone and press vol down, camera, and power st the same time to get to recovery.
you are NOT bricked.
You can also go into download mode and odin back to stock if necessary.
Check out qbking77's youtube to see how.
Sent from my SPH-D700 using XDA App

I've tried using the button shortcut to get to recover mode a few times.. Never loads. Just sits there forever.. tried the download mode shortcut too but that also just sits at the samsung logo. The download mode shortcut i tried was volume down and power.

No download mode is holding 1 on the keyboard and hold power. Then u can flash something with odin or heimdale. That's your only options if u can't get to recover. If the phone boots its nit bricked.
"The greatest respect you can earn is self respect" Louie Simmons

Oh sorry I was mistaken. I did try holding 1 on the keyboard to get to the download mode. Still only shows the samsung logo. Guess i'll be going by a store in the morning.
EDIT:
Anyone know where I might have gone wrong? I downloaded the oneclick root and copied all the recovery files to /system/bin/ as the oneclick would. Set permissions for all the recover files to 0755 as the one click would. Copied redbend_ua to /data/local and the zImage for CWM 3.1.0.1 PURPLE to /data/local/tmp and ran 'redbend_ua restore /data/local/tmp/zImage /dev/block/bml8
I was fairly confident that would work but it seems I was wrong.

One click must be downloaded to your computer then extracted and run the run.bat plug your phone in and click enter. That's it. Not suposed to put files into the phone directly.
Sent from my SPH-D700 using XDA Premium App

If you are getting the Samsung logo you are doing it wrong. Turn off the phone. Pull the battery. Put the battery back in. Pull out the key board. Put your finger on the 1 key and hold it down. While holding the 1 key press and hold the power button. Download mode will appear.
And to get into recovery properly press and hold the camera button first, then add pressing and holding volume down, then add pressing and holding power button until the recovery menu appears. Order is important.

Esteway.619 said:
One click must be downloaded to your computer then extracted and run the run.bat plug your phone in and click enter. That's it. Not suposed to put files into the phone directly.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Exactly. Also, there is a flashable zip for cwm 3.1.0.1. Who gave you the idea of putting these things in files? You will need to odin to ec05 before using the oneclick root exploit. You can pm me if you want for faster responses
Sent from my Epic 4G using XDA Premium App

All the oneclick does is use adb or whatever to execute commands on the phone itself. I basically did the exact same thing except using shell on the device itself to do all the commands as at the time I didn't have a computer I could connect to to actually use the 'one click'. Also I've never been able to get the windows drivers to work.
I was actually able to get into the download mode. I then used heimdall on my linux box to flash Froyo EC05 Prerooted/ClockWorkMod v2.5.1.0 (RFS Filesystem) Odexed. NO DATA WIPE/LOSS !! using the below command.
I tried to link to the zip file I used but i can't link to outside sites yet.
Code:
./heimdall flash --cache cache.rfs --kernel zImage --recovery recovery.bin --factoryfs factoryfs.rfs --modem modem.bin
I probably didn't need to do the factoryfs or modem options.
After that I was able to easily install the clean kernel and CWM 3.1.0.1 and everything is all good now.

phaze82 said:
All the oneclick does is use adb or whatever to execute commands on the phone itself. I basically did the exact same thing except using shell on the device itself to do all the commands as at the time I didn't have a computer I could connect to to actually use the 'one click'. Also I've never been able to get the windows drivers to work.
I was actually able to get into the download mode. I then used heimdall on my linux box to flash Froyo EC05 Prerooted/ClockWorkMod v2.5.1.0 (RFS Filesystem) Odexed. NO DATA WIPE/LOSS !! using the below command.
I tried to link to the zip file I used but i can't link to outside sites yet.
Code:
./heimdall flash --cache cache.rfs --kernel zImage --recovery recovery.bin --factoryfs factoryfs.rfs --modem modem.bin
I probably didn't need to do the factoryfs or modem options.
After that I was able to easily install the clean kernel and CWM 3.1.0.1 and everything is all good now.
Click to expand...
Click to collapse
Glad you are back up and running.

kennyglass123 said:
And to get into recovery properly press and hold the camera button first, then add pressing and holding volume down, then add pressing and holding power button until the recovery menu appears. Order is important.
Click to expand...
Click to collapse
THANKS! Order is important and now I know that. I tried 3 times with the results the same... always hung at the Samsung logo.
Really appreciate the input!

[Q] PC doesn't recognize phone even in download mode (No win 8 involved)

Hi,
So 2 days ago I flashed a stock rom, then CMW 6.0.4.8 (that advanced edition), then CM11 + GAPPS found in that same thread.
Result is an only half booting gio, I can enter pin, then select a language and then it's all black except for the battery and signal indicators.
I tried flashing again with a different recovery and flashed CMW 6.0.4.5. Now I got the bluescreen which is common on that version.
No problem, just put it in download mode and odin flash it... wel, not!
I tried on at least 5 different pcs, all windows 7, with custom driver packages, with official samsung kies (2.6), with reboots and without reboots, all usb ports and different usb cables. One pc began installing drivers for MSM72xx (GOOD), but then failed saying the device was disconnected while it wasn't. On most pcs it appears in device manager under usb devices as unknown with error 43, but trying to manually install inf files for it isn't working.
So no pc sees my phone when in download mode, I can't access recovery and I can't even make it to the android homescreen.
Any ideas on how to get it working again? Cause obviously it isn't bricked, its just that by pure coincidince all roads to a working phone are blocked (only half booting android + bugged recovery + weird behaviour in download mode).
EDIT:
Maybe usefull info. The inigial stockrom I flashed (the latest you can find on sammobile.com) didn't completely boot either. It stayed in the boot animation for almost 1 hour before I turned it off. I hope there wasn't something wrong with the stock rom cause me to have a broken download mode now (though it passed odin's md5 check).
Thanks,
Stan

No problem!!!
Stannieman said:
No PC sees my phone when in download mode, I can't access recovery and I can't even make it to the android homescreen
Click to expand...
Click to collapse
1. First Flash CM11 Blindly From Existing (Blue Screened) Recovery via Following Method:
Download latest CM 11 For Gio (http://download.androidarmv6.org/_builds/gio/stable/cm-11.0.0-RC5-GT-S5660-gio.zip) to your PC, place it on c:\ drive
Boot to recovery 6.0.4.5, press
Vol. down -> Home -> Vol. down -> Vol. down -> Home
Thus you'll enter "Install zip from sideload"
Download Minimal ADB from Here:
http://forum.xda-developers.com/showthread.php?t=2317790
. Connect your phone to PC via usb. Launch adb and type
Then Type:
adb devices
you'll get an output like
12346789 sideload
this means everything's ok
now type
adb sideload c:\cm-11.0.0-RC5-GT-S5660-gio.zip
wait aproximately 5 min for the rom to be copied to phone abd flashed
the press on the phone
back -> back -> vol. down -> vol.down -> Home -> vol. down -> Home
this is wipe data/factory reset
press
now back -> back ->
Home to reboot to system
Wait for the rom to boot up
Enjoy!
Click to expand...
Click to collapse
Thanks To @belyava
Now You Can Flash any other recovery via terminal method from within the ROM :good:
BTW have you tried pressing home button after black screen with half booting ROM?

@Stannieman
The biggest problem is you flashed
Stannieman said:
CM11 + GAPPS
Click to expand...
Click to collapse
at the same time. I don't know why, but the cm11 rom and gapps have to be flashed separately: you have to boot to system after flashing the rom, make some customizations(change language, enable WiFi, etc.) and then reboot to recovery to flash gapps.
And where do all of you get these "blueish" recoveries???? use this one

Ok thanks a looooot! Going to try it as soon as I'm home.
And yes I did try pressing the home button but still no launcher.
EDIT:
Unfortunately the blind recovery method doesn't work either, still unknown device.
If I can't get it fixed before Monday I'll buy a new one and explore the world of WP8.1.

Did you try linux?
when you connect the phone to linux PC in terminal type
lsusb
it should show all usb devices
I just don't know if odin would work under linux
I just stumbeld across this post coz I am unable to access download mode nor recovery on my phone(but that's another story)
also I think when you download adb for linux you can cd to platform-tools/ and while your phone is connected in download mode type
./fastboot devices
it should pop up
these are just my ideas...

Magic happened yesterday. I'm doing an internship in a company where they develop for android. When in download mode it got immediately picked up by one of the developers' pc and we were able to flash a stock rom with odin. I guess he has some extra drivers that came with the SDK or something. For some reason my pc still doesn't see it in download mode, but at least I've got an up and running Gio again!

[Factory Images] Factory Images and Flashing tools

NOTE: FLASHING KITKAT AFTER UPDATING TO LOLLIPOP (i.e. DOWNGRADING) IS NOT SUPPORTED. YOUR DEVICE WILL GET HARD BRICKED IF YOU ATTEMPT TO DO SO
Hello Yureka Users,
The factory image (fastboot flashable zip) and debuggable boot image are now available on Cyanogen Support page.
For the convenience of the users, we have also created a package containing required tools for flashing and a one-click flashing script.
These flash tools are available for download here - ( Windows - Linux - Mac )
There are detailed step by step instructions written for each OS ( Windows - Linux - Mac )
Flashing the whole package will get your phone back to factory state and WILL WIPE all data on your phone. (Except any data on the external microSD card, if you have one).
As newer updates come out in coming months, the support page will be updated with newer factory images.
In the spirit of the community, the flash tools package, and the script are up on github, and we welcome anyone who wants to improve on the flashing scripts/tools.
Cheers,
Team YU

Steps to flash factory image (WINDOWS)
Download the factory image fastboot package from Here
Extract the contents of the fastboot package into a folder.
Download this flashing tools package from here
Extract the contents of the flashing tools zip into the same folder
To make sure, check that system.img, boot.img etc files are in the same folder as flash-all.bat, fastboot.exe etc
Connect your phone in fastboot mode, steps for which are : -
a. Power off your phone
b. Press and hold the Volume Up key
c. With the Volume Up key, connect the phone to your PC/Laptop with USB cable
d. You can let go off the Volume Up key when Fastboot Mode is displayed on the screen
Run flash-all.bat by double clicking on it.
A command window will open and flashing procedure will start
DO NOT disconnect the device during flashing procedure
The command window will close after the flashing process is over.
Disconnect the USB cable, and boot the phone normally by long pressing the Power button.
=========================================================================================================
Steps to flash factory image (LINUX)
Download the factory image fastboot package from here
Extract the contents of the fastboot package into a folder.
Download this flashing tools package from here
Extract the contents of the flashing tools zip into the same folder
To make sure, check that system.img, boot.img etc files are in the same folder as flash-all.sh, fastboot.exe etc
Connect your phone in fastboot mode, steps for which are : -
a. Power off your phone
b. Press and hold the Volume Up key
c. With the Volume Up key, connect the phone to your PC/Laptop with USB cable
d. You can let go off the Volume Up key when Fastboot Mode is displayed on the screen
Run "flash-all" by double clicking on it. (Or you can run the flash-all.sh script from a terminal)
A command window will open and flashing procedure will start
DO NOT disconnect the device during flashing procedure
The command window will close after the flashing process is over.
Disconnect the USB cable, and boot the phone normally by long pressing the Power button.
=========================================================================================================
Steps to flash factory image (MAC)
Download the factory image fastboot package from Here
Extract the contents of the fastboot package into a folder.
Download this flashing tools package from here
Extract the contents of the flashing tools zip into the same folder
To make sure, check that system.img, boot.img etc files are in the same folder as flash-all.command, fastboot.exe etc
Connect your phone in fastboot mode, steps for which are : -
a. Power off your phone
b. Press and hold the Volume Up key
c. With the Volume Up key, connect the phone to your PC/Laptop with USB cable
d. You can let go off the Volume Up key when Fastboot Mode is displayed on the screen
Run flash-all.command by double clicking on it.
A command window will open and flashing procedure will start
DO NOT disconnect the device during flashing procedure
The command window will close after the flashing process is over.
Disconnect the USB cable, and boot the phone normally by long pressing the Power button.

Add Images
Nice Post Dude.
But u should atleast add screenshots to it and/ or a video link for it on how to do

help my phone bricked
After flashing custom ROM miui on YUREKA phone is completely dead ..only
red light is shown when connected to PC without battery ...with battery phone doesn't boot up ..
no fast boot
no adb
is there any tool to flash i have stock
also have backup
plz reply fast ...phone bricked

ravurambo said:
After flashing custom ROM miui on YUREKA phone is completely dead ..only
red light is shown when connected to PC without battery ...with battery phone doesn't boot up ..
no fast boot
no adb
is there any tool to flash i have stock
also have backup
plz reply fast ...phone bricked
Click to expand...
Click to collapse
same here. let me know if you find any solution

championswimmer said:
Hello Yureka Users,
The factory image (fastboot flashable zip) and debuggable boot image are now available on Cyanogen Support page.
For the convenience of the users, we have also created a package containing required tools for flashing and a one-click flashing script.
These flash tools are available for download here - ( Windows - Linux - Mac )
There are detailed step by step instructions written for each OS ( Windows - Linux - Mac )
Flashing the whole package will get your phone back to factory state and WILL WIPE all data on your phone. (Except any data on the external microSD card, if you have one).
As newer updates come out in coming months, the support page will be updated with newer factory images.
In the spirit of the community, the flash tools package, and the script are up on github, and we welcome anyone who wants to improve on the flashing scripts/tools.
Cheers,
Team YU
Click to expand...
Click to collapse
if i will flash this. will i revert back to stock recovery and locked bootloader ?
i come to know that lolipop update will be flashable only on stock recovery. is it true ?

does this method apply to fastboot files of cm12 as well?
Cause many users who directly flashed this cm12 fastboot files are now having hard bricked devices

championswimmer said:
Steps to flash factory image (WINDOWS)
Download the factory image fastboot package from Here
Extract the contents of the fastboot package into a folder.
Download this flashing tools package from here
Extract the contents of the flashing tools zip into the same folder
To make sure, check that system.img, boot.img etc files are in the same folder as flash-all.bat, fastboot.exe etc
Connect your phone in fastboot mode, steps for which are : -
a. Power off your phone
b. Press and hold the Volume Up key
c. With the Volume Up key, connect the phone to your PC/Laptop with USB cable
d. You can let go off the Volume Up key when Fastboot Mode is displayed on the screen
Run flash-all.bat by double clicking on it.
A command window will open and flashing procedure will start
DO NOT disconnect the device during flashing procedure
The command window will close after the flashing process is over.
Disconnect the USB cable, and boot the phone normally by long pressing the Power button.
=========================================================================================================
Steps to flash factory image (LINUX)
Download the factory image fastboot package from here
Extract the contents of the fastboot package into a folder.
Download this flashing tools package from here
Extract the contents of the flashing tools zip into the same folder
To make sure, check that system.img, boot.img etc files are in the same folder as flash-all.sh, fastboot.exe etc
Connect your phone in fastboot mode, steps for which are : -
a. Power off your phone
b. Press and hold the Volume Up key
c. With the Volume Up key, connect the phone to your PC/Laptop with USB cable
d. You can let go off the Volume Up key when Fastboot Mode is displayed on the screen
Run "flash-all" by double clicking on it. (Or you can run the flash-all.sh script from a terminal)
A command window will open and flashing procedure will start
DO NOT disconnect the device during flashing procedure
The command window will close after the flashing process is over.
Disconnect the USB cable, and boot the phone normally by long pressing the Power button.
=========================================================================================================
Steps to flash factory image (MAC)
Download the factory image fastboot package from Here
Extract the contents of the fastboot package into a folder.
Download this flashing tools package from here
Extract the contents of the flashing tools zip into the same folder
To make sure, check that system.img, boot.img etc files are in the same folder as flash-all.command, fastboot.exe etc
Connect your phone in fastboot mode, steps for which are : -
a. Power off your phone
b. Press and hold the Volume Up key
c. With the Volume Up key, connect the phone to your PC/Laptop with USB cable
d. You can let go off the Volume Up key when Fastboot Mode is displayed on the screen
Run flash-all.command by double clicking on it.
A command window will open and flashing procedure will start
DO NOT disconnect the device during flashing procedure
The command window will close after the flashing process is over.
Disconnect the USB cable, and boot the phone normally by long pressing the Power button.
Click to expand...
Click to collapse
@championswimmer Does this factory images contain twrp recovery and rooting? This is for 64 bit ryt? I am newbie for yu world coz i was a xperia user...plz help me I want to unlock my bootloader and root my yuereka...I am on cm 12 official installed via cm recovery...

Yureka hard brick
ravurambo said:
After flashing custom ROM miui on YUREKA phone is completely dead ..only
red light is shown when connected to PC without battery ...with battery phone doesn't boot up ..
no fast boot
no adb
is there any tool to flash i have stock
also have backup
plz reply fast ...phone bricked
Click to expand...
Click to collapse
Is Now ur phone ok...?

Kapiljhajhria said:
same here. let me know if you find any solution
Click to expand...
Click to collapse
facing the same problem after flashing the stock rom with fastboot only red led notification with out battery help me some one

kewalj2646 said:
facing the same problem after flashing the stock rom with fastboot only red led notification with out battery help me some one
Click to expand...
Click to collapse
Most probably your device is bricked. But no worried since its YU device you can get replacement. just call their CC.
Mine was bricked as well so i asked for replacement and they gave me one.

Pls post the Linux flashtools link as it is not working.

my yu yureka is also hard bricked no yu logo, plz if nayone can give me quick solution

Does this steps works or not ??

installation aborted
I got cm12 update few days ago.BT I can't install it
Check it out and solve it. https://youtu.be/BUVVj2aE5Jw

The link to get flash tool is not working, please provide the alternative link

any1 figured out the red light and hard bricked mine is also bricked since dec!

ashish_zarekar said:
if i will flash this. will i revert back to stock recovery and locked bootloader ?
i come to know that lolipop update will be flashable only on stock recovery. is it true ?
Click to expand...
Click to collapse
i am flashing cm12.1 after i got into bootloop. it has been very long since the flash has started. idk what to do. pls help immediately

Allen_Abraham said:
i am flashing cm12.1 after i got into bootloop. it has been very long since the flash has started. idk what to do. pls help immediately
Click to expand...
Click to collapse
do you still need help?
what is your problem

ashish_zarekar said:
do you still need help?
what is your problem
Click to expand...
Click to collapse
No bro, I fixed it. I just relaxed the ROM. ?

P6 bricked? Stuck on Huawei logo

Hello,
my problem is after trying to revert back to the stock rom I messed things up and I can't get back to fastboot mode.
But I will describe what I did. First thing I did many weeks ago was the installation of cyanogenmod 11 KitKat on the P6.
All worked fine except for the high power consumption. Because of that I decided to switch back to the stock rom.
To do that I have made the following steps.
1. I downloaded the Jelly Bean firmware from the official huawei website. (I can't post the link since I'm a new user)
2. I used the download extractor to extract boot.img and recovery.img
3. I flashed them via fastboot
4. I prepared a SD card with the update.app in the dload folder
5. booted the phone with volume buttons pressed. Update process started but failed. There was no error message only a huge FAIL message.
6. After that I switched back to TWRP recovery what worked fine
7. I build a flashable zip file with the update extractor of boot.img, recovery.img, system.img, cust.img, userdata.img and flashed it via TWRP
8. Than I realised that I mistakenly included the recovery.img which overwrote the TWRP recovery
Now the phone always starts to the huawei logo also when starting with volume buttons pressed. I can't access the fastboot mode anymore.
When shutting it down it reboots instantly.
My questions are the following.
* Can a corrupted recovery block the access of the fastboot mode or any mode to access the phone via USB to flash a new recovery?
* Are there other ways to reset the phone?
* Was it a problem to take a Jelly Bean stock rom after a KitKat installation?
* If the phone is bricked, do you have any suggestion what to do with it? Is it worthless now? Sell on ebay? Hope this is not necessary.
Thank you so much!

numbi said:
Hello,
my problem is after trying to revert back to the stock rom I messed things up and I can't get back to fastboot mode.
But I will describe what I did. First thing I did many weeks ago was the installation of cyanogenmod 11 KitKat on the P6.
All worked fine except for the high power consumption. Because of that I decided to switch back to the stock rom.
To do that I have made the following steps.
1. I downloaded the Jelly Bean firmware from the official huawei website. (I can't post the link since I'm a new user)
2. I used the download extractor to extract boot.img and recovery.img
3. I flashed them via fastboot
4. I prepared a SD card with the update.app in the dload folder
5. booted the phone with volume buttons pressed. Update process started but failed. There was no error message only a huge FAIL message.
6. After that I switched back to TWRP recovery what worked fine
7. I build a flashable zip file with the update extractor of boot.img, recovery.img, system.img, cust.img, userdata.img and flashed it via TWRP
8. Than I realised that I mistakenly included the recovery.img which overwrote the TWRP recovery
Now the phone always starts to the huawei logo also when starting with volume buttons pressed. I can't access the fastboot mode anymore.
When shutting it down it reboots instantly.
My questions are the following.
* Can a corrupted recovery block the access of the fastboot mode or any mode to access the phone via USB to flash a new recovery?
* Are there other ways to reset the phone?
* Was it a problem to take a Jelly Bean stock rom after a KitKat installation?
* If the phone is bricked, do you have any suggestion what to do with it? Is it worthless now? Sell on ebay? Hope this is not necessary.
Thank you so much!
Click to expand...
Click to collapse
When you say its bricked does that mean that it gets stuck on huawei ascend logo? If thats the case than you should be ablr to enter fastbboot since thats the sign you are in bootloader mode.
Sent from my P6-U06

tileeq said:
When you say its bricked does that mean that it gets stuck on huawei ascend logo? If thats the case than you should be ablr to enter fastbboot since thats the sign you are in bootloader mode.
Sent from my P6-U06
Click to expand...
Click to collapse
Well that is what I thought too, but I can't get a connection via adb or fastboot.
"adb devices" lists nothing. When connecting the phone via usb to the computer there is no log entry generated on the computer like it's the case with other usb devices.
I tried different usb cables. I'm unsure how to be really sure whether I'm in fastboot mode or not.
Before flashing the zip everything worked fine so it's very unlikely to be a driver issue or something related to the computer I think.

i have the same problem and i cant communicate with the device in any way but what happen to me that i download a wrong recovery img.
if someone can help please

i fix my phone and get it back to the stock recovery ::victory:

Can you please share how you make it? I have the same problem...

I fixed it by replacing the motherboard using a very detailed tutorial on ifixit.
The P6 is not build to be repaired by the customer but with the right tools it was ok.

skyhew said:
Can you please share how you make it? I have the same problem...
Click to expand...
Click to collapse
I turn the phone in the debug mode and flash the stock recovery back you enter the debug mode by press and hold on the volume down then after it the power for 10 sec. after you plug the phone to the computer via usb then download this file: 4shared.com/rar/9HO06Lpjba/p6_stock_recovery.html
and then unzip the file then open by order
1- adb-windows if you have windows
2- fastboot-windows
3- install-recovery-windows
and restart the phone and you have the stock recovery back

Samsung S20 Exynos boot looped due to wrong version of dtbo.img

Hi,
I have a global variant of S20 with Exynos chipset running rooted stock Android 10 with G980FXXS2ATE7 firmware.
Root was done with Magisk and it was properly working.
I installed a Magisk extension that caused the initial boot loop, but Recovery and Download mode was working. I was trying to install TWRP but that failed to load with some DTBO related problems. So I restored the stock recovery for Android 10 and then choose to flash the Android 11 version of dtbo alone without any additional files from that package, because I was hoping that it would make TWRP work. So I have a combination of stock files for Android 10 + corresponding rooted bootloader and stock recovery + Android 11 version of DTBO.
This was a big mistake, as since the device is rebooting every 30 sec. It only shows that the bootloader was unlocked and afterwards the "Samsung Galaxy S20 secured by Knox" screen. It stays here for a while and then reboots automatically.
Download mode and recovery are inaccessible. They simply do not appear, not with any key combination via which they worked earlier.
If I plug the phone into my laptop, there is absolutely no USB traffic, it is not recognized as a device.
Odin does not see the device either (as there is no USB device recognized by the OS).
The only thing I can do else is if I hold the Vol down + power button for a while and then plug in the charger when the screen goes dark, then the charging logo appears without showing the percentage of the battery. I stays there even if the unplug the charger. When touching the buttons, it goes back to the boot loop.
I have not found a way to power down the phone, even pressing and holding any combination of Vol up, Vol down and Power buttons.
I think the problem is that neither Recover nor Download mode can boot and this is because of the wrong DTBO file that I flashed.
Do you have any idea how I could repair and reflash the working DTBO file matching the firmware on the device under these circumstances?
Is there any trick for Exynos to boot from the SD Card like there is something for Qualcomm based phones?
Or any other way via which I could trigger some activity on USB?
Thanks for any suggestion

Try launching fastboot devices while holding fastboot keys.

Thanks for the suggestion!
I solved the problem finally.
It is strange, but recovery and download mode started to work with the hardware buttons after I removed the SD Card from the phone. I do not know how this is related, but afterwards I could flash with Odin and after reflashing the original firmware and the the usual vbmeta zip, the phone booted up properly.
Afterwards, I could reflash the magisk patched bootloader and regained root access as well.