Database Info

Another dead phone

Hi, I have flashed many different roms with no problems on HD2 and Desire S. This evening I thought I would try another Rom (why oh why), so duly wiped and done the usual preparation, but this time it just stuck at HTC for over half an hour, tried rebooting but nothing, tried all the ways on the forum to restart without taking the battery out, in the end I made the stupid mistake of taking the battery out and putting it back in . Well you know the rest, dead phone fried chip I think.
Now my questions are 1) its on contract from Tmobile 6 months ago, the device is obviously S-off so am wondering if I can still get it fixed by them. 2) How much does it cost to have a fried emmc chip replaced if I send it to HTC.
Any help would be greatly appreciated.

I sent it to HTC without the battery and got a repaired phone free of charge
Sent from my HTC Desire S using xda premium

Hi Dan. Can you tell me the process you went through and is your a contract phone

Can you boot into Recovery or Bootloader? The bootloop can be caused by many reasons, not only eMMC

Hi, can't boot into anything , the phone is just dead, doesn't do anything, no power.

correct me if im wrong but dosnt emmc failure still boot? im not 100% sure thats your problem

Ok, but I tried everything to power up with no luck, I know there was at least 80% battery when I used it, also nothing when I plug it in to the mains.

pandollar said:
Hi, can't boot into anything , the phone is just dead, doesn't do anything, no power.
Click to expand...
Click to collapse
This is a completely bricked phone (whatever the reason that caused it). But in this case the repair cannot state that it is S-Off. So go ahead for a replacement. There is a way to unbrick it (JTAG), but never heard so far that the HTC repair centres use that - all the problematic devices were just replaced, not repaired. Good luck

Ok, I will have to try and get them to replace it then. Many thanks for your help.

amidabuddha said:
This is a completely bricked phone (whatever the reason that caused it). But in this case the repair cannot state that it is S-Off. So go ahead for a replacement. There is a way to unbrick it (JTAG), but never heard so far that the HTC repair centres use that - all the problematic devices were just replaced, not repaired. Good luck
Click to expand...
Click to collapse
This is great..I have two bricked phones lying about that I have no idea what to do with...

virtu0s0 said:
This is great..I have two bricked phones lying about that I have no idea what to do with...
Click to expand...
Click to collapse
Find a person in your area that owns a JTAG, there is a great chance to fix them.

Did i just brick my phone?

I think i just bricked my phone. I am trying to return to S-on and after following all the instructions in the main sticky, i wrote the SUPERCID back to tmobile, and put in the writesecuflag 3 command, and rebooted the bootloader. Now the phone will not turn on at all. Won't power on regular and cannot turn it on into the bootloader. When i plug the phone into the computer QHUSB-DLOAD comes up in the device manager as to what it is saying it is attatched as. Adb shows no devices and RUU's cannot find the device. Omg i really hope i didnt hose this phone.

Did you flash first the ruu that came with your phone?
Sent from my HTC Sensation Z710e using XDA App

and1kar said:
Did you flash first the ruu that came with your phone?
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Nope i used the tmous 1.50.

I am pretty sure you forgot to run the RUU, and sadly yes I have to inform you that it is bricked :/

xsteven77x said:
I think i just bricked my phone. I am trying to return to S-on and after following all the instructions in the main sticky, i wrote the SUPERCID back to tmobile, and put in the writesecuflag 3 command, and rebooted the bootloader. Now the phone will not turn on at all. Won't power on regular and cannot turn it on into the bootloader. When i plug the phone into the computer QHUSB-DLOAD comes up in the device manager as to what it is saying it is attatched as. Adb shows no devices and RUU's cannot find the device. Omg i really hope i didnt hose this phone.
Click to expand...
Click to collapse
Sounds like you bricked it, yes :s

Thanks for the replies guys.

Since i got it from craigslist my only hope is paying htc to repair it i'm assuming?

It should still be covered by the original warranty right?

LooieENG said:
It should still be covered by the original warranty right?
Click to expand...
Click to collapse
Just got off the phone with HTC. It is still covered under their warranty. Hopefully since all my void stickers in good standing, I have no physical damage, was able to get the CID back to Tmous and the write secureflag3 went through, there will be no reason to deny it. Here is hoping! I think EXT4 recovery is still on there though. Hopefully it will be so bricked that they will have to reset it and reload the software to be able to do anything with it

Hope you manage to get it fixed!
A question, I have yet to root my XE, but is SUPERCID a must on a sim free phone if you want to flash roms?

the fact is that if it is so bricked that it won't turn on at all they won't check it further. many members achieved to get a new phone as replacement

