so i am trying to root my galaxy s4 sgh i337 that is the att model. i downloaded odin and activated usb debugging in the developer options. i am using cf auto root. so i select cf autoroot and connect my device. it shows a little blue bar when i connect my device but then when i click run odin stops at setup connection. how long should i have to wait here. and i have installed the latest drivers. uninstalled kies. i am using a brand new official samsung cable. and the device connects to my computer just fine and i can transfer data on it. why does odin get stuck on setup connection.
Does it say "Added" in Odin?
Yes
TGxLEGENDz said:
Yes
Click to expand...
Click to collapse
Did you put it in download mode ?
gosha98_ said:
Did you put it in download mode ?
Click to expand...
Click to collapse
Do i have to put the phone in download mode when i am just rooting it? I am not flashing a new rom to it yet
Yes
TGxLEGENDz said:
Do i have to put the phone in download mode when i am just rooting it? I am not flashing a new rom to it yet
Click to expand...
Click to collapse
every operation with odin like root or restoring stock need the phone in download mode.
gosha98_ said:
every operation with odin like root or restoring stock need the phone in download mode.
Click to expand...
Click to collapse
ok thank you so much i am now past the setup connection, but when i root it is failing every time in the same spot <ID:0/007> 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/007> Odin engine v(ID:3.1101)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1)
i am using cf autoroot. what option should i select when i load up odin, BL, AP, CP, or CSC
AP.
Strephon Alkhalikoi said:
AP.
Click to expand...
Click to collapse
ok now i am getting this when it fails
<ID:0/007> 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/007> Odin engine v(ID:3.1101)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
also on the phone in the top left in red letters it says secure check fail
and can i ask what all those two letter abbreviations stand for
Where did you download CF auto roof?
TGxLEGENDz said:
ok now i am getting this when it fails
<ID:0/007> 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/007> Odin engine v(ID:3.1101)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
also on the phone in the top left in red letters it says secure check fail
and can i ask what all those two letter abbreviations stand for
Click to expand...
Click to collapse
//
gosha98_ said:
//
Click to expand...
Click to collapse
i dont remember exactly where i downloaded it but i have tried it from a couple places. is there a link to download it from xda?
gosha98_ said:
//
Click to expand...
Click to collapse
ok looked in my history and i downloaded it from here and got the correct version to match my device and android version
https://autoroot.chainfire.eu/
could the problem be that i have a locked boot loader? im not entirely sure i do but would that cause this issue? it is saying secure magiccode check fail on my device.
Do you know the code name of your device?
TGxLEGENDz said:
i dont remember exactly where i downloaded it but i have tried it from a couple places. is there a link to download it from xda?
Click to expand...
Click to collapse
Or maybe, do you know model? For example: s4 LTE qualcom is 9505, mine 9515.. Yours ?
gosha98_ said:
Or maybe, do you know model? For example: s4 LTE qualcom is 9505, mine 9515.. Yours ?
Click to expand...
Click to collapse
the model is the s4 sgh-i337 and it is from at&t it is running android 5.0.1
TGxLEGENDz said:
the model is the s4 sgh-i337 and it is from at&t
Click to expand...
Click to collapse
Did you get lollipop update ? 5.0.1 firmware ?
gosha98_ said:
Did you get lollipop update ? 5.0.1 firmware ?
Click to expand...
Click to collapse
i am not sure. i got the phone from my friend and it already had 5.0.1 on it.
TGxLEGENDz said:
the model is the s4 sgh-i337 and it is from at&t it is running android 5.0.1
Click to expand...
Click to collapse
CF auto root doesn't Support this phone. That's why odin failed. You can try to use " Kingroot " to root.
gosha98_ said:
CF auto root doesn't Support this phone. That's why odin failed. You can try to use " Kingroot " to root.
Click to expand...
Click to collapse
ok where can i go to learn how to use and download kingroot
TGxLEGENDz said:
ok where can i go to learn how to use and download kingroot
Click to expand...
Click to collapse
https://kingroot.net/wap . download it from here. Then install the apk and click root. Wait, probabily it will reboot your phone and then check with an app if you got the root access permission.
gosha98_ said:
CF auto root doesn't Support this phone. That's why odin failed. You can try to use " Kingroot " to root.
Click to expand...
Click to collapse
okay kingroot worked! thank you so much!!! will i be able to install a custom recovery, and ROM?
Related
Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html
frliran said:
Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html
Click to expand...
Click to collapse
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.
Here is the log from odin
radicalisto said:
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.
Click to expand...
Click to collapse
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...
frliran said:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...
Click to expand...
Click to collapse
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )
Here is the log of the first file
radicalisto said:
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )
Click to expand...
Click to collapse
The previous log was from the new file I downloaded today.
This is the log from "Odin3 v3.07" using the first file I rooted my phone with:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE...Can you please help me to re-root my phone.
(And if you can, please send me a link to download root for the KitKat version so that I can re-root it when the update will rollout in my country.)
Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?
yes
radicalisto said:
Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?
Click to expand...
Click to collapse
Yes I am.
But in odin 3.9 there is AP and not PDA.
But I tried both in both odin versions: 3.7 and 3.9.
In odin 3.7 I am using PDA, and in odin 3.9 I am using AP.
Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.
)-;
radicalisto said:
Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.
Click to expand...
Click to collapse
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country
frliran said:
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country
Click to expand...
Click to collapse
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**
hmmm
radicalisto said:
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**
Click to expand...
Click to collapse
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...
Solved it (-:
frliran said:
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...
Click to expand...
Click to collapse
On the settings page under security..make sure you have reactivation lock uncheck...
Than try again..that's usually the problem
It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.
Thank you very much for your help
radicalisto said:
It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.
Click to expand...
Click to collapse
Yes (-:
Thanl you very much for your help and consideration
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUFNF4_N9005OLBFNG1_N9005XXUFNF2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please help
j0ndav3 said:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUFNF4_N9005OLBFNG1_N9005XXUFNF2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please help
Click to expand...
Click to collapse
Download and install a custom rom here (AOSP or Stock and etc). Assuming you have a custom recovery.
Graffiti Exploit said:
Download and install a custom rom here (AOSP or Stock and etc). Assuming you have a custom recovery.
Click to expand...
Click to collapse
I cannot boot in recovery mode. What can I try?
I don't know what to do.. (
j0ndav3 said:
I cannot boot in recovery mode. What can I try?
I don't know what to do.. (
Click to expand...
Click to collapse
From what version did you come from exactly? You can't flash an older one from your current one.
Install a custom recovery through Odin. Download one here at the forums.
Graffiti Exploit said:
From what version did you come from exactly? You can't flash an older one from your current one.
Install a custom recovery through Odin. Download one here at the forums.
Click to expand...
Click to collapse
from 4.4.2 but i tried to install a same 4.4.2 version with download booster and kids mode that's why i tried to manual update my note 3 n9005
sorry im a noob.. thanks..
j0ndav3 said:
I cannot boot in recovery mode. What can I try?
I don't know what to do.. (
Click to expand...
Click to collapse
Do you can boot in Download mode?
porcelana said:
Do you can boot in Download mode?
Click to expand...
Click to collapse
Yes i can boot in Donwload mode..
Is it possible to update my 4.4.2 to 4.4.2 with download booster? because to my previous version, there's no download booster that's why I tried to install that firmware..
j0ndav3 said:
Yes i can boot in Donwload mode..
Is it possible to update my 4.4.2 to 4.4.2 with download booster? because to my previous version, there's no download booster that's why I tried to install that firmware..
Click to expand...
Click to collapse
Is your new image from a same region as your old one ?
If you had a let's say UK Version of firmware, you cannot flash with a Hong Kong one. That's when problems start.
Don't worry, this is not a big deal. We just need more info.
having same problem here.. currently stuck with SweetRom 4.4.2 v20 with video camera not working!
Colide said:
Is your new image from a same region as your old one ?
If you had a let's say UK Version of firmware, you cannot flash with a Hong Kong one. That's when problems start.
Don't worry, this is not a big deal. We just need more info.
Click to expand...
Click to collapse
I had a Hongkong version then I tried to install the Philippine version I think that's the problem. Thanks I hope I can fix this
)))))))))
Colide said:
Is your new image from a same region as your old one ?
If you had a let's say UK Version of firmware, you cannot flash with a Hong Kong one. That's when problems start.
Don't worry, this is not a big deal. We just need more info.
Click to expand...
Click to collapse
Thanks Colide! I already fixed my phone! Thanks for your tips! I really appreciate it! many thanks!
Hi Everyone!
Can anyone helpe me with following trouble? I have a SM-9005 Dubai version.
I tried to flash lolipop 5.0 rom to my device via odin. but when installing system it said fails, even if i tried that several times the result is same. I used Odin 3.09 and then tried V1.85 after reading some suggestions for another guy in similiar situation. But unfortunately didn't help my case. on the device screen i see 3 lines of red messages saying :
UDC start
Volume size is too big 4620288<4718592
ODIN: Invalid ext4 image
and Odin messages:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005OXXENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I don't know what to do. Please help.
BR
FIRAT
is it locked to carrier?
When it fails on NAND write that shouldn't brick your phone because nothing on the device has been written by Odin. Is your device still working or are you just wondering how to flash Lollipop?
fuel3100 said:
is it locked to carrier?
Click to expand...
Click to collapse
Hi, no, It was sim free. Any sim could use.
speedyjay said:
When it fails on NAND write that shouldn't brick your phone because nothing on the device has been written by Odin. Is your device still working or are you just wondering how to flash Lollipop?
Click to expand...
Click to collapse
But when i switch on the device i always use the same screen. I can't do anything. Recover mode doesn't work too.
Well, i would like to flasg lolipop but sure my priority is to save the phone first. Then i can think about rom version.
So, what do you think about it ?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1BOC4_G900VVZW1BOC4_CL3846539_QB4392815_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<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> 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)
I was trying to root the s5 by downgrading but ran into a slight problem. Everytime I start the phone it boots for 5 mins, then goes into stock recovery. I have tried multiple different stock roms and none seem to work. Any help would be awesome.
What version were you downgrading from?
I believe BOG5
ldeveraux said:
What version were you downgrading from?
Click to expand...
Click to collapse
BOG5 I believe. At first it was telling me that when I ever I tried to root it, it would fail and then on the screen this would pop up: SW Rev Check Fail : Fused 2 Binary 1. Now whenever I start up the phone it tells me that the update failed and I need to use verizon software repair assistant to fix it.
calebp123 said:
BOG5 I believe. At first it was telling me that when I ever I tried to root it, it would fail and then on the screen this would pop up: SW Rev Check Fail : Fused 2 Binary 1. Now whenever I start up the phone it tells me that the update failed and I need to use verizon software repair assistant to fix it.
Click to expand...
Click to collapse
Anything OE1 or newer (yours is newer) can't be downgraded
ldeveraux said:
Anything OE1 or newer (yours is newer) can't be downgraded
Click to expand...
Click to collapse
Is there a link to the original verizon firmware or what should I do?
calebp123 said:
Is there a link to the original verizon firmware or what should I do?
Click to expand...
Click to collapse
You can just flash your phone back with stock firmware you were previously on. You can search the development thread for it. Unless you took a backup before doing all this, that's what you would have done if you read first..
Hi, my problem is I followed this post and installed CM 13 on the phone (Samsung Galaxy S4 SM-S975L(AT+T Refurb on Straight Talk)) and most of it works, but the calling/ texting/ data doesn't and I noticed the model number in >settings/ about phone now reads SGH-M919. any assistance to get call/ text/ data back would be appreciated.
Does the phone display the correct IMEI when you dial *#06#?
Did you try flashing a stock ROM with Odin: https://www.sammobile.com/firmwares/database/SM-S975L/ ?
audit13 said:
Does the phone display the correct IMEI when you dial *#06#?
Did you try flashing a stock ROM with Odin: https://www.sammobile.com/firmwares/database/SM-S975L/ ?
Click to expand...
Click to collapse
I appologise for the time it took me to reply, and thank you for the snappy one.
Yes the IMEI matches, and I have been trying to flash the stock rom for the past three days, it always fails though.
Boot into download mode and confirm that the model # is SM-S975L or m919.
What error are you getting in Odin? Posting the Odin log can sometimes help find a solution.
audit13 said:
Boot into download mode and confirm that the model # is SM-S975L or m919.
What error are you getting in Odin? Posting the Odin log can sometimes help find a solution.
Click to expand...
Click to collapse
Download mode says SM-S975L, that's how I found out the OS was wrong.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S975LUDUANB1_S975LTFNANB1_S975LUDUANB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I don't actually know if it has a Log dump, but this what the readout says when I run v3.7
Are you using the original Samsung USB cable on a USB 2.0 port?
Odin is not flashing aboot.mbn because the file doesn't match the phone.