Develop Bugs

[Q] Soft Bricked....can't unbrick or revert to stock rom...any thoughts?

I got a replacement GS3 through insurance and rooted it yesterday. Instead of flashing CWM I tried going with TWRP this time but didn't realize that TWRP doesn't read external SD cards and my roms were all saved on the external SD. And of course, this was after I wiped everything. So I tried unrooting and flashing back the stock firmware but it keeps failing in ODIN. So I tried re-rooting and flashing CWM which works but none of the roms will flash. I keep getting a system 7 error or something to that effect when I try flashing any rom. So now I can either get to recovery mode, or download mode. If I power the phone on it gets stuck on the Galaxy S3 screen. Any thoughts as to processes to try? Links? Threads? I've tried just about everything I could find.

kinjo1023 said:
I got a replacement GS3 through insurance and rooted it yesterday. Instead of flashing CWM I tried going with TWRP this time but didn't realize that TWRP doesn't read external SD cards and my roms were all saved on the external SD. And of course, this was after I wiped everything. So I tried unrooting and flashing back the stock firmware but it keeps failing in ODIN. So I tried re-rooting and flashing CWM which works but none of the roms will flash. I keep getting a system 7 error or something to that effect when I try flashing any rom. So now I can either get to recovery mode, or download mode. If I power the phone on it gets stuck on the Galaxy S3 screen. Any thoughts as to processes to try? Links? Threads? I've tried just about everything I could find.
Click to expand...
Click to collapse
Since when does TWRP not read external SD cards? It see's mine just fine, for well over a year. Where is your nandroid backup, you know the one you made before you did anything just incase it didn't go as planned? In any case you didn't give much information to help troubleshoot. 'I tried unrooting' - if you were going to flash a stock ROM there is no need to unroot anything as the stock firmware is just that, stock. How did it fail in ODIN? Did it say why it failed, what file were you trying to flash? More often than not the system 7 error is caused from an out of date recovery, normally i would tell you to start there but given the fact you admitted to just randomly attempting to flash things to the device you are going to want to start from stock. The second sticky thread in this sub-forum is where you should start reading, because based on your post you either need a refresher or never have read it to begin with.

dntesinfrno said:
Since when does TWRP not read external SD cards? It see's mine just fine, for well over a year. In any case you didn't give much information to help troubleshoot. 'I tried unrooting' - if you were going to flash a stock ROM there is no need to unroot anything as the stock firmware is just that, stock. How did if fail in ODIN? Did it say why it failed, what file were you trying to flash? More often than not the system 7 error is caused from an out of date recovery, normally i would tell you to start there but given the fact you admitted to just randomly attempting to flash things to device you are going to want to start from stock. http://forum.xda-developers.com/showthread.php?t=1725839
Click to expand...
Click to collapse
For whatever reason, TWRP wouldn't read my sd card. And when I said I tried unrooting - I just meant flashing back to the stock ROM. Odin fails when it gets to system write. It goes down a bunch of lines of code successfully but when it gets to system write, it fails every time. I've downloaded a few different stock ROM versions for AT&T and tried switching USB ports around my laptop. I've also tried a few different versions of ODIN but I'm not coming up with anything but a soft bricked phone still.

kinjo1023 said:
For whatever reason, TWRP wouldn't read my sd card. And when I said I tried unrooting - I just meant flashing back to the stock ROM. Odin fails when it gets to system write. It goes down a bunch of lines of code successfully but when it gets to system write, it fails every time. I've downloaded a few different stock ROM versions for AT&T and tried switching USB ports around my laptop. I've also tried a few different versions of ODIN but I'm not coming up with anything but a soft bricked phone still.
Click to expand...
Click to collapse
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.

dntesinfrno said:
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
Click to expand...
Click to collapse
I could have swore I made sure to check before I started the process but I cant' check now because the phone won't boot. Can't flash back to stock. Can't flash any roms. I can get into download mode and recovery though. It's weird. I've reverted other phones back to stock plenty of times. It just keeps failing no matter what I do with this.

