Database Develop

Bricked Galaxy tab 8.9?

Hello,
I do have the awful feeling that it may be bricked for good.
I don't have the specifics on how it came to be this way, but I hope you may help.
The only thing I'm getting on boot is the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
As you can imagine, there are no backups in kies.
If I try to boot into recovery all I see is an Android coming out of a box and the legend "Downloading".
I have tried to use oding v1.85 and it kind of sees the unit, the com port is recognized but nothing else.
Is there anything I can do to restore the OS on this tablet?
Any help is more than welcome.
Cheers.

What specific device do you have and what happens when you try Odin?

jd1639 said:
What specific device do you have and what happens when you try Odin?
Click to expand...
Click to collapse
Hi JD,
The tablet is specifically a P7300, according to the changelog of Odin the v1.85 should be the correct one for it but I have found that with v1.83 I can see something.
I can see on the tablet screen: "Odin Download Mode \ (Protocol v3)"
Thanks,
Max Leön

maxleonca said:
Hi JD,
The tablet is specifically a P7300, according to the changelog of Odin the v1.85 should be the correct one for it but I have found that with v1.83 I can see something.
I can see on the tablet screen: "Odin Download Mode \ (Protocol v3)"
Thanks,
Max Leön
Click to expand...
Click to collapse
Go to sammobile.com for the firmware for your device. You have to register but it's free. You'll download a zip file. Use 7-zip to extract the .tar.md5 file from it. Use that file in odin, PDA. Only have auto-reset checked.

away sinclso
jd1639 said:
Go to sammobile.com for the firmware for your device. You have to register but it's free. You'll download a zip file. Use 7-zip to extract the .tar.md5 file from it. Use that file in odin, PDA. Only have auto-reset checked.
Click to expand...
Click to collapse
Hi again,
I did what you said and got the firmware for the p7300, using Oding with just the Auto-Reboot checked and setting the upload for PDA with the tar.md5 file, this is the output on Oding:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7300UBLP5_P7300ZTALP3_P7300UBLP4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
Any ideas?
Cheers

Never mind, after 3 attempts the process ran successfully and seems that I have the tablet back.
Thank you very much for your help.

That's weird. It looks like odin never completed. I'd try it again. It should take about 5 plus minutes.
Your using Odin 1.83? I'd try 1.85. There also a 3.07.
---------- Post added at 03:39 PM ---------- Previous post was at 03:31 PM ----------
maxleonca said:
Never mind, after 3 attempts the process ran successfully and seems that I have the tablet back.
Thank you very much for your help.
Click to expand...
Click to collapse
Sounds great, glad it worked.

[Q] Help! phone got bricked!

Dear XDA geniuses, i could really need your help!
for the last month my battery started to run out pretty fast. Couple of days ago i noticed a weird thing, the screen started to flicker, and the phone disconnected itself from the cellular network. And then the worst has happened- the phone just shuts down itself and ever since i cant turn it on.
The only thing i can do is go into download mode, so i switched batteries and tried to install a stock firmware from sammobile with odin.
at first odin failed and told me that there is no PIT partition, i pressed reset and tried again from a different USB and then it told me "operation failed" without any reason. I tried it again and again with different version of odin, different firmware, different cable and every time the same thing- first no PIT partition and then just fail..
Please Help!

GuyTa said:
Dear XDA geniuses, i could really need your help!
for the last month my battery started to run out pretty fast. Couple of days ago i noticed a weird thing, the screen started to flicker, and the phone disconnected itself from the cellular network. And then the worst has happened- the phone just shuts down itself and ever since i cant turn it on.
The only thing i can do is go into download mode, so i switched batteries and tried to install a stock firmware from sammobile with odin.
at first odin failed and told me that there is no PIT partition, i pressed reset and tried again from a different USB and then it told me "operation failed" without any reason. I tried it again and again with different version of odin, different firmware, different cable and every time the same thing- first no PIT partition and then just fail..
Please Help!
Click to expand...
Click to collapse
You probably need to repartition your phone using a PIT file. It is very risky though so do so at your own risk.

