Odin ошибка fail auth

Can’t complete the Stock ROM flash on my galaxy grand prime SM-G530H. The following error is shown inside the Odin message box. 

<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> aboot.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010> FAIL! (Auth)
<OSM> 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?

Bálint Babics's user avatar

asked Sep 8, 2016 at 4:21

febin mathew's user avatar

1

I’m pretty sure you’re in Recovery mode. Put your device in Download mode (turn your device off, press and hold volume down and home buttons, then press and hold the power button until the download warning appears, then volume up to continue, connect USB and run Odin) to flash with Odin.

Putting your phone in Recovery mode is done the same way except volume up is pressed with the home key instead of volume down.

ale's user avatar

ale

19.7k34 gold badges109 silver badges159 bronze badges

answered Jan 4, 2017 at 14:05

David Banks's user avatar

You must log in to answer this question.

Not the answer you’re looking for? Browse other questions tagged

.

Источник

Android Forums

Help [ANSWERED] FAIL! (Auth) Error in Odin3 when trying to flash stock rom on my Galaxy Tab 4 8.0 (AT&T)


  • Thread starter

    KingOfTheNet


  • Start date

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

KingOfTheNet


  • #1

Ok so i’m not a huge android person so i was kinda expecting one or two mess ups. After a failed root attempt, my device would freeze on the AT&T screen after getting passed the initial startup screen and then the Samsung logo. I had to flash stock firmware on my phone before with Odin and it worked no problems, so i don’t really know why it wouldn’t work here.I Downloaded the exact firmware that matched my device (I recommend sammobile.com for firmware) and this is the thread that Odin gave me.

<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/005> Added!!
<ID:0/005> Odin engine v(ID:3.1101)..
<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> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

At this point i’m lost at what to do, and I don’t want to go through all the hassle and headaches of taking this to AT&T. I would assume other people have had this issue (after all it is the internet) and I know it can be fixed, I also have picture down below, hopefully this will help. All tips and replies are greatly appreciated :)

This picture was taken 1 minute after the error was given. Need more info on the error? Please ask!

20160926_143954.jpg

Jfalls63



May 15, 2015
4,339
3,391
918


  • #2

AT&T has only released the original firmware for 4.4.2
If you were on a higher Android version, 5.0 or newer, you can’t downgrade due to locked bootloader and Knox Security. You can only flash the version that is currently on the device or higher.
A lot of people have been looking for the current released firmware version and no one has it.

James L


KingOfTheNet


  • #4

Well I appreciate the reply. Sorry it took me so long to get back.

When I tried applying it through adb or my microsd card, it gives off «Status 7». Stupid question, but is that a fixable problem?

KingOfTheNet


  • #5

AT&T has only released the original firmware for 4.4.2
If you were on a higher Android version, 5.0 or newer, you can’t downgrade due to locked bootloader and Knox Security. You can only flash the version that is currently on the device or higher.
A lot of people have been looking for the current released firmware version and no one has it.

I appreciate the reply. Sorry it took me so long to get back.

Dumb question, but I would assume this means that I have to wait until someone posts the 5.1.1 firmware?
Last time I checked it, I was on Android Version 5.1.1 Lollipop. I know I could continue trying to install the ota update (which is what the person down below your response suggested i do), but i’ve been working with that for 3 days straight, all I see is error after error.
Another dumb question, is there an easy way to unlock the bootloader or possibly disable the Knox Security?
I do still have the OTA update saved to my computers hard drive if you (or anyone) can help fix these errors that occur during the update.

Installation Aborted!
(Status 7)
-and-
E: Failed to verify whole-file signature
E: Signature verification failed

I have looked through days worth of forums and videos on how to fix these errors and still the update fails to apply. D:

Jfalls63



May 15, 2015
4,339
3,391
918


  • #6

AT&T locks the bootloader up tight and I don’t know of a way to disable/remove Knox without a working system and root access.
Other than wait and hope that someone can pull the firmware from a working device and make a tar file that can be flashed with Odin, your best bet at getting the device working again would be to send it to a AT&T repair center.
Not sure if the cost for repair versus replacement would be worth it.

KingOfTheNet


  • #7

AT&T locks the bootloader up tight and I don’t know of a way to disable/remove Knox without a working system and root access.
Other than wait and hope that someone can pull the firmware from a working device and make a tar file that can be flashed with Odin, your best bet at getting the device working again would be to send it to a AT&T repair center.
Not sure if the cost for repair versus replacement would be worth it.

Could I possibly succeed by flashing a custom rom, or would I need the 5.1.1 firmware to do that to?

Jfalls63



May 15, 2015
4,339
3,391
918


  • #8

You need a custom recovery like TWRP to be able to install a custom ROM. The locked bootloader prevents installing a custom recovery.

Jfalls63



May 15, 2015
4,339
3,391
918


Jfalls63



May 15, 2015
4,339
3,391
918


  • #10

