I cannot get my file transfer to work after flashing my phone with clockworkmod.taz. I followed the instructions on this site, which is pretty much the same as the guide on XDA, except that it used Odin 1.85 instead of 3.04. The other thing that's different is that it didn't warn me that I needed to connect my S3 successfully to the PC before running the flash, so I didn't do it before flashing. My phone isn't rooted because I can't get the root file onto the phone to continue the steps.
Can anyone help me? I don't know what else to do. I know that the problem is the phone because I have another unflashed S3 that works fine on the same PCs. I have used different operating systems as well - XP SP3 x32 and W7 x64. Tried different USB ports. Reinstalled USB drivers and Kies. Disabled NOD32 antivirus. Nothing has worked. I am on the verge of returning this phone, but I don't know if flashing it with CWM has voided the possibility of a return.
Can I undo CWM flash? What else can I do? Will factory reset help?
NOTE TO MODS: Do NOT delete my thread again, please. At least give me a warning, move my thread, or something other than just erasing everything. My previous thread was deleted, so was all the work put into it.
I just removed CWM and flashed it with original ROM, but still cannot get the MTP working. I got the stock ROM from here. See the log below
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVALEM_T999TMBALEM_T999UVALEM_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> boot.img
<ID:0/007> cache.img.ext4
<ID:0/007> NON-HLOS.bin
<ID:0/007> recovery.img
<ID:0/007> rpm.mbn
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> system.img.ext4
<ID:0/007> tz.mbn
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Added!!
Click to expand...
Click to collapse
I also did a hard reset from the boot menu and this damn phone is still not connecting. Any suggestions at all?
I'm surprised no one was able to help. Anyway, it turns out the problem is with all Samsung phones. Given that I had no problem whatsoever with the 16GB version, but both 32GB versions didn't work, it seems to be limited to the 32GB Galaxy S3.
The solution is to connect your phone to your PC BEFORE syncing your phone with Google. Just skip the prompts, get to the phone apps page, and connect the phone. If it still doesn't connect, remove the SIM card and try again.
If you have already synced to Google, just do a factory reset.
Here is a link to a helpful thread: http://forum.xda-developers.com/showthread.php?t=1749201&page=2
Related
Hello,
I had flashed CM 11 and wanted to return to stock - I tried flashing NE2 in download mode using odin and it keeps failing with a nand write fail in odin? Any ideas? Knox is 0x1 (from long ago), I don't care about the knox. Is there a way to flash back to stock from Philz recovery which is currently installed and I can boot to recovery.
EDIT would a low battery level (5%) cause the nand write errors? I am charging it now to 100 % before attempting again.
Thanks.
cybershawngates said:
Hello,
I had flashed CM 11 and wanted to return to stock - I tried flashing NE2 in download mode using odin and it keeps failing with a nand write fail in odin? Any ideas? Knox is 0x1 (from long ago), I don't care about the knox. Is there a way to flash back to stock from Philz recovery which is currently installed and I can boot to recovery.
EDIT would a low battery level (5%) cause the nand write errors? I am charging it now to 100 % before attempting again.
Thanks.
Click to expand...
Click to collapse
Below with NE1 one-click
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sboot.bin
<ID:0/007>
<ID:0/007>
<OSM> All threads completed. (succeed 0 / failed 1)
SW REV CHECK FAIL DEVICE 2 BINARY 1
I tried it with N5100XXDNL5_N5100OXADNL5_N5100XXDNH3_HOME.tar.md5
\
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5100XXDNL5_N5100OXADNL5_N5100XXDNH3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
solved it - it just turned out to be patience and downloading the correct firmware.
I went to sammobile.com (which is official samsung I didn't know).
Search for GT-N5110
Got 4.4.2 (Poland - I didn't see U.S. but I'm told the wifi versions are all the same).
Used Odin 3.09 as administrator.
Official Samsung Cable
Charged to 100%
THe one i Used was N5110XXDNF1_N5110XEODNF1_XEO
(EDIT While that works, it's only good if you speak polish. Finally found the right one:
N5110UEU2CNE2_N5110XAR2CNE2_XAR - XAR is the code for USA
Boot loop after factory reset on GT-N5110
I tried to reset the device using Settings>Back up and reset>Factory data reset>Delete all.
Rebooted into a black screen with an Android with a hatch open and a blue spinning thing. It's been stuck in a endless loop of the startup screen with the name and model, which then goes to the Android with open hatch.
I pried the rear cover off and discovered that I don't have any screwdrivers small enough to remove the battery. So I'm wondering if there is any software based fix that I can try.
Holding down Power+Volume Down interrupts the loop and brings up this screen - blogyourearth.com/wp-content/uploads/2012/02/Samsung-Galaxy-S2-Warning-Custom-rom-installation.jpg
I've had the tablet for 2 years, so the warranty is long gone. I'd be open to flashing a Custom Rom/Kernel, as long as I'm able to go back to the default TouchWiz 4.1.2.
Bump/Update
Update/bump.
Tried flashing the stock 4.1.2. firmware from sammobile.com with Odin v3.07. - Doesn't seem to work, here are the status messages from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> Firmware update start..
<ID:0/004> boot.img -----Status was frozen on boot.img for 3 hours.
<ID:0/004> __Xmit Write fail
<ID:0/004> XmitData Fail..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone have any idea what's wrong? Should I try a different version of Odin, different firmware or what?
emc_2 said:
Update/bump.
Tried flashing the stock 4.1.2. firmware from sammobile.com with Odin v3.07. - Doesn't seem to work, here are the status messages from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> Firmware update start..
<ID:0/004> boot.img -----Status was frozen on boot.img for 3 hours.
<ID:0/004> __Xmit Write fail
<ID:0/004> XmitData Fail..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone have any idea what's wrong? Should I try a different version of Odin, different firmware or what?
Click to expand...
Click to collapse
Are you able to enter download mode without issues?
pvsgh said:
Are you able to enter download mode without issues?
Click to expand...
Click to collapse
Yes, no issues at all.
emc_2 said:
Yes, no issues at all.
Click to expand...
Click to collapse
Try flashing TWRP recovery, take a backup of your current ROM, and then try installing one of custom ROM .
pvsgh said:
Try flashing TWRP recovery, take a backup of your current ROM, and then try installing one of custom ROM .
Click to expand...
Click to collapse
Have no idea on how to do any of the above, but I'm googling now. Are there any guides/articles on how to do this, that You could point me in the direction of? Since I'm soft-bricked, is there any point in trying to back-up my presumably borked ROM? I've already downloaded my country specific, stock 4.1.2. ROM.
Many thanks for taking the time to help me and I apologize for the noob questions. I know my way around Windows, but when it comes to Android - I'm hopeless
I flashed TWRP successfully, I think...
Stumbled across the ODIN troubleshooting thread and one of the steps was to try different cables. The 10 foot cable I've been using for the past 8 months would only end up with a failure, stock cable... didn't even register. 8 inch cable I bought for my external battery had a successful flash in 10 seconds!
<ID:0/004> Added!!
<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> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
i.imgur.com/HPziH0E.png
emc_2 said:
I flashed TWRP successfully, I think...
Stumbled across the ODIN troubleshooting thread and one of the steps was to try different cables. The 10 foot cable I've been using for the past 8 months would only end up with a failure, stock cable... didn't even register. 8 inch cable I bought for my external battery had a successful flash in 10 seconds!
<ID:0/004> Added!!
<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> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
i.imgur.com/HPziH0E.png
Click to expand...
Click to collapse
OK so now you have a working TWRP recoveryand you also know what was causing ODIN to fail.
Next step would be to install a custom ROM, check the development section.
if you prefer stock then you ODIN your stock tar file which you downloaded.
Using TWRP, I backed up; EFS, Boot, Cache, System and Data. After the backup completed I followed the prompt to reboot and it booted into Android *happy dance*.
looks like all the user preferences are gone. No more password or background pictures and all apps have been removed from their folders. Basically looks like all the apps that I installed are there and any data associated. But all my preferences and set options are gone.
Going through the apps, I remembered that I had rooted using Framaroot. Do you think that may have been the cause for the soft-brick? Should I un-root and then try the factory reset again or just flash the stock ROM that I downloaded?
EDIT: didn't see your reply when I started typing this out. Since TWRP is flashed. Does that mean it has replaced whatever recovery Samsung had in place? If so; does having it installed/flashed increase the chance of a fairly stress free recovery in case of future problems?
So, it turns out pvsgh is pretty awesome!
It worked! Thank you so much. You rock!
Had to use another cable though. I think I need a new USB/Charge port
After flashing the stock ROM I had quite a bit of left over data like app folders and pictures/screenshots. Went into the stock recovery and did a factory reset from there, which wiped the internal storage back to factory state.
Should I flash TWRP again and use it to backup everything, now that everything seems to be working normal. Or just leave it as is?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
i.imgur.com/j9neU0B.png
emc_2 said:
It worked! Thank you so much. You rock!
Had to use another cable though. I think I need a new USB/Charge port
After flashing the stock ROM I had quite a bit of left over data like app folders and pictures/screenshots. Went into the stock recovery and did a factory reset from there, which wiped the internal storage back to factory state.
Should I flash TWRP again and use it to backup everything, now that everything seems to be working normal. Or just leave it as is?
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
recovery.img
system.img
cache.img
hidden.img
RQT_CLOSE !!
RES OK !!
Removed!!
Remain Port .... 0
All threads completed. (succeed 1 / failed 0)
Added!!
Removed!!
i.imgur.com/j9neU0B.png
Click to expand...
Click to collapse
You can take a backup that you can use to restore your tablet if you ever get issues again.
Or just follow the same procedure again.
Taking backup is completely a user choice whether he want it or not.
I've searched high, and I've search low for firmware for my phone (only to be led to sites whose download speed is atrocious).
My phone model is: SM-N910P
I've been searching for the .tar files for the firmware updates. The MD5 is either not valid by Odin's standard or something else.
Can someone point me along to a link of the latest Note 4 Stock Firmware update from a site that doesn't take all day to download from? Thanks Kindly.
P.s. Yes, I have gone through website and threads posting link to the correct firmware but all of them have not been MD5 correct or worked at all.
I'm also experiancing frequent crashes/restarts on the phone.
I got this phone from a family friend and its been acting weird in ways that are outside my comphrenension. It's rooted and they need it to factory state but all theses errors, problems, slow downloads, are making it near impossible.
Try downloading stock tar from this thread with your PC. You can and should verify the md5 before flashing in Odin when md5 is provided.
http://forum.xda-developers.com/showthread.php?p=63868221
Sent from my SM-N930P using Tapatalk
I flashed the file you linked to and this is what i got in Odin
<ID:0/009> 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/009> Odin engine v(ID:3.1101)..
<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> SingleDownload.
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> sbl1.mbn
<ID:0/009> rpm.mbn
<ID:0/009> tz.mbn
<ID:0/009> sdi.mbn
<ID:0/009> NON-HLOS.bin
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> system.img.ext4
<ID:0/009> FAIL! (Write)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
gordonfrohman said:
I flashed the file you linked to and this is what i got in Odin
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1101)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
aboot.mbn
NAND Write Start!!
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
FAIL! (Write)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Questions:
Which stock tar did you flash? (see end of this post)
Does the phone frequently reboot or boot to download mode (reporting) failure to normal boot? Any eMMC failures reported?
Things to check or try if non applicable:
Factory reset in stock recovery if no OS is installed. If you can boot OS, make sure that Settings/Security/reactivation lock is disabled and enable developer mode and enable USB debugging.
Verify correct Samsung driver installed on PC or uninstall and reinstall from Samsung support for Note 4.
Use original Samsung Note 4 cable or replace. A good quality USB data cable should work but if replacing, use OEM replacement.
Run Odin in administrative mode. Try the suggested Odin version (3.10.7 or 3.10.6) or latest version from here: http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
(Odd reported issues sometimes result in one of these reported as successful where various others weren't).
Try another USB port, cable or PC
Edit: All KIES and Smart Switch sessions should be killed prior to starting Odin session.
Do not Odin older stock tars; usable stock tars start at OG5 and up.
Sent from my SM-N930P using Tapatalk
My friends Note 2 stopped working.
There are some important photos in the devices internal memory and that's actually the only reason why I (we) would want the phone back in some kind of working condition.
I've asked about this problem in two other threads, but no luck there.
Sorry for spamming, but I'd really need some help - even if it's just some wild ideas!
When powered on the phone gets stuck at the Samsung logo, to turn it off you have to pull the battery.
If I plug the phone to a charger, it only shows a static pic of a battery, but nothing else happens. If it gets unplugged, the pic stays on the screen (have to boot or pull battery).
The laptop reacts (first time installs the device) when the phone is turned on and connected via USB.
I can get to Odin mode, but if fails.
I can also get to System recovery, but no help there. It just shows a bunch of failed to mount -things and ADB does not work (it connects to pc in Adb sideload though).
No luck trying with different Odin and firmware nor recovery.
Tried different usb-cables and -ports. With and without external SD card.
Installed and uninstalled drivers and stuff.
I don't think the phone is rooted.
Could the problem be NAND rw corruption?
I am wondering if flashing the recovery package with the re-partition ticked and the .PIT file will erase the photos from the internal memory?
If I'd do wipe data/factory reset, what chances would I have to get even some of the photos recovered (and what would be good software for that)?
Or does anybody have any other ideas?
Odin says things like these:
<ID:0/010> Added!!
<ID:0/010> Odin engine v(ID:3.1005)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> recovery.img
<ID:0/010> NAND Write Start!!
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
_______________________________________
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFND3_N7100OXAFND3_N7100XXUFND3_HOME.tar.md 5 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> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
_________________________________
In recovery it just shows a bunch of failed to mount -things
The only important thing in this case would be to get the photos saved! But then again the owner of the phone doesn't have the extra money to pay for repair or spare parts etc.
If anyone could help, it would be much appreciated!
When phone boots, all I see is Samsung logo, it doesn't go beyond that.
The phone was running 4.x stock rom and never rooted.
I can get the phone into download mode, but nothing after that when I try to ODIN, it just don't take it.
I left the PC there for very long time, but it just doesn't flash.
I made sure that my drivers are updates, used new ODIN V3.09.
Got the latest GalaxyNote2/ SGH-T889/TMB-T889UVUCMK7-20131209151709 firmware
the PC does detect the phone, and odin does find COM7 port.
any help would be appreciated.
Which file is failing to flash in Odin?
audit13 said:
Which file is failing to flash in Odin?
Click to expand...
Click to collapse
TMB-T889UVUCMK7-20131209151709.tar
Is there one particular file that is not flashing such as system, recovery, etc? It would be shown in the Odin log window.
its just one tar file that I was trying to flash through ODIN.
the 2nd button ( I forgot the name of it, the one that replaces the PDA )
Can you link me the sequences which I should follow to get to the stock ODIN?
Thanks,
Post the Odin log.
filename:
T889UVUCMK7_T889TMBCMK7_T889UVUCMK7_HOME.tar.md5
ODIN LOG:
<ID:0/007> 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/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is mk7 the most recent stock ROM? It doesn't seem to be based on this: https://www.sammobile.com/firmwares/database/SGH-T999/
The boot.img file failure leads me to believe the ROM is too old for the phone.
audit13 said:
Is mk7 the most recent stock ROM? It doesn't seem to be based on this: https://www.sammobile.com/firmwares/database/SGH-T999/
The boot.img file failure leads me to believe the ROM is too old for the phone.
Click to expand...
Click to collapse
This is for T889.
I think the most updated one is https://www.sammobile.com/firmwares/download/56160/T889UVUCOH4_T889TMBCOH4_TMB
I am downloading this to try now
here is the new file that I tried to flash.
T889UVUCOH4_T889TMBCOH4_HOME.tar.md5
and here is the log
<ID:0/007> 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/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Humour me but could you boot the phone into download mode and check the model #?
Have you tried using different USB cables and USB 2.0 ports?
Picture attached
Picture
Picture attached
Okay, the firmware looks good and the phone is running a 4.3 bootloader so the latest ROM from sammobile.com is the only ROM that can be flashed via Odin.
Did you get a chance to try different USB cables and USB 2.0 ports? Might try on a different computer too.
I tried different cables, will try another computer and see
Different computer didn't work either.
What else I can try?
It still fails to flash sboot.bin? The file is the bootloader which could mean the memory is damaged or the original Samsung USB cable needs to be used for flashing.
As a last resort, you could take the phone to a cell repair shop and ask them to flash the phone with a jtag cable or Octopus box.
byteless said:
TMB-T889UVUCMK7-20131209151709.tar
Click to expand...
Click to collapse
byteless said:
When phone boots, all I see is Samsung logo, it doesn't go beyond that.
The phone was running 4.x stock rom and never rooted.
I can get the phone into download mode, but nothing after that when I try to ODIN, it just don't take it.
I left the PC there for very long time, but it just doesn't flash.
I made sure that my drivers are updates, used new ODIN V3.09.
Got the latest GalaxyNote2/ SGH-T889/TMB-T889UVUCMK7-20131209151709 firmware
the PC does detect the phone, and odin does find COM7 port.
any help would be appreciated.
Click to expand...
Click to collapse
Your EMMC is bad probably.