Develop Bugs

Am I in brick city?

So i tried to update my AOKP with just using my phone. And after the reboot.. nothing happened. So i did a battery pull and now when I turn on my baby the led goes blue and stays there.. frozen. No access to recovery or download.
Black screen and blue led.. so yeah.
What I'm asking is.. there's no way of coming back?
Sent from my Old Evo using xda premium

Also.. I semi-bricked before and was able to fix via download mode.. so I know my way around.
Sent from my PC36100 using xda premium

When you updated AOKP you flashed the EL26 CWM kernel as per the instructions in all AOSP roms up until now? Both the recovery in AOKP 37 and the Zip for AOKP 39 (as far as I am aware) are not safe to flash in ICS Recovery.
BLoD is a sign that the bootloader is borked. Normally this is something fixable via JTAG. But it is also caused at Random by the Super Brick bug which can not be fixed. Sounds like you flashed not only an unsafe Zip but in an unsafe recovery and if you tell me you factory reset that would be even worse.
Our phone has a bug in its eMMC firmware which needs to be patched. All of the former ICS leaks have had kernels that can trigger it and last i checked only the Nighlies for CM9 have a safe updater binary used in conjunction with a made safe recovery are generally safe to flash from ICS. Which is exactly why the threads tell you to use the EL26 CWM kernel which if mobile can be flashed via mobile odin. Failure to do so will eventually at random trigger the bug.

Blue LED and not able to get phone into Odin mode = Hard Brick

another one bites the dust......i just don't know how the directions could be any more clear on flashing ICS ROM's. Maybe we need a sticky in every forum in bold letters that says:
"READ ME BEFORE FLASHING!"

I read the warnings and all that jazz. It was just a bad download thanks to the 4G. Mistakes happen. Relax @ above poster.
Yeah I went about it the right way. I have insurance with Sprint, hopefully I'll get lucky and get a new phone.
Thanks to the rest that answered.
Sent from my PC36100 using xda premium

