Develop Bugs

SGH-I747 AT&T Softbricked Maybe Hard

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?

[Q] i747 Unbricked Problem

I used the debrick-SGH-I747U-CUEMJB3.img on my hard bricked (no signs of life except for red charging light when plugged into charger) At&T i747 that had the ota 4.3 update and was able to get into download mode ! from there I flashed from custom recovery menu with d2att_I747UCUEMJB_bootloader.zip rom and it try to boot but not complete. then I try to flash from custom recovery with boot_CWM_I747MVLUEMK5.zip and when it was done flashing it said succeeded so I hit reboot then after that my phone was dead again and the sdcard debrick imgae no longer works..........somebody can help me???

Silly thought, but does the red charging light even come on when the phone is powered off on a normally working S3? My spidey-sense tells me to check if the screen works at all.
What happens when you do a battery pull, then replace the battery and plug in to charge?

usuariocubano said:
I used the debrick-SGH-I747U-CUEMJB3.img on my hard bricked (no signs of life except for red charging light when plugged into charger) At&T i747 that had the ota 4.3 update and was able to get into download mode ! from there I flashed from custom recovery menu with d2att_I747UCUEMJB_bootloader.zip rom and it try to boot but not complete. then I try to flash from custom recovery with boot_CWM_I747MVLUEMK5.zip and when it was done flashing it said succeeded so I hit reboot then after that my phone was dead again and the sdcard debrick imgae no longer works..........somebody can help me???
Click to expand...
Click to collapse
You likely got the results you got by flashing the wrong bootloader. The second zip you flashed is a bootloader for the Canadian variant (i747M) so, unless your phone is the Canadian variant, you would have bricked a second time. The debrick image helps you get your phone into download and/or recovery mode from where you can work your way up the rest of the food chain to full firmware restore. I presume your phone is an AT&T i747? You would need to create a new debrick image and try the process again. This time, when you get into recovery mode, try flashing a complete stock image. If the debrick file works, it should enable your phone boot into system. If you can get into system, use the instructions in the following thread to download a stock restore file and to your phone and then reboot into recovery (still with the debrick card) to flash the stock restore zip.
http://forum.xda-developers.com/showthread.php?t=2658486
If the new debrick doesn't work, your phone may need a JTag fix.

mstrswrd06 said:
Silly thought, but does the red charging light even come on when the phone is powered off on a normally working S3? My spidey-sense tells me to check if the screen works at all.
What happens when you do a battery pull, then replace the battery and plug in to charge?
Click to expand...
Click to collapse
the phone only show the red led for only a few second, nothing more

Larry2999 said:
You likely got the results you got by flashing the wrong bootloader. The second zip you flashed is a bootloader for the Canadian variant (i747M) so, unless your phone is the Canadian variant, you would have bricked a second time. The debrick image helps you get your phone into download and/or recovery mode from where you can work your way up the rest of the food chain to full firmware restore. I presume your phone is an AT&T i747? You would need to create a new debrick image and try the process again. This time, when you get into recovery mode, try flashing a complete stock image. If the debrick file works, it should enable your phone boot into system. If you can get into system, use the instructions in the following thread to download a stock restore file and to your phone and then reboot into recovery (still with the debrick card) to flash the stock restore zip.
http://forum.xda-developers.com/showthread.php?t=2658486
If the new debrick doesn't work, your phone may need a JTag fix.
Click to expand...
Click to collapse
the first time i use the unbriked image on my sd for i747, but after i flashed the wrong bootloader the unbricked image don't wotk i use for i747 and for i747m and nothing

usuariocubano said:
the first time i use the unbriked image on my sd for i747, but after i flashed the wrong bootloader the unbricked image don't wotk i use for i747 and for i747m and nothing
Click to expand...
Click to collapse
Usually, the unbrick image won't help if your phone is bricked from flashing a bootloader meant for another model but only when you wrongly flash an older bootloader for the same model. Looks like it is a real hard brick and a JTag may now be required.

[Q] galaxy s3 I747 wont boot past Samsung Galaxy s3 Logo, Did i brick my phone???

I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!

baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app

baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.

KorGuy123 said:
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app
Click to expand...
Click to collapse
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
Larry2999 said:
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.
Click to expand...
Click to collapse
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!

baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
It's time to start reading. Before doing any flashing/modding, you should make sure you understand what you're doing and know the risks.
Now as for Odin, it's quite straight forward. Phone needs to be in download mode, you put the PDA file in Odin and flash (if it's a Odin one-click, just need to hit start). One thing is to not interrupt it! Especially if flashing bootloaders cause that will brick your phone. Also, don't downgrade bootloaders.
There are a few guides in the sticky, I suggest you take an hour or two reading them so things like that don't happen again (or that you know what to do if it does).
GL!

baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
Alright. If wipe/reset didn't work, you'll need to restore full stock 4.3 via custom recovery. Here's what we need to do....
1) Download the Odin flashable *.Tar file for custom recovery. I prefer TWRP because of the GUI so that's where I'm pointing you to ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore file for 4.3 from the thread below... If you are using TWRP, then the first link is the one you need
http://forum.xda-developers.com/showthread.php?t=2658486
3) Copy the stock restore zip file to a good quality (micro) SD card
4) I presume you have Odin already so you will use this to flash custom recovery to your phone. Run Odin.exe on your PC. If you are using Odin v.3.09 then you need the AP tab. For all other versions, use the PDA tab. Navigate to the custom recovery *.Tar file you downloaded earlier and place this in the PDA (or AP tab). Leave the default settings as is and do not check/uncheck any boxes other than the default settings.
5) Boot the phone to download mode via the 3-button combo (Volume Down/Home/Power). When you get to Odin (Download) mode, press volume up to continue. Connect the phone to your PC with a good quality micro USB cable. Wait until Odin has recognized the device then click on the Start button to start firmware installation (flashing). Wait for the flashing to end and the <Pass> message. Disconnect the phone from the PC and pull the battery to stop auto reboot.
6) Place the micro SD card with the stock restore zip in your phone. Replace the battery and boot to recovery mode. If you were successful with the firmware flashing above, it should boot you to custom recovery.
7) Select install from external card and navigate to the stock restore zip file. Select this file and swipe the screen to start firmware installation. Wait for installation to complete. Then clear your cache/dalvik and reboot to system.
This will hopefully do it.

P605 LTE model - recovery boot loop post-root. HELP!

EDIT: RESOLVED.
Stupidly, I was following this root guide on the 4G/LTE P605 device pulled FRESH OUT OF BOX (obviously not acknowledging it's stock firmware was 4.3, I went on to follow the guide for P605 on Android 4.4.2:
http://androidxda.com/root-samsung-galaxy-note-10-1-sm-p605.
After 2 attempts with ODIN flashingthe CF auto root and trying to power cycle (turn off and back on), even trying to get BACK INTO download mode seemed impossible. It was on a BOOT LOOP so to speak. There was only 1 solution I could find, (which I commented on below) for this problem coming up on screen:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Power off and back on, trying to get to download mode: Above info loads on screen...
SOLUTION:
As device couldn't physically be turned off - I waited for the battery to die overnight. Tried DL mode booting and on the 2nd attempt it worked. This allowed me to download stock ROM (AUSTRALIA 4.3) and flash. All back to normal. The only question I have now - and am COMPLETEL baffled that after a FULL year on the market, there doesn't seem to be 1 working method to ROOT STOCK FIRMWARE on P605 Andriod 4.3 boggles the mind...
If 4.4.2 isn't available in Australia and I don't wish to flash a foreign STOCK ROM, am I just stuck with non-root?
Pretty piss weak, if you ask me.
RoOSTA

roosta said:
HI guys,
Following this and for me, it's no good for me:
http://androidxda.com/root-samsung-galaxy-note-10-1-sm-p605.
Galaxy Note 10.1 2014 P605 (LTE 4G version). New out of box and fully charged.
I installed the latest Odin (basically all files from the above link/s), using genuine Samaung cables/drivers, Odin detects device, but when I try to install the auto-root file, it doesn't restart like it normally should. The (COM3) connection disappears, as if the USB cable was disconnected (but it wasn't)....and the device quickly restarts to the following intro screen. It stays there, even if I try booting back up into download mode, this comes up without fail VERY TIME and sits there:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Is shown in the top corner. Despite 20+ attempts at rebooting into download mode, this device has no idea what it's doing and can't boot into any other screen. Have i bricked this device or can I recover this somehow, some way?
Any help is appreciated.
Click to expand...
Click to collapse
Hi,
If you can boot in download mode try to flash a stock ROM with Odin.

