Database Users

big problem

My phone fall down on the ground from my pocket and after that its like dead cannot enter bootloader recovery except when i conect it to pc.
when i connect it to pc and i try to enter recovery i get message "recovery is not seandroid enforcing i9505" and phone is restarting. only thing i can do is entering download mode and thats all how can i fix this thank you.

ivanmadzarov said:
My phone fall down on the ground from my pocket and after that its like dead cannot enter bootloader recovery except when i conect it to pc.
when i connect it to pc and i try to enter recovery i get message "recovery is not seandroid enforcing i9505" and phone is restarting. only thing i can do is entering download mode and thats all how can i fix this thank you.
Click to expand...
Click to collapse
- Shutdown ur phone
- Press button Volume up + Home + Power. When see the white title "Samsung Galaxy GT-i9505" drop the Power button
- It will go to CUSTOM Recovery

Joku1981 said:
- Shutdown ur phone
- Press button Volume up + Home + Power. When see the white title "Samsung Galaxy GT-i9505" drop the Power button
- It will go to CUSTOM Recovery
Click to expand...
Click to collapse
i tried this already but its not wokring when i connect it to pc its starting but i get message recovery is not seandroid enforcing i9505 and device its turning off. i can enter in download mode same but volume down button but i dont know how can that help me what can i do to fix it please someone... thanks

ivanmadzarov said:
i tried this already but its not wokring when i connect it to pc its starting but i get message recovery is not seandroid enforcing i9505 and device its turning off. i can enter in download mode same but volume down button but i dont know how can that help me what can i do to fix it please someone... thanks
Click to expand...
Click to collapse
if you can enter download mode, flash stock files via odin see if that allows your phone to boot normally

andy1weir said:
if you can enter download mode, flash stock files via odin see if that allows your phone to boot normally
Click to expand...
Click to collapse
ok i noticed something now when i enter in download mod it says downloading on screen and in the korner i see this
odin mode
product mode:gt-i9505
current binary custom
system status custom
knox kernel lock 0x0
knox warranty void 0x1
csb-config-lsb 0x30
write protection enable
emmc burst mode enabled how can i use odin is this how i connect it to odin i have the program but how can i use it

ivanmadzarov said:
ok i noticed something now when i enter in download mod it says downloading on screen and in the korner i see this
odin mode
product mode:gt-i9505
current binary custom
system status custom
knox kernel lock 0x0
knox warranty void 0x1
csb-config-lsb 0x30
write protection enable
emmc burst mode enabled how can i use odin is this how i connect it to odin i have the program but how can i use it
Click to expand...
Click to collapse
you need to find the stock files for you device and flash via odin, theres plenty guides of how to use odin, once you have the files its pretty easy, what software was it running originally? 4.2.2? or 4.3?

andy1weir said:
you need to find the stock files for you device and flash via odin, theres plenty guides of how to use odin, once you have the files its pretty easy, what software was it running originally? 4.2.2? or 4.3?
Click to expand...
Click to collapse
originaly was running 4.2.2 i am trying to find for dubai or uae is it problem if i donwload a firmware from different region then this

i downloaded this firmware http://forum.xda-developers.com/showthread.php?t=2409867 and i extracted it and i put it in the pda in odin trying when i press start i see FAIL
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
what i did wrong

ivanmadzarov said:
i downloaded this firmware http://forum.xda-developers.com/showthread.php?t=2409867 and i extracted it and i put it in the pda in odin trying when i press start i see FAIL
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
what i did wrong
Click to expand...
Click to collapse
hey there mate , your having a problem flashing that file because its a 4.2.2 rom and you already have a newbootloader which mean Not possible to downgrade when you have Knox Warranty Void. and you can check this threadto know more about KNOX, so Download and Flash a 4.3 base in your country and you should be fine.Have a nice day.
Edit: You can download a Official rom from here base from your country.

Repulsa said:
hey there mate , your having a problem flashing that file because its a 4.2.2 rom and you already have a newbootloader which mean Not possible to downgrade when you have Knox Warranty Void. and you can check this threadto know more about KNOX, so Download and Flash a 4.3 base in your country and you should be fine.Have a nice day.
Edit: You can download a Official rom from here base from your country.
Click to expand...
Click to collapse
i did same like you explained to me guys but its still not working same error
on the phone i can see this
start[224,1448]
sw rev, check fail: found :3, binary :1
Can anyone help me wake up my phone or atleast if someone have idea what the problem can or cannot be fixed

Samsung Galaxy s4 gt-i9505 crushed after firmware update. can i throw it away now?.

