Database Develop

[HELP] - upgrade gone wrong?

hi all,
i was on KL3, rooted, then KIES kept bothering me so i thought i'd upgrade to the new LA3 i think....
then the thing crashed and now all i get is the Firmware upgrade encounted an issue. PLease recovery mode in Kies and try again.
problem is, i cant get it to go into recovery mode?!??!?! (volume up, power?)
nothng works, KIes cant detect it, and cant upgrade anything, i am a total noob, and can only get into ODin mode..
HELP please?!?!?
what do i need to do, please step by step, what to download, what to press and whether i need to get a micro sd to install some firmware?
thankyou - urgent help needed!

First of all, relax
You said you can get into "Odin Mode"? I suppose that's download mode. Just go to this thread and everything is explained here. No need to worry
http://forum.xda-developers.com/showthread.php?t=1424997
Just flash another firmware (why not the latest) and everything will be just fine.
P.S. Once rooted, you should probably stay away from stock upgrades...
Press thanks if it helped

Recovery : vol up + home + power
If you get into recovery just wipe cache n wipe data
If error still there
Go to download :
vol dwn + home + power
Reflash new rom
Sent from my GT-N7000 using xda premium

this is all i get and gets stuck???
i chose this one: N7000XXLC1---------2.3.6-------2012 March----------N7000OXXLB3-----------France------------------------------------Download
went to bed for 2 hours and it didnt move...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLC1_N7000OXXLB3_N7000XXLB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img

