Soft or Hard Brick??? - T-Mobile Samsung Galaxy S 5

I have a G900T that I was a running Skiesrom CFW for about a month until I noticed it stopped detecting the sim card, getting constant reboots and restarts instead of powering down. I went to stock with odin thinking it would fix it but it did not. Any suggestions and opinions would greatly be appreciated. Thanks.

---

Happened to me too once when i flashed wrong rom using odin which lead me to Nil Baseband version and IMEI
Did u check them if they are ok

---

Install a SD card checking (SD Insight is the one I use) and check your SD card. There are thousands of fakes around that report they have much more storage than they actually do. They work fine at first until they fill up and you start trying to store data in locations that don't actually exist.

---

Sam7777777 said:
Happened to me too once when i flashed wrong rom using odin which lead me to Nil Baseband version and IMEI
Did u check them if they are ok
Click to expand...
Click to collapse
It looks like that may be the problem. It says unknown for both. Will try to fix and hope it works. Thanks.

---

fresco194 said:
It looks like that may be the problem. It says unknown for both. Will try to fix and hope it works. Thanks.
Click to expand...
Click to collapse
Not as easy as I though.

---

Have service mode also gone blank? u can check it using #*9090#
if yes, then your phone has kinda gone far from the normal damage state imo, as normal restore things like odin etc. doesn't help
Check Device Serial Number, if that's fine
IDK your Knowledge level but
Read this post till the End before attempting to do anything
I had recovered my phone from the following scenerio
1. Baseband - Unknown
2. IMEI - Nil
3. Service mode - Blank with horizontal lines
4. No Sim detection
5. Random reboots and restart instead of Power off
BUT
6. Seriel Number - Ok (Original)
In my case i wasn't able to get back imei baseband, no matter what i do, restoring efs backup, trying diffrent baseband, stock restore everything using odin diffrent Rom versions too but
nothing worked
I followed the steps given in thread mentioned below to recover my device, This thread and file/s mentioned in there are for Note 3 only
but i used the Note 3 file on S5 with SM-G900T PIT file,
Don't use PIT file from NOTE 3 (Thread)
Everything is back to normal except Service Mode is partially recovered, still i have it that way
(writing Note 3 file on S5 , i guess, the reason for broken service mode)
Here's the thread
https://forum.xda-developers.com/showthread.php?t=2567133
I had followed it till adb commands only, as far as i remember, didn't follow seriel number editing etc.
I'd recommend to follow the thread only if have have tried other ways to get around the issue and you are sure your phone is unrecoverable by any other means
bcuz Nowadays unknown baseband and nil imei happens too me sometimes but going stock ALWAYS gets them back
i'd recommend you to Backup your IMEI (EFS) Folder in current state (Most probably it is not corrupted) and store in somewhere safely and to be on a safer side backup bootloader too (Bootloader not needed but...you never know if you are not much of a developer)
Backup in multiple formats and with multiple tools (I always wanna play safe), Flashfire also backsup EFS
You can also backup whole folder manually too, your choice
For bootloader backup
i used following ADB command as Root
busybox dd if=/dev/block/mmcblk0 of=/sdcard/200MB.img bs=4096 count=50000
I don't know if this will work for you, Don't hold me responsible if your device gets even worse, just trying to help ; )
Lemme Know if any clarification is needed

---

Sam7777777 said:
Have service mode also gone blank? u can check it using #*9090#
if yes, then your phone has kinda gone far from the normal damage state imo, as normal restore things like odin etc. doesn't help
Check Device Serial Number, if that's fine
IDK your Knowledge level but
Read this post till the End before attempting to do anything
I had recovered my phone from the following scenerio
1. Baseband - Unknown
2. IMEI - Nil
3. Service mode - Blank with horizontal lines
4. No Sim detection
5. Random reboots and restart instead of Power off
BUT
6. Seriel Number - Ok (Original)
In my case i wasn't able to get back imei baseband, no matter what i do, restoring efs backup, trying diffrent baseband, stock restore everything using odin diffrent Rom versions too but
nothing worked
I followed the steps given in thread mentioned below to recover my device, This thread and file/s mentioned in there are for Note 3 only
but i used the Note 3 file on S5 with SM-G900T PIT file,
Don't use PIT file from NOTE 3 (Thread)
Everything is back to normal except Service Mode is partially recovered, still i have it that way
(writing Note 3 file on S5 , i guess, the reason for broken service mode)
Here's the thread
https://forum.xda-developers.com/showthread.php?t=2567133
I had followed it till adb commands only, as far as i remember, didn't follow seriel number editing etc.
I'd recommend to follow the thread only if have have tried other ways to get around the issue and you are sure your phone is unrecoverable by any other means
bcuz Nowadays unknown baseband and nil imei happens too me sometimes but going stock ALWAYS gets them back
i'd recommend you to Backup your IMEI (EFS) Folder in current state (Most probably it is not corrupted) and store in somewhere safely and to be on a safer side backup bootloader too (Bootloader not needed but...you never know if you are not much of a developer)
Backup in multiple formats and with multiple tools (I always wanna play safe), Flashfire also backsup EFS
You can also backup whole folder manually too, your choice
For bootloader backup
i used following ADB command as Root
busybox dd if=/dev/block/mmcblk0 of=/sdcard/200MB.img bs=4096 count=50000
I don't know if this will work for you, Don't hold me responsible if your device gets even worse, just trying to help ; )
Lemme Know if any clarification is needed
Click to expand...
Click to collapse
All of your scenarios is exactly what is going on with mine to the "T". Service mode is blank and I do get a serial number but blank IMEI. Even my phone powered on on it's own from being completely shut down for a while. I tried flashing PIT with odin to tried to re-partition but it would not flash. Gives me a secured failed in download mode. I will look into your suggestion. Thanks.

