Develop Bugs

Possibly Bricked?

Hey everyone,
I tried flashing a new rom from my phone earlier and I think it may not have flashed successfully. I hit reboot after it was finished installing but my screen remains blank and the blue led remains lit. I have tried battery pulling and using the button combos to go into either recovery or download mode but I haven't had any luck. When I use the buttons to go into recovery or download mode the led blinks for a second as though it is recognizing the command but the screen remains blank and the led stays solid blue. I have tried hooking the phone up to my computer and ODIN doesn't seem to recognize it either. Does anyone have any ideas or can anyone confirm if I am bricked? I would really appreciate some help. I have had this phone since the day it came out and have messed around with it quite a bit but I am out of ideas and have always been able to either boot into recovery or download mode Thanks in advance!

I would try a jig first. u can get one off ebay or make one. also if that doesn't work jtag maybe be your only option. hooe you can bring it to life man

What did you flash ? I was drunk as hell last night flashing a kernel in Odin in the phone section and wondering why it would never finish until I realized it was in phone not Pda .... I did it like 3 times before I finally fixed it got Cm7 back on it with no Baseband ... Funny now but odined a radio and all was fine.... The only thing that will usually F this phone up is flashing bootloader from int. Version that's a instant brick not fixable
Sent from my SPH-D710 using xda premium

I flashed the "tbm" FB17 rom which just came out today. I downloaded it directly to my phone so there is a possibility it could have been a bad download. Prior to that I was using Calkulin's stock FB17 deodexed rom which was released yesterday.

by chance did you use the touch recovery at all? lots of people have been bricking their devices lately using that.

gernade23 said:
I flashed the "tbm" FB17 rom which just came out today. I downloaded it directly to my phone so there is a possibility it could have been a bad download. Prior to that I was using Calkulin's stock FB17 deodexed rom which was released yesterday.
Click to expand...
Click to collapse
Get a jig and you'll get back into Odin
Sent from my SPH-D710 using xda premium

any suggestions for someone that can get into odin, but phone stuck in SGSII screen bootloop?
i flashed the calk's fb17 deodex version, and it started this boot loop. i pulled battery, and odin'd back to stock el29. still stuck in sgsii bootloop. it's seems to be acting like e: partition doesn't exist.

i have this problem as well

dgn_sandibalz said:
any suggestions for someone that can get into odin, but phone stuck in SGSII screen bootloop?
i flashed the calk's fb17 deodex version, and it started this boot loop. i pulled battery, and odin'd back to stock el29. still stuck in sgsii bootloop. it's seems to be acting like e: partition doesn't exist.
Click to expand...
Click to collapse
Go get sfhubs restore one click. That ought to fix it.
Sent from my SPH-D710 using XDA App

patrao_n said:
by chance did you use the touch recovery at all? lots of people have been bricking their devices lately using that.
Click to expand...
Click to collapse
I did and I bricked my phone. I am so pissed.
Jig won't work. I am so screwed.
Like fully HARD bricked. I hope there is a fix...

zzelinka said:
I did and I bricked my phone. I am so pissed.
Jig won't work. I am so screwed.
Like fully HARD bricked. I hope there is a fix...
Click to expand...
Click to collapse
jtag or just tell Sprint you were charging it and now it won't come on...
Sent from my SPH-D710 using xda premium

Not sure if this will work for you, but ill still send this link to you or those who might use this service.
http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-jtag-brick-repair/
Sent from my SPH-D710 using XDA App

Epix4G said:
jtag or just tell Sprint you were charging it and now it won't come on...
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Gibsonusa said:
Not sure if this will work for you, but ill still send this link to you or those who might use this service.
http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-jtag-brick-repair/
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
I'm going to go to Sprint today and if that doesn't work I might try the JTAG thing. Or just sell it to someone who wants to do it and get another phone. I don't really want to get another phone, but... I gotta do something.
Thanks for the responses.

The Offical how I hard bricked my E4GT thread

