Soft brick Need urgent help please SM-N900T - T-Mobile Samsung Galaxy Note 3

Hello, I am somewhat new here this is going to be second post.
I installed CWM from rom manager a while ago on my rooted note 3 N900T it was on kitkat 4.4.2 then I tried rebooting into recovery mode and then it wouldn't go in it would keep restarting, then after I did a battery pull now I get: ( Firmware upgrade encountered an issue. Please select recovery mode in kids & try again)
ODIN MODE
PRODUCT NAME: SM-N900T
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX KEANEL LOCK: 0X0
KNOX WARRANTY VOID: 0XL
QUALCOMM SECUREBOOT: ENABLE (CSB) AP SWAREV: S2, T2, A2, A3, P2
WRITE PROTECTION: ENABLE
VDC START
So I tried connecting to kies it wouldn't detecting it would just say "connecting" I tried on my mac osX mavericks and also on VMWare windows 7.
I tried to download the stock firmware and flash it via odin to come back to stock and thought maybe that would fix it but it keeps giving me a error.
I have the usb drivers installed as it detects the device, I am sure I have downloaded the correct firmware for the phone.
this is the firmware I downloaded: N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md 5
I tried using odin 3.07 and 3.09 both and ran it as administrator.
I checked the "time reset" also the "auto reboot" as mentioned, I tried adding it in pa in 3.09 and pda in 3.07
This is the error I get while trying to flash the rom: <OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Unfortunately that is what I get from odin sometimes it goes further down and then stops but most of the times i get this, I've tried using the original 3.0 usb cable with different usb ports and also another normal micro usb cable, both gives me the same error, I have tried to use JODIN as well on my mac but my device doesn't detect on that therefore i used my VMware windows 7 32bit. I tried that while I had kids installed on my computer and then I read that kies doesn't go well with odin so I uninstalled kies and tried again but no difference.
Could someone please help me out, I have been trying to fix this for 2 days I am a college student and I work part time, so it is very frustrating not to have a phone to use for work and college.

Your complicating yourself (just saying) get samsung KIES!
follow step by step:
1. go to tools.
2. firmware upgrade and initialisation
3. then just follow the on screen step by step and you'll be back on stock
4. the just re-root if you'd like

atlzonly89 said:
Your complicating yourself (just saying) get samsung KIES!
follow step by step:
1. go to tools.
2. firmware upgrade and initialisation
3. then just follow the on screen step by step and you'll be back on stock
4. the just re-root if you'd like
Click to expand...
Click to collapse
THanks, I didn't try that though, the issue seems to be VMWARE, so I went ahead and un-installed it and downloaded and installed parallels desktop 9 on my mac and then went from there. Flashed the stock rom via odin 3.07 and boom it was successfully installed and now I'm back on stock rom thank god, but thanks a lot i'm pretty sure that would work too because then you enter your model# and S/N/ and install stock

malimt said:
THanks, I didn't try that though, the issue seems to be VMWARE, so I went ahead and un-installed it and downloaded and installed parallels desktop 9 on my mac and then went from there. Flashed the stock rom via odin 3.07 and boom it was successfully installed and now I'm back on stock rom thank god, but thanks a lot i'm pretty sure that would work too because then you enter your model# and S/N/ and install stock
Click to expand...
Click to collapse
Just to let you know,i think that was a lil too much work dont you think lol. could have just used KIES. lol

Related

[Q] Rooting crashed/phone bricked and odin keeps failing/help please!

