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.
Related
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
So i believe i have soft bricked my phone,
I can get into recovery and download mode, but the phone either loads into download mode or it loads into the galaxy siii boot menu and stays there.
I have 2 backups, neither work.
I have tried flashing stock rom but odin has an error and does nothing afterward.
help please
this is what i get in Odin when flashing stock rom
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_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> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
try different port or cable or computer if you have kies installed uninstall it try redownloading can also try these
http://forum.xda-developers.com/showthread.php?t=2031840
jerrycoffman45 said:
try different port or cable or computer if you have kies installed uninstall it try redownloading can also try these
http://forum.xda-developers.com/showthread.php?t=2031840
Click to expand...
Click to collapse
oddly enough, i did what i said i tried in my original post on my home computer...and it works... lol
i dont know what was wrong or if i did anything different.
but the issue seems to be resolved now.
thank you for your help though
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.
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
using a note 2 today and it just decided to reboot on its own, and then never got passed the splash screen. i have twrp recovery installed. booted into recovery and couldnt do anything. couldn't mount anything, wipe anything, restore anything. all storage showed 0MB. kept giving errors that it couldn't mount any partitions (cache, system, etc.) something with error 16.
i tried flashing a stock rom with odin. that failed. just seems like it is totally corrupted and nothing can be written to it.
how does something like that happen just randomly???? any way back from the dead?
Is the phone an AT&T Note 2? Where did you find the stock ROM for Odin?
audit13 said:
Is the phone an AT&T Note 2? Where did you find the stock ROM for Odin?
Click to expand...
Click to collapse
yes AT&T note 2.
the stock rom i got from a link on this forum. i tried this one first, I317-UCUCNJ2-Stock.tar.md5, then this one I317-UCUCNE5-Stock.tar.md5
also tried re-partitioning after with this pit file, i317.pit
i tried using Odin v1.85 and Odin 3.07
What is the error message in the Odin log?
Tried using different usb cables and usb ports with Odin?
audit13 said:
What is the error message in the Odin log?
Tried using different usb cables and usb ports with Odin?
Click to expand...
Click to collapse
just tried it, same result. odin log? you mean the message output? here it is for when i tried with and without PIT file
Code:
[B]No pit file[/B]
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317-UCUCNE5-Stock.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> boot.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
[B]With pit file[/B]
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317-UCUCNE5-Stock.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> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
Without the pit file, it's failing with the boot.img file and this may be fixed by using an oem Samsung cable or different usb 2.0 port. It could also be that the bootloader in the rom is not for the phone or the phone's current bootloader is newer than the bootloader being fished.
audit13 said:
Without the pit file, it's failing with the boot.img file and this may be fixed by using an oem Samsung cable or different usb 2.0 port. It could also be that the bootloader in the rom is not for the phone or the phone's current bootloader is newer than the bootloader being fished.
Click to expand...
Click to collapse
tried different cables and ports and another ROM, I317UCAMA4.. still fails.
i think it's a lost cause.
I'm sure you are correct but this phone shows up as an sgh-i317 in download mode?
Where did you get the ROMs? AT&T never released an Odin-flashable ROM after 4.1.2.
audit13 said:
I'm sure you are correct but this phone shows up as an sgh-i317 in download mode?
Where did you get the ROMs? AT&T never released an Odin-flashable ROM after 4.1.2.
Click to expand...
Click to collapse
yes it shows as sgh-i317 when in download mode
roms were gotten from wherever one gets roms i guess