I agree with Rican Bomba... Not everyone is a Android hacking Guru. We are all trying to learn here. I bricked my phone and i did follow QBking77's instructions (Who i believe to be the best at explaining things thoroughly in his videos) yet, there are so many post that aren't clear. I had force closes like crazy on AOKP and before i found the one poster that said don't wipe in ICS... I had done it and lights out R.I.P. First E4GT. I have flashed way too many times to count without incident. Some posters put more info on how not to brick than others. I followed QBking's method to a tee and something was still wrong... I don't blame him (He makes things crystal clear and is great at what he does), things happened and that was that. I learned something from a poster who was very clear and i won't make the mistake again (not to mention I'm leaving AOKP alone lol). Take it easy on these guys, they will learn soon with a little friendly direction

Rican Bx Bomba said:
I read the warnings and all that jazz. It was just a bad download thanks to the 4G. Mistakes happen. Relax @ above poster.
Yeah I went about it the right way. I have insurance with Sprint, hopefully I'll get lucky and get a new phone.
Thanks to the rest that answered.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Never never never never download a ROM through Mobile Network... and if you do, make sure you check the md5. I think almost all of my 4G ROM downloads have been corrupt

iniz94 said:
Never never never never download a ROM through Mobile Network... and if you do, make sure you check the md5. I think almost all of my 4G ROM downloads have been corrupt
Click to expand...
Click to collapse
Flashaholic lol no computer access at my job and at home at the moment.
Sent from my PC36100 using xda premium

[Q] Sprint Galaxy S III Rooted/Installed ROM... Now won't power on. Help!

Hi everyone. I'm new to the forum and I'm looking for a little help today.
I rooted my new Sprint Galaxy S III using Odin3-v3.04, and CWM_SuperUser_v3.0.7. Afterwards I rebooted and all was good.
I then downloaded I9300_Omega_v6.0_XXALF6 ROM and loaded on my phone and rebooted into recovery to install the ROM. I went through the install process, selected remove bloatware and installed. When finished I checked the reboot phone and clicked finish. The phone turned off and didn't ever turn back on.
I have pulled the battery and tried to power on using recovery, download mode and just power but nothing works.
Anyone have any idea what I can do?
Thank you for your time and help.

alexanderd said:
Hi everyone. I'm new to the forum and I'm looking for a little help today.
I rooted my new Sprint Galaxy S III using Odin3-v3.04, and CWM_SuperUser_v3.0.7. Afterwards I rebooted and all was good.
I then downloaded I9300_Omega_v6.0_XXALF6 ROM and loaded on my phone and rebooted into recovery to install the ROM. I went through the install process, selected remove bloatware and installed. When finished I checked the reboot phone and clicked finish. The phone turned off and didn't ever turn back on.
I have pulled the battery and tried to power on using recovery, download mode and just power but nothing works.
Anyone have any idea what I can do?
Thank you for your time and help.
Click to expand...
Click to collapse
development area has a thread for that:
http://forum.xda-developers.com/showthread.php?t=1727171
ONLY use ROMs that you'll find here in these threads not the I9300; that s a different phone from ours.

Thanks I'll check there.

Honestly I was waiting for this to happen gid luck restoring it phone
Sent from my SPH-L710 using XDA

But seriously I hope you learned your lesson and will read and hope you get your phone fixed or replaced
Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2

Epix4G said:
But seriously I hope you learned your lesson and will read and hope you get your phone fixed or replaced
Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2
Click to expand...
Click to collapse
Hopefully this fail helps us all back from a potential brick. We live, flash and learn.
Sent from my SPH-D700 using xda premium

New phone on the way!
I was able to get a replacement sent from Sprint. Had to go to a corporate store and have a tech look at the phone and they agreed it was toast...
Luckily they didn't know it was due to my failed attempt to load an unsupported ROM.
Lesson learned... new phone should be in by the end of the week.
I'll be waiting for a supported ROM this time.

alexanderd said:
I was able to get a replacement sent from Sprint. Had to go to a corporate store and have a tech look at the phone and they agreed it was toast...
Luckily they didn't know it was due to my failed attempt to load an unsupported ROM.
Lesson learned... new phone should be in by the end of the week.
I'll be waiting for a supported ROM this time.
Click to expand...
Click to collapse
No wonder our insurance deductibles keep going up...

bizdady said:
No wonder our insurance deductibles keep going up...
Click to expand...
Click to collapse
+1
Still sucks for op
Sent from my SPH-L710 using Tapatalk 2

matrixzone5 said:
Honestly I was waiting for this to happen gid luck restoring it phone
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
Oh man tell me about it, I almost stupidly went on to the CM9 nightlies and downloaded the I9300 version before I thought to myself, "well wait a minute, that's not my model number!"
Duh, shoulda had a V8.

I didnt install a GSM rom but still managed to brick somehow. Didnt touch any system files or do anything to where i should be bricked either. Any idea when a full stock Odin package will be made? My phone has been bricked for almost 2 days now
Edit: i started a tread here a few days ago -> http://forum.xda-developers.com/showthread.php?t=1731416 if anyone cares to look or has any advice for me
Thanks

pizzlewizzle said:
I didnt install a GSM rom but still managed to brick somehow. Didnt touch any system files or do anything to where i should be bricked either. Any idea when a full stock Odin package will be made? My phone has been bricked for almost 2 days now
Edit: i started a tread here a few days ago -> http://forum.xda-developers.com/showthread.php?t=1731416 if anyone cares to look or has any advice for me
Thanks
Click to expand...
Click to collapse
What have you tried so far? Have you tried reflashing cwm recovery in Odin?

I did the same thing that the OP said, flashed that omega rom and now my phone wont turn on either.
I was going to try the jig method

taygutta said:
I did the same thing that the OP said, flashed that omega rom and now my phone wont turn on either.
I was going to try the jig method
Click to expand...
Click to collapse
Have you tried mskip's fix??
http://forum.xda-developers.com/showthread.php?t=1727171

bizdady said:
Have you tried mskip's fix??
http://forum.xda-developers.com/showthread.php?t=1727171
Click to expand...
Click to collapse
I want to do this but I somehow need to get the phone on. The buttons dont work.

Any luck?
My phone got stuck booting, so I tried to install the omega rom. The install worked well, and I clicked "reboot." Now the phone won't turn on. I can't get to ODIN or recovery anymore.
Did you guys find any fixes?

brickeds3 said:
My phone got stuck booting, so I tried to install the omega rom. The install worked well, and I clicked "reboot." Now the phone won't turn on. I can't get to ODIN or recovery anymore.
Did you guys find any fixes?
Click to expand...
Click to collapse
What happened is that you flashed a rom that was meant for the international version of the S3 and your on the US version. The only fix I have found is to send it to mobiletechvideos.com. I did and they say they can fix it and maybe save my data I have on it ( I just sent it in)
My fingers are crossed for the data recovery but as far as the phone I am going to send it for a exchange anyway.

Welp, I'm sad to say I just did the same thing too. Should have read. I'm a stinkin noob at this. I installed the I9300 version on a US version phone. Has there been any more development on this? Is the hardware fried, or is there a fix through that mobiletechvideos.com that was mentioned? What was the outcome of that, Taygutta, if you don't mind me re-bringing back up a potentially painful topic?? This thread made me a little sick, since it's my brother's new phone (someone else that knew what they were doing rooted it for him but he didn't like the rom, so I thought I would help him find a few other options to try flashing.)
Anyway, any confirmation that I'm buying my brother a new phone (so I can emotionally prepare for the purchase) or are there some other options?