I am not new to the rooting scene, however I have a problem that I can't seem to figure out. I've been reading now for the past 2 days, tried several things and still can't get this resolved. I've never had any issues in the past with odin and rooting samsung phones before, including ones with locked bootloaders. However, I've met my match. I tried following the tutorial listed on this site for rooting the samsung note 3 from tmobile. I watched the video and followed along with the files listed here
http://forum.xda-developers.com/note-3-tmobile/#root
My problem is as follows: I tried rooting with odin, installed kies for the usb support but halfway through the root process I get the big RED FAILED! phone's progress bar stops and it hangs. I though this was strange and never encountered this before. I then tried repeating the same process and same results, however this time around I am only able to bring the phone into "odin" mode "download" and not the original stock rom.
At first I was getting the original "the firmware encountered an upgrade issue" and couldn't bypass this unless I opted for download mode. I've tried the same steps to "unbrick" via oden with stock tmobile firmware for this phone and yet it yields the same results, big exclamation failed on odin. I then tried the process with the .pit file to partition that I found online somewhere and that fails too. My note starts up now, but stuck at the samsung galaxy note 3 screen. I've tried several versions of odin, switching usb cables, usb ports and I am unable to root this phone or even get it unbricked! i've read extensively here and can't seem to find a solution to my problem. Can someone PLEASE point me in the right directions?? BTW, I am using a mac with VMWARE, i've never encountered any issues with vmware in the past while running windows 8.
Phone says the following:
Once in download mode my phone says the following:
ODIN MODE
PRODUCT NAME: SW-N900T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICIAL
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
QUALCOM SECUREBOOT: ENAMBLE
RP SWREV: S2, T2, A2, A3 P2
WRITE PROTECTION: ENABLE
UOC START
and I get these results from ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_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..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please someone help me, I am desperate and I can't think of what to do next.
http://forum.xda-developers.com/showthread.php?t=2677032
TWEAKED N3
BACARDILIMON said:
http://forum.xda-developers.com/showthread.php?t=2677032
TWEAKED N3
Click to expand...
Click to collapse
I can't seem to do this on 2 versions of windows installed on vmware for my mac. Everytime I try odin fails! Is there a way you can help me do this with heimdall on my mac?

[Q] Soft Bricked Note 2 - Odin Failsn - Kies won't detect my phone - Help?!

I soft bricked my phone somehow, no clue. My phone was fine, battery died with no downloads, or anything running, went to turn it back on after plugging it in to find it bricked at the Samsung start screen.
I've tried restoring it with Kies, which won't recognize my phone is plugged in(??).
I've tried restoring it in Odin with Kies uninstalled, it keeps failing though.
Here's a copy of Odin's log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_T889UVBMD1_T889TMBBMD1_935627_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> 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> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> sboot.bin
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My Note 2 has never been rooted, and I'm completely at a loss as to what has happened. I've tried different USB cords and slots around my laptop, but don't have another computer I can try it on currently.
Also, After trying Kies and Odin I noticed in the top left corner of my Note's screen, KNOX WARRANTY VOID changed from 0 to 1, not sure what that means either!
Any suggestions? I'm lost without my phone!
Edit:
After ODIN fails, my phone says unsupported version also in the top left corner. I've tried 3 different stock ROMs.
Edit 2:
And now I can't get into the boot menu, just the download menu.
Kies also won't recognize that my phone is connected now.
Find latest firmware for your region and device and use Odin to flash it.
Regarding the file in your Odin log seems to be old firmware.
I've tried at least 4 different firmware versions, and am having no luck with any of them. Should I be looking for one that includes the OTA update from back in the winter?
Androidwizzard said:
Find latest firmware for your region and device and use Odin to flash it.
Regarding the file in your Odin log seems to be old firmware.
Click to expand...
Click to collapse
I have the same problem. any other sugestions?
Not yet, I've yet to find a firmware that works. :/
Jotapoggi said:
I have the same problem. any other sugestions?
Click to expand...
Click to collapse
FIX
kittylee said:
Not yet, I've yet to find a firmware that works. :/
Click to expand...
Click to collapse
Kittylee, take a look at this video " youtube . com / watch?v=GbAJH_mL6N4" I've downloaded the rar version of the clockwork recovery for my GT-N7100 from this site "galaxynote2root . com / cwm-recovery /" you have to choose the "RAR" version since it's thhe one odin uses.
OBS.: Remove the spaces from the links
It worked for me. try it.
:laugh:
Got it un-bricked! I was able to find the latest firmware on SamMobile's website, I can't link it though due to being a new user.
kittylee said:
Not yet, I've yet to find a firmware that works. :/
Click to expand...
Click to collapse
kittylee said:
Got it un-bricked! I was able to find the latest firmware on SamMobile's website, I can't link it though due to being a new user.
Click to expand...
Click to collapse
Which version of andriod is it?