Hey.
Hopefully someone can help me.
Ive a Samsung Galaxy s4 GT-I9505
Android version is (well im confused now but i think..) 4.4.2
Well what happened:
I wanted to unroot my phone. i clicked on unroot in SuperSU and wanted to flash the original firmware.
Well then my phone got stuck in "firmware upgrade encountered an issue."
WHAT I TRIED:
1. try
Flash 4.4.2 via odin (3.07 & 3.10) but it said: FAIL
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
2. flash 5.0.1 but: FAIL
3. try
flash stock recovery and Kernel but also FAIL.
3. try
Wanted to enter the recovery mode on the phone but its just bringing up "firmware upgrade encountered an issue." again.
4. try
went into KIES, KIES3 and Smart Switch to recover like it said but i just get:
"GT-I9505 doesnt allow initialization" or something like that.
5. try
flashing the original PIT file but it also failed at re-partiti
SO:
i can enter download mode but cant enter recovery or start the phone normally.
Additional info in odin mode:
ODIN MODE
GT-I9505
Samsung Official
kernel: 0x0
warranty: 0x1
LSB: 0x30
write protection: enabled
burst mode: enabled
(at flashin pit file also
start [224,1440]
start [224,1440]
secure check fail: pit
Im not really into switchin the motherboard or whatever i found...
Please can someone help.
If info is needed i give them if i can just need to know how.
I try to reply to this in between 5-20 minutes
Because i really want to get my phone fixed..
Its needed for work and i dont have any replacement.
Ive teamviewer also if needed
Already to for the fast answers and the help. i kiss everyone if my phone gets secured somehow.
greetings.

I think there is official 5.0.1 firmware you could try flashing that.

To resolve the "Firmware encountered an issue" error, plug a ROM into the BL (bootloader) slot in Odin and flash. Just be certain the ROM is Android 4.4.2 or later.

EDIT: The Solution of Strephon Alkhalikoi that i should plug the 5.0.1 original rom into Bootloader in Odin worked Like a CHARM.
Phone went on again. Booted 5.0.1. Updated everything.
I leave you a big thanks. you secured my day.
Not sure about how i can close this.
or leave it open for people who have the same problem.
Again thanks alot for the fast answer and the help.
greetings.

i9500 no recovery partition, and unable to restore stock using odin

Hello.
I got a new Galaxy S4 (I9500) this October, and decided I would go ahead and install custom recovery on it. Me thinking I can get anything to work did not heed the warnings that this model does not support it go ahead and try anyway. Long story short, I no longer have a functioning recovery partition.
I have tried to follow several guides, most of which tell me the same thing:
Get Samsung drivers (not Kies)
Download Odin (one version or another)
Get the I9500 Firmware and install using Odin.
My phone is (from the sticker below the battery):
MODEL:GT-I9500
FCC ID: A3LGTI9500
SSN:-I9500GSMH
It is factory unlocked.
The text displayed in Odin Mode:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
I have tried flashing both 4.4.2 (as it was delivered with) and 5.0.1, but I get the same error:
<ID:0/005> Odin engine v(ID:3.1100)..
<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> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The error that is displayed on the phone is:
SECURE MAGICCODE CHECK FAIL : boot
Any help would be greatly appreciated!

Coolcise said:
Hello.
I got a new Galaxy S4 (I9500) this October, and decided I would go ahead and install custom recovery on it. Me thinking I can get anything to work did not heed the warnings that this model does not support it go ahead and try anyway. Long story short, I no longer have a functioning recovery partition.
I have tried to follow several guides, most of which tell me the same thing:
Get Samsung drivers (not Kies)
Download Odin (one version or another)
Get the I9500 Firmware and install using Odin.
My phone is (from the sticker below the battery):
MODEL:GT-I9500
FCC ID: A3LGTI9500
SSN:-I9500GSMH
It is factory unlocked.
The text displayed in Odin Mode:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
I have tried flashing both 4.4.2 (as it was delivered with) and 5.0.1, but I get the same error:
<ID:0/005> Odin engine v(ID:3.1100)..
<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> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The error that is displayed on the phone is:
SECURE MAGICCODE CHECK FAIL : boot
Any help would be greatly appreciated!
Click to expand...
Click to collapse
You don't have an i9500. Whoever told you that was lying. You have an SGH-I337 which is a completely different model. You got an AT&T model. You are trying to flash the wrong firmware.
Here is the section for your device.
http://forum.xda-developers.com/galaxy-s4-att
Bottomline you got a ****ty device with a locked bootloader. You can forget about custom recoverys and custom roms.

Lennyz1988 said:
You don't have an i9500. Whoever told you that was lying. You have an SGH-I337 which is a completely different model. You got an AT&T model. You are trying to flash the wrong firmware.
Here is the section for your device.
http://forum.xda-developers.com/galaxy-s4-att
Bottomline you got a ****ty device with a locked bootloader. You can forget about custom recoverys and custom roms.
Click to expand...
Click to collapse
Model number in settings say GT-I9500, and I can use my Norwegian GSMH SIM card with it, which I would not have been able to on a AT&T phone. Anyway, at this point I don't care about custom recovery etc, I just want it working.
Edit: I also got Cyanogenmod working before I messed up the recovery

Coolcise said:
Model number in settings say GT-I9500, and I can use my Norwegian GSMH SIM card with it, which I would not have been able to on a AT&T phone. Anyway, at this point I don't care about custom recovery etc, I just want it working.
Edit: I also got Cyanogenmod working before I messed up the recovery
Click to expand...
Click to collapse
It's irrelevant what it says in the settings menu. It really easy to change it.
It's the part in download mode that matters.
PRODUCT NAME: SGH-I337
Alright if you say the already had CM on it, then you still have an unlocked bootloader. Whatever you do, do not flash a stock AT&T rom or it will upgrade your bootloader.
Here is TWRP recovery.
https://www.androidfilehost.com/?fid=24052804347763625
Flash it using Odin. 99% of Odin errors can be resolved by using a different usb port and/or using a different usb cable.

You've a franken phone.
Sent from my GT-I9500

BRICK - Accidentally flashed N900P firmware to N9005

Hello,
i got a device to repair. I am not so familiar with samsung devices so i would apreciate some advice/help.
I dont know how to flash correctly the n9005 firmware.
I cant go to recovery and when try to boot there is shown on the screen "kernel is not seandroid enforcing, set warranty bit : kernel" and the device is rebooting to this text over and over.
It Is N9005 (is written under the battery).
But when i go to download mode it is listed this:
Code:
Odin Mode
product name: SM-N900P
Current Binary: Samsung Official
System Status: Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
Qulcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, R1, A3, P1
Write Protection: Enable
I assume the owner accidentally flashed an n900P firmware to his n9005 device.
I tried many ODIN bversions (3.10.7,3.10.6,3.07,1.85) and stock 5.0, 4.4.2, 4.3 firmwares, various n9005 PIT files
when flashing a stock 4.4.2 firmware (only AP file from sammobile)
Code:
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> SingleDownload.
<ID:0/016> sbl1.mbn
<ID:0/016> NAND Write Start!!
<ID:0/016> FAIL! (Auth)
when flashing a stock 5.0 firmware (only AP file from sammobile)
Code:
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL! (Auth)
when flashing a 4.4.? csc file for n9005
Code:
<ID:0/015> Odin engine v(ID:3.1100)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Set PIT file..
<ID:0/015> DO NOT TURN OFF TARGET!!
<ID:0/015> FAIL!
<ID:0/015>
<ID:0/015> Re-Partition operation failed]
closest i got with this:
in ODIN 3.07 when flashing kitkat csc file i got
Code:
<ID:0/015> Firmware update start..
<ID:0/015> cache.img.ext4
<ID:0/015> NAND Write Start!!
<ID:0/015> hidden.img.ext4
<ID:0/015> FAIL
and on the device was shown:
Code:
secure check fail : PIT
Set warranty bit : cache
Unsupport dev_type

