Database Info

Having Withdrawals Already!!!

Ok so today I mow my yard and I plug in my Thunderbolt in to the USB charger on my PC when I come inside my phone is bootlooping. So I think ok whatever I will flash one of the many backup's I made.
So I pull the battery and boot into the bootloader, then when I go into recovery after about 2 seconds the phone powers off and starts bootlooping again??? Ok that's a first for me and I have been flashing and rooting since launch day of the OG Droid, (ok, ok not since the first day but like a month later). So I pull the battery again this time for 30 minutes because I read someone else had something like this happen yesterday. When I put the battery back in same thing! Now I pull the battery for 4 hours...same outcome.
Now I'm thinking RUU time so I grab the stock RUU pull the SD card from my Thunderbolt pop it in my Incredible load the RUU renamed to PG05IMG.zip and put it back in the Thunderbolt. Load the bootloader and flash the RUU. Reboot after it's done and would you believe it...the same thing! the phone won't load past the splash screen before rebooting.
I forgot to mention before trying all this I tried using adb to reboot into recovery and I kept getting "error: device not found" and I know how to use adb.
It's only been about 9 hours since I've been able to use my 2.3.4 GingerBread with parts of 3.0 Sense Thunderbolt and I already having withdrawals how am I going to make the next 2 to 3 weeks while it's being repaired???
Ok end rant...

Go to verizon, swap it for a new one. Warranty case for sure.

bilbobrian said:
Go to verizon, swap it for a new one. Warranty case for sure.
Click to expand...
Click to collapse
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.

I'm loosing faith in the Thunderbolt. I really feel we are all just a bunch of beta testers.

bunklung said:
I'm loosing faith in the Thunderbolt. I really feel we are all just a bunch of beta testers.
Click to expand...
Click to collapse
Huh? Off topic and makes no sense.
//Tap'd on my TBolt while grounded\\

bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
I understand your rooted but if it cant boot up then there is a problem. Just go to verizon and show them. Once they see it cant boot properly they will exchange it or overnight one to you.
I apologize if Im missing something..

bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
You may get away with getting it swapped through warranty. But I can't promise you it won't come back at you. Someone may have a solution for you though. Wouldn't give up yet. Sorry I don't.
//Tap'd on my TBolt while grounded\\

chkmate said:
Huh? Off topic and makes no sense.
//Tap'd on my TBolt while grounded\\
Click to expand...
Click to collapse
*Shrug*
He has a problem, I do too. We both own Thunderbolts. Maybe I should have been more specific.
To each his own. The end.

bunklung said:
*Shrug*
He has a problem, I do too. We both own Thunderbolts. Maybe I should have been more specific.
To each his own. The end.
Click to expand...
Click to collapse
Well then relate your problem with his. Just saying "your losing faith in Thunderbolt" tells me nothing. Don't mean to sound like an a$$, just saying. When I read your first comment I got nothing from it.
That being said...I haven't been a Bolt owner for long, but it does seem like a strange issue. You would think flashing a radio or backup would resolve the issue. But hasn't.
//Tap'd on my TBolt while grounded\\

Definitely sounds like a Warranty Issue. I'd try to get it exchanged if no one can come up for a solution to the problem.

I had a G1 back in the day that had some odd problem and I was rooted, Tmo looked at it and wouldn't touch it. So, I called HTC. I told them that I purchased the phone off Craigslist so Tmo couldn't help me, and asked how the warranty works on their end. They said that since the production of the phone started less than a year ago, they knew it was still eligible for warranty even without a receipt. There would be a triage fee if it was found to be a non-warranty issue, and it was something like $40 including the shipping back. I acted dumb when they asked if it was rooted...asked them what that meant? LOL. Sent it in, they fixed it and sent it back to me, no charge. Fast too. I was very happy and that is why I have stuck with HTC since then. It may or may not work for you, but it was painless for me.

bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
Such chivalry is rare in these days.
Applaud. Best of luck!
Sent from my ADR6400L using Tapatalk

bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
They don't care. Take my word for it. If it never boots they won't care.

I'm actually having this exact same issue. Has anyone found a solution yet or is the only solution to have the phone replaced?

Wow. I thought for sure hbooting the unsigned stock RUU would fix this. How about hbooting a signed ruu? It wouldn't hurt at this point.
Also make sure when you renamed the pgimg05. Zip that there was nothing at the end of the extention. I've heard some people say that windows has been known not to show that full file extension correctly.

