So I have messed up somewhere along the way. I have a T-Mobile sm-t817t. Tablet only boots to "an error has occurred while updating the device software". I cannot get my odin v3 10.7 to see the Tab_S2_t817T_boot.zip file. So I tried to flash the Permissive Lollipop 5.1.1, t810_5.1.1_boot. Now tablet only boots to error. I can get into download mode. I tried to flash the [RECOVERY] TWRP 2.8.7.x Lollipop 5.0.2/5.1.1 - SMT810/T710 but write always fails. Error on tablet is "Custom Binary blocked by FRP". Is there anyway to recover from this? I have not tripped knox as far as I can tell, it's still at 0.
Well first of you tried to flash a zip in Odin which is impossible it needs to be flashed with twrp then you flashed a t810 kernel on a t817 device.
You need to download and flash the stock t817 firmware then disable frp lock aka OEM unlock in settings.
Thanks for the reply, I tried to flash TMB-T817TUVU1AOG8-20151020225336 but now get a new error "sw rev. check fail device 2 binary 1". Am I trying to flash the wrong file or something?
instanoodle said:
Thanks for the reply, I tried to flash TMB-T817TUVU1AOG8-20151020225336 but now get a new error "sw rev. check fail device 2 binary 1". Am I trying to flash the wrong file or something?
Click to expand...
Click to collapse
Where do you see this error odin or the device?
Have you extracted the md5 from the zip and loaded into the AP slot?
Does it pass the md5 hash check?
The error is on the device, "sw rev. check fail device 2 binary 1"
Tar file extracted and mounted in Odin normally.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<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> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Try flashing the OJ3 firmware, downgrade may be blocked.
ashyx said:
Try flashing the OJ3 firmware, downgrade may be blocked.
Click to expand...
Click to collapse
Where is that OJ3 Firmware?
I have the same problem.
mrch0x said:
Where is that OJ3 Firmware?
I have the same problem.
Click to expand...
Click to collapse
SamMobile
ashyx said:
SamMobile
Click to expand...
Click to collapse
I see OH7 and OJ4 but no sign of OJ3...
Sent from my SM-T710 using Tapatalk
mrch0x said:
I see OH7 and OJ4 but no sign of OJ3...
Sent from my SM-T710 using Tapatalk
Click to expand...
Click to collapse
It's there. Just download oj4
Related
Ok guys, so I flashed 5.1.1 on my phone but I lost root. So I decided to root using the Skipsoft Toolkit. I think it tried to install a bootloader (pretty sure it did). Before this I tried to use the chainfire root but didnt work. ok So then the phone started boot-looping and I decided to flash 4.4.4 back on. But now Odin keeps giving me this error
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1100)..
<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> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
On the phone side the error I'm getting is this:
Code:
UDC START
SW REV CHECK FAIL : [ABOOT]Fused 2 > Binary 1
[1] eMMC write fail: ABOOT
Idk what to do at this point. I'm assuming I have to flash the boot-loader right?
If I could get some advice, so I don't brick my phone further.
Please please please, help! v__v
If you mean latest 5.1.1 you most likely have updated Samsung kernel security that won't let you downgrade bootloader, you need to flash current stock firmware to recover your device.
Pp.
PanchoPlanet said:
If you mean latest 5.1.1 you most likely have updated Samsung kernel security that won't let you downgrade bootloader, you need to flash current stock firmware to recover your device.
Pp.
Click to expand...
Click to collapse
I tried flashing 5.1.1 But to no avail. Anything else I could do?
I had a similar problem with my note 3. What in did was I backed up my sd card and wiped it, redownloaded stock bootloader and firmwares, and used a different usb cable and port . Then odin worked like charm
My friend ended up putting 4.4.4 on it somehow. Maybe it was just an issue with my computer? Thank you guys for your suggestions btw. I tried all of them.
ChameleonQS said:
My friend ended up putting 4.4.4 on it somehow. Maybe it was just an issue with my computer? Thank you guys for your suggestions btw. I tried all of them.
Click to expand...
Click to collapse
Do you happen to have the link to the 4.4 build? I'm trying to downgrade from 5.1.1 as well
For the past couple of days I've been unable to unroot my device using Odin, which I have done many of times on the past. I went to Sammobile and got the latest firmware to flash back to stock, but everytime I attempt to do so the process Fails. USB Debugging is enabled so I don't have a clue what the problem could be. I will list some general information as well as the results of the Odin process below:
Baseband Version: N910TUVUD0K2
Odin process result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1DOK2_N910T3TMB1DOK2_N910T3UVU1DOK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Updated: I've stumbled across a thread here on XDA which has a mirror link to Stock TW Firmware/Bootloader/Modem N910TUVU2DOK2, and after flashing this mirror link using Odin... my phone now is unrooted and back to stock. Many thanks to ShrekOpher for posting the mirror link and here is a link to his post: http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
Same issue
I just posted about this same issue a couple of days ago, if you go to my only post ive done so far you can see how we are in the same boat. What were you using before you got to your problem, which custom ROM?
I had this problem on the note edge. What helped me was flashing cwm recovery and wiping everything
Trebor313 said:
For the past couple of days I've been unable to unroot my device using Odin, which I have done many of times on the past. I went to Sammobile and got the latest firmware to flash back to stock, but everytime I attempt to do so the process Fails. USB Debugging is enabled so I don't have a clue what the problem could be. I will list some general information as well as the results of the Odin process below:
Baseband Version: N910TUVUD0K2
Odin process result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1DOK2_N910T3TMB1DOK2_N910T3UVU1DOK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Click to expand...
Click to collapse
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Catfish197621 said:
I just posted about this same issue a couple of days ago, if you go to my only post ive done so far you can see how we are in the same boat. What were you using before you got to your problem, which custom ROM?
Click to expand...
Click to collapse
I'm currently using [DOK2] TEKXodus HYBRID N4 URv7
mdiaz33685 said:
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Click to expand...
Click to collapse
I check and made sure that the reactivation lock was disabled, but it still didn't work. I guess I will keep an eye open to see if this issue can get resolved sometime in the near future
mdiaz33685 said:
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Click to expand...
Click to collapse
What are the odin settings for doing this install? I can't get it to recognize the file
Nevermind, quick google showed i should extract the file which im not used to doing for roms and use "AP"
waywardfrantz said:
What are the odin settings for doing this install? I can't get it to recognize the file
Nevermind, quick google showed i should extract the file which im not used to doing for roms and use "AP"
Click to expand...
Click to collapse
U have to unziip the firmware and in Odin u need to goto AP and point to the firmware... sometimes i have to remove the extention .md5 after u unzip the firmware depending on which Odin u use...
make sure u have the samsung drivers installed..
mdiaz33685 said:
U have to unziip the firmware and in Odin u need to goto AP and point to the firmware... sometimes i have to remove the extention .md5 after u unzip the firmware depending on which Odin u use...
make sure u have the samsung drivers installed..
Click to expand...
Click to collapse
I can't Odin to stock unless I change the name of the firmware file to .tar. it skips the md5 check I believe.
---------- Post added at 06:17 PM ---------- Previous post was at 06:14 PM ----------
Also go to supersu and do a full unroot before. I'm thinking maybe the supersu backup script could cause issues too
Hey guys I am was going from rooted 4.4 to 5.1.1 and running the dynamic kat rom...I downgraded to stock 4.4 and attempted to update through Kies...well the update hung at 87% for a long time and eventually failed, I got the "system encounted a firmware issue " error and was unable to restart...Kies will not recognize my note no matter how many times I flash the drivers and Odin always fails no matter the version I try to flash...Even SmartSwitch says "device failed to recognize", and I cannot flash twrp either (I even tried flashing PIT files which failed as well) (I still get a "comm4" connection in odin)
(4.4/5.0.1) <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<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> aboot.mbn
Had a similar issue too. Do an emergency recovery from kies. it will download latest stock firmware restore.
Kies cannot see my phone and I get odin error ; SW REV CHECK FAIL : [aboot]Fused2 > Binary 1 [1] eMMC write fail : ABO when I try to flash ANY rom
m33android said:
Kies cannot see my phone and I get odin error ; SW REV CHECK FAIL : [aboot]Fused2 > Binary 1 [1] eMMC write fail : ABO when I try to flash ANY rom
Click to expand...
Click to collapse
Have you tried a full internal wipe from recovery?
maybe retry 4.4.4 through ODIN and then moving forward?
up to date on modem/bootloader?
also, sometimes flashing in ODIN just fails for no apparent reason. when it does, you must unplug the phone, reboot the phone and enter bootloader mode again every time.
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]
hello friends i am unable to flash stock rom via odin. mine is n920c model uae. i tweeked previou rom for volte. few days back some thing happend and frp locked and to remove thet flashed some other combination file after that iam trying to flash rom. i can install old stock rom march 2017 rom of uae. but while flashing new january rom it shwoing message failed. help me please some one.
dandamatrix said:
hello friends i am unable to flash stock rom via odin. mine is n920c model uae. i tweeked previou rom for volte. few days back some thing happend and frp locked and to remove thet flashed some other combination file after that iam trying to flash rom. i can install old stock rom march 2017 rom of uae. but while flashing new january rom it shwoing message failed. help me please some one.
Click to expand...
Click to collapse
Post the Odin error screenshot and the check if that you have no modification done to stock January update file.
Just make sure by re-downloading a fresh & latest copy of your phone through Sammobile & flash through Odin.
i didnt make any modifications to the fresh file but same problem.
PRADEEPHONDA said:
Post the Odin error screenshot and the check if that you have no modification done to stock January update file.
Just make sure by re-downloading a fresh & latest copy of your phone through Sammobile & flash through Odin.
Click to expand...
Click to collapse
dandamatrix said:
i didnt make any modifications to the fresh file but same problem.
Click to expand...
Click to collapse
I asked you for a screenshot dude. If you need help you need to follow the words. Post screen shot of the error on odin. Check when the error occurs while flashing.
error occures at the system.img and immediate message faild in odin
PRADEEPHONDA said:
I asked you for a screenshot dude. If you need help you need to follow the words. Post screen shot of the error on odin. Check when the error occurs while flashing.
Click to expand...
Click to collapse
dandamatrix said:
error occures at the system.img and immediate message faild in odin
Click to expand...
Click to collapse
Then difinitely there is an corrupt file in the zip,
1; Unzip stock tar.md5 file through 7zip & remove system.img file.
2; Repack by choosing tar format/extension in 7zip.
3; Flash through Odin as usual & let me know. If it flashes without any error then you will have to re-download.
I TRIED WITH NEW INSTALLED FILE ALSO NO LUCK STILL SAME MESSAGE AS BELOW:
<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/004> Odin engine v(ID:3.1207)..
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> cm.bin
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PRADEEPHONDA said:
Then difinitely there is an corrupt file in the zip,
1; Unzip stock tar.md5 file through 7zip & remove system.img file.
2; Repack by choosing tar format/extension in 7zip.
3; Flash through Odin as usual & let me know. If it flashes without any error then you will have to re-download.
Click to expand...
Click to collapse
dandamatrix said:
I TRIED WITH NEW INSTALLED FILE ALSO NO LUCK STILL SAME MESSAGE AS BELOW:
<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/004> Odin engine v(ID:3.1207)..
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> cm.bin
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Dude what do you mean by newly installed file?
Post the version details of the file you are trying to flash through odin.
Screenshot of your existing version in settings about software information.