Please bare with me.
This is the second time this particular problem has happened to my device.
So I was on the tram coming back from my maths exam today.
(Running a ROM with Hardcore's SpeedMod K2-15)
I decide to change the song, all of a sudden, my screen turns black and I can't turn my phone back on. I as soon as it happened I thought uh oh. (the battery was at 74%.
So I tried to reboot my phone, didn't work.
Tried to get into download mode, didn't work.
Tried to get into recovery mode, didn't work.
Went to see if anything happened if I put in my charger AND USB cable. Both instances nothing happened.
When the incident happened last time, I was about to have it shipped to Samsung, was in the car on the way there and I was still pressing the power button in hope that it would work. Low and behold, it turned on, I flashed a different ROM and kernel and was on my merry way until today.
After browsing Q&A for around an hour the only other instances I've found with this problem are my original thread (around a month ago) when the same problem occurred.
http://forum.xda-developers.com/showthread.php?t=1302645
And another one I found today whilst browsing.
http://forum.xda-developers.com/showthread.php?t=1289063
also here
http://forum.xda-developers.com/showthread.php?p=18139062
So up to my knowledge this seems like a problem that isn't only a one off if I'm not the only one reporting it.
Is there anything I can possibly do to fix my phone or something to avoid doing so others don't run into the same unfortunate set of circumstances?
PS. two days ago I deleted a few folders on my USB storage as they were taking up too much storage space. I doubt they had anything to do with the problem though and that's the only difference I can think of that MAY have trigged the event. But I have no reason as to why it happened. I am also using NoMoarPowah and Chainfires3D mod (which I've been using for ages and i'm sure had nothing at all to do with the problem)
hopefully someone knows of a definite solution. :\
Wow the same thing is happening to my phone as well. Thanks for the detailed description. Hopefully we'll find a response soon. Also, I would suggest you investigate the volume of chode in the nearby vicinity of your phone, may be a problem (personal experience)
I just dropped mine off a stepladder in kfc, and i'm experiencing the same problem. Avoid doing this. Hopefully someone else has a better solution to your problem but for now, just don't drop it off any stepladders.
x0x0 leopardkitty69
pokergirl said:
You spelt bare wrong
Click to expand...
Click to collapse
I've made similar mistakes in life. You don't want to mix them up at the wrong time. *Shows bear scars*
leopardkitty69 said:
I just dropped mine off a stepladder in kfc, and i'm experiencing the same problem. Avoid doing this. Hopefully someone else has a better solution to your problem but for now, just don't drop it off any stepladders.
x0x0 leopardkitty69
Click to expand...
Click to collapse
ALSO Don't dinosaur with it, nor allow for sluts to touch it xoxoxoxoxoxoxoxoxox bb <3
pokergirl said:
last edited by pokergirl; today at 01:04 pm. Reason: I did it wrong!
Click to expand...
Click to collapse
you're doing it wrong!
Too late for the sluts, they're all over it! x0x0x0x0x0x
H3h3
H3h3h3h3h3h3h3h3h3 its ****ed darl <3 xxxxxx
Leopardkitty69 stop degrading urself g1rL g3t urs31f @ [email protected] xo
- A girl who knows how to control balls
leopardkitty69 said:
I just dropped mine off a stepladder in kfc, and i'm experiencing the same problem. Avoid doing this. Hopefully someone else has a better solution to your problem but for now, just don't drop it off any stepladders.
x0x0 leopardkitty69
Click to expand...
Click to collapse
I dropped it quite hard and it caused corruption on /efs partition.
lol'd
This thread has suddenly become a lot more interesting.
pokergirl said:
Through implementing my CAS 89 values and inserting chode = 2x length into my TVM solver i introduced the viagra into my phonem therefore, bringing its pwoer to 9001 and causing for it to groan in pleasure. Through utilising square volume = 2 * x * l with x = your vaginas length and y = The radius of your arsehole i solved this problem. (Personal experience, for more information visit (it made me delete the link))
P.s chodemaster - Your personal experience is obviously limited and incredibly detrimental to the phone. When YOU have caught all 151 original chodes you should post in this forum in a SERIOUS and well rounded individual manner
P.P.S NEED MOAR PYLONS
P.P.P.S THIS IS YOUR BIRTHDAY CARD FOR NEXT YEAR
Click to expand...
Click to collapse
Sigh I really need a solution. Not thread spam >.<
This sounds like a serious issue with your phone's hardware. You should return it to Samsung.
with the phones hardware itself?
If they manage to fix it do you think the'll notice it's been rooted?
I've removed the triangle and reset the flash count i've just got a new ROM on it.
(as in will it still be under warranty)
If you manage to reset the counter and get the original stock rom on it (or a new version which was meant for your device and came by kies) you should be perfectly fine, just don't root it again (until you get it back, that is).
Freakgs said:
If you manage to reset the counter and get the original stock rom on it (or a new version which was meant for your device and came by kies) you should be perfectly fine, just don't root it again (until you get it back, that is).
Click to expand...
Click to collapse
but it currently won't turn on at all ;|
giga502 said:
but it currently won't turn on at all ;|
Click to expand...
Click to collapse
In that case chances are very high that Samsung will simply replace it, given that they probably won't be able to turn it on, too.
That's what I've heard from many people atleast, who had issues turning their devices on.
Only way to find out: see if you can get warranty.
Other option: be honest that you rooted and hope for the best, yet I don't know how Samsung staff would react to that, probably not too good.
Ps:
I take it that you have a JIG and tried that one already? As you stated, that you did reset the counter.
Freakgs said:
In that case chances are very high that Samsung will simply replace it, given that they probably won't be able to turn it on, too.
That's what I've heard from many people atleast, who had issues turning their devices on.
Only way to find out: see if you can get warranty.
Other option: be honest that you rooted and hope for the best, yet I don't know how Samsung staff would react to that, probably not too good.
Ps:
I take it that you have a JIG and tried that one already? As you stated, that you did reset the counter.
Click to expand...
Click to collapse
I've given it to a friend but I highly doubt it would work. Anyway for now, I'm going to place it in rice JUST IN CASE there is a tiny bit of moisture on some part of the motherboard which is messing things up. If that dosn't work i'm going to go down to my mobile dealer and hope for the best
thanks for your help!
One question: Did you pull the battery, and put it back in?
I have had this sometimes before, it seems to be caused of overheating... But I'm not 100%. I have checked Logcat but nothing in there of interest.
ante0 said:
One question: Did you pull the battery, and put it back in?
I have had this sometimes before, it seems to be caused of overheating... But I'm not 100%. I have checked Logcat but nothing in there of interest.
Click to expand...
Click to collapse
no I havn't done that. I'm taking it back later today
Related
Hello everyone,
Firstly, I did not find a board dedicated to the S5660. So I posted it here.
Today, I tried to backup my current installation of Android to my SD. I used
a guide on androidpolice(dot)com, while searching for "complete android backup" in Google.
My phone had to be rooted, which it was, so I went on to download and install Clockworkmod's ROM Manager. I opened it up, fixed the permissions and made a backup. Before I could make one, I had to pick a phone model. However, these were all very strange types or brands I never even heard of.
I randomly picked one, and my phone NOT being listed should have served as a warning but alas, and the app started backing up. After it was done, it all seemed normal so I pressed "home" to go back to my main screen and pressed the "lock/power" button so my screen would turn off. I put the phone in my pocket.
Exactly 2 minutes later, I pull out my phone and I notice the screen is black, I push the lock/power button: nothing happens. I hold the lock/power button in the expectation that the phone will boot up since it might have been shut down accidentally. Nothing happens.
I remove battery, re-insert battery. I repeat this over a dozen or so times to no avail. I try the download or safe boot key-combinations (volume down + home + power) and nothing helps.
It's as if either all the keys are broken, something went seriously wrong in the interior hardware or hopefully, (the most simple possibility) my battery gave the ghost.
I went to the shop where I bought the Galaxy Gio and told them about the issues I had, they said they were going to send it to a Samsung Service Center for repairs. After I went home and had browsed the Internet for some possible solutions, I returned to the shop to try out several of the tricks that were listed (inserting battery on the exact same time when you press the buttons), nothing worked.
Does this smell to bricking or just a dead battery?
Before any conclusions are made (it sounds like its bricked though)...dead battery?... Did you try charging it?
Theonew said:
Before any conclusions are made (it sounds like its bricked though)...dead battery?... Did you try charging it?
Click to expand...
Click to collapse
It happened while I was at school, I immediately went to the shop and the guy helping me said he had plugged it in for a short while. I guess I believe him since I did not see it but he said the phone did nothing.
But how come a software malfunction can mess up the physical buttons like the power/volume or lock buttons?
Darmvlinder said:
But how come a software malfunction can mess up the physical buttons like the power/volume or lock buttons?
Click to expand...
Click to collapse
If the software of a device is corrupted, then the hardware won't work properly (if at all). Example: you flash a rom for a device with one button and your device has five, then of course the software wouldn't recognize the other buttons (this is just an example of the hardware part cause if you actually did that, your device wouldn't even start). Also, you said that you just randomly chose one made for another device, for future reference: NEVER flash a kernel, rom, etc. not made for your device or atleast not stated to work on your device.
Theonew said:
If the software of a device is corrupted, then the hardware won't work properly (if at all). Example: you flash a rom for a device with one button and your device has five, then of course the software wouldn't recognize the other buttons (this is just an example of the hardware part cause if you actually did that, your device wouldn't even start). Also, you said that you just randomly chose one made for another device, for future reference: NEVER flash a kernel, rom, etc. not made for your device or atleast not stated to work on your device.
Click to expand...
Click to collapse
Yes, I figured this when I tried to do the actual backup but it seems I was too stupid to stop the entire process.
I have already given it to the store as they will send the phone to a Samsung Service Center. Do you know how the processes of repairing for such phones work?
Also, if the phone is a total brick, it cannot be recovered whatsoever?
Darmvlinder said:
Yes, I figured this when I tried to do the actual backup but it seems I was too stupid to stop the entire process.
I have already given it to the store as they will send the phone to a Samsung Service Center. Do you know how the processes of repairing for such phones work?
Also, if the phone is a total brick, it cannot be recovered whatsoever?
Click to expand...
Click to collapse
The best thing to do is hope they can't repair it . If they happen to get it to work and find out you rooted it, they will just return it to you the way it is now. I hope you didn't tell the guy how this happened...
P.S. - No, I don't know the process they use to recover something like this. I'm no expert in recovering hard bricks (know a few stuff, but not in this case).
Theonew said:
The best thing to do is hope they can't repair it . If they happen to get it to work and find out you rooted it, they will just return it to you the way it is now. I hope you didn't tell the guy how this happened...
P.S. - No, I don't know the process they use to recover something like this. I'm no expert in recovering hard bricks (know a few stuff, but not in this case).
Click to expand...
Click to collapse
The guy asked me whether I had ever let the phone come into contact with water or fluids or if I ever let it fall down to the floor, neither of which have happened in the past. I also told him an update through Kies went awry and caused the system to be unstable till the crash of today.
The dude seemed pretty confident in that the warranty would cover. I don't know. I feel like a giant moron, to be honest.
Darmvlinder said:
The guy asked me whether I had ever let the phone come into contact with water or fluids or if I ever let it fall down to the floor, neither of which have happened in the past. I also told him an update through Kies went awry and caused the system to be unstable till the crash of today.
The dude seemed pretty confident in that the warranty would cover. I don't know. I feel like a giant moron, to be honest.
Click to expand...
Click to collapse
Another future reference (although you dodged the bullet here): never tell your manufacturer (or whoever is supposed to look after the warranty of your device,etc.) that you rooted (or even tried to root) your device. Well, you just have to hope for the best now .
Theonew said:
Another future reference (although you dodged the bullet here): never tell your manufacturer (or whoever is supposed to look after the warranty of your device,etc.) that you rooted (or even tried to root) your device. Well, you just have to hope for the best now .
Click to expand...
Click to collapse
I just sat through a Live Chat session with Samsung. Even though Google does not oppose rooting, Samsung effectively makes a deal out of it. I told him the same story, that an update through Kies made several things pop up on my phone which I did not understand etc. etc.
I am hoping for the best. But I am befriended with someone working in the store that sold the phone to me. He said most techs won't bother with low-budget smartphones (as in trying to grab you by the balls) and will much rather flash the phone with Samsung stock ROM.
Hi,
I read and followed lots of excellent threads on here and successfully rooted my S2. I then flashed it with the Revolution ROM which worked fine, later tried the VK + Siyah which also ran fine.
Today I decided to try WajkIUI but after flashing and rebooting, the phone reset, the button lights came on and then it hung. Now I can't get a thing out of it, no booting, no recovery mode and no sign of it in ODIN.
It sounds completely hard-bricked but I don't really understand how it can be.
Any ideas?
Have tried soft and hard resetting but nothing.
Cheers
Without recovery mode your last best (remote) chance before you send it to Samsung would be a jig.
That's what I was thinking but why would it hard brick if the flash had worked?
And if I send if back to Samsung the warranty will be void anyway won't it?
Unfortunately that one's like asking how long a piece of string is (in other words, who knows ?). If it's a case of the NAND being stuffed as a result of the flash, a JTAG repair may fix it, but you won't know that until/unless you send it to a JTAG repairer.
It may be a hardware issue, cpu might have carked it or something.
Yeah, you've pretty much voided the warranty by putting non-stock firmware on it, but at the end of the day if Samsung can't tell it's been messed with you might get away with a warranty repair/replacement.
You'll only know that if you send it in to them to be looked at. So I guess you've got two choices to consider (not including the remote chance of the jig getting you into download mode).
I guess you could try another battery. Always the possibility it might have died.
Crap. Well, I'll give a jig a go and if that doesn't work then send it back and see what happens.
@ op
did you tried the key press combination to get into download mode? the things you have done has a very less possibility of hard brick.
That's what I thought, but no combination seems to work.
Was the battery full when you flashed?
Sent from my GT-I9100 using Tapatalk
Think it was about 96%.
You never know, it might just be a completely knackered battery. If you're planning on getting it fixed come what may, spending 20 bucks or whatever they cost in your country on another battery won't be the waste of money you might initially think.
If it doesn't fix this problem, at least you'll have a 2nd battery when you do get it fixed. I know I've found having a 2nd battery a godsend since I got mine a month ago, has come in really handy on trips where I've been away for more than a day and has meant I haven't had to worry bout bringing a charger along.
Could a battery just die like that? Seems a bit of coincidence.
Dunno. Anything's possible I guess. Yeah you're right, that would be coincidence. Given what you were doing when it died, I'm betting the NAND is shot & it will need to be JTAG'd either by Samsung or someone else.
mraquinn said:
Could a battery just die like that? Seems a bit of coincidence.
Click to expand...
Click to collapse
Which sucks. That said, according to a site in the UK it costs about £8 plus postage. Have ordered a USB jig just in case, and for £3 it's worth a go.
The really annoying thing is whether to root again if/when I do get it sorted. Am also checking with my network, see if they'll have a go under warranty and I'll forget to mention I was rooting it.
MistahBungle said:
Dunno. Anything's possible I guess. Yeah you're right, that would be coincidence. Given what you were doing when it died, I'm betting the NAND is shot & it will need to be JTAG'd either by Samsung or someone else.
Click to expand...
Click to collapse
On that note....if I wanted to upgrade to ICS, how would that be done without rooting - ie. would the counter look the same? (Long shot)
Yeah if you're going to get it fixed, chances are you'll end up flashing/rooting it again, so the jig will come in handy.
I guess that's something you'll need to decide when you get it back/get a new one. What happened to you isn't the norm tho. The large majority of flashes go smoothly for most people. But the reality is, every time you do it, you do run that small risk of it barfing for any number of a gazillion reasons (which are normally impossible to discover once it's happened). That's the risk people like us who frequent sites like this take.
Yeah if they/Samsung can't tell what happened to it, you'll possibly get away with it. And the fact you rooted it isn't information you have to volunteer to them by any means As to exactly what you should tell them, that's up to you.
Edit to add - Let us know how you get on once you have it sorted. Always useful to have people's experiences on here to give other people it happens to some kind of idea of how it might go down.
mraquinn said:
Which sucks. That said, according to a site in the UK it costs about £8 plus postage. Have ordered a USB jig just in case, and for £3 it's worth a go.
The really annoying thing is whether to root again if/when I do get it sorted. Am also checking with my network, see if they'll have a go under warranty and I'll forget to mention I was rooting it.
Click to expand...
Click to collapse
Well, according to the boffins online I have to go into a store to see if they can repair it. Hopefully they won't be able to check whether it's been rooted or not instore. In fact, if they can't power it on, I don't see how they could.
Random technical question: how can a software/firmware fault stop the hardware from even starting?
My only reference is building a PC - even if you knacker the BIOS and the harddrive, it will still power on so you can access them to put them right.
mraquinn said:
Random technical question: how can a software/firmware fault stop the hardware from even starting?
My only reference is building a PC - even if you knacker the BIOS and the harddrive, it will still power on so you can access them to put them right.
Click to expand...
Click to collapse
Firmware includes the boot sequence and recovery sequence on Android .
power goes to boot on file in effect
Or key combination goes to load recovery or download .
jje
Is that a bit of a flaw, for circumstances just like this?
And, does this mean that the USB jig has no chance of working - or is that the exact reason it might work?
JJEgan said:
Firmware includes the boot sequence and recovery sequence on Android .
power goes to boot on file in effect
Or key combination goes to load recovery or download .
jje
Click to expand...
Click to collapse
i thing jig can solve the problem
So I sent my Atrix for repair as I couldn't stand the random reboots. It came back unfixed. I sent it again, this time warning Motorola that I wouldn't be ok with it coming back unfixed again and so it got back finally fixed.
However, the phone doesn't recognize the multimedia dock anymore ! Media center through HDMI works fine but not the dock : the phone doesn't charge nor does the audio work through the speaks I plug the dock to.
Do you think this is a software issue or an hardware one, something they messed up while repairing it.
If I have to send it one more time, I'll go nuts...
Thanks !
DannyBiker said:
So I sent my Atrix for repair as I couldn't stand the random reboots. It came back unfixed. I sent it again, this time warning Motorola that I wouldn't be ok with it coming back unfixed again and so it got back finally fixed.
However, the phone doesn't recognize the multimedia dock anymore ! Media center through HDMI works fine but not the dock : the phone doesn't charge nor does the audio work through the speaks I plug the dock to.
Do you think this is a software issue or an hardware one, something they messed up while repairing it.
If I have to send it one more time, I'll go nuts...
Thanks !
Click to expand...
Click to collapse
I'd guess that those things worked when it left, but not when it came back, that it would be a hardware issue if the software was unchanged. Just a thought though, do you have any mods installed or are you running a pure stock ROM?
Maybe they've noticed CM7 is better than their stock and they flashed CM7. :highfive:
lehjr said:
I'd guess that those things worked when it left, but not when it came back, that it would be a hardware issue if the software was unchanged. Just a thought though, do you have any mods installed or are you running a pure stock ROM?
Click to expand...
Click to collapse
Pure stock. And yes, it was working before it left for repair...
DannyBiker said:
Pure stock. And yes, it was working before it left for repair...
Click to expand...
Click to collapse
In that case I would say it's very likely that they broke something else. Their Facebook staff may be able to put you in touch with someone who can help as well as they seem to have access to people that the CSR's don't, or they may just delete your post. Motorola's Facebook did have a large number of complaints regarding issues with repairs a couple months ago, but they suddenly disappeared, most likely due to trying to do damage control (reputation management). There's also their forums, where the discussion of anything other than stock functionality is pretty much taboo. But yes, if it worked before, it should work now.
lehjr said:
In that case I would say it's very likely that they broke something else. Their Facebook staff may be able to put you in touch with someone who can help as well as they seem to have access to people that the CSR's don't, or they may just delete your post. Motorola's Facebook did have a large number of complaints regarding issues with repairs a couple months ago, but they suddenly disappeared, most likely due to trying to do damage control (reputation management). There's also their forums, where the discussion of anything other than stock functionality is pretty much taboo. But yes, if it worked before, it should work now.
Click to expand...
Click to collapse
Was it sent in on warranty or did you pay to have it fixed. Either way I feel for you because I know I sent my 2 atrixes in total of 3 times and even though they were fixed/replaced under warranty I still paid about $45 shipping in the end. Everyone on atrix forums keeps praising motorola build quality but I have failed to see it in mine or my wife's atrixes.
affiatic said:
Was it sent in on warranty or did you pay to have it fixed. Either way I feel for you because I know I sent my 2 atrixes in total of 3 times and even though they were fixed/replaced under warranty I still paid about $45 shipping in the end. Everyone on atrix forums keeps praising motorola build quality but I have failed to see it in mine or my wife's atrixes.
Click to expand...
Click to collapse
I think we're starting to see quite a few cases of storage related failures. I am a bit perplexed as what some consider to be qualifying characteristics of "build quality" myself.
lehjr said:
I think we're starting to see quite a few cases of storage related failures. I am a bit perplexed as what some consider to be qualifying characteristics of "build quality" myself.
Click to expand...
Click to collapse
I myself see having to send them in on hardware issues within the 1st year as poor build quality. A new replacement they sent me froze on GPS then would not boot past moto screen as if it bricked itself. Was replaced with another new one after another 15$ I paid for shipping
I think some think USA company means quality. My new atrixes shipped from Mexico
Yeah, I'll have to pay to send it back again as well...
Do you think it's worth trying to flash a custom rom to see if it "fixes" it ?
Thanks.
DannyBiker said:
Yeah, I'll have to pay to send it back again as well...
Do you think it's worth trying to flash a custom rom to see if it "fixes" it ?
Thanks.
Click to expand...
Click to collapse
No, because it's likely that they would use that in order to blame you for whatever is wrong with the device. If it's a hardware issue, no amount of third party software is going to fix it. I would however try to get in contact higher up in the chain of command regarding the issue. It's one thing to ship a device with a defect, it's another thing to have to ship the same device back and forth continuously to get it fixed. And the sad part is that this is just one of many similar stories regarding repairs. I guess that "New Motorola" just isn't quite so new after all.
lehjr said:
No, because it's likely that they would use that in order to blame you for whatever is wrong with the device. If it's a hardware issue, no amount of third party software is going to fix it. I would however try to get in contact higher up in the chain of command regarding the issue. It's one thing to ship a device with a defect, it's another thing to have to ship the same device back and forth continuously to get it fixed. And the sad part is that this is just one of many similar stories regarding repairs. I guess that "New Motorola" just isn't quite so new after all.
Click to expand...
Click to collapse
I would do a factory reset in recovery. My wife's came back with same issues it was sent in with. They replaced the screen for her. The proximity sensor still wasn't working right someone recommended factory reset from recovery. It fixed it for her. Before that I knew nothing about stock recovery
affiatic said:
I would do a factory reset in recovery. My wife's came back with same issues it was sent in with. They replaced the screen for her. The proximity sensor still wasn't working right someone recommended factory reset from recovery. It fixed it for her. Before that I knew nothing about stock recovery
Click to expand...
Click to collapse
Hmmm, I was assuming that was already done
lehjr said:
Hmmm, I was assuming that was already done
Click to expand...
Click to collapse
Yes but sometimes people don't realize there is more than one way to do a factory reset on stock. Until about a year ago I thought you could only do this through settings. Recovery is the best way I now know
A good tutorial for that ?
'Cause that's what I meant when I asked if flashing a custom ROM would help : can it be something that isn't properly setup at a software level ? I tried flashing the stcok rom again with RSDLite but it didn't delete any data so I'm not sure it really reset anything.
Thanks !
DannyBiker said:
A good tutorial for that ?
'Cause that's what I meant when I asked if flashing a custom ROM would help : can it be something that isn't properly setup at a software level ? I tried flashing the stcok rom again with RSDLite but it didn't delete any data so I'm not sure it really reset anything.
Thanks !
Click to expand...
Click to collapse
You mean a guide to factory reset the device in recovery? I thought that was in the manual, but it isn't, although I did find it here.
So I did a factory reset from Recovery, which worked as all was wiped. However, still no luck with the dock.
The reason I asked if trying to install a custom rom was a good idea is because I'm wondering if flashing another Webtop version or the HDMI-hack could make it work. To be clear : do you think that the fact that the Factory Reset didn't work establishes that it's hardware issue ?
DannyBiker said:
However, the phone doesn't recognize the multimedia dock anymore ! Media center through HDMI works fine but not the dock : the phone doesn't charge nor does the audio work through the speaks I plug the dock to
Click to expand...
Click to collapse
As you're able to attach the HDMI and this works are you sure it's not the dock that's faulty? Had a quick look around and came across this... http://www.atrixforums.com/forum/mo...my-hd-multimedia-dock-useless-without-tv.html also, have you tried to clean ect connectors/ports. Might be worth a try
I should try again but I have two docks and the other one doesn't work either. However, I do feel that the AC connector doesn't feel really stable when inside the dock..it just moves around. I'd have to try with the the other's dock AC cable but it's an UK one and I need an adapter.
The thing is that the dock wasn't touched while the phone was under repair so I don't see how it can break just like that.
As I stated before, connection through HDMI to a TV-set works fine as well as charging with the power cord.
EDIT : saw the link you shared and it feels like the exact same issue indeed !
Well, it's fixed...kinda.
I unlocked it and flashed the "fixed webtop addon" from CSROM. It still wasn't working but with it, I got that the message saying that the device was not in charge anymore when I disconnected from the dock, which it didn't before; it wasn't charging however.
I don't think that was relevant but then I decided to give a look at the dock again and removed the top of it and...tadaaa, it worked ! From what I understand, the dock's connectors were not entering the the phone's inputs enough. I still think it's because they ****ed up during repair but heck, I won't send it back for that...
Good to hear you got it working
just got this, new phone. I've been reviewing all its features, but it's started acting strange. when I plug in to charge, it no longer responds. the only way I got it to power on is after I remove/re-insert battery. I realize different phones will have different functions/settings, but my last phone never had these type of issues. I'm just at a loss as to what's going on. I have another week to return this phone, if it won't operate properly. Any insights would be greatly appreciated. I have the unlocked/no carrier logo, International I9300 version. It's running Android 4.1.1, which is what came installed.
twf498 said:
just got this, new phone. I've been reviewing all its features, but it's started acting strange. when I plug in to charge, it no longer responds. the only way I got it to power on is after I remove/re-insert battery. I realize different phones will have different functions/settings, but my last phone never had these type of issues. I'm just at a loss as to what's going on. I have another week to return this phone, if it won't operate properly. Any insights would be greatly appreciated. I have the unlocked/no carrier logo, International I9300 version. It's running Android 4.1.1, which is what came installed.
Click to expand...
Click to collapse
Hi I will save you alot of trouble here... Return the phone...Your phone should not be doing this especially a new one even if you can fix this it is something that is not normal and can spell trouble elsewhere with your phone.
I would recommend returning and getting another one
+1 return it and go for new one. Why to bother when return is an option.
hardware problem..just return it
turns off, won't power on, after/while charging
tallman43 said:
Hi I will save you alot of trouble here... Return the phone...Your phone should not be doing this especially a new one even if you can fix this it is something that is not normal and can spell trouble elsewhere with your phone.
I would recommend returning and getting another one
Click to expand...
Click to collapse
I've done a factory reset & it seems 2 b responding, as it should. I'm hoping it means that just an app, I'd installed, was causing the issue. If not, I've alerted the seller that I'd be returning/exchanging. Does this type of thing tend 2 happen, very often?
Update: OK, it's been over 12 hrs. since I did the factory reset. I've not done anything else, except enter my local settings. I've not logged in 2 any pre-installed apps, either. So far, it's still working fine. Now, should I assume this DID have something 2 do w/an app or what? I'm really trying 2 exhaust all possibilities b4 returning, as this can only be returned, if there IS something actually defective.
Please advise, again.
Thx,
Tereasa
No, only when the user corrupts the firmware/data.
twf498 said:
I've done a factory reset & it seems 2 b responding, as it should. I'm hoping it means that just an app, I'd installed, was causing the issue. If not, I've alerted the seller that I'd be returning/exchanging. Does this type of thing tend 2 happen, very often?
Update: OK, it's been over 12 hrs. since I did the factory reset. I've not done anything else, except enter my local settings. I've not logged in 2 any pre-installed apps, either. So far, it's still working fine. Now, should I assume this DID have something 2 do w/an app or what? I'm really trying 2 exhaust all possibilities b4 returning, as this can only be returned, if there IS something actually defective.
Please advise, again.
Thx,
Tereasa
Click to expand...
Click to collapse
There is no way to really understand what's going on without testing but that takes time and that is something you haven't got seeing as you need to return the phone within a week..
You could install one app at a time test then uninstall that app and move on to the next app to test but that is very time consuming depending on how many apps you had installed. (And it might not even be that what is causing the problem)
You could flash a new stock firmware and test but again that is time consuming plus you don't want to be doing that if you are returning the phone.
I can only tell you what I would do and that is to return it..The reason why I say that is because not having your phone respond when you plug into a charger would be a big issue for me especially on a new phone and like i said in my first post this could be signs of trouble elsewhere.
I would probably ask myself this question... maybe it was just a app or maybe it's something worse "can i take the risk" Phones cost alot of money and I think you should expect them to work without any problems when first purchased.
tallman43 said:
There is no way to really understand what's going on without testing but that takes time and that is something you haven't got seeing as you need to return the phone within a week..
You could install one app at a time test then uninstall that app and move on to the next app to test but that is very time consuming depending on how many apps you had installed. (And it might not even be that what is causing the problem)
You could flash a new stock firmware and test but again that is time consuming plus you don't want to be doing that if you are returning the phone.
I can only tell you what I would do and that is to return it..The reason why I say that is because not having your phone respond when you plug into a charger would be a big issue for me especially on a new phone and like i said in my first post this could be signs of trouble elsewhere.
I would probably ask myself this question... maybe it was just a app or maybe it's something worse "can i take the risk" Phones cost alot of money and I think you should expect them to work without any problems when first purchased.
Click to expand...
Click to collapse
:good:Well, as it turns out, it must be a serious issue w/phone. I've still not logged in/installed any other apps & it's starting do it all, again. So, back it will go. As u said, it's expensive! I really appreciate ur assistance.
[Q] "Retroactive Bricking" or "spontaneous" hardware fault? [Xpost One X/X+ Help]
*PSA: This will be crossposted in xda GenerAL Q&A and HTC One X+ forums, I hope cross posting is allowed, haven't seen it mentioned in rules.*
Hi all,
Quick disclaimer: I've been lurking parts of xda now and again for a couple years now, have flashed a couple of phones and tablets now and again for mainly practical reasons, recently getting more interested in it as a ""fun" interest or "hobby".
SO: I am very aware that this is my first post, the rules, search function, etc. ..
BUT: After extensively searching both google and specifically xda to help me resolve this issue *myself*, I decided to create an account and post. I'm sorry if this Q should have been put in the newbie thread, my assessment was that it probably has no place there.
ALSO PLZ NOTE: What was meant to be a succinct summary and question somehow turned into a condensed but complete rundown of events, so here is a...
TL;DR:
- Replaced HTC One X+ display/digitizer unit myself, ran fine for 5 weeks.
- Then: flashed twrp 2.7x or 2.8, not sure anymore, before installing Android HD Revolution 33.1 by mike1986, and following the official instructions, which ran great for about week until my phone spontaneously BRICKED THE F*CK OUT COMPLETELY.
(yes, true brick, paperweight, robot-corpse, whatever)
=> Question: IS "RETROACTIVE/RETROGRADE BRICKING POSSIBLE/A "THING"??
If so, what could I have done wrong? (POSSIBLY something to do with a bootimage of firmware that I was sure I had the up to date version of... dunno though).
=========================================================================
About 6 weeks ago:
- Cracked the display of my HTC One X+ badly by dropping it onto concrete-type floor at a rave/party
=> Decided to try and replace it myself, researched for a good while (talking several days here, 90s/00s kids),
=> Decided to replace the display/digitizer unit myself to save money and gain knowledge.
Repair process was challenging and nearly as nerve wracking as playing the WSOP (not kidding, have played it three times), had an issue immediately after putting it back together where it suddenly wouldn't charge AT ALL anymore (NO LED), and overheated, and had unusually fast battery drain of its remaining charge (which never ran out completely before resolving that issue, since I kept turning it off whenever possible).
=> Took it apart and put it together again XX times until realizing the power switch flex cable kept slipping out of its two (jawbone?) connectors during putting it back together (I was doing something wrong with the flex positioning).
=> This resolved the issue.
=> Felt like a hero and that I win at life (since this phone has a rep as being hard to meddle with, and this was my first time even opening, let alone taking apart a smartphone).
=> Continued joyful phone shenanigans for over one month.
=> THEN: Decided to root it, mainly because there was a particular app I wanted that required root ("Quick reply for Whatsapp/Pushbullet", for the curious).
My previous, very limited rooting/flashing experiences =
- Google Nexus One (CWM/Cyanogen) a few times, years ago
- Galaxy Tab 10.1 (CWM/Cyanogen 10.1 ages ago, TWRP/Omnirom Kitkat 4.4.4 recently) a couple times.
So, did my research (or so I thought..?) for this particular custom ROM, decided to go for Android Revolution HD for HTC One X/+ 33.1 by mike 1986 (because it looked fckin awesome, and it was, while it ran) and loved the sh*t out of my "new" phone for about a week. Especially the vastly improved battery life seemed almost surreal, a big deal for a fixed-battery phone.
Then, ONE FATFUL EVENING in a bar, I remember looking at my phone and seeing 35% left, (days before it would've been an amazing 70-80% on an avg. day), which may not be relevant as it was my birthday, so had been using it a lot that day => may be a moot point
- Next time I looked at the phone ( < 1 hour without active use for sure) it was dead.
"Hmmmm," thought slightly drunk me. Whatever, charge it later, weird sh*t happens.
- Got home later, charged it over night after booting it with usb cord attached (mains).
Seemed normal, I even set an alarm.
=> Alarm never rang because it was in a powered-off state again come morning, despite all-night charging.
=> It booted to HTC logo. Seconds later, it turned off again. Held down power again, all I saw was the soft touch buttons flashing red a few times. After this it unexpectedly became (or was secretly crowned):
!! COMPLETE AND UTTER FCKNG KING BRICK OF BRICK COUNTRY AND ATTACHED TERRITORIES !!
No power on with or without volume up/down held for whatever amount of time;
No charging, no heating up when "charging";
No LED in any colour or flashing frequency, ever;
No response after hours and days of charging on different USB cables on PC/wall socket;
PCs and laptops don't register a sign of anything when it penetrates their port parts, etc etc...
...
.Even that semi-mystical bright-light-exposure-while-charging "light sensor manipulation" thing (which apparently worked for a lo of people with similar issues) did nothing for the cause.
Promotion: *Paperweight status successfully acquired.* Yay.
=====================================================
Now, obviously my first thought was that the power flex that gave me trouble during display replacement probably slipped again., somehow (I had taped it down solidly I thought).
=> SO I opened it once again, flex position seemed ok, but I wasn't sure of its functionality as it did look kind of battered from the somewhat unprofessional repair I had conducted on it (which I openly admit to, though I really did try my absolute best).
- Spontaneously took mainboard/battery combo to a local independent phone/accessory shop after being told they'd take a look for free
(I was in there was in there buying a microsim adapter so I could use my ancient Nexus One, since my GF has my old S2 now, which she kindly offered back, but its hers now, so nah. Great phone though.)
=>Shop's advice echoed my thoughts: Flex cable may be screwed, I may have damaged it by bending in the wrong direction/too often, and that damage somehow didn't manifest until much later. I didn't mention the recent rooting + flashing as I deemed it irrelevant at the time.
Their secondary thoughts: Battery or mini-usb port fukt, (which would require soldering, which they don't even offer).
=> SO, feeling confirmed in my layman's assessment, I cheaply got a pristine new replacement flex on ebay, double checked all videos/tutorials, implemented the damn thing with considerably more skill/experience and even higher anticipation. What happened next was shocking:
Absolutely nothing, obv.
=> Did an additional epic f*ckton of internet/forum research, found similar problems and some resolutions, but no real answers, probably because my main problem translates to a kind of hybrid question.
So here I am now am with my core question:
Is it possible to FULLY brick an HTC/any smartphone but not become aware of this until one week later, when the device dies OVER ONE WEEK of reliable and amazing performance?
(and if yes, what aspect/stage of the flashing process is this likely related to?)
If the answer is NO, it must be a hardware fault with probability rank (I think)
:
1.) Battery dead for whatever reason
2.) Mini USB OR mainboard/integral component (equal rank as not sure), possibly caused by incompetent repair, but why or how would this express itself over a month later??
3.) Other, which I'm not aware of.
While researching new ROMS for the N1, I realized that I may have messed up on the "bootimg part" of the flashing process of the Revolution ROM, a part I found v. confusing in the instructions, even after rereading them many, many times. It was about the most recent firmware, which I was pretty sure I had anyway, since it was unrooted before and I do remember installing some firmware updates over the air.
I still did my best to follow the instructions though.
=> Maybe this has something to do with it, i.e. the hardware can't accept a charge because the software allowed it to become too uncharged (a fairly paradox concept to me, but apparently it can happen. Guess it's like a BIOS-type thing).
Thank you for anyone who read this far!
As it stands, I refuse to give up hope so soon after experiencing that rush of having fixed it myself.
Any specific or general help, tips, hints, pointers, replacement phones (One M8 or S5 plz., Iphones will go straight on ebay) would and will be greatly appreciated!!
The obvious choice is to get a new battery and see what happens, but I'm not sure if I wanna sink any more money into this phone, only to later find out the mainboard is at fault (not worth the money replacing), AKA "get a new phone without a contract", which would more than suck for me financially atm (Im ignoring my N1 here, which I love, but don't wanna be stuck with, esp. as it has the standard-issue broken power button (which I actually had repaired once under warranty, back in the ol' days of yore some prefer to refer to as 2009.
So guys: What's my move, if there is one, besides going to a local/online service centre (I live in Germany btw.) and probably paying unproportionate cash money to even have it looked at?
Cheers, thanks, merci, danke
PS: Just saw the polling function, so I attached one just for the hell of it, to see what happens (never used one before).
If you feel both qualified AND so inclined as to pass judgement on this here serious business, please indicate what you think may be the cause of my issue.
Poll is in "General QA" Forum original post: http://forum.xda-developers.com/general/help/retroactive-bricking-spontaneous-t2948954
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!
bear.are.cool. said:
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!
Click to expand...
Click to collapse
Oh yea I was meant to reply to this... Reading what I can of this, sounds like offmode charging wasn't working (Sounds like to me not 100% is it)
You can try this http://forum.xda-developers.com/showthread.php?t=2576405 <--- Windows only
That is a last ditch attempt at charging....Which is what it sounds like to me, please tell me If I'm wrong.
And NO, providing your device is S-ON you CANNOT BRICK IT
thanks
Lloir said:
Oh yea I was meant to reply to this... Reading what I can of this, sounds like offmode charging wasn't working (Sounds like to me not 100% is it)
You can try this http://forum.xda-developers.com/showthread.php?t=2576405 <--- Windows only
That is a last ditch attempt at charging....Which is what it sounds like to me, please tell me If I'm wrong.
thanks
Click to expand...
Click to collapse
Thanks for the reply!
I believe I actually ran into that (linked) post during my previous research, but just as is the case now, I don't get how I'm supposed to run a .bat from windows that influences the phone when windows doesn't recognize a thing when I plug the device in. Not in device manager, NADA.
EDIT: I do have S-ON, yes. BTW thanks for trying to help, but again, my fundamental question: Is "retroactive bricking" as I call it possible in theory?
bear.are.cool. said:
Thanks for the reply!
I believe I actually ran into that (linked) post during my previous research, but just as is the case now, I don't get how I'm supposed to run a .bat from windows that influences the phone when windows doesn't recognize a thing when I plug the device in. Not in device manager, NADA.
EDIT: I do have S-ON, yes. BTW thanks for trying to help, but again, my fundamental question: Is "retroactive bricking" as I call it possible in theory?
Click to expand...
Click to collapse
To get it working you need the android sdk tools. You also need to install HTC SYNC + Drivers then uninstall HTC sync leaving the drivers behind.
And In answer to your Q. No
After reading the TL;DR
Lloir said:
To get it working you need the android sdk tools. You also need to install HTC SYNC + Drivers then uninstall HTC sync leaving the drivers behind.
And In answer to your Q. No
After reading the TL;DR
Click to expand...
Click to collapse
Hmm, ok. I'll give it a go. So essentially, if I manage to implement this method correctly and I still get nothing, theres gotta be a hardware fault, correct?
bear.are.cool. said:
Hmm, ok. I'll give it a go. So essentially, if I manage to implement this method correctly and I still get nothing, theres gotta be a hardware fault, correct?
Click to expand...
Click to collapse
Probably
Sent from my Nexus 7 using Tapatalk
Lloir said:
Probably
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm trying to find a good guide on how to go through with this, as the post you linked is helpful but a bit vague.
One more question: When you say "offmode charging" is that synonymous with "offline charging"?
EDIT: Also, what I really do not get about the procedure outlined in the post is the following line
"Run the following script as a batch file while your phone is in USB fastboot mode."
=> How do i put this brick into anything mode?? It's in constant brick mode!
bear.are.cool. said:
I'm trying to find a good guide on how to go through with this, as the post you linked is helpful but a bit vague.
One more question: When you say "offmode charging" is that synonymous with "offline charging"?
EDIT: Also, what I really do not get about the procedure outlined in the post is the following line
"Run the following script as a batch file while your phone is in USB fastboot mode."
=> How do i put this brick into anything mode?? It's in constant brick mode!
Click to expand...
Click to collapse
Just a question. When you replaced the display, did you tamper with brightness control? I mean were you able to change the brightness after your repair?
And secondly, logically, I think its a hardware fault. Whatever happened, might have happened over the week or happened that specific day. Maybe the wire connecting the charger socket to the phone's board got cut/damaged during repair but worked for a while, then it imght have touched another wire and short circuited maybe?
Or maybe something inside was loose, and something happened to the phone, it fell or something, and a component got broken?
I would suggest comparing your internals to the internals of another HOX+ whether on youtube or whatever. And try to check the wire connecting the charger socket to the board. Another possibility is the battery got damaged as you stated. The last idea is, (And I hope it didn't get to that), the wire short circuited and fried the board.
All my theories are just as stated.. Theories, which may or may not be true. If there is an HTC Care center, I would suggest that you go to them, atleast for debugging.
Best of luck