ArkThompson said:
You probably need to repartition your phone using a PIT file. It is very risky though so do so at your own risk.
Click to expand...
Click to collapse
do you have a good guide for it? and where i can get a good .PIT file for I9305?

GuyTa said:
do you have a good guide for it? and where i can get a good .PIT file for I9305?
Click to expand...
Click to collapse
I don't think there are any guides for how to do it on the i9305. This guide is potentially applicable (just use i9305 files instead of Galaxy Duos ones) http://forum.xda-developers.com/showthread.php?t=2659635 but like I said, do so at your own risk.
This is the only PIT file I've been able to find for the i9305 http://forum.xda-developers.com/gal...fo-i9305-pit-file-flash-analysis-pit-t1950591 but I've never used it so I don't know if it works, especially on newer Android versions.

ArkThompson said:
I don't think there are any guides for how to do it on the i9305. This guide is potentially applicable (just use i9305 files instead of Galaxy Duos ones) http://forum.xda-developers.com/showthread.php?t=2659635 but like I said, do so at your own risk.
This is the only PIT file I've been able to find for the i9305 http://forum.xda-developers.com/gal...fo-i9305-pit-file-flash-analysis-pit-t1950591 but I've never used it so I don't know if it works, especially on newer Android versions.
Click to expand...
Click to collapse
Thanks for the help!
Before i try these one, does anyone has a PIT file that you tried on your I9305??

ArkThompson said:
I don't think there are any guides for how to do it on the i9305. This guide is potentially applicable (just use i9305 files instead of Galaxy Duos ones) http://forum.xda-developers.com/showthread.php?t=2659635 but like I said, do so at your own risk.
This is the only PIT file I've been able to find for the i9305 http://forum.xda-developers.com/gal...fo-i9305-pit-file-flash-analysis-pit-t1950591 but I've never used it so I don't know if it works, especially on newer Android versions.
Click to expand...
Click to collapse
Did what you offered, but odin got stuck in the "Get PIT for mapping.."
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXUFNJ1_I9305XEOFNJ1_I9305XXUFNJ1_HOME.tar.md5 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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
Click to expand...
Click to collapse
Tried to reboot my phone and PC, but still stuck. do you have an idea why?

GuyTa said:
Did what you offered, but odin got stuck in the "Get PIT for mapping.."
Tried to reboot my phone and PC, but still stuck. do you have an idea why?
Click to expand...
Click to collapse
Not sure, you could try a different Odin version maybe. I looked around online a bit and some people had luck trying it with a different cable. If that doesn't work then the PIT is probably no good. I could try dumping mine if you want but it will be the first time I've done it so don't blame me if it bricks your phone.

ArkThompson said:
Not sure, you could try a different Odin version maybe. I looked around online a bit and some people had luck trying it with a different cable. If that doesn't work then the PIT is probably no good. I could try dumping mine if you want but it will be the first time I've done it so don't blame me if it bricks your phone.
Click to expand...
Click to collapse
Tried different odin version, it doesn't stuck but says "re-partition operation failed". Tried different cable, didn't help.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXUFNJ1_I9305XEOFNJ1_I9305XXUFNJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
looks like i don't have choice but to try you'r PIT file. If that won't work I'm thinking of taking it to a lab, you think they'll be able to fix it?
Thanks A lot for the help!!

GuyTa said:
Tried different odin version, it doesn't stuck but says "re-partition operation failed". Tried different cable, didn't help.
looks like i don't have choice but to try you'r PIT file. If that won't work I'm thinking of taking it to a lab, you think they'll be able to fix it?
Thanks A lot for the help!!
Click to expand...
Click to collapse
I'm starting to think that your eMMC chip is dead so it's possible that your motherboard will need replacing. Try flashing a custom recovery in Odin and seeing if you get any error messages when you boot into it. I can make the file later tonight but it's probably better to try some other things first.