---

fresco194 said:
All of your scenarios is exactly what is going on with mine to the "T". Service mode is blank and I do get a serial number but blank IMEI. Even my phone powered on on it's own from being completely shut down for a while. I tried flashing PIT with odin to tried to re-partition but it would not flash. Gives me a secured failed in download mode. I will look into your suggestion. Thanks.
Click to expand...
Click to collapse
Unfortunately I did'nt get very far. I tried to odin flash a clean rom with a pit file and I get: Secure Check Fail : PIT:crying:

---

fresco194 said:
Unfortunately I did'nt get very far. I tried to odin flash a clean rom with a pit file and I get: Secure Check Fail : PIT:crying:
Click to expand...
Click to collapse
I don't remember exactly what was my scenerio about ODIN failure
It's been months since i went through the process
but vaguely i remember i changed the correct PIT file, took that from below drive link
https://drive.google.com/file/d/0BzyeAt2hy6XeLWdrTHNNQ0dDUlE/view
make sure u r using the correct file and latest odin .tar which is the link below
https://www.androidfilehost.com/?fid=457095661767125212
Another guy was also having this problem but i don't remember much.

---

Sam7777777 said:
I don't remember exactly what was my scenerio about ODIN failure
It's been months since i went through the process
but vaguely i remember i changed the correct PIT file, took that from below drive link
https://drive.google.com/file/d/0BzyeAt2hy6XeLWdrTHNNQ0dDUlE/view
make sure u r using the correct file and latest odin .tar which is the link below
https://www.androidfilehost.com/?fid=457095661767125212
Another guy was also having this problem but i don't remember much.
Click to expand...
Click to collapse
:good::laugh:You are the man!!:highfive: It was the PIT file. Even though the one I had said G900T it was not correct. Did you go through the adb stuff also?

---

fresco194 said:
:good::laugh:You are the man!!:highfive: It was the PIT file. Even though the one I had said G900T it was not correct. Did you go through the adb stuff also?
Click to expand...
Click to collapse
Yes, till ADB only, cuz my serial number was correct already, and i noticed my phone was back after that, as far as i remember

---

Sam7777777 said:
Yes, till ADB only, cuz my serial number was correct already, and i noticed my phone was back after that, as far as i remember
Click to expand...
Click to collapse
I think I'm going to give up. Thanks anyway. Really appreciated.

---

fresco194 said:
I think I'm going to give up. Thanks anyway. Really appreciated.
Click to expand...
Click to collapse
You are just one step away, if u hv time
make sure you have allowed adb to run as root (supersu app), check supersu app, if adb requested permisiion and thats falsly disallowed
Setup working ADB connection, test it
allow adb shell to run as root
run following commands one by one
adb devices
adb shell
su
when u type su and hit enter, it should ask you for supersu permission on ur phone interface
Grant the permission
Also
have Busybox installed in your device
Usb debugging (obviously)
that's coming in my mind right now
Good Luck, if you try

---

Sam7777777 said:
You are just one step away, if u hv time
make sure you have allowed adb to run as root (supersu app), check supersu app, if adb requested permisiion and thats falsly disallowed
Setup working ADB connection, test it
allow adb shell to run as root
run following commands one by one
adb devices
adb shell
su
when u type su and hit enter, it should ask you for supersu permission on ur phone interface
Grant the permission
Also
have Busybox installed in your device
Usb debugging (obviously)
that's coming in my mind right now
Good Luck, if you try
Click to expand...
Click to collapse
Success!!! My phone is back up and running fine. Had a little scare after I rebooted it was going into download mode and saying "could not do normal boot" but I just re-flashed recovery in odin and re flashed rom and everything is working with my IMEI and serial. Thanks again for your help.

---

fresco194 said:
Success!!! My phone is back up and running fine. Had a little scare after I rebooted it was going into download mode and saying "could not do normal boot" but I just re-flashed recovery in odin and re flashed rom and everything is working with my IMEI and serial. Thanks again for your help.
Click to expand...
Click to collapse
Good to hear this
:victory:
Service Mode recovered too?

---

Sam7777777 said:
Good to hear this
:victory:
Service Mode recovered too?
Click to expand...
Click to collapse
It says DIAG CONFIG on the first line and not supported on second line.

---

fresco194 said:
It says DIAG CONFIG on the first line and not supported on second line.
Click to expand...
Click to collapse
As expected
but that's okey as long as phone's core functionality is working
Anyways
Have Fun !

---

Sam7777777 said:
As expected
but that's okey as long as phone's core functionality is working
Anyways
Have Fun !
Click to expand...
Click to collapse
Agreed. Thanks.

---

bootloop- softbrick- battery might be bad too, had that happen- replaced battery bootloop stopped.