Database Develop

[Q] Stuck in Odin Mode and have tried everything

Hello,
Ok so I have an issue and have been searching and trying different options all day. I was rooted on MI9 with safestrap installed booted into Rom slot1 with Xnote flashed. For some reason I don't understand, I reset both stock rom and rom slot 1 (wiped data). After I restarted the phone, it was stuck with the Galaxy Note 3 logo and Custom padlock. After researching, I tried to flash stock MI9 using odin. This is the message I kept getting:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N900AUCUBMI9_1625098_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now when I restart the phone, it goes to Odin mode where it says to use Kies to fix the firmware issue. Of Course, Kies didn't recognize it. It will boot into downloader mode but not recovery mode. I now uninstalled Kies and tied to flash stock many times using just the AP button. The whole time getting the same message. I can't think of anything else to try. All I want to do is go to a firmware (I don't care what) stock and unrooted.
I see this popping up on the threads but have not been able to get back to normal. This sucks! Cann anyone please help me?

I have tried MI9 one click and it says "MD5 hash value is invalid"...Now when I do get into download mode it says:
ODIN MODE
PRODUCT NAME: SM-N900A
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION: Enable
<android icon>
Downloading...
Do not turn off target.
When it is in normal mode, it shows the above but asks to hook up to Kies for a firmware issue.

Arty Dodger said:
I have tried MI9 one click and it says "MD5 hash value is invalid"...Now when I do get into download mode it says:
ODIN MODE
PRODUCT NAME: SM-N900A
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION: Enable
<android icon>
Downloading...
Do not turn off target.
When it is in normal mode, it shows the above but asks to hook up to Kies for a firmware issue.
Click to expand...
Click to collapse
Are you sure you're on mi9? Looks like youre on mj5 already looking at your dl mode. If you are on mj5 you cant use kies to load up mi9 we cant downgrade bootloader.

This may or may not help you.
I recently worked on a friends AT&T S4 (locked bootloader like our Note 3). It was doing the same thing you describe. Once it got to System.img it seemed stuck. Then would fail. I was then on the screen that said use Kies. I tried 3 times to flash without luck but I noticed that each time it made a little more progress. I changed usb cables the 4th or 5th flash and it finally went through and completed the Odin flash. So I would say keep trying to flash, change USB and see if it gets a little farther each time.
Good luck

Haitian said:
This may or may not help you.
I recently worked on a friends AT&T S4 (locked bootloader like our Note 3). It was doing the same thing you describe. Once it got to System.img it seemed stuck. Then would fail. I was then on the screen that said use Kies. I tried 3 times to flash without luck but I noticed that each time it made a little more progress. I changed usb cables the 4th or 5th flash and it finally went through and completed the Odin flash. So I would say keep trying to flash, change USB and see if it gets a little farther each time.
Good luck
Click to expand...
Click to collapse
I was able to get it fixed by following http://forum.xda-developers.com/showthread.php?t=2559715. I was on MJ5, but I thought I was on MI9. I felt pretty dumb when I figured it out. I freaked out all day and when I got home, tried that and it worked, but you have to complete all the steps. If you just leave it at Flashing MJ5 it will be very buggy and will not work that great.
I feel so much better now! Thanks guys!

Tried to root 5.0.2 with 5.1.1 guide - softbricked it [SOLVED]

Hello!
Ok, I'll admit I didn't read closely enough in my haste to root my new phone, and now it's softbricked. My phone was brand new and still on the 5.0.2 firmware, and I tried to follow the guide at link here on XDA before updating to 5.1.1. After flashing the sboot.bin, it rebooted, but stuck at the Samsung logo screen with some green text at the top of the screen:
ASV TBL VER = 15
ASV TBL VER2 = 1285
ASV big:10 LITTLE:10 630:11 MIF:10 INT:10 CAM_DISP:10 (I think that's right, it's very tiny!)
I've been stuck there ever since! I can get into download mode, but that's it.
I'm not sure what to do now. I've tried reflashing the sboot.bin file, and I've tried flashing the 5.1.1 stock (COF8) ROM (which fails!)
Am I correct in thinking that the sboot.bin file will only boot 5.1.1 roms? If so, how do I get the ROM flashed if ODIN won't do it?
Any help will be greatly appreciated!