Just make sure you tell HTC you are the original owner and didnt get it from craigslist.Also DO NOT UNDER ANY CIRCUMSTANCES Mention any hacking forums like XDA,or ROOT, Just claim that it said "an update was available" so you chose to update and the battery died.I've had free repairs under warranty by using that same advice, A friend of mine mentioned root on his nexus one and they charged him for repair even though it was a month old as he voided the warranty

bonesy said:
Just make sure you tell HTC you are the original owner and didnt get it from craigslist.Also DO NOT UNDER ANY CIRCUMSTANCES Mention any hacking forums like XDA,or ROOT, Just claim that it said "an update was available" so you chose to update and the battery died.I've had free repairs under warranty by using that same advice, A friend of mine mentioned root on his nexus one and they charged him for repair even though it was a month old as he voided the warranty
Click to expand...
Click to collapse
I definitely didnt mention xda or flashing roms or anything, and I told them i received it as an anniversary gift (even though i really did get it from craigslist). Told them i rebooted the phone and it just never came back on. Which really is what happened while leaving out a few details lol.

I wonder what would them HTC guys think if they are already among us

same thing happened to me the other day on my evo 3d...gonna send it in to htc as well...hope they won't know...what are the chances of them getting the phone to turn on??
xsteven77x said:
I think i just bricked my phone. I am trying to return to S-on and after following all the instructions in the main sticky, i wrote the SUPERCID back to tmobile, and put in the writesecuflag 3 command, and rebooted the bootloader. Now the phone will not turn on at all. Won't power on regular and cannot turn it on into the bootloader. When i plug the phone into the computer QHUSB-DLOAD comes up in the device manager as to what it is saying it is attatched as. Adb shows no devices and RUU's cannot find the device. Omg i really hope i didnt hose this phone.
Click to expand...
Click to collapse

poktangju said:
same thing happened to me the other day on my evo 3d...gonna send it in to htc as well...hope they won't know...what are the chances of them getting the phone to turn on??
Click to expand...
Click to collapse
From everything i read online it really seems hit or miss depending on the technician you get. More often than not they seem to let things slide even if it seems obvious that they should have been able to see it was rooted etc. Here is hoping . I'm gonna send it out tomorrow and will keep this thread updated with developments if anyone is interested in how it went. I have read some HORROR stories about people sending there phone to HTC and it become missing in action for MONTHS. I really pray to christ that does not happen to me.
O/T a little bit, but how come with just about any other "thing" in life a warranty is good and is tied to the object and not to the person. Even though i got this phone off of craigslist, why should that have ANYTHING to do with it. The phone is the phone and the warranty is the warranty regardless of whose possession it is in. I just don't think tmobile should be able to do that. Also i think it's BS that if you buy a brand new phone and it breaks 2 days later, they give you a refurb and not a new one. How do they get away with this ****!

i think im gonna take my chances as well...the person i talked to at htc did say that if the damages were caused by me then i would have a choice to pay them to fix if not i would have to pay $35 to get the phone back...so this could end up costing the shipping to send phone and the $35 to get the phone back.
xsteven77x said:
From everything i read online it really seems hit or miss depending on the technician you get. More often than not they seem to let things slide even if it seems obvious that they should have been able to see it was rooted etc. Here is hoping . I'm gonna send it out tomorrow and will keep this thread updated with developments if anyone is interested in how it went.
Click to expand...
Click to collapse

Just wondering how this has progressed. Did you send your phone to HTC? Did they say what the potential repair costs could be?

Well i sent it out on 12/21 and they received it on 12/28. On the tracking website, it says "In repair". From experience, if it is going to have any issues or gonna charge you any money, it says under review until you have spoke to them and made arrangements or paid them. One thing that is pissing me off good is that every day, the day it says it was received is changed. So everyday i have checked, it went from saying received on 12/28, to 12/29, to 12/30, and now 1/1. So i dont know if that is just the way the system works, or if they are trying to sheist me and take forever and a day like some of the horror stories i have read. Not really sure what their is to do but send a replacement since it is hard bricked and cannot be resuscitated even with professional tools from all the research i have done online. In the meantime, i bought a galaxy s 2 and am LOVING it, except for the lack of development in comparison to here in sensation land!

did you get your phone back?
xsteven77x said:
Well i sent it out on 12/21 and they received it on 12/28. On the tracking website, it says "In repair". From experience, if it is going to have any issues or gonna charge you any money, it says under review until you have spoke to them and made arrangements or paid them. One thing that is pissing me off good is that every day, the day it says it was received is changed. So everyday i have checked, it went from saying received on 12/28, to 12/29, to 12/30, and now 1/1. So i dont know if that is just the way the system works, or if they are trying to sheist me and take forever and a day like some of the horror stories i have read. Not really sure what their is to do but send a replacement since it is hard bricked and cannot be resuscitated even with professional tools from all the research i have done online. In the meantime, i bought a galaxy s 2 and am LOVING it, except for the lack of development in comparison to here in sensation land!
Click to expand...
Click to collapse