Well since I just bricked my phone I decided to start this tread. I figured it would be helpful for people to read to keep them from bricking their phone by not following the same process of the unlucky few who have hard bricked their device.
I flashed the Rogue CM9 kernel through Mobile Odin Pro and while on the FB17 leak from Calk which is where I think I made my mistake. when I went to flash CM9 alpha 3.1 it got stuck at install for about 15 minutes before i decided to the battery which I knew was a HORRIBLE idea. When I tried to boot back up all I got was a blue light. My guess is that the phone didn't like that I had a AOSP Kernel while on a TW rom and got confused and froze because it didn't know what to do next. The good news it that sprint is ever so gracious to provide me with a new phone coming in the mail on Thursday since they don't have any in stock. I just told them I got a update and when it installed it wouldn't boot back up and I should hopefully be back in business with some CM9 yumminess later this week thank the cellular gods for insurance!
Some users are reporting that mobiletechvideos.com is somewhere you can send your phone too have it brought back from the dead.

I got the exact same thing but my sprint reps think that the screen went out and are trying to replace it.

So I just got my second e4gt yesterday from hard bricking mine by flashing CM9 alpha 3 then flashing cwm touch recovery after I restored a nandroid of el29 it just wouldn't boot back
Sent from my SPH-D710 using XDA App

digitalcrash said:
So I just got my second e4gt yesterday from hard bricking mine by flashing CM9 alpha 3 then flashing cwm touch recovery after I restored a nandroid of el29 it just wouldn't boot back
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Everyone should hear this LEAVE CWM TOUCH ALONE ...... DON'T EVER TOUCH IT ... it is most of what is bricking these phones ... Unless they fix it don't use it for this phone .... How many people have to brick because of it .... Use the trusted acs rouge or cwm but not the touch
Sent from my SPH-D710 using xda premium

Somebody should make a sticky thread that warns people not to install the touch recovery from rom manager for this device. I notice everyone who hard bricked their device was by installing touch recovery through rom manager while using the leak ics roms or cm9
Sent from my SPH-D710 using xda premium

I posted it all over shabby's thread.....DONT USE TOUCH RECOVERY.

I learned my lesson with touch recovery and I will never use it again
Sent from my SPH-D710 using XDA App

correct me if im wrong but unless you actually burnt the processor out or dropped it in water ...couldn't u use a usb jig to just put you in download mode and odin from there worked on my fist galaxy s and fortunately i haven't had to use one sense ..and fyi really cheap and easy to make

sfal8705 said:
I got the exact same thing but my sprint reps think that the screen went out and are trying to replace it.
Click to expand...
Click to collapse
thats what happened to me as well after an hour of playing with it they decided to replace it.
the jig does nada for it just to answer that question goes
and I wasn't using touch recovery I was using rouge recovery for CM9... I think I screwed up trying to flash using the cm9 recoveery for a tw rom...

sergioperalta81 said:
correct me if im wrong but unless you actually burnt the processor out or dropped it in water ...couldn't u use a usb jig to just put you in download mode and odin from there worked on my fist galaxy s and fortunately i haven't had to use one sense ..and fyi really cheap and easy to make
Click to expand...
Click to collapse
No sometimes there are hard bricks that don't respond to jig and only fix is a jtag ....happened alot with flashing international ROM ....bootloader would disable the USB port ....
Sent from my SPH-D710 using xda premium

sfal8705 said:
I got the exact same thing but my sprint reps think that the screen went out and are trying to replace it.
Click to expand...
Click to collapse
Tell them to put the chip in a different housing and see if it works, if its the screen it would work in a different housing. I did that with my og epic..
---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------
We really should make a sticky, or a thread that says DONT USE TOUCH RECOVERY!!! and just keep bumping it up to the top.

Yup CWM Touch killed my evo during restore and data wipe.. 1st it soft brick my phone and had to factory restore a .tar and now it finally killed my phone. gotta pick up my replacement tmmrow
And yes i was using a ICS FBXX rom during this

What is the recommended way to flash to cm9 3.1 from the calks ics fb17 leak without bricking the phone?
Sent from my SPH-D710 using Tapatalk

albe070 said:
What is the recommended way to flash to cm9 3.1 from the calks ics fb17 leak without bricking the phone?
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Flash Miui Rom then flash CM9. Dont use CWM touch at all.. just use a basic recovery like rogue or stock CWM