ArkThompson said:
I'm starting to think that your eMMC chip is dead so it's possible that your motherboard will need replacing. Try flashing a custom recovery in Odin and seeing if you get any error messages when you boot into it. I can make the file later tonight but it's probably better to try some other things first.
Click to expand...
Click to collapse
Didn't change much. Tried to flash only the recovery and got "No PIT partition" so i added the PIT file and again "Re-Partition operation failed"
You think its a lost cause? HW problem?

GuyTa said:
Didn't change much. Tried to flash only the recovery and got "No PIT partition" so i added the PIT file and again "Re-Partition operation failed"
You think its a lost cause? HW problem?
Click to expand...
Click to collapse
It's sounding like it might be. I made the file but I haven't tested it or anything. I'll pm you the password for the .zip since I don't want random people flashing it.

ArkThompson said:
It's sounding like it might be. I made the file but I haven't tested it or anything. I'll pm you the password for the .zip since I don't want random people flashing it.
Click to expand...
Click to collapse
Thank you very much for your help but it still doesn't work.. guess its toasted..:crying:

GuyTa said:
Thank you very much for your help but it still doesn't work.. guess its toasted..:crying:
Click to expand...
Click to collapse
That sucks, it sounds like it might have been sudden death syndrome or something because of the screen flickering. The last thing you could try is ticking nand erase all as well but that could potentially completely hard brick the phone because if it still fails to write after wiping you could lose your bootloader.
---------- Post added at 12:14 AM ---------- Previous post was at 12:04 AM ----------
GuyTa said:
Thank you very much for your help but it still doesn't work.. guess its toasted..:crying:
Click to expand...
Click to collapse
I just found this thread http://forum.xda-developers.com/galaxy-s3/help/sudden-death-i9300-t2786220 . You could try doing what he did and put a custom recovery instead of a stock ROM in PDA when using the PIT file but I doubt that it would work.

ArkThompson said:
I just found this thread http://forum.xda-developers.com/galaxy-s3/help/sudden-death-i9300-t2786220 . You could try doing what he did and put a custom recovery instead of a stock ROM in PDA when using the PIT file but I doubt that it would work.
Click to expand...
Click to collapse
I tried it with the last PIT file, still didn't work..

unable to reflash philz

I am currently rooted on stock rom with CF Auto Root and I am wanting to put Cyanogenmod on to my Note 4. I have tried to flash with odin Philz Touch but everytime I try to it fails. Am I needing to unroot my phone first then try flashing Philz to my phone? Or is there something I am doing wrong.

yamabushi336 said:
I am currently rooted on stock rom with CF Auto Root and I am wanting to put Cyanogenmod on to my Note 4. I have tried to flash with odin Philz Touch but everytime I try to it fails. Am I needing to unroot my phone first then try flashing Philz to my phone? Or is there something I am doing wrong.
Click to expand...
Click to collapse
Best bet is ask in recovery thread. Most of us are using twrp.
BAD ASS NOTE 4 + BAD ASS GEAR S

yamabushi336 said:
I am currently rooted on stock rom with CF Auto Root and I am wanting to put Cyanogenmod on to my Note 4. I have tried to flash with odin Philz Touch but everytime I try to it fails. Am I needing to unroot my phone first then try flashing Philz to my phone? Or is there something I am doing wrong.
Click to expand...
Click to collapse
I have also tried using TWRP and still get a failed message on odin I will creat a new thread there then.

If u can't get twrp to work ur either using the wrong Odin or something else.
BAD ASS NOTE 4 + BAD ASS GEAR S

update
I have been messing around with everything for the past couple of days and the only thing I can get to flash via odin is the stock rom and nothing else. I have tried multiple versions of odin from version 1.x-3.x and they are still failing when I try to flash TWRP Philz or even CF Auto root. I am still not sure why I am not able to flash any of those.