Tilagoon said:
Hi,
If you can boot in download mode try to flash a stock ROM with Odin.
Click to expand...
Click to collapse
As I said, I can't get to download mode. The issue could be the attempted CF-Auto-Root flash on 4.3 instead of 4.4.2... but doesn't explain why the device won't turn off, or can't get into DL mode, does it? I did find a couple of threads on this problem, but their fix is "remove the battery and try again"
http://forum.xda-developers.com/showthread.php?t=2611635&page=16
http://forum.xda-developers.com/showthread.php?t=2666432
Pitty you can't do that with a Note...my best bet could be to wait for the battery to completely die - sadly I recharged it before first use, which was the root attempt!

hallo i have the same problem for samsung sm-p605
can you tell me..how to make my phone off and go back to the recovery mode... because that phone can't remove the battery...

arrdiey said:
can you tell me..how to make my phone off and go back to the recovery mode... because that phone can't remove the battery...
Click to expand...
Click to collapse
Best thing you can do? leave the device on and for battery level to reach 0%. When it turns off, tutn back on holding power+down vol key and it should boot into standard download mode. Thankfully, I am back to that point. I am going to download and attempt to flash original STOCK rom to this device...

PHEW. Dodged a bullet there. Knox counter tripped to 1, but stock ROM installed and working as expected. Can i root the device on 4.3 or does it need to be on 4.4.2?
RoOSTA

'Support' seems to have died on this forum, or is it because no one browses the board after some months of the devices' release date?

Hey, just saw your thread, hopefully it's not to late
I recommend you to update to 4.4.2 and then root with towelroot. For me, the performance of 4.4.2 is muuuuuch better than 4.2
edit: If you dont know towelroot: https://towelroot.com/ Just click the Lambda, install and run the App and your tablet is rooted.
Good luck!

Maaario said:
Hey, just saw your thread, hopefully it's not to late
I recommend you to update to 4.4.2 and then root with towelroot. For me, the performance of 4.4.2 is muuuuuch better than 4.2
edit: If you dont know towelroot: https://towelroot.com/ Just click the Lambda, install and run the App and your tablet is rooted.
Good luck!
Click to expand...
Click to collapse
As stated, there is no Australian ROM for 4.2.2, I'd have to go for a foreign ROM which I don't really want to do. Why would Chainfire skip the Auto Root procedure for the OUT OF BOX Android OS?
RoOSTA

SG4 in 4.4.4 stock ROM is looping on grey battery icon.

So this happened about a month ago. The battery drained and when I left it charging I noticed that it was vibrating and showing the grey battery icon and this loops. I have the CMR Recovery v6.0.4.7 and can only access it when connected to the wall charger. I have left it a while on CMR while connected to the wall to see if it need charging but it just does the same thing when trying to boot. I have wiped cache, dalvik cache and selected the "Fix root" option before rebooting and nothing. I have not tried to flash a ROM in fear of bricking it. I made it as far as the "Upgrading Apps" window before fully booting but it turned off. I searched a bit and some people blame a faulty USB Port and/or power switch. I have no problem in buying and replacing the USB port and the power switch, though I don't have soldering tools for the power switch. But since I don't know what the issue is exactly I haven't rushed to buy the USB port replacement. So, the question is: is it a software or hardware problem and can it be fixed? I hope this is a software issue so it can be easier to solve.

I suggest putting the phone into download mode and see if Odin recognises the phone. If it does, I would flash the latest stock rom.

audit13 said:
I suggest putting the phone into download mode and see if Odin recognises the phone. If it does, I would flash the latest stock rom.
Click to expand...
Click to collapse
Odin does recognize the phone on Download Mode. So, what you are saying is to flash the latest non-rooted ROM (OFW), correct? Like the tar files found in sites like SamMobile? That won't remove my root nor custom recovery, right? Kinda of a newb question even though I kinda know the answer, but I just want to make sure.

Flashing a stock ROM will always remove root and twrp.

audit13 said:
Flashing a stock ROM will always remove root and twrp.
Click to expand...
Click to collapse
Hi. So, I flashed the latest stock ROM that is available on SamMobile and it fails in Odin. Now when I plug the phone without going to Download Mode its says something about recovery mode in Kies and and a firmware upgrade issue. What is happening? Thank for your responses, btw.
What I downloaded was a zip titled "SGH-M919-TMB-M919UVUAMDL-1366964131" and inside is and tar.md5 file called "M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar". There on the same folder as Odin.

What error message was displayed in the Odin log?
Post the entire Odin log if possible. This will help to determine the issue.
You confirmed that the phone is an sgh-m919 in download mode?
Even though you turn on the phone and see the message"...firmware upgrade encountered an error...", Odin can still be usedto flash a stock ROM as if the phone was in download mode.
The MDL firmware is too old. Try flashing the latest ROM.