Database Info

Bricked my Thrill already

Resolved the problem

bricked mine as well, but i did it with DynamicRam's tweaks that was posted on another forum and confirmed working on the Thrill. Mine is stuck at the LG boot screen and will NOT go passed it.
Ive tried recovering it. doesnt work. Tried the LG Recovery software and sadly it doesnt support the Thrill yet.

Well it makes me feel better knowing I'm not alone, but it still sucks for us huh? I was gonna try the unbricking method for the Optimus 3d but I'm afraid it wont work because it's a European ROM instead of the stock one for the Thrill. I am willing to try anything at this point but I don't have much confidence in this unfortunately.

Hey guys im really sorry to hear about your problem... i also replaced the app_process and system_server files as well as the 99 tweaks no boot animation file... all permisions checked then rebooted... worked great on my rooted thrill already see better battery life !!!
All i can tuink of is u prolly noticed with root explorer you need to click the mount/unmount button to paste the modded files... right after you check permissions u need to click the mount/unmount button again... that could screw it up if you didnt...
I have not heard of anyone getting a recovery working on this yet... i would take it back where ever you got it and tell them its broke... and get a replacement...
Good luck
Sent from my LG Thrill 4G

Trekfan422991 said:
Hey guys im really sorry to hear about your problem... i also replaced the app_process and system_server files as well as the 99 tweaks no boot animation file... all permisions checked then rebooted... worked great on my rooted thrill already see better battery life !!!
All i can tuink of is u prolly noticed with root explorer you need to click the mount/unmount button to paste the modded files... right after you check permissions u need to click the mount/unmount button again... that could screw it up if you didnt...
I have not heard of anyone getting a recovery working on this yet... i would take it back where ever you got it and tell them its broke... and get a replacement...
Good luck
Sent from my LG Thrill 4G
Click to expand...
Click to collapse
Thanks for the advice, but won't they see that it's been rooted after they finally figure it out and charge full price on a new one or something? I'd rather be 100$ down and wait out a fix than $600 down total.

i have returned many bricked devices if it wont get past that att screen tjere is no way to know
Sent from my LG-P925 using XDA App

i bricked my phone first phone yesterday just went back amd said it wont boot they dont know why it wont boot
Sent from my LG-P925 using XDA App

Not exactly sure what could have went wrong. Can you guys pm me exactly what you did that bricked your devices.
I have applied the tweaks with no issues
Sent from my LG-P925 using XDA App

N!ghtgold said:
i bricked my phone first phone yesterday just went back amd said it wont boot they dont know why it wont boot
Sent from my LG-P925 using XDA App
Click to expand...
Click to collapse
We do now...noted

manske90 said:
Well it makes me feel better knowing I'm not alone, but it still sucks for us huh? I was gonna try the unbricking method for the Optimus 3d but I'm afraid it wont work because it's a European ROM instead of the stock one for the Thrill. I am willing to try anything at this point but I don't have much confidence in this unfortunately.
Click to expand...
Click to collapse
That will not work.
I am trying to find a way to get into the phone to fix it AND see what could have went wrong. It doesn't make sense
Sent from my LG-P925 using XDA App

Trek.. It sounds like he was doing a different tweak. He was editing the build.prop not doing the 99 tweak
Sent from my LG-P925 using XDA App

00mred00 said:
Trek.. It sounds like he was doing a different tweak. He was editing the build.prop not doing the 99 tweak
Sent from my LG-P925 using XDA App
Click to expand...
Click to collapse
That's correct. Sorry that I wasn't quite specific enough.

Cant you atleast enter recovery mode? Because from there the problem would be solvable.
Sent from my LG-P925 using XDA App

Yes I am able to boot into stock recovery mode. I tried factory reset, clear cache, all those options available but none fixed it.

manske90 said:
Yes I am able to boot into stock recovery mode. I tried factory reset, clear cache, all those options available but none fixed it.
Click to expand...
Click to collapse
factory reset i believe does not rewrite the system partition.. only clears the data partition meaning the build.prop you edited, which is in the system partition, and is not going to be replaced by a working one...

manske90 said:
Resolved the problem
Click to expand...
Click to collapse
How?
Sent from my LG-P925 using XDA App

i bricked mine the first day i had it. Luckily most phone shop employees dont know the first thing about mobiles. Mine was stuck booting into CWM recovery after an update from LG, i should have read the forums before updating. I just took it back and said it keeps going into recovery and they gave me a new one. I havent installed CWM on this one just to be safe

