Develop Bugs

Soft brick Need urgent help please SM-N900T

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

[Q] Tried to flash back to stock, didn't work

Been having some strange issues with my GN2 (low memory warnings when ishouldn't, phantom button presses etc). Decided to flash back to stock though Odin so I can start over. Went though Odin, it said it worked, but when my phone rebooted, nothing was different
<ID:0/003> SetupConnection..
<ID:1/004> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> boot.img
<ID:1/004> NAND Write Start!!
<ID:1/004> cache.img
<ID:1/004> hidden.img
<ID:1/004> modem.bin
<ID:1/004> recovery.img
<ID:1/004> sboot.bin
<ID:1/004> system.img
<ID:0/003> Can't open the serial(COM) port.
<ID:1/004> tz.img
<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)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Thats the log through Odin..dunno how it couldn't open that com port, but everything else worked. What went wrong>?

What version of Tmo stock firmware did you try to flash? What version is your bootloader?
Hastily spouted for your befuddlement

Trying to flash the 4.3 version from December. It seems like no matter what I try flashing through Odin doesn't work. Tried stock rooted, stock unrooted and CFs autoroot and nothing works. Phone isn't rooted, it previously was...thinking it might fix the issue I did a factory restore in the recovery and lost it
Not sure what version my bootloader is

From what I have read the error "Can't open the serial(COM) port." is related to missing USB drivers. Try unistalling KIES if you have one installed already and see if it works.