I've been thinking about this problem, and I've come up with two options. Either flash back to the original boot loader, kernel, etc. Or somehow get a stock 5.1 ROM to flash.
Any thoughts?
Sent from my (old) SGH-M919 using XDA Free mobile app

More info...
When I try to flash a 5.1 stock rom, I get the following output from Odin:
<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 Successfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialization..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!
<ID:0/004>
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
FYI, the text in my download screen says:
ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: Custom
SYSTEM STATUS: Official
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:2 K:2 S:2
Does anyone know if T-mobile or Samsung could/would fix this, assuming I can't get it going in the next day or two?
thx.

SOLVED!
So for anyone else who finds yourself in this foolish situation, here is what worked *for me*.
The problem:
The newer sboot.bin wouldn't allow an older Android version to boot, and I couldn't Odin the newer COF6 or COF8 firmware.
The solution:
I downloaded and unzipped (technically un-tarred) the *STOCK COF8* firmware from Samsung (sammobile.com)
-To do that rename the file by removing the ".md5" extension. Yes Windows, we really do want to change the extension.
-If you don't have a program that recognizes the ".tar" extension, download PeaZip and install it - it's open source & awesome!
-Re-tar all of the files there *EXCEPT* for the sboot.bin.
-Boot into recovery as before, and open Odin - you should be a pro at this by now!
-Click the AP button and select the re-tarred stock firmware, and flash.
-Odin fails after a few files, but this is ok.
-Reboot and you should get a "failed update" error instead of the Samsung logo.
-Now Odin the *STOCK COF6* firmware
-Watch and thank God as it succeeds,and reboots ...normally
-Be patient, it still needs to update Android.
-Decide just how badly you need ROOT.....

Lovetoflyguy said:
SOLVED!
So for anyone else who finds yourself in this foolish situation, here is what worked *for me*.
.
Click to expand...
Click to collapse
You are a lifesaver. More specifically a $579 saver.

Lovetoflyguy said:
The solution:
I downloaded and unzipped (technically un-tarred) the *STOCK COF8* firmware from Samsung (sammobile.com)
-To do that rename the file by removing the ".md5" extension. Yes Windows, we really do want to change the extension.
-If you don't have a program that recognizes the ".tar" extension, download PeaZip and install it - it's open source & awesome!
-Re-tar all of the files there *EXCEPT* for the sboot.bin.
Click to expand...
Click to collapse
Scratch that. I used PeaZip instead of WinRar or 7Zip. I didn't name it tar.md5, flashed and it's booting up now. We'll see if it works.
How did you get the new tarball file you made to pass the MD5 check? I can't get past that check when I make a new .tar file or tar.md5.

Lovetoflyguy said:
SOLVED!
So for anyone else who finds yourself in this foolish situation, here is what worked *for me*.
The problem:
The newer sboot.bin wouldn't allow an older Android version to boot, and I couldn't Odin the newer COF6 or COF8 firmware.
The solution:
I downloaded and unzipped (technically un-tarred) the *STOCK COF8* firmware from Samsung (sammobile.com)
-To do that rename the file by removing the ".md5" extension. Yes Windows, we really do want to change the extension.
-If you don't have a program that recognizes the ".tar" extension, download PeaZip and install it - it's open source & awesome!
-Re-tar all of the files there *EXCEPT* for the sboot.bin.
-Boot into recovery as before, and open Odin - you should be a pro at this by now!
-Click the AP button and select the re-tarred stock firmware, and flash.
-Odin fails after a few files, but this is ok.
-Reboot and you should get a "failed update" error instead of the Samsung logo.
-Now Odin the *STOCK COF6* firmware
-Watch and thank God as it succeeds,and reboots ...normally
-Be patient, it still needs to update Android.
-Decide just how badly you need ROOT.....
Click to expand...
Click to collapse
i did everything you said but after (-Re-tar all of the files there *EXCEPT* for the sboot.bin.) step the new file was not recognized by odin.....any help???
IMP!!!! did you mean to flash odin from download mode or recovery mode because i've never heard of flashing odin from recovery mode

