I made a mistake upgrading my galaxy note with odin!!!!
I got the message ...
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Kies does not work, not recognizes my phone
When I try to go into recovery mode volume up + power + home, it goes to the same message.
I go into downloading mode, volume down +power +home
And Odin recognizes the device but a got this fail
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000_APBOOT_N7000ZSLPF_CL558430_REV02_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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I try with different tar to get back but did not work, If someone can help me I will be very thankful.
Tars used:
N7000XXKKA_N7000BUKK1_N7000SFRKK1_HOME.tar
N7000_CODE_N7000ZSLPF_CL558430_REV02_user_low_ship.tar
Rooted_Stock_Odex_N7000XXLC1.tar
N7000XXLS2.tar
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!
I am attempting to update my Note 3 to the Official Poland Kit Kat upgrade. I am have the T-Mobile SM-900t with X-Note 5.1 Rom. I have installed the MD5 file and Odin 3.09. I attempted to install the file and got failure.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_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)
<ID:0/004> Removed!!
I have auto reboot, f. reset time and phone bootloader update all checked. Luckily my phone is not bricked and still running under the old Rom. Any help that you could send my way would be great. Thanks
Hello,
I'm creating a new trend because I did try everything what I could find on forums to fix this issue.
I have a problem with Samsung galaxy s7 (SM - G930F) it got stuck on Samsung logo and when I connect it to PC in download mode using USB there is no sign. PC doesn't show anything, I tried all ports and many different cables.
What did I try is:
1) Volume UP+Home Then Power button - Nothing happens. Can't access to the menu for hard reset.
2) Safe mode - Power bottom when it turns on immediately hold power down - Nothing happens, can't run in safe mode.
3) Volume down+Home+Power -
WORKS - Download mode opened, Now the problem is I can't flash a firmware with ODIN3 coz basically PC not recognizing USB.
4) Yes I did download Samsung USB drivers and installed them.
5) I checked on Device Manager there is no sign of samsung USB or anything..
6) I also tried SmartSwitch - Nothing, it asks me to connect to device.
Basically the only things work are download mode and force restart - Volume Down+Power bottom.
The other thing when I charge the phone it shows empty battery logo, no green or red light, percentage or anything.
Any ideas guys? I'm losing a hope with this phone.
If it refuses to charge and the PC won't detect it, it's either an issue with the main board itself or the daughter board that houses the microUSB port.
The latter shouldn't be too difficult to replace.
MeltdownSpectre said:
If it refuses to charge and the PC won't detect it, it's either an issue with the main board itself or the daughter board that houses the microUSB port.
The latter shouldn't be too difficult to replace.
Click to expand...
Click to collapse
But how can it explained that I'm available to access to download mode by pressing volume down+home+power buttons but not available get into hard reset mode menu? I done reseach about hard reset mode and I read that the phone should be over 50% charged to make factory reset. I'm guessing that the phone is charging but not properly charging so I'm only allowed to access into download mode. Because if the phone wasn't charging at all it would be dead. Is this possible theory?
Incognitusum said:
But how can it explained that I'm available to access to download mode by pressing volume down+home+power buttons but not available get into hard reset mode menu? I done reseach about hard reset mode and I read that the phone should be over 50% charged to make factory reset. I'm guessing that the phone is charging but not properly charging so I'm only allowed to access into download mode. Because if the phone wasn't charging at all it would be dead. Is this possible theory?
Click to expand...
Click to collapse
There could be an issue with the recovery partition causing it to not boot into the stock recovery menu for you to do a hard reset.
Normally in circumstances like this, I'd suggest a clean flash of the latest stock firmware, but seeing as though the PC doesn't detect the phone, that won't be possible.
am facing the same problem except my computer does recognize the device although as a modem device and when trying to flash it using odin it fails with <ID:0/003> FAIL! (Auth) error message anybody help
nyarunda said:
am facing the same problem except my computer does recognize the device although as a modem device and when trying to flash it using odin it fails with <ID:0/003> FAIL! (Auth) error message anybody help
Click to expand...
Click to collapse
i am not sure for my answer but are you using the correct firmware version for your device?
maybe it is a carrier or region thing
also check what odin version you are using
rzr86 said:
i am not sure for my answer but are you using the correct firmware version for your device?
maybe it is a carrier or region thing
also check what odin version you are using
Click to expand...
Click to collapse
am using Odin3_v3.14.4;
about the firmware am not sure which to use;
the back of the phone says it an sm-g930t
but on the recoverymode it says it a sm-g930v
i have tried with both firmwares it gives the same error
nyarunda said:
am using Odin3_v3.14.4;
about the firmware am not sure which to use;
the back of the phone says it an sm-g930t
but on the recoverymode it says it a sm-g930v
i have tried with both firmwares it gives the same error
Click to expand...
Click to collapse
Hello, if the phone is reporting G930V in recovery mode then the phone is truly a G930V and that's the firmware you need to flash. It has to be the latest version and for your region.
So a G930V is a Verizon branded device, in your case it's been modified to accept G930F firmware which is always going to be a problem if you attempt to modify the device after that.
Get the latest G930V firmware and flash it with Odin 3.13 not 3.14. Once your phone is up and running you can decide what to do from there, a G930V will only work in the USA.
Tried this procedure still failed....here is odin's terminal log
<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..
<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> Added!!
<ID:0/004> Odin engine v(ID:3.1303)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 5040 M
<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> recovery.img
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and the following is displayed on the phone
odin mode (high speed)
product name:sm-g930v
current binary:samsung official
system status: official
fap lock: on
qualcomm secureboot:enable
rp swrev:b10(2,1,1,1,1) k10 s10
iddq:g(39), s(11) ma
cpu serial num:0xd8df2131
fused open loop voltage:1020mv
rpmb provisioned
sw rev check fail: [boot] fused 10>binary 1
nyarunda said:
Tried this procedure still failed....here is odin's terminal log
<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..
<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> Added!!
<ID:0/004> Odin engine v(ID:3.1303)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 5040 M
<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> recovery.img
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and the following is displayed on the phone
odin mode (high speed)
product name:sm-g930v
current binary:samsung official
system status: official
fap lock: on
qualcomm secureboot:enable
rp swrev:b10(2,1,1,1,1) k10 s10
iddq:g(39), s(11) ma
cpu serial num:0xd8df2131
fused open loop voltage:1020mv
rpmb provisioned
sw rev check fail: [boot] fused 10>binary 1
Click to expand...
Click to collapse
What firmware are you trying to flash?
nyarunda said:
Tried this procedure still failed....here is odin's terminal log
sw rev check fail: [boot] fused 10>binary 1
Click to expand...
Click to collapse
That is your problem.
You are trying to flash an older firmware than what is already on the device.
You need to flash G930V with bootloader 10 or higher.
So... I screwed up badly. I'm a noob and I was trying to get root access on my S7. I first followed this guide on the xda forums to step 15. While following this I had issues writing \data for the backup so I changed the partition from EXT2 to EXT3 fixing the issue. Then I was advised by someone that I shouldn't be following such an outdated guide and he sent me this one. But instead of going through the whole thing I only went from the part where I install the newest TWRP and everything worked. After a reboot on the the phone I booted into android and it was like after a factory reset with everything fine. I set some stuff on the phone up but didn't enable OEM unlock. Then the phone couldn't boot android with the FRP error. So I tried installing the stock firmware from here and that kept failing. Now whe I try to boot regularly instead of the samsung bootscreen with the FRP Lock error I get a light blue screen telling me to use the smart switch but ss didn't help me (it recognizes the phone and that something is wrong but the integrate fix option doesn't recognize the phone).
In odin I get this error when trying to flash the stock rom I linked to (Odin v 3.13) :
<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..
<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> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 4043 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> sboot.bin
<ID:0/004> param.bin
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can get my phone to currently only boot into the download mode and the broken boot mode where it tells me to use smart switch
If anyone has any idea on what I could do to to somehow restore the phone or to get it to a semi functioning state I'd be very grateful.
I'm currently downloading a stock rom from another website: https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/AUT/#SM-G930F 2020-03-26 edition and will try it out once it's downloaded.
[EDIT] No luck with the different ROM, still the exact same issue.
Snapdragon or exynos?
SM-G930F=exynos more roms etc.
eg. Galaxy S7 G930U is = snapdragon USA version
mb. u try flash exynos rom having snap device?
GeloXD said:
Snapdragon or exynos?
SM-G930F=exynos more roms etc.
eg. Galaxy S7 G930U is = snapdragon USA version
mb. u try flash exynos rom having snap device?
Click to expand...
Click to collapse
nope, I have an exynos chip in my phone, but thanks for the suggestion
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).