dntesinfrno said:
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
Click to expand...
Click to collapse
Here's another question for you, I've looked all over for the newest CWM in .tar format but everything comes in .img format. I can't use the .img in ODIN to flash to the phone and can't boot my phone to use the CWM app to flash. I suppose I could try TWRP again but when I flashed the first time - TWRP wouldn't read my EXT SD card.....

kinjo1023 said:
Here's another question for you, I've looked all over for the newest CWM in .tar format but everything comes in .img format. I can't use the .img in ODIN to flash to the phone and can't boot my phone to use the CWM app to flash. I suppose I could try TWRP again but when I flashed the first time - TWRP wouldn't read my EXT SD card.....
Click to expand...
Click to collapse
if you could wipe everything get on odin with 4.1.2 update reboot use cf root to root it (if you dont have root) after reboot download ROM Manager from Play Store install CWM recovery (easiest way to root) hope this works

[Q] Sprint Note 2 (SPH-L900) Bricked after attempted 4.3 Update

I've been having issue with my Sprint Note 2 for a while. I've also posted this to Reddit and other parts of the forum but so far have gotten no way to fix my issue. Here's the link to Reddit: http://www.reddit.com/r/techsupport...nt_note_2_sphl900_bricked_after_attempted_43/
Sorry, I didn't want to type that all up again and having to deal with formatting and such.
Basically, the gist of it, from what I can gather is that I have accidentally loaded the 4.3 bootloader with KNOX and it is currently preventing me from doing anything productive (flashing CWMR, rooting, installing stock, etc). I read here on the forum that there were ways to do so, especially this post: http://forum.xda-developers.com/showthread.php?p=46861777
I was wondering if there were steps for the Sprint Note 2 SPH-L900?
Any help in debricking my phone is appreciated.

Try these steps.
1. Boot phone into Odin/download mode
2. Flash twrp or cwmr via Odin.
3. When it reboots pull battery and then boot into recovery.
4. Flash this http://forum.xda-developers.com/showthread.php?p=36388145 it is mc2 bootloader, firmware, radio, etc...
5. Reboot phone. Things get weird for a few mins but it will boot.
You are now Knox free once again but you are also bone stock.
Sent from my SPH-L900 using XDA Premium 4 mobile app

jlmancuso said:
Try these steps.
1. Boot phone into Odin/download mode
2. Flash twrp or cwmr via Odin.
3. When it reboots pull battery and then boot into recovery.
4. Flash this http://forum.xda-developers.com/showthread.php?p=36388145 it is mc2 bootloader, firmware, radio, etc...
5. Reboot phone. Things get weird for a few mins but it will boot.
You are now Knox free once again but you are also bone stock.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've tried that multiple times. The problem here is that I can't load CWMR or TWRP. At first, I assume that I'd have to root so I downloaded the CF auto root file and flash it using ODIN. Then I tried installing CWMR (after converting to .tar using Caboomi's tool here on the forum). It would reboot and I tried holding down volume up + power + home button but nothing would happen. I try combinations of that and still nothing. I flashed the 4.3 sboot.bin to get it back to stock Samsung bootloader then retried with CWMR without rooting first this time and it still doesn't work. ODIN would tell me that it succeeds but I can't enter Recovery no mater the combination of keys that I press. I'm assuming this has to do with Knox in which case I'd just have to wait for the official 4.3 firmware on SamMobile to flash it since stock 4.1.2 won't work.

QuantumInteger said:
I've tried that multiple times. The problem here is that I can't load CWMR or TWRP. At first, I assume that I'd have to root so I downloaded the CF auto root file and flash it using ODIN. Then I tried installing CWMR (after converting to .tar using Caboomi's tool here on the forum). It would reboot and I tried holding down volume up + power + home button but nothing would happen. I try combinations of that and still nothing. I flashed the 4.3 sboot.bin to get it back to stock Samsung bootloader then retried with CWMR without rooting first this time and it still doesn't work. ODIN would tell me that it succeeds but I can't enter Recovery no mater the combination of keys that I press. I'm assuming this has to do with Knox in which case I'd just have to wait for the official 4.3 firmware on SamMobile to flash it since stock 4.1.2 won't work.
Click to expand...
Click to collapse
After flashing cwm do battery pull...Don't let it auto-reboot.
Also try different version of Odin maybe