yamabushi336 said:
I have been messing around with everything for the past couple of days and the only thing I can get to flash via odin is the stock rom and nothing else. I have tried multiple versions of odin from version 1.x-3.x and they are still failing when I try to flash TWRP Philz or even CF Auto root. I am still not sure why I am not able to flash any of those.
Click to expand...
Click to collapse
Since u having all these issues. U need to delete everything and start fresh. Fresh downloads off all. New Odin new drivers new Roms new everything.
BAD ASS NOTE 4 + BAD ASS GEAR S

Odin to stock. Factory reset. Follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2903733
Flash any rom you want.
I'll walk you through it if need be.

10-K said:
Odin to stock. Factory reset. Follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2903733
Flash any rom you want.
I'll walk you through it if need be.
Click to expand...
Click to collapse
I just did a reinstall of stock and a factory reset like you said and i am still getting errors with odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltetmo-trltetmo-smn910t.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

yamabushi336 said:
I just did a reinstall of stock and a factory reset like you said and i am still getting errors with odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltetmo-trltetmo-smn910t.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What Odin are u using
BAD ASS NOTE 4 + BAD ASS GEAR S

The one I've been using is version 1.85 since that's the only one that works when I flash stock

yamabushi336 said:
The one I've been using is version 1.85 since that's the only one that works when I flash stock
Click to expand...
Click to collapse
Should be 3.07 that might be one of ur issues. When u downloaded the zip to root using cf auto root it came with it. Start over with fresh downloads. Delete all ur other stuff
BAD ASS NOTE 4 + BAD ASS GEAR S

BACARDILIMON said:
Should be 3.07 that might be one of ur issues. When u downloaded the zip to root using cf auto root it came with it. Start over with fresh downloads. Delete all ur other stuff
BAD ASS NOTE 4 + BAD ASS GEAR S
Click to expand...
Click to collapse
I have just deleted all instances of odin and of CF auto root I have downloaded previously and I am still getting the same error message as in my previous post with odin 3.07

yamabushi336 said:
I have just deleted all instances of odin and of CF auto root I have downloaded previously and I am still getting the same error message as in my previous post with odin 3.07
Click to expand...
Click to collapse
So u redownloaded everything all the files found in tekhd thread and u still getting error
BAD ASS NOTE 4 + BAD ASS GEAR S
---------- Post added at 08:09 PM ---------- Previous post was at 08:08 PM ----------
When I say start fresh I mean all of it. Fresh ROM fresh drivers fresh everything.
BAD ASS NOTE 4 + BAD ASS GEAR S

BACARDILIMON said:
So u redownloaded everything all the files found in tekhd thread and u still getting error
BAD ASS NOTE 4 + BAD ASS GEAR S
Click to expand...
Click to collapse
I redownloaded the zip file that contains odin and CF and yes it did still gave me the FAIL! (AUTH) error.

How to Root the Samsung Galaxy Note 4: http://youtu.be/mdkLxNNLGiA
BAD ASS NOTE 4 + BAD ASS GEAR S
---------- Post added at 08:17 PM ---------- Previous post was at 08:17 PM ----------
Step by step video
BAD ASS NOTE 4 + BAD ASS GEAR S

BACARDILIMON said:
How to Root the Samsung Galaxy Note 4: http://youtu.be/mdkLxNNLGiA
BAD ASS NOTE 4 + BAD ASS GEAR S
---------- Post added at 08:17 PM ---------- Previous post was at 08:17 PM ----------
Step by step video
BAD ASS NOTE 4 + BAD ASS GEAR S
Click to expand...
Click to collapse
Still giving me the FAIL! AUTH error even with the files he as provided in his video

Then it is ur phone
BAD ASS NOTE 4 + BAD ASS GEAR S
---------- Post added at 08:58 PM ---------- Previous post was at 08:58 PM ----------
Sorry man something went bad someplace
BAD ASS NOTE 4 + BAD ASS GEAR S

Just use flashify to flash recovery and untick reactivation lock in settings
Sent from my SM-N910C using XDA Free mobile app

