Problem flashing stock rom - All threads completed. (succeed 0 / failed 1) - Samsung Galaxy S8 Questions and Answers

I have an unlocked Samsung S8 (SM-G950U) and I'm unable to get Odin to flash a stock rom to it. I'm able to boot it and the current software is:
AP: G950USQS7DTB3
CP: G950USQU7DTF4
CSC G950UOYN7DTB3
When I boot into download mode, it reads: CARRIER: TMB
At this point I'm thinking this isn't an issue of Odin not being able to communicate with the phone. Odin sees it and lists the COM port as expected. I've tried multiple USB cables, USB ports (2.0), uninstalling/reinstalling Samsung drivers, tried from another PC, etc.
Here's a sample log:
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 4685 M
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried multiple firmware versions from updato and sammobile including TMB and others but they've all failed like this. I'm not sure what else to do at this point to get it back to current firmware level.
Any input or assistance you may be able to offer would be greatly appreciated.

Hi, i'm having the same issue with a Samsung S8 (SM-G950U). Did you find a solution?

I'm Having same issue with SM-G9500

Related

GT-I9505 failing boot - restarting constantly, failed system update, "no command".

GT-I9505 failing boot - restarting constantly, failed system update, "no command".
My S4 wanted to install an update: before letting it proceed I thought it would be good t backup - however after/during backup (Kies/ Smart Switch on Windows 10) something happened, and now it fails to boot:
1. get the Samsung splash screen with the model number, followed, eventually with
2. the Samsung colourful grpacis "fireworks" which stop, and then the phone Vibrates/buzzes twice, and then restarts,
3. GOTO '1' - repeating itself continuously.
I've tried recovery reboot - it appears to try to update the system but fails with "no command"
Keis had reported,
Current version: PDAJ2 / PHONEJ2 / csc:0J1 (BTU)
Latest version: PDAK2 / PHONEK2 / cscK1 (BTU)
Size: 1458 MB
Don't seem to be able to do much else (hard reset or wipe cache). I think I can get into download mode - I've no idea what happened or how to get my phone back!
Please help.
Network unlocked phone - sim on monthly with Three / Hutchinson network UK.
Download your phone's firmware from sammobile.com and use Odin to flash it.
There are various tutorials and videos that can guide you through the process.
Unless your problem is hardware related, the above should fix it.
S4 (GT-I9505 LTE) stuck in bootloop, can't boot recovery & ODIN write error.
Okay so Kies 3 and Smart Switch say that the 9505 cannot be "initialised":
Kies3 says:
"Model name: GT-1505
'GT-1505' does not support initialising. "
Smart Switch says :
"Model name: GT-19505
'GT-lg505' does not support initialising.
Please contact our service centre. "
Odin Reports:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1203)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> aboot.mbn
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I suppose this implies the wrong Flash files has been used?
The Device was bought from Three in the UK, and is the GT-I9505, however it never splash-screen the network logo or anything: Recent Verson history AFAIK has been:
I9505XXUHOE3
I9505XXUHOJ2
And then POSSIBLEY a failed update to I9505XXUHPK2
I've tried I9505XXUHOJ2_I9505BTUHOJ1_BTU, and I9505XXUHPK2_I9505BTUHPK1_BTU from sammobile - these both produce the "Complete(Write) operation failed" error, however, I used the "BTU" versions - should I be using the H3G versions?
Many thanks.
Wenger786
It sounds redundant but confirm that the model # in download mode is the gt-i9505.
The aboot.mbn file is not flashing because the file is not for your phone, you need to try a different USB cable, you need to try a different USB 2.0 port, the bootloader in the phone is newer than the bootloader in the firmware, or a combination of these items.
audit13 said:
It sounds redundant but confirm that the model # in download mode is the gt-i9505.
The aboot.mbn file is not flashing because the file is not for your phone, you need to try a different USB cable, you need to try a different USB 2.0 port, the bootloader in the phone is newer than the bootloader in the firmware, or a combination of these items.
Click to expand...
Click to collapse
Still same problems?
Hardware fault?
At this point, I would try the latest versions of the 9505 firmware for other carriers in your country. If that doesn't work, maybe a cell repair shop can flash it using something like an octopus box.

AT&T Galaxy S8 stuck in Emergency Recovery mode

Hello this is my 1st XDA post my Galaxy S8 is stuck in emergency recovery mode Odin, Smart Switch, Kies everything I've tried nothing work plz help the phone is in download mode but fails at Setup Connection
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 5945 M
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
the phone is connected and in download mode I've tried every port and cable I got also I have the latest USB drivers installed plz help any answers will be gladly appreciated
what am
Okay nvm I'm no longer in need of assistance after contacting a guy on discord not only did he help me fix the emergency recovery problem he also was able to carrier unlock the phone to work with any carrier
Hey, I have the same issue. What worked for you?

SGH-M919: No PIT Partition, Unable to boot to recovery. pls Help

