So I was trying to wipe my tablet in order sell it. It had Cyanogenmod 9.0 on it. After I factory wiped, it was stuck in a boot loop. Wouldn't get past the Cyanogenmod boot screen before it rebooted.
So I tried going into CWM recovery and reflashing Cyanogenmod. Once I did that, it now boots up onto the "Firmware upgrade encountered an issue" screen and won't go to anything else.
If I try to put it into either recovery or download, it just turns off then goes back to the same screen. I've tried to use Kies to restore it and nothing. Tried Odin and this comes up
"<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3113_CWM_RECOVERY-6.0.1.1_SUPERSU-0.96_BUSYBOX-1.20.2.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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)"
I have no idea what to do past this. Any help would be greatly appreciated.
Tab 2 firmware upgrade encountered an issue a solution
Zargari said:
So I was trying to wipe my tablet in order sell it. It had Cyanogenmod 9.0 on it. After I factory wiped, it was stuck in a boot loop. Wouldn't get past the Cyanogenmod boot screen before it rebooted.
So I tried going into CWM recovery and reflashing Cyanogenmod. Once I did that, it now boots up onto the "Firmware upgrade encountered an issue" screen and won't go to anything else.
If I try to put it into either recovery or download, it just turns off then goes back to the same screen. I've tried to use Kies to restore it and nothing. Tried Odin and this comes up
"<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3113_CWM_RECOVERY-6.0.1.1_SUPERSU-0.96_BUSYBOX-1.20.2.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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)"
I have no idea what to do past this. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I had the same problem, kies didn't work, neither did odin. I used every fix suggestion I could find.
It finally dawned on me that the battery was holding everything in place. I took off the back of my Tab 2 and removed
the battery. I re-installed the battery after 10 minutes and was able to re install a stock rom. I hope thishelps.
Related
I am not responsible if you brick your phone although you are likely soft bricked if you are reading this guide. This is how I successfully restored after flashing a T959 Odin rom/pit, I had to use a Jig after to get into download mode then was provided the necessary files by cnote74 on the following thread
http://forum.xda-developers.com/showthread.php?t=978836&page=16
Here is a Jig on Amazon, I bought mine on Ebay for 3 dollars.
http://www.amazon.com/SainSmart-Dongle-Samsung-Captivate-Vibrant/dp/B0053H73JQ
1.Open Odin.
2.Remove your memory and sim card
3.Boot your T959V into Download mode (Hold volume up + volume down then plug in your usb cable)
4.In Odin check Re-Partition, Auto Reboot, F.Reset Time
5.Select Sgs4g.pit for the PIT file
6.Select T959VUVKC1-REV00-ALL-low-CL933594.tar.md5 for PDA
7.Select T959VUVKC1-Phone-CL932707.tar.md5 for Phone
8.Select SGH-T959V-CSC-TMB.tar.md5 for CSC
9.Click start.....
10.Success!
D/L
Odin
KC1
Thought i saw something like this before, but nonetheless, thanks for this.
Sent from my rockin' Galaxy S 4G using XDA Premium App
Sorry to bump up an old thread, if anyone help who is familiar enough to help me with this, I really do appreciate.
Basically, I can't boot into the phone and I am currently stuck on "Firmware upgrade encountered an issue" error screen (http://androidcentral.us/wp-content/uploads/2013/09/Firmware-upgrade-error.png) whenever I boots up. I tried the step above on odin and it is giving the following error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T959VUVKC1-REV00-ALL-low-CL933594.tar.md5 is valid.
<OSM> T959VUVKC1-Phone-CL932707.tar.md5 is valid.
<OSM> SGH-T959V-CSC-TMB.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..
<OSM> All threads completed. (succeed 0 / failed 1)
May I know what does this mean and what else can I try?
wyst said:
Sorry to bump up an old thread, if anyone help who is familiar enough to help me with this, I really do appreciate.
Basically, I can't boot into the phone and I am currently stuck on "Firmware upgrade encountered an issue" error screen (http://androidcentral.us/wp-content/uploads/2013/09/Firmware-upgrade-error.png) whenever I boots up. I tried the step above on odin and it is giving the following error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T959VUVKC1-REV00-ALL-low-CL933594.tar.md5 is valid.
<OSM> T959VUVKC1-Phone-CL932707.tar.md5 is valid.
<OSM> SGH-T959V-CSC-TMB.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..
<OSM> All threads completed. (succeed 0 / failed 1)
May I know what does this mean and what else can I try?
Click to expand...
Click to collapse
Its been awhile since I used Odin (I used heimdall as I'm on linux...), but I think this means that Odin is having difficulty talking to your device. Have you checked that you have the right drivers installed? You could also try running Odin as administrator.
If this fails, another thing to try would be a One-Click - see http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V/Heimdall_One-Click
Good luck!
UPDATE: I switched USB ports and it seems that it's now flashing...standby
UPDATE 2: All fixed.
Unhide for original post:
I think I need a bit of help. So last night busybox updated to the latest version (from the app). Now today when I go to start up my phone it starts up, but stays on the Galaxy S3 logo. I can boot into CWM recovery and download mode just fine. So I was attempting to flash (via Odin) back to stock so I could start fresh. I was following the advice from here: http://forum.xda-developers.com/showthread.php?t=1840030. And the bootchains flashed fine, but the root66.tar keeps failing.
This is the log I get:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_VZW_I535VRBMA2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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)
What am I doing wrong?
Also I was running a older build of SynergyROM if that's of any use.
I followed a tutorial because its looked the best i had seen for a while and it had most the files included it was off this forum in the developers section so i booted my s5300 into download mode started up odin 3 and begin placing the files in the correct paths. Once in the correct paths i pressed start and here is what i get a fail? can anyone explain why this might be happening i think the old owner who gave me the brick said he had partioned it so he could use a custom rom ive booted into recovery mode and i see is it cyanmobile amd clockworkmod but i think the clockwork dont have any files? and something else anyway here is the code of the odin result any help would be very helpful has ive been up all night trying to repair it to no avail i dont know how much more i can take hehe?:laugh:
EDIT: might be worth mentioning it does still have a custom rom on the partition i can successfully install it boot when i reboot it just says onkey 7s reset?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5300_XXLF5.tar.md5 is valid.
<OSM> MODEM_S5300_XXLF5.tar.md5 is valid.
<OSM> CSC_S5300_BTULF1.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> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
pablo77777 said:
I followed a tutorial because its looked the best i had seen for a while and it had most the files included it was off this forum in the developers section so i booted my s5300 into download mode started up odin 3 and begin placing the files in the correct paths. Once in the correct paths i pressed start and here is what i get a fail? can anyone explain why this might be happening i think the old owner who gave me the brick said he had partioned it so he could use a custom rom ive booted into recovery mode and i see is it cyanmobile amd clockworkmod but i think the clockwork dont have any files? and something else anyway here is the code of the odin result any help would be very helpful has ive been up all night trying to repair it to no avail i dont know how much more i can take hehe?:laugh:
EDIT: might be worth mentioning it does still have a custom rom on the partition i can successfully install it boot when i reboot it just says onkey 7s reset?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5300_XXLF5.tar.md5 is valid.
<OSM> MODEM_S5300_XXLF5.tar.md5 is valid.
<OSM> CSC_S5300_BTULF1.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> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2560314
I rooted my Girlfriends S7 Edge and when she restarted, it went into a boot loop. I have used every option in oden except autostart,Flash lock, and deviceonfo. I want to return to stock. G935T
this if from standard options using only AP
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_TMB_G935TUVU1APB6_G935TTMB1APB6_CL7103056_QB8543665_REV02_user_low_ship_MULTI_CERT.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone screen says:
SW REV CHECK FAIL : [aboot]Fused 4 > Binary 1
It looks like you're trying to flash a firmware which is older than the one installed. Try to find latest firmware.
It was running 6.1 then went custom shoudnt i be able to flash same version?
rhettc2 said:
It was running 6.1 then went custom shoudnt i be able to flash same version?
Click to expand...
Click to collapse
tried newest version and still same problem. Smart Switch and kies wont even recognize the phone. I have installed the samsung driver.
Went to samsung official site and tried download from there thank you very much!
Samsung SGH-T779 (Galaxy Tab 2 T-Mobile)
Hey team, I've spent several hours trying to work through what's going on with this Galaxy Tab 2 which my Dad wanted to give to my son.
Here's the status of the tablet. It hasn't been regularly used for years. When plugged in you get mostly non-responsiveness. BUT, after charging it for a few days, you can unplug it and then it will allow you to try Odin mode (power + volume down) and it FAILS to try recovery mode (holding power + volume up).
Firstly, when it tries to go into recovery mode, the top left blue wording appears "booting recovery" and then regardless of how long or I continue to hold vs. releasing the power button and up volume, it goes black and then goes into a kind of boot loop where it'll flash a stagnant "SAMSUNG" logo, then go dark and freeze on a kind of "glowing" but not changing SAMSUNG logo. I can press the power button and it'll go off, and then boot up to the two SAMSUNG logos again, but stays frozen there indefinitely.
Unable to factory reset from recovery mode, I've gotten the tablet into Odin Mode. I have used https://forum.xda-developers.com/t/...-versions-samsung-rom-flashing-tools.2189539/ for my guide to which Odin version (primarily 1.85, but I've tried 3.04, 3.06, 3.07 just to see if they worked better.) I've used this guide to help with the logistics of flashing the stock firmware: https://forum.xda-developers.com/t/guide-odin-flash-guide.1671969/
The TAR files I'm using are from https://samfw.com/firmware/SGH-T779/TMB/T779UVTMF4 and show the following file names.
BOOTLOADER_T779UVTMF4_1255797_REV00_user_low_ship.tar.md5
CSC_TMB_T779TMBMF4_1255797_REV00_user_low_ship.tar.md5
MODEM_T779UVTMF4_1255797_REV00_user_low_ship.tar.md5
PLATFORM_T779UVTMF4_1255797_REV00_user_low_ship.tar.md5
I've been plugging the Platform file into the PDA slot, since there's not a PDA/Code in the file packet. I get the following message thread when running:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_T779UVTMF4_1255797_REV00_user_low_ship.tar.md5 is valid.
<OSM> PLATFORM_T779UVTMF4_1255797_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_T779UVTMF4_1255797_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_TMB_T779TMBMF4_1255797_REV00_user_low_ship.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've also tried the file here: https://a2zrom.com/samsung-sgh-t779-firmware which only has one file named:
T779UVTMF4_T779TMBTMF4_T779UVTMF4_HOME.tar.md5
I plugged this into the PDA slot and the result was the following message thread:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T779UVTMF4_T779TMBTMF4_T779UVTMF4_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any direction here would be tremendously appreciated!
The only other information I can offer is that occasionally I HAVE had the SAMSUNG logo loop stall out at a greyed out horizontal battery symbol with a greyed out circle of "sun rays" before it goes black for good.
Any assistance would be greatly appreciated!
Thanks XDA wizards.
aamccarty
Same situation here. I think i will smash it with a hammer
Stay tuned, maybe we'll figure it out together.
First, don't use win 10 or 11, use win7 or Linux for flashing!!!! Than try again...
Maybe its EMMC bug aka flash chip is dead. But you can try flashing ROM with pit file for your model (don't use any others).