Purchasing a potentially bricked Sensation; Advice and Suggestions?

Hey guys. I have a chance to pick up a mint sensation locally for a cheap price. The seller is under the impression it is bricked. I've read through the threads for a while now but thought I would ask for some help/advice. The seller told me that he bricked the phone by trying to unroot it but has also said he was trying to "flash boot or something." He has made it clear that the phone will not turn on or show any signs of life. He has tried multiple batteries as well.
So, is there any way to ensure it is bricked? I had thought that maybe he messed up flashing a new rom.
If it is clearly bricked, what would be a good price to snag it for?
Would it be possible to buy it and contact HTC in regard to the warranty? What would this cost?
Thanks in advance,
PS; I have read about the inablility to charge after flashing CWM. I'm not sure if CWM was installed or not. I will ask that asap.

Sounds like an inappropriate file was flashed to hboot, in which case it's dead. Short of jtagging there is no way to fix it.

Thanks for the quick reply globatron. That sucks to hear that it probably is fried. Would the HTC warranty cover this type of repair?

MRpeabodyia said:
Thanks for the quick reply globatron. That sucks to hear that it probably is fried. Would the HTC warranty cover this type of repair?
Click to expand...
Click to collapse
No, they wouldnt as it was from user error.
Matt

Do you know for sure they wouldn't cover it? All morality aside it could be argued that it wasn't user error considering I'm not entirely sure what the seller did to it.

MRpeabodyia said:
Do you know for sure they wouldn't cover it? All morality aside it could be argued that it wasn't user error considering I'm not entirely sure what the seller did to it.
Click to expand...
Click to collapse
Well,morality aside you can always tell them that the OTA update bricked it.If you are a TMOUS customer you can try and contact T-mo first.They are usually easier to deal with than HTC.

NYCguy I read through your thread discussing your dealings with Tmous. I had thought about contacting them but they have been a huge pain for me lately. (Almost to the point of ending my contract). I shot HTC an email out of curiousity so I should hear back from them soon. I've had to replace a phone before via T-mobile and it was pretty smooth. I just don't want to do it all the time as this may look odd on their end.

NYCguy I read through your thread discussing your dealings with Tmous. I had thought about contacting them but they have been a huge pain for me lately. (Almost to the point of ending my contract). I shot HTC an email out of curiousity so I should hear back from them soon. I've had to replace a phone before via T-mobile and it was pretty smooth. I just don't want to do it all the time as this may look odd on their end.

Well I bought my "bricked" sensation. I spoke with the seller for a while and it seems he had rooted it, received notification of the OTA, and attempted to unroot it. He didn't give me specifics on the procedure he used but I'm going to read as much as I can, depending on when my monster child will let me, and attempt to fix this thing. I read about the battery tricks and will try those tonight. Any suggestions as this point guys?

Well after reading and tinkering with this thing for a while it seems I have the dreaded qhsusb brick. I already spoke with HTC and it is under warranty until November of 2013. My new question is, Will HTC be able to tell the device was ever rooted? A rom was never installed so it should be stock. Seems the seller made a mistake in trying to go from s-off to s-on. Just hoping I won't have to pay much to have a new one sent from the manufacturer.
Thanks

MRpeabodyia said:
Well after reading and tinkering with this thing for a while it seems I have the dreaded qhsusb brick. I already spoke with HTC and it is under warranty until November of 2013. My new question is, Will HTC be able to tell the device was ever rooted? A rom was never installed so it should be stock. Seems the seller made a mistake in trying to go from s-off to s-on. Just hoping I won't have to pay much to have a new one sent from the manufacturer.
Thanks
Click to expand...
Click to collapse
Well if it's a QHSUB brick that means the phone is truely DEAD.If you can't boot into bootloader,can't charge it and can't connect to a PC,then i don't see how could they tell if it was rooted or not.There is no way for them to tell.You just tell them you bricked it while trying to install the OTA update,or do as i did and contact T-mobile.
Good luck!

Thought I would update this thread for anyone who may stumble across it at a later date. I went ahead and sent my bricked phone into HTC. They repaired the phone and sent it back. I was suprised to see that they didn't send me a refurb.
I have to say that HTC were very easy to work with were quick in returning my phone.

Used RUU, screen doesn't turn on

I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.

