I am trying to flash TWRP into my Samsung Galaxy A8 (2018) based on official instructions from: https://forum.xda-developers.com/galaxy-a8-2018/samsung-galaxy-a8-2018-roms-kernels-recoveries--other-development/recovery-twrp-3-2-2-0-galaxy-a8-2018-t3818201 I have followed the instructions carefully and repeated several times. I initially tried things on linux with adb and heimdall, however heimdall was failing to flash, so I returned back to the exact Windows instructions using Odin3 v3.13.1. When I try to flash twrp-3.4.0-0-jackpotlte.img.tar into my Samsung Galaxy A8 (2018) aka SM-A530F, Odin fails consistently with this log: Added!! Odin engine v(ID:3.1301).. File analysis.. Total Binary size: 35 M SetupConnection.. Initialzation.. Get PIT for mapping.. Firmware update start.. NAND Write Start!! SingleDownload. recovery.img RQT_CLOSE !! Complete(Write) operation failed. All threads completed. (succeed 0 / failed 1) Removed!! I believe my phone is not RMM locked because I see Developer Options in my settings. I tried the process with OEM unlocking enabled and disabled in my phone Dev Options. No success yet. I googled the issue for a few hours, however people mostly report seeing RQT_CLOSE when phone is RMM locked, which I believe is not my case. Maybe this is related to the recent Android update I installed yesterday. Phone software: Android 9 Baseband version: A530FXXUECTH1 Kernel version: - 4.4.111-19323942 - #1 Mon Aug 3 15:36:52 KST 2020 Build number: PPR1.180610.011.A530FXXUECTH2 Security patch level: August 1,2020 Security software verion: - ASKS v3.1.1 Rlease 20200120 - ADP v3.0 Releasae 20191001 - SMR Aug-2020 Release 1 What does RQT_CLOSE actually mean? Could you please help investigate?

Can't complete the Stock ROM flash on my galaxy grand prime SM-G530H. The following error is shown inside the Odin message box. Added!! Odin v.3 engine (ID:10).. File analysis.. SetupConnection.. Initialzation.. Get PIT for mapping.. Firmware update start.. aboot.mbn NAND Write Start!! FAIL! (Auth) All threads completed. (succeed 0 / failed 1) I hope the problem is with the NAND Write Start!! part. I tried with three of the stock ROMs and getting the same result. What should I do to overcome this problem?

I need to know how to un-**softbrick** the Samsung Galaxy Core Prime. I don't know how it got bricked, I was just asked to fix it. It looks like a bootloop issue. The Product name is **SM-G360V**. I have already attempted flashing TWRP on it with Odin3, but it fails saying SECURE CHECK FAIL : recovery and the next line is Custom Binary(recovery) Blocked By R/L. I have no idea how to flash a custom ROM (of which I can't find) without a custom recovery.

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 some A13's I am trying to get into. They are company phones and their previous users have left the business but with pin codes and accounts still on their company phones. I am trying to get around FRP so I can reset these phones and put them to good use. What I have tried so far - Using DroidKit, however it won't recognise the phone as USB debugging on turned off (and unable to turn it on as settings hidden behind passcode) - Flashing stock firmware on to the device (Still hit the same FRP problem) Has any got any suggestions or advice? Thanks

I installed LineageOS on my Samsung M20. After installing it removed the TWRP. However, I needed TWRP to install MAGISK so I flashed the TWRP image again but this time the phone is stuck on the TWRP splash screen. It can only reboot (Power + Volume down), it isn't detected by ODIN nor can I enter download mode, therefore only the Samsung boot logo and the TWRP splash screen.

I have a Galaxy S5 (T-Mobile). I recently booted into TWRP (flashed with odin,) and attempted to flash Resurrection Remix with NikGapps using an SD card. Upon reboot RR was stuck on the loading screen, and on reboot it tried to boot to TWRP but that got stuck on the splash screen too. I tried to reflash with odin, but even in Download Mode the phone is not recognized by odin. I've tried: 1. Countless reboots 2. Unplugging and replugging, trying different cables 3. Trying to get Fastboot to work (Unsuccessful) 4. Letting TWRP load for an hour (Unsuccessful) Extra info: Every reboot redirects to the broken TWRP install, and Download Mode is still accessible from the phone. If someone could help me, that would be nice because I'm scared this phone might be bricked.

I want to change the CSC code for my Samsung Galaxy S21 Ultra for less bloatware, and Google Assistant available. The firmware I wanted to update: . My phone's current build: . I used Odin v3.13.1, but I tried multiple versions, as well as the patched one, with failure. Here is the full traceback of the error:

