I am not sure this was posted or not, however if it has, please point me to the right direction as I am not able to find it.
Situation:-
Using the phone as per normal. It auto lock or manual lock it. Wanna unlock/wake up the phone it doesnt. This happened once in awhile not sure when as unable to determine the cause as sometimes running a game and I lock it and sometimes lock it without running anything i.e. back to home. To wake up, I reboot the phone by long pressing on/off button. Was using CheckRom ICS... And at one occurance the phone really died on me and unable to reboot no matter what I did. Sent in to SC and got back a new Motherboard.
Now it is happening again. Now in JB 4.1.2 (OmegaRom). The phone just fell in to a deep sleep and cant wake up unless I reboot the phone. I hope I dont get the forever slumber/sudden death situation again.
Anyone can give guidance or advise on how to check what is the matter or anyone having the same experience?
Flash back to stock and check if it occurs. If it does use triangle away and send it back in mate
Sent from my GT-I9300 using XDA Premium HD app
firstknightfirst said:
I am not sure this was posted or not, however if it has, please point me to the right direction as I am not able to find it.
Situation:-
Using the phone as per normal. It auto lock or manual lock it. Wanna unlock/wake up the phone it doesnt. This happened once in awhile not sure when as unable to determine the cause as sometimes running a game and I lock it and sometimes lock it without running anything i.e. back to home. To wake up, I reboot the phone by long pressing on/off button. Was using CheckRom ICS... And at one occurance the phone really died on me and unable to reboot no matter what I did. Sent in to SC and got back a new Motherboard.
Now it is happening again. Now in JB 4.1.2 (OmegaRom). The phone just fell in to a deep sleep and cant wake up unless I reboot the phone. I hope I dont get the forever slumber/sudden death situation again.
Anyone can give guidance or advise on how to check what is the matter or anyone having the same experience?
Click to expand...
Click to collapse
I am experiencing exactly the same thing , so unrooted and back on stock ics now and even that doesn't seem stable...planning to sell it off next week... desperately hoping it doesn't slìp into deep slumber when I am selling it...
Sent from my GT-I9300 using xda premium
tommy2601 said:
I am experiencing exactly the same thing , so unrooted and back on stock ics now and even that doesn't seem stable...planning to sell it off next week... desperately hoping it doesn't slìp into deep slumber when I am selling it...
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Oh no... I like the phone and I hope I dont have to sell it off.... So I am hoping someone here woudl be able to help me out.... I am backing up nearly everyday with TiB....
Even I love my s3 but I love note 2 even more and I am buying a note 2....the main reason I am selling it is if it conk out one day here in India it's very difficult to claim warranty we really need to slug it out with Samsung India and I don't have the time or patience to do that...
Sent from my GT-I9300 using xda premium
happened to me too
I don't recall it happened to me while using stock touchwiz roms.
However, since I've moved to AOSP roms (first AOKP M1 and then JellyBam), it happened to me 3 or 4 times now.
Do you get it also on touchwiz roms? Which OmegaRom are you using?
Wich kernel are using my mates? Maybe that is problem, combination firmware and kernel...
Regards
using latest OmegaRom... as mentioned... first happened in CheckROm and even in Wanam...
Was using siyah kernel... so now testing Perseus and see wtr this happened or not...
Just happened when I have monster warlord running and locked it.. when I unlock... it happened again... must be something like not enuf ram or went into deep sleep... very strange indeed. Nevertheless change to Perseus to test out different kernel for now...
tommy2601 said:
I am experiencing exactly the same thing , so unrooted and back on stock ics now and even that doesn't seem stable...planning to sell it off next week... desperately hoping it doesn't slìp into deep slumber when I am selling it...
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
If u sell a broken phone,that is such a douchebag move no offence to u but really i wud feel sorry for the man u sold it..
Sent from my GT-I9300 using xda premium
Download this app https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en and post the screenshot. It might be SDS
Same happened with my phone. Go to see what it's up to and suddenly its not responding. The only option is to hold power down until it reboots.
It would also do it on in coming calls and managed to delete a text which arrived shortly before it froze.
Hoped upgrading to the latest firmware would help, didn't. Going without root, nope. Freezing apps in Titanium, still no joy.
Finally this morning I had enough and went for a full wipe. Very little installed but no problems since.
Would suggest doing the same, especially if you plan to sell the phone anyway.
CHEVYbarracuda1 said:
If u sell a broken phone,that is such a douchebag move no offence to u but really i wud feel sorry for the man u sold it..
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hi buddy, selling a dying phone at a good price and buying something u love even more is douche bag move....then I really petty ur retarded and douche bag thinking
Sent from my GT-I9300 using xda premium
Have the same problem with mine, using the latest wanam stock rom and every now and again the phone will either just restart or lock with the screen off (led notification will keep blinking however).
Just trying the official Vodafone rom now through Odin. If this doesn't solve it I think the phone will have to go back.
To note: issue appeared after installing some root apps. Notably adfree and beats drivers. Anybody else have either installed?
tommy2601 said:
Hi buddy, selling a dying phone at a good price and buying something u love even more is douche bag move....then I really petty ur retarded and douche bag thinking
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I said no hard feelings.. U said that u hope that it doesnt slips into deep slp when u r selling it.. so bassically u r trying to sell broken phone for a price of good one usable...also i havent insulted u before so why r u insulting me??That my friend is called lack of culture..
Sent from my GT-I9300 using xda premium
CHEVYbarracuda1 said:
I said no hard feelings.. U said that u hope that it doesnt slips into deep slp when u r selling it.. so bassically u r trying to sell broken phone for a price of good one usable...also i havent insulted u before so why r u insulting me??That my friend is called lack of culture..
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Please keep this on topic:
Seems like a common issue, I've now unrooted my phone and loaded stock 4.1.2 from Sammobile using odin, reset the binary counter, removed SD card and i'm still having crashes and hangs. Seems my phone is on the way out?
THEsirloin said:
Please keep this on topic:
Seems like a common issue, I've now unrooted my phone and loaded stock 4.1.2 from Sammobile using odin, reset the binary counter, removed SD card and i'm still having crashes and hangs. Seems my phone is on the way out?
Click to expand...
Click to collapse
Just return it to the nearest samsung store for repair.. I believe it is hardware failure
Sent from my GT-I9300 using xda premium
Mine has just started doing this, literally a matter of days ago - coincidence??
TimmyRaa said:
Mine has just started doing this, literally a matter of days ago - coincidence??
Click to expand...
Click to collapse
When did it happen? Was it around Wednesday last week? Just thinking that maybe an updated app or something?
I have now updated again using kies with the official 4.1.2. I have no problems with restarts when using the stock apps. I have however had issues with the google servers and now believe this to have been the main reason for the crashes earlier (Christmas new phone activation traffic?).
Out of interest, have you been running adfree or the beats audio driver? I had mine working all day yesterday, installed both and then the hangs started coming back again.
Also worth noting that adfree now states that a newer version is available when loading up, but non exists (that i know of?)
CHEVYbarracuda1 said:
I said no hard feelings.. U said that u hope that it doesnt slips into deep slp when u r selling it.. so bassically u r trying to sell broken phone for a price of good one usable...also i havent insulted u before so why r u insulting me??That my friend is called lack of culture..
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I am not selling it to some innocent 3 person I am exchanging it with note 2 by paying the difference amount at a local Samsung retail store (just sending back there own Frankenstein to them)
And about culture my friend I don't need a lesson from a person who doesn't even have the sensibility to understand that his comments can hurt others(u started It fIrst)..
As today Is my last day in the s3 forum I don't want to sign off on a bitter note so sorry if I have hurt u in anyway.
Sent from my GT-I9300 using xda premium
THEsirloin said:
When did it happen? Was it around Wednesday last week? Just thinking that maybe an updated app or something?
Click to expand...
Click to collapse
I can't say for sure, but around Wednesday isn't unreasonable.
Out of interest, have you been running adfree or the beats audio driver? I had mine working all day yesterday, installed both and then the hangs started coming back again.
Also worth noting that adfree now states that a newer version is available when loading up, but non exists (that i know of?)
Click to expand...
Click to collapse
I do run AdFree, and yeah, I saw the notice about the new version - it's a different app entirely... still called AdFree, uninstall the old one, and install the new one. Not sure why they did that.
I'm at a loss - I just reinstalled XELL4, and it's still doing it. Short of doing a full wipe and starting afresh (which I really can't be bothered with), I don't know what else to try. Was working fine up until now.
Related
I don't think best buy would even noticed if I return a rooted phone as long as the rom is as close stock as I can get. Any opinions?
Sent from my Htcclay's Remixed Remix using XDA App
slinky1914 said:
I don't think best buy would even noticed if I return a rooted phone as long as the rom is as close stock as I can get. Any opinions?
Sent from my Htcclay's Remixed Remix using XDA App
Click to expand...
Click to collapse
theres no guarantees but you are correct they probably wont notice that it doesn't work. What they will be looking for is if the phone works, water damage indicator and physical damage. They will probably once over the phone then return it as long as you are within your proper return period.
talltexan said:
theres no guarantees but you are correct they probably wont notice that it doesn't work. What they will be looking for is if the phone works, water damage indicator and physical damage. They will probably once over the phone then return it as long as you are within your proper return period.
Click to expand...
Click to collapse
That's what I'm thinking. It works it just won't have as much bloatware on it. There just gonna resell it anyway. I tried to restore the nandroid of the original rom but once restored it gets stuck at the first samasung splash screen.
Sent from my Htcclay's Remixed Remix using XDA App
slinky1914 said:
That's what I'm thinking. It works it just won't have as much bloatware on it. There just gonna resell it anyway. I tried to restore the nandroid of the original rom but once restored it gets stuck at the first samasung splash screen.
Sent from my Htcclay's Remixed Remix using XDA App
Click to expand...
Click to collapse
Well with all returns what they do is send it back to Tmobile they will send it to Samsung and get turn into a refurbish unit (for exchanges and such) They will flash the OEM Rom back on it.
Flash stock using Odin? It brings the phone unrooted and all the bloatware back
zephiK said:
Flash stock using Odin? It brings the phone unrooted and all the bloatware back
Click to expand...
Click to collapse
No I haven't yet. Seems like a lot of work if they are gonna do it anyway. And some people have had some issues.
Sent from my Htcclay's Remixed Remix using XDA App
If you flash back via ODIN make sure the three button recovery works because if ODIN crashes mid-way (I've had this happen twice on my previous Vibrant) you've got a brick if you can't get it back into download mode via the buttons. Do a forum search. Or maybe if you wound up with the dreaded black screen of death that wouldn't be such a bad thing. They'd almost have to take it back then.
i just returned one the other day to best buy and the chick went through the phone for a couple of minutes, checked settings and menus and then also checked for physical damage. i had reflashed it back to stock anyways as bell's version comes with a bunch of specific apps. i was glad i did flash it back and i also relocked it to bell's network as i had unlocked it for use on rogers
hondaguy said:
i just returned one the other day to best buy and the chick went through the phone for a couple of minutes, checked settings and menus and then also checked for physical damage. i had reflashed it back to stock anyways as bell's version comes with a bunch of specific apps. i was glad i did flash it back and i also relocked it to bell's network as i had unlocked it for use on rogers
Click to expand...
Click to collapse
It is true every once in a while you will get a rep who knows their stuff (when i worked at t-mobile i would play with customers who had flashed new ROMs on their G1 ) However most of the time you will get minim wage joe blow and he could give a rats ass.
talltexan said:
It is true every once in a while you will get a rep who knows their stuff (when i worked at t-mobile i would play with customers who had flashed new ROMs on their G1 ) However most of the time you will get minim wage joe blow and he could give a rats ass.
Click to expand...
Click to collapse
true, true
slinky1914 said:
No I haven't yet. Seems like a lot of work if they are gonna do it anyway. And some people have had some issues.
Sent from my Htcclay's Remixed Remix using XDA App
Click to expand...
Click to collapse
It really isn't.. its better to be safe than sorry. At least thats how I feel.
And as far as that phone -- pc logo, I guess they would take it back but if they ask you how did it get that way? you're going to have to lie about it and its just going to feel really awkward.
Truthfully though, all they'd have to be trained to do is not accept returns if you see the superuser app. That'd be the easiest way to see if someone has rooted their phone & If you're not even going to take the effort to flash it back to stock, you're probably not going to delete that app either.
Just re-Odin it & call it a day. It took me less than 5 minutes to get back to stock & maybe another 5 to download the necessary files.
This will also ensure that you don't have any leftover contacts or log ins to facebook or anything like that on there (better safe than sorry).
Thanks guys. I was using my slide for the last couple of days by picked the vibrant back up and fell back in love. If I do decide to return it I'll put it back on stock. Thanks again guys.
Sent from my SGH-T959 using XDA App
i dont think they care
just aslong as it lokks in good shape
but sometimes you get that one derp that feels the he/she needs to look through it
Why don't u install one clig lag fix from market and unroot it? Should be easy.
Sent from my SGH-T959 using XDA App
nguyenmd said:
Why don't u install one clig lag fix from market and unroot it? Should be easy.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
What about installing the Galaxysrooter from the app market then unrooting it with this app?
Im a little new at all this so please excuse me if i sound dumb. Cant you just flash a nandroid backup and then undo root also?
geocepe said:
Im a little new at all this so please excuse me if i sound dumb. Cant you just flash a nandroid backup and then undo root also?
Click to expand...
Click to collapse
Yup, that'll work as well. Or you could download a nandroid that is stock without root.
i got my vibrant the day it came out, from costco... $99
Swapped it a week later, Couldn't unroot it for some reason, but they didn't notice... then again it was costco
They won't care trust me i worked for tmo. These people don't even know what root is they might think its a plant. They just scan it out of their inventory and send it to samsung. If it has root on it they are not going to send it back to tmo just to find u or look to charge your account. That is soooooo tedious cuz u have to do an IMEI search which hardly works on TMOs internal network (i tried when i worked with them never really worked) so yea all they look for is hardware damage and the liquid damage indicator other then that ur golden.
qhusb_dload is popping up to dowlnload everytime i plug my phone into my computer, it wont charge, and this only happened today after it died, it just didnt want to get recognized by the computer or to charge. please help me because i dont want to return it to tmo since its rooted D:
anthonylancer said:
qhusb_dload is popping up to dowlnload everytime i plug my phone into my computer, it wont charge, and this only happened today after it died, it just didnt want to get recognized by the computer or to charge. please help me because i dont want to return it to tmo since its rooted D:
Click to expand...
Click to collapse
I dont know whats wrong, but just because its rooted, does not mean you cant return it. If its a hardware issue it will still be covered. But it sounds like maybe a bad battery
Sent from my NRGized Amaze...
via xda premium
thanks man!
anthonylancer said:
thanks man!
Click to expand...
Click to collapse
No prob. I would try stopping by your local carriers store and see if the have a battery laying around to test, or it u know someone else who has the phone try theirs. If its not the battery, post back and we'll go from there
Sent from my NRGized Amaze...
via xda premium
I have heard this issue alot on xda, and i'll say its pretty much bricked, if you can't turn it on or get into the bootloader or recovery tmobile/wind/htc wouldn't be able to, other people with the same issue said they got it replaced with no problems, so you got nothing to worry about
Buy a new battery.
Sent from my SGH-T989 using Tapatalk 2 Beta-2
anthonylancer said:
qhusb_dload is popping up to dowlnload everytime i plug my phone into my computer, it wont charge, and this only happened today after it died, it just didnt want to get recognized by the computer or to charge. please help me because i dont want to return it to tmo since its rooted D:
Click to expand...
Click to collapse
OMG another one
Its not bricked dude, its a battery failure. See my thread, I've got the same issue, its solved by replacing the batttery..
http://forum.xda-developers.com/showthread.php?t=1561104
You can call up HTC North America [email protected] 866-449-8358 if you are in US, they will ship you the battery free of cost.
When I called them up they asked me to ship the phone back, however I had also had unlocked the bootloader voiding the warranty, so I took a chance and told them I tested the phone at local tmo center it works with replacement battery (even though I hadn't)...they said no need to ship the phone then...we'll have the battery sent out to you...and it arrived in 3 business later although I had to wait quite long as there was weekend in between...
BTW what ROM/Kernel/recovery combo were you using before it died ?
Mafioso said:
OMG another one
Its not bricked dude, its a battery failure. See my thread, I've got the same issue, its solved by replacing the batttery..
http://forum.xda-developers.com/showthread.php?t=1561104
BTW what ROM/Kernel/recovery combo were you using before it died ?
Click to expand...
Click to collapse
If it's the same setup that you and my buddy had... Then I think we may have found a culprit... Just hoping its not :/
Sent from my HTC_Amaze_4G using Tapatalk 2 Beta-4
glacierguy said:
If it's the same setup that you and my buddy had... Then I think we may have found a culprit... Just hoping its not :/
Sent from my HTC_Amaze_4G using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
We can't blame NRGZ's ROM for it, as its the most popular ROM for this phone and to my knowledge just the ROM can't cause such a bug, the kernel might (even i'm not sure for that but still)...can any devs (Adjust? ) give their opinion on it ?
Mafioso said:
We can't blame NRGZ's ROM for it, as its the most popular ROM for this phone and to my knowledge just the ROM can't cause such a bug, the kernel might (even i'm not sure for that but still)...can any devs (Adjust? ) give their opinion on it ?
Click to expand...
Click to collapse
Lol he just started doin roms recently i dont think hes going to be able to tell u anything. And no ones blaming nrgz rom. I think the belief is that its one of the recovery's
Sent from my NRGized Amaze...
via xda premium
aj_2423 said:
Lol he just started doin roms recently i dont think hes going to be able to tell u anything. And no ones blaming nrgz rom. I think the belief is that its one of the recovery's
Sent from my NRGized Amaze...
via xda premium
Click to expand...
Click to collapse
lol, just mentioned him coz he also mentioned he had this same issue and is a dev
Hello all, I was walking my friend through rooting his phone over Google talk. He rooted all went well a few days later he wanted to Rom it. He made a mistake and flashed the international omega Rom on his US ATT samsungi747. His phone is now dead. No way to get into recovery or download mode. Just dead. Bricked. What can I do to help him? As I am partially responsible cause I was helping him. I did not know much about the Rom he was flashing.
I was reading about a possible fix with a jig but can not find a jig for.the Samsung i747.
Please any and all advice would be greatly appreciated.
Sent from my ADR6400L using Tapatalk 2
Sorry but looks like its gone. Have seen a few ppl able to recover with mskips fix but only if theyre able to turn phone on.
DeathGrind said:
Hello all, I was walking my friend through rooting his phone over Google talk. He rooted all went well a few days later he wanted to Rom it. He made a mistake and flashed the international omega Rom on his US ATT samsungi747. His phone is now dead. No way to get into recovery or download mode. Just dead. Bricked. What can I do to help him? As I am partially responsible cause I was helping him. I did not know about the Rom he was flashing.
I was reading about a possible fix with a jig but can not find a jig for.the Samsung i747.
Please any and all advice would be greatly appreciated.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
A compatible jig may be your only solution if you can't get into download mode manually. A jig would force the phone into download mode, once in download mode you'd be able to flash the stock AT&T firmware through Odin.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Has anyone ever tried just returning it and saying it randomly died? If they can't turn it on then there's no way to tell it's rooted
Only joking
"All this knowledge is giving me a major brainer!"
In the blacked Screen try flash with Odin.
Sent from my Hybrid Note using Tapatalk 2
DakiX said:
In the blacked Screen try flash with Odin.
Sent from my Hybrid Note using Tapatalk 2
Click to expand...
Click to collapse
he's in oregon and I'm in california. I think he is freaking out. But he did say ODin was not recognizing the device.
ADB? ^^
Sent from my Hybrid Note using Tapatalk 2
Error 1. Not reading
Error2. Wrong section... not reading
If he cant get cwm or screen to show something who knows what he did...fix: there is none get another device and read before u do stupid stuff.... u can't expect us to fix lack of reading or not knowing what ur flashing....
im on my phone. expect terrible typos.
DeathGrind said:
oh no. Its his first android phone. He only had it about a week. I can't believe this. I feel so bad for him.
Thanks for the reply
I have been looking for a jig that is compatible with the att samsung galaxy s3 sgh-i747 and had no luck. Do they exist?
Click to expand...
Click to collapse
A jig is a jig the one I bought for my captivate works 100% on gs3, get the jig put into phone if don't boot into download mode, hold down power button with jig still in if that don't work ur screwed .... your better off trying make ur own jig ( YouTube it ) cause if the phone runs out of battery and won't charge then u have another issue...
---------- Post added at 12:38 AM ---------- Previous post was at 12:27 AM ----------
Moh_Jay said:
Has anyone ever tried just returning it and saying it randomly died? If they can't turn it on then there's no way to tell it's rooted
"All this knowledge is giving me a major brainer!"
Click to expand...
Click to collapse
Just cause "we " can't turn it on don't mean they eventually can't ..
Btw you maybe able to save your friend
http://forum.xda-developers.com/showthread.php?t=1743757
"All this knowledge is giving me a major brainer!"
Moh_Jay said:
Btw you maybe able to save your friend
http://forum.xda-developers.com/showthread.php?t=1743757
"All this knowledge is giving me a major brainer!"
Click to expand...
Click to collapse
Thanks man! I ordered him one. Hopefully it will work. He's also going to make one tomorrow.
A huge thank you to all the people that provided helpful information and friendly advice.
I was actually expecting more ridicule, but it was minimal. . I know we messed up, but I never knew you could "brick" a phone from flashing a Rom.
Anyway thanks again guys! I will keep you posted on if the jig works or not.
Sent from my ADR6400L using Tapatalk 2
Moh_Jay said:
Has anyone ever tried just returning it and saying it randomly died? If they can't turn it on then there's no way to tell it's rooted
Only joking
"All this knowledge is giving me a major brainer!"
Click to expand...
Click to collapse
The morning I was picking up my phone...a dude walks in and says that his phone doesn't turn on anymore after having it a week. I thought to myself..."he flashed an international ROM...what a douche".
Some people actually have there phones just stop working. Happened to my friend that had a Samsung galaxy nexus, stock unrooted. Just died. There was nothing I could do to fix it.
Sent from my ADR6400L using Tapatalk 2
DeathGrind said:
Thanks man! I ordered him one. Hopefully it will work. He's also going to make one tomorrow.
A huge thank you to all the people that provided helpful information and friendly advice.
I was actually expecting more ridicule, but it was minimal. . I know we messed up, but I never knew you could "brick" a phone from flashing a Rom.
Anyway thanks again guys! I will keep you posted on if the jig works or not.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
If you didnt know a rom could brick a phone you shouldnt be flashing period. Theres always ALWAYS bold letters that says this may brick your phone an or we are not responsible if this breaks your phone... no one with there first android should be flashing till they know android smoothly... *sigh*
Usually 90% of the time your always able to get into recovery mode. From what I've read this only happens when flashing the omega Rom. People make mistakes.
I've rooted and rom'd 100s of phones, and never not been able to get back to recovery.
Sent from my ADR6400L using Tapatalk 2
SiNJiN76 said:
The morning I was picking up my phone...a dude walks in and says that his phone doesn't turn on anymore after having it a week. I thought to myself..."he flashed an international ROM...what a douche".
Click to expand...
Click to collapse
The good and bad of brand new phone on the market. Some people do not like reading and want to be handed the solution.
Noobs....read.....read...read some more....go to bed....get up...read some more...have cookies for snack time....read some more... and then read some more... and for the love of GOD....read some more before flashing anything!
I mean that in the nicest way, becasue I have questions on a semi-regular basis also.
jcbofkc said:
The good and bad of brand new phone on the market. Some people do not like reading and want to be handed the solution.
Noobs....read.....read...read some more....go to bed....get up...read some more...have cookies for snack time....read some more... and then read some more... and for the love of GOD....read some more before flashing anything!
I mean that in the nicest way, becasue I have questions on a semi-regular basis also.
Click to expand...
Click to collapse
If ppl read things 95% of there questions would be answered. The other 5% could be found by google
I understand telling him to read. And he did so for about a week. He succesfully used odin to root his phone. A few days later he said he wanted to Rom, and asked me how to do a proper back up with titanium backup. I ran him through the backup procedure.
I mean I totally thought that if he made it through the rooting procedure that he was good to go. Rom'ing has always been to me something fairly easy, and if something went haywire, just boot to recovery.
I've had people ask for help that flashed an incomplete or corrupted download, but have always been able to at least power the phone on, or at the very least have it recongnized in adb.
I have been reading and googling about a fix, but information seems minimal on this current circumstance. So I reached out to the community for advice.
Sent from my ADR6400L using Tapatalk 2
DeathGrind said:
I understand telling him to read. And he did so for about a week. He succesfully used odin to root his phone. A few days later he said he wanted to Rom, and asked me how to do a proper back up with titanium backup. I ran him through the backup procedure.
I mean I totally thought that if he made it through the rooting procedure that he was good to go. Rom'ing has always been to me something fairly easy, and if something went haywire, just boot to recovery.
I've had people ask for help that flashed an incomplete or corrupted download, but have always been able to at least power the phone on, or at the very least have it recongnized in adb.
I have been reading and googling about a fix, but information seems minimal on this current circumstance. So I reached out to the community for advice.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Personally i wait a bit to root rom a brand new phone... however ive never had a issue untill i fried my gs mesmerize so im a lil hesitant
Yeah, this is the first serious issue I have ran into in almost 3 years of mod'ing android phones.
Sent from my ADR6400L using Tapatalk 2
Okay, Im an ass so I say that up front. I flashed a bad kernel and I hardbricked my 5 day old galaxy s3 fro Tmobile. I took it to the local repair place that does JTAG repairs, which btw, does not work on the weekends. according to them the JTAG'ing takes 40 hours which I think is more because I kept calling and seeing if the phone was showing any signs of life. Anyone know how long the actual JTAG procedure actually takes cause 40 hours seems like a long time to me. Even after they said there was no guarantee that it would work and bring my phone back from the dead.
I am not new to rooting or flashing roms and kernels and things of that nature. So for the record I did not read first about bad kernels floating about so again Im an ass.
First mistake was flashing anything from this forum, this is for the international version ONLY.
Secondly a jtag should bring it back to life.
I'm not sure of the timeframe but 40 hours seems like a lot of time to do anything.
Sent from my GT-I9300 using xda premium
barbie1215 said:
Okay, Im an ass so I say that up front. I flashed a bad kernel and I hardbricked my 5 day old galaxy s3 fro Tmobile. I took it to the local repair place that does JTAG repairs, which btw, does not work on the weekends. according to them the JTAG'ing takes 40 hours which I think is more because I kept calling and seeing if the phone was showing any signs of life. Anyone know how long the actual JTAG procedure actually takes cause 40 hours seems like a long time to me. Even after they said there was no guarantee that it would work and bring my phone back from the dead.
I am not new to rooting or flashing roms and kernels and things of that nature. So for the record I did not read first about bad kernels floating about so again Im an ass.
Click to expand...
Click to collapse
Could you describe how exactly you hardbricked your phone? As far as I know hardbricking is pretty much impossible on the s3 and probably extremely rare (this is the first case I've heard about it).
Sent from my GT-I9300 using Tapatalk 2
Whoosh13 said:
Could you describe how exactly you hardbricked your phone? As far as I know hardbricking is pretty much impossible on the s3 and probably extremely rare (this is the first case I've heard about it).
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Flashing a kernel for the international version on a US version will send you on the road to brick town.
Sent from my GT-I9300 using xda premium
nodstuff said:
Flashing a kernel for the international version on a US version will send you on the road to brick town.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Ah sorry my bad, I read it again and saw its the T-Mobile version
Sent from my GT-I9300 using Tapatalk 2
Well..on youtube you can see how the jig works and it doen't take that long.
Sent from my GT-I9300 using xda premium
A kernel won't hardbrick a phone. If you flash a correct kernel it should boot. A way to brick it is to flash a wrong firmware from here. Cause the first thing being flashed on a firmware with odin is bootloader. Then you will have an expensive paperweight.
Sent from my GT-I9300 using xda premium
afaik s3 has separate kernel and recovery where flashing a kernel dosent touch the recovery , so practically it should not be hard bricked
If I were you I would approach to XDA forum first! where all the " DO DOES " happen!
are you 100% sure its bricked?
I dont really know about it, but from my experience bootloader flash and emmc bug are the only ways to hardbrick S3, flashing wrong kernel should make your phone unbootable, but shouldnt do a **** to your download mode (if flashed right, put under pda in odin), however if you put it under bootloader box, than it might flashed kernel on bootloader partition which deffinatly makes hard brick.
Sent from my GT-I9300 using xda app-developers app
Can you enter download mode with 3 button combination?
Sent from my Galaxy SIII
Phone is already at the servicecenter as you can read... So those questions do not add anything.
JTAG doesn't take 40 hours btw, takes a lot less.
Sent from my GT-I9300 using xda app-developers app
Ok, what I don't really undertand how all people got the idea that he's speaking about the US version. Yes, he said he got it from t-mobile, but if you buy in germany from t-mobile you'll get the international version also.
L
Why he or she doesn't give us the answer?
Really weird guy.
NEXUS 7
I bet its not hard bricked, it would just be soft bricked, if the correct firmware is flashed it shud be back to life...
Sent from my GT-I9300 using xda app-developers app
9Lukas5 said:
Ok, what I don't really undertand how all people got the idea that he's speaking about the US version. Yes, he said he got it from t-mobile, but if you buy in germany from t-mobile you'll get the international version also.
L
Click to expand...
Click to collapse
Because if you do some research and look at the persons other post on xda it is in the T-Mobile galaxy SII section.
Sent from my GT-I9300 using xda premium
I tried
sebarkh said:
Can you enter download mode with 3 button combination?
Sent from my Galaxy SIII
Click to expand...
Click to collapse
I tried the three combo until my fingers went numb I tried so many cables and computers and then I was like this thing isnt doing ANYTHING no vibration NOTHING. The JTAG didnt take the first time around so now they are still "trying" according to them ofcourse. I tried ODIN but it did not recognize my phone so that was no good. I tried everything I knew to try and that why I finally caved and gave it to the JTAG guys.
barbie1215 said:
I tried the three combo until my fingers went numb I tried so many cables and computers and then I was like this thing isnt doing ANYTHING no vibration NOTHING. The JTAG didnt take the first time around so now they are still "trying" according to them ofcourse. I tried ODIN but it did not recognize my phone so that was no good. I tried everything I knew to try and that why I finally caved and gave it to the JTAG guys.
Click to expand...
Click to collapse
Since its 5 days old have u tried warranty replacement?
help!
sebarkh said:
Can you enter download mode with 3 button combination?
Sent from my Galaxy SIII
Click to expand...
Click to collapse
this happened to my phone. and yes i can enter odin but idk what to flash!
Hello,
I have the following problem and I'm wondering if it is solvable:
My Galaxy S2 (actually from a friend) was rooted and working fine on ICS.
Then I wanted to install a custom rom (Resurrection Remix 3.0.9 Jelly Bean).
It is not my first time doing this as I've did it a multiple times on my own S2.
The same ROM is working fine on my own S2.
Somewhere around 50% of installation, the phone turned itself off.
We did make sure that the battery was fully charged before proceeding with the installation.
Now I cannot Start it.
Can't enter Recovery Mode.
Can't enter Download Mode.
The screen just remains black as if there is no battery in it.
Swapped battery, but still same issue.
It doesn't even show the charging animation when power cable is plugged in.
I have ordered a USB JIG to put it in Download Mode from MobileTechVideos.com but I don't think this will work because there is no sign of life.
It is obviously hard bricked.
What could I do to fix this problem?
Thank you
Sad to say but you have to avail JTAG services to sort this out
Sent from my GT-I9300 using xda premium
Which method did you use? Also, do you have your firmware/baseband/version of ICS the phone was running when this happened? If its the emmc brickbug, dont waste your money on a jig or JTAG. Neither will be of any use.
Sent from my GT-I9100 using xda app-developers app
HAXTREME said:
Which method did you use? Also, do you have your firmware/baseband/version of ICS the phone was running when this happened? If its the emmc brickbug, dont waste your money on a jig or JTAG. Neither will be of any use.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I don't know the exact baseband version.
The last three charachters were LQ6.
If I remember correctly it was I9100XXLQ6
What exactly is the emmc brickbug?
Is there a solution for this one?
dinci5 said:
I9100XXLQ6
What exactly is the emmc brickbug?
Is there a solution for this one?
Click to expand...
Click to collapse
Ah.. ICS 4.0.4?
http://forum.xda-developers.com/showthread.php?p=28388184
There's no solution. Insert he battery and wait for a bit. If it starts to heat up a lot around the camera, I'm sorry to say the phone is utterly useless from now on. Only a motherboard replacement will help.
Sent from my GT-I9100 using xda app-developers app
HAXTREME said:
Ah.. ICS 4.0.4?
http://forum.xda-developers.com/showthread.php?p=28388184
There's no solution. Insert he battery and wait for a bit. If it starts to heat up a lot around the camera, I'm sorry to say the phone is utterly useless from now on. Only a motherboard replacement will help.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thank you HAXTREME.
That's not very good news but at least I know now.
btw yes, it was ICS 4.0.4
I've rooted a couple of android phones without any trouble.
I honestly didn't know that this bug existed even though I searched on the net for the risks before I started it.
I guess Samsung will not fix this under warranty?
dinci5 said:
Thank you HAXTREME.
That's not very good news but at least I know now.
btw yes, it was ICS 4.0.4
I've rooted a couple of android phones without any trouble.
I honestly didn't know that this bug existed even though I searched on the net for the risks before I started it.
I guess Samsung will not fix this under warranty?
Click to expand...
Click to collapse
Thats why everyone keeps screaming to read up before rooting, mate. Its kinda hard to miss, every third thread seems to have a mention of it. And a sticky in the general section.
Anywho, whats done is done. Bad luck I guess. If you're under warranty, theres hope yet. You can take it to them saying it randomly died out and you have no idea how or why. Since the motherboard is toast, they have no way of figuring out you rooted it (or tried to). Say it happened when you kept it to charge or something. You could get lucky. :fingers-crossed:
Use the thanks button instead of typing out a post.
Hope it works out. Good luck. :good:
If your still under warrenty they usually repair it for you, had mine repaired recently. they will replace the motherboard. Good Luck