[Q] GT-i9003 cannot start after flash

Hi,
I have just flash my GT-i9003 using Odin to GT-I9100_O2U_I9100XWLP3_I9100O2ULP4_I9100XXLPR, but I failed to upgrade, and I am not able to start my phone since then, any help?

can you bring it back to download mode?
hold volume down +home button + power button
coz if you can bring it to download mode ... reflash to XXKPE first
tell us what was your stock rom before you tried flashing?

I cannot even boot up or do anything to it. I have also tried to remove it's battery and put it back, tried to start again, but still nothing happen.

can you try doing this method?
http://forum.xda-developers.com/showthread.php?t=1411768
but be very careful

Hi, I have tried several times, but still nth happen. any other idea? Thanks

im just a newbie too and im just trying to refer from topics that i have read
hmmmm probably its not just a soft brick but a hard one
maybe you need to buy a USB jig for i9003 or make one
there are tutorials available about it on google
but as ive heard they wont really work if your phone doesnt turn on at all
or lastly send it to samsung service center if you are still under warranty and tell them that it happened while you updated with kies
then hope and pray they will replace parts or fix it for free
if not under warranty anymore
http://www.jtagbox.com/category/riff-jtag-box-owners-unbrick-your-phone/
sorry mate, this is the farthest i can go
i hope some others can give better ideas

Its an obvious hard brick as you flashed a rom meant for i9100. Service centre you go
Cheers
Sent from my GT-i9003 powered by Stable and Smooth CleanKpu rom

i have the same problem
my gt-i9003 is not booting after i format my system mistakenly via clockworkmod and it stopped booting i need help lpease.

I have gotten a solution to the problem by flashing ddlf2
Sent from my GT-I9003 using xda premium

A sad, sad story. One more sl9003 has bites the dust.
In developer section even it was not related topic, the moderators kept the 5th thread only to warn sl9003 flashers.
Sorry to know it.

JTAG may help you

amsad said:
I have gotten a solution to the problem by flashing ddlf2
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
Neither ddlf2 helps

(Q) How To Correct Corrupted/Faulty DATA Partition on P6800?

Hello..
I'm getting ERROR message everytime I try to enter the recovery mood. Its happened 2 days ago. I've tried to flash the stock ROM for several times and hoping that could correct this issue. Unfortunately, that couldn't help and leaving me dissapointed.
I noticed this issue for the first time when my device cannot process the command line "Updating BLA BLA..." during entering the recovery mood. Its stop there and nothing is happened for about more than 5 minutes until I forced it to shutdown by long pressing the power button. Then, I tried to enter the recovery mood for the second time. You guys know what happened to my device?
I predict that situation is okay until when I try to WIPE all data and encountered an error message with the red text asking me to 'use UI to format system and reboot'.
But, I still don't know what to do. I'm hoping that you guys with kind hearted to please do help me. Thanks in advance.
One more thing, please teach me how to make this flash counter mark (!) disapear......... THANKS.
Sent from my GT-P6800 using XDA Premium HD app

Mind was replaced new mainboard.
If you cannot, I recommend you read Samsung note forum. There are thread about 'parted' command to repartition to skip bad block. Mind was success to skip and boot but lost a lot of gigabyte.
Sent from my GT-P6800 using xda app-developers app

Thanks for replying to my question.. Will read the forum for sure.. Thank you.

Recently I faced the similar problem twice. The 1st time was using ODIN to flash the latest CWM and then format the DATA folder through the advance setting... solved the problem...
2 days ago, I faced the same problem again and the solution above won't help at all. I use the ODIN flashed the original Samsung firmware and do reset to default through the original recovery and it works. But I lost all my internal data in the internal memory.
So, you could try the suggestion above if it helps. Just the 2nd one WILL DELETE ALL DATA and it is UNRECOVERABLE. So you been warned. Don't blame me if you lost your multi-billion project file.

