Database Users

[HELP] Is my vibrant completely bricked?

Not sure if this is the right section or not, but I felt I would get the best response from this forum.
OK.. so I was running euegene's Vibrant6 ROM, but I was having trouble getting any of the lagfixes to work correctly. So I decided to follow the steps outlined in this post: ((apparently I cannot post links))To flash the stock rom and so on. I had never used odin before, but a quick google search found me some directions and it seemed simple enough. So I try to flash with odin and I kept getting stuck at "File analysis.." After disconnecting my phone and trying to restart it, the phone would just go to the screen with the phone + warning sign + a computer. I was able to get back in to download mode from there. Still could not progress past the file analysis. I tried all of the tips outlined in this thread(apparently I cannot post links)) and after reading that last post, I was able to uninstall my previously existing drivers from my moto cliq.
Finally, odin progressed passed the file analysis and was flashing the filesystem.rfs file. I had a nice blue progress bar on the downloading screen, I thought everything was going to be fine. Then my phone went to a blank Blue Screen. The progress bar in odin seemed stalled at about 25%. As this was my first time using odin, I had no idea if this was normal. I let it sit this way for a good 10 - 15 min. No change. At this point I started getting concerned and thinking this can't be normal. I gave it a few more minutes and still no change. Odin was still just sitting there, right about 25% on filesystem.rfs and blank blue screen on the phone. So then I unplugged the phone, pulled the battery and put it back in, expecting that phone - error sign - computer screen again and hoping to reboot the pc and try again. No such luck.
Now my phone will do nothing. Plugged in to the pc with odin running no response whatsoever from the phone. Plugged in to the wall, no response. It's like I'm trying to turn it on without the battery in. I fear the worst and I'm 99.9% sure you guys will just confirm this as I can't get in to ANYTHING. What I would really like to know though is where I went wrong. Is it really normal for an Odin flash to take that long and to sit at that point?
EDIT: Quick follow-up question, and this is probably going to sound completely stupid, but I don't really care: is the "internal sd" an actual micro sd card that can be accessed at all, so that I can at least get my pictures/videos and such off of if I have to get a new vibrant?

this should be posted in the q/a section
I'm no expert, and I'm not sure what went wrong, but you can try to unplug phone from the USB charger, unplug the battery, put battery back in, hold volume up + volume down and plug back into usb charger (connected to computer) to see if you get a responce from the phone.
Sent from my SGH-T959 using XDA App

merrifield69 said:
this should be posted in the q/a section
I'm no expert, and I'm not sure what went wrong, but you can try to unplug phone from the USB charger, unplug the battery, put battery back in, hold volume up + volume down and plug back into usb charger (connected to computer) to see if you get a responce from the phone.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thank you for the quick response. Sorry about the wrong section, wasn't really sure this would fit best. Tried what you said and IT WORKED first try. I'm now in download mode. NOW, I would like to retry the flash with odin, but I also need to know if I'm doing something wrong, or if this was a fluke? Should odin sit at that point (25% flashing filesystem.rfs) for that long with a blue screen on the phone? I was under the impression it should be a pretty fluid and somewhat quick process.

skoozi said:
Thank you for the quick response. Sorry about the wrong section, wasn't really sure this would fit best. Tried what you said and IT WORKED first try. I'm now in download mode. NOW, I would like to retry the flash with odin, but I also need to know if I'm doing something wrong, or if this was a fluke? Should odin sit at that point (25% flashing filesystem.rfs) for that long with a blue screen on the phone? I was under the impression it should be a pretty fluid and somewhat quick process.
Click to expand...
Click to collapse
when i flashed using odin i didnt seen any blue screen only the download screen wha are ou trying to flash are you sure its for the vibrant?

cdw9800 said:
when i flashed using odin i didnt seen any blue screen only the download screen wha are ou trying to flash are you sure its for the vibrant?
Click to expand...
Click to collapse
Yes, I downloaded a rar for stock vibrant, it contains :
s1_odin_20100512.pit which i put in the PIT field, and T959UVJFD.tar, which i put in the PDA field
EDIT: this is from the "odin1.0_T959UVJFD_512.pit_rootupdate.rar" which is linked in a few posts in this forum.