I'm guessing you were SuperCID, and S-on? If so, sorry to say you are now bricked.
Should have read this, stickied to the top of General: http://forum.xda-developers.com/showthread.php?t=2181929

Wow. The level of suck here is amazing. Thanks. Nothing that can be done at all?

Jonathan_A said:
When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing.
Click to expand...
Click to collapse
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.

redpoint73 said:
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.
Click to expand...
Click to collapse
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.

Jonathan_A said:
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.

Everyone makes stupid mistakes once in a while. But yeah, that really sucks. If you have access to a Linux computer, you might try the JET tool in Development, or check the unbricking thread in General. But I don't think anyone has been able to come back from this after the 3.18 RUU or OTA + SuperCID.
Beyond that, you can try to find a repair shop that will JTAG the phone. It will cost you, but better than buying a new phone.

iElvis said:
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.
Click to expand...
Click to collapse
Well, it's still under warranty, and I'm hoping that since the bootloader was relocked and the RUU technically succeeded, they'll just send me a new one or something. Though I'll take a whack at the JET thing if I can find my Linux live CD... Thanks a ton, I'm feeling pretty dumb here and you guys have been really helpful.

Jonathan_A said:
I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.

redpoint73 said:
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.
Click to expand...
Click to collapse
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.

Jonathan_A said:
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.
Click to expand...
Click to collapse
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick

exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.

Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
Good luck bud!
Sent from my HTC One X using xda app-developers app

Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.

iElvis said:
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.
Click to expand...
Click to collapse
Ooh, thanks. Good to know. They'll be my next try. You all have probably just saved me ~$300

Jonathan_A said:
I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.
Click to expand...
Click to collapse
Happened to me too :c Has anyone had any luck using JET?

If the emmc partition table is still intact its feasible, but im pretty sure the ruu/ota kills it upon install. who knows why. seems to be a security "feature" since s-off seems to work fine.

Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.

I had a similar issue where my screen wouldn't turn on but it was still on and usable. I went to the AT&T store and got a replacement. Tell them you installed the AT&T update and then the screen stopped working. They probably won't be able to fix it but they'll give ya a new phone if you're under warranty. My phone was far from stock (rooted, bootloader unlocked, S-off, custom kernel and ROM), and they still gave me a new one. Make sure you go to an AT&T store though, I tried three different Best Buys and they were all noobs that had no idea what to do.
Edit: Didn't read post above so you can disregard this. But if you go to a store they can give you a new one on the spot instead of having to wait for one to be shipped to you.