louforgiveno said:
After flashing cwm do battery pull...Don't let it auto-reboot.
Also try different version of Odin maybe
Click to expand...
Click to collapse
I tried 3.07, 3.09, and even barebone 1.85 that came with CF auto root. It doesn't work. I can't load recovery just fine (according to ODIN) but I can't get into Recovery.

Here is the fix https://www.dropbox.com/s/s2clvyo4y6gar6s/4.3_Unbrick.tar
I promise this will fix your issue, but when you get done, you will be on MC2 with the 4.3 bootloader, but, it will boot, let you flash recovery and everything. I know this because I did the same thing as you and flashed the old cf-auto root and bricked my phone to, and I created this file to fix it and if you look in the help section, you will find my thread on how to unbrick after 4.3 update fail.
I promise though, this will fix your fone

Keithgordon said:
Here is the fix https://www.dropbox.com/s/s2clvyo4y6gar6s/4.3_Unbrick.tar
I promise this will fix your issue, but when you get done, you will be on MC2 with the 4.3 bootloader, but, it will boot, let you flash recovery and everything. I know this because I did the same thing as you and flashed the old cf-auto root and bricked my phone to, and I created this file to fix it and if you look in the help section, you will find my thread on how to unbrick after 4.3 update fail.
I promise though, this will fix your fone
Click to expand...
Click to collapse
...My God..... What ever you did, it worked. Turns out, Caboomi's file didn't work too well. I couldn't get CWMR working at all even after converting to .tar. I used TWRP instead and it works. Problem was that it asked me for my password, which I don't know since I tried everything, so I had to resort to wiping everything. I installed the file jlmancuso suggested, loading it onto SD card then flashing using TWRP, and now my Samsung Note 2 is debricked.
Your file was a godsend. Thank you!

No recovery stuck on bootloop
im having the same issue could you post that dropbox link again

So i was able to get recovery back but it wont let me mount my sd card so i cant flash anything through recover was hoping the file you have could be loaded through odin as it is a .tar file correct please help and thanks in advance.
Keithgordon said:
Here is the fix https://www.dropbox.com/s/s2clvyo4y6gar6s/4.3_Unbrick.tar
I promise this will fix your issue, but when you get done, you will be on MC2 with the 4.3 bootloader, but, it will boot, let you flash recovery and everything. I know this because I did the same thing as you and flashed the old cf-auto root and bricked my phone to, and I created this file to fix it and if you look in the help section, you will find my thread on how to unbrick after 4.3 update fail.
I promise though, this will fix your fone
Click to expand...
Click to collapse

rckingws6 said:
So i was able to get recovery back but it wont let me mount my sd card so i cant flash anything through recover was hoping the file you have could be loaded through odin as it is a .tar file correct please help and thanks in advance.
Click to expand...
Click to collapse
Yes, flash that file in Odin, it will downgrade you to MC2 with the MK4bootloader

Keithgordon said:
Yes, flash that file in Odin, it will downgrade you to MC2 with the MJA bootloader
Click to expand...
Click to collapse
MJA ? Isn't that an s4 bootloader?

louforgiveno said:
MJA ? Isn't that an s4 bootloader?
Click to expand...
Click to collapse
yep, sorry, I just woke up....I meant whatever version we are on with the note, what is it? MK4? I have both so I keep switching back and forth in the threads. Funny thing is, they are completely different, i will change that, thanks for pointing that out

my friend 's L900 bricked too ，but I cant download the file you provide , the error message is “Error (509) This account's public links are generating too much traffic and have been temporarily disabled”
may you provide another URL to download it or mail it to me ？ my email is [email protected] , thanks.
another question , how can i flash it into device with ODIN ？ from Pit ？ bootloader ？PDA ？PHONE ？ or others ？
Sent from my SPH-L900 using xda app-developers app
---------- Post added at 06:23 PM ---------- Previous post was at 06:14 PM ----------
Keithgordon said:
yep, sorry, I just woke up....I meant whatever version we are on with the note, what is it? MK4? I have both so I keep switching back and forth in the threads. Funny thing is, they are completely different, i will change that, thanks for pointing that out
Click to expand...
Click to collapse
my friend 's L900 bricked too ，but I cant download the file you provide , the error message is “Error (509) This account's public links are generating too much traffic and have been temporarily disabled”
may you provide another URL to download it or mail it to me ？ my email is [email protected] , thanks.
another question , how can i flash it into device with ODIN ？ from Pit ？ bootloader ？PDA ？PHONE ？ or others ？
Sent from my SPH-L900 using xda app-developers app