yeah those are correct. try having re-partition checked because that worked for me. also, make sure you dont have any files on the csc field. are you using the correct drivers on your system??

rpesigan6 said:
yeah those are correct. try having re-partition checked because that worked for me. also, make sure you dont have any files on the csc field. are you using the correct drivers on your system??
Click to expand...
Click to collapse
Every time I try it with the re-partition option clicked it seems to hang at this status:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
I am retrying this now, I have a small fraction of the blue progress bar on the "Downloading..." screen on my phone. Neither the device nor odin seem to be doing anything. How long should this normally take?
As far as I know the drivers are correct.. I installed the x64 drivers from the link provided in the informative links sticky in this forum. adb was working fine.. device manager lists the phone as "SAMSUNG USB Composite Device" and Driver details window lists three .sys files w/ version 5.16 built by WinDDK
EDIT: not sure if this helps.. here is screen shot of odin & driver details h**p://i37.tinypic.com/2cn8501.jpg (will not allow me to link or post img)

ok instead of flashing the s1_odin_20100512.pit in the PIT field, try flashing the other PIT which should be s1_odin_20100513.pit
THAT IS WITH THE 13, NOT THE 12.
you can find the 13.pit in one of the rar files. look deep into the rar files. im pretty sure you will find it

rpesigan6 said:
ok instead of flashing the s1_odin_20100512.pit in the PIT field, try flashing the other PIT which should be s1_odin_20100513.pit
THAT IS WITH THE 13, NOT THE 12.
you can find the 13.pit in one of the rar files. look deep into the rar files. im pretty sure you will find it
Click to expand...
Click to collapse
Unable to find any such file. After some google'ing, I was able to find an s1_odin20100513.pit from the samsungfirmwareworld i9000 forum. tried that with re-partition still checked. Same result. Tried again with re-partition unchecked, it gets to modem.bin, tries to work and then my phone goes to a blank RED screen.

skoozi said:
Unable to find any such file. After some google'ing, I was able to find an s1_odin20100513.pit from the samsungfirmwareworld i9000 forum. tried that with re-partition still checked. Same result. Tried again with re-partition unchecked, it gets to modem.bin, tries to work and then my phone goes to a blank RED screen.
Click to expand...
Click to collapse
a blank red screen? all i can say is possibly try using another windows computer.

rpesigan6 said:
a blank red screen? all i can say is possibly try using another windows computer.
Click to expand...
Click to collapse
I had a similiar issue but mine was worse, I unplugged on accident during a kernal transfer. Get into download mode and keep the phone plugged in while you load ODIN. Then reset the phone back into download by removing the battery with it still plugged in. This should allow you to put the stock firmware back on. Use the 512/tar you already have. It is usually almost always an ODIN problem and not a truly bricked phone. I've ****ed my phone up a LOT and always able to revert after messing with ODIN.
Regards,
B

vibrantFTW said:
I had a similiar issue but mine was worse, I unplugged on accident during a kernal transfer. Get into download mode and keep the phone plugged in while you load ODIN. Then reset the phone back into download by removing the battery with it still plugged in. This should allow you to put the stock firmware back on. Use the 512/tar you already have. It is usually almost always an ODIN problem and not a truly bricked phone. I've ****ed my phone up a LOT and always able to revert after messing with ODIN.
Regards,
B
Click to expand...
Click to collapse
I'm trying to do this, but if I open ODIN with the phone already in download mode, ODIN does not see it. Pulling the battery and putting back in (downloading screen still up during this) does not change that. Maybe I misunderstood?
yes, i did.. likely at 4 am i guess.. so far its gotten past the modem.bin which it hasnt done in a couple hours of messing with this.. now its on filesystem.rfs again and stalling again, only now its only at about 10 - 15% as opposed to the 25% i was getting a couple hours ago before it stalled. This is with re-partition unchecked, btw. With it checked, odin still just sits at do not remove target.