marwanxx said:
Hello..
I'm getting ERROR message everytime I try to enter the recovery mood. Its happened 2 days ago. I've tried to flash the stock ROM for several times and hoping that could correct this issue. Unfortunately, that couldn't help and leaving me dissapointed.
I noticed this issue for the first time when my device cannot process the command line "Updating BLA BLA..." during entering the recovery mood. Its stop there and nothing is happened for about more than 5 minutes until I forced it to shutdown by long pressing the power button. Then, I tried to enter the recovery mood for the second time. You guys know what happened to my device?
I predict that situation is okay until when I try to WIPE all data and encountered an error message with the red text asking me to 'use UI to format system and reboot'.
But, I still don't know what to do. I'm hoping that you guys with kind hearted to please do help me. Thanks in advance.
One more thing, please teach me how to make this flash counter mark (!) disapear......... THANKS.
Sent from my GT-P6800 using XDA Premium HD app
Click to expand...
Click to collapse
Try to reflash and repartition using original Pit file and original firmware( assume is Honeycomb ) for ur tab using Odin 3.17, I've encountered this kind of problem before and voila! It nvr happen again.
Sent from my GT-P6800 using XDA Premium HD app

where to get odin 3.17?
thanks, btw..
*Question: I'm using Odin 3 v1.85. Is only the Odin 3 v1.70 could correct the problem?

