Having had enough trouble with Marshmallow ROMs for the Tab S 10.5 (T-Mobile) I've been trying to revert to the stock 5.0.2, maybe even try bumping back to 5.11, the last stable ROM I (could have sworn I) had, if I could find it.
But Odin fails when I try to load the MD5 file
<ID:0/003> 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/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It's possible that the error is the same and there's no problem with the PIT file, but I can't tell.
Tried with Odin versions 3.09, 10 and 11
I've also tried copying the MD5 to my SD card to try to load it in TWRP, but it can't find the file, only a couple ZIPs I used to install 6.0.2 so not sure if I can actually install a stock firmware that way
file - T807TUVU1BOE1_T807TTMB1BOE1_T807TUVU1BOE1_HOME.tar.md5
Any guesses what I'm missing?
VinniePB said:
Having had enough trouble with Marshmallow ROMs for the Tab S 10.5 (T-Mobile) I've been trying to revert to the stock 5.0.2, maybe even try bumping back to 5.11, the last stable ROM I (could have sworn I) had, if I could find it.
But Odin fails when I try to load the MD5 file
<ID:0/003> 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/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It's possible that the error is the same and there's no problem with the PIT file, but I can't tell.
Tried with Odin versions 3.09, 10 and 11
I've also tried copying the MD5 to my SD card to try to load it in TWRP, but it can't find the file, only a couple ZIPs I used to install 6.0.2 so not sure if I can actually install a stock firmware that way
file - T807TUVU1BOE1_T807TTMB1BOE1_T807TUVU1BOE1_HOME.tar.md5
Any guesses what I'm missing?
Click to expand...
Click to collapse
You need to put it in download mode first.
Did you install the Samsung USB drivers?
If that doesn't help, try another PC.
Both are done - tab's in download mode, and USB drivers installed.
I've modded this tablet alone a couple times, using Odin and just copying ZIPs to the tablet, so it's neither of those issues. Note the "Added!" message at the start of the session, so it got the connection to the device.
The pause between setup connection and the fail message is fairly long, a couple of minutes, so more like a timeout than an instant lack of connection.
Tried it in Administrator mode as well.
VinniePB said:
Both are done - tab's in download mode, and USB drivers installed.
I've modded this tablet alone a couple times, using Odin and just copying ZIPs to the tablet, so it's neither of those issues. Note the "Added!" message at the start of the session, so it got the connection to the device.
The pause between setup connection and the fail message is fairly long, a couple of minutes, so more like a timeout than an instant lack of connection.
Tried it in Administrator mode as well.
Click to expand...
Click to collapse
Try removing the ".md5" from the filename and trying again
Related
Is there a trick to getting the Epic EI22 Stock GB rooted?
Trying to root my wife's phone, because she's complaining of poor battery life.
I'm on a rooted Epic Touch, so I don't know the nuances of the EPIC 4G.
I tried to flash kernel-GB-3a.tar.md5 using odin 1.81 and it was on com4, successfully verified the checksum and tried to flash something, but failed to verify.
reference: http://forum.xda-developers.com/showthread.php?t=1307980
Has something changed recently with EI22 that makes it harder to root? I guess the oneclick method no longer works?
Has anyone successfully rooted from EI22 stock?
A little forum search in General will show you a "how to root the OTA or Google update". It requires a custom kernel like samurai, nubernel or shadowkernel. You can also simply Odin in CWM 5.0.2.7 without reboot checked. Remove from Odin, boot directly into CWM and flash a custom prerooted GB ROM.
Sent from my SPH-D700 using XDA App
Thanks kenny,
found it: http://forum.xda-developers.com/showthread.php?t=1339478
QBKing77 Videos are the greatest for info and how to's
trying to root, getting the following ODIN warning:
using: kernel-GB-3a.tar.md5 and ODIN 1.85 to flash, "auto-reboot" checked, F. Rest Time unchecked.
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
the box on the Upper Left says FAIL!, right above ID:COM :[com3]
badkarmah187 said:
trying to root, getting the following ODIN warning:
using: kernel-GB-3a.tar.md5 and ODIN 1.85 to flash, "auto-reboot" checked, F. Rest Time unchecked.
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
the box on the Upper Left says FAIL!, right above ID:COM :[com3]
Click to expand...
Click to collapse
Cable is probably going bad. Try it again without the battery in and using the computer and USB cords as power to get into download mode.
badkarmah187 said:
trying to root, getting the following ODIN warning:
using: kernel-GB-3a.tar.md5 and ODIN 1.85 to flash, "auto-reboot" checked, F. Rest Time unchecked.
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
the box on the Upper Left says FAIL!, right above ID:COM :[com3]
Click to expand...
Click to collapse
That's happened to me before. You either need to unplug and replug the USB cable or you need to unplug, reboot into download mode, and then replug in the USB cable. I can't remember which one was the fix and which one just annoyed me more.
OK, shortly after I posted the error message I soft bricked my phone. Probably a bad factory cable.
I used this post to Restore it back to Froyo,
[How to] Restore a semi-bricked Epic or Bring it back from the brink!: http://forum.xda-developers.com/showthread.php?t=1052813
Another words, I flashed to following:
victory_8G_100528.pit and SPH-D700-EC05-8Gb-REL.tar
I also used a non stock cable!
After this I was able to Flash ACSRecovery1.0.0.5.tar.md5, and than CleanGB.
I think the Baseband went back to EC05, should I flash the EI22 modem? (if there is one available)
There is no EI22 modem.bin file. There is a flashable delta for EC05toEI22 in the modems thread in the stickies in Development. I have found the modem works well.
Sent from my SPH-D700 using XDA App
I have been trying to fix my soft bricked Galaxy S3 for a couple of days and nearly tearing my hair out at this point...
Ok I installed a nightly and yep came up dirty. So I needed to restore it. Any help would be fantastic
So far I have tried 2 different computers, two different USB cables, all the different ports on each computer.
I have tried every Odin version and nothing seems to help. I have tried restoring the latest Samsung updates (back to stock) and a root ROM....nothing. Is there a way that I can reset the binary counter since I believe this to be the problem? i know I can download triangle away from the Google Play store but how do I put it in the phone that is soft bricked? I can put it in Recovery Mode or Download Mode but as you see fixing it with Odin has proved illusive.
The farthest I have gotten is this:
In Odin 3.04
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDMD5.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
For the the Samsung stock I only get as far as "leave the cs" then when I wipe the data/cache and reboot I get that dreadful Samsung logo and it stays that way for hours.
Help???
Thanks!
the.seeker said:
I have been trying to fix my soft bricked Galaxy S3 for a couple of days and nearly tearing my hair out at this point...
Ok I installed a nightly and yep came up dirty. So I needed to restore it. Any help would be fantastic
So far I have tried 2 different computers, two different USB cables, all the different ports on each computer.
I have tried every Odin version and nothing seems to help. I have tried restoring the latest Samsung updates (back to stock) and a root ROM....nothing. Is there a way that I can reset the binary counter since I believe this to be the problem? i know I can download triangle away from the Google Play store but how do I put it in the phone that is soft bricked? I can put it in Recovery Mode or Download Mode but as you see fixing it with Odin has proved illusive.
The farthest I have gotten is this:
In Odin 3.04
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDMD5.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
For the the Samsung stock I only get as far as "leave the cs" then when I wipe the data/cache and reboot I get that dreadful Samsung logo and it stays that way for hours.
Help???
Thanks!
Click to expand...
Click to collapse
this is why you should have a nandroid. try fully wiping and restart. if that doesn't work try to use a different odin and make sure you downloaded the correct firmware.
You posted this already in an existing thread maybe 15mins ago and I answered a few min ago. No need to double post. Just be patient. It can sometimes take a few hours or more before someone who knows how to help will come on and answer. Especially later in the evening during the week.
Sent from my SGH-T999L using xda premium
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925T_UVU2COF8_BASEBAND.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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I get this anytime I try to do a flash, not for sure what to do. kinda bricked right now, but been doing some research and I see that bthere is a PIT file i can flash back onto it? but I cant find it for the S6, do we have access to a PIT file yet? can anyone help me please?
I had a similar issue the last time I flashed a Custom ROM then tried flashing a firmware afterwards - I was able to get around by shutting down Odin completely - disconnect and reboot the phone in download mode after it fails by holding the volume down-power-home buttons - reconnect phone to PC then open up Odin. Might take 2 - 3 tries but eventually should work. Make sure you have the files in the right slot (BL/AP/CP) when you are flashing via Odin.
jlmnote said:
I had a similar issue the last time I flashed a Custom ROM then tried flashing a firmware afterwards - I was able to get around by shutting down Odin completely - disconnect and reboot the phone in download mode after it fails by holding the volume down-power-home buttons - reconnect phone to PC then open up Odin. Might take 2 - 3 tries but eventually should work. Make sure you have the files in the right slot (BL/AP/CP) when you are flashing via Odin.
Click to expand...
Click to collapse
sorry mi englesh (i`m brazilian)
I have same problem, buts after ( not a pit found) now is ( e: failed to mount )
helpe please.
Hello,
First, my note 2 stuck at boot logo.
When i try to enter recovery stuck about 15 seconds on logo after that says with red failed to mount /efs (no such file or directory) ; failed to mount /system (no such file or directory); failed to mount /cache (no such file or directory) ; failed to mount /cacahe/recovery/last_recovery (no such file or directory) ; failed to mount /data (no such file or directory).
I read that it would be something about a "rescue fireware" was a topic on the XDA forum but no link was not working.
Please help me fast!
Thx!
alex2003881 said:
Hello,
First, my note 2 stuck at boot logo.
When i try to enter recovery stuck about 15 seconds on logo after that says with red failed to mount /efs (no such file or directory) ; failed to mount /system (no such file or directory); failed to mount /cache (no such file or directory) ; failed to mount /cacahe/recovery/last_recovery (no such file or directory) ; failed to mount /data (no such file or directory).
I read that it would be something about a "rescue fireware" was a topic on the XDA forum but no link was not working.
Please help me fast!
Thx!
Click to expand...
Click to collapse
Same happened to my phone too and no luck. still stuck! Someone help please!
If you can boot into Odin mode, flash a stock rom from sammobile.com.
audit13 said:
If you can boot into Odin mode, flash a stock rom from sammobile.com.
Click to expand...
Click to collapse
I tryed this no result
What happened when you used Odin? Post the Odin log?
audit13 said:
What happened when you used Odin? Post the Odin log?
Click to expand...
Click to collapse
Nand write fail. Or Sometimes, complete write operation failed!
audit13 said:
What happened when you used Odin? Post the Odin log?
Click to expand...
Click to collapse
When i try to put rescue firware with odin says setup connection after that fail.
Tomorrow i'm going to samsung official service.
I'll comeback with edit!
karanvirkohli said:
Nand write fail. Or Sometimes, complete write operation failed!
Click to expand...
Click to collapse
What does the log actually say? It probably failed when trying to flash a certain file.
Did you try different USB cables and USB ports?
Flash repair firmware
4 file
Sent from my GT-N7100 using Tapatalk
Hey, sorry for hijacking your thread.
I have the same problem. I tried many different scenarios and I couldn't fix it. I gave up and went to Samsung and after 48hs I called finding out that they refused to fix it. Talked to the IT guy and he said he has no idea how to fix it and told me the only fix is to change the whole motherboard and he said its not suggested to do so as its expensive. I have no idea what I should do. I flashed custom recovery, stock recovery. Tried to separate the whole firmware and flash it piece by piece using the skipsoft tool. I tried flashing PIT files with custom recovery, stock recovery, stock rom I have tried multiple PIT files from multiple websites.
This happens when I try flashing stock rom downloaded by samfirm or sammobile.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNL1_N7100OJVFOD1_N7100XXUFOA1_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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
If I to flash a PIT file using any of the scenarios mentioned above I get this ( the 4 files repair rom in this example )
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_N7100XXDLJ2_422394_REV00_user_low_ship.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> CODE_N7100XXDLJ2_422394_REV00_user_low_ship.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> MODEM_N7100XXDLJ2_422394_REV00_user_low_ship.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_XEF_N7100OXADLJ2_422394_REV00_user_low_ship.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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
It will keep doing this forever until I unplug the cable. I'm running stock Kitkat 4.4.2 but all methods I find are for older versions with different bootloaders yet I still tried them as there are no recent fix from what I can find.
In the first situation, the sboot.bin causes an error because the bootloader in the ROM is older than the phone's current bootloader.
Did you try flashing the latest stock ROM from sammobile.com using Odin 3.07 in the PDA slot? Sammobile.com ROMs should only be unzipped once to yield a tar.md5 file and flashed in the PDA slot.
Tried different USB cables and USB ports?
audit13 said:
In the first situation, the sboot.bin causes an error because the bootloader in the ROM is older than the phone's current bootloader.
Did you try flashing the latest stock ROM from sammobile.com using Odin 3.07 in the PDA slot? Sammobile.com ROMs should only be unzipped once to yield a tar.md5 file and flashed in the PDA slot.
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Yes I did all that. Same error. If I extract the tar file and do another odin flashable tar using skipsoft tool it doesnt work, removing one file at a time didnt work either. I tried the latest on sammobile, the latest on sammobile for my country, and the latest from Samfirm for my country. I also tried using SmartSwitch and Kies recovery using the serial number and model number and they don't recognise the phone during downloading like about 60% of downloading it will show an error that it doesnt recognise it.
When flashing the sammobile.com tar.md5 file in Odin's PDA/AP slot, do you receive an error message? If yes, what is the error?
audit13 said:
When flashing the sammobile.com tar.md5 file in Odin's PDA/AP slot, do you receive an error message? If yes, what is the error?
Click to expand...
Click to collapse
Same exact error of post #10
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNL1_N7100OJVFOD1_N7100XXUFOA1_HOME.tar.md 5 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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
The ROM being flashed has a bootloader that is too old or the ROM is not meant for the phone.
The model # for the phone has been confirmed as being a gt-n7100 on the Odin screen?
audit13 said:
The ROM being flashed has a bootloader that is too old or the ROM is not meant for the phone.
The model # for the phone has been confirmed as being a gt-n7100 on the Odin screen?
Click to expand...
Click to collapse
Odin screen that is in download mode ? Yes it says GT-N7100.
You're using the latest ROM for the phone? Which country?
audit13 said:
You're using the latest ROM for the phone? Which country?
Click to expand...
Click to collapse
Yes. Egypt. I have used both latest on sammobile and download by using samfirm. I have tried both of them. I have tried indian and few other countries all lead to the same error.
Are you using the original Samsung cable?
audit13 said:
Are you using the original Samsung cable?
Click to expand...
Click to collapse
It is not the one that came with the phone but it is one that I bought from Samsung. I also tried few other cables that came with LG and Asus phones.
This morning I flashed Lineage 14.1 and there were no errors. But it got stuck at the Samsung logo during reboot. I waited about 15 minutes. I could not figure out how to fix it so I decided to flash the stock firmware using Odin. It passed but also got stuck at the same screen during reboot. Then I did a hard system recovery but still could not boot past the Samsung logo. After that I install Samsung Kies 3, but it said the phone is no longer supported. Then I tried Kies 2.6 but it said the phone SGH-M919 does not support initialization. Now I can't get to the system recovery screen anymore. It would say there is an issue with the firmware update and try again in Kies. I cannot flash the stock firmware in Odin anymore either. It would fail with a complete write error. I don't know what else to try. Please help me.
Did you confirm the phone's model # in download mode?
You tried different USB cables, different USB ports, and different versions of Odin?
What was the exact Odin error?
Yes, the model is correct SGH-M919. I've tried Odin 3.0.7 and 3.10.6. I used Odin 3.0.7 to root and install TWRP recovery using the same original Samsung USB cable. So the cable and port should be OK. I tried it again this morning and noticed it took a long time after the message "Get PIT for mapping.."
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried it again using a different USB port and this time it failed right away. I didn't see the line "Get PIT for mapping" this time. Here are the messages in Odin.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
I was using the USB ports at the front of the PC and none of them worked. I tried one port at the back and it worked. Thank you very much. I never thought this would make a difference because I use the ports in the front all the time with my other iPhones, iPads, USB memory sticks and never had a problem. I lost all my data on the phone but that's OK. I would not dare to install custom ROM again. It looked so easy in youtube videos. Thanks again.
Glad you got it working. I always use the ports at the back of my desktop because I find it more reliable than the front case ports.