vegeta_badman said:
i did everything you said but after (-Re-tar all of the files there *EXCEPT* for the sboot.bin.) step the new file was not recognized by odin.....any help???
IMP!!!! did you mean to flash odin from download mode or recovery mode because i've never heard of flashing odin from recovery mode
Click to expand...
Click to collapse
Always!!!! flash Odin files in Download mode.

i did everything as u said it...But i can not flash the STOCK (COF6) in odin it fails..plz help:crying:

Lovetoflyguy said:
When I try to flash a 5.1 stock rom, I get the following output from Odin:
<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 Successfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialization..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!
<ID:0/004>
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
FYI, the text in my download screen says:
ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: Custom
SYSTEM STATUS: Official
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:2 K:2 S:2
Does anyone know if T-mobile or Samsung could/would fix this, assuming I can't get it going in the next day or two?
thx.
Click to expand...
Click to collapse
how did you flash the firmware back to stock because i cant enter download mode:crying:

Cannot flash anything through Odin

So here's my problem. I bought my Note 4 (SM-N910T3) with 5.1.1 and rooted. As soon as 6.0.1 released, I downloaded and flashed and then rooted a little later. I started having some small issues because of the root so I did some research and found a systemless root method on XDA that was a possible solution. At some point, probably from flashing MM, my Baseband and Bootloader got updated to the newest at the time. That was fine at the time but I starting missing some of the features of 5.1.1 that got removed in the update. So now I'm looking at iB4STiD's Rapture ROM which is build upon stock 5.1.1 but I've hit a pretty major wall. No matter what I try, how many times, I cannot flash anything through Odin, besides 6.0.1 that I haven't tried. iB4STiD provides the Baseband and Bootloader files to flash with his ROM which are for my specific model.
Now, I've read in a couple places that you can't downgrade your bootloader but that sounds weird to me so maybe someone can explain more if that's correct. Now for some info:
Download Mode Text:
Code:
[COLOR="Red"]ODIN MODE (HIGH SPEED)[/COLOR]
PRODUCT NAME: SM-N910T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (2)
[COLOR="Silver"]QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, R1, A2, P1[/COLOR]
[COLOR="Blue"]SECURE DOWNLOAD: ENABLE[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
Now this is what comes up when I attempt to flash:
Odin:
Code:
<ID:0/008> 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/008> Odin engine v(ID:3.1203)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Download Mode:
Code:
[COLOR="Red"]SECURE CHECK FAIL: aboot
[1]eMMC write fail: ABOOT[/COLOR]
I am at the end here and mentally exhausted so if anybody can give some guidance or advice then that would be awesome. Let me know if you need more info!

It's silly. But I remember trying to unroot my nte 4 by going back to stock, odin kept failing until I s
Used the official USB cable of the note 4. I had to borrow my step dad's USB to successfully get the thing back working.
Sent from my SM-N910T using Tapatalk

nano303 said:
It's silly. But I remember trying to unroot my nte 4 by going back to stock, odin kept failing until I s
Used the official USB cable of the note 4. I had to borrow my step dad's USB to successfully get the thing back working.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yep I tried 4 different cables and different ports, including 2 OEM samsung cables that came from my Note 4 and an older phone. Nothing.

squiglybob13 said:
Yep I tried 4 different cables and different ports, including 2 OEM samsung cables that came from my Note 4 and an older phone. Nothing.
Click to expand...
Click to collapse
You can't downgrade T3 via ODIN once you upgrade to MM. So basically you are stuck with latest bootloader.

pvsgh said:
You can't downgrade T3 via ODIN once you upgrade to MM. So basically you are stuck with latest bootloader.
Click to expand...
Click to collapse
Yea that's what I was afraid of. My next issue though is I can't seem to flash ANYTHING via Odin. I even tried a stock rom that matched my current bootloader and it gave me the same error.

squiglybob13 said:
Yea that's what I was afraid of. My next issue though is I can't seem to flash ANYTHING via Odin. I even tried a stock rom that matched my current bootloader and it gave me the same error.
Click to expand...
Click to collapse
Use PhoneInfo application from Playstor to check your exact bootloader version and post it here. The error from your 1st post shows only when you try to downgrade.

I believe I've got the same problem (N910T, I tried to downgrade to 5.1.1 so that I can install Rapture v8.2), except in Odin it stops at system.img.ext4 then fails. I tried restoring with my backup through TWRP but now it's giving me this:
extractTarFork() process ended with ERROR=255
Basically I'm stuck with Odin and TWRP, I have the 5.1.1 firmware which doesn't work, and I'm currently downloading the 6.0.1 firmware and hopefully I'll be able to get it working again after this 2.2GB file finishes downloading with my 10mb/s internet -.-

System Software not authorized by AT&T

Hi All This is my first post here .
yesterday i had a problem installing Xposed framework it said that it need a custom rom to be istalled
so i downloaded the TWRP app chosed my recovery version and run it, it was flashed succesfully but when i tried to boot to it i got this message in blue screen "System Software not authorized by AT&T ... "
I was able to boot the system normally so i tried to recovere the original stock recovery i downloaded an app called Flashify downloaded a stock recovery ( im not sure that it was the original ) and flash it , after rebooting i was shocked by the blue screen on the recovery and also on the system so i can't boot to the system now !
I tried to flash another TWRP using odin 3.10.6 and 3.12.3 but in the two cases it fails with this error :
Code:
<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> recovery.img
<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)
Im totally lost now i have a lot of personal data inside ( 6gb of pics + 200 mb of call records + phone numbers )
I bought the phone from a third party , and we dont have any AT&T agency here
Information about the phone :
- I think that the phone was rooted because the root checker said that but when i install the su it said that i need a binary update and every time i do that it reboot without updating , when i tried from the recovery it said,signature failed or something like that .
- I had android 5.1 i think it was a custom rom because when the s6 logo appear I see under Custom with an open lock
When i go to the download mode they write
ODIN MODE //it was there even before i flash it
PRODUCT NAME : SM-G920V
CURRENT BINARY : CUSTOM // it was OFFICIAL before flashing
SYSTEM STATUS : CUSTOM
REACTIVATION LOCK : OFF
SECURE DOWNLOAD : ENABLED
RP SWREV : B:4 K:3 S:3
on the back of the phone the product name is : SM-G920F
on the previous rom it was : SM-G920F
Please any solution to back up my DATA then flash a new rom updated with a custom recovery Or even recover the original stock recovery only ( i was not using an AT&T sim card )