marwanxx said:
where to get odin 3.17?
thanks, btw..
*Question: I'm using Odin 3 v1.85. Is only the Odin 3 v1.70 could correct the problem?
Click to expand...
Click to collapse
Here:
http://forum.xda-developers.com/attachment.php?attachmentid=428348&d=1288241246
ps. This DID work for me. I was unable to flash a working ICS with v1.85 but this version 1.70 worked.
UPDATE: My P6800 No longer powers on. No Recovery, No Download mode. nada ;(

kable said:
Here:
http://forum.xda-developers.com/attachment.php?attachmentid=428348&d=1288241246
ps. This DID work for me. I was unable to flash a working ICS with v1.85 but this version 1.70 worked.
UPDATE: My P6800 No longer powers on. No Recovery, No Download mode. nada ;(
Click to expand...
Click to collapse
there's another thread with this problem in 'general' will edit with link momentarily. i'm having the /data format/mount error, and i'm afraid to try flashing ICS with a previous ODIN version as i CANNOT afford to loose this device.. from what i understand... THIS is the superbrick bug.... and with no warranty for customers in the US.... ugghhh..

There is a way to fix it . You need to bet it JTAG ed . I cant vouch for the guy but there is someone
On XDA that does offer that service . I dont have the link right now but do a search and you can find
It I hope . I will look for the link later . Dont give up there is hope .
http://www.jtagbox.com/jtag-news/ri...brick-dead-boot-repair-supported-world-first/
I have been looking at this.

[CAUTION][ICS][UPDATE][DOWNGRADE]Read before flashing ICS

After the ICS was leaked, it bought some good news and as well some bad news..
Some of our user have just bricked their mobile after performing a wipe data thru recovery..
The cause of error is yet unknown..
Out user vijai has published some of the known causes...
The credit goes to vijai for pointing it out
vijai2011 said:
CAUSES
Symptoms of super brick(caused by emmc bug):
1.Phone gets stuck at splash screen.
2.recovery gets stuck at whenever trying to access corrupted partition.
3.ODIN gets stuck at flashing factoryfs.
4.You can flash kernel but almost nothing else using both ODIN and cwm.
Sent from my GT-N7000 using xda app-developers
Click to expand...
Click to collapse
vijai2011 said:
FIX
No problem....temporary fix to avoid bricking is to avoid using cwm to flash anything,doing wipes in cwm,formatting partitions in cwm,doing factory reset through settings and by typing code in phone,removing large size files from sdcard.
The permanent fix is to disable MMC_CAP_ERASE in kernel while making it.Any kernel dev can do that easily I guess....
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
This definitely doesn't mean that all galaxy R handset are brick bug or you may encounter such problem..
Only a few have encountered the problem and the cause is yet unknown. This definitely, doesn't stop you from flashing ics..if you want to flash keep these things in mind.
Also, please do not completely rely on brick bug app from play store because the app (imo) is not supported to our device (correct me if i am wrong)
(i am no developer, just heard from my fellow user )
*****NOTE******
This applies to the Stock ROM released by machram and as well to all those ROM which are based/built upon the Stock ROM.
Click to expand...
Click to collapse
SO WHAT DOES IT MEANS TO YOU ?
If you have already flashed ICS, you are requested not to wipe data through CWM/Stock recovery and also do not factory reset the phone till the issue is identified. i.e. Once ICS === No Wipe (till its rectified)
Click to expand...
Click to collapse
Currently there are only two users who have hard bricked their phone after flashing ICS.
As you might be aware by now that the emmc brick bug app is not compatible with our phone.
The most elite developer Entropy512 wants to make it compatible and hence wants some sample..
Entropy512 said:
Can someone who experienced damage and still has their device contact me via PM? One of my contacts wants to collect a few damaged devices.
Click to expand...
Click to collapse
Note: I dnt recommend you to brick your phone
(thanks m.kochan, callmeventus, cooleagle)
A big thanks to entropy for showing interest to our device

Caution:
Here's what to say from a user who bricked his phone
mj.vikram said:
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck..
Click to expand...
Click to collapse
*******UPDATE********
Here is the new fix method
vijai2011 said:
And guys for the guide to safe flash:
Flash a GB kernel,boot into recovery,flash any rom.GB or ICS.Its safe to wipe in gb kernel.But once you flashed ICS you arent safe.If you need to wipe again,you need a GB kernel again.
This was the method we used in Note to wipe when had not got a safe kernel.
Click to expand...
Click to collapse
We have got one lucky user who is enough brave and tested this method
selva.simple said:
To make a conclusion to that, i have tested your method in Galax R buddy. I found that i had a GB kernel in my phone. So why wait till i reach home. Tested now itself. I tested two rounds. One is for getting ICS via CWM flash and the other is for getting ICS via CWM restore.
First Test:
1. Flashed GB kernel
2. Rebooted to Recovery
3. Wipe data
4. Flash ICS by CWM flash i.e., "Install from Zip" method
5. Reboot
Second Test:
First Three points are same. and finally Restored a nandroid backup of ICS i took earlier. Reboot
In both the method i was able to boot the phone and get the ICS ROM and ICS kernel. To add more,
After both boots, I tested the system apps and data apps - mainly Play store, Gmail, Music player, Gallery, Camera for any FC issues. Everything is working perfectly and no issues created apart from existing issues of ICS.
Click to expand...
Click to collapse

And I forgot to add that It is not necessary that brick occurs once you do the above said things....for example,brick may occur at 10th factory reset,100th flash etc....And it is safe to flash anything with Odin as it shouldn't invoke MMC_CAP_ERASE from kernel when flashing.
Sent from my GT-N7000 using xda app-developers app

vijai2011 said:
And I forgot to add that It is not necessary that brick occurs once you do the above said things....for example,brick may occur at 10th factory reset,100th flash etc....And it is safe to flash anything with Odin as it shouldn't invoke MMC_CAP_ERASE from kernel when flashing.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes i do agree..d problem may arise on 1st or on 100th wipe...
Bt the cause is yet unknown...
So imho, all the noobs shldnt do..who knows they get it for the first time...
Sent from my GT-I9103 using Tapatalk 2

Seriously? Removing large size files from sdcard can brick my phone?

Fusrodah said:
Seriously? Removing large size files from sdcard can brick my phone?
Click to expand...
Click to collapse
Dont know...but i have tried deleting large files as 1gb game data...such as max payne and asphalt7
No brick...
Sent from my GT-I9103 using Tapatalk 2

Fusrodah said:
Seriously? Removing large size files from sdcard can brick my phone?
Click to expand...
Click to collapse
Yes....sometimes.....it was reported by like 2 users have galaxy Note.While deleting large files,the phone stuck and force reboot caused damaged sdcard.
Sent from my GT-N7000 using xda app-developers app

vijai2011 said:
Yes....sometimes.....it was reported by like 2 users have galaxy Note.While deleting large files,the phone stuck and force reboot caused damaged sdcard.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Well, how much reports from Galaxy R users with bricks? I see one from mj.vikram. Anyone else?

So a little story now.
From where has this infamous brick bug appeared??
Analysis by kernel devs say that MMC_CAP_ERASE command in kernels are present from gb periods.But why hasn't it been causing problems in GB?That's because it was disabled as Google didn't see the need for it.
But in ICS they feel that just removing files causes security problems.so they thought of enabling MMC_CAP_ERASE command which will completely wipe instead of removing.
So why should it need to brick our devices?
That's because,one of the Google engineer said that our mmc uses buggy firmware that initiates wrong process when the kernel receives MMC_CAP_ERASE command.
Actually MMC_CAP_ERASE command and mmc buggy firmware are harmless on its own.But when both are combined the result is super brick.
Sent from my GT-N7000 using xda app-developers app

This is not the worst scenario. In worst case you're gonna get hardbrick with no possibility to turn your device on.
MMC_CAP_ERASE on - wasn't present in every ICS version, at least not for S2 (I know that NOte users had bigger problem with that). All previous 4.0.3 were totally safe. Latest 4.0.4 - unfortunately not. It's not really buggy firmware that causes any problem here. According to Entropy512 (I guess the best xda-expert in that matter) MMC_CAP_ERASE was activated in order to improve writing speed. Hard brick occur if the all three conditions are fulfilled here:
1) You have a faulty (brickable) emmc-chip
2) If MMC_CAP_ERASE command is activated in kernel
3) If you perform wipe/restore nand backup/install roms (wipe-type) where:
a) cwm recovery - very high risk
b) stock recovery - lower risk but still not equal 0.
So faulty emmc chip is a bomb, mmc_cap_erase is a fuse, wiping in cwm - is a trigger or fire!
Not all devices are endangered, only those with brickable emmc-chips. In regard to Note or S2 it's easier because those devices have great dev support and there were thoroughly examined. So there are known some ways to bypass this problem. In case of SGR is much harder. First of all ... we don't know which chips are really sane and which are not.