I had this problem.. what I basically did was:
- Open Odin... add all the PIT and PDA files up (Re-partition UNCHECKED)
- Plug the phone in USB
- When the green battery was on the screen: hold volume buttons (basically.. get into download mode)
- Once in download Odin doesn't detect anything? Unplug USB and replug it back in
- Odin should detect your phone and one of the boxes should be labeled: COM[#]
Any # should be fine as long as you have the proper drivers
Then hit the start button. During this whole process, you should see the Android digging with a blue bar right below it. The screen shouldn't go black, blue, or anything crazy. Just android digging and a blue progress bar.
http://forum.xda-developers.com/showthread.php?t=734475&highlight=Stock Was the thread I used. Download hashtab (google it) and verify that the MD5 checksums are correct, once installed right click the file -> properties -> hashtab and then copy paste the MD5 on that thread an verify that it is correct.
For me the Odin process took less than a minute, the trick for me was to preload everything in Odin before plugging in the phone otherwise it would get stuck.
Personally, I don't think your phone is bricked anyway. Just some technical difficulties with getting Odin to work. The first time around when I was trying out Odin, it was messing up for me. Hope this helps.
Vibrant Drivers: http://forum.xda-developers.com/showthread.php?t=728929 -- If these aren't the set of drivers you're using, then uninstall yours and install this. This one works with no problems.

rpesigan6 said:
a blank red screen? all i can say is possibly try using another windows computer.
Click to expand...
Click to collapse
Was able to try this this morning.. it worked first try. With all the problems I was having, I was dumbfounded with how smooth it went. Don't know what was going on. Thank you all for your help with this

Hey guys, I figured I'll post here since I think I bricked my phone.... I was trying to install Eugene's Vibrant6 and I got stuck on the Vibrant Logo with Samsung at the bottom. I tried to reset with both volume buttons and power button and got to grey battery and nothing else... what can I do? Anyone can help me?
Thanks.

I fear my problem is worse as i was having the same issue with it loading filesystem.rfs and was stalling so i attempted to restart the process and now all that will display on my phone is an image of a cell phone a computer and a yield sign between. Plz help

Sounds like you need to upgrade Odin3 1.0 to Odin3 1.7

Ok i DL'ed Odin3 1.7 and still the same. The vibrant screen doesn't even come up, just an image of a cell phone and a comuter with a yield sign in between.

Start odin on your pc, remove batt, insert USB, hold down volume buttons and pop in the batt. This always gets me into download.
Sent from my SGH-T959 using XDA App

May god bless you and your children, and your childrens children, and their children!!!!!!!!!

Hello! Problem with ODIN

I recently bought my SGS International version and very pleased with it, in an attempt to improve its performance I tried to install a new ROM.
The process of hacking the root user I didn't encounter any issues, however, when I tried to flash using ODIN it didn't seem to work. I selected the files, connected SGS (debugging mode), the software recognized the phone (yellow bar with com port), but I click to start received the following:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
It seemed to be stuck on file analysis.
Perhaps the ODIN version I'm using isn't up to date? With that in mind can anyone give me a download link? (had trouble finding one).
Also, I'm not sure if it's related or not, but Kies refuses to recognize my device, it's getting stuck with the message connecting.
Any thoughts?
Thanks!

uncheck the debugging mode.

you must boot into a special mod named download mode.
to do this, you have to power down your phone, take the battery out for a few sec, remove sim and external sd card,then plug in the battery and press volume down button, keep it pressed, press home button, keep it pressed, then press power button until you see an android robot with a shovel. it will say:downloading... and below: do not turn off target!!! then you can open odin, select the files you want to download then connect the phone (important!) then you can start flashing.
hope this helps.

u dont need to take the battery out to get in to download mode!

you know just for dischargement and safety, this will be 100 percent safe if odin doesnt screw up.

Thank you all for your replies!
However. I run odin while the phone is download mode, I have the digging android while I do the above

Odin 1.7 is on the forum or google/search .
Your problem may be the rom rather than Odin ..
http://forum.xda-developers.com/showthread.php?t=846913
jje

Thanks for the link, the rom is darkys, which is well known. I'll try with a newer version of odin when I get home

the rom is darkys, which is well known
Known for what ???
jje

It failed with another rom I tried though

Eladku said:
It failed with another rom I tried though
Click to expand...
Click to collapse
No offence but I think you haven't got a clue what your doing. Best to research some more and actually understand what your trying to achieve.

help with bricked SM-G900T1

My internal memory was getting full and so I was trying to clean up some junk. Well, I must have deleted too much!!! After trying to reboot, I received error message "Could not do normal boot"and it goes into odin. I tried to use odin to flash it back to stock, but no luck. It appears like I need a bootloader in order to solve this issue. Any suggestions? Thank you so very much.

If you need a bootloader,
give a look in this thread
http://forum.xda-developers.com/showthread.php?t=2732110
(second or third o fourth post)

many110 said:
My internal memory was getting full and so I was trying to clean up some junk. Well, I must have deleted too much!!! After trying to reboot, I received error message "Could not do normal boot"and it goes into odin. I tried to use odin to flash it back to stock, but no luck. It appears like I need a bootloader in order to solve this issue. Any suggestions? Thank you so very much.
Click to expand...
Click to collapse
Your phone is not bricked if you are getting system error messages or able to boot to download (Odin) mode. Bricked means that a phone responds the same as a brick does. So unless you have a red clay brick that also boots to download mode..
To fix your phone, go to download mode and flash the full stock firmware image for your model /carrier. You should do this in conjunction with the correct PIT file for your phone. Many people skip the PIT file and still prevail. But it's an unnecessary risk to skip it and you would do so at your own peril.
You say that flashing stock didn't work, but you provided no details whatsoever. You don't need a new bootloader, you need to use Odin correctly. To help spot where you are going astray, you need to describe step by step how you are using Odin, the name of the stock firmware file you are flashing, your phone model and verbatim, what you see on the Odin screen. A screen shot or photograph of the download mode screen on the phone would help too.
.

fffft said:
Your phone is not bricked if you are getting system error messages or able to boot to download (Odin) mode. Bricked means that a phone responds the same as a brick does. So unless you have a red clay brick that also boots to download mode..
To fix your phone, go to download mode and flash the full stock firmware image for your model /carrier. You should do this in conjunction with the correct PIT file for your phone. Many people skip the PIT file and still prevail. But it's an unnecessary risk to skip it and you would do so at your own peril.
You say that flashing stock didn't work, but you provided no details whatsoever. You don't need a new bootloader, you need to use Odin correctly. To help spot where you are going astray, you need to describe step by step how you are using Odin, the name of the stock firmware file you are flashing, your phone model and verbatim, what you see on the Odin screen. A screen shot or photograph of the download mode screen on the phone would help too.
.
Click to expand...
Click to collapse
I tried using the "u1_02_20110310_emmc_EXT4.pit" along with "CF-Auto-Root-kltemetropcs-kltemetropcs-smg900t1.tar.md5", on "Odin3-v3.07" and I get, what looks like the download mode, except it states in the upper right hand corner (in red letters) "Could not do normal boot". The only way out is to do a battery pull. It will allow me to go into "Download mode", as the second picture indicates, and Odin states stays on "Reset". The message it states is as follows: D:0/006> NAND Write Start!!, <ID:0/006> cache.img.ext4, <ID:0/006> RQT_CLOSE !!, <ID:0/006> RES OK !!, <ID:0/006> Removed!!, <ID:0/006> Remain Port .... 0, <OSM> All threads completed. (succeed 1 / failed 0), <ID:0/006> Removed!!. Then I once again get the "Could not do normal boot" error message.
Any Suggestions? I greatly appreciate your help. Thank you.

Can you boot into recovery?
Sent from my SM-G900F using XDA Free mobile app

many110 said:
Any Suggestions?
Click to expand...
Click to collapse
You aren't following the suggestions made earlier. You are taking shortcuts that you think won't matter and introducing all kinds of variables. And failing. If you really want to get your phone working, you should follow the advice rather than taking liberties and winging it.
Flash a stock firmware image, not a modified image intended for rooting. First you need a stable system - you can root afterwards. Make sure it is a 100% stock tar for your carrier and use Odin 3.09 instead of the older version you have. Flash the firmware .tar file and PIT file at the same time, with the PIT, F. reset and auto reboot checked in Odin. If the Odin flash fails, try a different USB cable and port. A different computer if you need too.
Also you gave no details about the PIT file, other than the file name. We cannot tell if that is the correct file for your phone. The PIT file needs to match your phone model, ROM size and carrier. There is a XDA thread that should have the correct file. Probably the one that I uploaded here.
As well, if you get an Odin flash failed message, do not close or reset Odin. Instead pull the battery on your phone, replace it and then boot to download mode (press and hold volume down, then home, then the power button). Then try flashing again. The flash will inevitably succeed the second time, even though it failed at first.
.

fffft said:
You aren't following the suggestions made earlier. You are taking shortcuts that you think won't matter and introducing all kinds of variables. And failing. If you really want to get your phone working, you should follow the advice rather than taking liberties and winging it.
Flash a stock firmware image, not a modified image intended for rooting. First you need a stable system - you can root afterwards. Make sure it is a 100% stock tar for your carrier and use Odin 3.09 instead of the older version you have. Flash the firmware .tar file and PIT file at the same time, with the PIT, F. reset and auto reboot checked in Odin. If the Odin flash fails, try a different USB cable and port. A different computer if you need too.
Also you gave no details about the PIT file, other than the file name. We cannot tell if that is the correct file for your phone. The PIT file needs to match your phone model, ROM size and carrier. There is a XDA thread that should have the correct file. Probably the one that I uploaded here.
As well, if you get an Odin flash failed message, do not close or reset Odin. Instead pull the battery on your phone, replace it and then boot to download mode (press and hold volume down, then home, then the power button). Then try flashing again. The flash will inevitably succeed the second time, even though it failed at first.
.
Click to expand...
Click to collapse
What am I doing wrong????
I followed your advise and still no luck. You claim that my phone is not "bricked" but yet I did everything that you recommended and I'm still in the same place. I downloaded your "PIT.tar" file and had to change the name, because "Odin3 v3.09" would not recognize it. I put the pit file and AP file (AND YES, it is a full STOCK image) at the same time, tried it with "re-partition checked" and it failed! I tried it with out and it went through, but I am not able to get any further. Still getting "could not do normal boot"
"You state that I am taking short cut". Could you let me know what I am missing or at least direct me to a tutorial that does not show any short cuts? I get as far as seeing the "red android" figure, with and eye patch and it states that it will restart in 10 seconds. After reboot, I get the same message "Could not do normal boot". :crying:
By the way, would it matter that the pit file that you directed me to is for tmobile and this is a Metro pcs phone? Thank you.

I tried to give you good advice in my first post. Do you recall what I said?
Answer:
fffft said:
To help spot where you are going astray, you need to describe step by step how you are using Odin, the name of the stock firmware file you are flashing, your phone model and verbatim, what you see on the Odin screen. A screen shot or photograph of the download mode screen on the phone would help too.
Click to expand...
Click to collapse
And you still aren't doing so. You are not describing what you are doing step by step. You are not giving us file names so that we know which version of stock firmware you tried to install. Or whether it was really stock. You didn't paste the Odin log - what you saw onscreen. You pepper us with a summary and a few details and expect us to divine what has happened. It doesn't work that way. No one can help you constructively if you refuse to provide abundant information about your situation.
The best you can hope for is drive by guesses or perhaps someone patient that might try to cajole information out of you. We'd all like to help you, but you're making it difficult. It would be in your best interests to provide exhaustive detail because those details are the key thing that will enable people to help you. If you change your mind and provide the detail, someone in the forum will try to help you.
Good luck.
.

fffft said:
I tried to give you good advice in my first post. Do you recall what I said?
Answer:
And you still aren't doing so. You are not describing what you are doing step by step. You are not giving us file names so that we know which version of stock firmware you tried to install. Or whether it was really stock. You didn't paste the Odin log - what you saw onscreen. You pepper us with a summary and a few details and expect us to divine what has happened. It doesn't work that way. No one can help you constructively if you refuse to provide abundant information about your situation.
The best you can hope for is drive by guesses or perhaps someone patient that might try to cajole information out of you. We'd all like to help you, but you're making it difficult. It would be in your best interests to provide exhaustive detail because those details are the key thing that will enable people to help you. If you change your mind and provide the detail, someone in the forum will try to help you.
Good luck.
.
Click to expand...
Click to collapse
Well, I am not too sure how much more can be described from all of my last post, but here goes:
I power up the phone and I get a quick flash, before what looks like the download screen, appears and up at the top left hand corner the message reads "Could not do normal boot" and the under the green android figure are the words "Downloading... Do not turn off target!!"
I then continue to do a battery pull and I proceed to go into download mode (Holding vol. down button, home button and power button at the same time. I get Warning message and at bottom it states "Use volume up: continue, volume down: Cancel(restart phone). I push the volume up button. I am now in down load mode. If you look at the sceen at this point, this is how my SM-G900T1 is booting up, EXCEPT for those little red words at the top. In normal download screen, it states "ODIN"MODE". When I boot up my SM-G900T1, those little red words at the top say "Could not do normal boot" instead of ODIN.
Once I am in download mode, I proceed to use the files that you recommended (the .pit file and the AP file). I load up the files into Odin and I click, start. It begins to work and it then says, "RESET" while it is blue. My phone restarts and I see the red android figure with an eye patch and at the bottom it says, restart in 10 seconds.
the phone proceeds to restart and it goes back to that error message, which looks like the download mode, with the words up at the top , in red letters state "Could not do normal boot. ODIN MODE"
in white letters:
Product Name: SM-G900T1
Current Binary: Custom
System Status: Cusatom
Knox Warranty void: 0x1 (4)
Qualcomm Secureboot: enable (CSB)
RP SWREV: S1, T1, R1, A1, P!
UDC START
my phone goes no further than this and have kept it connected to odin. Now I look up at ODIN and it shows PASS!! in a green box with a time of 02:10. But my phone will not boot up. I restart and I get the message once again"Could not do normal boot"[/LIST
Hopefully someone could help. Thank you.

Well the important thing is that you can get to download mode (aka Odin mode) one way or the other.
Odin is well known for being fussy with cables, USB ports and other details, so don't panic if you get a failed Odin write or two. I also explained how to get around that in most cases.. leave Odin open on your PC screen and pull the phone battery again, go back to Odin mode on the phone and then press start on the Odin screen to try flashing a second time.
many110 said:
Well, I am not too sure how much more can be described from all of my last post
Click to expand...
Click to collapse
You are getting better with details (thanks) and I'm sure that this is frustrating to you. But you are nowhere near telling us step by step what you are doing. for a start, you didn't name the stock firmware image file that you were using, something that I specifically requested. So without meaning to offend you.. you aren't paying attention to details.
By "step by step", I meant a description of each step you took. For example listing each button you press in Odin.. telling us exactly what you type into each box and so forth. You may not see the point of that, but remember that we are not standing over your shoulder. And one wrong action can ruin your write. So that kind of step by step detail is extraordinarily valuable in troubleshooting.
Anyway, there are many ways to go about anything. Since you can get to download mode and your Knox bit is 0x1, I'd suggest installing or reinstalling TWRP, so that you can reliably boot to a stable recovery mode. From there you can look at almost anything, fix things, install custom ROMS, etc.
If you want to continue with Odin instead, then make sure that you are using a real stock .tar or .tar.md5 image, use a different USB cable and try again. If you are persistent, it will work.
.

fffft said:
You aren't following the suggestions made earlier. You are taking shortcuts that you think won't matter and introducing all kinds of variables. And failing. If you really want to get your phone working, you should follow the advice rather than taking liberties and winging it.
Flash a stock firmware image, not a modified image intended for rooting. First you need a stable system - you can root afterwards. Make sure it is a 100% stock tar for your carrier and use Odin 3.09 instead of the older version you have. Flash the firmware .tar file and PIT file at the same time, with the PIT, F. reset and auto reboot checked in Odin. If the Odin flash fails, try a different USB cable and port. A different computer if you need too.
Also you gave no details about the PIT file, other than the file name. We cannot tell if that is the correct file for your phone. The PIT file needs to match your phone model, ROM size and carrier. There is a XDA thread that should have the correct file. Probably the one that I uploaded here.
As well, if you get an Odin flash failed message, do not close or reset Odin. Instead pull the battery on your phone, replace it and then boot to download mode (press and hold volume down, then home, then the power button). Then try flashing again. The flash will inevitably succeed the second time, even though it failed at first.
.
Click to expand...
Click to collapse
any idea where i can get the PIT files for a metro s5?? i found the TAR file and used that in ODIN and it wont get past the metro splash screen. sits there for hours and gets REALLY hot. I tried doing a factory reset in recovery but it fails and reboots. Im hoping maybe a PIT file/repartition would do it i cant find a damn pit file anywhere. model number is G900T1. I used the stock firmware from the site below.
http://samsung-updates.com/details/26200/Galaxy_S5_SM-G900T1/SM-G900T1/TMB/G900T1UVU1ANCI.html

For future reference or anyone else reading this post. If you are running a stock ROM on a SM-G900T, even with root "memory low" alerts can be ignored becouse internal storage has a memory partition to act as emulated memory. In addition, android automatically unloads the oldest unused items from memory. I get these messages all the time, "internal memory usage exceeds maximum limit" or some such. They appear in the status bar without toasts, so their not too annoying. Yes you can clear a lot of stuff out with root,... But first understand your device AND what you intend to remove. If you don't understand it yet then leave it until you research it. Also, I recommend that you research your device before you buy it. I did, thats why my SM-G900T1 is a recent purchase, instead of going for the S6. Now if I could just find out how to root it without a computer when the kernel is dated Nov 10 2014.....
"The power of accurate observation is frequently called cynicism by those who don't have it."

Please delete. Wrong thread.

Help needed

My connection with the pc just got lost in the middle of a firmware update. Now i'm stuck in some special recovery mode ( the phone is asking to recover with samsung kies) but kies never get a connection with the phone. I tryed to install the firmware with Odin, everything goes just fine till the hidden image where the Odin gives me fail.
I cannot go to download mode or normal recovery mode.
Pls help!!!!

..

calinormy said:
My connection with the pc just got lost in the middle of a firmware update. Now i'm stuck in some special recovery mode ( the phone is asking to recover with samsung kies) but kies never get a connection with the phone. I tryed to install the firmware with Odin, everything goes just fine till the hidden image where the Odin gives me fail.
I cannot go to download mode or normal recovery mode.
Pls help!!!!
Click to expand...
Click to collapse
Did you terminate Kies in windows task manager? Kies can cause Odin to fail!

Ups. No. I will try this right now

fffft said:
You should do firmware writes with a notebook or UPS, a power interruption while writing critical system files can cause all kinds of damage.
Unfortunately you didn't provide much detail for us to work with. Not even a screenshot or photograph of what you see on the screen of your phone now or the log from Odin or Kies. Even your thread title didn't convey any useful information.
Pull your phone battery. Then try to enter download mode by pressing and holding the volume down key, then the home key, then the power key. Then try to flash a full, stock firmware image and proper PIT file concurrently. If you run into any difficulties, give a detailed description of what you tried, the Odin log and a photo of the phone screen.
More than likely it's recoverable. Despite the lack of details in your post, your stumbling block is probably that you aren't using a PIT file to correct (likely) partition damage that occurred during your power interruption.
.
Click to expand...
Click to collapse
I resolved my problem. I just flashed the pit file only with repartition checked in Odin and after that my phone just came alive. No need to flash full firmware. Thanks for help to you and everyone!

SM-G900F bricked (?) water damaged - can get into download mode

Felt slight stupid as I saw my s5 going round the washing machine, thought I'd have a play after it's dried out.... I like learning but don't really know phones.
It was encrypted but was stock firmware.
Currently:
- It powers on
- I can get to the download in boot ok (vol. down)
- It resets when trying to get into recovery mode
- Kies see's something trying to connect but times out. Heimdall detects it but throws errors upon trying to flash , I'm yet to try Odin, just getting stock firmware as I write this.
(Heimdall error - libusbx: error [winusbx_submit_bulk_transfer] ReadPipe/WritePipe failed: [22] Th
e device does not recognize the command.)
I've got some more playing around to do but it feels like, at least, the storage is screwed but that's a complete guess.
1) I was hoping someone would know if it's worth playing further?
2) Whether anyone could take a guess of whether replacing the mother/logic board would be a *possible* fix
3) Could anyone point me to any resources explaining the how the phone works- I'm initially trying to understand what components sit on the logic board and the boot sequence. e.g. could the CPU/ storage be fried but it still boot this far?
Many thanks in advance for any help.