confirm you have close antivirus if running
Dont put ROM file too deep, better keep on Root folder e.g. C:/Folder/***.tar.md5
Dont use USB extension, attach USB cable direct to slot on PC, try using different slot (preferably back side PC)
N dont forget to put device in download mode.

Thankyou Dr.Ketan and eug3n91
worked after i switched to the onboard USB.
i guess thats probably why Kies failed too....
this site is fantastic, been a lurker for a while, but never needed to post until today and its proven to be very succesful with both of you helping out so quick.
cant thankyou enough!

Dr.Ketan I am facing the same problem and did exactly the same but this is all i get
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK3_N7000ODDKK1_N7000DDKJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<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> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> boot.bin
<ID:0/015> cache.img
<ID:0/015> factoryfs.img

same problem here. flashed ROCKET ROM but now i can just go into download mode and CWM. ICS roms stuck on NAND WRITE START and GB roms on FACTORYFS.IMG
I tried everything ever mentioned i guess:
-Tried fix it with KIES but it doesn't even find my device
-use different USB port
-install USB drivers new
-flash Q1_20110914_16GB.pit
-flash other kernel "CF-Root-SGN_XX_OXA_LPY-v5.3-CWM5"
-flash "N7000_XXKL8" where i have to flash three files with odin v1.85
-took the battery out for a longer time
-Flashed different Stock Roms (wipa and without wipe)
-flashed the Abyss Kernel 4.2 again
-flashed "Criskelo's Rom" with CMW
-Tried on different PC with Windows XP
Please there must be a way to help me and khok3893

ow1166 said:
same problem here. flashed ROCKET ROM but now i can just go into download mode and CWM. ICS roms stuck on NAND WRITE START and GB roms on FACTORYFS.IMG
I tried everything ever mentioned i guess:
-Tried fix it with KIES but it doesn't even find my device
-use different USB port
-install USB drivers new
-flash Q1_20110914_16GB.pit
-flash other kernel "CF-Root-SGN_XX_OXA_LPY-v5.3-CWM5"
-flash "N7000_XXKL8" where i have to flash three files with odin v1.85
-took the battery out for a longer time
-Flashed different Stock Roms (wipa and without wipe)
-flashed the Abyss Kernel 4.2 again
-flashed "Criskelo's Rom" with CMW
-Tried on different PC with Windows XP
Please there must be a way to help me and khok3893
Click to expand...
Click to collapse
I'm afraid this has to do with corrupted memory partitions. It's what devs called 'superbricks' if I'm not mistaking...
You could try a ROM with a PIT file, hoping that would repartition any bad sectors.
Again, I could be mistaken. Try to read some other threads around here. A lot of.others have also encountered this problem

khok3893 said:
<ID:0/015> factoryfs.img
Click to expand...
Click to collapse
When you stuck at factoryfs.img = system partition corrupted

I tried with PIT file (Q1_20110914_16GB.pit) and ICS LYP Rom and it stucks on "NAND WRITE START" that comes after "factoryfs.img" I even uses "re-partition" in Odin. Nothing works.....

[Q] PIT or not PIT ?

I updated my Samsung Galaxy Note GT-N7000 (bought from Amazon France in fev-12) to the latest official Android version begining of July (4.1.2 or something like that) using Samsung Kies. No root nor any unnofficial modifications.
About 2 weeks later, as I was using it normaly (reading emails or browsing simple website), it turned off and it has not been able to restart since then. Starting screen is freezed to SGNote GT-N7000 ; no recovery mode available ; only download mode available.
I've tried to instal official Firmware with no success, with theses configs :
- Firmware : N7000XXLSZ_N7000XXLSO_N7000XEFLS4_HOME.tar
- Win7 64bits : with Odin v1.85 ; 1.83 ; 3.07 ; 3.07 in XP SP3 + administrator mode ; supermarket bougth cable or official Nexus 4 cable (official GT-N7000 cable broken...)
- Win7 32bits with Odin 3.07 normal mode and XP SP3 + administrator mode ; official Nexus 4 cable
- WinXP with Odin 3.07 ; official Nexus 4 cable
Here is the message I get on each 3 PC, with Odin 3.07
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLSZ_N7000XXLSO_N7000XEFLS4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
I'm getting to the conclusion my SNote is semi-bricked and it needs a new PIT ; before triying it I'd like to have an "expert opinion" as adviced on many sites ; what do you think ? Should I give it a try or consider sending it to Samsung (2y warranty applicable it seems to me) ?
I'm currently downloading an older Firmware version just to give it one last try before PIT or sending to Samsung. (N7000XXLRI_N7000XEFLP2_XEF.zip)
Thx in advance,
Quinteen

I forgot to add that :
- I installed latest USB drivers (latest KIES on Win7 64b ; standalone drivers on others PC)
- I killed all Kies processes before starting Odin
- I Disabled Anti-virus on Win XP & Uninstalled antivirus on Win 7 64b
Thx
q

One last precision : when using Odin 1.85 there is no error message ; it seems blocked writing NAND (waited for round 1h) :
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLSZ_N7000XXLSO_N7000XEFLS4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
Thx
q

No better result with an older firmware on Odin3.07 win7 64b (N7000XXLRI_N7000XXLRB_N7000XEFLP2_HOME.tar.md5) : same faillure message as in first post.
My phone was pretty full (230 MB free), might it be that I need to cilck the Erase NAND option ?
Thx,
Q

quinteen said:
No better result with an older firmware on Odin3.07 win7 64b (N7000XXLRI_N7000XXLRB_N7000XEFLP2_HOME.tar.md5) : same faillure message as in first post.
My phone was pretty full (230 MB free), might it be that I need to cilck the Erase NAND option ?
Thx,
Q
Click to expand...
Click to collapse
take out battery, reinsert, go to download mode, flash philz kernel (.tar) file (the one corresponding to your rom), flash using odin, once done, go to recovery (volume up+home+power), just to confirm that you have philz kernel, it would have option as philz settings. From there you can do factory reset and in mounts and storage you can wipe /system /data /preload /cache and then go to download mode and try to flash stock rom again. Also make sure stock rom download is not incomplete. Although these steps are might not help but you can still try.
Edit: did you wipe anything on stock recovery before trying to flash stock rom?

treacherous_hawk said:
take out battery, reinsert, go to download mode, flash philz kernel (.tar) file (the one corresponding to your rom), flash using odin, once done, go to recovery (volume up+home+power), just to confirm that you have philz kernel, it would have option as philz settings. From there you can do factory reset and in mounts and storage you can wipe /system /data /preload /cache and then go to download mode and try to flash stock rom again. Also make sure stock rom download is not incomplete. Although these steps are might not help but you can still try.
Edit: did you wipe anything on stock recovery before trying to flash stock rom?
Click to expand...
Click to collapse
Thanks for your answer Treacherous_hawk :
1/ I didn't wipe anything as my phone could only start in download mode when I started having these pb
2/ my phone isn't rooted and if I install philz kernel I guess the flash count will be incremented and I won't be able to send my phone to Samsung, right ?...
Quinteen

quinteen said:
Thanks for your answer Treacherous_hawk :
1/ I didn't wipe anything as my phone could only start in download mode when I started having these pb
2/ my phone isn't rooted and if I install philz kernel I guess the flash count will be incremented and I won't be able to send my phone to Samsung, right ?...
Quinteen
Click to expand...
Click to collapse
And by the way how do I get the ROM number given that I can't boot my phone ?....

quinteen said:
And by the way how do I get the ROM number given that I can't boot my phone ?....
Click to expand...
Click to collapse
you can flash xxlsz, xxlt5/6/7 any one of those. yes the counter might increase but if it works you can reset it to 0 using triangle away, but again only if it works, and if it is not booting and if you still have warranty why not send it for repair as it is.

quinteen said:
I updated my Samsung Galaxy Note GT-N7000 (bought from Amazon France in fev-12) to the latest official Android version begining of July (4.1.2 or something like that) using Samsung Kies. No root nor any unnofficial modifications.
About 2 weeks later, as I was using it normaly (reading emails or browsing simple website), it turned off and it has not been able to restart since then. Starting screen is freezed to SGNote GT-N7000 ; no recovery mode available ; only download mode available.
I've tried to instal official Firmware with no success, with theses configs :
- Firmware : N7000XXLSZ_N7000XXLSO_N7000XEFLS4_HOME.tar
- Win7 64bits : with Odin v1.85 ; 1.83 ; 3.07 ; 3.07 in XP SP3 + administrator mode ; supermarket bougth cable or official Nexus 4 cable (official GT-N7000 cable broken...)
- Win7 32bits with Odin 3.07 normal mode and XP SP3 + administrator mode ; official Nexus 4 cable
- WinXP with Odin 3.07 ; official Nexus 4 cable
Here is the message I get on each 3 PC, with Odin 3.07
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLSZ_N7000XXLSO_N7000XEFLS4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
I'm getting to the conclusion my SNote is semi-bricked and it needs a new PIT ; before triying it I'd like to have an "expert opinion" as adviced on many sites ; what do you think ? Should I give it a try or consider sending it to Samsung (2y warranty applicable it seems to me) ?
I'm currently downloading an older Firmware version just to give it one last try before PIT or sending to Samsung. (N7000XXLRI_N7000XEFLP2_XEF.zip)
Thx in advance,
Quinteen
Click to expand...
Click to collapse
Maybe this should prove of some help with the right Philz kernel:
http://forum.xda-developers.com/showthread.php?t=2384160
I think u have lost recovery and by flashing the right recovery, you can boot ur phone and take the next steps.

[Q] Help with flashing back to stock s5 at&t kitkak 4.4

I need some help, I installed a rooted lollipop 5.0 because my current 4.4 was buggy. Unfortunately lollipop 5.0 was even worse. Now I am trying to flash back to stock using odin, but I can't find kitkat 4.4 only 4.2 and I tried flashing to that and I keep receiving Auth- fail. So now my phone is soft bricked. I can only access download window and the recovery. I tried everything I cant get back to 4.4 nor lollipop 5.0 so please advice what to do. I I can get a download for kitkat 4.4 I would try flashing that maybe that will work. I have a at&t galaxy s5.

Nikedrop said:
I need some help, I installed a rooted lollipop 5.0 because my current 4.4 was buggy. Unfortunately lollipop 5.0 was even worse. Now I am trying to flash back to stock using odin, but I can't find kitkat 4.4 only 4.2 and I tried flashing to that and I keep receiving Auth- fail. So now my phone is soft bricked. I can only access download window and the recovery. I tried everything I cant get back to 4.4 nor lollipop 5.0 so please advice what to do. I I can get a download for kitkat 4.4 I would try flashing that maybe that will work. I have a at&t galaxy s5.
Click to expand...
Click to collapse
Try flashing the stock oca4 kernel. That's the stock lollipop kernel

michael872410 said:
Try flashing the stock oca4 kernel. That's the stock lollipop kernel
Click to expand...
Click to collapse
I didn't update to lollipop via update, i download a zip and installed it that way. I guess Ill give the stock lollipop kernel a try. Would you be able to post a link to the stock kernel, i cant find one for at&t.

Nikedrop said:
I didn't update to lollipop via update, i download a zip and installed it that way. I guess Ill give the stock lollipop kernel a try. Would you be able to post a link to the stock kernel, i cant find one for at&t.
Click to expand...
Click to collapse
If you are still on any 4.4. firmware ( 4.4.2 or 4.4.4), you should be able to flash the full 4.4.2 or 4.4. You will need to put the ap (pda), phone and csc. this will erase all of your data, but if you never took the 5.0 ota,you should be able to get to 4.4.x then root make sure you use odin and a good cable (not USB 3.0)

michael872410 said:
If you are still on any 4.4. firmware ( 4.4.2 or 4.4.4), you should be able to flash the full 4.4.2 or 4.4. You will need to put the ap (pda), phone and csc. this will erase all of your data, but if you never took the 5.0 ota,you should be able to get to 4.4.x then root make sure you use odin and a good cable (not USB 3.0)
Click to expand...
Click to collapse
I will try to a different cable (ive been using the 3.0 cable) Ive tried so many downloads of the 4.4.2 firmware and on all of the odin fails. I kept getting odin Auth failed. I tired using the csc,ap,cp all at once and separately but the only to successfully flash was cp modem. Would the 3.0 cable really make that big of a difference to not flash 3.0?

This is my odin error log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_G900AATT1ANCE_964333_REV00_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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<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)
and my phones log
odin mode
product name: SM-G900A
current Binary: Samsung Official
System status: Official
Reactivation lock(KK): off
KNOX warranty void:0X0
qualcomm secureboot: enabled (CSB)
UDC start
SYS REV CHECK FAIL(S) : Refer 2> Binary 1
Secure CHECK fail : system

Nikedrop said:
This is my odin error log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_G900AATT1ANCE_964333_REV00_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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<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)
and my phones log
odin mode
product name: SM-G900A
current Binary: Samsung Official
System status: Official
Reactivation lock(KK): off
KNOX warranty void:0X0
qualcomm secureboot: enabled (CSB)
UDC start
SYS REV CHECK FAIL(S) : Refer 2> Binary 1
Secure CHECK fail : system
Click to expand...
Click to collapse
If you took the OTA or sideloaded the OTA you _will not_ be able to downgrade from 5.0, if you did it through the flashfire method which does not upgrade the bootloader it is possible, but from what i can see, you sideloaded the ota zip which means you can't. Otherwise, the unbrick guide in the general section should work fine, and if not that's a perfect place to ask for help.

Rakuu said:
If you took the OTA or sideloaded the OTA you _will not_ be able to downgrade from 5.0, if you did it through the flashfire method which does not upgrade the bootloader it is possible, but from what i can see, you sideloaded the ota zip which means you can't. Otherwise, the unbrick guide in the general section should work fine, and if not that's a perfect place to ask for help.
Click to expand...
Click to collapse
So when i installed the zip through recovery that means I side loaded the ota zip? So what are my options? I tried to load the zip again but now it wont load, the phones just reboots. What can I do?
http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900a/ this is where in installed the 5.0 from. I guess it is ota :/

Nikedrop said:
So when i installed the zip through recovery that means I side loaded the ota zip? So what are my options? I tried to load the zip again but now it wont load, the phones just reboots. What can I do?
http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900a/ this is where in installed the 5.0 from. I guess it is ota :/
Click to expand...
Click to collapse
So is there anything I can do?

Nikedrop said:
So is there anything I can do?
Click to expand...
Click to collapse
Solved. So if anyone needs help let me know

yes,i need heelp dude. i was on 4.4.2 rooted with safestrap. i did a reset from inside safestrap and now the phone wont boot. it will however go into dl mode and i can access stock recovery. its like i wiped my OS... ive tried reflashing thru odin but i think im following the wrong thread. also most of the files im finding are broken

Nikedrop said:
Solved. So if anyone needs help let me know
Click to expand...
Click to collapse
What do you mean by solved? Did you successfully downgrade from 5.0 after taking the official ota?

mcnaught82 said:
What do you mean by solved? Did you successfully downgrade from 5.0 after taking the official ota?
Click to expand...
Click to collapse
No unfortunately I wasn't unable to downgrade but I was able to restore my phone back to lollipop after attempting to downgrade

Nikedrop said:
Solved. So if anyone needs help let me know
Click to expand...
Click to collapse
I need help i jusst softbricked mine trying to downgrade any ideas?

michael872410 said:
Try flashing the stock oca4 kernel. That's the stock lollipop kernel
Click to expand...
Click to collapse
Do you have a link for the stock kernel Odin ?

Help!
Nikedrop said:
Solved. So if anyone needs help let me know
Click to expand...
Click to collapse
I've got the same sitch:
odin mode
product name: SM-G900A
current Binary: Samsung Official
System status: Official
Reactivation lock(KK): off
KNOX warranty void:0X0
qualcomm secureboot: enabled (CSB)
AP SWREV: S1, T2, R1, A3, P1 (This line is not in the screen you saw based on what you listed earlier on this thread)
UDC start
SYS REV CHECK FAIL(S) : Refer 2> Binary 1
Secure CHECK fail : system

I have the same issue as you had how do I fix it?
Thanks

Nikedrop said:
Solved. So if anyone needs help let me know
Click to expand...
Click to collapse
Can you explain what you did to fix the problem?

Hi guys,i need help.i have G900A S5 with -oc4(5.0 stock).somebody nows how downdrade to -nce(4.4.2)?

Help restoring to stock | Odin wont work

Hello! So Im selling my tab s2 but I need it to be returned to stock to do so. Only part is odin fails on EVERY firmware I put through it and smart switch and Kies try to update but dont recognize while in bootloader mode. Below is the error Im getting. Ive tried pulling the PIT and flashing but no luck. Ive tried changing the port on my pc too but no luck.
Im on a T710 with a 5.1.1 rom installed. Any help would be much apreciated!
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the tablet I get "check fail device 2 binary 1" in red below everything in the top right.

I think that means you're flashing firmware that is below bootloader version. I had it happen. There is a 1B and 2B for bootloader version like on here
https://samsung-firmware.org/model/SM-T810/region/XAR/
I went in stupid mode and got it to flash ignoring that error and it darn near didn't boot at all. Nothing worked for me even 2B versions until I flash a good backup in recovery then odin went fine without that red error.

You're flashing the wrong firmware. You're trying to flash a revision 1 firmware on a device running revision 2 firmware.
You need an XXU2 firmware.

ashyx said:
You're flashing the wrong firmware. You're trying to flash a revision 1 firmware on a device running revision 2 firmware.
You need an XXU2 firmware.
Click to expand...
Click to collapse
Thanks! Im downloading T710XXU2CPH1 6.0.1 from sammobile but its downloading at 300 kb/s :crying: should I do this or flash the 5.1.1 revision 2 for anyone who wants root?

Sugardaddy_duncan said:
Thanks! Im downloading T710XXU2CPH1 6.0.1 from sammobile but its downloading at 300 kb/s :crying: should I do this or flash the 5.1.1 revision 2 for anyone who wants root?
Click to expand...
Click to collapse
Download it from UPDATO

ashyx said:
Download it from UPDATO
Click to expand...
Click to collapse
I cant thank you enough! Please tell me where you live so I can come hug you!

Sugardaddy_duncan said:
I cant thank you enough! Please tell me where you live so I can come hug you!
Click to expand...
Click to collapse
If you were female maybe lol. [emoji12]

T-Mobile G920T S6 downgrade 6.0.1 to 5.1

Hi, have a T-Mobile G920T S6 with 6.0.1 and want to downgrade to 5.11. Receiving the following odin FAIL error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU2BOFJ_G920FOXA2BOFJ_G920FXXU2BOFJ_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and following error on the phone:
"Sw rev check fail device 4 binary 2"
Tried (2) different original Samsung ROMs:
G920TUVU2COF6_G920TTMB2COF6_G920TUVU2COF6_HOME.tar.md5
on (2) different versions of Odin 10.+. No luck with any fixes in forums.
Any help would be greatly appreciated.
Thanks,
-Todd

cogancorp said:
Hi, have a T-Mobile G920T S6 with 6.0.1 and want to downgrade to 5.11. Receiving the following odin FAIL error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU2BOFJ_G920FOXA2BOFJ_G920FXXU2BOFJ_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and following error on the phone:
"Sw rev check fail device 4 binary 2"
Tried (2) different original Samsung ROMs:
G920TUVU2COF6_G920TTMB2COF6_G920TUVU2COF6_HOME.tar.md5
on (2) different versions of Odin 10.+. No luck with any fixes in forums.
Any help would be greatly appreciated.
Thanks,
-Todd
Click to expand...
Click to collapse
I thought I'd read that 6.0 was not going to prevent flashing back to 5.0 but I may be wrong. If I may inquire, what is your reasoning in wanting to go back to LP?

cwhiatt said:
I thought I'd read that 6.0 was not going to prevent flashing back to 5.0 but I may be wrong. If I may inquire, what is your reasoning in wanting to go back to LP?
Click to expand...
Click to collapse
Hi, thanks for the reply. All of the phones in our office are on 5.1 and we wanted to clone a new phone to save the time of setting up. We did a test run on 6.0.1 and the battery performance was horrible. Even on a rooted S6 phone with Greenify and most of the boatware frozen we got half the life as a 5.1. Let me know if you have any info on how to downgrade.
Thanks again for the note.
-Todd

coagncorp said:
Hi, thanks for the reply. All of the phones in our office are on 5.1 and we wanted to clone a new phone to save the time of setting up. We did a test run on 6.0.1 and the battery performance was horrible. Even on a rooted S6 phone with Greenify and most of the boatware frozen we got half the life as a 5.1. Let me know if you have any info on how to downgrade.
Thanks again for the note.
-Todd
Click to expand...
Click to collapse
Not sure of what MM setup you ran, but to each his own and if you like LP better by all means for what you like!
First question, you have a T model device correct? 920T or 925T?
I ask because I read that you mention a Tmo based device, but the tar file showing from your ODIN shot show a tar file meant for "F" device?
You will definitely want to make sure and use the correct file for your actual device! Maybe the shot was a generic one, IDK, but that is very important!
And to downgrade, I did this many times when MM first came out and I began my ROM update build.
Just check this post. Confirmed working and can be done in just a couple minutes.
The reason the odin fails at the sboot.img part is because if the screenshot is accurate and you tried flashing a F based tar on your T based device, it's because sboot.img is the bootloader and they aren't compatible with eachother.
Good luck and if you want the most customizable S6 rom for any device, check my OZOP v14 for LP and OZOP v5 is current MM build!
Hope the info works out for you!

coagncorp said:
Hi, thanks for the reply. All of the phones in our office are on 5.1 and we wanted to clone a new phone to save the time of setting up. We did a test run on 6.0.1 and the battery performance was horrible. Even on a rooted S6 phone with Greenify and most of the boatware frozen we got half the life as a 5.1. Let me know if you have any info on how to downgrade.
Thanks again for the note.
-Todd
Click to expand...
Click to collapse
Also, if you had a rooted S6, maybe try Deep Sleep battery saver over greenify. I have a flat S6 which is rooted and running stock firmware and Deep Sleep and I average about 17hours between charges with a 4hr 10min SOT.
Sent from my SM-G920T using XDA-Developers mobile app

stangdriver44 said:
Not sure of what MM setup you ran, but to each his own and if you like LP better by all means for what you like!
First question, you have a T model device correct? 920T or 925T?
I ask because I read that you mention a Tmo based device, but the tar file showing from your ODIN shot show a tar file meant for "F" device?
You will definitely want to make sure and use the correct file for your actual device! Maybe the shot was a generic one, IDK, but that is very important!
And to downgrade, I did this many times when MM first came out and I began my ROM update build.
Just check this post. Confirmed working and can be done in just a couple minutes.
The reason the odin fails at the sboot.img part is because if the screenshot is accurate and you tried flashing a F based tar on your T based device, it's because sboot.img is the bootloader and they aren't compatible with eachother.
Good luck and if you want the most customizable S6 rom for any device, check my OZOP v14 for LP and OZOP v5 is current MM build!
Hope the info works out for you!
Click to expand...
Click to collapse
Any ideas why i cannot downgrade, I perfer lollipop, and I have downgraded before, recently I jumped on your newest MM rom, and now I want to go back to Lollipop, but it wont allow me to flash the bootloader or modem, so I tried a whole firmware, and it still gives me this message

za33ck said:
Any ideas why i cannot downgrade, I perfer lollipop, and I have downgraded before, recently I jumped on your newest MM rom, and now I want to go back to Lollipop, but it wont allow me to flash the bootloader or modem, so I tried a whole firmware, and it still gives me this message
Click to expand...
Click to collapse
Just a noob question, what does apple has to do with android?

britchel said:
Just a noob question, what does apple has to do with android?
Click to expand...
Click to collapse
lol wow, I fixed it, wrong image attached.