Dirt SOFT BRICK SGH-T989!! - T-Mobile Samsung Galaxy S II SGH-T989

OK! SO, basically it's like this!
i have the phone SGH-T989 anf its going in downloading mode but not in recovery! ok and no OS is installed as it only stuck at SAMSUNG logo when turning on normally!
now i have alll the ODIN version but i am using ODIN v1.85V for this! and firstly when i flash that
T989UVMC6_T989TMB_T989UVMC6_HOME.tar
file it says GETTING PIT partiotion something
and then NO PIT found or something like that!!
now i used other ODIN version V3.04 V3.07 or .09
but all JUST HANGS like ODIN works but nothing righ above [ID:COM] SECTION AND NOTHING ON PHONE OR SOMETHING!!
doesn't even start the process after pressing START!
what the HELL should i do even tried PIT file in that but it says FAIL i do tick RE-PARTITION also! ) i also have
T989UVLI4_T989TMBLI4_T989UVLI4_HOME.tar
but same with this and i have this PIT file!
CELOX_USA_0824.PIT
HELLPPPP!

Never check "repartition"...you may have dug a hole with that already I'm afraid.
To flash the official firmware, Odin 3.04 or 3.07 are the ones to try. You need to be sure your phone is in download and communicating with Odin. If you don't see "added" when you plug it in, your drivers aren't right.
That other pit you mentioned is not for this device, not that I know of anyway. Flashing that will likely be the end if your phone.
And one big thing with Odin.....Kies can not be running. Go into the PC's task manager and end any kies processes. Then open Odin. Then plug your phone in.
See how that goes. Any errors, write them down and post them here.
Repartitioning may have already landed you in hot water tho...

Related

[Q] Phone stuck at "Samsung Galaxy S II" Logo