Fusrodah said:
Well, how much reports from Galaxy R users with bricks? I see one from mj.vikram. Anyone else?
Click to expand...
Click to collapse
Just two as of now so don't panic !
You can use ICS 4.0.4 but till the cause of the bricking is confirmed just don't preform any Wipe data / Wipe Cache / Factory reset operations while on ICS 4.0.4 ROM.
As per mkochan if you want to go back to the stock ROM for giving it to the service center / etc then directly flash GB / 2.3.x ROM without wiping the cache / data using CWM.
m.kochan10 said:
1) To avoid brick = don't wipe, don't do factory reset, do not restore nandbackups.
a) If you wanna to get rid of this fw.version
-> Flash a safe kernel / or best stock rom directly via Odin.
-> Wipe after installation process is done. NOT BEFORE!
2) To recover...one guy from Note section wrote a tutorial for those bricked devices that was able to turn on. He managed to recover it but he had to sacrifice 2-3 gb of internal storage. If device is not bootable then it's a motherboard replacement.
3) Turning off this function in kernel is not easy thing. I don't think this flag can be easily removed. I'm not a kernel guy....so I'm sorry but don't know much more about that. Our devs can take a look, maybe they can find a solution.
4) Bootloaders cannot be flashed via recovery, not via mobile odin either. And FW-odin version is still unavailable so I assume you still have GB ones.
5) About USB jig - Is your DM protocol the same like before? 2.0? (people with 2.1 have never been able to used jig as far as I remember)
Click to expand...
Click to collapse

Okay, we must wait for kernel with disabled MMC_CAP_ERASE. I hope we'll get it. Thanks for the information.

Oh my god
I did factory reset in ics because my keyboard dissappeared. Will my device hard brick?
I cannot understand why Samsung realeses a firmware which should make our mobile dead! What is this function even for?
Sent from my GT-I9103 using xda premium

You can find sort of explanation on the previous page

Just wondering should I worry about this if the bug eMMC app reports that I have a sane chip?

Google86 said:
Just wondering should I worry about this if the bug eMMC app reports that I have a sane chip?
Click to expand...
Click to collapse
I think app is not working for SGR, both user have used this app and app shown sane chip yet those both guys devices are bricked.
We should contact dev of app to make comp with SGR.
Sent from my CM7.2 powered Galaxy R using Tapatalk 2.

Damn it , I knew this would happen.....
"Friends forever." - Ventus

Guys actually you could check if you have any bad blocks in any partition through gpartrd in adb.Just looking its info.will post when I find some.
Sent from my GT-N7000 using xda app-developers app

OP please add this also,
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck ..
Sorry i have't seen this thread and created new one, so if you think i have created duplicate one please ask Justin to delete it....

mj.vikram said:
OP please add this also,
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck ..
Click to expand...
Click to collapse
Dude i dont have a GB Backup (CWM BACKUP)
and dude, what you gonna do now, how will you get back your phone ???

HELP with Soft Brick

