Hi guys I just bought a SGH-I747 AT&T and the issue with it is it goes into Download mode just fine, works with Odin 3.7 loads a stock rom and then it sais reset but the phone doesn't reset just goes to black screen and then Odin sais Pass. I press the power button and Samsung appers and vibrates and goes back to black. When I try Recovery mode it show the blue writing on the left upper and the Samsung and then it goes to black screen. I put two different stock roms and same story. Kies won't recognize it and I installed recovery-clockwork-touch-6.0.4.3-d2att.tar to try to get into recovery mode and of course no luck. Don't know the history on this, so if anyone could help I would really appreciate it. Thanks in advance.
gica69 said:
Hi guys I just bought a SGH-I747 AT&T and the issue with it is it goes into Download mode just fine, works with Odin 3.7 loads a stock rom and then it sais reset but the phone doesn't reset just goes to black screen and then Odin sais Pass. I press the power button and Samsung appers and vibrates and goes back to black. When I try Recovery mode it show the blue writing on the left upper and the Samsung and then it goes to black screen. I put two different stock roms and same story. Kies won't recognize it and I installed recovery-clockwork-touch-6.0.4.3-d2att.tar to try to get into recovery mode and of course no luck. Don't know the history on this, so if anyone could help I would really appreciate it. Thanks in advance.
Click to expand...
Click to collapse
I found out that the phone had 4.1.1 on it and the guy tried to flash 4.2.2 and upon doing the odin mode flashing odin gave Firmware upgrade encountered an issue Please select recovery mode in Kies & try again So these are just some helpful facts for anyone who has gone through it. Thanks in advance for any help
gica69 said:
I found out that the phone had 4.11 on it and the guy tried to flash 4.22 and upon doing the odin mode flashing odin gave Firmware upgrade encountered an issue Please select recovery mode in Kies & try again So these are just some helpful facts for anyone who has gone through it. Thanks in advance for any help
Click to expand...
Click to collapse
What firmware were you trying to flash via Odin and are you sure the seller didn't previously flash (or try to flash) the 4.3 on it? If it wasn't higher than 4.3, then you may try recovery via Kies as follows ....
Install and launch Samsung Kies on your PC (not Kies 3). Open the Tools menu and select Firmware Upgrade and Initialization
Do not connect your phone to your PC yet. Remove the battery cover and record device info written in the battery compartment
In Kies, enter your phone model (SGH-I747)
Enter the phone serial number and click OK to all the security questions. Follow all the instructions on Kies
Connect the phone when prompted and follow the rest of the instructions
Wait for firmware upgrade to complete
Good luck!
If this doesn't work, then you may try flashing the 4.1.1 stock image via Odin. Look for the correct stock image via the following thread ...
http://forum.xda-developers.com/showthread.php?t=1739426
The one you want for Samsung Galaxy S3 AT&T (4.1.1) is I747UCDLK3
PLEASE don't try any of the above if you were already on the 4.3 bootloader as things will only get worse.
Larry2999 said:
What firmware were you trying to flash via Odin and are you sure the seller didn't previously flash (or try to flash) the 4.3 on it? If it wasn't higher than 4.3, then you may try recovery via Kies as follows ....
Install and launch Samsung Kies on your PC (not Kies 3). Open the Tools menu and select Firmware Upgrade and Initialization
Do not connect your phone to your PC yet. Remove the battery cover and record device info written in the battery compartment
In Kies, enter your phone model (SGH-I747)
Enter the phone serial number and click OK to all the security questions. Follow all the instructions on Kies
Connect the phone when prompted and follow the rest of the instructions
Wait for firmware upgrade to complete
Good luck!
If this doesn't work, then you may try flashing the 4.1.1 stock image via Odin. Look for the correct stock image via the following thread ...
http://forum.xda-developers.com/showthread.php?t=1739426
The one you want for Samsung Galaxy S3 AT&T (4.1.1) is I747UCDLK3PLEASE don't try any of the above if you were already on the 4.3 bootloader as things will only get worse.
Click to expand...
Click to collapse
I have already tried the I747UCDLK3 not from the link you gave me though. I did notice that the one you mentioned is a rooted stock do you think I should still do it? The rom flashes fine no errors in Odin but when it sais RESET the phone turns off the download mode and vibrates once then goes black then later Odin sais Pass but I cannot start it it just bootloops and vibrates and it stays that way As far as the Kies procedure you gave me don't I have to be in recovery mode for it to see the phone? I cannot get to that mode just download mode. Let me know thanks for your help
gica69 said:
I have already tried the I747UCDLK3 not from the link you gave me though. I did notice that the one you mentioned is a rooted stock do you think I should still do it? The rom flashes fine no errors in Odin but when it sais RESET the phone turns off the download mode and vibrates once then goes black then later Odin sais Pass but I cannot start it it just bootloops and vibrates and it stays that way As far as the Kies procedure you gave me don't I have to be in recovery mode for it to see the phone? I cannot get to that mode just download mode. Let me know thanks for your help
Click to expand...
Click to collapse
If you were successful in flashing via Odin, I would have suggested you try doing a hard wipe/reset in recovery. However, you said you can't get to recovery mode so this may not work. What happens when you try booting into recovery mode?
For Kies, you wouldn't have to be in recovery mode for the firmware restore to happen. Normally, you would have to connect your (powered-on) phone to your PC for it to be recognized by Kies. However, as you can't power on, we are forcing Kies to prepare the specific required firmware for your device by manually entering in the device information. Thus, when the phone is connected, you have firmware ready to make it work.
It may also be that the firmware you downloaded and flashed via Odin may not be the correct or full version. There are so many sources of "stock" firmware these days that one can never be too sure. You may go to Sammobile.com to download the stock firmware and compare the size of the extracted file to the one you used. The odin flashable tar.md5 file should be about 1.1Gb in size.
Larry2999 said:
If you were successful in flashing via Odin, I would have suggested you try doing a hard wipe/reset in recovery. However, you said you can't get to recovery mode so this may not work. What happens when you try booting into recovery mode?
For Kies, you wouldn't have to be in recovery mode for the firmware restore to happen. Normally, you would have to connect your (powered-on) phone to your PC for it to be recognized by Kies. However, as you can't power on, we are forcing Kies to prepare the specific required firmware for your device by manually entering in the device information. Thus, when the phone is connected, you have firmware ready to make it work.
It may also be that the firmware you downloaded and flashed via Odin may not be the correct or full version. There are so many sources of "stock" firmware these days that one can never be too sure. You may go to Sammobile.com to download the stock firmware and compare the size of the extracted file to the one you used. The odin flashable tar.md5 file should be about 1.1Gb in size.
Click to expand...
Click to collapse
When I go in recovery it shows blue writing in left upper corner and Samsung logo and then black screen. I think I did use the Sammobile firmware at 1.1. My clock in download mode shows 6. I don't think that would affect it though. Could it be that Odin doesn't really write the firmware that's why flashing doesn't change anything? I don't think the jig would do anything maybe sending it for a jtag reflash is the trick.
I am lost for now. If you guys can think of anything new let me know and thanks again.
gica69 said:
When I go in recovery it shows blue writing in left upper corner and Samsung logo and then black screen. I think I did use the Sammobile firmware at 1.1. My clock in download mode shows 6. I don't think that would affect it though. Could it be that Odin doesn't really write the firmware that's why flashing doesn't change anything? I don't think the jig would do anything maybe sending it for a jtag reflash is the trick.
I am lost for now. If you guys can think of anything new let me know and thanks again.
Click to expand...
Click to collapse
You didn't mention if you tried the Kies option. I had a similar problem once when upgrade to 4.1.1 via Kies failed during the process and that was how I was able to recover. However, since you bought this from the secondary market, there is no way of telling for certain what the previous owner did wrong which would have been useful for recovery options.
One of the nice things about Odin is that you usually know the results immediately. If it says Pass, therefore, that's likely what it means. So Odin did flash something. But what did it flash? The counter you saw in download mode shows how many custom system installations there have been and 6 does show there has been some previous heavy tinkering with the phone. As you are still able to get into download modes, I would suggest you try flashing custom recovery (TWRP or CWM) via Odin. If this works and you are able to get into recovery mode, you may then try doing a hard wipe/reset via recovery. You may also try flashing the other (rooted) 4.1.1 file via Odin. At this stage, you really have nothing to lose in trying all options. I guess if you can get into recovery mode, the problem is almost solved as this leaves plenty of options.
A jig wouldn't help as that only gets you to download mode which, for now, you don't have a problem with. JTag should always be a last resort option only. Let me know how far it goes and good luck!
When flashing in Odin, did you check auto reboot? If you did, try flashing again but uncheck auto-reboot. When you see Reset in the status windows, disconnect the USB cable, pull out the battery, wait a few seconds until the phone completely shuts down, put back in the battery, get into recovery, wipe cache, do a factory reset, and reboot.
audit13 said:
When flashing in Odin, did you check auto reboot? If you did, try flashing again but uncheck auto-reboot. When you see Reset in the status windows, disconnect the USB cable, pull out the battery, wait a few seconds until the phone completely shuts down, put back in the battery, get into recovery, wipe cache, do a factory reset, and reboot.
Click to expand...
Click to collapse
This damn phone is starting to annoy me. I can still get into download mode but my phone gets usb device not recognized now. I have access to another I747 phone so my question is if I have access to the pit file from that phone can anything be done with the Debrick utility and a SD card with only download mode access? Thanks in advance.
Go into download and let us know what is shown on the screen.
audit13 said:
Go into download and let us know what is shown on the screen.
Click to expand...
Click to collapse
Odin Mode
Product Name: SGH-I747
Custom Binary Downloads: Yes (6 Counts)
Current Binary: Samsung Official
System Status: Official
Qualcomm Secure Boot: Enable
Green Android Icon Downloading...
Do not turn off target!!!
OK I plugged the USB in and out a few times and it allows to write every few tries. Back to my question can I do something in download mode if I have another i747 that I can copy stuff from? I also tried the suggestion to uncheck auto-reset pull the usb cable then the battery and try to go to recovery but it doesn't.Any suggestions are welcomed.
Try flashing a stock 4.1.1 rom from sammobile using Odin. Do not check auto reboot. When you see reset in the status window, disconnect the usb cable, pull the battery, replace the battery, boot into recovery, and wipe. I have done this numerous times on my i747m after flashing custom ROMs.
audit13 said:
Try flashing a stock 4.1.1 rom from sammobile using Odin. Do not check auto reboot. When you see reset in the status window, disconnect the usb cable, pull the battery, replace the battery, boot into recovery, and wipe. I have done this numerous times on my i747m after flashing custom ROMs.
Click to expand...
Click to collapse
I will try it again I think I already did but when I put the battery back and click the Vol+ Home Power I get the blue writing and then black screen. Should I wait like 10 min on the black screen or it should be quick. Thanks
Keep holding the buttons until the blue writing disappears and the green android appears with the green progress bar.
audit13 said:
Keep holding the buttons until the blue writing disappears and the green android appears with the green progress bar.
Click to expand...
Click to collapse
Is there an unbrick.img for 4.1.1 or 4.1.2 I noticed that there are files for 4.3 that allow you to go in recovery and erase stuff reinstall. Let me know cause I sure couldn't find it.
If u can get it into download mode u are never ever hard bricked my friend...take it from a guy who had to dust off his old galaxy sll last weekend & still can't get into d/l mode on my s3 after a week & even with a jig lol
Sent from my SGH-T989 using xda app-developers app
gica69 said:
Is there an unbrick.img for 4.1.1 or 4.1.2 I noticed that there are files for 4.3 that allow you to go in recovery and erase stuff reinstall. Let me know cause I sure couldn't find it.
Click to expand...
Click to collapse
The unbricking image only helps you get into download mode from where you can work your way up the rest of the food chain. As you can already get into download mode without difficulties, I doubt if that's what you really need. You are also able to flash ROMs successfully in download mode via Odin so you've gone far up on the food chain already. Perhaps you are not doing the recovery thing correctly enough. Like Audit said, you need to continue holding down the Volume Up and Menu buttons whilst releasing the Power button after you see the first flash until the recovery menu appears and then do a hard wipe/reset.
Perhaps you could also try flashing TWRP via Odin if CWM isn't working.
Larry2999 said:
The unbricking image only helps you get into download mode from where you can work your way up the rest of the food chain. As you can already get into download mode without difficulties, I doubt if that's what you really need. You are also able to flash ROMs successfully in download mode via Odin so you've gone far up on the food chain already. Perhaps you are not doing the recovery thing correctly enough. Like Audit said, you need to continue holding down the Volume Up and Menu buttons whilst releasing the Power button after you see the first flash until the recovery menu appears and then do a hard wipe/reset.
Perhaps you could also try flashing TWRP via Odin if CWM isn't working.
Click to expand...
Click to collapse
I already tried holding the Home and Volume up buttons for 4-5 minutes at which point my fingers got a bit tired. The reason I wanted the unbrick.img is that I am now having issues with the computer recognizing the device in usb. I plugged and unplugged so many times that it no longer works that way so I wanted to do it via sd card. The unbrick.img gets you in recovery mode and download mode as it allows you to boot from the card not from the internal HD. But the only ones I have seen are for the 4.3 issues. And I tried It but did not put my device in recovery.
gica69 said:
I already tried holding the Home and Volume up buttons for 4-5 minutes at which point my fingers got a bit tired. The reason I wanted the unbrick.img is that I am now having issues with the computer recognizing the device in usb. I plugged and unplugged so many times that it no longer works that way so I wanted to do it via sd card. The unbrick.img gets you in recovery mode and download mode as it allows you to boot from the card not from the internal HD. But the only ones I have seen are for the 4.3 issues. And I tried It but did not put my device in recovery.
Click to expand...
Click to collapse
I couldn't find one either although you may be able to create yours using the command line posted in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
You may also try using a jig to get back into download mode. Have you, however, considered exercising any buyer protection options you have on the phone since, it would appear, the guy sold you a lemon?
Hi,
I recently got a SM-T210 from a friend to repair. The description given was that their kids factory reset the unit and won't boot anymore. First the tablet had the death sleep issue which is a easy fix. But after that the tablet simply continues to show the "Samsung GALAXY TAB3" boot screen and never finishes booting.
As I'm known with Odin I simply downloaded the original firmware from sammobile for this tablet and took the firmware version for the Netherlands as that's where I live. There are 2 4.4.2 versions available and downloaded them both. When using Odin 3.09 and higher I simply cannot install the firmware, but on Odin 3.07 it can. Although it installs the tablet still fails to boot properly and hangs at the tab logo as described earlier.
With Odin 3.09 or higher I'm not even able to install the firmware as it says that there is no PIT file and NAND flash write fails. I've found 2 PIT files for this tablet on the forums and even with the use of these PIT files it still errors with the same issue and installation seems impossible with these versions of Odin.
I've also tried installing TWRP recovery but that won't boot either. When booting the tablet with volume key up it shows the Andriod icon with the spinnng "intestines" and alot of red error messages show not able to find /system and /data. My guess is that this is pretty bad, but that is what I want to fix with the stock firmwares and/or the PIT files (LT02.pit and T210(R).pit).
I'm currently out of ideas to revive this tablet and almost start thinking that it's completely dead, but before throwing it in the garbage bin I'm wondering if anybody here is able to help me further with this issue.
If you think you miss critical information, let me know so I can supply it!
Any help is greatly appreciated and thanked for!
langerak said:
Hi,
I recently got a SM-T210 from a friend to repair. The description given was that their kids factory reset the unit and won't boot anymore. First the tablet had the death sleep issue which is a easy fix. But after that the tablet simply continues to show the "Samsung GALAXY TAB3" boot screen and never finishes booting.
As I'm known with Odin I simply downloaded the original firmware from sammobile for this tablet and took the firmware version for the Netherlands as that's where I live. There are 2 4.4.2 versions available and downloaded them both. When using Odin 3.09 and higher I simply cannot install the firmware, but on Odin 3.07 it can. Although it installs the tablet still fails to boot properly and hangs at the tab logo as described earlier.
With Odin 3.09 or higher I'm not even able to install the firmware as it says that there is no PIT file and NAND flash write fails. I've found 2 PIT files for this tablet on the forums and even with the use of these PIT files it still errors with the same issue and installation seems impossible with these versions of Odin.
I've also tried installing TWRP recovery but that won't boot either. When booting the tablet with volume key up it shows the Andriod icon with the spinnng "intestines" and alot of red error messages show not able to find /system and /data. My guess is that this is pretty bad, but that is what I want to fix with the stock firmwares and/or the PIT files (LT02.pit and T210(R).pit).
I'm currently out of ideas to revive this tablet and almost start thinking that it's completely dead, but before throwing it in the garbage bin I'm wondering if anybody here is able to help me further with this issue.
If you think you miss critical information, let me know so I can supply it!
Any help is greatly appreciated and thanked for!
Click to expand...
Click to collapse
Nothing to loose so i should give it one more try with Kies. I remember that years ago i had a problem with a samsung phone and even Odin wasn't helping me. I did it with Kies then which fixed it. No garantuees though.
Droidphilev said:
Nothing to loose so i should give it one more try with Kies. I remember that years ago i had a problem with a samsung phone and even Odin wasn't helping me. I did it with Kies then which fixed it. No garantuees though.
Click to expand...
Click to collapse
Thanks, I've tried it with Kies but it won't even recognize the tablet. When I put it in Download mode and connect it to my computer the Kies welcome screen keeps switching every 2 seconds to the connecting screen, back to the welcome screen and keeps on going like that.
Any ideas left?
langerak said:
Thanks, I've tried it with Kies but it won't even recognize the tablet. When I put it in Download mode and connect it to my computer the Kies welcome screen keeps switching every 2 seconds to the connecting screen, back to the welcome screen and keeps on going like that.
Any ideas left?
Click to expand...
Click to collapse
Except for correct drivers etc etc not really, no.
I am facing same problem.
My Tab 3 (Sm-T210) has gone too.
Now I can't restore it.
I have downloaded Stock ROM from sammobile.org,
but I can't extract this properly.
It always says that "files are corrupted".
I am also going to be hopeless as like as you.
So my phone was acting up - random reboots, keystroke delays, apps closing, etc. after latest 5.1.1 OTA update...
Then I really f***'d **** up by using Odin to try to flash 4.4.4 on my phone with reactivation lock still on - it failed. Now I get the following display when I turn it on
"firmware upgrade encountered an issue. Please selected recovery mode in Kies & try again." Kies also does not recognize the S/N on my SM-N910A.
USB debugging was activated. I'm thinking that the reactivation lock is blocking the image to load and/or I flashed the wrong tar.md5 file, even though I tried 2 different ones. Sammobile incidentally does not have the ATT variant firmware files available, so I went to random websites with links to successful roots.
I can't boot the phone nor flash any firmware through Odin apparently, so while I can enter "download mode" and Odin does recognize the device, it "fails" instantly. My only options are boot to this error screen or enter download mode. Obviously, I can't "uncheck" the reactivation lock through the GUI, as it doesn't load.
Is there another way to at least get the phone running again? Any advice? Do I have a new paperweight?
Thanks,
J
the3y3guy said:
So my phone was acting up - random reboots, keystroke delays, apps closing, etc. after latest 5.1.1 OTA update...
Then I really f***'d **** up by using Odin to try to flash 4.4.4 on my phone with reactivation lock still on - it failed. Now I get the following display when I turn it on
"firmware upgrade encountered an issue. Please selected recovery mode in Kies & try again." Kies also does not recognize the S/N on my SM-N910A.
USB debugging was activated. I'm thinking that the reactivation lock is blocking the image to load and/or I flashed the wrong tar.md5 file, even though I tried 2 different ones. Sammobile incidentally does not have the ATT variant firmware files available, so I went to random websites with links to successful roots.
I can't boot the phone nor flash any firmware through Odin apparently, so while I can enter "download mode" and Odin does recognize the device, it "fails" instantly. My only options are boot to this error screen or enter download mode. Obviously, I can't "uncheck" the reactivation lock through the GUI, as it doesn't load.
Is there another way to at least get the phone running again? Any advice? Do I have a new paperweight?
Thanks,
J
Click to expand...
Click to collapse
Find good copy of 5.1.1 firmware and reflash
Sent from my SAMSUNG-SM-N930A using XDA Premium HD app
whooohooo!
norbarb said:
Find good copy of 5.1.1 firmware and reflash
Sent from my SAMSUNG-SM-N930A using XDA Premium HD app
Click to expand...
Click to collapse
It worked just flashing the proper 5.1.1 AP file only! Thanks, norbarb!
The cable was extremely finicky, not sure if it was a USB driver issue or what, but I literally had to limit all body movements to not disturb the transfer. A few times it failed because of intermittent signal loss.
url
the3y3guy said:
It worked just flashing the proper 5.1.1 AP file only! Thanks, norbarb!
The cable was extremely finicky, not sure if it was a USB driver issue or what, but I literally had to limit all body movements to not disturb the transfer. A few times it failed because of intermittent signal loss.
Click to expand...
Click to collapse
I can't post the URL, but I got the right firmware from " androidromupdate "
I have the same problem with my note 4. After flashing firmware 5.1.1 it resulted in a bootloop for 30 min getting very hot.
So I used factory settings / clear cash in the recovery menu that got me back to the first welcome chose language screen. But after setting up wifi etc. it still wants to know the Samsung account login wich doesn't seem to work. Resulting again in an frp lockup. Is there any way to get rid of this frp lock? Perhaps rooting the device or installing a custom firmware / rom?
Or even going back to stock rom 4?
I was on 6.0.1 MM and was trying to downgrade to 5.1.1 Lollipop. One tutorial told me to enable USB debugging, disable OEM unlock, and then flash TWRP through Odin. After doing this, my phone won't turn on or go into recovery mode. It will only flash the charging screen with red letters saying "custom binary blocked by FRP lock" and go into download mode. When I try to flash stock firmwares from SamMobile using Odin, I always get the FAIL message. I have tried every USB in my house and every port on my computer. I keep trying to download alternate 6.0.1 firmware off SamMobile, but the website is not downloading anything to my computer for some reason. Please help!
aparker56 said:
I was on 6.0.1 MM and was trying to downgrade to 5.1.1 Lollipop. One tutorial told me to enable USB debugging, disable OEM unlock, and then flash TWRP through Odin. After doing this, my phone won't turn on or go into recovery mode. It will only flash the charging screen with red letters saying "custom binary blocked by FRP lock" and go into download mode. When I try to flash stock firmwares from SamMobile using Odin, I always get the FAIL message. I have tried every USB in my house and every port on my computer. I keep trying to download alternate 6.0.1 firmware off SamMobile, but the website is not downloading anything to my computer for some reason. Please help!
Click to expand...
Click to collapse
You cannot downgrade from 6 to 5.11, Samsung has blocked that.
You can download the latest 6.01 TAR from here and flash via Odin: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
That should get you back working.
koop1955 said:
You cannot downgrade from 6 to 5.11, Samsung has blocked that.
You can download the latest 6.01 TAR from here and flash via Odin: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
That should get you back working.
Click to expand...
Click to collapse
I'm trying to download this and the page just keeps saying " waiting for www.androidfilehost.com...." but not doing anything. I'm using chrome and I don't have an ad-block extension installed. This seems to be the same problem with downloading off of SamMobile. Any advice?
aparker56 said:
I'm trying to download this and the page just keeps saying " waiting for www.androidfilehost.com...." but not doing anything. I'm using chrome and I don't have an ad-block extension installed. This seems to be the same problem with downloading off of SamMobile. Any advice?
Click to expand...
Click to collapse
I just downloaded and it worked fine. Android File Host will always be faster and I grab the TAR files off of SAMMOBILE and upload pretty much within 24 hours.
A couple of things to try:
1) You are trying to download to a computer, not to your phone, right?
2) If so, restart your PC. Simple and it often fixes things.
3) If you are on Windows, try using IE or Edge. I am a Chrome user as well, but you might have something going on with your browser.