The Samsung Rep at Best Buy is supposed to have the stock firmware and can flash your device but I think they only have the OTA updates. If one is near your location, might be worth checking in to.

KingOfTheNet


  • #11

Ok, so after a long couple of months of doing research and using a SPH-L720 and a GT-P3113 as «Lab Rats», I’m starting to understand how rooting works and how to do it. I do have a small update on the state of the tablet, and I have reasoning to believe the frozen at&t logo is the result of hardware failure.

My neighbor, who works at home with androids, managed to download the update and flash it successfully, via stock recovery, and told me that it would still freeze on the AT&T logo. He explained how it could be a hardware problem because the update flashed WITHOUT ISSUE, and still gave the same result. So, I need to take it to Best Buy or AT&T to have it fixed, i’m hoping they just replace it.

After doing more research, people were saying on different forums how the «All-In-One» firmware files have a slim chance of flashing successfully, and that «Multi-File» firmware files almost always work. But, knowing that the bootloader on this thing is locked (for some dumb reason that i’ll never understand), even if I did manage to find the 4 file firmware for this tablet, it would probably still fail.

I have, however, successfully rooted the other 2 devices mentioned above. I keep copies of stock firmwares, custom recoveries, and flashable .ZIP files on my hard drive. I do still have the OTA update for the SM-T337A on my hard drive as well, but I do kinda think it is the result of hardware failure.

It doesn’t make sense to me how KingRoot could cause a hardware failure. But then again, I never rooted any android at that time, or modified any android software. But, on the other hand, I still think it’s a software problem. The logic of AT&T to provide the stock firmware on the internet but, the bootloader is locked, what the actual «flip» were they thinking? Uploading a stock rom, meant for downgrading your device if problems are caused by new updates, but locking the bootloader up so tight, that we cant even do what the stock rom was intended to do, there’s no point in uploading the stock rom in the first place. And maybe if AT&T had the IQ of a tree instead of a newborn baby, they would upload the updated firmware like they did the stock rom.

I don’t wanna try to do the same with my SM-G850A, i’m probably gonna get the same outcome, plus, no developers are working on root methods or custom recoveries for this device, I guess i’m in stuck the deep end right now.

Last edited:

KingOfTheNet


  • #12

AT&T locks the bootloader up tight and I don’t know of a way to disable/remove Knox without a working system and root access.
Other than wait and hope that someone can pull the firmware from a working device and make a tar file that can be flashed with Odin, your best bet at getting the device working again would be to send it to a AT&T repair center.
Not sure if the cost for repair versus replacement would be worth it.

Well i’m very happy to announce that I successfully made the Lollipop Firmware for the tablet. If you want to know how I did it, i’m going to make a whole new post about it, and i’ll include a download link. I know this may help alot of people with my same problem, being that I soft bricked my tablet.

Link to the post: http://androidforums.com/threads/sm…nally-available-for-download-no-joke.1099890/

Last edited:

Similar threads

  • This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
Источник

Can’t complete the Stock ROM flash on my galaxy grand prime SM-G530H. The following error is shown inside the Odin message box. 

<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> aboot.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010> FAIL! (Auth)
<OSM> 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?

Bálint Babics's user avatar

asked Sep 8, 2016 at 4:21

febin mathew's user avatar

1

I’m pretty sure you’re in Recovery mode. Put your device in Download mode (turn your device off, press and hold volume down and home buttons, then press and hold the power button until the download warning appears, then volume up to continue, connect USB and run Odin) to flash with Odin.

Putting your phone in Recovery mode is done the same way except volume up is pressed with the home key instead of volume down.

ale's user avatar

ale

19.7k34 gold badges109 silver badges159 bronze badges

answered Jan 4, 2017 at 14:05

David Banks's user avatar

You must log in to answer this question.

Not the answer you’re looking for? Browse other questions tagged

.

Источник

I recently installed a few new ROMs on my Samsung Galaxy S4 and, foolishly, did not make a backup of my stock ROM.  I found that all of the ROMs I used (CyanogenMod, SlimKat, and OmniROM) would not let my phone use 4G LTE service and I ended up having a lot of problems with even 3G service.  So I decided to re-flash my S4 with the stock ROM, a process I thought would have been trivial.  Instead, I found that going back to the old stock ROM wasn’t as easy as I thought and I struggled to find answers to some of the error messages I was seeing.  The two that caused the most headache were the “FAIL (auth)” error and the “SW REV CHECK FAIL” error.

These errors indicate that the phone cannot use the ROM provided (via Samsung’s ODIN loader) because the ROM is either not legitimate or is a version prior to the one currently installed.  Basically, if you’ve flashed a ROM that is Android 4.4.2 (KitKat), you will not be able to revert back to an earlier version (such as Android 4.2.2).  The solution is the find the authentic ROM for the same version you’re already at.  In my case, I needed KitKat and wanted the official stock ROM.