Lint6 said:
Been having some strange issues with my GN2 (low memory warnings when ishouldn't, phantom button presses etc). Decided to flash back to stock though Odin so I can start over. Went though Odin, it said it worked, but when my phone rebooted, nothing was different
<ID:0/003> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 1 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Thats the log through Odin..dunno how it couldn't open that com port, but everything else worked. What went wrong>?
Click to expand...
Click to collapse
I believe the / failed 1 is because of the COM port issue. If uninstalling and then re-installing Kies doesn't work, try getting the Samsung USB drivers from here http://forum.xda-developers.com/gal...b-drivers-samsung-usb-drivers-mobile-t1655286 (depeding on the computer you have, of course) Although the thread is for the S3, the drivers are computer related, so they should still work.
Hope it helps.

Lint6 said:
Trying to flash the 4.3 version from December. It seems like no matter what I try flashing through Odin doesn't work. Tried stock rooted, stock unrooted and CFs autoroot and nothing works. Phone isn't rooted, it previously was...thinking it might fix the issue I did a factory restore in the recovery and lost it
Not sure what version my bootloader is
Click to expand...
Click to collapse
Its the new bootloader that is not letting you all you can really do is flash a recovery in odin maybe reflash the 4.3 then do the recovery like philz and it should let you get to recovery to flash a rom
Sent from my GT-N7105 using XDA Premium 4 mobile app

[Q] GT-N7100 is stuck at GT-N7100 logo, goes no further.

Good days to everyone!
I've got a situation with my GT-N7100. It doesn't seem to get past the first logo during boot-up, ever.
I've tried the newest MD5 version for that model. "N7100UBUEND1_N7100TCEEND1_N7100UBUEND1_HOME.t ar.m d5"
Used the PIT file to Re-Partition and several versions of Odin.
With the PIT file, only version V3.07 hangs at, "Get PIT for mapping..", all other versions seem to fail.
Pit File used: Q1_20110914_16GB.pit
Pit File used: PIT_N7100_16GB_20121102
Without the file I get: (Using the tar.md5 packet with V3.07 Odin)
<ID:0/004> Firmware update start..
<ID:0/004> tz.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
Odin V3.09
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
The phone will not go into recovery mode, the only thing I can get it to do is enter download mode.
How this started? Holding the phone, looking at it. It reset itself and never came back.
I disabled my Anti-Virus... Not sure what else to try. Thank you very much in advance!
***UPDATE*** (I was able to enter recovery mode but it seems to fail to mount anything.)
***UPDATE*** (At wits end, not sure what else to try. I'm thinking the NAND has become corrupt and or unrecoverable. Or unless there was a way to, similar to PC's, do a chkdsk repair. At this time i'm downloading the toolkit and attempt anything through ADB, I feel there is nothing more I could do to Un-Brick the phone. I read about Soft/hard Brick, the phone seems to be Soft Bricked but nothing is allowing me to repair/recover through any download method. Booting into recovery fails to mount everything [as seen in pics]. So this is hard Bricked?)

Galaxy Tab 3 (SM-T217A) Soft Brick

Galaxy Tab 3 AT&T (SM-T217A) Soft Brick
Previously on 4.4.2, downloaded the only available firmware from sammobile (4.4.2)
Used Odin to attempt to flash fresh and kicked me to this perpetual "Firmware upgrade encountered an issue. Please select recovery mode in Kies and Try again." Loop.
Have tried Kies 2 & 3 and neither recognize the device.
attempted to use odin 3.07,3.09.3.10,3.12 and get FAIL!
ODIN LOG:
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Im really out of ideas, i need this tablet for school
any help is appreciated

KrossTee said:
Galaxy Tab 3 AT&T (SM-T217A) Soft Brick
Previously on 4.4.2, downloaded the only available firmware from sammobile (4.4.2)
Used Odin to attempt to flash fresh and kicked me to this perpetual "Firmware upgrade encountered an issue. Please select recovery mode in Kies and Try again." Loop.
Have tried Kies 2 & 3 and neither recognize the device.
attempted to use odin 3.07,3.09.3.10,3.12 and get FAIL!
ODIN LOG:
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Im really out of ideas, i need this tablet for school
any help is appreciated
Click to expand...
Click to collapse
Hi did the same dam thing on my t210r .....you flashed the wrong firmware . Take a minute and slap yourself. Then search for the pit file for your device and the last correct firmware you used check repartition in odin (i used 3.12)insert pit file ,firmware, in correct odin slots ensure the device is recognized . Let me know if this wasnt the solution.

T-Mobile SIII Bricked

Hey,
I had a non-rooted T-Mobile SIII with stock ROM installed. A few days back, it just rebooted automatically and got in a boot loop. I don't know what happened. After that, I tried to install the stock ROM again via Odin but it seems that Odin is not writing anything on it. The download mode shows
ODIN MODE
PRODUCTNAME: SGH-T999
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
WARRANTY BIT: 1
BOOTLOADER RP SWREV:1​
WHAT HAPPENS
The Phone turns on but cannot go further than the "Samsung Galaxy S3" logo
When I try to go to the recovery mode, the Samsung logo with booting recovery comes and then it just shifts to the boot loop
I can get to the Download Mode and Odin recognizes the device.
It shows the PASS status after writing a recovery image but it just doesn't work
WHAT I HAVE DONE UNTIL NOW
Tried to flash CMW (touch and non-touch both). Odin gives pass but it still boots to boot loop
Same happens with TWRP
Tried to flash the Stock F/W but Odin fails every time before even trying

What error is shown in the Odin log? Tried using different usb cables and usb ports with Odin?

T-999 unbrick
By your description, it looks like your kernel is corrupt. It happened a few times with my note 3 stock, as well as my S III back in the day.
The way I unbricked successfully each time, was to feed Odin one piece of the stock ROM at a time, in this order:
1. Kernel
2. TWRP 2.7.0
3. ROM
IMPORTANT: if you end up going this way, be sure to power down the unit after each STEP. I even removed the battery, just to be sure.
DO NOT ALLOW ODIN TO REBOOT THE UNIT.
Last thing, be aware that the stock upgrade you use has to match any firmware upgrade you may have flashed in the past.
This is a way doable solution.
Ping me if you have questions or need links. I'm still a newly registered user on this board and can't post links yet.
Good luck!
Abdullah.tariq1988 said:
Hey,
I had a non-rooted T-Mobile SIII with stock ROM installed. A few days back, it just rebooted automatically and got in a boot loop. I don't know what happened. After that, I tried to install the stock ROM again via Odin but it seems that Odin is not writing anything on it. The download mode shows
ODIN MODE
PRODUCTNAME: SGH-T999
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
WARRANTY BIT: 1
BOOTLOADER RP SWREV:1​
WHAT HAPPENS
The Phone turns on but cannot go further than the "Samsung Galaxy S3" logo
When I try to go to the recovery mode, the Samsung logo with booting recovery comes and then it just shifts to the boot loop
I can get to the Download Mode and Odin recognizes the device.
It shows the PASS status after writing a recovery image but it just doesn't work
WHAT I HAVE DONE UNTIL NOW
Tried to flash CMW (touch and non-touch both). Odin gives pass but it still boots to boot loop
Same happens with TWRP
Tried to flash the Stock F/W but Odin fails every time before even trying
Click to expand...
Click to collapse

dangmouse said:
The way I unbricked successfully each time, was to feed Odin one piece of the stock ROM at a time, in this order:
1. Kernel
2. TWRP 2.7.0
3. ROM
Click to expand...
Click to collapse
I followed all your steps. I made it sure after every step that my phone powered down. I also removed the battery for a while after every step but it all ends up the same way. The Kernel and The Recovery are successfully written but it gives an error on the ROM. And nothing changes, I still can't boot to recovery or OS
ODIN LOG
<ID:0/011> Added!!
<ID:0/011> Odin engine v(ID:3.1203)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> SingleDownload.
<ID:0/011> boot.img
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
<ID:0/011> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/011> Removed!!
<ID:0/011> Added!!
<ID:0/011> Odin engine v(ID:3.1203)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> SingleDownload.
<ID:0/011> recovery.img
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
<ID:0/011> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/011> Removed!!
<ID:0/011> 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/011> Odin engine v(ID:3.1203)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> SingleDownload.
<ID:0/011> sbl2.mbn
<ID:0/011> FAIL!
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Are you using the latest stock ROM from sammobile.com?

audit13 said:
Are you using the latest stock ROM from sammobile.com?
Click to expand...
Click to collapse
Yes, I downloaded the latest firmware available on the sammobile.com

Maybe try flashing with a pit file.

audit13 said:
Maybe try flashing with a pit file.
Click to expand...
Click to collapse
Where can I get the pit file??

You'll have to search to find the correct pit file ford your phone's model number and onboard memory size.
Did you flash the stock firmware as a single file in Odin? Tried different usb ports and usb cables?

audit13 said:
You'll have to search to find the correct pit file ford your phone's model number and onboard memory size.
Did you flash the stock firmware as a single file in Odin? Tried different usb ports and usb cables?
Click to expand...
Click to collapse
Yes I tried one file and different usb ports and cables

So you unzipped the file from sammobile only once to get a tar.md5 file?

audit13 said:
So you unzipped the file from sammobile only once to get a tar.md5 file?
Click to expand...
Click to collapse
Yes I used the tar.md5 file

If you can find a pit file and it still doesn't work with the pit file, the memory chip in the phone may be damaged.
https://www.androidfilehost.com/?w=files&flid=6471

audit13 said:
Maybe try flashing with a pit file.
Click to expand...
Click to collapse
Same result after trying with a pit file.

Based on everything you have tried and the end result, I think the memory chip is damaged.

audit13 said:
Based on everything you have tried and the end result, I think the memory chip is damaged.
Click to expand...
Click to collapse
Is there anything I can do 'bout that?

I don't think so. The simplest solution may be to find a used phone with a damaged screen and working motherboard.

audit13 said:
I don't think so. The simplest solution may be to find a used phone with a damaged screen and working motherboard.
Click to expand...
Click to collapse
Thanks for your help man. It seems that the memory chip is fried. Searching for a motherboard now

In your first post you said you can get into download mode.
As last resort I'd try ADB. Try flashing recovery and or boot or even the entire ROM (sideload) via adb (and not Odin). Plenty of tutorials here and on the web and you seem knowledgeable enough to do that yourself.