There's one more thing you can try. There's a little device called a USB Jig. It was made for SGS-2 to clear the yellow triangle and reset flash counts in ODIN mode. It also puts your phone in ODIN mode by simply plugging it into the USB port of a powered down phone. Once in ODIN mode, you can reflash a stock ROM, recovery, etc. You can buy these for around $20 or less on the web.
If this does not work, I'm afraid nothing will.
Good luck.

6uPMAH said:
There's one more thing you can try. There's a little device called a USB Jig. It was made for SGS-2 to clear the yellow triangle and reset flash counts in ODIN mode. It also puts your phone in ODIN mode by simply plugging it into the USB port of a powered down phone. Once in ODIN mode, you can reflash a stock ROM, recovery, etc. You can buy these for around $20 or less on the web.
If this does not work, I'm afraid nothing will.
Good luck.
Click to expand...
Click to collapse
Somewhere in the thread an answer exists. You are not the first to do this.
I think the jig is the best way.
Sent from my SPH-L710 using Tapatalk 2

Help! phone won't turn on (t959d koodo)

Hi,
I just got the phone and flashed a custom recovery. I flashed a new rom (liquidsmooth) and it looked like it was successful. I selected reboot and the screen shut off. Now, It won't turn on. It's possible that the battery died but shouldn't it turn on again once I plug in the usb cable? Is it possible to brick the device from cwm?
thanks

Dear lord I hope that's a typo because this is the t989(d) forums. If it is a typo and you're using a t989 then you probably need to wipe cache/dalvik.
Sent from my SAMSUNG-SGH-T989

As Mr. Mintharis said... I'm hoping as well that you had a typo and you didnt flash a T989 (GALAXY S2 TMobile) rom on a (GALAXY S) device. If so your probably hard bricked. If that was a typo and you did flash a rom and it wont turn on then there may be a few problems that are solvable. I got a few questions.
1. DId you do a factory reset before installing? Did you wipe system?
2. Can you get into CWM?
3. Can you get into Download Mode?
If you cant get into download mode, recovery, or get the phone to boot then you are in serious trouble because the phone is a a fancy paper weight. If you can however, you could try doing a full reset on all the settings and deleting cache/dalvik and then reflashing and trying again. However you may be in luck since you said you just got the phone. I'm assuming you got it from your carrier (I'm guessing its T-Mobile, idk any other carriers for this device) and they will replace a broken device (that does not have extensive physical damage or water damage) within 20 days of purchase date. Since your phone is hard bricked they will do it completely for free with no charge (usually... if they do.. it will be about 5$) and then you're good. They will overnight a phone to you and you just send your old one back when you get it (MAKE SURE TO ASK FOR DIRECTIONS ON HOW TO PROPERLY SEND IT BACK!).
Sorry for the long post but wanted to be through and give you alot of answers in 1 time so we dont drag this post out.