So I have an old Infuse that my kids use and it went crazy the other day. Not sure what happened. Long story short I keep getting a boot loop at the ATT screen. This phone is not rooted and I'm not sure if it was on Froyo or GB. I've flashed every return from brick I can find on XDA. I'm using Odin and I'm pretty familiar with flashing/rooting etc. Can't figure this one out. The only thing I can think is the boot loaders are not the correct ones? Not sure, I keep seeing GTG's ultimate unbrick but all the links I get to it don't work. this is the only thing I haven't tried. Any help would be appreciated.
Edit to add: After I flash in Odin it goes to reboot then does the open update, verifying update, installing update, successfully installed update package.
Copying media files it says failed to mount/sdcard, can't mount /sdcard your storage not prepared yet please use UI menu for format and reboot. ??? I think that's the problem. How do I fix??

Just search in the stickies for bootloaders. That will solve your problems
Sent from my SGH-I997 using xda app-developers app

COfatboy said:
So I have an old Infuse that my kids use and it went crazy the other day. Not sure what happened. Long story short I keep getting a boot loop at the ATT screen. This phone is not rooted and I'm not sure if it was on Froyo or GB. I've flashed every return from brick I can find on XDA. I'm using Odin and I'm pretty familiar with flashing/rooting etc. Can't figure this one out. The only thing I can think is the boot loaders are not the correct ones? Not sure, I keep seeing GTG's ultimate unbrick but all the links I get to it don't work. this is the only thing I haven't tried. Any help would be appreciated.
Edit to add: After I flash in Odin it goes to reboot then does the open update, verifying update, installing update, successfully installed update package.
Copying media files it says failed to mount/sdcard, can't mount /sdcard your storage not prepared yet please use UI menu for format and reboot. ??? I think that's the problem. How do I fix??
Click to expand...
Click to collapse
If you'd like to try GTG's Ultimate Unbrick, you can find a working download here:
http://forum.xda-developers.com/showpost.php?p=22404446&postcount=391

Tried everything and no go. Not sure where to go from here. Sure seems like a hardware issue.

COfatboy said:
Tried everything and no go. Not sure where to go from here. Sure seems like a hardware issue.
Click to expand...
Click to collapse
You mentioned it's boot-looping at the Samsung logo - perhaps there's an issue with the power button.
Here's a couple of threads that may be helpful:
http://forum.xda-developers.com/showthread.php?t=2107558
http://forum.xda-developers.com/showthread.php?t=1996709

prairied0gg said:
You mentioned it's boot-looping at the Samsung logo - perhaps there's an issue with the power button.
Here's a couple of threads that may be helpful:
http://forum.xda-developers.com/showthread.php?t=2107558
http://forum.xda-developers.com/showthread.php?t=1996709
Click to expand...
Click to collapse
It goes past the Samsung logo screen then to the ATT Rethink Possible screen then keeps looping on that screen over and over. It charges normally also.

COfatboy said:
It goes past the Samsung logo screen then to the ATT Rethink Possible screen then keeps looping on that screen over and over. It charges normally also.
Click to expand...
Click to collapse
I would try flashing just a kernel (not the whole unbrick package). I have been in a similar situation and after trying everything imaginable that's what ended up fixing it for me.
Sent from my SGH-I997 using Tapatalk 2

prairied0gg said:
I would try flashing just a kernel (not the whole unbrick package). I have been in a similar situation and after trying everything imaginable that's what ended up fixing it for me.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Tried that earlier I thought, tried again just to make sure. Still no go. I appreciate all your help! :good: I'm gonna give up for tonight anyways.

COfatboy said:
Tried that earlier I thought, tried again just to make sure. Still no go. I appreciate all your help! :good: I'm gonna give up for tonight anyways.
Click to expand...
Click to collapse
This happened to me earlier. What I did was-
1 Went to full stock using heimdal one click, After completetion, U may stuck in bootloop in at&t as you said
2 Flash efs.zip found in the link below using odin. put efs.zip in odin and untouch any other setting and flash, (Ur imei may be previously corrupted so u got bootloop). This doesnot do any harm. So flash with confidence. If ur device doesnot show up in odin after u flash with heimdal one click , reinstal drivers with kies mini
Link for download http://forum.xda-developers.com/showthread.php?t=1729838
3 Now u'll be out of AT&T bootloop if ur imei was previously corrupted.
I was in similar situation. And this solved my proble.
Hit me thanks if I helped you :good:

Thanks for all the advise. Still not working. Tried everything above and much more. Different things I do give different results but pretty much the same in end. Either sticks in recovery or boot loops one way or another. Really don't see how this could be related to software but you never know I guess.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app