nobody?
I make a step further.
Now i can flash system (AP) or i can flash twrp recovery or root trough ODIN, but i cant flash the whole stock, because it will fail everytime on sbl1.img, aboot or hidden.image.ext4
So now i can boot the system, but with N900P modem, kernel and othe rpartitions, so wifi dont work ect.
Now it would be superb to have a zip file with stock modem,sbl,aboot,non-hlos to flash it trough TWRP.
please any advice?

Sorry for my English!!
Download your region firmware from sammobile and pit file for your device n9005 note 3 open europ from xda.
Open odin select pit then the rom on itch specific place flash everything...
Let me know if you've got a positive result.
Sent from my SM-N910F using XDA-Developers mobile app

tried this dozen times. It gives me error when Odin tries to write the sbl1 or aboot or modem partition (as i wrote in OP). It gives error because the pit file doesn't match.

Is it possible the phone's motherboard was swapped for a 900p?

don't know... maybe. so you suggest to imstall stock N900P firmware?

https://mega.nz/#!kQtGnCYZ!7jko1XT7fPc9mIGHE8JLZhOvaeGH6qQbaW7Y6RYBQjU
This is a pit file for n9005 Europe
I advice you to reflash the rom of your original specific model with the pit file with wipe partition checked
Let me know wen u did
Sent from my SM-N910F using XDA-Developers mobile app

