Develop Bugs

can't flash stock rom on Odin, stacked !! help!!!

Hi all, so I installed the cyanogenmod's new update, I used its in the system update, thought it will be pretty safe just like a stock android update, but then my phone stuck at boot screen. and I really don't have time to mingle with the system right now. I need the phone like 3 hours ago!! i downloaded the stock rom and try to use odin to flash it. then it gives me this error message.
I tried, change the cable, change usb port, change odin version, but nothing works so far. (((
Please help !!
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<ID:0/008> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

You have the 4.3 bootloader on your phone? If you do, you can't use Odin to flash a stock ROM because it may brick your phone. You can only use Odin to flash a 4.3 stock ROM that had specifically been compiled for use with Odin.

audit13 said:
You have the 4.3 bootloader on your phone? If you do, you can't use Odin to flash a stock ROM because it may brick your phone. You can only use Odin to flash a 4.3 stock ROM that had specifically been compiled for use with Odin.
Click to expand...
Click to collapse
Is there a 4.3 rom we can flash with odin? I attempted (stupidly) to flash stock after a CM11 nightly caused a bootloop and would not allow me to enter recovery. All I can do for the moment is enter download mode. Every rom I try to flash I get the same error along with the error on my phone reading:
SW REV CHECK FAIL : Fused 2 > Binary 0
Is there anything I can do?
EDIT: Finally found a fix. I flashed a rom from this thread.
http://forum.xda-developers.com/showthread.php?t=1980683
Just go to their website and download the file for your specific model. After flashing my phone booted up in CM11 (what I previously had installed) but it crashed upon loading the lockscreen. Luckily I could enter recovery mode and do a factory reset. This fixed everything!

[Q] Phone SoftBricked in the middle of the night, help!

I haven't done any ROM updates for a couple of weeks, and I was sound asleep when the phone rebooted. It sat 'rebooting' for two hours before I woke up.
I'm able to reboot into Download Mode, but have been unable to install anything that has worked. I tried flashing both TWRP2.7.0.0 and the stock ROM, but neither have worked. TWRP is still showing as 2.6.3.1 on my phone, and I get a failure when loading the Stock rom that looks like this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLUFNH2_I747MOYBFNH2_I747MVLUFNH2_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> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I'm also able to boot into Recovery mode, but it appears that the phone is encrypted (it asks for a password, even though I've never encrypted it!) and when I try to factory reset or wipe dalvik or anything else, I get: E: Unable to mount '/cache'
Can you help? Phone is a rooted SGS-I7474M on Telus, and was running Slim 4.4.4 build 7.0 Official 5979. I'm using TWRP as my recovery.

Maybe try loading a stock from image using Odin? You can download the stock images from sammobile

Tony_YYZ said:
Maybe try loading a stock from image using Odin? You can download the stock images from sammobile
Click to expand...
Click to collapse
I think that's what I've been doing? I've downloaded this stock firmware: sammobile.com/firmwares/download/34793/I747MVLUFNH2_I747MOYBFNH2_TLS.zip/ and then tried loading it via ODIN?
Perhaps I'm missing something... Appreciate your thoughts!

hardidu said:
I think that's what I've been doing? I've downloaded this stock firmware: sammobile.com/firmwares/download/34793/I747MVLUFNH2_I747MOYBFNH2_TLS.zip/ and then tried loading it via ODIN?
Perhaps I'm missing something... Appreciate your thoughts!
Click to expand...
Click to collapse
Oh, my mistake. That's what I was suggesting. Sorry...I don't know what else to try.

What bootloader is on your phone?
You're trying to alter the bootloader which is causing the error after trying to flash aboot.mbn.

audit13 said:
What bootloader is on your phone?
You're trying to alter the bootloader which is causing the error after trying to flash aboot.mbn.
Click to expand...
Click to collapse
You've lost me... I have no idea. I don't think I've ever touched the bootloader unless that's packaged with Slimkat or TWRP,
How do I find out and what's my next step?

<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
The aboot.mbn file is a bootloader that Odin is trying to load onto your phone. but the current bootloader is preventing this because the bootloader your are trying to load is not compatible with your phone or the current bootloader is newer than the bootloader Odin wants to flash.
Does your phone still boot into download mode? You're sure your phone is an i747m (Canadian version of s3)?
If your phone can boot into download mode, I recommend you flash the latest version of Philz Touch for the d2lte, copy a custom ROM to your external SD card, boot into Philz, and flash the custom ROM so you can at least get your phone booted. Once booted, install the Samsung Phone info app. This app will tell you the baseband and bootloader on your phone.

audit13 said:
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
The aboot.mbn file is a bootloader that Odin is trying to load onto your phone. but the current bootloader is preventing this because the bootloader your are trying to load is not compatible with your phone or the current bootloader is newer than the bootloader Odin wants to flash.
Does your phone still boot into download mode? You're sure your phone is an i747m (Canadian version of s3)?
If your phone can boot into download mode, I recommend you flash the latest version of Philz Touch for the d2lte, copy a custom ROM to your external SD card, boot into Philz, and flash the custom ROM so you can at least get your phone booted. Once booted, install the Samsung Phone info app. This app will tell you the baseband and bootloader on your phone.
Click to expand...
Click to collapse
I tried loading I747MVLDLK4_aio.tar.md5 and here's the log from the fail I ended up with:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLDLK4_aio.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Loading Philz also failed.

Are you flashing the latest Philz tar.md5 file? You can't flash the zip in Odin. You should be able to flash the Philz zip in TWRP.

audit13 said:
Are you flashing the latest Philz tar.md5 file? You can't flash the zip in Odin. You should be able to flash the Philz zip in TWRP.
Click to expand...
Click to collapse
I was using Skips Toolkit to try and load Philz... I'll try using TWRP

Flash Philz tar.md5 in Odin or the zip in TWRP. I prefer not to using any tool kits.

audit13 said:
Flash Philz tar.md5 in Odin or the zip in TWRP. I prefer not to using any tool kits.
Click to expand...
Click to collapse
The process all looks good, log:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-d2att.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> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
But still boots with TWRP... despite a PASS in Odin.

Samsung Galaxy Note 2 N7100

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.

Unable to flash firmware

I tried to flash Samsung Galaxy note 2 Gt-N7100 firmware N7100XXUFNL1_N7100ODDFNI1_N7100DDUFND1_HOME.tar.md5 using odin version 1.85 ,3.07 , 3.09 , 3.12 .3 but i am getting Fail as odin status i found that i need to flash pit file so , i flashed pit PIT_N7100_16GB_20121102.pit along with it but still getting status as Fail .Then i tried flashing twrp too but still status is fail
odin 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..
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
I have TWRP recovery installed but i am unable to mount .
Internal storage , External sd card ,OTG are showing 0mb.When i boot into twrp a to3g window opens in to my laptop.
Please help me fix this.

Try flashing without pit file. Try different USB cables and USB ports.

audit13 said:
Try flashing without pit file. Try different USB cables and USB ports.
Click to expand...
Click to collapse
i have tried flashing without pit file , tried another usb cable and another ports too but still it's not working.Please help me

Bruh can your please share this topic with others too?

where you found that PIT file so i can try this too

janezz2 said:
where you found that PIT file so i can try this too
Click to expand...
Click to collapse
I googled "pit file for note 2 n7100" .

When you try to flash the phone with Odin and no pit file, what errors appear in the Odin log? Did you confirm the model # in download mode?
Post the Odin log when a flash fails. These logs can provide clues as to what's causing the problem.

audit13 said:
When you try to flash the phone with Odin and no pit file, what errors appear in the Odin log? Did you confirm the model # in download mode?
Post the Odin log when a flash fails. These logs can provide clues as to what's causing the problem.
Click to expand...
Click to collapse
odin 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..
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Try flashing without repartitioning.
Tried different USB cables and USB ports.

audit13 said:
Try flashing without repartitioning.
Tried different USB cables and USB ports.
Click to expand...
Click to collapse
how

Flash the stock rom from Sammobile.com using Odin without a pit file.

audit13 said:
Flash the stock rom from Sammobile.com using Odin without a pit file.
Click to expand...
Click to collapse
same error did not work

Old Tmo Note 2

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.