yea I still cant dowload it sorry for being a pest.
Keithgordon said:
Yes, flash that file in Odin, it will downgrade you to MC2 with the MK4bootloader
Click to expand...
Click to collapse

hello if you are online i need some help i dl the 4.3 note 2 update it has a different build than the one sprint has there are some features that are not on this build is there any way for me to get the ota from sprint
rckingws6 said:
yea I still cant dowload it sorry for being a pest.
Click to expand...
Click to collapse

rckingws6 said:
So i was able to get recovery back but it wont let me mount my sd card so i cant flash anything through recover was hoping the file you have could be loaded through odin as it is a .tar file correct please help and thanks in advance.
Click to expand...
Click to collapse
Try using TWRP instead. It gives you the option to mount an external SD card. Also try restarting into recovery again. I had Recovery bugged out on me once.

QuantumInteger said:
Try using TWRP instead. It gives you the option to mount an external SD card. Also try restarting into recovery again. I had Recovery bugged out on me once.
Click to expand...
Click to collapse
i need some help

yea i can get into twrp recovery now but my sdcard wont mount thats why im trying to use odin
QuantumInteger said:
Try using TWRP instead. It gives you the option to mount an external SD card. Also try restarting into recovery again. I had Recovery bugged out on me once.
Click to expand...
Click to collapse

For those of you who have bricked Note 2s (SPH-L900), I'm going to drop a DropBox link here to a folder of ALL of the files that I used to unbrick my phone. I experimented with multiple methods (and several sleepless nights). Some of them will be useful to you, not all. I have the Android SDK and Caboomi's converter for .img to .tar. It doesn't work too well for CWMR just FYI. ODIN-OC will attempt to load stock MC2 onto your phone but it won't work if it's bricked. Arc Converter is a program I used to try convert the MK4 .zip file to .tar to try and flash an update using ODIN. It didn't work. The steps that I took to unbrick my phone will be posted after the link.
https://www.dropbox.com/sh/c2bfpfdf0qbs6bu/ZiNC-BF5kf
Be patient. Some of the files are still updating.
Steps:
1) Put your phone into Download mode by holding volume down + power + home button at bootup
2) Use ODIN (3.07 or 3.09) to load the 4.3_Unbrick.tar file. This will take a bit of time so be patient. Once the phone boots up again, you'll get past the boot screen that says "Samsung Galaxy Note II" and you'll get the Samsung logo with the spinning icon but it will loop. This is normal.
3) Next, power off (yank the battery and cable, leave battery out but plug the cable back in) and reboot into download.
4) Flash the TWRP .tar file (don't try converting the CWMR to .tar, it won't work) then reboot.
5) Hold volume up + power + home button (be patient here)
6) You should see the Team Win logo. You're now in recovery. The TWRP may ask you for the password. It is NOT the passcode to your lockscreen or your Google password. I have no idea what it is. At this point, you'd have to wipe your phone (internal only) if you want to flash the stock recovery.
7) Load the MC2 stock recovery file with counter reset onto a microSD card and mount it onto the phone (play around with TWRP, if it doesn't see the SD card the first time, restart or play with the mount function). Just be careful not to wipe your microSD card.
8) Flash the stock recovery (give it time) and it'll restart. You should be back at 4.1.2.
EXTRA STEPS
If you're still interested in 4.3, load the MK4 update onto the microSD card as well. BEFORE you go through the activation process for the 4.1.2 firmware at boot, boot into recovery. Flash the 4.3 update using stock recovery. This should put you onto 4.3 after the phone reboots. You should now have stock 4.3 (no root).

Sorry for all the download errors, I am uploading to my websight right now and as soon as it uploads, I will post the URL, it should download much faster too. I didnt realize so many people needed it