Odin engine v(ID:3.1301)..
 File analysis..
 Total Binary size: 12081 M
 SetupConnection..
 Initialzation..
 Set PIT file..
 DO NOT TURN OFF TARGET!!
 Get PIT for mapping..
 Firmware update start..
 NAND Write Start!!
 SingleDownload.
 abl.elf
 xbl.elf
 FAIL! (Auth)

 Complete(Write) operation failed.
 All threads completed. (succeed 0 / failed 1)

I also tried unlocking the bootloader, but it didn't work.

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.

*My original problem is at https://android.stackexchange.com/questions/214200/ . You can simply ignore my original problem since it's kinda not related to this question. Just share some backgrounds.* --- Now, I am trying a different (first stock release) ROM and hopefully, this time, it can work. After downloading this ROM, I got the following 5 files:

camera.pit
CODE_GC100XXALJF_413474_REV00_user_low_ship.tar.md5
CSC_HOME_OLB_GC100OLBALJB_409864_REV00_user_low_ship.tar.md5
CSC_OLB_GC100OLBALJB_409864_REV00_user_low_ship.tar.md5
MODEM_GC100XXALJG_REV01_CL1210642.tar.md5

I guess CODE_GC100XXALJF_413474_REV00_user_low_ship.tar.md5 is **AP** option because it has the biggest size. But just a guess. How to use them with Odin? Which one belongs to which option?

I mostly worked on Samsung phones, but I also had a shot on some cheap MTK phones. Over the course of rooting/flashing roms/flashing kernels I built myself/using Odin (Samsung)/etc. on a lot of phones, not once did I need to change any USB debugging option, except on my first try when I was still new to Android. But, once I began learning how Android works (and becoming an Android dev in the process), turning on USB debugging didn't make sense when interacting with the phone outside of Android, because as far as I know, USB debugging is only *soft*. That is, the phone hardware didn't care, but the OS requires it for debugging purposes (ADB access). So, basically, when you need to flash something in recovery mode **OR** via a tool (e.g. Odin, Heimdall), you don't need USB debugging. But, when you are talking to the OS (logcat, etc.), USB debugging makes sense. So, why do almost all of the online tutorials that I revisited **require** turning on USB debugging even though you're outside of Android? Is there something I don't know that needs it? Or are they naive and simply *followed the leader* (copy-pasted another tutorial into their own blogs)?

Samsung Galaxy A51 received an OTA update last night - installed it, auto-restarted, loaded the Samsung welcome page, then loaded a bright blue screen with:

ODIN MODE (AVB fail)
SUPER: Build-id does not match with the reference
(SUPER): 71281625R, (BOOTLOADER): 66118624

Downloading...
Do not turn off target
Do not disconnect USB cable during the software update!
Volume down key + side key for more than 7 secs : cancel (restart phone)

And a barcode in the bottom-right corner of the screen. Followed the instructions to restart (vol & side key) but just returned to the same ODIN page. Same when restarting when connected to the PC. PC says it can't recognise the USB device when it's connected. I'm not interested in using the phone again, I just want to retrieve photos and any other data from it if possible. I'm a relative novice, but I can follow instructions if anyone has a solution? Thanks!

My Samsung Tab A6 2016 (SM-T585) doesn't boot when I press the power button and volume down. I did nothing, I was using it last night like every day, but today that happened. It says > An error has occurred while updating the device software. > Use the Emergency recovery function in the Smart Switch PC software. I tried to enter download mode and flash it with Odin. I downloaded the corresponding Samsung firmware (maybe) but it fails in Odin. Sometimes Odin says the repartition operation failed, sometimes there is no PIT partition. I don't know if there's any Odin alternative or something I can do.