Galaxy s6 System Software not authorized by AT&T

Hi All This is my first post here .
yesterday i had a problem installing Xposed framework it said that it need a custom rom to be istalled
so i downloaded the TWRP app chosed my recovery version and run it, it was flashed succesfully but when i tried to boot to it i got this message in blue screen "System Software not authorized by AT&T ... "
I was able to boot the system normally so i tried to recovere the original stock recovery i downloaded an app called Flashify downloaded a stock recovery ( im not sure that it was the original ) and flash it , after rebooting i was shocked by the blue screen on the recovery and also on the system so i can't boot to the system now !
I tried to flash another TWRP using odin 3.10.6 , 3.11 and 3.12.3 but in the two cases it fails with this error :
Code:
<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> recovery.img
<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)
Im totally lost now i have a lot of personal data inside ( 6gb of pics + 200 mb of call records + phone numbers )
I bought the phone from a third party , and we dont have any AT&T agency here
Information about the phone :
- I think that the phone was rooted because the root checker said that but when i install the su it said that i need a binary update and every time i do that it reboot without updating , when i tried from the recovery it said,signature failed or something like that .
- I had android 5.1 i think it was a custom rom because when the s6 logo appear I see under Custom with an open lock
When i go to the download mode they write
ODIN MODE //it was there even before i flash it
PRODUCT NAME : SM-G920V
CURRENT BINARY : CUSTOM // it was OFFICIAL before flashing
SYSTEM STATUS : CUSTOM
REACTIVATION LOCK : OFF
SECURE DOWNLOAD : ENABLED
RP SWREV : B:4 K:3 S:3
on the back of the phone the product name is : SM-G920F
on the previous rom it was : SM-G920F
Please any solution to back up my DATA then flash a new rom updated with a custom recovery Or even recover the original stock recovery only ( i was not using an AT&T sim card )
(whitch version i should use to flash 920F or V or A ? )