I will try. I avoided to wipe partitions while users say here on xda that it is a one way ride. ?

Samsung seems to have pretty good security measures in place to prevent flashing incorrect ROMs via Odin.
The failure to flash the 9005 aboot file tells me the bootloader on the rom and the bootloader in the phone do not match.

so how it can be, that i have an n9005 device with n900p Firmware and all partitions?

Does the imei in the phone match the imei on the printed label under the battery?

And why not your device would be a N900P ? Remove battery and see...
Maybe your USB is bad (it happened to me : 4 cables, 3 not working, 1 working hopefully)
Or maybe your downloaded ROM can't been flashed (weird, but it happened also to me), so flash the same model, but other revision (exemple OD3 doesn't work, try with OJ3, in my case)
Good luck !

use kies to install firmware. from kies select tools then "Emergency firmware recovey".

Munawar Mehmood said:
use kies to install firmware. from kies select tools then "Emergency firmware recovey".
Click to expand...
Click to collapse
the kies dont see my device.

cedric3 said:
And why not your device would be a N900P ? Remove battery and see...
Maybe your USB is bad (it happened to me : 4 cables, 3 not working, 1 working hopefully)
Or maybe your downloaded ROM can't been flashed (weird, but it happened also to me), so flash the same model, but other revision (exemple OD3 doesn't work, try with OJ3, in my case)
Good luck !
Click to expand...
Click to collapse
as i wrote under thebbattery is written n9005. usb is good use it to flash other phones. tried to flash about 4 stock roms.