Jonathan_A said:
Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.
Click to expand...
Click to collapse
Since the phone is bricked, there is really no way of them knowing (by checking the phone anyway) that you modded it. And as mentioned, AFAIK there has never been a reported case of AT&T denying warranty service due to the bootloader having been unlocked (and probably aren't even going to check). AT&T is much less strict then HTC, as its in AT&T self interest to keep you as a happy customer (paying that big old monthly bill), rather then fight over something like a single warranty exchange.
There have been some cases of the OTA randomly bricking devices that are fully stock (and probably possible with the RUU as well). Any time you mess with the hboot, if things get interrupted somehow, its possible to brick the phone. So for all AT&T knows, this is what happened in your case.
I'm normally not a big fan of making a warranty claim for your own negligence, and as a result of you modding the phone. But I suppose this is a bit of a gray area, since the RUU really shouldn't brick the phone solely due to SuperCID.
---------- Post added at 10:04 AM ---------- Previous post was at 09:58 AM ----------
exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Did HTC actually deny your warranty service due to a record of you having unlocked the bootloader? Just curious, because it would be the first I have heard of that actually happening.
Yes, as the warning state when you unlock the bootloader, it voids the warranty (at least in theory). But in actual practice, whether they honor the warranty or not after BL unlock seems to be much more of a gray area.
Its true that the carrier will be more lenient than HTC. But I know there was some discussion on the "international" (quad core) One X forum, where HTC was actually honoring the warranty if the bootloader was unlocked. But they were actually denying warranty service if any custom ROM had ever been installed on the device. Even if the device was returned to the stock ROM before sending in. So apparently, they have some way of knowing a custom ROM was previously installed (even if uninstalled). If the phone was bricked, I wonder if they would still be able to check this?
Of course, how HTC honors the warranty may also vary from region to region.

My Phone turn off suddenly, help me please!!

Hey guys. I have a problem I tried to speak Spanish as forums but got HTCMania solve anything.
Before I thought it was problem of CM 11 that I turned off the phone suddenly (not restart, it shuts down) and occurred 1 time every 3 or 4 days, now increasingly occurs more often, yesterday I turned off the phone 6 times, this night while sleeping 3 times went out. It made me late for work again because the phone was turned off and the alarm did not go off ... following tips, did not solve anything. I factory reset everything I installed the stock ROM without root or anything, I installed Paranoid Android, SlimKat, Illusion ... nothing, with all the ROM I just turn off the phone. Not have more than 3 ½ months of use and this has been happening since 1 month. I gather it can be battery problem or the device itself, but it is something that has no solution for me. I live in Venezuela and bought me phone my mother and sent from Spain, along with the bootloader already unlocked, the warranty is not going to accept me or have possibility to send. I have searched a thousand Internet sites (Venezuela because the outside you can not buy anything here) and I do not find the battery moto G, to buy and to me installed in a technical service, but even on Amazon U.S. found nothing .
I fell into despair because I can not find any solution, I've calibrated the battery and also keeps shutting off, so I already was without resources, ideas and nothing to do but to stay with the phone and continuously be aware that if the phone turns off,,,, I have to turn it on again, buy an alarm clock to not be late for work again.
Continue pending if anyone can give me some solution, try anything, because nothing I lose ... buy a phone in this country is an impossible task because notice that a regular phone range Moto G (which is cheaper) costs Complete 4 months my salary.
Again thank you very much for your help and am awaiting any news that they can provide me. Hughs

I can't help you, nor I'll even bother trying.Your phone probably has some hardware fault ( too much gaming on it? ).
But what I wanted to tell you is that, you shouldn't have screwed around with your phone, if you can't afford to lose it. You should have never unlocked the bootloader in first place.
A lesson has been learned.

liveroy said:
I can't help you, nor I'll even bother trying.Your phone probably has some hardware fault ( too much gaming on it? ).
But what I wanted to tell you is that, you shouldn't have screwed around with your phone, if you can't afford to lose it. You should have never unlocked the bootloader in first place.
A lesson has been learned.
Click to expand...
Click to collapse
I unlocked the bootloader because I live far from the site where phone was bought. if phone got any problem I can't send it to warranty anytime so whats suposed I must to do? to be on stock frimware and don't root my phone? so all we must do that? then can't understand why there are lot of scene about root ROMs and all that. of course I know my rosks when I unlock my bootloader and root my phone but is my decission, if noone must unlock the bootloader then this kinds of forums would be useless.
Anytime, this community is the best for this kind of scene, root, ROMs and all around that.
I didn't play too much just played a bit, you really think that suposed hardware problem is because I rooted my phone? I bought it 3 1/2 mounth ago and I didn't have any problem, just 1 mounth ago started with this. I think is a factory problem, maybe hardware maybe battery, but not around root or ROM installed.
I was asking just because maybe someone got the same problem and can help be. I appreciate your cooperation like all kind of cooperation but need solutions, not lessons of what I souldn't do.
Thanks anytime

Replacement batteries can be found on eBay. I'd try that first.

SbM_ said:
Replacement batteries can be found on eBay. I'd try that first.
Click to expand...
Click to collapse
They can't import stuff there that easy, thats one of his main problems.Probably eBay is not an option for him.Not 100% sure about that tho.

liveroy said:
too much gaming on it? ).
You should have never unlocked the bootloader in first place.
A lesson has been learned.
Click to expand...
Click to collapse
What are you saying??? Are you kidding?!?
gaming on a phone dont destroy it :/
"a lesson has been learned" nope because he did not understand what happened

1- you should fomated all your phone ( use TWRP recovery), then flash stock Firmware.
2- after that,you turn off your phone BY YOU and plug chager for 1 day.
3- restart your phone and check.
4- it's my solutions. :thumbup: ,hope it's help.
Sent from my XT1033

agalam84 said:
I unlock my bootloader and root my phone...
Click to expand...
Click to collapse
as u wrote seems an hardware problem so not solvable itself.
u can relock the bootloader the bootloader and remove warning at boot if u want maybe motorola accept it in warranty, i havent clear if u can sent it to them...
when your problem start? after that u did something or itself, maybe something with bootloader
i hope u can solve your problem

AXD96 said:
What are you saying??? Are you kidding?!?
gaming on a phone dont destroy it :/
"a lesson has been learned" nope because he did not understand what happened
Click to expand...
Click to collapse
With that said, I don't think you'll understand even if I paint it for you.
Try reading my post again, give it a thought for a while, eventually it will come to my mind what I'm saying and why.

liveroy said:
With that said, I don't think you'll understand even if I paint it for you.
Try reading my post again, give it a thought for a while, eventually it will come to my mind what I'm saying and why.
Click to expand...
Click to collapse
sorry I do not want to be rude but he want a solution not a moralist