[Q] SGH-T999 soft-bricked in download mode only, Odin fails every time! Please help

SGH-T999 soft-bricked in download mode only, Odin fails every time! Please help me
I am new to forums and am in dire need of help. I have learned all that I know through google searches and spending at least 10 hours trying to solve this, so I need simple, easy-to-follow instructions.
I wanted to try experimenting with cyanogenmod so I tried using the one-click installer. On my wife’s galaxy s3 it failed but installed CWM and I think it removed GAAPS and booted up in stock touchwiz. After trying to get cyanogen on it and failing I decided to use Odin to get it back to factory settings and it worked!!
My Tmobile SGH-T999, however, is soft-bricked. I can't even get into simple recovery (volume up + power + home) but I can get into download mode. When I try booting it up normally, I get the message:
"firmware upgrade encountered an issue. Please select recovery mode in Kies and try again". The top left of the screen says:
Product name: GSH-T999
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warrenty Bit: 0
BOOTLOADER AP SWREV: 1
I've tried using Odin 3.07 to put the same firmware (from sammobile) that I used on my wife's phone. I tried flashing the firmware with the proper 16gb pit file and that also failed. I'm pretty sure the PIT file I have works because I didn't get an error message (an earlier attempt with a different PIT failed with a PIT error message on the phone).
Whenever I use Odin it completes 99% of the way and give me this error message (at the end)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Successfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I've installed the latest samsung USB drivers, got from sammobile.com the latest firmware (for 4.3) and put it in the PDA slot, got what seems to be an accurate PIT file. I'm using a new USB cable. It worked for my wife's galaxy s3 but I have no idea how to make it pass!
I sincerely hope that you can help me.
warmly,
-Bryce J
PM me if you want to chat, text, or call me!
What did you do to yours to get it softbricked in the first place? Did you ever update to a 4.4 ROM? You are trying 4.3 and if you ever updated to 4.4 bootloaders/modem, then you can't go down to 4.3
Did you buy your phone new, or used online? A lot of used phones are some bastardized hybrid i747 and t999 parts.
sameboat
I'm having something similar. I'm just trying to get to factory reset but can't even get to recovery mode.
Simple fix. Download the stock firmware and boot into Download mode. Follow the Odin tutorial and you should be fine.

[SOLVED] ODIN Flash failed (for downgrade, custom-to-stock, etc)