Yep. Touch recovery seems to be the common denominator amongst the bricked phones. I was lucky enough to just get mine swapped out at a Sprint Service Center. I certainly won't be using CWM Touch for anything ever again.

blackroseMD1 said:
Yep. Touch recovery seems to be the common denominator amongst the bricked phones. I was lucky enough to just get mine swapped out at a Sprint Service Center. I certainly won't be using CWM Touch for anything ever again.
Click to expand...
Click to collapse
I think the culprit is using an aosp recovery while on a TWIZ ROM... I would avoid that because I bet that is the issue...

It doesnt seem to be just the Clock Work Mod Touch. It would seem that sbrissen thinks that in ICS the data partition or blocks are slightly different and this is causing errors when flashing ICS or back to GB from ICS. So id say for now stay away from ICS in general until this is completely sorted.

HaiKaiDo said:
It doesnt seem to be just the Clock Work Mod Touch. It would seem that sbrissen thinks that in ICS the data partition or blocks are slightly different and this is causing errors when flashing ICS or back to GB from ICS. So id say for now stay away from ICS in general until this is completely sorted.
Click to expand...
Click to collapse
so what do you say people do who have flash ICS and want to get back to GB without screwing up.. just use a .tar?

You can add me to the list...also was using touch recovery. I wonder what Sprint/Samsung is thinking about all of our E4GTs coming in for repair hahaha
Sent from my (temp) Desire HD using XDA App

YoungAceAtlanta said:
so what do you say people do who have flash ICS and want to get back to GB without screwing up.. just use a .tar?
Click to expand...
Click to collapse
Yes. I odin back to el29 stock with root and then install cwm rogue then restore a previous backup. The process is bit much but better to be safe than sorry
Sent from my SPH-D710 using xda premium

[Q] Help I think I bricked my phone!

My phone was constantly rebooting so i went into CWM and did a factory reset and it froze while wiping and since then it wouldnt reboot. I went to this thread http://forum.xda-developers.com/showthread.php?t=1551901&page=11 and followed the directions for the one click recovery using odin 1.81 but it stopped updating on the data.img. I kept it connected for over an hour. I disconnected the cable and rebooted the phone. now when i turn it on it says "firmware upgrade encountered an issue please select recovery mode in kies and try again" i tried holding power and volume down and it briefly boots up but then goes to the firmware upgrade screen. Kies isnt recognizing the phone as being connected. Any help would be greatly appreciated!

you are not the first one today (yesterday) reporting the same problem. There were about 3~4 incidents reported during today. So, don't go further at this time. I hope some more Devs joining to give more helps.
During the time you are waiting, read the almost same case -
http://forum.xda-developers.com/showthread.php?t=1554392
http://forum.xda-developers.com/showthread.php?t=1549382
Also, please describe the full details about what you did and how you did -
where did not download the rom, what's your rom/kernel version before installing the rom, how did you proceed to odin the rom, etc...
You mentioned that you tried to flash the rom using the one click recovery using odin 1.81. Can you please be more details about this?
Before flashing the rom, you said that your phone was constantly rebooting. What was your rom and kernel at that time? Do you think there was anything suspicious causing the rebooting?
Maybe the solution would be simple but I saw many people reported same thing, there would be common issue in here. So, we need to find out what that is....
Sorry for not giving you the suggestion at this time.

This isn't an ODIN issue. ODIN is just the messenger in this case.
There is a problem between the ICS kernels and custom recovery where it will sometimes corrupt your /data partition if you reset/wipe/restore/format/etc. Any large partition operations are suspect. Copying files seems fine. It doesn't necessarily do it every time so it'll work for some but brick others. Even if it works a couple of times, it can brick at any time.
The EMMC memory actually becomes damaged and even JTAG repair will not fix. By the time you get to ODIN the damage is already done. ODIN won't be able to write to /data even using a .pit file with repartition set, ODIN one-click won't write to it, CWM will hang writing to it, JTAG will have issues also.
Your best bet is to get a replacement.
There are multiple threads about this, which is why people suggest you go back to a GB-based kernel+CWM to do your ROM flashing.
This is one thread where the data.img corruption is discussed:
http://forum.xda-developers.com/showthread.php?t=1504808