The only place to get the stock ROM is from http://www.sammobile.com/firmwares/ and they do require you to register as a member for free (well worth it).  Once you’re there, enter your phone’s model number (you can find this in your phone’s status settings) and download both ODIN and the firmware (usually around 1-2GB in size).

Once downloaded, load up ODIN, unzip the ZIP of the ROM they gave you, click PDA in ODIN and select the extracted TAR ROM file.  Place your phone in “download mode” (if you’re not sure how to do this, watch this video: http://www.youtube.com/watch?v=9qh4z4JWLpI) and ODIN should show there is a new device and will give it a COM number.  Click start and you should be on your way to having a stock phone again!

Источник
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

  • #1

Hello,
I’m new this forms… but i’m trying to root my Samsung Galaxy S4 Verizon. I’m trying to flash a kernel its called (SCH-I545_MD2_423399_Kernel.tar.md5) with Odin3 v3.07 and here is the report:

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MD2_423399_Kernel.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

I install all the driver and Kies and still nothing here is the video that is telling me what to do:

How To ROOT Verizon Galaxy S4 EASIEST Method! — YouTube

i install all what he tell me but when i boot Odin go to PDA click the kernel and hit start (my device is in Odin mode) it shows reboot with blue square and then FAIL with the red square can someone help me. Thank You!

  • #2

I’m having the same problem. Did you get an answer?

  • #3

Dear TheLamerAndroid

i had the same problem from the morning and i was stuck too

i did research for a long period now and came with the answer that if you flash cf root via odion that would bring your phone alive

here’s the link for the cf auto
http://download.chainfire.eu/316/CF-Root1/CF-Auto-Root-jflte-jfltexx-gti9505.zip?retrieve_file=1

i assume you are running 4.4.2 and wanted to flash back to 4.3 as that what i tried and thats where the problem came.

flash the cf auto root and after when you get into your phone, flash a custom rom and via that try flashing back to 4.3. thats what am going to do now.

Hope this helps you

  • #4

ChainFire worked for me yesterday on my friend’s S4, It was a simple file dump with Odin v3.7. Success. ROOT.

Later when you want to flash a ROM, just make sure when you download the CWM 6 recovery for your phone in download mode, then uncheck the «Auto-reboot» buttton off or it will revert back to the OEM recovery. and hold power+home+vol up until you see the samsung logo, then let go of the vol up button, but still hold the other two until the CWM logo pops up.
I recommend using ClockWorkMod 6 recovery instead of Twrp 2.6, I just have had more luck with CWM. also twrp cant read 64gb sd cards.

  • #5

hi im new but ive been having this problem for days now. i tried re downloading everything, restarting my computer and phone, tried motochopper and odin, different versions of odin. anyone else have this?

  • #6

Did you ever get a resolve for this issue…I have the same issue…..Fail on Odin is as far as I can get. Please let me know, thanks!

  • #7

go to settings>security>device administrators and disable it + go to remote controls turn it off + reactivation lock

  • #8

Thank you very much. After using Kies 3 to upgrade my rooted Sprint Note 4 I lost root. So I tried to reroot using Chainfire’s fix, but I kept on getting a «fail (auth)» message. I have been looking for a fix for about a week. Not one of the forums mentioned disabling «Device Administrators» and turning off «Remote Controls» and «Reactivation Lock». I couldn’t find «Remote Controls», but I took care of the other two and it worked the first time.
Thanks again.

  • #9

My phone is rooted, and I accidentally clean wiped it using CWM recovery — the file system was also deleted. Now, the problem is, I can’t install any rom ( Custom Rom and even the stock firmware) — keeps on saying installation aborted. the worst thing is, I flash CF root in my phone using odin and now I’m stock at ODIN. when I start my phone, it automatically gets into odin mode, even if I try to hit recovery mode. And odin can’t even detect my phone now :(

BTW my phone is, SM-G530H/SD ( Galaxy Grand Prime)

can someone help me please!!!

  • #10

help I had android 5.0 on my Samsung galaxy s4. so I used odin3 to try to flash firmware from same moble I have tried all there firmware they all fail and even this recovery firmware fails. phone wont turn on just goes to scree that says software update has failed connect to computer and use version upgrade repair which I don’t have. I can get phone in download mode for odin but that’s it please help!

  • #11

THANKS MAN IT FIXED THE FAIL! (auth) Error in Oden

  • #12

Thank you so much i love you i have been trying to root for hours and hours and turning off those settings actually fixed my problem! :)

  • #13

are these settings located in odin if so how to do i get there

  • #14

Thanks. I solved the problem

Similar threads

  • Advertising
  • Cookies Policies
  • Privacy
  • Term & Conditions

Источник

Понравилась статья? Поделить с друзьями:
  • Oce 940 фальцовщик ошибка
  • Oculus произошла непредвиденная ошибка ovr40779122
  • Occt тест процессора ошибки
  • Office tab ошибка
  • Office 2010 ошибка 1714