Hi Guy, Trying to Flash my Samsung Tab S2 T810 with T810XXU2BOJ1
Got the stock ROM via SamMobile
No matter which Canada version of the stock ROM I use I get this same error.
Tablet will not load pass the welcome screen and cannot access anything but Odin mode.
Really stuck here guys.
Think I need a PIT file for SM-T810 32GB
Really need some help, Thanks in advance :fingers-crossed:
Error with Odin 3.12.5
<ID:0/004> 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/004> Odin engine v(ID:3.1205)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
I have got Factory T810XXU2BOJ1 firmware and uploaded it to Google.Drive.You can download it and try to flash with Odin.If you need PIT-file only you should unpack CSC......tar.Hope you know how to flash factory firmware.
Related
Hi
Can somebody help me with this problem
Firstly during an official update from 2.3.6 to 4.0.4 using KIES bombed out at 4% so soft bricked is what we call it!!!
Can only boot into download mode so using odin to wack on
"N7000XXLRG_N7000DBTLRG_DBT\N7000XXLRG_N7000DBTLRG_N7000XXLRB_HOME.tar.md5"
Following message appears in Odin
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRG_N7000DBTLRG_N7000XXLRB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<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> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006>
<ID:0/006> Receive Response form LOKE
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there anyway I can force write to it?
Could it be the firmware that is the issue or would I get this on everything I try?
Please help
Thanks
EFCLEE said:
Hi
Can somebody help me with this problem
Firstly during an official update from 2.3.6 to 4.0.4 using KIES bombed out at 4% so soft bricked is what we call it!!!
Can only boot into download mode so using odin to wack on
"N7000XXLRG_N7000DBTLRG_DBT\N7000XXLRG_N7000DBTLRG_N7000XXLRB_HOME.tar.md5"
Following message appears in Odin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006>
<ID:0/006> Receive Response form LOKE
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there anyway I can force write to it?
Could it be the firmware that is the issue or would I get this on everything I try?
Please help
Thanks
Click to expand...
Click to collapse
Did you select the firmware .tar file in odin PDA tab only?
This sometimes happens due to bad download file, try flashing some other firmware, preferably GB so that you can wipe if required.
search google with 'Receive Response form LOKE" and you will find lot of people having same issue and most of them able to resolve by flashing different firmware.
jeetu1981 said:
Did you selected the firmware .tar file in odin PDA tab only?
This sometimes happens due to bad download file, try flashing some other firmware, preferably GB so that you can wipe if required.
search google with 'Receive Response form LOKE" and you will find lot of people having same issue and most of them able to resolve by flashing different firmware.
Click to expand...
Click to collapse
No I have been adding it to PHONE, is this wrong?
Anyways I just tried it again adding to PDA and this time it gets stuck on
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRI_N7000OXXLP8_N7000XXLRB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
Any ideas?
EFCLEE said:
No I have been adding it to PHONE, is this wrong?
Anyways I just tried it again adding to PDA and this time it gets stuck on
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRI_N7000OXXLP8_N7000XXLRB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
Any ideas?
Click to expand...
Click to collapse
Yes, its completely wrong, you should select single firmware .tar in PDA tab only. Try again by rebooting your phone and check if you have kies running, if so close it completely.
SUGGESTION- Do not flash ICS stock rom now, I am not sure what has been messed up by flashing this using phone tab (ICS phone files on GB base, not sure), best is flash stock GB firmware first, then wipe in stock recovery and flash ICS.
jeetu1981 said:
Yes, its completely wrong, you should select single firmware .tar in PDA tab only. Try again by rebooting your phone and check if you have kies running, if so close it completely.
SUGGESTION- Do not flash ICS stock rom now, I am not sure what has been messed up by flashing this using phone tab (ICS phone files on GB base, not sure), best is flash stock GB firmware first, then wipe in stock recovery and flash ICS.
Click to expand...
Click to collapse
WOW!!! Restarted phone wacked it into PDA and BAM!! started to copy over!!!
A million thank you's Jeetu1981 your a fkin diamond!!!!!
EFCLEE said:
WOW!!! Restarted phone wacked it into PDA and BAM!! started to copy over!!!
A million thank you's Jeetu1981 your a fkin diamond!!!!!
Click to expand...
Click to collapse
Cool... Consider urself lucky this time
And click on thanks is better than million thanks, lol
Sent from my GT-N7000
Dear all,
I found a new firmware on sammobile site and thought to upgrade my Galaxy note from:
N7000JPLPD_N7000OJPLP7_N7000XXLPT_HOME.tar.md5
to:
N7000JPLR8_N7000OJPLR8_N7000XXLRK_HOME.tar.md5
(Both of them for Pakistan)
First I used Odin 1.83 to flash but after about 20% the Odin turned red indicating 'Fail'
Then I searched the web and (I know it's my fault) somewhere downloaded Odin 1.85, checked all the fields on Odin, like "Re Partition- Autoboot-F reset time"
I check them all and then another mistake.... used the same MD5 file in all 3 'PDA, PHONE, CSC" and flashed again.
And also used the PIT file which was in the Odin 1.85's folder.
Now I can enter the download mode but if I try to flash the new ROM, it goes upto 20% and says something like this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000JPLR8_N7000OJPLR8_N7000XXLRK_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> hidden.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And If I flash the older ROM it says like:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000JPLPD_N7000OJPLP7_N7000XXLPT_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> cache.img
<ID:0/008> NAND Write Start!!
<ID:0/008> factoryfs.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help
sulemani1 said:
Dear all,
I found a new firmware on sammobile site and thought to upgrade my Galaxy note from:
N7000JPLPD_N7000OJPLP7_N7000XXLPT_HOME.tar.md5
to:
N7000JPLR8_N7000OJPLR8_N7000XXLRK_HOME.tar.md5
(Both of them for Pakistan)
First I used Odin 1.83 to flash but after about 20% the Odin turned red indicating 'Fail'
Then I searched the web and (I know it's my fault) somewhere downloaded Odin 1.85, checked all the fields on Odin, like "Re Partition- Autoboot-F reset time"
I check them all and then another mistake.... used the same MD5 file in all 3 'PDA, PHONE, CSC" and flashed again.
And also used the PIT file which was in the Odin 1.85's folder.
Now I can enter the download mode but if I try to flash the new ROM, it goes upto 20% and says something like this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000JPLR8_N7000OJPLR8_N7000XXLRK_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> hidden.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And If I flash the older ROM it says like:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000JPLPD_N7000OJPLP7_N7000XXLPT_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> cache.img
<ID:0/008> NAND Write Start!!
<ID:0/008> factoryfs.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help
Click to expand...
Click to collapse
Hi friend just try flashing to GB and then to any other.
Use company cable for data transfer, try with another usb port and i hope it must get cleared.
Press THANKS if it helped you
Thank you my friend, but could you guide me where to find GB? And what GB actually is? The older 2.3.6 Ginger bread?
sulemani1 said:
Thank you my friend, but could you guide me where to find GB? And what GB actually is? The older 2.3.6 Ginger bread?
Click to expand...
Click to collapse
GB actually is the older 2.3.6 Ginger
you find GB in sammobile site
If it's failing at factory.fs then you could be in longer term trouble, let us know.
Sent from my GT-N7000 using xda premium
dude... try this,,
just pull out the battery. wait for 10 secs.. reinsert. go back to download mode.. use odin 1.85 and just select the tar.md5 fine in pda section.. donot check repartion.. dont use pit file.
PS: if odin is stuck once.. u cannot continue from there.. the phone needs a reboot for another try
I read somewhere saying that flashing pit file must be accompanied by bootloader or your device might brick.
Sent from my GT-N7000 using xda premium
nokiamodeln91 said:
dude... try this,,
just pull out the battery. wait for 10 secs.. reinsert. go back to download mode.. use odin 1.85 and just select the tar.md5 fine in pda section.. donot check repartion.. dont use pit file.
PS: if odin is stuck once.. u cannot continue from there.. the phone needs a reboot for another try
Click to expand...
Click to collapse
Thanks friend.
I did it. Im ok now.
Thanks to all of you who helped me here.
hi,
well i have a galaxy gear v700, and i tryed to flash it before but i couldnt do well, after it i think it has a brick . but using this tutorial http://forum.xda-developers.com/showthread.php?t=2776157 i give my watch a new life, now i want to upgrade to tizen and i cant, kies tell me that the firmware was modify and no upgrade avable, and when i try to put a rom odin doesnt load, and stop on the last point that i show here what can i do to upgrade to tizen
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> kernel-GB-3a.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
my Smart Watch Bloked
samsung tizen not responding
sir,
i own a samsung tizen z1 ,the device is not responding only logo sign is shown, i decided to flash it but md5 bootloader is locked so not able to flash -using odin software i need bootloader file to flash it and unlock it.. plz help
radekamilo said:
hi,
well i have a galaxy gear v700, and i tryed to flash it before but i couldnt do well, after it i think it has a brick . but using this tutorial http://forum.xda-developers.com/showthread.php?t=2776157 i give my watch a new life, now i want to upgrade to tizen and i cant, kies tell me that the firmware was modify and no upgrade avable, and when i try to put a rom odin doesnt load, and stop on the last point that i show here what can i do to upgrade to tizen
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> kernel-GB-3a.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
Click to expand...
Click to collapse
Hello.
Recently my phone got stuck so i decided to reboot it, after reboot theres just a logo screen.
Recovery mode doesnt work.
Charging works (but after yesterday's manipulations charging logo is turning on but seem to be stuck either (though i guess its working just not animated anymore)).
Download mode works.
My OS was Cyanogen (i dont remember version).
I am kinda newbie but i ve read some stuff on the intenet and tried to solve the problem with Odin. I used N7000XXLSZ_N7000OXELS7_N7000XXLSO_FACTORY_SER with Odin versions: 1.83, 1.85 and 1.87 with
boxes checked PDA, PHONE, CSS.
1. Odin 1.85 is getting stuck on "NAND Write Start".
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000XXLSZ_906407_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7000XXLSO_REV_05_CL1240075.tar.md5 is valid.
<OSM> CSC_OXE_N7000OXELS7_975051_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
2. Odin 1.83 is getting stuck on "zImage".
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000XXLSZ_906407_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7000XXLSO_REV_05_CL1240075.tar.md5 is valid.
<OSM> CSC_OXE_N7000OXELS7_975051_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
3. Odin 1.87 is getting stuck on "NAND Write Start".
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000XXLSZ_906407_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7000XXLSO_REV_05_CL1240075.tar.md5 is valid.
<OSM> CSC_OXE_N7000OXELS7_975051_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
I ve tried about 5+ times with each version.
You are my last hope fellas
Try just flashing an Odin version of philZ kernel. Also try another laptop with freshly installed samsung USB drivers.
Flash PhilZ kernel from Odin 3.07. After this, you'll have working PhilZ Touch Recovery
Try flashing philz cwm as they said or try flashing a stock ROM from sammobile.com .. And only use PDA and untick auto reboot ..
I tried to root my phone today and I failed and my phone is not working right now. Does anybody know how to fix it? Can someone please help me? Please!!! Thank you so much.
hxsports said:
I tried to root my phone today and I failed and my phone is not working right now. Does anybody know how to fix it? Can someone please help me? Please!!! Thank you so much.
Click to expand...
Click to collapse
My phone current is look like this. And I tried Odin flash and the process is failed.
<ID:0/004> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 332 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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> abl.elf
<ID:0/004> xbl.elf
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
hxsports said:
My phone current is look like this. And I tried Odin flash and the process is failed.
<ID:0/004> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 332 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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> abl.elf
<ID:0/004> xbl.elf
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
My phone stuck in Download mode right now and it shows
partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0INDIVLDUMT_EDRHS_IMTHSGAUEMSAC
if your phone won't boot because of verified boot, either flash back to stock or flash vbmeta_disabled.tar
if you tried to patch your boot.img this wouldn't really be a problem because magisk patches vbmeta for you when you patch.
if you tried to flash a magisk zip you should have followed instructions for twrp which requires flashing vbmeta_disable.tar in Odin. in other words you couldn't have followed instructions.
hxsports said:
I tried to root my phone today and I failed and my phone is not working right now. Does anybody know how to fix it? Can someone please help me? Please!!! Thank you so much.
Click to expand...
Click to collapse
bootloader is locked!! You got a US phone version, you can not Root neither install a custom Rom or TWRP.
Download the last official Rom for your phone, and flash it through Odin. Then your phone will work again.
3mel said:
if your phone won't boot because of verified boot, either flash back to stock or flash vbmeta_disabled.tar
if you tried to patch your boot.img this wouldn't really be a problem because magisk patches vbmeta for you when you patch.
if you tried to flash a magisk zip you should have followed instructions for twrp which requires flashing vbmeta_disable.tar in Odin. in other words you couldn't have followed instructions.
Click to expand...
Click to collapse
I can't flash anything into it because it say OEM lock and
hxsports said:
I can't flash anything into it because it say OEM lock and
Click to expand...
Click to collapse
flash the correct stock firmware for your phone and nothing else. if you have an American FE there's NOTHING ELSE that will work on it.
3mel said:
flash the correct stock firmware for your phone and nothing else. if you have an American FE there's NOTHING ELSE that will work on it.
Click to expand...
Click to collapse
Correct. There are sites, from where you may download the last available firmware for your phone!
Download it and flash it correctly with Odin, and it will work.
Download SM-G781U1 / Galaxy S20 Fan Edition 5G SM-G781U1 XAA in Samfw - Samsung firmware download
SM-G781U1 / Galaxy S20 Fan Edition 5G SM-G781U1 XAA samsung firmware download all model, lastest, fast update, completely free and fast speed in Samfw.com ✅
samfw.com
Download the latest one for US version for this phone, currently they jumped to bootloader v.7
Carreful, I gave you a link for S20 FE 5G !! If you got S20 FE 4G, download the adequate one.