That's my mistake, it was supposed to read t989d.
1) I did do a factory resets
2) & 3) I can't turn on the phone or get into download mode
I bought it from koodo (carrier in Canada) yesterday. I'm going to try to exchange it today; hopefully they'll do it. For future references, is there a specific way I should be flashing? I used to have a t959, the t-mobile vibrant, and never had any issues with cwm because it never touched download mode. Anyways, thanks for the replies.
Edit: I did flash using odin which hung a couple of times. Regardless, i eventually got it back to original condition by flashing the custom recovery (by odin with green pass) and doing a nandroid backup. The bad odin flashes should have been negated when I did nandroid backup, no?

You said you had the problems after you flashed liquidsmooth? Exactly which file did you download and flash from the site?
Sent from my SGH-T989 using xda premium

Ok, just figured it out. I flashed wrong version of liquid smooth. The link in their thread goes to their facebook page and I clicked on the first link like an idiot. I got it exchanged a few minutes ago so all's well that ends well. Thanks all for the replies.
Lesson of the day: Don't be stupid.

mani_is_ms said:
Ok, just figured it out. I flashed wrong version of liquid smooth. The link in their thread goes to their facebook page and I clicked on the first link like an idiot. I got it exchanged a few minutes ago so all's well that ends well. Thanks all for the replies.
Lesson of the day: Don't be stupid.
Click to expand...
Click to collapse
Read read read.. If you are not 100% sure what you are doing just ask someone.. Sometimes you will get flamed for it but it's better than getting a bricked phone lol and you'll most likely get an answer..
I'm glad you got it replaced
Sent from my SGH-T989 using xda premium

For all the flashers here for the T989

The whole process is pretty simple on what I have done. I will explain my situation here and my question that has got be baffled.
So it all started about two weeks ago, where I was flashing LiquidSmooth on my phone. I had a Touch-type CWM. It isn't mega old but it's pretty old for CWM, I haven't updated in a while (as i've seen there are updates to recent ones).
Anywho, I did a complete wipe, used the darkside wipe, alongside with the darkside cache wipe.
I think this was my fault, so please correct me anyone if I am wrong here. I accidentally hit "reboot phone" instead of "reboot bootloader"
I got a permabrick from this whole ordeal. It was a permabrick because It said QHSUSB_DLOAD in the device manager, looking this up further confirmed my reasoning. I didn't want to jtag because that invovles removing the phone to pieces and soldering on wires etc. etc.
So I resorted to send it out to Samsung.
All is well when it came back. I made sure this time the whole phone was setup properly.
So I use Odin install for CWM and SU was installed via CWM. I install an older version of CWM (non-touch, i believe 1st revision as i've posted in one of the threads).
I kept stock ROM, everything was working okay and suddenly, KERPLUNK, it went back into permanent brick after I deleted cache partition, dalvik cache, and battery cache wipe. I didn't do fix permissions or anything, just hit reboot afterwards.
This is a super head scratcher here..... Anyone know where I went wrong?
Any insight here is greatly appreciated! :good:
P.S. I am now sending in my phone TWICE to Samsung for repairs.

If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it

LoopDoGG79 said:
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
Click to expand...
Click to collapse
I finally jumped in the water and flashed twrp! Yay!
Sent from my SAMSUNG-SGH-T989 using xda premium

All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium

rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
great call on that I had to educate a few users that the d2tmo is not for our phone but indeed the S3. Good catch on your part and it sounds like user error as well

LoopDoGG79 said:
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
Click to expand...
Click to collapse
Could you please educate me with a link referring to what TWRP is? Sorry, i'm still fairly new to the scene and all i've ever been educated upon is CWM.
suaverc118 said:
I finally jumped in the water and flashed twrp! Yay!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Nice! What is TWRP and how is it like?
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I've flashed the hercules ROM. I know this for sure because Liquidsmooth was working, it was extremely glitchy (playing games gave me pixelated actions sometimes, and using something like gameCIH/Game Guardian was unworkable). So i decided to ditch it and was getting ready to flash Jedi Mind Trick.
After the whole hard bricking ordeal, I decided to stick to stock rom, and even on that, I just flashed CWM and SU ONLY. Rebooted, and deleted the cache's (like i've posted to you) with absolutely no success. It baffled me that I bricked the phone AGAIN too!
playya said:
great call on that I had to educate a few users that the d2tmo is not for our phone but indeed the S3. Good catch on your part and it sounds like user error as well
Click to expand...
Click to collapse
Yes..... there is something wrong, i feel it is a user error also, but i'm very unsure where to even start
Once again, all of your insight is well appreciated! I just do not want to hardbrick my phone AGAIN and have to send it to Samsung. I am not allowed to even think of a replacement because this was a b-day present a year or two ago from my fiance.

