My phone just boots to the "Saumsung Galaxy Note II" screen and it is stuck there. I dont think its a loop because it doesnt loop (by that I mean it doesnt disappear and appear).
I m afraid using odin would erase everything.
I want to save my data, what should I do? Which rom do i use?
I tried downloading 3 to 4 note 2 roms but they all failed in odin.
Please specify what I need to download in order to save my data.
At this point, I am also ready to just give up and restore factory settings. I went to the at&t technicans, who are completely useless and they used their roms and couldnt help at all. I went to a fix phone place and they couldnt do anything either.
Please help!
Ummmm do you know that you posted this in the s6 forum and not the note 2?
Sent from my SM-G920V using Tapatalk
i know but no one is capable of answering there.
Flash the stock Note 2 firmware on your phone via Odin. It should restore it to normal. Below are the stock firmware from Sammobile. Just pick the one from your country.
http://www.sammobile.com/firmwares/database/GT-N7100/
i tried the US version first.
http://www.sammobile.com/firmwares/confirm/13212/I317UCAMA4_I317ATTAMA4_ATT/
yinxzon said:
there is no US version..
Click to expand...
Click to collapse
Verizon: SCH-i605
AT&T: SGH-i317
T-Mobile: SGH-T889
Sprint: SPH-L900
Choose the right one, download, and flash via ODIN
se1000 said:
Verizon: SCH-i605
AT&T: SGH-i317
T-Mobile: SGH-T889
Sprint: SPH-L900
Choose the right one, download, and flash via ODIN
Click to expand...
Click to collapse
sorry i found it but it doesnt work.
this time it didnt fail.. just says (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
yinxzon said:
sorry i found it but it doesnt work.
this time it didnt fail.. just says (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
Click to expand...
Click to collapse
Are you putting the phone in download mode?
se1000 said:
Are you putting the phone in download mode?
Click to expand...
Click to collapse
yes it is. says downloading do not turn off target！！
yinxzon said:
yes it is. says downloading do not turn off target！！
Click to expand...
Click to collapse
Make sure you have the right drivers and the odin box shows blue
se1000 said:
Make sure you have the right drivers and the odin box shows blue
Click to expand...
Click to collapse
Failed! Drivers should be installed as it shows up on device manager after I installed Kies 3.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
downloaded both roms and both failed again
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
You haven't said how this happened...
Did you flash a custom rom then it failed to boot?
Do you have custom recovery installed?
Tried odin on another computer or different USB port?
I had strange errors like that when I used a different usb cable. Went back to the genuine samsung one that came with the phone and it was ok.
Also, make sure Kies isn't loaded when you are trying to flash.
Your phone was stuck in boot screen. You could just have it factory wiped your or reset cuz the system files were corrupt and can't fully load... now that you may or may not have damaged the rom from flashing different flash file. Say good bye to your data... you have to search for the stock rom of your unit and search for tuts on how to use heimdall...
Sent from my HUAWEI P6-U06 using XDA Free mobile app
I downloaded various custom roms, all of which failed once this happened. I havent tried odin on a different computer and I only have one usb on my surface pro 3. I will try another computer.
I am using the original USB.
What do you mean Kies isnt loaded... I am using the Kies md5???
darqo, i am using the stock rom.
heimdall doesnt work either.
when installing the driver on zadig i only see the gadget serial and i dont see the samsung driver for me to update.
if it detects your device it can flash it use heimdall to fix your kernel preloaders and be sure to download the apropriate flash files.... some russian forums has lots of stock roms to choose from. what seems to be the usual error, is the first thing you must start with. dig on google for some tuts to resolve the error. in my case i disabled samsung kies. i only used its preloader drivers to detect my device. then used other software to fix it... i had that problem too with stuborn drivers. i used usbdeview to remove unwanted drivers the keeps bugging the program the instal the usb drivers from samsung kies program folder... you need a clean pit file for your device and fresh stock rom, a clean or fixed cache.rfs, dbdata.rfs to fix corrupted partitions of your unit...
''SOME DEVS ARE LAZY THESE DAYS, CAN'T BLAME THEM THEY NEED TO EARN A LIVING''
Sent from my Connect-V3 using XDA Free mobile app
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 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
Hello,
I downloaded a PDA from this guide on XDA:
http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/odin-gt-p5100-4-2-2-stock-rom-t3022183
followed the instructions, but I forgot to see if ID:COM is turning blue, and it didn't, but I pressed start. I got this message on Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5100XXDNA1_P5100NEEDNA1_P5100XXDMG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
Odin won't recognize my TAB? on Odin I press AP button and select my md5 file, but ID:COM won't change.
**Edit: I also tried an older version of Odin, Odin 1.85. and I got this message: (On this Odin it did show 0:[COM3])
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5100XXDNA1_P5100NEEDNA1_P5100XXDMG1_HOME.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)
My recovery is TWRP
What can I do?
Thanks!
verynoob said:
Hello,
I downloaded a PDA from this guide on XDA:
http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/odin-gt-p5100-4-2-2-stock-rom-t3022183
followed the instructions, but I forgot to see if ID:COM is turning blue, and it didn't, but I pressed start. I got this message on Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5100XXDNA1_P5100NEEDNA1_P5100XXDMG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
Odin won't recognize my TAB? on Odin I press AP button and select my md5 file, but ID:COM won't change.
**Edit: I also tried an older version of Odin, Odin 1.85. and I got this message: (On this Odin it did show 0:[COM3])
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5100XXDNA1_P5100NEEDNA1_P5100XXDMG1_HOME.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)
My recovery is TWRP
What can I do?
Thanks!
Click to expand...
Click to collapse
try with different set of USB cables or USB ports. check you have Samsung USB drivers installed. remove kies, if installed.
go to recovery mount/unmount data
billysam said:
try with different set of USB cables or USB ports. check you have Samsung USB drivers installed. remove kies, if installed.
go to recovery mount/unmount data
Click to expand...
Click to collapse
Thank you, I tried all ports, didn't help.
I have no Kies installed, and about drivers: If Windows recognizes my P5100 (It appears on my computer and I can access the files) doesn't it mean that drivers are installed?
Perhaps it's the usb cable? I bought a cheap one from eBay after the original one broke (after a few years )
Thanks
verynoob said:
Thank you, I tried all ports, didn't help.
I have no Kies installed, and about drivers: If Windows recognizes my P5100 (It appears on my computer and I can access the files) doesn't it mean that drivers are installed?
Perhaps it's the usb cable? I bought a cheap one from eBay after the original one broke (after a few years )
Thanks
Click to expand...
Click to collapse
Nope, it's not the USB cable since it shows at ID:COM in Odin 1.85.
Did you tried mount/unmount data from the custom recovery and then flashing from ODin?
billysam said:
Nope, it's not the USB cable since it shows at ID:COM in Odin 1.85.
Did you tried mount/unmount data from the custom recovery and then flashing from ODin?
Click to expand...
Click to collapse
Not yet because I've actually installed Andy's unofficial CM 13 (Android 6.x) and it's working quite well
*Edit: Is the 4.2.2 official JB from Samsung? I mean, why would they update such an old tablet after such a long time anyway?
**Edit 2: I went to TWRP recovery (2.8.7.2), and clicked Mount, I un-ticked the 'v' next to Data, but it didn't work. Also, after I restarted and went back to recovery I saw that there is a 'v' next to Data, as if it didn't really unmount anything? Why didn't it let me umount Data? (Or after restarting, it mounts it back?)
verynoob said:
Not yet because I've actually installed Andy's unofficial CM 13 (Android 6.x) and it's working quite well
*Edit: Is the 4.2.2 official JB from Samsung? I mean, why would they update such an old tablet after such a long time anyway?
**Edit 2: I went to TWRP recovery (2.8.7.2), and clicked Mount, I un-ticked the 'v' next to Data, but it didn't work. Also, after I restarted and went back to recovery I saw that there is a 'v' next to Data, as if it didn't really unmount anything? Why didn't it let me umount Data? (Or after restarting, it mounts it back?)
Click to expand...
Click to collapse
Samsung released JB for tab 2 long ago and that too they didn't bother to update for all the regions they shipped initially.
so we all flashed whatever region we got the JB firmware from.
close any other program running on your pc. absolutely no kies, no anti-virus.
try with different odin or use odin multi downloader 4 versions.
it should flash.
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!
hi everyone my name is Cameron and i just joined XDA today
So last night i attempted to root my S7 model number: SM-G930A and i messed up. I'm new to all this but its interested me for a while now and i thought i would give it a shot. So at the moment my phone just goes through the boot loop and is useless. I've tried using Odin to install the original firmware for the device but when doing so i get this message:
<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> 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..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Note: when i put in the AP file Odin acts unresponsive and takes several minutes to load this portion so i thought that was strange. I've tried using v3.10.7 and the newest 13 i think it was and no success. Could anybody shine some light on this for me?
thanks for your time guys
From what I could gather the latest is 3.12.7, so I'm not sure where you got 13 from. 3.12 and higher is required to flash the latest firmware so it makes sense it failed in 3.10. It freezes when you add the AP because it is verifying the checksum. Be patient, this software is an internal tool and not designed with user friendliness in mind. Try to get hold of version 3.12.7 and try again.
irelia is cancer said:
hi everyone my name is Cameron and i just joined XDA today
So last night i attempted to root my S7 model number: SM-G930A and i messed up. I'm new to all this but its interested me for a while now and i thought i would give it a shot. So at the moment my phone just goes through the boot loop and is useless.....
Note: when i put in the AP file Odin acts unresponsive and takes several minutes to load this portion so i thought that was strange. I've tried using v3.10.7 and the newest 13 i think it was and no success. Could anybody shine some light on this for me?
thanks for your time guys
Click to expand...
Click to collapse
Is the G930A an AT&T device? If so doesn't it have a Locked Bootloader? If this is correct - Root isn't going to be available with Chainfire and no TWRP.
BTW - It always takes Odin several seconds to load the AP tar file.
Sent from my SM-G930W8 using Tapatalk
shaggyskunk said:
Is the G930A an AT&T device? If so doesn't it have a Locked Bootloader? If this is correct - Root isn't going to be available with Chainfire and no TWRP.
BTW - It always takes Odin several seconds to load the AP tar file.
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
yes its an AT&T device. I couldnt tell you the answer to the bootloader question though. i barely know anything about all of this stuff, im just trying to learn but thanks for your input
irelia is cancer said:
yes its an AT&T device. I couldnt tell you the answer to the bootloader question though. i barely know anything about all of this stuff, im just trying to learn but thanks for your input
Click to expand...
Click to collapse
Afaik all US S7 models (Snapdragon) have locked bootloaders, AT&T, Verizon and T-Mobile
G930A is a carrier-locked variant of the S7 (snapdragon), it's Bootloader cannot be unlocked thus root and custom recovery isn't possible. With the firmware, I suggest using the latest update of ODIN
Goodluck!