I have Samsung Galaxy M11 (SM-M115F/DS). I want to install TWRP in it. But I can't unlock the bootloader or go to download mode. I already enabled OEM Unlock. I saw on some sites that on this device I have to press both volumes up and down to go to download mode or unlock the bootloader but actually, nothing happens. It only goes to recovery mode with power and volume up. There it has a "Reboot to Bootloader" option. When I go there, I get this When I give the options to start, I return to recovery mode.

A friend of mine asked me for some help with bringing back some lost data from his phone where there was an essential piece of information in it (his little son unwaveringly deleted it). It's been years since I tried that sort of thing, but I gave it a go. I just read some people had varying degrees of success with third-party apps essentially using **MOBILedit**. I knew that, for it to have extended access to the phone's (Samsung Galaxy Z Fold4) memory, I had to set up root access for the phone. So I went to download the relevant firmware data (SMF 936B Turkey 2024-10-16 F936BXXS8GXIC, he bought the phone while on vacation in Turkey) and **Odin**. And before that, I had downloaded **Magisk**. But when I activated download mode and set **Odin** to work, it just ended with failed. And after that, whatever effort I put in to get out of download mode, it didn't work. Now I'm stuck in download mode. I need answers to two questions: 1. Does this mean I may have completely erased data from memory? 2. What should I do to fix this situation and get out of download mode?

Summary: I am unable to revert my Samsung Galaxy Note 9 or **N9600** (Snapdragon variant) to stock firmware due to an issue where Download Mode doesn’t allow flashing, and I’m receiving error messages during the flashing attempts. When I try to enter Download Mode, I only see a blue screen with a downloading icon, and no information is displayed, unlike the usual mode where information such as "Do Not Turn Off Target" is shown. I disabled the OEM Unlock option, thinking it was the culprit and that doing so would fix the errors I encountered with Odin. Unfortunately, this only made things worse, as now I’m seeing the "Custom Binary (boot) blocked by OEM Lock" message, preventing my device from booting properly. --- What happened: 1. OEM Unlocking: OEM Unlock was enabled, but I disabled it, and after a reboot, the "Custom Binary (boot) blocked by OEM Lock" message appeared, making the phone unbootable and showing the error when starting. 2. Download Mode Issue: I’ve tried using Odin to flash the stock ROM multiple times, but it fails. When I attempt to use the SamFirm tool, I get an "**MTP Fail**" message. 3. Recovery Mode: In the past, I flashed TWRP (custom recovery) for the "crownqltechn" variant from this forum: https://xdaforums.com/t/official-twrp-sm-n9600-galaxy-note-9-crownqltechn.3845536/ and installed DotOS. To remove TWRP, I flashed the stock recovery image, believing it would help resolve issues with the bootloader. Now, I have the stock Android recovery instead of TWRP. 4. Download Mode Behavior: When choosing “Reboot to Bootloader” in recovery mode, it opens Download Mode, but it looks different from when I press Bixby + Volume Down. The usual information doesn’t show up (e.g., “Do not turn off target”). It only shows the blue screen with the downloading icon. --- What I tried: Used multiple stock ROMs from different sources (SamFirm, etc.), placed the correct files in Odin as usual, but received errors during flashing. The error messages I encountered include:

threads completed, succeeded 0 / failed 1.

Additionally, I tried changing various Odin options (like "Flash Lock" and "NAND Erase"), but they made no difference. Odin just can't deliver anything to Android while in this abnormal Download Mode. However, the phone is still recognized by Odin, and the blue box appears. Tried the ADB sideload option in the stock recovery options, but realized it’s only meant for applying software updates, and I couldn't use ADB commands either (e.g., adb getprop). The phone was in sideload mode when using the "Apply Update" option from Recovery. Downloaded and installed the latest Samsung drivers (version 1.7.61.0) to ensure proper communication between my phone and the PC, but the issue persists. --- Current Status: OEM Unlock is disabled, and I can’t access Developer Options or the OS because of the "OEM Lock" message upon boot. --- Additional Info from DM: >CURRENT BINARY: Custom > >FRP Lock : OFF > >OEM LOCK : ON > >KG STATUS : Checking > >RP SWREV : B9(1,1,1,9,1) K9 S9 Other details from Download Mode include RPMB and DID. I really don't plan to use closed-source and paid software; I just want to see what options I have.

I have an Alcatel Idol 3 phone with a broken power button and a broken touchscreen. I am only able to boot into download mode by holding down the volume up and down buttons while plugging it into the charger. Is it possible to make an image of the internal memory on my phone instead of flashing it? Can QFIL do it, or is that just for writing data?

after I'm install new firmware on Samsung A52 from: https://samfw.com in Download Mode i got:

CURREMT BINARY: Samsung Official
FRP LOCK: OFF
OEM LOCK: ON(L)
KG STATUS: CHECKING (00)
WARRANTY VOID: 0x)
QUALCOMM SECURYTYBOOT: ENABLE
RP SWREV: etc
SECURE DOWNLOAD: ENABLE
HDM STATUS: NONE

KG STATUS stuck on CHECKING could it be a firmware fault? - I got SIM - I'm waiting long time - Before Installation i got status: COMPLETED