Hey there awesome people!
I have been weeping over my N3N refusing to accept Stock firmware I was downloading.
I followed these steps to flash the stock firmware I would download:
Flashing STOCK firmware (via ODIN):
Put phone off / battery pull
Download ODIN (this one or whichever is newest at the time you read this)
Open up ODIN (as Administrator on Windows PC)
Press and HOLD DOWN the Volume Down [AND] the Home buttons. THEN Press the POWER button. On the screen it will show, press Volume UP to go to DOWNLOAD mode
Plug your phone into the PC and ODIN will show you (in the log) that a device has been Added!
Click the AP button and navigate to your downloaded firmware.
Let ODIN finish the MD5 check and then press START to start flashing
So, at this point, your ODIN will either be showing PASS or FAIL.
If it shows PASS, you're good to go. Skip to Installing a recovery.
If it shows FAIL, read the Log (displayed in the program's left hand side) and observe this:
Code:
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Before showing FAIL!, the last thing it should've listed should be hidden.img
If yours didn't show this, it probably didn't flash the phone upto this point. What we want is for the boot.img, recovery.img, system.img, modem.bin and cache.img to have been flashed to the phone.
When it shows FAIL!, it means that the bootloader it is trying to flash is older than what the phone already has. You will probably find that you are stuck here when you're coming from LL to KK or JB, or from a newer KK to an older one.
Fear not It still worked!
What we do now is just flash a recovery to the phone (we will be replacing the stock recovery that stock ROM comes with), (or root it) and we'll be good to go.
Installing a custom recovery:
Download a recovery (I use TWRP Materialized )
Unzip it and re-open your ODIN (if your ODIN was still open, hit the RESET button)
Do a battery pull on the phone, and boot into DOWNLOAD mode again.
Connect the phone to the PC. ODIN should show in the Log that a device has been added.
Click AP button and navigate to where your Custom recovery is.
After ODIN finishes MD5 check, hit START and let the Custom recovery be flashed.
After this is done, boot into recovery by holding down the Volume Up [AND] Home buttons then pressing Power button.
Go into recovery and wipe Data, Cache and Dalvik (factory reset) and reboot the phone.
BOOM! You'll see the Samsung logo doing its thing and we'll be good to go!
Leave a thanks if this helps :highfive:
Shoutout to @rihawi who pointed this trick out in this post!
boydee said:
What we do now is just flash a recovery to the phone (we will be replacing the stock recovery that stock ROM comes with), (or root it) and we'll be good to go.
Click to expand...
Click to collapse
Okay. I had the Odin Fail because I was trying to downgrade to a firmware with earlier bootloader and as you described I installed TWRP. But now I still get the same error in Odin when trying to install this firmware even with TWRP in place... What should I do?
mcpossity said:
Okay. I had the Odin Fail because I was trying to downgrade to a firmware with earlier bootloader and as you described I installed TWRP. But now I still get the same error in Odin when trying to install this firmware even with TWRP in place... What should I do?
Click to expand...
Click to collapse
List for the steps you're taking to install. I fear that we might have gotten lost somewhere along the way.
The idea is to FIRST install the firmware, THEN install TWRP, then reboot (TWRP should be the last thing you install.)
boydee said:
List for the steps you're taking to install. I fear that we might have gotten lost somewhere along the way.
The idea is to FIRST install the firmware, THEN install TWRP, then reboot (TWRP should be the last thing you install.)
Click to expand...
Click to collapse
Your post title says "for downgrade". So I have a firmware with, let's say, bootloader binary version 3 installed. I want to downgrade to an older firmware which has bootloader binary version 2. I can't just flash the older firmware, because Odin fails. So I was following your guide to install TWRP to somehow downgrade through that, but it doesn't work.
When it shows FAIL!, it means that the bootloader it is trying to flash is older than what the phone already has. You will probably find that you are stuck here when you're coming from LL to KK or JB, or from a newer KK to an older one.
Click to expand...
Click to collapse
This is where I'm at right now.
mcpossity said:
Your post title says "for downgrade". So I have a firmware with, let's say, bootloader binary version 3 installed. I want to downgrade to an older firmware which has bootloader binary version 2. I can't just flash the older firmware, because Odin fails. So I was following your guide to install TWRP to somehow downgrade through that, but it doesn't work.
This is where I'm at right now.
Click to expand...
Click to collapse
That's okay! it's perfectly fine for it to FAIL!
Flash it again and copy/paste the ODIN Log here for me to see and advise on what you should do next.
Cheers! :highfive:
odin fail
xda-developers LOGIN REGISTER search plus
Join the Experts
Post Preview:
i used odin3 v3.12.7
this is what appears on the log tab.
Added
Odin engine v(ID:3.1207)
File analysis
setupconnection
initialization
get pit for mapping
firmware update start
NAND write start
Singledownload
sboot.bin
cm.bin
Fail
Complete(write) operation failed
all threats completed. (success 0/ failed 1)
how can i fix this. please help..
please send me message @
[email protected]
facebook- fed refalbor
please. i badly need your help. i am using samsung j7 2016 (j710gn)
Fai always on installing at same way you said
Dear xdas .. I trying the same to download the firmware for the Gt-N5100 at the same steps you explain before but always failed , note that I try that to try resolve the wifi problem after last update, so cannot install firmware and that is the result of ODIN, please let me know if any result here:<ID:0/005> 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/005> Odin engine v(ID:3.1207)..
<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> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
not helpful. you only flashed the recovery and not the whole system file. flashing the system file will took you a minute while the error on takes less than a second.
After i do the odin recovery it showed PASS . but after that phone tried to restart and the samsung logo came on thrice flashing and gone OFF . Now the phone is in dead mode. Please help me to help to resolve this. My phone is samsung note 2(GT7105)
hi, if i flash firmware via odin, programs and files on internal memory will erase or not? thanks
Hi, i was flashing an older version of android to my Samsung Galaxy S7 Edge, using odin, i entered all the files in Odin and it was working fine up until it was almost finished and i accidentally bumped my phone and Odin displayed a FAIL immediately... lol wow i am such a idiot. I disconnected, reconnected, tried to re-run Odin again, it told me it failed right away so theres no fixing it with Odin anymore. I tried restarting phone, i somehow got it to restart but it doesnt show samsung logo or anyting, i just see a Recovery Booting... in the top left corner of screen in tiny letters... i can get it into download mode but nothing else. I dont know what to do, somebody help me out here. How do i fix this??
Cyclone53 said:
Hi, i was flashing an older version of android to my Samsung Galaxy S7 Edge, using odin, i entered all the files in Odin and it was working fine up until it was almost finished and i accidentally bumped my phone and Odin displayed a FAIL immediately... lol wow i am such a idiot. I disconnected, reconnected, tried to re-run Odin again, it told me it failed right away so theres no fixing it with Odin anymore. I tried restarting phone, i somehow got it to restart but it doesnt show samsung logo or anyting, i just see a Recovery Booting... in the top left corner of screen in tiny letters... i can get it into download mode but nothing else. I dont know what to do, somebody help me out here. How do i fix this??
Click to expand...
Click to collapse
Hello, I got a very similar issue on my phone. I spent more than a week trying to find a solution and everytime I got a FAIL. This morning I got a PASS! here is what I did:
_ Use odin v3.12.7 with administrator priviledges.
_ In options I checked: Autoreboot, Re-Partition, F.Reset Time and Phone Bootloader Update.
_ I loaded BL, AP, CP and CSC Files (it was CSC and not Home_CSC).
_ I started the phone in transfert mode (home, volume down and start button). And then press volume up to activate the transfer mode.
_ I connected the phone to the computer and the Phone appeared in ID:COM.
_ I pressed "Start".
And this time the transfer did not fail. It took several minutes and then the phone rebooted and I got the welcome screen as good as new.
I don't know if it worked because I selected "Re-partition" and "phone bootloader update" this time or if it's because I downloaded the lastest stock rom from samsung I was able to find at present (maybe both). But I am so happy now.
Good luck to you and BE CAREFUL because Re-Partition and updating the bootloader could definitely brick your phone...
Secure boot fail
Im getting a secure boot fail after update. Ive tr8ed just AP and odin says boot fail. Phone says secure boot fail. And ive tried all ap,bl,csc,cp and i get from odin re partition fail and again on phone secure boot fail. Is there a way to maybe bypass secure boot. Oem is not optional and it will fail trying the combo rom for factory binary as well. Before the update i was ablento flash everything basically regardless of csc and verison.
Hello,
I downgrade and i tried many stock ROMs (marshmallow and lollipop) and checke all youtube videos, nothing is working. I always i got error. So i want to ask if with your instructions you managed to install stock marshmallow ROM from stock nougat on A510F just because you additionally chose "Re-Partition" and "Phone Bootloader Update" ?
Thanks.
zool_80 said:
Hello, I got a very similar issue on my phone. I spent more than a week trying to find a solution and everytime I got a FAIL. This morning I got a PASS! here is what I did:
_ Use odin v3.12.7 with administrator priviledges.
_ In options I checked: Autoreboot, Re-Partition, F.Reset Time and Phone Bootloader Update.
_ I loaded BL, AP, CP and CSC Files (it was CSC and not Home_CSC).
_ I started the phone in transfert mode (home, volume down and start button). And then press volume up to activate the transfer mode.
_ I connected the phone to the computer and the Phone appeared in ID:COM.
_ I pressed "Start".
And this time the transfer did not fail. It took several minutes and then the phone rebooted and I got the welcome screen as good as new.
I don't know if it worked because I selected "Re-partition" and "phone bootloader update" this time or if it's because I downloaded the lastest stock rom from samsung I was able to find at present (maybe both). But I am so happy now.
Good luck to you and BE CAREFUL because Re-Partition and updating the bootloader could definitely brick your phone...
Click to expand...
Click to collapse
boydee said:
That's okay! it's perfectly fine for it to FAIL!
Flash it again and copy/paste the ODIN Log here for me to see and advise on what you should do next.
Cheers! :highfive:
Click to expand...
Click to collapse
hello guys, sorry, i'm new here.. i've just faced the problem with my phone.. idk why my phone was stuck, i've tried to remove the battery and tried to restart, it seemed the same, just stuck on samsung logo. i tried to enter to recovery mode, it failed. i've tried to install the original stockrom and it's failed..
here the problem and condition:
1. stuck on samsung logo
2. can't enter recovery mode
3. only download mode can be use
i've tried the stockrom but in odin said...:
<ID:0/021> 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/021> Odin engine v(ID:3.1101)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Initialzation..
<ID:0/021> Get PIT for mapping..
<ID:0/021> Firmware update start..
<ID:0/021> SingleDownload.
<ID:0/021> spl.img
<ID:0/021> NAND Write Start!!
<ID:0/021> sboot.bin
<ID:0/021> sboot2.bin
<ID:0/021> param.lfs
<ID:0/021> boot.img
<ID:0/021> recovery.img
<ID:0/021> system.img
<ID:0/021> cache.img
<ID:0/021> hidden.img
<ID:0/021> SPRDCP.img
<ID:0/021> FAIL!
<ID:0/021>
<ID:0/021> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
what should I do?
need help, please.. thanks
a few days ago my Samsung bootloop, I found a solution. Download the latest firmware for your Samsung, which is suitable for your country. enter download mode, just flash AP, later he will install and reboot. when rebooted later if it isn't mistaken it appears no modem / radio (I forgot). enter download mode again, flash CP only. then device will reboot and enter recovery default. in recovery select wipe factory. and my samsung will reset again. I hope this helps you.
hi my problem is this
<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/008> Added!!
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 952 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> spl.img
<ID:0/008> sboot.bin
<ID:0/008> sboot2.bin
<ID:0/008> param.lfs
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i cant flash stock firmware for my samsung galaxy core prime, smg360hu but it stucks at system.img then fails always. help me please
Hi,
Just decided to use Odin v3.14 to update my Australian spare Samsung SM-G900iwith Indian G900IDDS1CSA1 firmware as it was a later build, seemed to proceed OK but finished with <OSM> All threads completed. (succeed 1 / failed 1.
It had previously been updated to G900IDVU1CQJ2_G900ITEL1CQJ2_G900IDVU1CQJ2_HOME.tar.md5 which was working perfectly.
<ID:0/003> Added!!
<ID:1/004> 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/003> Odin engine v(ID:3.1401)..
<ID:1/004> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:1/004> File analysis..
<ID:0/003> Total Binary size: 2496 M
<ID:1/004> Total Binary size: 2496 M
<ID:1/004> SetupConnection..
<ID:0/003> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> NAND Write Start!!
<ID:1/004> SingleDownload.
<ID:1/004> aboot.mbn
<ID:1/004> sbl1.mbn
<ID:1/004> rpm.mbn
<ID:1/004> tz.mbn
<ID:1/004> sdi.mbn
<ID:1/004> NON-HLOS.bin
<ID:1/004> boot.img
<ID:1/004> recovery.img
<ID:1/004> system.img.ext4
<ID:1/004> cache.img.ext4
<ID:1/004> hidden.img.ext4
<ID:1/004> modem.bin
<ID:0/003> Complete(Write) operation failed.
<ID:1/004> RQT_CLOSE !!
<ID:1/004> RES OK !!
<ID:1/004> Removed!!
<ID:1/004> Remain Port .... 1
<OSM> All threads completed. (succeed 1 / failed 1)
Click to expand...
Click to collapse
Can I retain the updated build and just use ODIN to replace what failed?
Any suggestions GREATLY APPRECIATED.
Cheerz
Hello, there is 'firmware upgrade encountered an issue' thing on my samsung. I plugged to pc and pc sees the device but odin stuck at initialzation or fail. Any suggestion?
G Morn Folks I m stuck in the same situation thought different phone mode. this is M205F. Odine FAILS @ Recovery.img
Background
Latest Stock ROM of Samsung Maisk Rooted nd TWRPed. Wanted to downgrade to ANdroid 9 from 10 after realizing severe restrictions of the latter.
Odin 14x ( wtith Chinese verbiage @ start up screen ) used and used 2 Versions of stock ROMs.
Tried AP solo & AP + HOME_CSC COmbos
Both FAIL and leave me with ocean blue screen message "an error has occured while updating the deivce software..Use he emergency recovery function in the smart switch sw." and smart switch isnt recognizing my mob either.
Where do I go from here ?

Note 3 Soft Brick - Need help please

Phone: SM-N900T Note 3 T-Mobile
Long story short, I've soft bricked by wife's phone while trying to do a CF autoroot with Odin.
The error i'm receiving is:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I've tried hooking it up to Kies (Kies Lite) to run the Emeregency Firmware Recovery, but Kies won't recognise the device.
It just sit's there saying connecting.
I've tried using Odin to flash the stock firmware and I get a error after Nand Write.
Stock Firmware i'm trying to Flash: N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I then came across this method below for using Heimdall to flash a recovery and I can't get past the Libusb -12 error on multiple computers/laptops.
http://forum.xda-developers.com/showthread.php?t=2545009
I've tried using Zadig.exe and replacing the MSM8960 Drivers with the libsub-win32 drivers which cause gave an error.
I'm at a loss now as how to proceed, i'm no expert on rooting, but i've rooted my own Note 3 and now my Note 4 with no problem.
Any help would be appreciated in getting this running, as we don't have money to get a new phone for my wife since we just had our first baby and finances are tight.
Are you using the original Samsung cable? Tried different USB ports? The rom is the latest from sammobile.com?
audit13 said:
Are you using the original Samsung cable? Tried different USB ports? The rom is the latest from sammobile.com?
Click to expand...
Click to collapse
I've used the original note 3 cable, a note 4 cable and different usb ports.
I've tried it on two desktops and a laptop. The rom isn't the latest from sammobile, i'm trying to flash to original stock rom that it came with 4.4.2.
Should I be trying to flash 5.0?
Thank you though for the response. I was getting a little disheartened with the lack of them.
Yes, try flashing the latest lp rom.
firmware upgrade
I had the same problem ( firmware upgrade encountered a problem) what I found is the one needs to use a windows laptop or desktop with windows 7 installed and use the original cable, Odin 3.09 and find the ( HLTE_USA_TMO.pit ) file, search xda for the file. Put the phone in download mode and then run odin after the phone is connected choose pit tab and add the pit file then next click nand erase all, after that go to ap and put the lollipop firmware i used N900TUVSPL1_N900TTMBLPL1_TMB-v5.0.1 then click start and let it run. It should go thru the whole process, when done and phone reboots into the white tmobile screen turn the phone off and press the power, volume up and home button right after phone turns off to get to the stock recovery and while there select the factory/data reset and hit the power button, then reboot phone and that will boot up the phone and get you to the start screen. I hope this works for you and anybody else with this problem i worked with mine.

Categories

Resources