[Q] Samsung Note II N7105T Broken

Hey All,
I have a current predicament on my hands.. I have a N7105T that I had rooted and I noticed my TWRP was out of date..So I decided to update it using an app I downloaded from the play store (Name has been lost to me) but it downloaded it and installed and updated..But I had presumed that something had gone wrong because It didn't reset on its own, so i reset it myself and after that it wouldn't load and was stuck on the boot screen (Where it tells you what phone you have)
I looked on here and found a solution, downloaded Odin and a restore TAR for my particular model..after that successfully worked I then decided to try and install a new rom on my phone...Well that was a bad idea, I did as was instructed wiped the data etc: clean installation..but for some reason it kept failing to install..
So now I cant even get into the Boot Manager and all its showing is that there was a problem with the firmware and to use Kies to fix it up, So I downloaded a stock rom from sammobile and followed the instuctions to load the rom onto my phone from another topic on this site...
It is now constantly failing when I try and use Odin to load the rom...It just hangs and then says failed in red.
I am stessing because I really need my phone and I know I should have just left it working but I like to try and experiment but unfortunately it has backfired on me.
I have the samsung drivers installed and I have one stock rom for my particular phone but I am in the process of downloading an older version.
My Provider is Telstra.
I hope I have provided enough info and not rambled on too much.
Regards
Justin