duvalbmarley said:
Just use flashify to flash recovery and untick reactivation lock in settings
Sent from my SM-N910C using XDA Free mobile app
Click to expand...
Click to collapse
I would but I am currently not rooted anymore been trying to restore root on my phone but it has been a no go.

[Q] PingPong Root -> TWRP -> Brick! :( Help!

TL;DR DON'T try to install a custom recovery yet. As of 5/12/15, the bootloader prevents you from doing that. At the moment, you can only root, which you can do through Ping Pong Root (google it). And if for some reason you goofed up and installed a custom recovery, go to AT&T and just say the bare minimum, that you "tried to update your phone" and it keeps telling you "this error message." If they prod more, you can say you "updated the firmware," but obviously withhold the words "flash," "recovery," etc.
So I greatly REGRET that I installed a custom recovery. I'd appreciate any help. I'm bricked in the "System software not authorized by AT&T has been found on your phone." Here's what I did leading up to it:
1. Installed Ping Pong Root party_beta5.7z. Unzipped, installed, rooted.
2. Root Checker verified root!
3. Determined my my phone is: G920AUCU1AOCE.
4. Downloaded TWRP 2.8.6.2 through Flashify for Samsung Galaxy S6 (zeroflte).
5. Flashed it through Flashify
6. Bricked (light blue screen with text) and bootloop.
Help!
EDIT: Steps I've taken so far:
1. Download Odin Tar files from http://forum.xda-developers.com/att-...g920a-t3103835
2. Connected phone to PC in download mode after installing USB drivers and ODIN 3.10.6
3. Put all 4 tar files into their corresponding spots.
EDIT2: No luck. Tried multiple ports, multiple computers, and used the official cable. Also Ran as administrator. After making sure my device is recognized as COM3 (blue box), and the tar files are plugged in, I keep getting the below error:
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT3: Played dumb, took it to at&t store with a tech support center, and they re-flashed a clean install for me. Whew.

I don't think u can use custom recoveries yet buddy..

Yeah, I goofed bigtime. I'm really regretting it.

It's telling me this:
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Let it be known root does not equel unlocked bootloader. I'd of wait or am for something like safestra to make it's way over.

aznkenshin said:
I'd appreciate any help. I'm bricked in the "System software not authorized by AT&T has been found on your phone." Here's what I did leading up to it:
1. Installed Ping Pong Root party_beta5.7z. Unzipped, installed, rooted.
2. Root Checker verified root!
3. Determined my my phone is: G920AUCU1AOCE.
4. Downloaded TWRP 2.8.6.2 through Flashify for Samsung Galaxy S6 (zeroflte).
5. Flashed it through Flashify
6. Bricked (light blue screen with text) and bootloop.
Help!
EDIT: Steps I've taken so far:
1. Download Odin Tar files from http://forum.xda-developers.com/att-...g920a-t3103835
2. Connected phone to PC in download mode after installing USB drivers and ODIN 3.10.6
3. Put Firmware into AP.
Praying this will work...
EDIT2: No luck. It tells me "Can't open the serial(COM) port." I'm thinking it's the drivers fault? Looking into it...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2711451
download odin 3.10.6 and just use all the tar files....MINE IS FINALLY ALIVE

plaxy+ said:
Let it be known root does not equel unlocked bootloader. I'd of wait or am for something like safestra to make it's way over.
Click to expand...
Click to collapse
So in the meantime, what should I do to at least have an operable phone? (

skylinegtr116 said:
http://forum.xda-developers.com/showthread.php?t=2711451
download odin 3.10.6 and just use all the tar files....MINE IS FINALLY ALIVE
Click to expand...
Click to collapse
OH! I was only using the "AP_****" files. I should plug in the CSC, CP, and BL too???????

aznkenshin said:
oh! I was only using the "ap_****" files. I should plug in the csc, cp, and bl too???????
Click to expand...
Click to collapse
yes all the files

skylinegtr116 said:
yes all the files
Click to expand...
Click to collapse
No luck
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_G920AUCU1AOCE_CL4351102_QB4488924_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_G920AUCU1AOCE_CL4351102_QB4488924_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_G920AUCU1AOCE_CL4351102_QB4488924_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_G920AATT1AOCE_CL4351102_QB4488924_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<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> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

The link above is broken, where can I get these files?
PS: Why do they provide a custom recovery if it straight "bricks" your phone? How is that even considered a working release and why don't they (TWRP) post a damn warning about it?

plaxy+ said:
Let it be known root does not equel unlocked bootloader.
Click to expand...
Click to collapse
Just joined last month, this was their third post currently, and knew this :good:
OP joined late 2011 and thought that just by gaining root, we could install custom recoveries on a still locked bootloader...........
LEARN FROM THIS, people! Don't want to go through this? Follow instructions!
That being said, from what I know of soft bricks, you are doing the right steps to fix it, I just don't have any experience with them to be able to tell you what you're doing wrong. People who have unlocked bootloader phones and installed custom recoveries, tripping KNOX, were able to flash back to stock and get KNOX back to 0x0, but again, they have the unlocked bootloader to be able to do that.... don't know what else to tell you other than to bring it to an ATT service center, play dumb, and see if they'll swap you into a new one
hayateyoshida said:
The link above is broken, where can I get these files?
PS: Why do they provide a custom recovery if it straight "bricks" your phone? How is that even considered a working release and why don't they (TWRP) post a damn warning about it?
Click to expand...
Click to collapse
They do post a warning about it - they post what phones this IS for, and our phone is NOT listed! People, please learn how to read if you're going to screw around with your phones! You can't just say "I have an S6 Edge" and think they're all the same! TWRP clearly states the following two devices have recoveries available:
Samsung Galaxy S6 (zeroflte)
Samsung Galaxy S6 (Sprint) (zerofltespr)
Do you see zeroflteatt on that list? Do you think zeroflte = zeroflteatt? If you don't know what model phone you have and flash away, you're gonna have a bad day......

aznkenshin said:
So I greatly REGRET that I installed a custom recovery. I'd appreciate any help. I'm bricked in the "System software not authorized by AT&T has been found on your phone." Here's what I did leading up to it:
1. Installed Ping Pong Root party_beta5.7z. Unzipped, installed, rooted.
2. Root Checker verified root!
)
Click to expand...
Click to collapse
what??
ATT galaxy s6 has root ?

Have you tried recovery through smart switch
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app

netnerd said:
what??
ATT galaxy s6 has root ?
Click to expand...
Click to collapse
yep. pingpong root

LeKtRiCzzz said:
Have you tried recovery through smart switch
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Click to expand...
Click to collapse
Yes, after going to update and software emergency setup, I plugged in Model and Serial number on the sticker of my phone, and it auto-closes.
Sent from my GT-I9505G using XDA Free mobile app

Agree 500%
KryptosXLayer2 said:
Just joined last month, this was their third post currently, and knew this :good:
OP joined late 2011 and thought that just by gaining root, we could install custom recoveries on a still locked bootloader...........
LEARN FROM THIS, people! Don't want to go through this? Follow instructions!
That being said, from what I know of soft bricks, you are doing the right steps to fix it, I just don't have any experience with them to be able to tell you what you're doing wrong. People who have unlocked bootloader phones and installed custom recoveries, tripping KNOX, were able to flash back to stock and get KNOX back to 0x0, but again, they have the unlocked bootloader to be able to do that.... don't know what else to tell you other than to bring it to an ATT service center, play dumb, and see if they'll swap you into a new one
They do post a warning about it - they post what phones this IS for, and our phone is NOT listed! People, please learn how to read if you're going to screw around with your phones! You can't just say "I have an S6 Edge" and think they're all the same! TWRP clearly states the following two devices have recoveries available:
Samsung Galaxy S6 (zeroflte)
Samsung Galaxy S6 (Sprint) (zerofltespr)
Do you see zeroflteatt on that list? Do you think zeroflte = zeroflteatt? If you don't know what model phone you have and flash away, you're gonna have a bad day......
Click to expand...
Click to collapse
---------- Post added at 11:25 AM ---------- Previous post was at 11:24 AM ----------
Smart Switch does NOT work in the AT&T version of the S6.
LeKtRiCzzz said:
Have you tried recovery through smart switch
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Click to expand...
Click to collapse

aznkenshin said:
EDIT3: Played dumb, took it to at&t store with a tech support center, and they re-flashed a clean install for me. Whew.
Click to expand...
Click to collapse
Great, I have just booked an appointment. But buddy, is it possible for you to upload Odin Tar?
Thanks!

nagnrik said:
Great, I have just booked an appointment. But buddy, is it possible for you to upload Odin Tar?
Thanks!
Click to expand...
Click to collapse
Read my OP

aznkenshin said:
Read my OP
Click to expand...
Click to collapse
ATT re-flashed the firmware, it is fine now. Thanks!

Help! Phone bricked, Odin will not see S6

I have a Tmobile S6 and not sure wife clicked to update super user and now phone will not go past tmobile splash screen. I now have the phone in download mode and Odin 3.09 or 3.11 will not see it. I haev tried different ports, uninstalling and reinstalling Kies and samsung drivers and different usb ports. also tried a win 7 pc since this one is win 10.
Odin will never see com port. Any ideas?

I was finally able to get it to see the phone but then go this message
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/007> 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/007> Odin engine v(ID:3.1101)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Anyone?

Did u get it figured out?
Sent from my SM-G920T using XDA-Developers mobile app

No I did not, I am still fighting it. I cannot get it write the rom with Odin. I really need some help.

I am not at home so cannot verify which version of Odin I use. Have you tried flashing the EPF1 baseband version tar file or which file are you trying to flash in Odin?
Sent from my SM-G920T using XDA-Developers mobile app

Have you tried smart switch?

the file is G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar I cannot find the link I downloaded from , sorry

MukDroid said:
I have a Tmobile S6 and not sure wife clicked to update super user and now phone will not go past tmobile splash screen. I now have the phone in download mode and Odin 3.09 or 3.11 will not see it. I haev tried different ports, uninstalling and reinstalling Kies and samsung drivers and different usb ports. also tried a win 7 pc since this one is win 10.
Odin will never see com port. Any ideas?
Click to expand...
Click to collapse
If you have a Tmobile variant then I think u have downloaded the wrong file brother.
Go to page 1 of this post and download the zip, then extract it and flash the file via Odin.
http://forum.xda-developers.com/showthread.php?t=3408162
MukDroid said:
the file is G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar I cannot find the link I downloaded from , sorry
Click to expand...
Click to collapse
Sent from my SM-G920T using XDA-Developers mobile app
---------- Post added at 01:51 AM ---------- Previous post was at 01:40 AM ----------
I used Odin version 3.10.6
Sent from my SM-G920T using XDA-Developers mobile app

cwhiatt said:
If you have a Tmobile variant then I think u have downloaded the wrong file brother.
Go to page 1 of this post and download the zip, then extract it and flash the file via Odin.
http://forum.xda-developers.com/showthread.php?t=3408162
Sent from my SM-G920T using XDA-Developers mobile app
---------- Post added at 01:51 AM ---------- Previous post was at 01:40 AM ----------
I used Odin version 3.10.6
Sent from my SM-G920T using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you the phone is now up and running!! I am not sure how I managed to download the wrong files but you saved the day I really appreciate it!

MukDroid said:
Thank you the phone is now up and running!! I am not sure how I managed to download the wrong files but you saved the day I really appreciate it!
Click to expand...
Click to collapse
It sounds like you may have been attempting to flash very outdated firmware. If you are not currently on a bootloader that allows a downgrade, you will not be able to flash older firmware. Only same or newer.
If you are at all unsure what version is correct for your phone, I highly suggest you avoid using Odin to make modifications. You have the potential to truly brick your phone.
On that note: your phone was not bricked, and Odin did see your device. Bricked means unrecoverable, and Odin will not flash without a valid target.