Hello All,
My Device is S4 SGH M919(T-Mobile USA), Not Rooted and have been running on Lineage OS 17.1 + TWRP recovery for several months until recently when the phone started to randomly shut off mic or reboot or crash often. nandroid backup used to be my savior. In an attempt to resolve the issue, I tried to reformat the phone, install different Lineage OS versions 17.1 and 18.1 which didn't improve my situation. I then switched to Lineage recovery(which I now regret was a bad move!) which not only improvised my situation but I lost ability to perform nandroid backups since then. I have been trying to revert to TWRP recovery but am facing the several issues which are listed below. My phone is very unstable now; it boots sometimes, crashes often and most times it gets stuck trying to enter recovery. i am able to get into download mode.
Issues:
Missing/Corrupted PIT Partition
Unable to boot to Recovery
Frequent crash
Troubleshooting Attempts Performed:
Flash PIT partition file using ODIN
<ID:0/003> Added!!​<ID:0/003> Odin engine v(ID:3.1401).​<ID:0/003> File analysis..​<ID:0/003> Total Binary size: 0 M​<ID:0/003> SetupConnection..​<ID:0/003> Initialzation..​<ID:0/003> Set PIT file..​<ID:0/003> DO NOT TURN OFF TARGET!!​<ID:0/003>​<ID:0/003> Re-Partition operation failed.​<OSM> All threads completed. (succeed 0 / failed 1)​
Flash stock android via ODIN with/without PIT partition file
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2616 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flash TWRP recovery using ODIN
<ID:0/003> Added!!​<ID:0/003> Odin engine v(ID:3.1401)..​<ID:0/003> File analysis..​<ID:0/003> Total Binary size: 8 M​<ID:0/003> SetupConnection..​<ID:0/003> Initialzation..​<ID:0/003> Get PIT for mapping..​<ID:0/003>​<ID:0/003> There is no PIT partition.​<OSM> All threads completed. (succeed 0 / failed 1)​
Flash TWRP recovery + PIT file using ODIN
<ID:0/003> Added!!​<ID:0/003> Odin engine v(ID:3.1303)..​<ID:0/003> File analysis..​<ID:0/003> Total Binary size: 8 M​<ID:0/003> SetupConnection..​<ID:0/003> Initialzation..​<ID:0/003> Set PIT file..​<ID:0/003> DO NOT TURN OFF TARGET!!​<ID:0/003>​<ID:0/003> Re-Partition operation failed.​<OSM> All threads completed. (succeed 0 / failed 1)​
Checking PIT Partition using Heimdall
heimdall print-pit
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
if you appreciate this software and you would like to support future
development please consider donating:
Donate | Glass Echidna
initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
Ending session...
Rebooting device...
Releasing device interface...
Things already verified
Connecting to PC USB Port with original quality USB cable; Tried changing USB cable and the port
Installed required samsung USB drivers
tried with multiple ODIN versions which all used to work in the past
How to recover from here?
May be I am not using the correct PIT file? I tried and couldn't find many so far.
Assuming there is no physical damage to the board inside, what additional steps I could try to get back to recovery mode? I look forward for your expert suggestion/next steps here.
Thank You!
Tried taking this to a Samsung service center but as expected they denied looking into this citing the phone is too old, is no longer being supported and better buy a new phone.
I am still wondering if I can revive this phone so that I can use this to continue experimenting with custom ROM.. Any options still worth trying to revive this phone?

Cannot flash Galaxy S8+ (G955U, Verizon Snapdragon)

I am currently using a Galaxy S8+ (G955U) with Snapdragon + Verizon. The bootloader version is also v7. Every time I attempt to flash the phone, it always comes up with this.
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 23 M
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Odin detects my phone and all, and I have also successfully rooted an older Samsung phone with Odin (Galaxy S6 Edge +), but for some reason my S8+ doesn't wanna cooperate.
This has been happening to me whether its trying to flash stock firmware (current and older versions), as well as trying to flash TWRP (also current and older versions).
I have also tried multiple versions of Odin (3.12.5, 3.13 patched, 3.14.4, etc.) to no avail.
At this point I just want to know if its possible to downgrade my phone from Android 9 down to Android 7 for rooting purposes, or if there is a current existing root for Android 9 that will work with this phone (and won't produce the same error as above).

SM-T510 recovery:Error validating footer.

My tablet is currently stuck in download mode where every time i try to cancel it, it just reboots back into download mode with the error "recovery:Error validating footer. (6)", "VBMETA T510XXU5CVG2, 54266617A" This occurred while i was messing around trying to root the tablet after i had attempted to flash TWRP to the device (ver: https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html). I believe this is 2016 tab firmware and my tab is a 2019 which may be the reason its bricked, however i have attempted to flash 2 versions of what i believe to be the correct firmware, one from frija and one from samfw, with both failing in odin hanging on SetupConnection. At one point i was able to restart the tablet after these flashes with the error "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." After which i was able to flash the samfw firmware in a flash that only took 3 seconds to complete without the usual file logs.
logs:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
This allowed me to clear the error but it is back to being stuck on downloading loop.
The bootloader was unlocked prior to this issue and i believe i was on a fresh unmodified boot.img prior to TWRP flash. I have not been able to find any information that has worked in helping me fix this issue.
Product Link: https://www.amazon.com/gp/product/B07Q3T1YJS/
Frija Version: T510XXU5CVG2/T510OXM5CVG2/T510XXU5CVG2
Frija Filename: SM-T510_1_20220725192041_c4u4t0y6d6_fac.zip.enc4
samfw file: https://samfw.com/firmware/SM-T510/XAR/T510XXU5CVG2
I would appreciate any help or advice anyone can give thanks!

Categories

Resources