Develop Bugs

[Q] SGH-I317 Can't enter recovery mode

I have searched these forums and everywhere else I can find mentioning this problem online, but nothing has worked yet. I'm hoping someone here may be able to point me in the right direction.
I rooted my AT&T Galaxy Note 2 SGH-I317 a couple weeks ago and was messing around and stupidly tried upgrading to 4.3, and now I can't boot and can't enter recovery mode. NOTE: Download mode works just fine, either by manually holding Volume Down/Home/Power or by using a USB Jig, I just can't enter recovery mode by holding Volume Up/Home/Power
I am able to flash just fine with Odin (I have tried version 3.07 and 3.09), it says Pass every time but the darn phone still won't boot and won't let me into recovery mode so that I may clear the cache and get it to boot.
I have tried flashing back to the factory firmware, to which Odin says Pass but still no go on the boot.
I have also tried setting up an ADB connection in Windows 7 (so that I may get the phone into recovery mode without hardware buttons), but since my computer will only recognize the phone when it's in download mode (since I can't boot the phone so Windows 7 will see it like it normally would) ADB won't work.
I'm at my wits end here, does anyone have any clue how I may fix this problem? What's really frustrating is I just bought a Galaxy Gear Watch and about a week later messed up my phone
Thanks, and I appreciate any help you can give me.
EDIT: Forgot to mention something. When I turn the power to the phone on and don't enter download mode, it stays on the Samsung Galaxy Note II screen, and that's all that happens.
Also, this is exactly what my Download screen info says:
FACTORY MODE
PRODUCT NAME: SGH-I317
CUSTOM BINARY DOWNLOAD: Yes(6 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 1
RP SWREV: A2

Got the phone to finally boot up
I finally got my phone to at least boot up. Although, I still can't get into recovery mode.
I followed this post: http://forum.xda-developers.com/showthread.php?t=2596256 and downloaded this file
It boots, and is currently 4.1.2, however when I try to get to recovery mode, the graphics flicker and the screen goes blank for a couple mins then reboots to the OS.

geekinator said:
I finally got my phone to at least boot up. Although, I still can't get into recovery mode.
I followed this post: http://forum.xda-developers.com/showthread.php?t=2596256 and downloaded this file
It boots, and is currently 4.1.2, however when I try to get to recovery mode, the graphics flicker and the screen goes blank for a couple mins then reboots to the OS.
Click to expand...
Click to collapse
I had a similar issue moving from Jedi to Jedi Master X.
I had to use an older Odin 2.85 to install a CWM recovery(I prefer TWRP UI)
Once I had the CWM I could install Jedi Master X2 and I had to wait about 30 mins for it to get through boot.
I thought I had a good soft brick but eventually I found a combiination of Odin, recovery and Rom to get it to work.
Good Luck

Recovery screen is now up!
After I was able to boot, I tried flashing again to stock firmware, and this time the recovery menu works just fine! I'm almost back to where I need to be. After resetting to factory defaults, I'm hoping I can do an OTA update to 4.3 so my Galaxy Gear will work again.

geekinator said:
After I was able to boot, I tried flashing again to stock firmware, and this time the recovery menu works just fine! I'm almost back to where I need to be. After resetting to factory defaults, I'm hoping I can do an OTA update to 4.3 so my Galaxy Gear will work again.
Click to expand...
Click to collapse
Update to 4.3 official will fail if you have a custom recovery...
I suggest using the leaked 4.3 we have...
It will give you all of the gear functions....and allow you to keep root and dump the bloat that you don't want...
A best case situation ....IMHO....g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...

geekinator said:
After I was able to boot, I tried flashing again to stock firmware, and this time the recovery menu works just fine! I'm almost back to where I need to be. After resetting to factory defaults, I'm hoping I can do an OTA update to 4.3 so my Galaxy Gear will work again.
Click to expand...
Click to collapse
Glad you were able to figure it out... I just had a similar problem because TWRP froze up on me halfway through flashing a ROM. Had to ODIN CWMR back on and flash a ROM... lesson learned... always keep a ROM on your SD card in case your phone soft bricks - if you can get into download mode at least you will be able to work around it!!

I'll give that a try
gregsarg said:
Update to 4.3 official will fail if you have a custom recovery...
I suggest using the leaked 4.3 we have...
It will give you all of the gear functions....and allow you to keep root and dump the bloat that you don't want...
A best case situation ....IMHO....g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Click to expand...
Click to collapse
Thanks, I'll definitely give that a try.

geekinator said:
Thanks, I'll definitely give that a try.
Click to expand...
Click to collapse
Instead of the leaked you can use the official without locking yourself into the 4.3 bootloader
http://forum.xda-developers.com/showthread.php?t=2589891

hi to all my senior
---------- Post added at 07:25 AM ---------- Previous post was at 07:17 AM ----------
i have problem with my samsung note 2 i317 of white screen of death i tried flashing with many file but no successes it always fail (ODIN) with latest version im able to go to download mode tryed with most of the firmware please help if any body can thankks in adv.
FACTORY MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY:Samsung official
SYSTEM STATUS: Custom
this much it shows on the download mode screen pls help Thanks.

i have problem with my samsung note 2 i317 of white screen of death i tried flashing with many file but no successes it always fail (ODIN) with latest version im able to go to download mode tryed with most of the firmware please help if any body can thankks in adv.
FACTORY MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY:Samsung official
SYSTEM STATUS: Custom
this much it shows on the download mode screen pls help Thanks.

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?

Would like to return phone to Normal State

I ended up having to use CF auto-root, I was able to update cwm from within it.
After I tried rooting (didn't notice the guide I was using was 3 years old until it was too late) my phone got the "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT: KERNEL" . And it would not ****ing start up. My phone was 4.4.4 and I was trying to flash some 4.2.2 or later stuff onto it I guess, it messed my phone up. The only one and I mean ONLY one that would work was the 4.2.2 auto-root.
I was on kies before all of it and now kies won't even read my phone. Any way I can get my phone back to normal now, and possibly try the rooting again? It's slow and laggy now, my SD card won't be read, and my wifi doesn't work. I'm quite miserable but at least my phone works.. I have root access now so maybe I can fix it from within the phone? I appreciate the help!
EDIT: I tried getting cyanogen rom onto it and it got all messed up again after that, wouldn't get past cyanogen loading animation so I had to figure out how to fix it again for another 3 hours -.-

dameware said:
I ended up having to use CF auto-root, I was able to update cwm from within it.
After I tried rooting (didn't notice the guide I was using was 3 years old until it was too late) my phone got the "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT: KERNEL" . And it would not ****ing start up. My phone was 4.4.4 and I was trying to flash some 4.2.2 or later stuff onto it I guess, it messed my phone up. The only one and I mean ONLY one that would work was the 4.2.2 auto-root.
I was on kies before all of it and now kies won't even read my phone. Any way I can get my phone back to normal now, and possibly try the rooting again? It's slow and laggy now, my SD card won't be read, and my wifi doesn't work. I'm quite miserable but at least my phone works.. I have root access now so maybe I can fix it from within the phone? I appreciate the help!
EDIT: I tried getting cyanogen rom onto it and it got all messed up again after that, wouldn't get past cyanogen loading animation so I had to figure out how to fix it again for another 3 hours -.-
Click to expand...
Click to collapse
Go to this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Download the NH7 or NK2 firmware (both are 4.4.4) and flash it using ODIN. Not sure why Kies isn't seeing your phone, it should, but ODIN should work. You may have to flash, pull battery, flash again, all without rebooting, for it to take.
This will get you back to stock. Then, if you want to root, get the CFAutoRoot for the phone, this will flash a non-stock recovery to give you root. This will give you the SEANDROID messages you were seeing. Use Triangle Away, if you want to get rid of them.
Rob

rlichtefeld said:
Go to this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Download the NH7 or NK2 firmware (both are 4.4.4) and flash it using ODIN. Not sure why Kies isn't seeing your phone, it should, but ODIN should work. You may have to flash, pull battery, flash again, all without rebooting, for it to take.
This will get you back to stock. Then, if you want to root, get the CFAutoRoot for the phone, this will flash a non-stock recovery to give you root. This will give you the SEANDROID messages you were seeing. Use Triangle Away, if you want to get rid of them.
Rob
Click to expand...
Click to collapse
It won't read it because my phone is now too old of a device for the program (2.2.2 or whatever). Thank you very much I'm trying all this right now, finally a firmware download that doesn't take 6 hours because of horrible servers!
I will update on if this works or not, I'm guessing it will

I am having a similar situation. I used CM installer to root my S4 then the screen went white and the Installer stopped working. I tried to reset but only got the same Enforcing and warrant messages and the CyanogenMod loading screen.
I am trying to get to recovery mode by doing power+home+volume up button. I got into there and seeing a menu of commands. What should I do now? Will factory reset get me back into original state or I need to install a zip?

Lopakas said:
I am having a similar situation. I used CM installer to root my S4 then the screen went white and the Installer stopped working. I tried to reset but only got the same Enforcing and warrant messages and the CyanogenMod loading screen.
I am trying to get to recovery mode by doing power+home+volume up button. I got into there and seeing a menu of commands. What should I do now? Will factory reset get me back into original state or I need to install a zip?
Click to expand...
Click to collapse
EDIT:
Done and done! It all worked out, thank you thank you!
Now to try cyanogen and my device will be back to beast mode.
Just do what he says and you should be fine; factory reset never did anything for me :/

[Q] Help please Samsung Galaxy S3 unbrick.

Hello Everyone.
Please, I need some help. I was trying to downgrade an ATT Samsung Galaxy S3 from 5.0 to 4.1.1 and try to unlock it.
First, Try to flash with Odin 3.04, Odin 3.07 and Odin 3.09 with the firmware 4.1.1 from Samsung. It always failes.
So I rooted it , installed a team Win Recovery Project 2.6.3.1 and flashed a custom rom based on Android
4.1.2 thinking it will break the bootloader. Nothing.
I tried Emergency Recovery with Kies did not work.
In odin mode:
Product Name: SGH-I747
Current Binary: Custom
System Status: Custom
Qualcom Scoreboot: Enable
Warranty Bit:1
Bootloader AP SWREV:3
I spent hours on it. I don't know what to do.
Anyone has a idea to help me please?
Thanks you very much in advance.

If you can get into download mode, flash the latest Philz d2lte recovery using the tar.md5 file and Odin. Copy a ROM to an external SD card (I recommend the latest CM11), boot into recovery, flash the ROM, boot the phone. Once the phone boots, confirm your bootloader and modem version. I recommend not flashing anthing until you at least know your bootloader version.
Continuing to flash files without knowing the bootloader verson can hard brick you phone.

audit13 said:
If you can get into download mode, flash the latest Philz d2lte recovery using the tar.md5 file and Odin. Copy a ROM to an external SD card (I recommend the latest CM11), boot into recovery, flash the ROM, boot the phone. Once the phone boots, confirm your bootloader and modem version. I recommend not flashing anthing until you at least know your bootloader version.
Continuing to flash files without knowing the bootloader verson can hard brick you phone.
Click to expand...
Click to collapse
Thank you for your quick answer like you said i tried to flash cyanogen mod 11 and it aborted. How can I find out my bootloader version?

MEEEEEEEE said:
Thank you for your quick answer like you said i tried to flash cyanogen mod 11 and it aborted. How can I find out my bootloader version?
Click to expand...
Click to collapse
If you're on Philz touch, download AROMA file manager and store it on your external SD. You can get it here.
Boot into recovery and flash the file manager like you would install a ROM and it will open the file manager. Once you're up in the AROMA file manager, one of the menu options is to open a console. Once you're up in the console window the following command will tell you what bootloader you have loaded:
Code:
getprop ro.bootloader
That command will work from ADB shell in custom recovery too, if you happen to have ADB and all the drivers set up right on your computer.
What error did you get when flashing with Philz? Was it error 7?

Yes. It was a status 7. And I don't know what happens. Right now it looks hard bricked. I can not even it start it and put it on the downloading mode. When I plugged it to the power source without the battery. I have a big red led on and any responses. What is it? Can I go back to the downloading mode with a jig?

MEEEEEEEE said:
Yes. It was a status 7. And I don't know what happens. Right now it looks hard bricked. I can not even it start it and put it on the downloading mode. When I plugged it to the power source without the battery. I have a big red led on and any responses. What is it? Can I go back to the downloading mode with a jig?
Click to expand...
Click to collapse
Pull the battery, leave it out for a few minutes, then try to boot into recovery or download mode. This has cured some curious behavior for me a few times (just a shot in the dark though).
Another random thought, do you know how much battery power you had left? I'm a little surprised a failed CM flash would result in a hard brick when you still had download and recovery working before. Any chance the battery is dead? It won't charge without a working rom.
If that doesn't work and you can't get into recovery or download mode it might be time to move on to the debrick threads.

You may have to try a de-brick image. Status 7 usually occurs when the recovery is out of date.

jason2678 said:
Pull the battery, leave it out for a few minutes, then try to boot into recovery or download mode. This has cured some curious behavior for me a few times (just a shot in the dark though).
Another random thought, do you know how much battery power you had left? I'm a little surprised a failed CM flash would result in a hard brick when you still had download and recovery working before. Any chance the battery is dead? It won't charge without a working rom.
If that doesn't work and you can't get into recovery or download mode it might be time to move on to the debrick threads.
Click to expand...
Click to collapse
I tried to take the battery out and the flash is light on for a micro second but the phone does not boot. I can not go either in the recovery mode nor the downloading mode.
The is a custom rom on the phone. There is a slim kat v9 on it.

MEEEEEEEE said:
I tried to take the battery out and the flash is light on for a micro second but the phone does not boot. I can not go either in the recovery mode nor the downloading mode.
The is a custom rom on the phone. There is a slim kat v9 on it.
Click to expand...
Click to collapse
You did put the battery back in after pulling it for a couple of minutes, right? Looking back at my previous post it was poorly worded.
The fact that you went from working recovery and download to not working on a status 7 is curious. Usually status 7 errors are the developers trying to protect us from ourselves; your recovery is out of date, you are trying to flash a rom that isn't for your phone or doesn't like your bootloader, something like that. When you get a status 7, usually the recovery didn't actually do anything. It failed a safety check and quit. That's what made me wonder if maybe your battery just died.

So you flashed CM11 for the d2lte using the latest version of Philz? Did you flash anything else?

Actually I gave the cellphone to someone few days ago and he told me that I needed to unlock the bootloader and install EZ-unlock. Unlocked the bootloader. Philz is still on the recovery partition. The firmware flashed is slim kat v9. Since the bootloader has been unlocked. The phone does not want to start. I tried to take out the battery for few minutes. it does not change anything.

MEEEEEEEE said:
Actually I gave the cellphone to someone few days ago and he told me that I needed to unlock the bootloader and install EZ-unlock. Unlocked the bootloader. Philz is still on the recovery partition. The firmware flashed is slim kat v9. Since the bootloader has been unlocked. The phone does not want to start. I tried to take out the battery for few minutes. it does not change anything.
Click to expand...
Click to collapse
the phone wont start because the i747 bootloader does not come locked. what ez-unlock does for this device is effectively BRICK it!!!!! i know because thats how i bricked my first i747. now you really do need the debrick image. when plugged in , without battery does the led show red ?
http://forum.xda-developers.com/showthread.php?t=2549068
"all i can really do , is stay out of my own way and let the will of heaven be done"

Yes. The red led is showing when I plugged the device without the battery.
mrrocketdog said:
the phone wont start because the i747 bootloader does not come locked. what ez-unlock does for this device is effectively BRICK it!!!!! i know because thats how i bricked my first i747. now you really do need the debrick image. when plugged in , without battery does the led show red ?
http://forum.xda-developers.com/showthread.php?t=2549068
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse

MEEEEEEEE said:
Yes. The red led is showing when I plugged the device without the battery.
Click to expand...
Click to collapse
pretty positive sign of a brick if thats all you can get. check the link for the "de-brick" thread that i posted. remember that sometimes it takes more than one try , and while one sdcard will work for one phone , it may or may not work for another. just keep trying. good luck.:thumbup:
"all i can really do , is stay out of my own way and let the will of heaven be done"

Do I need to get a jig to un-bricked it?

MEEEEEEEE said:
Do I need to get a jig to un-bricked it?
Click to expand...
Click to collapse
nope. read the thread. a de-brick image and sdcard should do it.
"all i can really do , is stay out of my own way and let the will of heaven be done"

A jig would be helpful if the phone boots but you can't get into download mode.

[Q] help - i think my phone is temporary bricked

hi,
so i just got my s6 edge for sprint shipped to me (it wasn't activated to any service when i got it). here is the order of events i took:
1) tried to activate my service, but there was a delay in porting the #
2) while waiting for them to port it, i rooted it, installed twrp and a rom (this was when it was on 5.0.2)
3) they called and said they were ready to port, but the new rom didn't have the activation software in it. so i stalled them and said i would call back. i then reverted back to stock using odin.
4) got the number ported and was fine using the phone at that point.
5) this is where the day turned bad...... i didn't realize that coincidentally today, a new firmware was released to 5.1.1 and the phone auto-updated to it while i wasn't looking
6) i went to go re-root it using the same 5.02 root and now my phone is stuck. it's sitting on the "Samsung Galaxy S6 Edge, Powered by Android" screen and in the top left in red it says "RECOVERY IS NOT SEANDROID ENFORCING"
7) i tried to restore it back to the stock using odin, but it errored in the download mode (i don't remember the error off hand)
i can get into download mode, and that's about it. i had to let the phone's battery die on it's own to turn it off (this phone gets super hot, btw)
so i guess what i need to know is how to restore back to factory default again, now that it thinks it's on 5.1.1. is there any hope?

I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.

bbacon said:
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
Click to expand...
Click to collapse
check this post, download the tar and flash it in odin. it worked for my phone!
http://forum.xda-developers.com/showpost.php?p=61650724&postcount=142
it got me into a recovery image that worked and i was able to factory reset in there. my phone is booting properly now. (after it reboots when done, it took a bit on the first title screen to do anything, just be patient)

Thanks man, that worked great. Although I found out in the process of trying to fix it the past few days, I must have flashed a non-compatible kernel because once it boots the touch screen is unresponsive. I guess I'll have to wait until the firmware download is available after all. Thanks again for the help though