**The Iusse** ------------- Well, this is normally a simple task but I have a lot of problems. I hope you can help me. To begin, let's explain the situation: I have an *SM-J510FN device with firmware from Spain* to which, according to what I have been told, the unlock pattern was changed and the owner does not remember it, so he can not unlock the phone. ---------- **What I've tried** ------------------- **1:** The first thing I did was enter Recovery mode with Power + Volume Up + Home. After showing me the android icon looking for updates, I get a screen that says "Sin comandos" ("No commands") for a few seconds. Then the menu appears in which I choose "Wipe data / factory reset". When doing this, this message appears in red: E:format_volume: make ext4 failed on /dev/block/bootdevice/by-name/userdate with 1(I/O error) ---------- **2:** After this failure, I downloaded Odin3 (V3.12), Samsung drivers and a firmware from sammobile, the most updated with Android 7 for this device, which is not rooted (I say in case it has something to do with the problems ) I open Odin, I select the firmware where it says "AP", I connect the phone and start it with Power + Volume Down + Home, and the screen that says "Downloading, Do not turn off target" appears. In the log, odin says: Added!! I configure the options in this way: After a few minutes in which progress bars in Odin and on the phone are advancing, and messages appear in the log, Odin looks like this: Obviously, the phone restarts, but it does not start the system normally. Return to the Recovery menu, the same one that I entered to try de factory reset. Select "Reboot system now" and this time if it enters the system... but the same system, with the same unlock pattern. Nothing has changed. I tried to go back to the Recovery menu in case at least the error had been fixed when I tried to do the factory reset, but it was still the same, I have to say that I have tried the same with previous versions, even with Android 6 that is the one that comes from factory, but the problem is the same. ---------- **3:** I tried exactly the same as before, only adding Odin a PIT file for this device and checking the option of "Re-Partition", but the result is the same: Odin does everything he has to do without giving any error, but when it's over, the phone restarts and everything stays the same. ---------- I do not know what else I can try to restart this device. ***Any ideas?***

So I have a bricked gt-s5830i (galaxy ace) and when I try to flash it using odin I get this error: Added!! Enter CS for MD5.. Binary Check MD5.. Do not unplug the cable.. Please wait.. Checking MD5 finished Sucessfully.. Leave CS.. Odin engine v(ID:3.1100).. File analysis.. SetupConnection.. Initialzation.. Get PIT for mapping.. Firmware update start.. SingleDownload. sbl.bin NAND Write Start!! BcmCP.img FAIL! Complete(Write) operation failed. All threads completed. (succeed 0 / failed 1) Removed!! It started boot looping after it randomly got stuck and I took out the battery since I couldn't do anything at all. This is the firmware I tried: http://www.sammobile.com/firmwares/download/37194/S5830IXXLK3_S5830IDBTLK1_DBT/ http://www.sammobile.com/firmwares/download/14913/S5830ZXXLK3_S5830ZDBTLK2_DBT/ Does anyone know what's causing this? This is also the first time I'm flashing a phone. The rom was downloaded from sammobile because the ones from samsung-updates seem to have broken downloads.

for the first time ever i'v tried to root my samsung device I am running a Samsung Galaxy S10+ SM-G975F I started by making sure OEM was unlocked + USB debugging put the phone into bootloader mode and unlocked it, then i proceeded to copy the AP firmware file across from my PC to the phone, Then used The Magisk Manager app to create the patched file, Copied this back over to my PC and flashed with ODIN v3.13 After the flash was complete for the root, the video i was watching mentioned you have to boot into recovery mode from download mode, via Hold Volume Down + Power button until the device restarts Quickly Hold Volume Up + Bixby Button + Powerbutton, Until you see the bootloader warning flash then release all buttons except the Volume Up, until you boot into recovery mode. Now I'v tried absolutely everything possible combination wise Does anyone here have any solutions that may be of assistance as to me doing something incorrect? the video i followed was this one. https://www.youtube.com/watch?v=o3a8YnWT3yk I can enter Download mode still with the Key Combinations, just i'm unable to reach Recovery mode with the combinations that are explained to use Thank you.

I've been trying to flash a custom recovery and ROM to an old Galaxy Core Prime. Based on advice I received on Reddit, I decided to try using Heimdall. I put the phone into Odin Mode and connected it to the computer. I then attempted to create a PIT file for my device, in order to flash the TWRP .TAR file to it. The process started, before I received the following error message: > Downloading device's PIT file... > > ERROR: Failed to send request to end PIT file transfer! > > ERROR: Failed to download PIT file! > > Ending session... > > ERROR: Failed to send end session packet! > > Releasing device interface... I don't know what happened. What went wrong? How do I fix this issue? If needed, here are some clearer photos showing my situation:

If I boot the phone in system recovery, it doesn't detect the phone:  But when I boot the phone normally, Odin can detect it:  If I flash TWRP recovery anyway, the log is: Odin engine v(ID:3.1005).. File analysis.. SetupConnection.. and it's stuck there (which makes sense). I have unlocked OEM and USB debugging. More Information: - **Odin version:** 3 - **Phone:** Samsung J1-6 J120H

I have Samsung Galaxy S6 Edge Plus (SM-G928I). It was stuck while updating to Android 7.0. Tried ODIN, but still, it was stuck in the boot loop. So I decided to downgrade it to Android 6.0, but in ODIN, I am getting the following error: SW REV CHECK FAIL : Fused 1 > Binary 0. how do I fix this?