I had the same problem with you... I've learned that I shouldn't trust thing I don't download my self and read what it says.....
Anyways what I would suggest is go to twrp website and download the .tar of the recovery and use Odin to install it on to your phone and see if you can get into the recovery mode
(Volume down+power or volume up+home+power)
If that does the work install Kies onto your phone and under tools -》firmware upgrade and initialize (note you should only do this as your last resort since it'll put a boot loader that you won't want onto your phone
Gl
Sent from my SGH-I317M using Tapatalk

lil-devil said:
I had the same problem with you... I've learned that I shouldn't trust thing I don't download my self and read what it says.....
Anyways what I would suggest is go to twrp website and download the .tar of the recovery and use Odin to install it on to your phone and see if you can get into the recovery mode
(Volume down+power or volume up+home+power)
If that does the work install Kies onto your phone and under tools -》firmware upgrade and initialize (note you should only do this as your last resort since it'll put a boot loader that you won't want onto your phone
Gl
Sent from my SGH-I317M using Tapatalk
Click to expand...
Click to collapse
Ok...First I thank you for the help with Twrp
I have installed a stock rom from sammobile, I have got Twrp working but I have some problems atm
1. I cannot copy files onto my External SD Card
2. My Phone Memory is showing as Minus Storage
3. My Sim Card cannot be read from my phone.
Would you know of any fixes for these issues

Really wish I can help you but my best suggestion is to use Kies and do the firmware upgrade. ....
Sorry~
Sent from my SGH-I317M using Tapatalk

[SOLVED] How do you enter recovery mode for TWRP ? (Bootloop)

Hello everyone. I was attempting to install the Liquid Smooth 3.0 Beta ROM but it said failed in red words. So i wiped again and installed my backup. Its been stuck in boot loop. I've looked and can't seem to find how to enter recovery mode. I tried holding power + volume up + home and it just restarts the phone before it gets to the boot loop screen. Also, once I get in recovery mode, what would be the next step to fix the boot loop? Right now im reinstalling the ROM I had on backup (intergalactic) . Or should I wipe and re-install the backup?
Thanks
EDIT: Found the combo ( Volume up + home ). Now restoring my backup. If this doesn't fix the bootloop what should I do? Also when I mount my USB in recovery it doesn't show up on my computer.

TrippyAzN said:
Hello everyone. I was attempting to install the Liquid Smooth 3.0 Beta ROM but it said failed in red words. So i wiped again and installed my backup. Its been stuck in boot loop. I've looked and can't seem to find how to enter recovery mode. I tried holding power + volume up + home and it just restarts the phone before it gets to the boot loop screen. Also, once I get in recovery mode, what would be the next step to fix the boot loop? Right now im reinstalling the ROM I had on backup (intergalactic) . Or should I wipe and re-install the backup?
Thanks
EDIT: Found the combo ( Volume up + home ). Now restoring my backup. If this doesn't fix the bootloop what should I do? Also when I mount my USB in recovery it doesn't show up on my computer.
Click to expand...
Click to collapse
If you get to recovery mode, try doing a hard wipe/reset to return your phone to its original settings. You will lose all saved data so please keep your backup. Your phone may not be recognized by the computer in recovery mode but in download mode. Are you using custom recovery or stock recovery? If custom, which one?

Larry2999 said:
If you get to recovery mode, try doing a hard wipe/reset to return your phone to its original settings. You will lose all saved data so please keep your backup. Your phone may not be recognized by the computer in recovery mode but in download mode. Are you using custom recovery or stock recovery? If custom, which one?
Click to expand...
Click to collapse
Hello. How do I Hard Reset? I am using TWRP recovery mode. I've tried download mode and still not recognized. I also downloaded the latest driver.

TrippyAzN said:
Hello. How do I Hard Reset? I am using TWRP recovery mode. I've tried download mode and still not recognized. I also downloaded the latest driver.
Click to expand...
Click to collapse
Good! With TWRP, you will see the wipe option on the home screen immediately you get into recovery mode. Just do the standard wipe and then reboot to system.

Larry2999 said:
Good! With TWRP, you will see the wipe option on the home screen immediately you get into recovery mode. Just do the standard wipe and then reboot to system.
Click to expand...
Click to collapse
Just did that, still at the boot screen

TrippyAzN said:
Just did that, still at the boot screen
Click to expand...
Click to collapse
Sometimes, it may take several minutes after the reset for your phone to finally boot up so you may have to wait a bit before deciding it didn't work. However, do you recall what (stock) Android version you had before you attempted to flash the custom ROM?

Larry2999 said:
Do you recall what (stock) Android version you had before you attempted to flash the custom ROM?
Click to expand...
Click to collapse
Before I rooted? I was Jelly Bean 4.1.2 I think. But I flashed many Custom ROMs, the last one was 4.3 . The one I was installing was 4.4.2. But I dont think thats the problem, It just said failed to flash. And the back up restore was successful, just a boot loop. If I could get my computer to recognize my phone I could put my original ROM download in and flash that.

TrippyAzN said:
Before I rooted? I was Jelly Bean 4.1.2 I think. But I flashed many Custom ROMs, the last one was 4.3 . The one I was installing was 4.4.2. But I dont think thats the problem, It just said failed to flash. And the back up restore was successful, just a boot loop. If I could get my computer to recognize my phone I could put my original ROM download in and flash that.
Click to expand...
Click to collapse
Normally, if it was just a case of your phone getting stuck in a boot loop, a hard wipe/reset will fix that. If it's still not coming on, then it could be a slightly more severe case of firmware failure which, thankfully, can be easily recovered from since you can get into download and recovery modes. Your best option now would be to flash an official (stock) ROM to get your phone back in working order. From what you've said about the firmware history, stock Android 4.3 would be your best bet as you probably have the 4.3 boot-loader already. You can download the zip file you will find in the discussion thread below and flash this via TWRP recovery. The process is fairly simple. Download the zip file to your PC - do not extract. Verify the MD5. Copy to a micro SDHC card. Place the card in your phone. Boot to recovery mode. Select install and navigate your way to the zip file you just copied. Swipe across the screen to confirm installation. Wait for installation to complete. Clear your cache/dalvik. Reboot your system. Good luck!
http://forum.xda-developers.com/showthread.php?t=2658486
Before flashing custom ROMs, it is always helpful to do a lot of research as there is no easier way to brick or backdoor your phone.
NB
You need a special app to verify MD5. It's just a check to ensure you have the correct file and it downloaded correctly. If you do not have the app, check that the zip you have is about 933MB after download.

Larry2999 said:
Normally, if it was just a case of your phone getting stuck in a boot loop, a hard wipe/reset will fix that. If it's still not coming on, then it could be a slightly more severe case of firmware failure which, thankfully, can be easily recovered from since you can get into download and recovery modes. Your best option now would be to flash an official (stock) ROM to get your phone back in working order. From what you've said about the firmware history, stock Android 4.3 would be your best bet as you probably have the 4.3 boot-loader already. You can download the zip file you will find in the discussion thread below and flash this via TWRP recovery. The process is fairly simple. Download the zip file to your PC - do not extract. Verify the MD5. Copy to a micro SDHC card. Place the card in your phone. Boot to recovery mode. Select install and navigate your way to the zip file you just copied. Swipe across the screen to confirm installation. Wait for installation to complete. Clear your cache/dalvik. Reboot your system. Good luck!
http://forum.xda-developers.com/showthread.php?t=2658486
Before flashing custom ROMs, it is always helpful to do a lot of research as there is no easier way to brick or backdoor your phone.
NB
You need a special app to verify MD5. It's just a check to ensure you have the correct file and it downloaded correctly. If you do not have the app, check that the zip you have is about 933MB after download.
Click to expand...
Click to collapse
Which do I download? First or second link? Also How should I get my computer to recognize my phone? And if I do that, flashing a fresh ROM wont fix the boot loop?

TrippyAzN said:
Which do I download? First or second link? Also How should I get my computer to recognize my phone? And if I do that, flashing a fresh ROM wont fix the boot loop?
Click to expand...
Click to collapse
You need the first one since you are on TWRP. You are not connecting your phone to the computer at all so there is no worry about that. You only need to download the image to your computer and then copy it to an external Micro SD card using another device like a camera, phone, SDHC card reader/writer or SDHC card adapter if your PC has the required slot. Once you have the recovery image saved on to the external SD card, insert the card into your phone and boot into recovery mode. You will then install the zip from the card. This ROM should not only fix the boot loop, it will restore your phone to as near factory settings as possible including resetting your flash counter, installing the complete stock system and stock recovery.
Once you have your phone back in working order, you can revert to flashing custom ROMs but please be very careful and do all the research you need. Specifically, you should avoid any ROMs that may attempt to mess with your boot-loader.

Larry2999 said:
You need the first one since you are on TWRP. You are not connecting your phone to the computer at all so there is no worry about that. You only need to download the image to your computer and then copy it to an external Micro SD card using another device like a camera, phone, SDHC card reader/writer or SDHC card adapter if your PC has the required slot. Once you have the recovery image saved on to the external SD card, insert the card into your phone and boot into recovery mode. You will then install the zip from the card. This ROM should not only fix the boot loop, it will restore your phone to as near factory settings as possible including resetting your flash counter, installing the complete stock system and stock recovery.
Once you have your phone back in working order, you can revert to flashing custom ROMs but please be very careful and do all the research you need. Specifically, you should avoid any ROMs that may attempt to mess with your boot-loader.
Click to expand...
Click to collapse
Thanks for your help! That was a great idea, moving my SD card to a different device then putting the .zip in there and flashing from my device. Worked Perfectly. Didn't even have to use the restore file you linked me, I just re-flashed the old ROM i was using ( brand new, not the back up ). And its starting up now, all of my apps, widgets, wallpapers, and messages are exactly how I left them. Which is weird because of how many times I wiped and the fact that I re-flashed a brand new ROM lol.
Man this makes me not want to change ROMs anymore. Small stuff like this makes me paranoid. I don't have a back up phone lol

TrippyAzN said:
Thanks for your help! That was a great idea, moving my SD card to a different device then putting the .zip in there and flashing from my device. Worked Perfectly. Didn't even have to use the restore file you linked me, I just re-flashed the old ROM i was using ( brand new, not the back up ). And its starting up now, all of my apps, widgets, wallpapers, and messages are exactly how I left them. Which is weird because of how many times I wiped and the fact that I re-flashed a brand new ROM lol.
Man this makes me not want to change ROMs anymore. Small stuff like this makes me paranoid. I don't have a back up phone lol
Click to expand...
Click to collapse
Glad to know your phone is now functioning normally. One of your earlier restore operations probably restored your data whilst the new ROM you flashed restored the system without deleting data. Thankfully, you didn't lose anything. Now the phone is back to normal, please be careful with flashing ROMs especially custom ones.

[Q] Bricked my I747 - Please Help?

Hello,
I'm sure there are many threads on about what I'm about to asked but I am a noob and I don't know what to do!!
I tried to flash cm11 to my I747 last night but it failed. So I tried to flash my recovery and it failed at first but second time around it was successful. Only thing is that when it booted, it got stuck on AT&T splash. I left it for about 15-20 minutes but nothing happened. Wasn't sure if my screen was going to burn the image so I turned it off and removed the battery. I have been doing research on how to recover but I want to make sure I do everything correct so I can at least go back to stock.
If there is anyone out there that can please give me some help I would greatly appreciate it!
Thanks!!
Is this fixable?

loc626 said:
Hello,
I'm sure there are many threads on about what I'm about to asked but I am a noob and I don't know what to do!!
I tried to flash cm11 to my I747 last night but it failed. So I tried to flash my recovery and it failed at first but second time around it was successful. Only thing is that when it booted, it got stuck on AT&T splash. I left it for about 15-20 minutes but nothing happened. Wasn't sure if my screen was going to burn the image so I turned it off and removed the battery. I have been doing research on how to recover but I want to make sure I do everything correct so I can at least go back to stock.
If there is anyone out there that can please give me some help I would greatly appreciate it!
Thanks!!
Is this fixable?
Click to expand...
Click to collapse
\
Yeah. Should be fixable. First, can you try booting to recovery and doing a wipe/reset? I presume you have custom recovery? If this doesn't work, then you can try flashing a complete compatible stock restore image via recovery to get the phone working or flash a custom ROM? What Android version were you on prior to the attempt to flash CM? This would let us know what stock version to revert to.

I was running 4.3 before trying to flash the custom rom. I tried flash the stock rom last night using Odin, but it the flash failed on me twice. I also noticed that the micro sd I had in my cell is now completely dead. When I plug it into my pc it does not show up. I think it still shows up in recovery but it doesnt seem to be working. Im worried about sticking another card in and for some unknown reason it going dead too.
I only found a flash for 4.1.1 as far as stock rom goes.

loc626 said:
I was running 4.3 before trying to flash the custom rom. I tried flash the stock rom last night using Odin, but it the flash failed on me twice. I also noticed that the micro sd I had in my cell is now completely dead. When I plug it into my pc it does not show up. I think it still shows up in recovery but it doesnt seem to be working. Im worried about sticking another card in and for some unknown reason it going dead too.
I only found a flash for 4.1.1 as far as stock rom goes.
Click to expand...
Click to collapse
If you were already on 4.3, please do not try to flash 4.1.1 now otherwise you could risk bricking your phone. If you tried doing the hard wipe/reset via (custom) recovery and this did not work, you can try flashing a complete stock restore image via recovery. See the instructions in the following thread ....
http://forum.xda-developers.com/showthread.php?t=2658486
Unfortunately, you would need to load the stock restore zip to a (micro) SD card. Unless you are able to save files to your phone, there is no other way. Once you have the restore zip ready, boot your phone to recovery mode and flash. You can revert to a custom ROM once your phone is back to working normally.

I had this problem TeamWin Recovery. I put Philz recover on there and it worked fine. You will probably have to ADB philz recovery to your phone, if you chose to try Philz. This is what worked when I rooted my girlfriend's phone.

An easy way to install Philz Touch recovery would be to download and install the latest tar version for the d2lte and flash it via Odin.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte

Thanks to everyone for your help and solutions.
My co-worker, who flashed my root and recovery, was able to get it back to 4.3 stock. Unfortunately, the backup that he made before rooting did not work in recovery [twrp]. So I lost all my pics from the last two months since getting my phone.
As sad as I was that I couldn't recover the pics, I am happy to have my phone back to normal+root.
I'm not sure, but maybe it bricked from trying to flash cm11 thru twrp?! Can't really say, but the recovery did not go thru either.... It went thru "successfully" but after I would reboot then it would stay on ATT splash.
Oh well... all is good now. I will steer away from custom roms for now and wait until the 4.4 update comes out for my i747. Or if i get another phone later on, I can use the s3 as a lab rat.
Again, thanks to everyone!