You say that it is bricked again. Do you mean by that, that you cannot get into recovery?
Sent from my SAMSUNG-SGH-T989 using xda premium

XxGoKoUxX said:
Could you please educate me with a link referring to what TWRP is? Sorry, i'm still fairly new to the scene and all i've ever been educated upon is CWM.
Nice! What is TWRP and how is it like?
I've flashed the hercules ROM. I know this for sure because Liquidsmooth was working, it was extremely glitchy (playing games gave me pixelated actions sometimes, and using something like gameCIH/Game Guardian was unworkable). So i decided to ditch it and was getting ready to flash Jedi Mind Trick.
After the whole hard bricking ordeal, I decided to stick to stock rom, and even on that, I just flashed CWM and SU ONLY. Rebooted, and deleted the cache's (like i've posted to you) with absolutely no success. It baffled me that I bricked the phone AGAIN too!
Yes..... there is something wrong, i feel it is a user error also, but i'm very unsure where to even start
Once again, all of your insight is well appreciated! I just do not want to hardbrick my phone AGAIN and have to send it to Samsung. I am not allowed to even think of a replacement because this was a b-day present a year or two ago from my fiance.
Click to expand...
Click to collapse
Flash this in recovery, reboot recovery, and you will have TWRP!!
TWRP 2.3.1.1

DM_Sledge said:
You say that it is bricked again. Do you mean by that, that you cannot get into recovery?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yes, it is perma-bricked, meaning the only method of fixing the brick is jtagg'ing
Upon plugging it into device manager, I get the prompt "QHSUSB_DLOAD" and phone doesn't even boot on no matter what combinations I make.
LoopDoGG79 said:
Flash this in recovery, reboot recovery, and you will have TWRP!!
TWRP 2.3.1.1
Click to expand...
Click to collapse
Thank you LoopDo, I will do this after I get my phone home again.

I have this phone, and none of the steps you listed would brick the device. Even with no ROM on the phone, you should still be able to get into recovery.
Is there something you aren't telling us?
Sent from my Galaxy Nexus using xda premium

Nope, wouldn't be a reason why I would lie because then the problem will never be resolved.... I'm kind of nervous on reflashing ONE more time after the phone comes home again....
The phone has been fixed once AGAIN, and it is in the process of being shipped back to me.
Phone will be home Wednesday and I will give it ONE more try
Wish me luck!
P.S. my PC has been glitchy lately, so that MAY or MAY NOT contribute to the permabrick, then again the brick doesn't happen until I flash stuff via CWM.
P.S.S. I've since re-installed Win 7 again, it hasn't been glitchy since

XxGoKoUxX said:
Nope, wouldn't be a reason why I would lie because then the problem will never be resolved.... I'm kind of nervous on reflashing ONE more time after the phone comes home again....
The phone has been fixed once AGAIN, and it is in the process of being shipped back to me.
Phone will be home Wednesday and I will give it ONE more try
Wish me luck!
P.S. my PC has been glitchy lately, so that MAY or MAY NOT contribute to the permabrick, then again the brick doesn't happen until I flash stuff via CWM.
P.S.S. I've since re-installed Win 7 again, it hasn't been glitchy since
Click to expand...
Click to collapse
You most likely flashed the Wrong Liquidsmooth ROM (incompatible Kernel), and it hard bricked the phone. It happened to me the same way, and I had to send it in for JTAG.