raider3bravo said:
Wow. I thought for sure hbooting the unsigned stock RUU would fix this. How about hbooting a signed ruu? It wouldn't hurt at this point.
Also make sure when you renamed the pgimg05. Zip that there was nothing at the end of the extention. I've heard some people say that windows has been known not to show that full file extension correctly.
Click to expand...
Click to collapse
I thought hbooting the stock RUU would fix it as well, and yep it was named correctly. It's funny because it would stay on the hboot screen as long as I let it with no issue what so ever but within 2 seconds of going into recovery it would reboot.
I went back to Best Buy today as that is where I bought it to see how much they would charge to ship it out to be fixed. The mobile manager remembered me because I was 1st on the pre-order list. (I'm sure we all remember the train wreck the Best Buy pre-orders became) So any way he really went out of his way to help me. He said he has had 3 other Thunderbolts brought in for the same issue. He was able to send my phone in under their Black Tie program.
I told him I rooted the phone and was willing to pay for the repairs but he said he was pretty sure that the other 3 phones were not rooted. He said that he knew FOR SURE that at least one of the phones was not rooted because the lady that owned it did not have any branches in her family tree, (his words not mine). Since he has seen it 3 times he was not charging me. He only asked that I had the stock hboot on the phone. I had already flashed that in my attempt to get it running.

I'm with cstrife, I managed to destroy my tab with a mix of flashing and charging via outlets in India. It bootlooped for a while then just kind of gave up and began to display a strange download screen when I plugged it in to charge. I brought it to VZW and played stupid, I told them I woke up and it had this weird screen... I had a brand new one at my door the next morning and haven't heard a word from them... It probably just costs more to check it out deep enough to find out its rooted than it does to just give you a refurbished one, gut swap yours, and then send to someone else as a refurbished one...
Sent from my SCH-I800 using XDA App

Had this happen to me and just pulled my SD card, rebooted and it was fine. Not saying it will work for u but give it a shot.
Sent from my ADR6400L using XDA App

bp328i said:
I thought hbooting the stock RUU would fix it as well, and yep it was named correctly. It's funny because it would stay on the hboot screen as long as I let it with no issue what so ever but within 2 seconds of going into recovery it would reboot.
I went back to Best Buy today as that is where I bought it to see how much they would charge to ship it out to be fixed. The mobile manager remembered me because I was 1st on the pre-order list. (I'm sure we all remember the train wreck the Best Buy pre-orders became) So any way he really went out of his way to help me. He said he has had 3 other Thunderbolts brought in for the same issue. He was able to send my phone in under their Black Tie program.
I told him I rooted the phone and was willing to pay for the repairs but he said he was pretty sure that the other 3 phones were not rooted. He said that he knew FOR SURE that at least one of the phones was not rooted because the lady that owned it did not have any branches in her family tree, (his words not mine). Since he has seen it 3 times he was not charging me. He only asked that I had the stock hboot on the phone. I had already flashed that in my attempt to get it running.
Click to expand...
Click to collapse
Honesty turned out to be the best policy in this case. Congrats.
Sent from my ADR6400L using Tapatalk

MrHawaii said:
Honesty turned out to be the best policy in this case. Congrats.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Thanks, now I just have to wait 2 to 3 weeks to get it back. What to do with all that time!!!

[Q] Anyone experience earpiece issue?

On my skyrocket from AT&T I was having an issue with the battery indicator getting stuck at 100%.
I updated the phone to the latest OTA update, no root or anything on this phone, all completely stock.
After update phone info is as follows:
Model Number: SAMSUNG-SGH-I727
Android Version: 2.3.6
Baseband Version: I727UCLA3
Kernel Version: 2.6.35.11
Build Number: GINGERBREAD.UCLA3
After I did the update the battery indicator has not come back (awesome right?, not so fast.)
Now I have an issue with call quality, my best attempt at describing it is like the ear piece sounds blown out, it kind of has a vibrate when people talk, Its not just one persons phone either, its any call I get/place.
I'm not sure if I should try a factory reset, revert back to 2.3.5?, Go to AT&T for a new one.
If anyone has had this issue and knows how to fix it please post. I apologize ahead of time if this is already posted somewhere, I looked for a few hours on google and couldn't find it anywhere. Also even if you don't know how to fix it, could you please post if your having the same issue so I know I'm not alone and have some ammo if I do have to go to AT&T.

Visit AT&T Store
Of course I'm 4 days outside my 30 day trial period so I would have to get a replacement mailed to me if I can't get it to work.
Lady I spoke with there was very nice (as always) but didn't have any idea what to do (as always) and advised I try and factory reset it. What the hell, mine as well.
Also got her to tell me that if I root and custom rom it and it still dosn't work I can still RMA it. So she went against what all their documentation says so now I can do what I want
Figure ill factory reset first, if that dosn't work I'll ODIN it back to the original 2.3.5 if possible.
Ill keep updating this thread though incase anyone else has a similar issue.

albeemichael said:
Of course I'm 4 days outside my 30 day trial period so I would have to get a replacement mailed to me if I can't get it to work.
Lady I spoke with there was very nice (as always) but didn't have any idea what to do (as always) and advised I try and factory reset it. What the hell, mine as well.
Also got her to tell me that if I root and custom rom it and it still dosn't work I can still RMA it. So she went against what all their documentation says so now I can do what I want
Figure ill factory reset first, if that dosn't work I'll ODIN it back to the original 2.3.5 if possible.
Ill keep updating this thread though incase anyone else has a similar issue.
Click to expand...
Click to collapse
Haha, just because she said that doesn't mean anything. Read the contract, that trumps what some lady says. Anyways, you can flash back to stock and warranty it, so it doesn't matter what anyone says

Absolutely Right
xcrazydx said:
Haha, just because she said that doesn't mean anything. Read the contract, that trumps what some lady says. Anyways, you can flash back to stock and warranty it, so it doesn't matter what anyone says
Click to expand...
Click to collapse
As the title says you absolutely correct. Lady probably didn't have a clue lol.
I called their warranty support line and am going to drive to their wallingford exchange place.
I was talking with my father before I called and figured if I went in and said get a manager, and told him/her if I don't have a new phone in my hand in 10 minutes, your losing a customer in 10 minutes, I bet I would get my phone
Regardless I'm getting a replacement, I did try the factory reset, didn't work. Also tried downgrading the device to 2.3.5 stock, and this also did not work.
Think its hardware, the static is only on the ear piece. Speaker phone, head phones, and bluetooth do not have the issue so I think its a odd coincidence

To anyone that may have been checking on this, it seems I got a rare case, there was actually a hardware problem on my device. Just a coincidence that I noticed it right after an update, I took it to the Customer Service place AT&T has in Wallingford, CT and the lady tried to re-flash the phone (what she said was standard procedure, she HAS to with every issue.) This didn't work so she gave me a new one.
All in all, only bad part of the experience was that it happened at all. New phone is working great.

Glad tohear that you got this taken care of.
Sent from my SAMSUNG-SGH-I727 using xda premium

Verizon is sending my 4th GSIII

First one was hacked almost immediately. Ended up perma-roaming with an IMEI of 0.
They replaced that with a new one. Of course they wanted to re-up my contract and steal my unlimited data. I looked the guy dead in the eye and said "No, that's unacceptable." He said "but unlimited data isn't in the system." I said "There's no 'system' to it. I take my old SIM, put in in a new phone, and walk out." Then he wanted to tell me that wouldn't work, until I grabbed my old phone, SIM, and threw it in the new phone. Then the manager walked up and said I could go.
That phone lasted until yesterday. Capacitive touchscreen starts acting up. Reboot, nothing. Turn it off for a while (CM10 was running hot), and it started working for just a couple of minutes. Restored to stock and it stopped working all together.
Took that to the store, and they were nice once they figured out that this one didn't come from online, but another store. Then they realized it was out of 14 days so it had to be a refurb. Wanted to ship it with free 5 day, but I paid $15 for it to get here by 10am this morning. Not a bad deal, over all.
Refurb arrives this morning, pull the SIM, battery, etc from the old one, and boot it up. Capacitive layer works properly, so that's good. Skip all the My Verizon and Google stuff, because I want to get everything tested. Open a few apps, good. Press physical home button....
NOTHING. Press it again. Nothing. Third time (really pressing hard this time), it pauses for a few seconds then slowly crawls back to the homescreen.
Freaking refurb. I call up verizon and they were super nice. Explained this was my 3rd phone, and they are overnighting another GS3 for free. Let's hope this lasts a little longer.
Edit: just realized this was my first actual post! I've been a member here since I got my first smart phone: an HTC Touch with WM 6!

I'll bet those VZW reps are loving to see you come through the door :laugh:
It's amazing how easy it is to get into the refurb vortex and not be able to get out. As you've seen, device after device has some inconspicuous issue that requires a return. These forums are loaded with these stories.
Hopefully the next one will be the one that keeps you happy, out of the VZW stores, and out of that vortex.

A QPST backup would have kept you out of this loop lol. So sorry to hear the struggle!

con247 said:
A QPST backup would have kept you out of this loop lol. So sorry to hear the struggle!
Click to expand...
Click to collapse
Yeah, I was in IRC while switching to CM10. invisibleK tried to help me out, but this was before the EFS or QPST fixes.

I too got the IMEI of 0 prior to QPST backups (ironically I got it from a TW rom, never flashed a AOSP rom. I think it was the lean Kernal.) I tried restoring my efs.sbn but I am stuck in roaming. If I Odin back to stock and take my phone back to a VZW will they give me a new one?

I got Verizon to do an even swap form a GNEX to a GS3 because of the connectivity issues it has had...free upgrade

no wonder verizon doesnt like people rooting their phones. op's fault

First two refurbs were your fault, hopefully with this 4th one it'll act right, and you won't mess it up.

luke1333 said:
no wonder verizon doesnt like people rooting their phones. op's fault
Click to expand...
Click to collapse
Yeah, I'd like to say it's vzw's fault for locking things down, but it happens on other networks as well. Looks like a Samsung issue.
Jothen2002 said:
I got Verizon to do an even swap form a GNEX to a GS3 because of the connectivity issues it has had...free upgrade
Click to expand...
Click to collapse
Hah, I tried to switch to a gnex and they talked me out of it.
tgom222 said:
I too got the IMEI of 0 prior to QPST backups (ironically I got it from a TW rom, never flashed a AOSP rom. I think it was the lean Kernal.) I tried restoring my efs.sbn but I am stuck in roaming. If I Odin back to stock and take my phone back to a VZW will they give me a new one?
Click to expand...
Click to collapse
Yeah, they should replace it, just play dumb and make sure you're on stock. But you'll end up with a return if it's been more than 14 days, and you really don't want that. Instead, just use QPST to write your IMEI to your phone. You don't need a backup, just the number on the back of the phone.
Neverendingxsin said:
First two refurbs were your fault, hopefully with this 4th one it'll act right, and you won't mess it up.
Click to expand...
Click to collapse
How is a faulty capacitive layer on a touchscreen my fault? A ROM doesn't make a touchscreen go bad.

Issues Accepting OTA

I had to reset my phone back to stock due to some issues with data/signal issues. I'm now not able to accept the ota vrlg7 every time i hit check for update it says service unavailable. I have my imei, stock,bootloader locked back. Im able to get on the internet so I know data isnt an issue as far as connectivity..

Maybe try a factory reset from inside touchwiz?

fr8cture said:
Maybe try a factory reset from inside touchwiz?
Click to expand...
Click to collapse
tried that a no go..I have a replacement coming tomorrow so i guess i could wait it out...Its my fourth one...

I had the same issue. I called support and they sent me a new sim card. Once I threw it in there and it activated the error went away. I would call or go into a store and get a new sim.

Hate to tell you but you probably need a new phone. I was getting that message with my first GS3. I took it to the store I bought it at and they tried a new sim...same message. They didn't want to, but I demanded they give me a new phone. I paid full retail price for the phone, so I didn't want it replaced with some refurb piece of junk.
I commented before reading further posts. Hope your replacement is good.
Sent from my SCH-I535 using xda app-developers app

I have this problem too. I wonder how many people have this problem and don't know it? Not everyone is as update happy as the people on this forum are..... Myself included
Sent from my SCH-I535 using xda premium

The new replacement solved the issues..but decided to get new sim as well just to make sure..I am not 100% sure but Im beginning to think that some of the peoples issues may lie within flashing certain roms and zip alterations and causing hardware issues... I could be wrong but the thought has crossed my mind

antawnm26 said:
The new replacement solved the issues..but decided to get new sim as well just to make sure..I am not 100% sure but Im beginning to think that some of the peoples issues may lie within flashing certain roms and zip alterations and causing hardware issues... I could be wrong but the thought has crossed my mind
Click to expand...
Click to collapse
I have never rooted or flashed any rom on this phone, 100% stock. This started a few days after the last update.

Hard Bricked My US Cellular S3, I think, please help!

I haven't tried the jig, but all the other symptoms such as dead screen,functionless buttons and all are there, so I think it is Hard Bricked. It's really weird what happened, I rooted my S3, it was working perfectly, then I unlocked the bootloader, it was perfectly fine even after that, then using ROM Manager I installed clockwork recovery mod, it was was working great. Then, I deleted my android market using ES File Explorer, and the guide for replacing the market told me to look for Vending.apk and then delete it, I looked but couldn't find it, so I 100% remember I tapped the search button in ES File Explorer and searched for Vending.apk, then suddenly a window popped up with names of files flashing but it didn't say searching or anything just three dots (...) and under there were two options YES and NO. I pressed No, it closed and then popped up again so this time I pressed Yes. then the names of files kept flashing and then it finished but didn't give me any search result, But my Phone memory was showing Empty, only the sd card folder was there and nothing else so I closed the app and opened it again, still the phone memory was empty, I was freaked out, so I restarted the phone and then, it never started :crying: I don't know what happened. Please help?

odin back to stock and start over....your device is far from hardbricked.

Really?? Can you please tell me step by step what to do?? I'm a complete noob at this!
droidstyle said:
odin back to stock and start over....your device is far from hardbricked.
Click to expand...
Click to collapse

My device does not go into download mode, nor in recovery, it's buttons are useless and there's a completely dead screen.
droidstyle said:
odin back to stock and start over....your device is far from hardbricked.
Click to expand...
Click to collapse

have you tried a different battery?

I forgot to mention, it's brand new, this happened the second day I bought it. So, the battery is flawless and perfect.
droidstyle said:
have you tried a different battery?
Click to expand...
Click to collapse

No its dead for sure. He tried to unlock the us cellualr S3 which would result in a perma brick.
You don't need to unlock the bootloader of the us cellular S3. That is why everything is labeled "verizon unlock" and stuff.

con247 said:
No its dead for sure. He tried to unlock the us cellualr S3 which would result in a perma brick.
You don't need to unlock the bootloader of the us cellular S3. That is why everything is labeled "verizon unlock" and stuff.
Click to expand...
Click to collapse
ahh i missed that detail...yes i agree its dead for sure! jtag or new replacement time.

Since it's only a couple days, take it back into USCC store. You're in your 15 day Window, they should swap it for a new one. Act dumb, don't tell them you rooted it. Just say you heard it buzz and it died. They'll mark it down as defective and give you a new one

How the hell was I supposed to know that? The US Cellular S3 is completely identical to the Verizon one, the only difference is the carrier logo, I rooted it with the Verizon S3's guide everything went perfectly fine, so I continued to do all the other stuff. I just got it 2 days ago :crying: . Huff, I've sent it for JTAG to a friend.
droidstyle said:
ahh i missed that detail...yes i agree its dead for sure! jtag or new replacement time.
Click to expand...
Click to collapse

ShazzyK-IDEOS said:
How the hell was I supposed to know that? The US Cellular S3 is completely identical to the Verizon one, the only difference is the carrier logo, I rooted it with the Verizon S3's guide everything went perfectly fine, so I continued to do all the other stuff. I just got it 2 days ago :crying: . Huff, I've sent it for JTAG to a friend.
Click to expand...
Click to collapse
a simple google search would of told ya that...
http://lmgtfy.com/?q=is+the+bootloader+unlocked+on+the+usc+galaxy+s3
research then flash dont flash then research!

tallgrasshawk said:
Since it's only a couple days, take it back into USCC store. You're in your 15 day Window, they should swap it for a new one. Act dumb, don't tell them you rooted it. Just say you heard it buzz and it died. They'll mark it down as defective and give you a new one
Click to expand...
Click to collapse
Great idea, but, I'm not in the US. I bought this phone from a guy who brought it from the US, I got it for half the price of an S3 here. So now, I don't know what to do, I gave it to friend, I hope he'll fix it, but if he's unable to can I give it to Samsung?

True, well said :'( I messed up big time.
droidstyle said:
a simple google search would of told ya that...
http://lmgtfy.com/?q=is+the+bootloader+unlocked+on+the+usc+galaxy+s3
research then flash dont flash then research!
Click to expand...
Click to collapse

Hi everyone,
I think my fiance might have hard-bricked his (new! Less than 24 hrs old!) Verizon Samsung Galaxy S III. He researched, rooted, set up bit-defender and it was working fine but when he tried to copy music files onto the micro-SD, they appeared to have gone onto the hard-drive instead and made his phone uber sluggish. We had some friends over, so he dropped the issue for a while and then went back to try to fix it only to make things worse. I know there isn't enough detail there about what *else* he tried to do, but when he came to bed last night he was kicking himself for not researching it enough and mentioned that he tried taking the batter out, resetting it, taking the sim card out, resetting it, telling bit defending to wipe the phone, etc. but all it would do last night was just display the 'samsung' logo then go to black.
This morning, I found your threads and tried to do the power+down+home advice that I've seen on a few threads here but it didn't work (obviously).
I suggested using the micro-SD adapter to try to explore the files on a PC, so we might look into that later.
Is there anything else you guys would recommend? I'm thinking the only thing to fix it now is the dopey route. :silly:
-Ami

Your phone is Soft Bricked not hard bricked, otherwise it wouldn't even turn on, Use A USB JIG to force it into download mode, then reflash with Odin.
Aminarra said:
Hi everyone,
I think my fiance might have hard-bricked his (new! Less than 24 hrs old!) Verizon Samsung Galaxy S III. He researched, rooted, set up bit-defender and it was working fine but when he tried to copy music files onto the micro-SD, they appeared to have gone onto the hard-drive instead and made his phone uber sluggish. We had some friends over, so he dropped the issue for a while and then went back to try to fix it only to make things worse. I know there isn't enough detail there about what *else* he tried to do, but when he came to bed last night he was kicking himself for not researching it enough and mentioned that he tried taking the batter out, resetting it, taking the sim card out, resetting it, telling bit defending to wipe the phone, etc. but all it would do last night was just display the 'samsung' logo then go to black.
This morning, I found your threads and tried to do the power+down+home advice that I've seen on a few threads here but it didn't work (obviously).
I suggested using the micro-SD adapter to try to explore the files on a PC, so we might look into that later.
Is there anything else you guys would recommend? I'm thinking the only thing to fix it now is the dopey route. :silly:
-Ami
Click to expand...
Click to collapse

ShazzyK-IDEOS said:
Really?? Can you please tell me step by step what to do?? I'm a complete noob at this!
Click to expand...
Click to collapse
If you're such a noob and unprepared for a brick, maybe you shouldn't have ventured down custom ROM/unlock avenue?
Just a thought.
Sent from my SCH-I535 using Tapatalk 2

ShazzyK-IDEOS said:
Your phone is Soft Bricked not hard bricked, otherwise it wouldn't even turn on, Use A USB JIG to force it into download mode, then reflash with Odin.
Click to expand...
Click to collapse
Yeah, this morning it won't even turn on no Samsung, no hope. Lesson learned... hopefully not a very expensive one.. :fingers-crossed:

Aminarra said:
Yeah, this morning it won't even turn on no Samsung, no hope. Lesson learned... hopefully not a very expensive one.. :fingers-crossed:
Click to expand...
Click to collapse
Pull the battery, put it in and let it charge for a while couple hours. Then hold vol - , home and power. If it week go into download/Odin mode you're fine. If so then go to the development thread stickies and follow droid style guide section 6
Sent from my SGS3 running Eclipse Touchwiz

Great thought, but let me tell you before my Galaxy S3 I owned a Wildfire S, tinkered with it every bit, OC,Rom,bootloader and everything, before that I owned a Huawei U8150, my first android, I literally went bezerk modding that thing. So, I'm not a noob at this,I was a noob at this different Carrier different software kinda thing, I thought the phone was the same and indeed it is, but the difference is that the Verizon's Bootloader is locked. I'm well familiar with everything, I just messed up by not researching that if the bootloader was unlocked already, mainly because I was a bit too excited about getting my S3.
1ManWolfePack said:
If you're such a noob and unprepared for a brick, maybe you shouldn't have ventured down custom ROM/unlock avenue?
Just a thought.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse

tallgrasshawk said:
Since it's only a couple days, take it back into USCC store. You're in your 15 day Window, they should swap it for a new one. Act dumb, don't tell them you rooted it. Just say you heard it buzz and it died. They'll mark it down as defective and give you a new one
Click to expand...
Click to collapse
Yup!