Samsung SM-G900A stuck in Odin Mode with UDC start - Tried Everything! - AT&T Samsung Galaxy S 5

So I was rooting or flashing my phone (not really sure I'm fully qualified to do these things now) and I think while using Odin I unplugged the usb and so now my phone just says
ODIN MODE
PRODUCT NAME: SM-G900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK (KK): ON
KNOX WARRANTY: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T2, A1, A4, P1
SECURE DOWNLOAD: ENABLE
UDC START
and in the middle it says
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I've read a million threads that are all very similar but nothings worked. I've tried to use Kies 3 but it doesnt recognize my phone. I tried to go to the Firmware Upgrade and Initialization and it doesnt know my model number.
I've tried using the G900A_Downgrade_to_NCE.tar.md5 in Odin but it was a FAIL. I tried using G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5 in Odin but it was a FAIL.
I tried using the instructions from http://forum.xda-developers.com/showthread.php?t=2785363 but it is still a FAIL.
When I use Odin it says this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And my phone says:
SW REV CHECK FAIL : [aboot]Fused 4 > Binary 1
So please lay on me your awesome wisdom please. Thank you.

Only thing left to do is try flashing the stock partitions through Odin.
https://www.androidfilehost.com/?fid=95916177934554805

Hmm i'll give it a try. Thanks!

Mine stuck on samsung logo now after flashing this file any help

Related

[Q][Solved] Brick, can't flash

Hello Friends!
I have bricked my s5830i ace, while I wanted to return to stock with odin. Unfortunately I didn't check USB debugging, so I couldn't flash it.
The problem is the following:
-Usb debugging isn't checked=>Can't flash=>Can't unbrick
Please help me! If i connect the phone to the first USB, odin says: Operation(Write) failed...or something...I can't try now.
Or when I connect to the second USB, odin says: Connecting(or something like that) and stucks...
Please help me! I'm very nervous, and I don't want to bring it to service!
You're my last hope
(If you need details, I could have a look at flashing process, and messages)
Well, how did you brick it? Seems like you flashed the wrong firmware (a firmware for 5830 without the 'i')
If that's the case and odin is stuck at setting up connection, then bad luck. A jtag (if you know someone with one) or service center are your options.
I'm sad to hear that. I wanted to flash the official 2.3.6 from samfirmware. If I know well, I should use Odin 1.84, or 1.85 and the file, which I have downloaded should be under PDA section...
Does your ace still go into download mode?
If so, it might be fixed by flashing the correct firmware.
Make sure to have your firmware in your pc root (C:/) since i've read that it helps.
I've put the correct firmware (Samfirmware S5830i Hungary Telenor)...It boot into download mode without any problem. I haven't tried to put the md5 file to the root, but I will try it soon. Thanks. I hope It's a good idea.
But I think I should check USB debugging in settings, but I can't do this, because It's bricked
coda00 said:
But I think I should check USB debugging in settings, but I can't do this, because It's bricked
Click to expand...
Click to collapse
As far as I'm concerned, usb debugging doesn't matter when flashing via odin. Edit: confirmed, since in download mode the system isn't loaded, there's nothing to debug.
Most odin problems occur when using wrong firmware, wrong .ops file or filename, when drivers aren't installed, or when not running odin as admin.
Okay....nothing worked.
I've tried everything, which you've said.
Odin write me every time:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5830iXXLD3_S5830iBTULC1_S5830iXXLD2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl.bin
<ID:0/004> BcmCP.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
That's all...I tried everything...maybe my last chance is the service
OK.....news...
I've tried to remove the Rafael.Baugis kernel, and I got new message from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5830iXXLD3_S5830iBTULC1_S5830iXXLD2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response form LOKE
<ID:0/004> BcmCP.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response form LOKE
<ID:0/004> boot.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response form LOKE
<ID:0/004> system.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004>
<ID:0/004> Receive Response form LOKE
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
WOW...
Problem solved
I've found a multi package here:
http://forum.xda-developers.com/showthread.php?t=1822109
It helped me...my phone is unbricked again
And of course I've flashed the stock rom too.

S5 Active (G870A) stuck at AT&T logo

I was having issues with the WiFi on my phone so I made backups to the SD card, removed it and did a factory reset on the phone. I'm not sure what it was running at the time, but not lolipop. It now boots to AT&T logo and heats up until I pull the battery out (I've waited upwards of 30 mins). I tried flashing stock and 0F3 roms with odin and I get the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone it says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"
I've tried flashing with PIT, tried flashing the boot loader, G870AUCU1ANE4_Full_Odin, and G870A_OC5_Bootloader, to no avail. I also downloaded Samsung Kies 3 and tried to do Firmware upgrade and initialization, which also didn't work. It comes up to Firmeware emergency recovery and asks for a recovery code (which I don't have). I've also tried from recovery mode to factory data reset and also tried to flash the roms from external SD. Is there anything else I can try or something I am missing that can get this working? Any help would be greatly appreciated.

Galaxy S6 Kernel is not Seandroid Enforcing, Boot Loop and cant load original Rom

So, my galaxy S6 Tmobile is SHOWING Kernel is not Seandroid Enforcing. Custom Binary Block by FAP Lock. The phone turns off after showing that and if I plug it in a charger, it continues to restart.
After doing intensive research, many recommended I restore to original rom which I tried and I keep getting a FAIL on Odin.
I keep getting
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
and on the Phone screen it shows:
ODIN MODE
PRODUCT NAME: SW-G920T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FAP LOCK: ON
SECURE DOWNLOAD: ENABLED
KNOX WARRANTY VOID: 1 (0x0301)
RP SWREV: B:3 K:2 S:2
SW REV. CHECK FAIL. DEVICE: 3. BINARY: 1
I have tried steps and now is very frustrated. Please help
:crying::crying::crying:
Month ago, I got the same issue and need to Odin back to stock. I search and download the latest firmware and flash by Odin.
dreamzland said:
So, my galaxy S6 Tmobile is SHOWING Kernel is not Seandroid Enforcing. Custom Binary Block by FAP Lock. The phone turns off after showing that and if I plug it in a charger, it continues to restart.
After doing intensive research, many recommended I restore to original rom which I tried and I keep getting a FAIL on Odin.
I keep getting
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
and on the Phone screen it shows:
ODIN MODE
PRODUCT NAME: SW-G920T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FAP LOCK: ON
SECURE DOWNLOAD: ENABLED
KNOX WARRANTY VOID: 1 (0x0301)
RP SWREV: B:3 K:2 S:2
SW REV. CHECK FAIL. DEVICE: 3. BINARY: 1
I have tried steps and now is very frustrated. Please help
:crying::crying::crying:
Click to expand...
Click to collapse
You need to start over download the latest firmware right from sammobile.
Plug in to pc in download mode and select ap ans find the .tar file
It will work but has to be 5.1.1 you can not downgrade to 5.0.2 if you was on 5.1.1 before the mishap .
Oem lock just means you can't flash kernels and such I believe unless its selected on in developer settings .
This does not mean you can't go back to 5.1.1 stock firmware
Sent from my SM-G920F using XDA Free mobile app

AT&T NOTE 5 flash to T-Mobile Version - Secure Check FAIL: (BOOTLOADER)

Hello! I am new to XDA.
I moved carriers from AT&T to T-Mobile. I am attempting to install T-Mobile's ROM on an AT&T Galaxy Note 5 SM-N920A in order to address some issues that I have had with Wi-Fi Calling, and phone call quality. I don't want ROOT or any other customizations. Just stock T-Mobile Android 7.0. I have been attempting to use the following ROM's
N920TUVU4EQG3_N920TTMB4EQG3_N920TUVU4EQG3_HOME.tar .md5
N920TUVU4EQJ3_N920TTMB4EQJ3_N920TUVU4EQJ3_HOME.tar.md5
I am receiving the same error on the phone during the flash attempt "Secure Check Fail: (bootloader)
Running ODIN 3.12.10 as Admin
Installed Samsung USB drivers
USB Debugging is checked.
I performed the firmware swap with my Galaxy S7 with no problems. There were 4 files in the Zip when I did that process (each dropped in ODIN path's BL, AP, CP, and CSC), but I could not find these 4 for my Note5. Each time I downloaded from Updato or SamMobile there was only on "Ap" file. Is that the issue?
PHONE SCREEN TEXT:
Odin Mode
Download Speed: Fast
Product Name: SM-N920A
Current Binary: Samsung Official
System Status: Official
FAP LOCK: Off
SECURE DOWNLOAD: Enabled
Knox Warranty Void: 0
RP SWREV: B:4 K:0 S:1
Secure Check Fail: (Bootloader)
ODIN OUTPUT:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Successfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1210)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialization..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> cm.bin
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
Any Suggestions? Thanks in advance!
i have the same problem

Custom Binary blocked by FRP error for Samsung Note 4 (Tmobile)

Getting Custom binary blocked by FRP error when trying to boot my Samsung Note 4 in Recovery or Kernel mode.
I tried to flash the srock recovery rom using odin v3.09 as well as v3.12.5 and it did not work, got below error logs from odin
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910TUVU2EPJ2_N910TTMB2EPJ2_N910TUVU2EPJ2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Logs shown on my phone Download mode screen
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910T3
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: ON
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, R1, A3, P1
SECURE DOWNLOAD: ENABLE
UDC START
SECURE CHECK FAIL: aboot
[1] eMMC write fail: ABBOT
Stock Recovery rom i am using is N910TUVU2EPJ2_N910TTMB2EPJ2_N910TUVU2EPJ2_HOME.tar.md5

Categories

Resources