Well i tried QBKings how to unbrick video and used the stock el29 stock rom through odin. It looks like it was going to work. it finished all the way but now it just gets stuck in a boot screen loop
i get update logfile does not exist deleteing cryption meta data
#manual mode#
updating application....

Maybe try using odin to flash a kernel with recovery, and get into recovery before it reboots(or pull battery since it won't boot after odin is done doing its thing). then restore a nandroid, or flash a Rom?
Sent from my SPH-D710 using xda premium

(Duplicate post - person above asked already)

sleshepic said:
Maybe try using odin to flash a kernel with recovery, and get into recovery before it reboots(or pull battery since it won't boot after odin is done doing its thing). then restore a nandroid, or flash a Rom?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I think we are in synch - http://forum.xda-developers.com/showthread.php?t=1556609 (the suggestion that I provided).
Adding to this, I personally recommend to format the sdcard before installing anythig - there's a option to format sdcard.

sleshepic said:
Maybe try using odin to flash a kernel with recovery, and get into recovery before it reboots(or pull battery since it won't boot after odin is done doing its thing). then restore a nandroid, or flash a Rom?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Well i managed to be able to get it to boot into rogue recovery or power + down so i can flash through odin. I tried flashing a rom but it cant get past formatting system.
im going to try to restore to a previous rom now

armandosal said:
Well i managed to be able to get it to boot into rogue recovery or power + down so i can flash through odin. I tried flashing a rom but it cant get past formatting system.
im going to try to restore to a previous rom now
Click to expand...
Click to collapse
It will never get past the data its corrupted and bricked ... There is no fixing it you should have never done anything in cwm with a ics kernel there are multiple threads that well tell you that ...read read ....you will now hope that sprint will replace your phone or you have insurance...good luck with sprint
Read this thread its what is wrong with your phone
http://forum.xda-developers.com/showthread.php?t=1504808
Sent from my SPH-D710 using xda premium

I'll add on to Epix4G's comment with another link:
How Not To Brick Your E4GT

I finally ended up getting another phone from my insurance company. Is there a way to get any of my data from the phone?
Sent from my SPH-D710 using XDA

armandosal said:
I finally ended up getting another phone from my insurance company. Is there a way to get any of my data from the phone?
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Nope once it's data partition is screwed it's done for and not recoverable
Sent from my SPH-D710 using Tapatalk 2 Beta-5

Ok. Thanks. on the plus side I got Cyanogenmod 9 on my phone.
Sent from my SPH-D710 using xda premium

[Q] Phone loops in Samsung Logo, will not go into recovery!

My phone kept looping on the loading screen, so i pulled the battery and got in CWM. When i did a data wide so i can restore from a saved file the phone got stuck on wiping.
So i pulled the battery and the phone kept on looping the samsung logo and would not go back to CWM, got inside ODIN and tried the stock one click EL29 ODIN method, everything flashes but gets stuck on data.bin. i re-start the process to only be stuck in the same data.bin step. the ODIN one click pro does not stop responding it just gets stuck.
I tried the ODIN method where i load the stock none rooted tar file in pda mode, this method completely passes but when it restarts it goes back to loop mode.
I tried getting into recovery mode but it loops also (Holding Volume up and power)
I am currently trying a different ODIN oneclick TAR file, maybe this will work, i will update when it finishes.
I do not know what to do next, i have flashed all individual files in ODIN also.

http://forum.xda-developers.com/showthread.php?t=1525495
Seriously again and you can't search.......you are bricked.....
http://forum.xda-developers.com/showthread.php?t=1504808
And you were using a ics kernel with cwm huh ?
Sent from my SPH-D710 using Tapatalk 2

I did search all over xda and androidcentral, i was in ics 4.0.4. Thanks for the links i left the phone flashing, when i get home i will read those threads. If it all fails ill just go to sprint tech bench and get a refurbish replament.

You were on a ics ROM ?
Used a ics kernel to wipe data ?
Were using ROM manager?
Using touch cwm ?
Didn't read OP for the ROM either ?
Almost all ics roms will tell you not to use a ics kernel with cwm that is the cause of the bricks ...
If you can answer yes to any of the above you didn't read enough... There are a dozen threads about bricking phones on here that would have saved your phone....good luck at sprint getting it replaced
Sent from my SPH-D710 using Tapatalk 2

mrperez816 said:
I did search all over xda and androidcentral, i was in ics 4.0.4. Thanks for the links i left the phone flashing, when i get home i will read those threads. If it all fails ill just go to sprint tech bench and get a refurbish replament.
Click to expand...
Click to collapse
What were u using to flash ? The OP of every aosp ROM Wether cm9 codename aokp all say to flash the el26 cwm kernel and flash from there and if going back to GB to use a stock tar and then go from there ...
Sent from my SPH-D710 using Tapatalk 2

i had CWM, i was running ics 4.0.4 fine build 30 since it came out. It just started the stupid animation loop and thats when i decided to do a data wipe in CWM. but then i did the ODIN One Click and it gets stuck on data.bin.
I work for Sprint....
This is my first time ever posting on any forums and i have been flashing since the EVO came out, i have flashed ICS to the EVO 4G and back to GB with no issues, this phone is the first to give me such issues.

mrperez816 said:
i had CWM, i was running ics 4.0.4 fine build 30 since it came out. It just started the stupid animation loop and thats when i decided to do a data wipe in CWM. but then i did the ODIN One Click and it gets stuck on data.bin.
I work for Sprint....
This is my first time ever posting on any forums and i have been flashing since the EVO came out, i have flashed ICS to the EVO 4G and back to GB with no issues, this phone is the first to give me such issues.
Click to expand...
Click to collapse
Samsung screwed us by changing some partitions and until we get source to know what they did its best to follow the OP to a T because no one has bricked when using a GB kernel to wipe or flash ....just the ics ones
Yes I had og evo nexus s and 3d ....this one sucks to have to flash the way we do but its the better phone so you do what you have to
Sent from my SPH-D710 using Tapatalk 2

You could have not said it any better lol, i on purpose broke my photon 4g and one of the replacements on the list was the E4GT and got that one sent to me lol, such an amazing phone but issues like this kill me. i did that rouge in odin and it just loops on the android with the box but does not do anything else.
Ill keep trying different things, custom count is at 3 maybe by the time i give up it might be in the 100's because i wont get a replacement till tuesday...

mrperez816 said:
You could have not said it any better lol, i on purpose broke my photon 4g and one of the replacements on the list was the E4GT and got that one sent to me lol, such an amazing phone but issues like this kill me. i did that rouge in odin and it just loops on the android with the box but does not do anything else.
Ill keep trying different things, custom count is at 3 maybe by the time i give up it might be in the 100's because i wont get a replacement till tuesday...
Click to expand...
Click to collapse
The no data tar will completely flash but won't boot on it but you can put it back to stock like that with sfhub el29 no data
Some one in the data thread I gave u did remap the data partition to his Sd card and rigged it .... That could work until you get replaced
Sent from my SPH-D710 using Tapatalk 2

Just odin the el26+cwm kernel and reboot into recovery and wipe and flash like normal. I had the bootloop before snd this worked for me.
EL26+CWM Kernel link: http://db.tt/0QJkleJR
Edit: just read your whole post and it does sound like your bricked. You can try what I stated above, but I don't think it will work.
Sent from my SPH-D710 using Tapatalk 2 Beta-5

mrperez816 said:
i had CWM, i was running ics 4.0.4 fine build 30 since it came out. It just started the stupid animation loop and thats when i decided to do a data wipe in CWM
Click to expand...
Click to collapse
This is where your /data partition got corrupted. The data wipe in ICS-based CWM.
mrperez816 said:
but then i did the ODIN One Click and it gets stuck on data.bin.
Click to expand...
Click to collapse
ODIN OneClick is just serving as the messenger to tell you your /data partition is corrupted. You could have used CWM, ODIN, ODIN OneClick, etc. They would all tell you the same thing. The EMMC memory is actually damaged, it isn't just a partition data problem.
It is unfortunate to have the issue with ICS-based kernels and custom recovery, but that is why all the threads stress using GB-based kernels with custom recovery to do your flashing.
Lesson learned. At least you work for Sprint and can probably get things resolved with less hassle.

Yeah lesson learned. I just did the repair ticket on it and will have one on tuesday.
When the new one comes i will go straight to ICS build 31, and not even mess with anything else.
Its just amazing how we cant figure out a way to format/partition the currupted /data.

mrperez816 said:
Its just amazing how we cant figure out a way to format/partition the currupted /data.
Click to expand...
Click to collapse
It isn't a format issue.
The hardware emmc memory is damaged.
JTAG bitblasting would have overwrote everything if it was fixable. That is failing in this case.
So basically you are asking why we can't reformat a hard drive that crashed and make it work.

You are doing what's right. I had to flash the one click Odin 3 times to get out of a boot loop after trying to restore a GB ROM MD5 from a ICS kernel. Learned the hard way. But if you can get to DL mode, you can usually fix it. After the third time i was able to get into standard Android recovery and do a factory data reset. Then flashed the rom again and it booted right up. I was lucky though. Hope it works out.

PHONE WONT BOOT AFTER USING ALPHA 6 ICS(darchstar)
I was using this rom since it came out and haven't had 1 problem. after just using it normally it froze. did a battery pull and tried to reboot but was stuck on logo with the cm9 animation. so i went to recovery mode i had an error. i tried doing a format and froze. so i did another battery pull and now my phone wont boot into recovery or download mode. all i get is a blue led light. any ideas?

I'd like to think that putting BIGGER red text in the OP's might help but apparently not...
Sent from my SPH-D710 using xda premium

Oops, ignore me
Sent from my SPH-D710 using xda app-developers app

xDarkStarx27 said:
I was using this rom since it came out and haven't had 1 problem. after just using it normally it froze. did a battery pull and tried to reboot but was stuck on logo with the cm9 animation. so i went to recovery mode i had an error. i tried doing a format and froze. so i did another battery pull and now my phone wont boot into recovery or download mode. all i get is a blue led light. any ideas?
Click to expand...
Click to collapse
Your /data partition is dead. Formatting/ wiping from ICS recovery is VERY BAD, it makes bricks.... time to use insurance/TEP... sfhubs post on this page applies to you as well...
Sent from my SPH-D710 using xda app-developers app

[Q] Soft bricked my phone

So this is kind of a unique issue i'm having. I have the I-747 on AT&T and flashed AOKP rom (it was taking too long to get JB). It worked for about 3 days and then got stuck in the android boot screen (used the rom feature to get rid of the pink unicorns). after that, I booted into recovery and reset my phone, and it worked again for a few more days, then it wouldnt boot again (I dont believe I changed any settings between the boots). After this time, it wouldnt let me boot into recovery and would only boot to the android start screen and stop. I used odin to flash the stock rom, which only took me to the 2nd samsung boot screen and stopped (after the AT&T splash shows up). I looked online and saw someone say try CF-root using odin, tried that and it didnt help. Then tried using a custom kernel siyah s3, and now it will only show the initial samsung splash screen before turning off again. Any suggestions here? I figured I'd stop researching since i dont want to really mess up my phone worse than it already is

mrneilix said:
So this is kind of a unique issue i'm having. I have the I-747 on AT&T and flashed AOKP rom (it was taking too long to get JB). It worked for about 3 days and then got stuck in the android boot screen (used the rom feature to get rid of the pink unicorns). after that, I booted into recovery and reset my phone, and it worked again for a few more days, then it wouldnt boot again (I dont believe I changed any settings between the boots). After this time, it wouldnt let me boot into recovery and would only boot to the android start screen and stop. I used odin to flash the stock rom, which only took me to the 2nd samsung boot screen and stopped (after the AT&T splash shows up). I looked online and saw someone say try CF-root using odin, tried that and it didnt help. Then tried using a custom kernel siyah s3, and now it will only show the initial samsung splash screen before turning off again. Any suggestions here? I figured I'd stop researching since i dont want to really mess up my phone worse than it already is
Click to expand...
Click to collapse
I have a similar issue, someone please help

Your main issue now is that you flashed siyah. We don't have one. If you can get to download mode, you will want to flash back to stock.
Sent from my SGH-I747 using xda premium

As DeathSdoor said...flash stock.
Sent from my SAMSUNG-SGH-I747

d3athsd00r said:
Your main issue now is that you flashed siyah. We don't have one. If you can get to download mode, you will want to flash back to stock.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks guys! So I used odin to flash the stock boot loader and stock rom, but it is still hanging up on the 2nd samsung screen like it initially did (the one after the AT&T boot animation). Any other ideas on what could be the cause?

How long is the hang? Sure is just not the 1st initial boot of the new rom?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

blaker13 said:
How long is the hang? Sure is just not the 1st initial boot of the new rom?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
The first boot can take as long as 5 minutes sometimes. So, if you haven't waited that long, then try out some patience. Otherwise, try booting into recovery (stock now) and factory reset.
Sent from my SGH-I747 using xda premium

bump!
I have this same issue. I have restored to stock rom and it does the Samsung boot, then AT&T, then it goes to Samsung pulsating with a blue pulsating LED.
I have left it in that mode for at least 15 minutes and it never boots.
I can still get into download mode.
Thanks in advance for any help!

Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?

jethro650 said:
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
Click to expand...
Click to collapse
I let it run for 2 hours (left the house came back and i was still on. And phone wont boot into recovery at all ( i tried many times, but it just boots normally and skips recovery until it gets to the 2nd samsung screen, then stops there).
I dont know if this is relevant, but while the phone is off and plugged in, i can still see the battery meter and the Green LED (so i'm guessing it's still working, it just wont boot)

mrneilix said:
And phone wont boot into recovery at all ( i tried many times, but it just boots normally and skips recovery until it gets to the 2nd samsung screen, then stops there).
Click to expand...
Click to collapse
Same here!!!

jethro650 said:
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
Click to expand...
Click to collapse
As Jethro said clean everything and factory format in recovery. Your just not doing the buttons right to get in to recovery
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

blaker13 said:
As Jethro said clean everything and factory format in recovery. Your just not doing the buttons right to get in to recovery
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I went into recovery many times before, I'm definitely hitting the buttons right but it still wont go into recovery, it just tries booting like normal. I can go into download mode easily, but that's it.
jbizz, did you start getting this error after flashing AOKP rom also? trying to figure out what could have caused the issue in the first place

I'm not really skilled on these things, but I once had a similar issue with my phone not booting and had to end up using Kies to emergency restore it. Odin wouldn't recognize my phone but kies would.
Although I think my issue with odin may be stemming from my computers usb ports...
Sent from my SGH-I747 using XDA Premium HD app

I actually flashed a bad kernel and the phone wouldn't boot after that.
What is the proper way to boot into Stock Recovery?
Sent from my SAMSUNG-SGH-I777 using xda premium

Fixed it! What I did was go into Kies software and did a firmware upgrade instead of trying to flash from odin, then put it in download mode instead of recovery, but it still worked. Thanks for all the help, guys! guess it's time to move to a CM based rom?

mrneilix said:
Fixed it! What I did was go into Kies software and did a firmware upgrade instead of trying to flash from odin, then put it in download mode instead of recovery, but it still worked. Thanks for all the help, guys! guess it's time to move to a CM based rom?
Click to expand...
Click to collapse
Thats bad badassness! I will try that when I get home!
Sent from my SAMSUNG-SGH-I777 using xda premium

mrneilix:
Please give me step by step what you did! Kies is being a bastard!
Sent from my SAMSUNG-SGH-I777 using xda premium

jbizz said:
mrneilix:
Please give me step by step what you did! Kies is being a bastard!
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Sure, I'm doing this largely from memory since I mostly figured it out by throwing stuff at the wall to see what sticks.
Open Kies->tools->firmware upgrade and initialization->enter model name then serial number (they're behind the battery) -> put the phone in download mode and plug it in. it should take care of the rest.
Fair warning, this will fully wipe your phone, i lost all my pics (thank you google+'s instant upload or i'd be PISSED) and titanium backup (there goes my 3 stars on every level in angry birds and great scores in temple run), but at least you get a phone that can function as more than a paper weight, right?

mrneilix:
You're my new best friend and I don't even know you!!!
Thanks for the help, you're a legend!
Sent from my SAMSUNG-SGH-I747 using xda premium