I've read a lot about SDS and there seems to be no general consensus on the symptoms of it. Some people say they can enter recovery/dl/etc but the phone crashes all the time. Others say that their phone doesn't turn on at all and won't charge.
Here is my issue with my S3.
I just recently installed 4.3 pacman rom. I got everything set up and everything was going great. I tried to flash ACID MOD 7.0/DevilKernel, and they both failed, so I rebooted back into the system and the phone just shut off.
If I take the battery out and hook it up to a charger, the LED will light up. However, if I plug it in with the battery already inside of it, the LED does not turn on. Also, if I hook up the phone to my computer, it'll make a sound like it is trying to mount the device, but it'll make a stutter sound like it failed. It doesn't do this automatically, it only does it if I try to enter recovery/download mode/or turn the phone on.
I'm not sure if the phone is completely dead, or bricked, or what is going on? Or if anyone has any other suggestions - other than changing the battery, which I did do, lol.
Sounds bricked. What model is you s3 btw? And can you post links to everything you've flashed?
SDS doesn't affect our S3's, it was only the international model that had this issue, and I believe it was only on the original firmware.
Sent from my SCH-I535 using Tapatalk 4
http://forum.xda-developers.com/showthread.php?t=2015525
latest nightly
+ 4.3 gapps. it booted fine from gapps.
http://forum.xda-developers.com/showpost.php?p=38599629&postcount=1005
acid mod v7
2802 + 2805 for sammy devices
http://forum.xda-developers.com/showthread.php?t=2240832
devil kernel
prior to flashing pac i installed 2.6.3 twrp because the 2.5.x i was on did not work. i booted in, flashed pac, got everything set up. after restoring the apps and whatnot, i went back to twrp to install acid + devil kernel. they both failed, so i just rebooted from there and it never turned back on. i just assumed the battery was dead, charged my bat in my external charger, and yeah, never turned on since then.
any way to do this without jtag? i'm not at home right now to do something like that and am out of the country, so im a bit unsure how hard it'd be to get those supplies.
i was able to go to a samsung a/s place, but they would only send back to america. i don't think it is worth paying 200+ when this phone is probably only worth 400 or so out of the box, brand new, maybe even less.
i just assumed it was SDS because the symptoms seemed spot on, but it was really weird. i've never had any issues like this flashing roms and it wont' even go to the boot logo. if i plug it in, it makes it seem like it is trying to mount, but there are no vibrations or anything like that on the phone.
thanks for all the help doc, like always.
Thanks for providing the links! Makes it so much easier to help when we don't have to search for everything!
I'm afraid you have bricked your device. I don't know about the Acid mods compatibility with our device, so it may be part of the problem, but that kernel is for the international S3 (I9300/9305). (I'm assuming you have the T999 btw). Never flash anything for the international models, you're nearly guaranteed to brick the phone!
But there's hope! Verify your model number by looking under the battery. Then check out KAsp3rd's unbrick thread in the development section. It should be towards the top.
Give that a shot and say a prayer! It won't fix all bricks, it depends on what was overwritten, but there's a good chance it'll fix yours!
In the future, it's best to stay out of the international models forum altogether! The devices are very different and you take a huge risk when using anything you find there!
Good luck!
Sent from my SCH-I535 using Tapatalk 4
Thanks Doc. I don't think it'll be fixed unless someone in that thread wants to try to flash that devil kernel and see if they can unbrick it w/o jtag. I followed those instructions to a T, and no dice. Although, I can't really tell if my battery is charged right now. I don't have my external charger on me. I will try again tomorrow, but I really doubt it at this point.
Really? Maybe give it another try with a different SD if possible. I saw the posts there and there's no reason I can see that it wouldn't fix when aboot got overwritten.
Sent from my SCH-I535 using Tapatalk 4
DocHoliday77 said:
Really? Maybe give it another try with a different SD if possible. I saw the posts there and there's no reason I can see that it wouldn't fix when aboot got overwritten.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, it is really weird.
After some toying with it I figured out that it only tries to mount the device when connected to the computer IF and only IF my phone is connected to the computer with no battery. It didn't do this before, which is odd. Even if I take out the SD card it still does this now. Before it would fail to make any sound, and now it tries to install the driver. But then it says it fails to install the driver for it, which is the bricked one, the SUBS DWLND or whatever.
I tried following Kasp3rd's advice to hold the button down longer, and I held it down for a whole five minutes with no luck.
I will try another SD when I get the chance, right now I only have a 64gb with no avail to back it up. The SD card is super old though, you are right Doc. It is from my OG droid, but really I haven't had a need for SD cards since I was on an iPhone after my droid and since the S3 is mine, but i'm not using it, I never really bought a nice SD card for it.
I'm going to run to the store in a bit to get one though and hopefully that will make a difference?
May have missed the part about it being 64GB before. Could be the age, but also those 64's have given lots of folks some problems in the past. Seems the S3 can be a bit finicky with those.
Sent from my SCH-I535 using Tapatalk 4
Related
Hi there...
So I have a slight issue. I've been away from the XDA community for a while now, and anyways, I came back and wanted to upgrade into the latest Fresh 3.5.0.1 Rom. So I downloaded it, new radios, and new pri pack, and put it on and went to work. Now that I'm here at work, I flashed 3.5, the new radios, and the new pri. Rebooted (I think I probably should have rebooted after flashing the rom, before loading up the others :-\). I got the wonderful green error arrow thing. I've had this happen before when flashing roms, so I pulled the battery, waited a few minutes, then put it back in. Pushed the power button, and now I have a brick. It won't power up at all.
So I need help, as I've never had a brick before and I'm stuck here at work, working on my mac laptop. Any advice on how to get the phone to start into recovery so I can nandroid backup would be wonderful.
Edit: I was upgrading from Fresh Evo 3.3.0.1. According to Fresh, I should have been able to flash this rom over my old version. :-\
Does anything happen when you try and power on? Ie does the phone vibrate and do anything at all? Also when you plug the phone on does the charging lite come on? I hate to say this but if you answer no to everything it looks like you may have a brick. But there is always hope.
I could be wrong but I think toy were suppose to boot the rom then flash the radios.
wrapkgb said:
Does anything happen when you try and power on? Ie does the phone vibrate and do anything at all? Also when you plug the phone on does the charging lite come on? I hate to say this but if you answer no to everything it looks like you may have a brick. But there is always hope.
I could be wrong but I think toy were suppose to boot the rom then flash the radios.
Click to expand...
Click to collapse
No light with charging, not even the most faint bit of vibrating other than my own pulse I do have insurance on the phone however through Asurion or however you spell it.
Also, I was going to delete this thread before you posted here, as I realized too late that this isn't the question forum
Wrong forum maybe, but its already here so its all good. With what you said I would have to say you in fact have a brick unfortunately. I would work on trying to get a replacement from asuron. Sucks man, radios can be dangerous if something goes wrong in the process of flashing them.
wrapkgb said:
Wrong forum maybe, but its already here so its all good. With what you said I would have to say you in fact have a brick unfortunately. I would work on trying to get a replacement from asuron. Sucks man, radios can be dangerous if something goes wrong in the process of flashing them.
Click to expand...
Click to collapse
I guess that's what I get for not being more active in the community >.>
Gonna check with Sprint during my lunch to see if they'll replace it for free as a defect ^.^
Sure would be nice not to have to pay that 100 dollar deductible.
Ya, unfortunately you probably pulled the battery while the radios were updating. Good thing you have insurance, because that Evo is done.
Why not take it to Sprint? Just say it stopped working. Make sure to delete any suspicious files from the SD card.
jxr94 said:
Ya, unfortunately you probably pulled the battery while the radios were updating. Good thing you have insurance, because that Evo is done.
Click to expand...
Click to collapse
I pulled the battery after I rebooted and it went to the green ! screen. :-\.
Wish the outcome was a little better!
Ok, so like...two days ago, I followed qbkings video on how to root & clockworkmod an epic with EI22, well it worked. I got recovery working A ok and played around with some roms and stuff. They all worked for the most part, but after rebooting my phone, the SAMSUNG loading screen wouldnt fade away, realizing it had been soft bricked. I tried recoveries but they didnt work. tried tutorial after tutorial after tutoria, but no luck. When trying the Odin unroot method It'd always be stuck on like a factory. file, and keep getting the phone - ! - computer error afterwards. Ive tried looking around the forums and such, but no go. I really need help with this.
You didn't look to hard. There have been 5 threads like this in the last 2 weeks. Go to the stickies, top of development and follow post 1 of How to restore a semi-bricked Epic.
Sent from my SPH-D700 using XDA App
Uh yeah, that was one of the first posts I tried. Never worked for me. Followed exactly step by step and repeated the process five times, but ive been constantly getting stuck on factoryfs.rfs
oh ****, now it wont even turn on. tried charger usb, nothing! no indicator or anything. damn. am I screwed?
I think you were better off leaving your phone alone. If following instructions is difficult, than that should have been your first clue. Id post a link to help you, but you have already read and tried it, and even that didn't work........time for you to buy an iphone I guess.
Sent from cyandroid
Try pulling the battery and sd card, let sit for an hour with usb unplugged, then connect to usb cable with odin running and try to boot into download mode.
If it goes, pop the battery in and load up ei22 or another odinable tar along with the recovery in qbkings videos. Make sure only reboot is checked in odin.
If not, go back and try every step in the sticky. I doubt that you have a problem that has not been experienced already.
Sent by my CleanGB Epic using XDA App
So you tried buying and using a better cable? And tried with both the battery and sd card out using only the computer as a power source like the thread in Development said to do?
b16flybye said:
I think you were better off leaving your phone alone. If following instructions is difficult, than that should have been your first clue. Id post a link to help you, but you have already read and tried it, and even that didn't work........time for you to buy an iphone I guess.
Sent from cyandroid
Click to expand...
Click to collapse
That's a bit flamish.
shane6374 said:
That's a bit flamish.
Click to expand...
Click to collapse
Sometimes the truth hurts.
I tend to agree with that sentiment, nothing against you OP, but there are some that gravitate to technology and feel at home, and then there are some that gravitate and lack the necessary skills for something like this.
This is a very straight-forward task, especially with all of qbking's hard work in making those very easy to follow videos, and other's time typing out tutorials, so I really fail to see how most have so much trouble making it work. Maybe they belong in the latter analysis.
Sent from my SPH-D700 using Tapatalk
azyouthinkeyeiz said:
Sometimes the truth hurts.
I tend to agree with that sentiment, nothing against you OP, but there are some that gravitate to technology and feel at home, and then there are some that gravitate and lack the necessary skills for something like this.
This is a very straight-forward task, especially with all of qbking's hard work in making those very easy to follow videos, and other's time typing out tutorials, so I really fail to see how most have so much trouble making it work. Maybe they belong in the latter analysis.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
We all started somewhere on this, and I bet most people didn't have success right away. I know I didn't on either platform I've worked on. I'm just sick of the n00b flaming around here. These people might be the ones who's roms or kernels you running in a year. Just show some respect.
Sent from shane6374's Epic via Tapatalk
Youll have to find one of them jigs to get you back into download mode I assume usually time heals all mistakes though if your inpatient id look up how to make an odin(download) reset jig ( I think its called that). I think there a thread about that lying around here somewhere...
Sent from my OG Epic
Yeah, not trying to knock on you too hard, but qbkings videos should be all you need for successfully rooting and flashing. He works hard on them and is very clear with instructions.
Sent from cyandroid
Yup, Ive tried different cables,ports, no battery, battery but got nothing. I thoroughly read through the entire post and tried what was suggested and got nothing. Phone wont turn on or do anything. I'm thinking that i'm screwed. I have been thinking about getting a replacement epic for a while, cause some time ago I actually accidentally dropped it from my desk and this happened to it http://imgur.com/ZBlNn still worked fine, so I didn't really bother thinking about replacing it, but now I'm guessing that I have to. If I do end up requesting for a replacement, any tips/fore warnings about what I should say when I talk to the guys over at sprint before i end up mumbling like an idiot.
Yup, Ive tried different cables,ports, no battery, battery but got nothing. I thoroughly read through the entire post and tried what was suggested and got nothing. Phone wont turn on or do anything. I'm thinking that i'm screwed. I have been thinking about getting a replacement epic for a while, cause some time ago I actually accidentally dropped it from my desk and this happened to it http://imgur.com/ZBlNn still worked fine, so I didn't really bother thinking about replacing it, but now I'm guessing that I have to. If I do end up requesting for a replacement, any tips/fore warnings about what I should say when I talk to the guys over at sprint before i end up mumbling like an idiot.
With the soft brick you might have been able to save it. It happened to my brothers phone and what I did to fix it was wipe everything, factory reset
Then flash stock rom. Wipe everything again
Then flash stock kernel
Wipe everything again
Then it was perfect.
If you had already been flashing roms.and such then your problem wasn't following directions.
You just might have flashed a rom without a supported kernal. Causing bootloop
As far as where you are now.. maybe tell then you dropped it and it never turned back on?
I don't think they can ever find out you rooted it if it never turns on again lol
Sent from my PG86100 using XDA App
Jbluna said:
Yup, Ive tried different cables,ports, no battery, battery but got nothing. I thoroughly read through the entire post and tried what was suggested and got nothing. Phone wont turn on or do anything. I'm thinking that i'm screwed. I have been thinking about getting a replacement epic for a while, cause some time ago I actually accidentally dropped it from my desk and this happened to it http://imgur.com/ZBlNn still worked fine, so I didn't really bother thinking about replacing it, but now I'm guessing that I have to. If I do end up requesting for a replacement, any tips/fore warnings about what I should say when I talk to the guys over at sprint before i end up mumbling like an idiot.
Click to expand...
Click to collapse
Don't use the broken screen as the reason or they will charge you around $100. Just try and make sure you get across the point that its the faulty phone (even if it isn't) and make sure you have an accurate believable story on how it got bricked. If you mention anything about messing with root or anything similar they won't replace it.
True. But on another note you can't say much. Only other thing I can think of is saying maybe you tried updating the device and it died
Sent from my PG86100 using XDA App
Seriously you ignored the odin mode jig? it jumps you back into download mode and you should be able to odin back to eco5........ Ill find a how to for ya.
Its all over a simple google search and you can find a usb jig for about 8 bucks.
Sent from my OG Epic
I just unbricked my wife's EPIC with this: http://forum.xda-developers.com/showthread.php?t=1052813
thanks dyehya for the howto tutorial!
Jus tell them you took it off charge this morning and it wouldn't come on.
Did you try the mythological magic button? The pin hole behind the cover next to the camera lens?
my phone was on aokp and fine but i decided i just wanted to go back to the blazer i had
i boot into recovery and im in my cwm recovery (not rogue)
but when i go to wipe/factor reset the screen flashes its stock recover with the little green android in the background and freezes there
i think WTF? no biggie i pop out battery just boot into recovery again and start over
nope doesnt work im stuck on samsung galaxy s screen with yellow triangle
finally get home to comp and go into odin mode try to flash stock ek02 and that doesnt work just gets me stuck at data
so i try it without data and that works but now it just bootloops
so now i dont know if im brick'd or just in some boot loop
any help would be great!!!
hope everything i typed makes sense if not ill clarify
dont know what to tell ya man....im in a hole right now and i see no light either...
i was on codename and the phone was fine for a whole day and a half. i uncderclocked it to 800mhz and undervolted 100mv and the phone ran beautiful for a day and a half. then all of a sudden like two hours ago it froze. went in to a bootloop. trying to figure this out right now...odin wont recognize my phone at alllllll
damn man that is certainly worse than my situation not
seems like ics isnt as stable as we hope haha, but man idk why my phone get stuck when flashing the data.img in odin it never gets past this... im thinking its bricked which really sucks but just gotta roll with the punches... if anyone can help please do ill be up a little while longer
Yeah its bricked.
ross4747 said:
damn man that is certainly worse than my situation not
seems like ics isnt as stable as we hope haha, but man idk why my phone get stuck when flashing the data.img in odin it never gets past this... im thinking its bricked which really sucks but just gotta roll with the punches... if anyone can help please do ill be up a little while longer
Click to expand...
Click to collapse
ICS isn't unstable you just messed up basically. This is why you should read the brick threads and warnings first about flashing between ICS. And gingerbread. Your phone sounds like it's bricked. Sorry dude.
As for the guy with the boot loop. You're probably not bricked you just need to try and get into download mode and odin a stock rooted rom. How long did you pull the battery for?
Under volting can cause boot loops but your issue could be a combination. I would post in the brick thread. Someone experienced with that problem can help you.
I recommend pulling the battery and waiting an hour or so then redo it.
Good luck!
Sent from my SPH-D710 using Tapatalk 2 Beta-5
LordJummy said:
ICS isn't unstable you just messed up basically. This is why you should read the brick threads and warnings first about flashing between ICS. And gingerbread. Your phone sounds like it's bricked. Sorry dude.
As for the guy with the boot loop. You're probably not bricked you just need to try and get into download mode and odin a stock rooted rom. How long did you pull the battery for?
Under volting can cause boot loops but your issue could be a combination. I would post in the brick thread. Someone experienced with that problem can help you.
I recommend pulling the battery and waiting an hour or so then redo it.
Good luck!
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
ya i tried man...but odin doesnt recognize my phone... im thinking its the LG usb cable i have. i read somewhere that the pins inside the acttual cable arent the same as the E4GTs cable. so tomorrow im gonna get my stock cable.
Carbajal3009 said:
ya i tried man...but odin doesnt recognize my phone... im thinking its the LG usb cable i have. i read somewhere that the pins inside the acttual cable arent the same as the E4GTs cable. so tomorrow im gonna get my stock cable.
Click to expand...
Click to collapse
That's possible if its some proprietary cable. These phones use a standard mini USB to USB so any standard generic cable should work. I use a really thick and durable Logitech cable that came with a mouse, or sometimes a generic super long one I have that's like 10 feet
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Ok u guys to to read the OP again for what your flashing you cannot flash any ROM from ICS right now it has a high risk of brick if your going to flash an ICS ROM the best bet is from a cwm based kernal like EL26 not Rogue and you shud be back on GB so use one of SFhub packages it takes an extra 10 minutes tops
Sent from my SPH-D710 using XDA
MJHawaii said:
Ok u guys to to read the OP again for what your flashing you cannot flash any ROM from ICS right now it has a high risk of brick if your going to flash an ICS ROM the best bet is from a cwm based kernal like EL26 not Rogue
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Wow. Now you're spreading more misinformation. You certainly can flash roms from ICS recovery its just not 100% safe in all versions and flavors.
Its generally user error that's causing the bricks. The OP will usually claim he did everything perfect but 99% of the time it comes out sooner or later they did something wrong out of haste or neglect.
You're not necessarily helping though with your false info. No offense intended I just don't want you further confusing some poor noob who takes your word...
And just to further clarify: yes odin'ing stock EL26 is safer than flashing from ICS based CWM.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Carbajal3009 said:
dont know what to tell ya man....im in a hole right now and i see no light either...
i was on codename and the phone was fine for a whole day and a half. i uncderclocked it to 800mhz and undervolted 100mv and the phone ran beautiful for a day and a half. then all of a sudden like two hours ago it froze. went in to a bootloop. trying to figure this out right now...odin wont recognize my phone at alllllll
Click to expand...
Click to collapse
Get back into DL mode and flash back to stock and invest in a usb download jig its 5$ and comes in handy in soft brick and bootloop situations
Sent from my SPH-D710 using XDA
MJHawaii said:
Get back into DL mode and flash back to stock and invest in a usb download jig its 5$ and comes in handy in soft brick and bootloop situations
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Apparently you're not reading the entire thread lol. Scroll up man.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
LordJummy said:
Wow. Now you're spreading more misinformation. You certainly can flash roms from ICS recovery its just not 100% safe in all versions and flavors.
Its generally user error that's causing the bricks. The OP will usually claim he did everything perfect but 99% of the time it comes out sooner or later they did something wrong out of haste or neglect.
You're not necessarily helping though with your false info. No offense intended I just don't want you further confusing some poor noob who takes your word...
And just to further clarify: yes odin'ing stock EL26 is safer than flashing from ICS based CWM.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
as i said you cannot flash anything from ICS without running a risk of bricking your phone its a known issue
Goodnight jummy:what:
Sent from my SPH-D710 using XDA
MJHawaii said:
as i said you cannot flash anything from ICS without running a risk of bricking your phone its a known issue
Goodnight jummy:what:
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
No. You just flat out said you can't flash from ICS CWM. I was clarifying that is not true. Don't take it personally.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
OP: Phone is bricked, need to take to Sprint for replacement. More on your problem here:
Stuck at Data.img
And to see what the general advice is on avoiding this:
How Not To Brick Your E4GT
@Carbajal, yes it's your LG cable. I have same problem with same cable (from Optimus S). Sammy cable will fix it if you still have it. I forget the specific reason why but in layman's terms it was explained to me that the Sammy cable may have a longer pin which triggers the recognition. If you search the Q&A forum you should be able to find the thread.
MJHawaii said:
Get back into DL mode and flash back to stock and invest in a usb download jig its 5$ and comes in handy in soft brick and bootloop situations
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
i cant get the odin program to see my phone!! i can get into DL mode but am not able to flash anything through it...why?? i tried two different computers and three different cables but no go
Carbajal3009 said:
i cant get the odin program to see my phone!! i can get into DL mode but am not able to flash anything through it...why?? i tried two different computers and three different cables but no go
Click to expand...
Click to collapse
As you didn't clarify it before, did you try the Sammy cable provided with the phone? If that isn't doing it you may want to check Device Manager (assuming Win PC) and make sure nothing is disabled or not working properly. I mention this as it happened to me once when I tried to reassign the COM ports to use CDMA Workshop.
garwynn said:
@Carbajal, yes it's your LG cable. I have same problem with same cable (from Optimus S). Sammy cable will fix it if you still have it. I forget the specific reason why but in layman's terms it was explained to me that the Sammy cable may have a longer pin which triggers the recognition. If you search the Q&A forum you should be able to find the thread.
Click to expand...
Click to collapse
Word!
It freaked me out when I first tested this phone months ago since I came from Optimus S also. Didn't want to unpack all the accessories so just used the cable that came with the LG Optimus S, would charge, but no data. Thought the USB port on the E4GT was busted. Then tried 2 more LG Optimus S cables with the same result. Was about to return the phone when on a whim unpacked the flimsy looking Samsung cable and voila, it worked.
That flimsy looking Samsung cable has gotten me through over 300 flashes now w/o ever having a cable related problem.
garwynn said:
OP: Phone is bricked, need to take to Sprint for replacement. More on your problem here:
Stuck at Data.img
And to see what the general advice is on avoiding this:
How Not To Brick Your E4GT
Click to expand...
Click to collapse
ross, this is your problem. i'm in the same boat. in that thread, someone was able to repartition the /data partition to his sdcard and it worked (albeit at the cost of sdcard space). worth a shot, but keep up with that thread as it's pretty active.
Thanks guys who inputed about that LG cable. I took me a while to find my original sammy cable!! but my phone workds again and im soooooo happy. Thanks a bunch.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
garwynn said:
OP: Phone is bricked, need to take to Sprint for replacement. More on your problem here:
Stuck at Data.img
And to see what the general advice is on avoiding this:
How Not To Brick Your E4GT
Click to expand...
Click to collapse
I did this sunday morning, trying out AOKP. Read that there was a possibility for corruption, did it anyway. after deciding it was too buggy for my liking as a daily driver, i attempted to go back. Tried my USB Jig with no luck.
Took it into Sprint on Monday, an hour later the tech tells me its toast. (Tell me something I don't know). I tried so hard to weasel out a new White model.
I've got a refurb'd black model and i'm suspecting there's a few issues with it. Its completely stock, no root. I've had to reboot four times today already from not turning on or coming out of sleep. Then every so often the phone will not stop vibrating during a haptic feedback response. I've turned haptic and vibrate off, but it still locks up on occasion. Funny but weird as hell. Probably gonna take it in later this week and try my luck again at getting a new model.
Hi. I'm new here and first, want to say hello. I've been on iPhones for many years. Finally got bored and crossed over to the "Dark Side" lol.
Second....I need help!!! lol or just some good old advice. I've searched and searched but can't really find a definitive answer. Too much conflicting info out there. One thing I did learn is that this forum is thee best so here I am!
I successfully rooted my i747 Galaxy S3 (Rogers). The trouble arose when I tried to install a Custom ROM. I kept getting errors, and after a bunch of research, I read that I should update my CWM. I did and that's when the trouble started. It went into a loop. It would just stay on a black screen. I can't get into Recovery mode or anything else for that matter. It will not power up in any way. It will now show the charging indicator light when it's charging. It's as dead as my ex-wife in the sack . Obviously I've bricked it. I've learned that a jtag repair would fix it....and have since been told by an android buddy that it won't. Any advice or info would be appreciated!
The phone was on 4.1.1 and it's the Rogers i747 model (same as AT&T)
P.S, Rooting on a Mac sucks! I'm thankful that I had a PC at home too! Not that turned out too good
Update...as per Tech Support at Rogers, I removed the battery and plugged it in. The red indicator light came on. But it does not stay on and it goes out shortly after, battery in or not. Thought one more piece of info may help someone figuring this out.
Charge it as much as you can, search for the return to stock thread on here (make sure you get the one for your carrier), do that and if it isn't working after that, then you'll probably have to get it replaced.
Sent from my SGH-I747 using xda premium
Monkeymannnn said:
Charge it as much as you can, search for the return to stock thread on here (make sure you get the one for your carrier), do that and if it isn't working after that, then you'll probably have to get it replaced.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I appreciate the reply but I can't connect to the phone at all. Couldn't return it to stock even if I wanted to.
mrkay said:
I appreciate the reply but I can't connect to the phone at all. Couldn't return it to stock even if I wanted to.
Click to expand...
Click to collapse
Once it's charged, are you able to get in download mode? If so, there's a light at the end of the tunnel. Odin can bring you back up.
If your pc doesn't recognize it, reboot it (pc). Try a different cable/usb port. Reinstalling the drivers is an option too.
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
Once it's charged, are you able to get in download mode? If so, there's a light at the end of the tunnel. Odin can bring you back up.
If your pc doesn't recognize it, reboot it (pc). Try a different cable/usb port. Reinstalling the drivers is an option too.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It won't charge at all. Left it overnight and nada. I'll try again, but highly unlikely that it will. I also tried different ports as well as different computers to connect to. My only concern is that I take it back and Samsung discovers that it's been messed with. Oh well, it's only money
mrkay said:
It won't charge at all. Left it overnight and nada. I'll try again, but highly unlikely that it will. I also tried different ports as well as different computers to connect to. My only concern is that I take it back and Samsung discovers that it's been messed with. Oh well, it's only money
Click to expand...
Click to collapse
Could say that you tried to update with kies and that's what you got.. Works like a charm usually
In my stupidity I've hard bricked not one but TWO AT&T GS3's same thing black screened and nothing else. I doubt very seriously you'll get it to charge. Here's the good news I'm assuming it's still under warranty and if it is when you take it to the warranty store at AT&T they will try two batteries to see if it boots and when it doesn't you'll get a new phone. You don't have to tell them nothing. As far as you know you shut it down to charge when you went to bed and it wouldn't boot in the morning.
Worked for me needless to say I'm WAAAAAY more carefull and spend a lot of time here reading and double and triple checking everything!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
S3freak said:
In my stupidity I've hard bricked not one but TWO AT&T GS3's same thing black screened and nothing else. I doubt very seriously you'll get it to charge. Here's the good news I'm assuming it's still under warranty and if it is when you take it to the warranty store at AT&T they will try two batteries to see if it boots and when it doesn't you'll get a new phone. You don't have to tell them nothing. As far as you know you shut it down to charge when you went to bed and it wouldn't boot in the morning.
Worked for me needless to say I'm WAAAAAY more carefull and spend a lot of time here reading and double and triple checking everything!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Not to make you sound stupid, there are no such things as stupid questions here at least I've learned that while enjoy my stay here at xda, but did you accidentally flash an international ROM? This sounds like a case of it.
The first phone I hard bricked I'm sure that's what I did. It became a beautiful paper weight. Not sure what happened the second time I had got off work late and instead of going to bed I was tinkering with my phone. I don't really know what happened. Careless and not reading, not making sure of what I was doing. I learned the hard way and I spend a lot more time studying and staying with the AT&T forums for my phone.
I have to admit I've really had fun here learning.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Everything was telling me it was in fact the power button malfunctioning. I was using Bubor's CM10.2, later updated to CM11. And it was starting to happen everyday. It would happen in CWRM and TWRP, and also the Power menu would often pop up.
So I bought a new "refurbished" cappy from Amazon for about $100. Didn't test it out on stock. Just jumped straight in to flashing CM11 and migrating my files.
And then it did the same exact thing. :crying: Just restarting itself for no apparent reason right when I started using it.
Also, it doesn't usually to do it when it's just sitting there playing music. No, it waits until I pick it up and try to do anything.
So is it possible I bought what looks like a brand new phone with the same exact problem? Or do I need to do some more investigation into the software.
Also, I have always had shoddy results when flashing. I can't get EFS to do a backup, I can't get the stock rooted rom to boot up, I always have a yellow and blue warning triangle on startup.... I know how important it is to follow directions exactly, and I do not get good results with these guides. (I'm saying this just to provide more evidence that perhaps I'm messing something up)
I have 2 glides here. One is my production phone and the other one is used for developing my ROM.
So I can say they use the same software and my dev phone has the same reboot prob like you describe. Working fine until I try to do things. Not always but often enough that it makes me angry.
There are others having the same issue which seems to be hardware related. So if you have a brand new device you should think about reverting to stock and replace it by warranty..
You can take a look here for some more details:
http://forum.xda-developers.com/showthread.php?t=2847894
-----
Sent from my SGH-I927 using XDA Android mobile app