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.
Related
I apparently did not do enough reading prior to trying to downgrade my AT&T S5 to 4.4.2 after taking the OTA 5.0 update.
I am now stuck at either the 'firmware upgrade failed' or phone constantly going to the recovery menu (depending on if i've tried to push an AP file via Odin).
I know understand downgrading is impossible at this point, but I'm trying to find a way to get my phone back up and running. Any assistance on what file(s) I can push via Odin to resolve would be greatly appreciated. My device was not rooted prior to the OTA lollipop update so I'm limited to the 'stock' recovery options.
DamnYank! said:
I apparently did not do enough reading prior to trying to downgrade my AT&T S5 to 4.4.2 after taking the OTA 5.0 update.
I am now stuck at either the 'firmware upgrade failed' or phone constantly going to the recovery menu (depending on if i've tried to push an AP file via Odin).
I know understand downgrading is impossible at this point, but I'm trying to find a way to get my phone back up and running. Any assistance on what file(s) I can push via Odin to resolve would be greatly appreciated. My device was not rooted prior to the OTA lollipop update so I'm limited to the 'stock' recovery options.
Click to expand...
Click to collapse
You need to flash the OC4 stock kernel.
muniz_ri said:
You need to flash the OC4 stock kernel.
Click to expand...
Click to collapse
Muniz, i would be more than happy to. I've been searching though for a 5.0 sm-g900a tar/md5 file that i can load/flash via Odin but I have not been able to find any (other than a 'pre-rooted' one but I want to stay stock/ unrooted if possible).
Do you have any tips on where I could find it?
Thank you!
muniz_ri said:
You need to flash the OC4 stock kernel.
Click to expand...
Click to collapse
I found your other thread, i tried using your G900A_OC4_Stock_Rooted_Firmware.tar.md5 file via Odin and selecting it for the AP field. When executing, Odin gives me:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900A_OC4_Stock_Rooted_Firmware.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> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
And the phone screen shows SECURE CHECK FAIL: system
It looks like I was able to resolve with the info in this post:
http://forum.xda-developers.com/att...phone-trying-to-downgrade-to-4-t3076706/page4
Sorry for not finding that sooner, usually my search-fu is pretty solid but my searches just weren't hitting that (or Muniz's other stock files available from androidfilehost).
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)?
https://www.androidfilehost.com/?fid=24499762635997683
I posted it in the Marshmallow Update Thread..
I thought it would get lost in the mix so I wanted to give it's own thread..
Edit: Please do not try to flash the .Zip in recovery.. this is just a compressed file. Unzip and you can flash this using ODIN..
I recommend a factory reset before flashing..
Stock, rooted or details?
Sent from my SM-G920T using XDA Premium 4 mobile app
Maddball said:
Stock, rooted or details?
Sent from my SM-G920T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It literally just came out today for the SM-G920T so my guess is this is stock.
what would be the best way to flash this if i'm on a custom ROM right now?
just regular flash through ODIN?
tflogic said:
what would be the best way to flash this if i'm on a custom ROM right now?
just regular flash through ODIN?
Click to expand...
Click to collapse
Put the .tar into PDA and flash. You'll have to install your recovery again through ODIN also. I haven't been able to find a root unless you use a universal kernel in the s6 thread or in the unified development thread. I'm DL'ing now. I'll post after I try a few kernels compatible.
magda623 said:
Put the .tar into PDA and flash. You'll have to install your recovery again through ODIN also. I haven't been able to find a root unless you use a universal kernel in the s6 thread or in the unified development thread. I'm DL'ing now. I'll post after I try a few kernels compatible.
Click to expand...
Click to collapse
according to this post, SuperSU Beta seems to be working fine.
tflogic said:
according to this post, SuperSU Beta seems to be working fine.
Click to expand...
Click to collapse
Possibly. However, there is no recovery for our device listed on the recovery page. The fact that recovery breaks the boot.img without root sounds shaky though. I'll try it a few different ways. DL is done. Flashing now.
Zaphodspeaks said:
https://www.androidfilehost.com/?fid=24499762635997683
I posted it in the Marshmallow Update Thread..
I thought it would get lost in the mix so I wanted to give it's own thread..
Click to expand...
Click to collapse
Think I flash this on my.metro pcs version I flashed the tmobile 5.1.1 update on my metro pcs version it's basically the same phone
Maddball said:
Stock, rooted or details?
Sent from my SM-G920T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is 100 percent stock.. from Sam Mobile..
Hell it came out early this morning.. No one has had the time yet to make a custom version..
I don't recommend updating from a Custom ROM..
If your 100 percent 5.1.1 Stock you can flash this with ODIN with no problems..
Oh its a Zipped .Tar file.. Don't try to flash the Zip.. Again do NOT try and flash the .Zip.. it will fail and you will be stupid to try..
https://support.t-mobile.com/docs/DOC-21138
Pros:
- Fast
- Beautiful UI
- New functions
- Ram Management has been fixed
- Better battery life
Cons:
- Lost some important functions
Sent from my SM-G920T using XDA-Developers mobile app
i have a sm-g920t with an argentinian sim my firmware is G920TUEU3COK1. Can i use my SIM in this firm?
adidas123 said:
Pros:
- Fast
- Beautiful UI
- New functions
- Ram Management has been fixed
- Better battery life
Cons:
- Lost some important functions
Sent from my SM-G920T using XDA-Developers mobile app
Click to expand...
Click to collapse
Which functions? I haven't noticed anything missing so far.
I'm having trouble flashing this in Odin (3.09). It gets stuck at NAND Write Start! I tried several times. I even waited 15 minutes, but no progress. Is this because the TAR file is 3.6 GB? My computer recognizes my phone's USB connection. Earlier tonight I flashed a TAR file for my Galaxy Tab S without a problem. So weird. I tried different USB ports and reinstalled the drivers.
Here's what ODIN shows:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
Hi,
I tried to flash this using odin but it did not work so I went ahead and used Samsung Smart Switch that automatically downloads 6.0.1 and flashes it. The process, however, failed and now the phone (G920T) is stuck on a blue screen that says, "An error has occurred while updating the system software. Use emergency recovery function in the Smart Switch PC software." (image: http://i.imgur.com/t401aO6.png). Rebooting the phone takes me to the same place. I'm, however, able to get into download mode. I have tried the emergency recovery in download mode as specified by this video: https://www.youtube.com/watch?v=mi7O0OvnS2E, but it still fails, giving me this error: http://i.imgur.com/t401aO6.png. Could someone help me get my phone working?
A few notes:
- My previous firmware was 5.1.1 stock, however, I had flashed a rooted kernel using odin.
- Within download mode, it says the following: swrev b:3 k:2 s:2
Thank you in advance.
EDIT: flashing with odin gives me this error: http://i.imgur.com/oGZiCow.png
HKSpeed said:
I'm having trouble flashing this in Odin (3.09). It gets stuck at NAND Write Start! I tried several times. I even waited 15 minutes, but no progress. Is this because the TAR file is 3.6 GB? My computer recognizes my phone's USB connection. Earlier tonight I flashed a TAR file for my Galaxy Tab S without a problem. So weird. I tried different USB ports and reinstalled the drivers.
Here's what ODIN shows:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
Click to expand...
Click to collapse
You using an older version of ODIN
Try Odin3_v3.10.7
Need help, Im looking for the latest modem and bootloader for this. Just the bootloader and modem. Thanks!
Zaphodspeaks said:
You using an older version of ODIN
Try Odin3_v3.10.7
Click to expand...
Click to collapse
Thanks. That worked. I didn't know there was a newer version available.
I don't suppose there will be a recovery-flashable version of this one, will it?
HKSpeed said:
I'm having trouble flashing this in Odin (3.09). It gets stuck at NAND Write Start! I tried several times. I even waited 15 minutes, but no progress. Is this because the TAR file is 3.6 GB? My computer recognizes my phone's USB connection. Earlier tonight I flashed a TAR file for my Galaxy Tab S without a problem. So weird. I tried different USB ports and reinstalled the drivers.
Here's what ODIN shows:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
Click to expand...
Click to collapse
Maybe try redownloading the file and unzipping again
---------- Post added at 04:56 PM ---------- Previous post was at 04:54 PM ----------
BigDaddy38 said:
Maybe try redownloading the file and unzipping again
Click to expand...
Click to collapse
What Odin Are you using?
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]
note 5 N920T
Successfully flashed Sick/Flu ROM about 2-weeks ago and it was (is) excellent. It was like getting an entirely new phone in battery life and speed. Long story short, tried to add fingerprint scans and bricked it--only to find out this was the one caveat to the ROM. So proceeded to reflash ROM while talking with family during Thanksgiving--I had really prepared the first time and felt pretty comfortable doing it again--but not being focused I ended up deleting the wrong information and soft bricking it.
At this juncture the only item still visible on the internal drive is TWRP. I AM able to boot into ODIN mode and the software does recognize my phone and I am also able to boot into TWRP. Other than that I do not have any OS on the phone at this time. I've downloaded the original firmware, but multiple attempts at flashing it have failed. Hours and hours of reading it seems that I may be missing a PIT file (?), but I haven't been able to confirm that is the actual problem or locate the specific N920T PIT file anyways. Seems like many of the discussion strings died in 2015
I can provide more details about the failure messages I read on ODIN and my phone during reflash attempts if anyone has the patience and time to help me. I spent essentially 13 hours straight all over the internet with no success and am reaching the point of throwing it into a fire
<ID:0/006> 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/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Attempts at flashing stock ROM.
Please does anyone have suggestions? I have scoured all prior threads in this regard and had no success
Wyattthomas said:
<ID:0/006> 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/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Attempts at flashing stock ROM.
Please does anyone have suggestions? I have scoured all prior threads in this regard and had no success
Click to expand...
Click to collapse
If you need the PIT file you can get it here but you'll have to create an account in order to see the download links.
http://www.sammobile.com/forum/showthread.php?t=30106
By the way don't use an old firmware, you have to use the very last firmware you were using before ever doing anything to it.
I did find the PIT file several hours ago and it doesn't appear to have been the problem. Its actually the only file that will "successfully" flash on the phone.
I've tried flashing the original android firmware that was on device originally as well as the most recent android firmware. Between each attempt the computer and phone were reset. No dice.
Wyattthomas said:
I did find the PIT file several hours ago and it doesn't appear to have been the problem. Its actually the only file that will "successfully" flash on the phone.
I've tried flashing the original android firmware that was on device originally as well as the most recent android firmware. Between each attempt the computer and phone were reset. No dice.
Click to expand...
Click to collapse
Have you tried booting into recovery and flashing a downloaded rom? You should be able to get into twrp and then flash from there... If you can't get into twrp then reflash twrp and try again.
MrMike2182 said:
Have you tried booting into recovery and flashing a downloaded rom? You should be able to get into twrp and then flash from there... If you can't get into twrp then reflash twrp and try again.
Click to expand...
Click to collapse
WELL-------IT flippin' worked!!!!!!!!!!!!!1
So I HAD also tried flashing the new ROMs with TWRP several times before but that wasn't working either. Later on I realized that I was off by a couple months on the latest Android 6.1.1. update and repeated ODIN flashes with new bootloaders/PIT files etc all continued to fail. Didn't think about trying the TWRP flash again
I am going out for a drink. This phone ruined my Thanksgiving, but for the records I'm immediately flashing the Sick as Hell ROM again. I know exactly how to do it in my sleep now. AVOID USING FINGERPRINT lock and it is otherwise an amazing ROM. Fast, Fast, Fast, and battery goes all damn day. Spotify hack is wonderful too.
Wyattthomas said:
WELL-------IT flippin' worked!!!!!!!!!!!!!1
So I HAD also tried flashing the new ROMs with TWRP several times before but that wasn't working either. Later on I realized that I was off by a couple months on the latest Android 6.1.1. update and repeated ODIN flashes with new bootloaders/PIT files etc all continued to fail. Didn't think about trying the TWRP flash again
I am going out for a drink. This phone ruined my Thanksgiving, but for the records I'm immediately flashing the Sick as Hell ROM again. I know exactly how to do it in my sleep now. AVOID USING FINGERPRINT lock and it is otherwise an amazing ROM. Fast, Fast, Fast, and battery goes all damn day. Spotify hack is wonderful too.
Click to expand...
Click to collapse
Create a full backup first so you have something to fall back on and restore if anything goes wrong again.
MrMike2182 said:
Create a full backup first so you have something to fall back on and restore if anything goes wrong again.
Click to expand...
Click to collapse
First thing I did. I've since backed it up about 3 more times...never again will I make that fatal error.