While installing LineageOS on my Samsung Galaxy Tab S6 Lite, I have ended up with a blue screen that says "An error has occurred while updating the device software." There is also a text in red in the top corner that says: "VOLTAGE Level " While looking online, it appears to me that I am supposed to use odin (or jodin3 for me, a linux user) and then flash the device firmware. However all these instructions appear to be in the Download mode, which I can not seem to be able to get to. The bootloader is unlocked but the tablet is not rooted. I can not figure out how to get into Download mode on this device. I have fastboot and heimdall installed, as well as adb however the problem is that none of these are able to get the device into download mode. In my /var/log/messages/ I get: Feb 12 09:42:04 localhost kernel: usb 3-2.3: new high-speed USB device number 97 using xhci_hcd Feb 12 09:42:09 localhost kernel: usb 3-2.3: device descriptor read/64, error -110 Feb 12 09:42:25 localhost kernel: usb 3-2.3: device descriptor read/64, error -110 Feb 12 09:42:25 localhost kernel: usb 3-2.3: new high-speed USB device number 98 using xhci_hcd Feb 12 09:42:25 localhost kernel: usb 3-2.3: device descriptor read/64, error -71 Feb 12 09:42:25 localhost kernel: usb 3-2.3: device descriptor read/64, error -71 Feb 12 09:42:25 localhost kernel: usb 3-2-port3: attempt power cycle Feb 12 09:42:26 localhost kernel: usb 3-2.3: new high-speed USB device number 99 using xhci_hcd Feb 12 09:42:26 localhost kernel: usb 3-2.3: Device not responding to setup address. Feb 12 09:42:26 localhost kernel: usb 3-2.3: Device not responding to setup address. Feb 12 09:42:26 localhost kernel: usb 3-2.3: device not accepting address 99, error -71 Feb 12 09:42:26 localhost kernel: usb 3-2.3: new high-speed USB device number 100 using xhci_hcd Feb 12 09:42:26 localhost kernel: usb 3-2.3: Device not responding to setup address. Feb 12 09:42:27 localhost kernel: usb 3-2.3: Device not responding to setup address. Feb 12 09:42:27 localhost kernel: usb 3-2.3: device not accepting address 100, error -71 Feb 12 09:42:27 localhost kernel: usb 3-2-port3: unable to enumerate USB device Any suggestions? THanks again in advance, for any and all help!

I pulled out a Samsung Galaxy S6 that has not been used in a while. **It has never been rooted or had custom software**, and it was working last time. But now it was not starting up, it got stuck at the boot animation with blinking Samsung logo. When booting in recovery mode, it said "dm-verity error", which indicates corrupt system files. I do not care about the contents, I am okay with wiping the phone. I booted in download mode and tried flashing the original software with Odin 3.14 on a Windows 10 computer. This phone is SM-G920F from Vodafone Italy. [I downloaded the newest software from SamMobile, G920FXXU6EVG1.](https://www.sammobile.com/samsung/galaxy-s6/firmware/SM-G920F/OMN/download/G920FXXU6EVG1/1676670/) Odin failed while transferring system.img and now the phone only starts up to a screen saying "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." Download mode works, but recovery mode does not. I downloaded and installed Smart Switch and tried the emergency recovery initialization. It stops, saying "This model does not support firmware upgrades and initialization." Trying to flash the software with Odin again fails at sboot.bin. With re-partition option enabled, it says Can't open the specified file (Line: 2006). With erase nand option enabled, it fails at Erase... All fails occur almost instantly. This phone has re-activation lock enabled, so flashing a custom recovery like TWRP also fails (I do not mind tripping Knox), with error "Custom Recovery Blocked By R/L". **I know the Google and Samsung account credentials** to remove the lock, but the phone needs to start up to enter them! Other things attempted in vain: * Re-installing drivers from Smart Switch * Older version of Odin (3.10) * Older version of Windows (7) * Different USB cable (works fine with other devices) * Different USB port (2.0) * Rebooting the phone between each attempt * The older software that phone was running (G920FXXU6ERF5) * The software with four files (BL, AP, CP, CSC instead of just AP) * Extracting the .pit file from the CSC file and adding it to the Pit tab in Odin * Flashing only recovery.img (extracted from the .tar.md5 file and put into a new .tar file and added to AP) * The generic Italian software (ITV instead of OMN) I even tried hijacking R/L with Hagard's tool, which claims to succeed, but the lock is still on. The only way to shut the phone off is by letting the battery run out or disconnecting it. How can the original software be flashed to this phone to get it to start up again, with or without data? Please help.

I am using a Samsung Galaxy A23. I noticed my phone's bootloader was unlocked, so I tried to lock it while in download mode. But it is stuck there and gives an error verifying vbmeta image. Please help.

My device is Samsung Galaxy S3 I9300 and I did a complete factory reset. The device is **NOT** rooted yet. It works properly. I can do all of the following with my device: * Power off using device keys. * Start in **recovery mode** and **download mode** using device keys. * device is detected properly in **normal mode** and **recovery mode** by adb when is connected to PC through a USB cable * I am able to reboot the device using adb reboot command * adb reboot recovery works well. The problem is that if I run adb reboot bootloader or adb reboot-bootloader commands, the device is booted in normal mode, NOT in **download mode**. The only way to reboot the device in **download mode** is to use the **Power + Volume Down + Home** keys

Whenever I try accessing download mode on Samsung Galaxy S20 FE, I click on reboot to bootloader but it takes me to a bootloader menu, where I get options like recovery mode, start, boot to FFBM, etc... yet, all of these options lead me into the main recovery mode menu. The phone is locked by T-Mobile and I think it may have something to do with it, I'm trying to flash the modem to unlock the phone. Any advice on how to get it unlocked?

How do I get past download mode (boot verify image load failed) on Samsung A01 (SM-S111D)?