DallasCZ said:
as I wrote, under the battery is written N9005. USB is good : I use it to flash other phones. I tried to flash about 4 stock roms.
Click to expand...
Click to collapse
Install Kies ot SmartSwitch (Kies' replacement)
Go to Emergency
Enter N9005 in device model
Enter the S/N number (written under the battery)
Connect your phone (don't worry if it is not recognized)
Go !
It will download the right update and install it : be patient, don't disconnect the phone or internet...
Good luck

jemis1983 said:
https://mega.nz/#!9BtkxK4A!Gy7muVwEtYBQFtxktDfCFK3VfcMZanfOMdOP9Elrm1U
This is a pit file for n9005 Europe
I advice you to reflash the rom of your original specific model with the pit file with wipe partition checked
Let me know wen u did
Sent from my SM-N910F using XDA-Developers mobile app
Click to expand...
Click to collapse
this is only a bat file to store the pit from the device.There is no pit file inside.

cedric3 said:
Install Kies ot SmartSwitch (Kies' replacement)
Go to Emergency
Enter N9005 in device model
Enter the S/N number (written under the battery)
Connect your phone (don't worry if it is not recognized)
Go !
It will download the right update and install it : be patient, don't disconnect the phone or internet...
Good luck
Click to expand...
Click to collapse
smart switch sys that my device dont support iniciation (after i added the sn number and mobile number.

DallasCZ said:
smart switch sys that my device dont support iniciation (after i added the sn number and mobile number.
Click to expand...
Click to collapse
Ok, and have you found the PIT file for your device ?

cedric3 said:
Ok, and have you found the PIT file for your device ?
Click to expand...
Click to collapse
I have the pit file for N9005 i flashed it using ODIN ..it was all ok
When i try to flash the AP image of stock (that cotains all parts BL,AP,CSC, CP) the flash ends by starting with flashing BL partitions sbl1.img)
When try to flash BL (bootloader) there is error in flashing sbl1.img.
the same goe with CSC and CP images (always show some error in flashing aboot.img and other partitions and ODIN stops.
I can flash AP (the AP that is only the system,recovery,boot) it goes well, the device starts but has some errors (because of missing parts in CSC and CP?.). wifi dont work i see full signal but there is no simcard inserted
Now i can boot the device the imei that is shown in the android systme is other than the imei on the back (under the battery).
I think someone tried to flash a N900P firmware over the N9005.
Now i cant flash the rest of the partitions.

Another bootloop issue

Apologies for the repost, found this to be a better place to pose the plea for assistance
_____
Hello all. . .
Longtime reader (learner), first time poster. Trying to bring son's GS5 back to life -- it's stuck in boot loop ("Samsung GALAXY S5" splash screen appears, reboots). Unknown cause, not due to any flashes, ROMs, ROOT, etc
All attempts to enter recovery mode (Vol up + PWR + Home) initially successful (get blue text: RECOVERY BOOTING. . . .) then display goes black, repeats. -- never see Recovery screen. Yes, I've cycled power, battery out, wait, etc, etc.
Can successfully enter Download mode, Odin v3.09 recognizes connection, but all attempts to write to memory fail.
GS5 displays:
ODIN MODE:
PRODUCT NAME: SM-G900P
CURRENT BINARY: Samsung Original
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1 T3 A1 A3 P1
SECURE DOWNLOAD: ENABLE
UDC START
<press Odin Start button>
Odin displays:
<ID:0/008> Odin v.3 engine (ID:8)..
<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> NAND Write Start!!
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Device display adds line:
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
____
Cannot determine build number and original box long gone. I've downloaded a couple firmware zips from sammobile (Sprint CDMA) using files nearest to best guess for purchase date. Is it necessary to match the exact files which originally came installed or should later firmware releases also normally load? In other words, is the fail due to trying a wrong firmware revision?
Any other info I need to include here? Thanx in advance!
flyyboyy

Hello again:
Zero replies, did I omit important information in my first request -- or am I just rehashing previous inquiries about boot loop problems? (I have read through all posts relating to boot loops but found no answers that solved the to write to Nand failures). Forgive me if it's here and I simply didn't recognize it. . .
So (succinctly) why might Odin fail to write when attempting to reload the original firmware: . . . NAND Write Start!! . . . FAIL! (Auth) . . .Complete(Write) operation failed. . . .All threads completed. (succeed 0 / failed 1)
What might I be doing wrong, or what might I try instead?
Thanks again
flyyboyy said:
Apologies for the repost, found this to be a better place to pose the plea for assistance
_____
Hello all. . .
Longtime reader (learner), first time poster. Trying to bring son's GS5 back to life -- it's stuck in boot loop ("Samsung GALAXY S5" splash screen appears, reboots). Unknown cause, not due to any flashes, ROMs, ROOT, etc
All attempts to enter recovery mode (Vol up + PWR + Home) initially successful (get blue text: RECOVERY BOOTING. . . .) then display goes black, repeats. -- never see Recovery screen. Yes, I've cycled power, battery out, wait, etc, etc.
Can successfully enter Download mode, Odin v3.09 recognizes connection, but all attempts to write to memory fail.
GS5 displays:
ODIN MODE:
PRODUCT NAME: SM-G900P
CURRENT BINARY: Samsung Original
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1 T3 A1 A3 P1
SECURE DOWNLOAD: ENABLE
UDC START
<press Odin Start button>
Odin displays:
<ID:0/008> Odin v.3 engine (ID:8)..
<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> NAND Write Start!!
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Device display adds line:
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
____
Cannot determine build number and original box long gone. I've downloaded a couple firmware zips from sammobile (Sprint CDMA) using files nearest to best guess for purchase date. Is it necessary to match the exact files which originally came installed or should later firmware releases also normally load? In other words, is the fail due to trying a wrong firmware revision?
Any other info I need to include here? Thanx in advance!
flyyboyy
Click to expand...
Click to collapse

Same thing with me.. patience gets you through it..
The same thing happened to me, same phone and same contract carrier (Sprint).
I bought my phone from a third party who apparently restores it to near-mint condition. The OS it had was one of the first releases of 6.0 /marshmallow. I tried downgradingit back to 5 / lollipop because i heard that call recording was still enabled with that OS.
I used Odin versions 3.7 thru 3.10 i believe and flashed every version of 5 that was listed on sam mobile and samsung 's site and all of them either failed to initiate- citing the same readings and failure reasons in odin that you mentioned - or they "succeeded" and resulted in boot loops.
I also failed to flash any of the earlier ROM versions of android 6 than the one my SM-G900P phone came with.
Finally, i succeeded in flashing 2 types of ROMS, the version of 6 my phone started with, then subsequently the most recent version released earlier in march 2017 (this month).
Conclusion: i believe the order that you flash these roms for our model phone with our carrier matters. Flash your phone with ROM images from the version that it came with, and continue sequentially and chronologically until your boot screen finally shows something other than that lovely little sprint logo
Good luck with your son's phone, and please let us k ow how it goes..... as i think this may be a recurring theme we may see more often in the future. I imagine the problem lies with either odin, samsung sm-g900p, or the sprint/cdma ROMa we're dealt.
-Rob

Have you tried samsung kies yet? Odin is for rooting your phone. Samsung kies will put updated firmware in your phone. I have used it several times in the past on a sam phone. It will work. Its from samsung company.