Related
EDIT: Yes I know that this has been a long standing issue...but I never heard of it until it happened to me!!! So no need to come in and comment like 4 or 5 others felt the need to do with "lol this is old news u r teh dumbz hurr" I just wanted to bring this up to any new captivate owners like myself :]
If for some reason you have a hankering for some stock 2.1 from your captivate like I did for whatever random reason tonight......if you see an an OTA (Over The Air) Update for your captivate....DO NOT DO IT!!!!!! I say this because I did this tonight thinking that MAYBE this was some form of a 2.2 silent update push..or hell just some bugfixes would have been nice...so i went ahead and downloaded it, it prompted for a restart so it could flash it......and when it attempted to flash...it got about 50% and failed! Well at this point im thinking...awesome...ATT at its finest. So it said it was going to reboot back to android, I waited patiently...waited.....it hot about 3 minutes with phone in hand and screen off when i feel 2 *buzz* buzz* ! I think to myself HOORAY! its okay ....well i was wrong...that was my Captivates last words so to speak. I have tried plain powering on the phone....trying to go into recovery, trying to go into download mode even using a JIG to get back into download mode.....nothing the screen is blank completely, seems as if its not even getting power. :\ I am now the sad owner of a Captivate shaped door stop /facedesk .....Thankfully i yelled at the ATT people on the phone tonight enough to get a replacement phone lol! I am greatfull for this and felt as if i should pass this along to you guys until this gets sorted out. And no im not the only one thats had this problem
http://forums.wireless.att.com/t5/Samsung/Samsung-Captivate-Bricked/td-p/2008787/page/2
thats just one of many threads where this has happened. I dunno if this is new or old news...but Still i thought that i should put this out here.
Bryan
I think this is a known issue. Many phones had this happen with the release of JH7. It was provably just the JH7 update that got pushed to your phone. I wouldn't get my hopes up
Sent from my SGH-I897 using XDA App
bradleyG said:
I think this is a known issue. Many phones had this happen with the release of JH7. It was provably just the JH7 update that got pushed to your phone. I wouldn't get my hopes up
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
this wasnt a post about me getting my hopes up for a 2.2 update lol. This was a warning to those who dont about that fail update thats messing up a ton of phones. ;D
blackberry,iphone captivate, whatever. i have learned NEVER EVER do OTA update download it from phone authors site or whatever no matter what phone it is OTA is spelled BRICK....
I didn't received any ota from att but last year I forced update my phone and it works fine with me though without any issue. I think its the same ota update but I manually force to update my phone lol
Sent from my SAMSUNG-SGH-I897 using XDA App
leo5111 said:
blackberry,iphone captivate, whatever. i have learned NEVER EVER do OTA update download it from phone authors site or whatever no matter what phone it is OTA is spelled BRICK....
Click to expand...
Click to collapse
I'm of the assumption that a OTA bricks less than 0.1% of the devices that attempt an update. Granted that may be a large number if the number of devices are large..but not much of a chance to brick in the big picture
JH7 pushed to mine flawlessly when i got my phone last month, no issues at all.
HaiKaiDo said:
And no im not the only one thats had this problem
http://forums.wireless.att.com/t5/Samsung/Samsung-Captivate-Bricked/td-p/2008787/page/2
thats just one of many threads where this has happened. I dunno if this is new or old news...but Still i thought that i should put this out here.
Bryan
Click to expand...
Click to collapse
That thread started in September, that's ancient in tech years.
bradleyG said:
I think this is a known issue. Many phones had this happen with the release of JH7. It was provably just the JH7 update that got pushed to your phone. I wouldn't get my hopes up
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
+1 Still betting on St. Patty's Day release, office pool ya know.
Razzman said:
JH7 pushed to mine flawlessly when i got my phone last month, no issues at all.
Click to expand...
Click to collapse
+100 Mine got the OTA fine and it was even rooted on edge service. Meh, who can tell why some did brick and others didn't. For sure I'll never do another OTA again. I love my 1007 build too much to return it.
HaiKaiDo said:
If for some reason you have a hankering for some stock 2.1 from your captivate like I did for whatever random reason tonight......if you see an an OTA (Over The Air) Update for your captivate....DO NOT DO IT!!!!!! I say this because I did this tonight thinking that MAYBE this was some form of a 2.2 silent update push..or hell just some bugfixes would have been nice...so i went ahead and downloaded it, it prompted for a restart so it could flash it......and when it attempted to flash...it got about 50% and failed! Well at this point im thinking...awesome...ATT at its finest. So it said it was going to reboot back to android, I waited patiently...waited.....it hot about 3 minutes with phone in hand and screen off when i feel 2 *buzz* buzz* ! I think to myself HOORAY! its okay ....well i was wrong...that was my Captivates last words so to speak. I have tried plain powering on the phone....trying to go into recovery, trying to go into download mode even using a JIG to get back into download mode.....nothing the screen is blank completely, seems as if its not even getting power. :\ I am now the sad owner of a Captivate shaped door stop /facedesk .....Thankfully i yelled at the ATT people on the phone tonight enough to get a replacement phone lol! I am greatfull for this and felt as if i should pass this along to you guys until this gets sorted out. And no im not the only one thats had this problem
http://forums.wireless.att.com/t5/Samsung/Samsung-Captivate-Bricked/td-p/2008787/page/2
thats just one of many threads where this has happened. I dunno if this is new or old news...but Still i thought that i should put this out here.
Bryan
Click to expand...
Click to collapse
August called it wants its omg failed update back
Sent from my SGH-I897 using XDA App
Razzman said:
JH7 pushed to mine flawlessly when i got my phone last month, no issues at all.
Click to expand...
Click to collapse
Yup... This, but then my phone was new and unmodded at the time.
Thx for the info
viperrepiv said:
Thx for the info
Click to expand...
Click to collapse
No problem
I know its easy to flame. But we were all new once.
smokestack76 said:
I know its easy to flame. But we were all new once.
Click to expand...
Click to collapse
Join Date : March 2010
New
cappysw10 said:
Join Date : March 2010
New
Click to expand...
Click to collapse
July 2010 for you. You are new as well
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!!!
Hi folks. First post.
Just upgraded to a Skyrocket from an Aria. I got a confirmation that it shipped and a link to set up my device via Ready2Go. Has anyone tried this? How does it work? Does it set it up exactly as if you were doing it manually? It seems like a cool feature, but it almost seems too good to be true, especially coming from AT&T. I just don't want anything setup incorrectly or differently (like having to use all the apps through some AT&T portal or something).
I've used it a few times. Works very well.
So I just got this lovely device from the ATT refurb store for ten bucks. And the problem I'm having is that ready2go will not sync to the device. I tried four times with reboots of phone and computer in between tries. What a stupid ass idea this is. Leave it to ATT to find a way to screw up a perfectly good system. Any way since it won't sync I can't use the phone at all. I've gotten Odin to recognize the device and know I can flash CWM then another ROM and that's what I'll end up doing but first just wanted to see if anyone else has run into this issue before or has any ideas.
hechoen said:
So I just got this lovely device from the ATT refurb store for ten bucks. And the problem I'm having is that ready2go will not sync to the device. I tried four times with reboots of phone and computer in between tries. What a stupid ass idea this is. Leave it to ATT to find a way to screw up a perfectly good system. Any way since it won't sync I can't use the phone at all. I've gotten Odin to recognize the device and know I can flash CWM then another ROM and that's what I'll end up doing but first just wanted to see if anyone else has run into this issue before or has any ideas.
Click to expand...
Click to collapse
Why can't you use the phone at all because of ready to go? I always skip that ready to go crap and set up my phone myself. So be more specific when you say can't use. Is it locked up? Need more info...
Sent from my SAMSUNG-SGH-I727 using xda premium
garydv2002 said:
Why can't you use the phone at all because of ready to go? I always skip that ready to go crap and set up my phone myself. So be more specific when you say can't use. Is it locked up? Need more info...
Click to expand...
Click to collapse
Well there is no option to skip it. Just back or continue. So if you go to continue it gives web address to go to and the code to enter to sync up. I enter the code and it just sits at the spinning beachball of death forever. How where you able to bypass this setup? I think it may be new from ATT as far as putting in on the phone right after the splash screen.
I would just flash cwm in Odin and flash a custom rom. Skip the stock BS
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
BS is right. Like I said in my first post I know how to get around it I was just seeing if anyone else had it happen.
hechoen said:
BS is right. Like I said in the OP I know how to get around it I was just seeing if anyone else had it happen.
Click to expand...
Click to collapse
No, I skipped it. Then I looked around my new phone for a few minutes. Then I said, hmmm time for a new rom.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
hechoen said:
Well there is no option to skip it. Just back or continue. So if you go to continue it gives web address to go to and the code to enter to sync up. I enter the code and it just sits at the spinning beachball of death forever. How where you able to bypass this setup? I think it may be new from ATT as far as putting in on the phone right after the splash screen.
Click to expand...
Click to collapse
Hit the home button and all that ready to go crap goes away and allows you to procede setting up the phone.
And xcrazydx is right you might just want to flash a custom rom if you can't figure out how to get past ready to go. Especially since you have a refurbished device and warranty is of little or no issue...
Sent from my SAMSUNG-SGH-I727 using xda premium
garydv2002 said:
Hit the home button and all that ready to go crap goes away and allows you to procede setting up the phone.
Click to expand...
Click to collapse
Negative. I'm not a noob and I'm very familiar with Samsung devices. lol It will go nowhere with out the sync that's not working. More annoying than anything else. And just seeing if anyone else had this happen.
hechoen said:
Negative. I'm not a noob and I'm very familiar with Samsung devices. lol It will go nowhere with out the sync that's not working. More annoying than anything else. And just seeing if anyone else had this happen.
Click to expand...
Click to collapse
It's been so long I don't remember much about ready2go. I never used it, I know that much
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
It's been so long I don't remember much about ready2go. I never used it, I know that much
Click to expand...
Click to collapse
Looks like it's off to odin touch recovery then flash ICS. Still really freakin annoying though.
hechoen said:
Looks like it's off to odin touch recovery then flash ICS. Still really freakin annoying though.
Click to expand...
Click to collapse
Yeah, sorry I don't remember
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Hey I came from an Aria as well. Big change.
I don't use ready2go. Waste of effort. Might as well just customize on the phone itself. Why else is it a "smartphone" then?
I know for sure I skipped it just don't remember what button I pushed to do it. As much as I flash this phone and my wife's phone I don't take time to use that ready to go crap if I flash an update in Odin I usually turn right around and flash cwm then root then restore my apps data etc with titanium backup. Never has made me use ready to go....
Sent from my SAMSUNG-SGH-I727 using xda premium
*Sorry if this has been already asked, I just want to confirm everything for my exact make and provider.
Hello XDA Forums, long time lurker, and about time I started contributing to the community.:good:
Anyway, I received my Galaxy S3 via VZW preorder a few weeks ago. It ran like a charm. However, as of today, the messenger app keeps crashing, and no longer responds/works. The question of whether or not it was because I rooted it caused the problem is irrelevant, but I digress...
I called Verizon about the problem and they are sending me a replacement in overnight shipping, and as of now they don't know it's rooted.
Whenever i boot the phone it has the custom symbol with the lock on it, will that mean my warranty will be voided and I will have to pay for the full price? Although I ordered overnight shipping it won't be shipped for another 2 days due to the fact that tomorrow is sunday. It is still rooted ATM. Thanks in advance guys! Hope to be a long-time active member here.
You need to Odin back to stock. Also before doing that make sure that your flash counter in download mode is at 0 and not at custom stuff. If it is use triangle away app v 1.7 to get rid of the flash count. THEN Odin back to stock.
Yes, if you send it back rooted they will void it.
silver04v said:
You need to Odin back to stock. Also before doing that make sure that your flash counter in download mode is at 0 and not at custom stuff. If it is use triangle away app v 1.7 to get rid of the flash count. THEN Odin back to stock.
Yes, if you send it back rooted they will void it.
Click to expand...
Click to collapse
Ok, can you link me to a tutorial on how to do so? Thanks.
GalaxyS3IsMeh said:
Ok, can you link me to a tutorial on how to do so? Thanks.
Click to expand...
Click to collapse
The tutorial is what they posted.
Sent from my SCH-I535 using xda premium
Well for example how would you check the flash count?
Dudenell said:
Well for example how would you check the flash count?
Click to expand...
Click to collapse
The flash counter appears in the download screen. Press and hold power, vol down, and home button until boot.
Sent from my SCH-I535 using Tapatalk 2
Don't worry
GalaxyS3IsMeh said:
*Sorry if this has been already asked, I just want to confirm everything for my exact make and provider.
Hello XDA Forums, long time lurker, and about time I started contributing to the community.:good:
Anyway, I received my Galaxy S3 via VZW preorder a few weeks ago. It ran like a charm. However, as of today, the messenger app keeps crashing, and no longer responds/works. The question of whether or not it was because I rooted it caused the problem is irrelevant, but I digress...
I called Verizon about the problem and they are sending me a replacement in overnight shipping, and as of now they don't know it's rooted.
Whenever i boot the phone it has the custom symbol with the lock on it, will that mean my warranty will be voided and I will have to pay for the full price? Although I ordered overnight shipping it won't be shipped for another 2 days due to the fact that tomorrow is sunday. It is still rooted ATM. Thanks in advance guys! Hope to be a long-time active member here.
Click to expand...
Click to collapse
I have returned 2 rooted VZW phones for hardware failure. DId it through the mail. No problem. I believe that there was a court ruling that messing with software on phones doesn't void hardware warraanty but I'm too lazy to google it right now. GL.
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!