I'm not new to rooting, I'm coming from the Samsung Epic 4G.. My new Epic Touch 4G is stuck at the Samsung Galaxy II GT-I9100 Logo.. Really annoying. Here's what happened...
I rooted my new Epic touch with this link: http://www.forums.acsyndicate.net/s...lus-Stock-Rooted-BusyBox-CWM5-and-Plus-Tweaks
Everything was working fine.. I then wiped the phone (the usual) and flashed the stable Starburst ROM
I rebooted and started getting an error saying "Sorry! The application Status Bar (processcom.android.systemui) has stopped unexpectedly. Please try again."
The notification bar was not present at all.. Soft reboots started recurring so I tried to restart but it didn't work. I ended up pulling the battery.
I then entered CWM and took a different approach.. I followed some steps from "Weltwon" (http://forum.xda-developers.com/showthread.php?t=1276320&page=169) and it didn't even get pass the "Logo" screen.. I pulled the battery once again (uh-oh)...
After putting the battery back in, I entered download mode and tried to Odin back to EG30 but it still stalled at the "Logo" screen.
Being that I wasn't coming from another ROM, is it possible that I messed something up when I formatted system in the "mounts and storage" tab?
Hopefully it's not a goner.. Any help would be appreciated.
Here's my Odin log after using the stock kernal pulled tar file..
No pit was added..
<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> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
so let me get this straight.. you odin and everything was working properly. then you wanted to flash a custom rom and then you got errors. now you tried to odin again and you get stuck at samsung screen?
have you done this?
- ODIN with a different usb cable, or computer?
- redownload the roms?
ODIn to stock should boot and fix your errors in my expereince..
SocialReject said:
I'm not new to rooting, I'm coming from the Samsung Epic 4G.. My new Epic Touch 4G is stuck at the Samsung Galaxy II GT-I9100 Logo.. Really annoying. Here's what happened...
I rooted my new Epic touch with this link: http://www.forums.acsyndicate.net/s...lus-Stock-Rooted-BusyBox-CWM5-and-Plus-Tweaks
Everything was working fine.. I then wiped the phone (the usual) and flashed the stable Starburst ROM
I rebooted and started getting an error saying "Sorry! The application Status Bar (processcom.android.systemui) has stopped unexpectedly. Please try again."
The notification bar was not present at all.. Soft reboots started recurring so I tried to restart but it didn't work. I ended up pulling the battery.
I then entered CWM and took a different approach.. I followed some steps from "Weltwon" (http://forum.xda-developers.com/showthread.php?t=1276320&page=169) and it didn't even get pass the "Logo" screen.. I pulled the battery once again (uh-oh)...
After putting the battery back in, I entered download mode and tried to Odin back to EG30 but it still stalled at the "Logo" screen.
Being that I wasn't coming from another ROM, is it possible that I messed something up when I formatted system in the "mounts and storage" tab?
Hopefully it's not a goner.. Any help would be appreciated.
Click to expand...
Click to collapse
Silly question, but did you actually flash a ROM or just kernels after performing Weltwon's steps? I don't know what he was posting that regarding, but it seemed his instructions asked you to format /system (ie erase your ROM) but never mentioned flashing your new ROM by CWM or by Odin. Perhaps that was just understood in the context he was replying to, but if you didn't do so, you'd have a kernel on your phone but no ROM, meaning you could boot into Recovery, but there would be no ROM to boot into.
sfhub said:
Silly question, but did you actually flash a ROM or just kernels after performing Weltwon's steps? I don't know what he was posting that regarding, but it seemed his instructions asked you to format /system (ie erase your ROM) but never mentioned flashing your new ROM by CWM or by Odin. Perhaps that was just understood in the context he was replying to, but if you didn't do so, you'd have a kernel on your phone but no ROM, meaning you could boot into Recovery, but there would be no ROM to boot into.
Click to expand...
Click to collapse
I think I'm gonna just throw it away...
I woke up this morning and tried to boot into recovery and got a black screen sorta like this... "Phone . . Triangle with exclamation mark inside . . Computer"
I go into download mode and it says my Product name is GT-9100 !?
No computer ever recognizes it as a device, it's just a paper-weight now smh
if you cant get into download mode you might be screwed.. if you can tho, i recommend flash the eg30 with root, not just a kernel.. using odin and having it put in the pda slot with just auto reboot checked.. flashing just a kernel won't fix your problems
elliwigy said:
if you cant get into download mode you might be screwed.. if you can tho, i recommend flash the eg30 with root, not just a kernel.. using odin and having it put in the pda slot with just auto reboot checked.. flashing just a kernel won't fix your problems
Click to expand...
Click to collapse
I can get into download mode but the phone isn't recognized at all, by any of my computers.. My product name says GT-I9100 rather than SPH-D710. weird
hm.. if you can get into download mode try this guid out.. http://forum.xda-developers.com/showthread.php?t=1282415
Make sure you have correct drivers of course, make sure you try dif usb ports if possible and dif cables if possible.. maybe even a dif. odin
SocialReject said:
I can get into download mode but the phone isn't recognized at all, by any of my computers.. My product name says GT-I9100 rather than SPH-D710. weird
Click to expand...
Click to collapse
when you flash a rooted kernel, all our phones say GTI9100....
wase4711 said:
when you flash a rooted kernel, all our phones say GTI9100....
Click to expand...
Click to collapse
Oh. Well, I've tried different drivers.. Even reinstalled Kies but the phone won't recognize at all. I'll try some more USB cords.
wase4711 said:
when you flash a rooted kernel, all our phones say GTI9100....
Click to expand...
Click to collapse
Yea.. it does say GT I9100 with a exclamation mark in a yellow triangle.. besides that, his phone still isnt booting lol.. all you need is to get your pc to see the phone.. when you open Odin and plug phone in while in download mode, you don't get a COM to light up?? try using different version of Odin.. try restarting your pc etc etc.. try another computer if possible too.. trial and error lol, id keep putting your phone into download mode too.. i had this problem with my OG Epic.. it took a while but I finally got it to read in ODIN
elliwigy said:
Yea.. it does say GT I9100 with a exclamation mark in a yellow triangle.. besides that, his phone still isnt booting lol.. all you need is to get your pc to see the phone.. when you open Odin and plug phone in while in download mode, you don't get a COM to light up?? try using different version of Odin.. try restarting your pc etc etc.. try another computer if possible too.. trial and error lol, id keep putting your phone into download mode too.. i had this problem with my OG Epic.. it took a while but I finally got it to read in ODIN
Click to expand...
Click to collapse
Odin can't recognize it because my computer doesn't even recognize it. I plug it in and go to device manager and there's no signs of it. Maybe it's the drivers, idk. I haven't even activated it to Sprint yet so I doubt that they help a "stranger"
Try a USB jig
Sent from my Samsung Galaxy S2
I heard usb jig only works if I can't already get into download mode.
Sent from the future.

soft brick issues

ive been trying to fix this issue on my own for the past 5 hours but just cant so i'm going to try to get help from you lovely people at XDA.
so i tried to unlock my bootloader using CASUAL and it soft bricked my phone failing half way through. now when i try to boot into the OS, it says theres been a fireware problem, reset using kies.
so kies is not compatible with verizon note 2's, awesome, i know.
so i try to use ODIN to flash a stock rom in download mode. and ODIN will not recognize my phone in download mode. ive tried every driver package under the sea and nothing seems to work. and on top of that, when ODIN used to work, it kept failing at boot.bin files and would fail.
so i cant get ODIN to recognize my phone any more, but my computer does, and the files i try to download all fail at the boot.bin file.
any help would be great, i know i can get this phone fixed its just very frustrating at the moment.
for those wondering, i fixed this issue by using another windows computer to find my phone via odin,
then just flashed the PIT file, nothing in the PDA section.
phew. trial and error.
where did you get PIT file?
bryannh said:
for those wondering, i fixed this issue by using another windows computer to find my phone via odin,
then just flashed the PIT file, nothing in the PDA section.
phew. trial and error.
Click to expand...
Click to collapse
Where did you get the PIT file??

NAND write FAIL

Hello,
Before the update of 4.3, everything was working perfectly. The phone was rooted prior to the update.
After the update, I can't root the phone. I tried Odin 1.85/87, 3.07 & 3.09. It always says the same error (beside the 1.85v which just stop working).
The phone works well. It connects to the computer too. Only the Odin 1.87 see the phone when it is in download mode. The other versions I had to boot the phone connect it, **** it down then go into download mode for odin to say ''added''.
Anyway... I am about to throw this phone in the garbage. Un-rooted phone are not fun. Pun intended.
Maybe you need updated drivers? Did you follow the 4.3 rooting guide?
If your phone still has warranty, rooting a stock 4.3 ROM will it.
Problem fixed!
/Thread.
Used windows XP.
No more warranty. Never used anything else than the stock simply because I just don't have the time and am quite lost with all the custom rom and their advantages.
------
EDIT: I used Odin 3.09 clicked on AP then selected the .md5 file. It passed but I got the message that it didn't work. Herm.

[Q] Stock S3 stuck on boot cycle, can't access recovery mode, and odin fails

Hi a few days ago my phone was restarted and it got stuck on the samsung galaxy s3 screen. It is a t-mobile sgh-t999 model. It will boot into download mode but not recovery. After trying Kies to no result. I have deleted it from my pc and attempted to recover by flashing the stock rom using odin. I've tried that many times and always fails as well.
I have reinstalled s3 drivers. Made sure Kies is completely gone. I have downloaded the stock rom and three versions of Odin 3.04 3.07 and 3.09 and I get the same results. A write failure. Does anyone have any ideas how to proceed?
One observation I've noticed is that the bar underneath the Android in Download mode never appears. Which leads me to think that it never starts the process of taking the firmware.
Any ideas what to do next?
What is the error message?
Having same trouble
hi Serio22
NAND Write Start!!
FAIL!
Complete(write) operation failed.
serio22 said:
What is the error message?
Click to expand...
Click to collapse
Hi Serio22
NAND Write Start!!
FAIL!
Complete(write) operation failed.
Same exact issue on my sgh-t999
This morning it restarted itself (plugged into charger all night) and stuck at Samsung Galaxy SIII on screen. Recovery doesn't work and it will go into download mode. I am downloading the stock firmware from (sammobile firmwares SGH-T999) and will try installing with Odin tomorrow.
I will likely fail like you guys. I have taken such good care of the phone, never drop it, not a scratch on the screen...and this randomly happens in the middle of the night.
Please update!
Same exact issue on my SGH-T999 which makes me wonder that this is some software update issue that has possibly impacted many phones at this time.
In my case, it also restarted by itself this morning and got stuck at Samsung Galaxy SIII on screen. I started from figuring out if it was a hardware issue but the phone seems OK physically (i.e. the power button is not stuck, etc.). Recovery doesn't work and it will go into download mode like indicated by others above. I tried downloading the stock firmware SGH-T999 from Sammobile (actually a couple of different versions and tried installing via Odin 3.-07 many times but always failed with the error message above or
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
I also tried installing non-stock recovery files (TWRP, trying CWM at the moment) and that worked but without success in changing anything in the initial issue.
Sounds like they are sending bad firmware bricking our phones over night. Sorry I've found no solution yet.
whattheschmidt said:
Same exact issue on my sgh-t999
This morning it restarted itself (plugged into charger all night) and stuck at Samsung Galaxy SIII on screen. Recovery doesn't work and it will go into download mode. I am downloading the stock firmware from (sammobile firmwares SGH-T999) and will try installing with Odin tomorrow.
I will likely fail like you guys. I have taken such good care of the phone, never drop it, not a scratch on the screen...and this randomly happens in the middle of the night.
Please update!
Click to expand...
Click to collapse
Just an observation. I too was only getting the
"Complete (Write) operation failed." message at first.
After trying to flash the stock rom via Odin multiple times, I now get
"NAND Write Start!!"
"FAIL!"
Hope I didn't make it worse.
MarcinT said:
Same exact issue on my SGH-T999 which makes me wonder that this is some software update issue that has possibly impacted many phones at this time.
In my case, it also restarted by itself this morning and got stuck at Samsung Galaxy SIII on screen. I started from figuring out if it was a hardware issue but the phone seems OK physically (i.e. the power button is not stuck, etc.). Recovery doesn't work and it will go into download mode like indicated by others above. I tried downloading the stock firmware SGH-T999 from Sammobile (actually a couple of different versions and tried installing via Odin 3.-07 many times but always failed with the error message above or
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
I also tried installing non-stock recovery files (TWRP, trying CWM at the moment) and that worked but without success in changing anything in the initial issue.
Click to expand...
Click to collapse
SGH -t999 Pit File
Does anyone have any idea if flashing the stock rom with the T999 pit file in Odin possibly fix this problem? I've been reading about it, but can't really determine if this is the next step to troubleshoot this problem.
Write start and immediate fail in my case as well.
Keep looking into this and updating thread. I already ordered a new phone because of this but will want to fix this phone to sell it if not just sell the new one and stick with this longer...
I tried updating to the newest version of ROM using Kies but that did not work, either. Sometimes the phone cannot be recognized by Windows and sometimes Kies says it is "connecting" with the phone. When I tried updating, Kies did not see the phone, so maybe it had a negative impact on the download. I am going to uninstall the drivers and install them again just before connecting the phone to Kies and try updating again. This stuff is really time consuming.
I could not find a good CWM recovery file to flash via Odin so I did not try that. The interesting thing is that successfully flashing TWRP recovery file did not do anything - I still cannot get into recovery mode. Then I tried flashing stock recovery file again - and got the FAIL! message from Odin.
I've seen other threads talking about this issue, but don't remember if it was ever fixed. Have you guys tried different cables or computers?
I've tried a different cable (non-stock) but that did not help at all. I can try a different computer and will report here.
No update on fixing the phone...I tried everything I could on my end really. I think I will have to look at sending it in to Samsung?
I bought a used S5 on ebay. Much faster and nicer...liking it quite a bit. Samsungs update to break my phone and buy a newer Samsung worked I guess.
Daughter's SIII crashed also, her phone was bootlooping. Since her volume button doesn't work, I used a jig to put into D/L mode. Flashed T999LUVUBOH1_T999LTMBBOH1_T999LUVUBOH1_HOME.tar.md5 from Sammobile and ODIN said it passed. The phone will not go passed the "T-Mobile 4G LTE" screen. I've tried several times, always passes, always gets stuck.
Daughter doesn't mind, she's been using the Note II that I didn't want to part with after getting myself the Note 5
When flashing the stock rom with Odin, do not check anything except f.reset time. After flashing, and seeing the word reset in the status window, remove USB cable, remove battery, replace battery, boot into recovery, assuming the volume up me home button work, no perform a factory wipe.
The volume up and down button don't work?

Can you help my N7100 wont boot up because its stuck in boot loop.

Hi everyone. This is the first time ive posted anything on here. I will try to fully describe my problem that i really need help to fix.
My wife got my old Note 2 is rooted and she got my
Dad's old unrooted Note 2. After deciding that she didnt want a rooted phone she decided to use my father's unrooted phone. Due to apps updating and the internal memory getting full she ingored the warning message not really realising the outcome. The phone eventually shut itself down and is stuck on the Samsung logo (boot loop). So i gave her my old rooted phone back because she said that it just died. The same happened to the rooted phone too.
I asked before what she did and i was told nothing it just died. So i had nothing to go on. It wasn't until a week later when I tried to sort the problem out she said the System Memory was getting full and a message came up warning of this. So now I believe the problem is that the on board memory has got full and the phone seized. Much like what happens to a PC when the main hard drive gets full!
When i attempt to boot the phone up the Samsung logo show and stays on, never booting up. This happens with both phones. When i hold the Home key, Power button and Up volume switch. The phone loads the first Part of the boot up and at the moment it goes to the system screen it goes blank for a split second and back to the start of the boot. No matter how many times i try it fails. So I can't Factory reset or erase anything because i can get to it that screen.
So I try something else. I press the Home button, Power button and the Down on the volume to access the Download mode. This works fine. So i used Odin to try to put Rom onto the phone hoping this will solve the problem. Both phones connects to Odin alright and I can set up ready to load a rom onto it, however when i press start on Odmin to do its job everthing starts ok but then it goes red with a Failed error message. This happens when i try this on both phones, I seem to be stuck no knowing what to do. I have tried using all the ports on my laptop (window 7) and that makes no difference. The same happens on both devices.
I think i need to clear the memory somehow but have no idea how to do it when i can only access Download mode. I would be very grateful for any help on this but if all else fail I will try to build up static on a ballon and see if putting the near will wipe the memory, lol. Only joking. Im desperate to sort this out.
Any ideas?
Try to flash newest rom via odin using pit file.
What is the Odin error message? What file fails to flash? Is Odin able to pick up the partition information from the phone?
audit13 said:
What is the Odin error message? What file fails to flash? Is Odin able to pick up the partition information from the phone?
Click to expand...
Click to collapse
Hi audit13's Avatar. Thanks for your reply.
The file i downloaded from samsung. The offical rom N7100XXUFNL1
Below is what shows in the measage window.
<OSM>N7100XXUFN1_N7100EURFNG1_N7100XXUFNG1
<OSM>Chaecking MD5 finished successfully..
<OSM>Leave CS..
<ID:0/005>Odin v.3 engine (ID:5)..
<ID:0/005>File analysis..
<ID:0/005>SetupConnection..
<ID:0/005>Initialzation..
<ID:0/005>Set PIT file
<ID:0/005>DO NOT TURN OFF TARGET!!
<ID:0/005>Can't open the specific file.. (Line: 1876)
<OSM>All threads completed. (Succeed 0 / failed 1)
I dont understand the 3rd question... how do u check that?
zett89 said:
Try to flash newest rom via odin using pit file.
Click to expand...
Click to collapse
Thanks for your reply. Not sure how to that?
You're using the latest rom from sammobile.com? If you are, you're unzipping it to have a tar.md5 file? Looks like you may not need a pit file as Odin is able to read the pit information from the phone.
audit13 said:
You're using the latest rom from sammobile.com? If you are, you're unzipping it to have a tar.md5 file? Looks like you may not need a pit file as Odin is able to read the pit information from the phone.
Click to expand...
Click to collapse
What should i do then. Could you walk through it as im a bit of a novice...
You may not need a pit file as Odin looks like it can read the information from the phone. Try flashing the stock ROM from Sammobile.com.
If the ROM doesn't flash, try different USB cables and USB ports.
download newer version of Odin HERE
and uncheck repartition.
yaro666 said:
download newer version of Odin HERE
and uncheck repartition.
Click to expand...
Click to collapse
Will do. I will keep you posted...

Categories

Resources