I have bricked my phone installing the Liquidsmooth ROM too. I downloaded the wrong ROM, though. The thread should have a big ****in warning to double check the ROM you are about to download, otherwise your phone is a toast. There were more people who bricked their phones by installing the Liquidsmooth.
Well, I got it back from the warranty and the phone looks good. Installed that Liquidsmooth again and played for a day. Tried other JB ROMs. Most of them are OK in terms of battery life and smoothness, but there is something wrong with the signal. People always say my voice isn't clear. I got tired of all this BS and testing new ROMs and went to back to ICS and won't look back, not anytime.
Don't use darkside scripts, btw. You don't need that anymore.

I'd like to say thank you for everyone's patience. All of your insight is more than helpful!
DroidDonX said:
You most likely flashed the Wrong Liquidsmooth ROM (incompatible Kernel), and it hard bricked the phone. It happened to me the same way, and I had to send it in for JTAG.
Click to expand...
Click to collapse
I might have, but the one i downloaded (which is still on the phone's memory card) is a hercules ROM. Either way on my second try there was a hard brick also, in return of which I had to resend it in. The second try was just simply: Odin---->CWM---->Root---->SU---->wipe cache partition+fix permissions+wipe dalvik cache via CWM (not the super scripts).
cipsaz said:
I have bricked my phone installing the Liquidsmooth ROM too. I downloaded the wrong ROM, though. The thread should have a big ****in warning to double check the ROM you are about to download, otherwise your phone is a toast. There were more people who bricked their phones by installing the Liquidsmooth.
Well, I got it back from the warranty and the phone looks good. Installed that Liquidsmooth again and played for a day. Tried other JB ROMs. Most of them are OK in terms of battery life and smoothness, but there is something wrong with the signal. People always say my voice isn't clear. I got tired of all this BS and testing new ROMs and went to back to ICS and won't look back, not anytime.
Don't use darkside scripts, btw. You don't need that anymore.
Click to expand...
Click to collapse
Thanks again for your insight I think i'm done with flashing for a little bit for now.... I kind of want as factory of a JB Rom as possible. :good:
If anyone has any idea where I can get that, please let me know as my Stock ICS is a bit laggy at times, with the facial recognition system, it lags even worse!

rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
that just happened to me today with liquid smooth. i had to unroot, flash stock, and start over. im pretty sure i got it from goo.im under hercules. unfortunate mislabeling? oh yeah, and if your phone shows anything other than nothing, youre not hard bricked. thats why its called Hercules, i think. ive been soft bricked so many times from dumb **** like. ****ing with the governors and all that **** cm gives you the option to do when there aint even a 1080p camera that works fully = / lol <3 Cm I Love Yew!! But yeah, odin will set you free!!!

[Q] I747 Won't boot, even into recovery

Well, I screwed up. I went to install Omega ROM from my rooted Galaxy SIII ATT. I was lazy, and downloaded the first thing I found that looked like a flashable zip, but it turned out to be for the international version. The AROMA installer worked great. It finished, and I pressed the reboot button at the end of the installer. The screen immediately went black. I figured it was no big deal because I had up-to-date backups on my external SD card of every ROM I had flashed. I tried to boot into recovery and restore a backup, but the phone doesn't even start to turn on. The screen stays totally black.
I tried a firmware recovery with Kies, a wipe with ODIN, and a wipe with adb, but none worked because I can't get the device in recovery or download mode.
Like I said, I have all my data backed up, so I have no problem with wiping my phone or getting rid of root and re-rooting and restoring. However, I would like to avoid driving to the nearest AT&T store or shipping my phone off to Samsung because I'm pretty sure my warranty is void.
Sorry for the lengthy post!
Samsung Galaxy SIII AT&T White 16GB w/ 32GB class 10 microSD

LukeNookem said:
Well, I screwed up. I went to install Omega ROM from my rooted Galaxy SIII ATT. I was lazy, and downloaded the first thing I found that looked like a flashable zip, but it turned out to be for the international version. The AROMA installer worked great. It finished, and I pressed the reboot button at the end of the installer. The screen immediately went black. I figured it was no big deal because I had up-to-date backups on my external SD card of every ROM I had flashed. I tried to boot into recovery and restore a backup, but the phone doesn't even start to turn on. The screen stays totally black.
I tried a firmware recovery with Kies, a wipe with ODIN, and a wipe with adb, but none worked because I can't get the device in recovery or download mode.
Like I said, I have all my data backed up, so I have no problem with wiping my phone or getting rid of root and re-rooting and restoring. However, I would like to avoid driving to the nearest AT&T store or shipping my phone off to Samsung because I'm pretty sure my warranty is void.
Sorry for the lengthy post!
Samsung Galaxy SIII AT&T White 16GB w/ 32GB class 10 microSD
Click to expand...
Click to collapse
Sounds like you hard bricked it. You can try buying a jig but I guarantee you need to ship it off for jtag service
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Yeah, sorry to bring it to you, but flashing a different firmware on your device has probably hard bricked it. Maybe try anything you can to reach download mode and ODIN stock firmware. If that fails, try to find a way to get it unbricked, maybe mobiletechvideos, as I've heard good reviews about them. Wish you the best of luck!
Sent from my Galaxy S3

TheKucho said:
Yeah, sorry to bring it to you, but flashing a different firmware on your device has probably hard bricked it. Maybe try anything you can to reach download mode and ODIN stock firmware. If that fails, try to find a way to get it unbricked, maybe mobiletechvideos, as I've heard good reviews about them. Wish you the best of luck!
Sent from my Galaxy S3
Click to expand...
Click to collapse
Thanks for the reply. I was kinda afraid of this. Do you think the Samsung Galaxy S Download Mode JIG off of mobiletechvideos could help? Or would you just recommend bringing it in to get fixed? Incidentally, should I bring it in to the AT&T store or send it off to Samsung? I hear custom ROMs and the like don't void your Samsung warranty, only your AT&T one.
Thanks!

LukeNookem said:
Thanks for the reply. I was kinda afraid of this. Do you think the Samsung Galaxy S Download Mode JIG off of mobiletechvideos could help? Or would you just recommend bringing it in to get fixed? Incidentally, should I bring it in to the AT&T store or send it off to Samsung? I hear custom ROMs and the like don't void your Samsung warranty, only your AT&T one.
Thanks!
Click to expand...
Click to collapse
send it to MobileTechVideos and they will fix it like its nothing........ just BE FULLY SOBER (yuknowhatimean) before flashing anything
synergy ROM 4.1.2 WITH Ziggy Kernel using ATT Galaxy S3
took my Skyrocket to them and they did it like it was nothing

LukeNookem said:
Thanks for the reply. I was kinda afraid of this. Do you think the Samsung Galaxy S Download Mode JIG off of mobiletechvideos could help? Or would you just recommend bringing it in to get fixed? Incidentally, should I bring it in to the AT&T store or send it off to Samsung? I hear custom ROMs and the like don't void your Samsung warranty, only your AT&T one.
Thanks!
Click to expand...
Click to collapse
If your phone is truely hard bricked, a usb jib will not work. I hard bricked mine when a kernel flash went wrong. I sent it in for jtag repair, it only cost me 30 bucks or so to send it in. I sent it in to this person http://www.ebay.com/itm/281117528352?ssPageName=STRK:MEWAX:IT&_trksid=p3984.m1423.l2649 mobiletechvideos is a little steep IMO at 60 bucks for jtag.

Well, you guys are great. I took it in to my local AT&T Service Center and they fixed it in 5 minutes for free, even though my warranty was void. I gotta say, I was pretty surprised with the awesome service.
Thanks a million!

LukeNookem said:
Well, you guys are great. I took it in to my local AT&T Service Center and they fixed it in 5 minutes for free, even though my warranty was void. I gotta say, I was pretty surprised with the awesome service.
Thanks a million!
Click to expand...
Click to collapse
good for yu, and lucky they did it without asking unecessary stupid questions cuz you didnt have a warranty
anywz lay off the rooting and try stock for a while, its stable, not as fast as custom Roms, crazy battery life (depends on how yu, use it but nothing to worry abut stock has the best battery performance), samsung killa features and its completely safe and better than custom roms that might sht your phone after a while...........:silly:
Synergy Rom 4.1.2 w/ Ziggy kernel using ATT Galaxy S3