OK, I'm a little further along with this now.
I'm using various versions of odin (3.0.7,9,12.3). Various computers (all windows 10 now but did try heimdal on a 2 nix machines) and a whole lot of leads. Just getting Odin to recognise the phone was fun.
Tried using the AP part to install the BTU UK version of firmware from sammobile
Tried getting the hidden .img.tar from it and flashing that
Tried flashing a twrp recovery
But all come up with
Code:
GetPIT for Mapping
There is no PIT Partition
So I got a couple of Pit files for and tried them with the Re-partition ticked
Code:
Set PIT file...
DO NOT TURN OFF TARGET!!
Complete (Write) Operation failed
OSM All threads completed (succed 0/ failed 1)
So a few questions:
1) How do I uploda photos here? Or do they have to be inserted links. May be my low post count? Or I'm blind
2) Is it normal that odin stops recognising the phone the moment there's an error like the one's I'm having. Odin's ID:COM part goes blank and I have to remove/ insert the USB again.
I just want to check that's not some other reason.
3) Is there anyway to test whether the NAND's working/ can be accessed without pressing that scary NAND erase all button?
Many thanks

Why not just get it fixed from service center?

beardedfool said:
OK, I'm a little further along with this now.
I'm using various versions of odin (3.0.7,9,12.3). Various computers (all windows 10 now but did try heimdal on a 2 nix machines) and a whole lot of leads. Just getting Odin to recognise the phone was fun.
Tried using the AP part to install the BTU UK version of firmware from sammobile
Tried getting the hidden .img.tar from it and flashing that
Tried flashing a twrp recovery
But all come up with
Code:
GetPIT for Mapping
There is no PIT Partition
So I got a couple of Pit files for and tried them with the Re-partition ticked
Code:
Set PIT file...
DO NOT TURN OFF TARGET!!
Complete (Write) Operation failed
OSM All threads completed (succed 0/ failed 1)
So a few questions:
1) How do I uploda photos here? Or do they have to be inserted links. May be my low post count? Or I'm blind
2) Is it normal that odin stops recognising the phone the moment there's an error like the one's I'm having. Odin's ID:COM part goes blank and I have to remove/ insert the USB again.
I just want to check that's not some other reason.
3) Is there anyway to test whether the NAND's working/ can be accessed without pressing that scary NAND erase all button?
Many thanks
Click to expand...
Click to collapse
Yeah that sounds like water damage alright. I'm sorry to tell you it sounds like your NAND is semi-corrupted in that part of the BL seems to have survived but basically everything else is kaput.
If the PIT partition is missing that is a flag right there to a likely NAND corruption.
Sorry to be the one to have to tell you this but at this point you're best bet is to take it as a total loss and try to sell any undamaged parts (ex. Digitizer, LCD) to raise the cash for a new phone.