Related
I have sent my sensation back for repair after totally bricking it in the process of returning my device to s-on.
My phone was completely dead, no response from charging, no response from computer adb, fastboot just DEAD!
I tried to supercharge my battery to make sure the recovery was not to blame but no joy there either.
My question is, with my phone in this state, will htc repair be able to tell that i have voided my warranty?? I told them that this happened during an ota update
Any opinions or comments from those who have done the same would be appreciated.
bobsie41 said:
I have sent my sensation back for repair after totally bricking it in the process of returning my device to s-on.
My phone was completely dead, no response from charging, no response from computer adb, fastboot just DEAD!
I tried to supercharge my battery to make sure the recovery was not to blame but no joy there either.
My question is, with my phone in this state, will htc repair be able to tell that i have voided my warranty?? I told them that this happened during an ota update
Any opinions or comments from those who have done the same would be appreciated.
Click to expand...
Click to collapse
Hi,
Sorry to hear about your predicament.
Did you actually manage to get S-ON ?
If not ,then it will be obvious what you have done.
No point in lying about it .
Just come clean or they will think you are taking the p*$$
malybru said:
Hi,
Sorry to hear about your predicament.
Did you actually manage to get S-ON ?
If not ,then it will be obvious what you have done.
No point in lying about it .
Just come clean or they will think you are taking the p*$$
Click to expand...
Click to collapse
I bricked my phone in the final step of returning to s-on...fastboot reboot-bootloader.....ok.....no response from phone DEAD.
Since posting i have checked the tracker for my phone repair and it says that it has been shipped today with no mention of cost. Obviously i haven't recieved the device yet but it looks very promising.
After reading many nightmare stories regarding htc uk repair service, if the information that i have just seen on the tracker is true i.e. phone recieved on 22nd. - dispatched on 23rd., i think that is excellent service especially considering the nature of the fault.
I'll be more buoyant when the phone is in my hands though!
malybru said:
Hi,
Sorry to hear about your predicament.
Did you actually manage to get S-ON ?
If not ,then it will be obvious what you have done.
No point in lying about it .
Just come clean or they will think you are taking the p*$$
Click to expand...
Click to collapse
Yes, they will try to find every reason to make sure the repairs are not covered under warranty...if they dont, then you can say it was your Good Luck!!!
bobsie41 said:
I bricked my phone in the final step of returning to s-on...fastboot reboot-bootloader.....ok.....no response from phone DEAD.
Since posting i have checked the tracker for my phone repair and it says that it has been shipped today with no mention of cost. Obviously i haven't recieved the device yet but it looks very promising.
After reading many nightmare stories regarding htc uk repair service, if the information that i have just seen on the tracker is true i.e. phone recieved on 22nd. - dispatched on 23rd., i think that is excellent service especially considering the nature of the fault.
I'll be more buoyant when the phone is in my hands though!
Click to expand...
Click to collapse
Hi,
Hope all goes well.
Well, as I know, some people sent their sensation back to repair with ENG OFF and did not really got into any trouble with warranty problem.
Think about it...How would they know? You cant get the phone to boot up, so how would they? They will just reflash the phone through the original process or replace the board inside. They dont have the time and money to go looking for evidence of you voiding the warranty. Its cheaper for them to reflash the phone than to see what you did. Not sure how they do it, but I know they have a method that most of us cannot do. Wont cost them much, at all. Im sure its related to a jtag. They will hook up the board to a device that will reflash the software.
Matt
Just an update to the situation.
I recieved my phone back today fully repaired, new PCBA-mainboard etc. etc. un-branded, un-locked. Was told it would have the latest os installed but came with 2.33 but i've successfully upgraded it. Now to play (a lot more carefully this time!).
For those who totally brick there phone like i did, take heart from my escapade but, perhaps i was just lucky!
Alright guys, after seeing 2.20 being rootable I decided to dive back into the One X. I traded my S3 for it + $50. Flawless S3, seriously. The guy I traded with seemed perfectly cool and legitimate but now an issue has arisen.
I didn't think to check it when we made the trade (though I checked other things like mobile data, etc.) but when I made a call later, the person on the other end couldn't hear me.
Here's what I've found:
Microphone works for recording video
Microphone works *on speaker phone*
Microphone works with an external source (bluetooth headset or earbuds with mic)
but the regular handset microphone does not appear to work.
Does anyone have ANY idea what might cause this? Unfortunately, I've already rooted. Literally the only thing I've done. I tried AOKP nightly, I've tried Nocturnal Limited edition. Next I'm going to attempt a RUU.
I've talked to the guy. He swears it was working, I'd like to believe him but neither of us tested it. He didn't test calls on the S3 either so it's not like he wasn't taking the same gamble.
He says that if I can get it working, he'll trade back but since he gave it to me working (as far as he knows) he won't trade back
I'm at a loss here. Can I (legally) mark the S3 as stolen? In that as far as I know, he made me a bad trade and will not simply give me my device back in return for his and his money
HAAAAALLLLLLPPPPP!
Thanks
MyronJ906 said:
Alright guys, after seeing 2.20 being rootable I decided to dive back into the One X. I traded my S3 for it + $50. Flawless S3, seriously. The guy I traded with seemed perfectly cool and legitimate but now an issue has arisen.
I didn't think to check it when we made the trade (though I checked other things like mobile data, etc.) but when I made a call later, the person on the other end couldn't hear me.
Here's what I've found:
Microphone works for recording video
Microphone works *on speaker phone*
Microphone works with an external source (bluetooth headset or earbuds with mic)
but the regular handset microphone does not appear to work.
Does anyone have ANY idea what might cause this? Unfortunately, I've already rooted. Literally the only thing I've done. I tried AOKP nightly, I've tried Nocturnal Limited edition. Next I'm going to attempt a RUU.
I've talked to the guy. He swears it was working, I'd like to believe him but neither of us tested it. He didn't test calls on the S3 either so it's not like he wasn't taking the same gamble.
He says that if I can get it working, he'll trade back but since he gave it to me working (as far as he knows) he won't trade back
I'm at a loss here. Can I (legally) mark the S3 as stolen? In that as far as I know, he made me a bad trade and will not simply give me my device back in return for his and his money
HAAAAALLLLLLPPPPP!
Thanks
Click to expand...
Click to collapse
tell him you fixed it and when u meet up, switch phones and RUN off. thank me if I helped :good:
adulel08 said:
tell him you fixed it and when u meet up, switch phones and RUN off. thank me if I helped :good:
Click to expand...
Click to collapse
lol you helped with a good laugh. That's genius, dude
Run the ruu. If the microphone works in other situations you're fine. Run the ruu.
And no you can't legally say it was stolen.
Sent from my HTC One XL
---------- Post added at 08:37 PM ---------- Previous post was at 08:29 PM ----------
Can't seem to edit my post. I didn't realize you were using the other microphone. You should run the ruu regardless to at least try and sort out any sort of software issue.
Sent from my HTC One XL
ECEXCURSION said:
Run the ruu. If the microphone works in other situations you're fine. Run the ruu.
And no you can't legally say it was stolen.
Sent from my HTC One XL
Click to expand...
Click to collapse
That's about what I thought actually. I'll run the RUU but can you explain what might have happened? If it's not actually broken hardware I don't have a problem keeping the phone but need to know how to avoid it
MyronJ906 said:
That's about what I thought actually. I'll run the RUU but can you explain what might have happened? If it's not actually broken hardware I don't have a problem keeping the phone but need to know how to avoid it
Click to expand...
Click to collapse
The microphone volume is a perennial problem with this phone. No one seems to know for sure what causes it. Reseting and ruu'ing ought to fix it.
Thanks guys, downloading the 2.20 RUU now. It does have to be the 2.20 RUU since I'm already on 2.20 right? No downgrading, is that correct?
I really hope this fixes it, because I love the One X. Haha, don't know how I dodged this problem the first time I had it.
Now I must ask and re-verify.
While booted into Nocturnal Lite
Run RUU
Reboot into stock and make sure everything's working
Reinstall recovery via fastboot
Install ROM of choice
Fastboot boot.img for ROM of choice
Boot up
Love One X
That's it right?
MyronJ906 said:
Thanks guys, downloading the 2.20 RUU now. It does have to be the 2.20 RUU since I'm already on 2.20 right? No downgrading, is that correct?
I really hope this fixes it, because I love the One X. Haha, don't know how I dodged this problem the first time I had it.
Now I must ask and re-verify.
While booted into Nocturnal Lite
Run RUU
Reboot into stock and make sure everything's working
Reinstall recovery via fastboot
Install ROM of choice
Fastboot boot.img for ROM of choice
Boot up
Love One X
That's it right?
Click to expand...
Click to collapse
Correct, you cannot downgrade. But to RUU, you have to relock or it will fail. Also, once you relock, you have to RUU then and there because your phone won't boot up. You'll need to go through the whole unlock/root process again. Remember this will wipe your phone.
iElvis said:
Correct, you cannot downgrade. But to RUU, you have to relock or it will fail. Also, once you relock, you have to RUU then and there because your phone won't boot up. You'll need to go through the whole unlock/root process again. Remember this will wipe your phone.
Click to expand...
Click to collapse
Cool, so I'm not as much of an idiot as I thought. having a new problem though. All my RUUs keep failing. USB error? I feel like a noob.
I was perfectly fine with my first One X and this one is giving me hell now. That's what I get for dancing with the devil lol
By the way, thanks a lot guys. I usually don't need half this much assistance, but you know ish happens.
MyronJ906 said:
Cool, so I'm not as much of an idiot as I thought. having a new problem though. All my RUUs keep failing. USB error? I feel like a noob.
I was perfectly fine with my first One X and this one is giving me hell now. That's what I get for dancing with the devil lol
By the way, thanks a lot guys. I usually don't need half this much assistance, but you know ish happens.
Click to expand...
Click to collapse
Did you relock? An RUU will fail otherwise.
iElvis said:
Did you relock? An RUU will fail otherwise.
Click to expand...
Click to collapse
Yeah man, relocked. I'm running the AT&T RUU found here. Fastboot OEM readCID still shows SuperCID, I'm reinstalling HTC Drivers and then I'll restart the computer. Maybe that's all it is.
MyronJ906 said:
Yeah man, relocked. I'm running the AT&T RUU found here. Fastboot OEM readCID still shows SuperCID, I'm reinstalling HTC Drivers and then I'll restart the computer. Maybe that's all it is.
Click to expand...
Click to collapse
Unplug your phone, turn it off, and restart it. Sometimes that helps. It won't boot, but you can get it back into the bootloader.
Does it need to be in Fastboot or Bootloader? I'm close to giving up on the laptop (which worked fine for the other 90%) and trying my ancient desktop
MyronJ906 said:
Does it need to be in Fastboot or Bootloader? I'm close to giving up on the laptop (which worked fine for the other 90%) and trying my ancient desktop
Click to expand...
Click to collapse
Bootloader.
Pretty sure my drivers have just fubarred. I'm not showing up on adb devices either. GRRRRRR this is driving me mad
EDIT: Finally got the RUU to run. Had to replace the standalone HTC drivers with fullblown HTC sync but it's whatever lol. Now to see if the RUU actually fixes the problem
Ran the RUU. Didn't fix it. I'll run it again, but any more ideas?
MyronJ906 said:
Ran the RUU. Didn't fix it. I'll run it again, but any more ideas?
Click to expand...
Click to collapse
"It" meaning the microphone? The phone is working okay otherwise? If so, I'm out of ideas. Might try flashing different roms to see if there's any change.
iElvis said:
"It" meaning the microphone? The phone is working okay otherwise? If so, I'm out of ideas. Might try flashing different roms to see if there's any change.
Click to expand...
Click to collapse
Yeah, I meant the microphone still isn't working. I've been on the stock RUU, AOKP, and Nocturnal. All of them have the same issue so I'm expecting that it's hardware.
I just don't know what to do guys. I guess I'll e-mail HTC, swing by the AT&T store in hopes of something, and call it done. I find it ****ty that the guy won't cooperate so far because truthfully I *would* at least cooperate but it's tough when he says it was working when he had it and I say it wasn't working when I had it.
BUT he says that he didn't make any calls that day. However, he "knows it was working when he gave it to me"
Guys, I just don't even know what to do. If I can't get it replaced, he completely won out on the trade. I was originally asking for + $100 and lowered it to + $50 for him. Yet he doesn't want to do anything for me.
I want to handle all of this responsibly, but I also want a completely functional phone
MyronJ906 said:
Can I (legally) mark the S3 as stolen?
Click to expand...
Click to collapse
For what purpose, a homeowners/renters insurance claim, or something else? Don't want to sound preachy, but insurance fraud is serious business, and a federal crime. Not worth it for a phone. Homeowners insurance claims for theft also require a police report, which is also something you obviously do not want to falsify.
If the microphone was malfunctioning before you did any mods to the phone, it would seem to me that the guy scammed you. Its highly improbable it was working for him, then just "coincidentally" broke around the time he traded it.
Try unlocking again, and flashing a new ROM. Combination of RUU, then fresh ROM may make a difference. Otherwise, I don't think HTC can do a warranty repair without proof of purchase. But they can probably fix it for a fee. True, the other guy will have made out on the deal, but at least you'll have a working phone.
redpoint73 said:
For what purpose, a homeowners/renters insurance claim, or something else? Don't want to sound preachy, but insurance fraud is serious business, and a federal crime. Not worth it for a phone. Homeowners insurance claims for theft also require a police report, which is also something you obviously do not want to falsify.
If the microphone was malfunctioning before you did any mods to the phone, it would seem to me that the guy scammed you. Its highly improbable it was working for him, then just "coincidentally" broke around the time he traded it.
Try unlocking again, and flashing a new ROM. Combination of RUU, then fresh ROM may make a difference. Otherwise, I don't think HTC can do a warranty repair without proof of purchase. But they can probably fix it for a fee. True, the other guy will have made out on the deal, but at least you'll have a working phone.
Click to expand...
Click to collapse
I did mean for the insurance claim. I didn't want to do it fraudulently which is why I asked. I wasn't sure what the exact definition of stolen (or even lost) in this regard is. But this doesn't count so that's no longer an option. Haha I now see that the AT&T warranty plan doesn't cover user idiocy, just drops and spillage.
I'll RUU again then install an AOSP ROM. I'm pretty sure it's the hardware mic that's busted though. Does speakerphone use a secondary microphone? I imagine videorecording does. If so, do the camcorder and speakerphone use the same mic?
Maybe the noisecanceling mic is screwing things up and that could be software but I think the microphone is just physically broken.
Idiot me, being the hardcore modder made changes to the phone *before* testing for the microphone. In my defense, I've owned the One X before so I knew what the hardware was capable of. I knew the current state of ROMs, so why not pick up where I left off?
I'll send HTC a pity e-mail and see where that gets me. Better to try and fail than to never have tried at all.
EDIT: I wanted to ask as well, does anyone think ROM flashing/BL unlocking etc. Really could have caused this? I mean, if it did there's no reason different software shouldn't fix it. But if it's hardware, that establishes that it's more likely that it wasn't my fault, right?
Hello,
I followed step-by-step this thread.( http://forum.xda-developers.com/showthread.php?t=1982982 )
Since I ve been a listener and this is first time caller, Im not allowed to reply in Developer section until 10 post are made.
This is my first post and need help.
Everything works just as the DEV explained. The bugs are the known ones, and it works...fine.
But, things like the camera bug (3rd party apps cant use it, like instagram, guess Skype, Google Now, etc...), screenshots and auto-rotation made me want to go back. (I could manage the APN thing by following one of the replier's advices)
So, question is: Is out there a more stable CM10 ROM? (I know the link I related isnt from actual CM10, yet a modified one. But after reaserch I found that the original CM10 also have this same known issues). If there isn't. Is there a way to go back to a bug-free ICS version?
If there is, I would need a step-by-step guide.
Thanks in advance for all replies.
______
Motorola Atrix 2 - CM10/MagicMod ROM
WaltLlanos said:
Hello,
I followed step-by-step this thread.( http://forum.xda-developers.com/showthread.php?t=1982982 )
Since I ve been a listener and this is first time caller, Im not allowed to reply in Developer section until 10 post are made.
This is my first post and need help.
Everything works just as the DEV explained. The bugs are the known ones, and it works...fine.
But, things like the camera bug (3rd party apps cant use it, like instagram, guess Skype, Google Now, etc...), screenshots and auto-rotation made me want to go back. (I could manage the APN thing by following one of the replier's advices)
So, question is: Is out there a more stable CM10 ROM? (I know the link I related isnt from actual CM10, yet a modified one. But after reaserch I found that the original CM10 also have this same known issues). If there isn't. Is there a way to go back to a bug-free ICS version?
If there is, I would need a step-by-step guide.
Thanks in advance for all replies.
______
Motorola Atrix 2 - CM10/MagicMod ROM
Click to expand...
Click to collapse
Sure you can go back to stock ICS.
Find the FXZ file for your region here: http://sbf.droid-developers.org/edison/list.php
Follow The noob guide on how to flash FXZ here: http://forum.xda-developers.com/showthread.php?t=1396650
HELP!!
Waiting4MyAndroid said:
Sure you can go back to stock ICS.
Find the FXZ file for your region here: http://sbf.droid-developers.org/edison/list.php
Follow The noob guide on how to flash FXZ here: http://forum.xda-developers.com/showthread.php?t=1396650
Click to expand...
Click to collapse
I followed the steps to flash the SBF and give my Atrix 2 the stock ICS version again.
I did the whole process and clicked START
After a while, several minutes, it showed
"FAILED FLASHING PROCESS, FAILED FLASHING PROCESS. 5/20 REBOOT-BOOTLOADER -> NO ARRIVAL MESSAGE NOTIFICATION; PHONE DISCONNECTED"
And in the result column it shows FAILED
I made sure the battery was full before begin the process, and I haven't touched the phone at all since it started.
What do I do? It's still plugged and the screen's off (Don't sure if the phone is off). I havent touched a thing.
This is the SBF I downloaded:
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip
from here: http://sbf.droid-developers.org/edison/list.php
EDIT:
When still plugged in, I pressed the POWER button, and nothing happened, Thought it was off.
I closed the RSD and unplugged the phone from PC and tried to turn it on. NOTHING HAPPENED.
No LED light, No Moto logo, nothing.
Removed battery, tried again....nothing...at all. ¿Dead?
Is it totally screwed? Nothing to do about? PLEASE HELP ME!. Im about to die.
WaltLlanos said:
I followed the steps to flash the SBF and give my Atrix 2 the stock ICS version again.
I did the whole process and clicked START
After a while, several minutes, it showed
"FAILED FLASHING PROCESS, FAILED FLASHING PROCESS. 5/20 REBOOT-BOOTLOADER -> NO ARRIVAL MESSAGE NOTIFICATION; PHONE DISCONNECTED"
And in the result column it shows FAILED
I made sure the battery was full before begin the process, and I haven't touched the phone at all since it started.
What do I do? It's still plugged and the screen's off (Don't sure if the phone is off). I havent touched a thing.
This is the SBF I downloaded:
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip
from here: http://sbf.droid-developers.org/edison/list.php
EDIT:
When still plugged in, I pressed the POWER button, and nothing happened, Thought it was off.
I closed the RSD and unplugged the phone from PC and tried to turn it on. NOTHING HAPPENED.
No LED light, No Moto logo, nothing.
Removed battery, tried again....nothing...at all. ¿Dead?
Is it totally screwed? Nothing to do about? PLEASE HELP ME!. Im about to die.
Click to expand...
Click to collapse
If your phone is ATT version MB865, then you used the wrong SBF. The one to flash is
InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip md5=2BF9CCD528C05D26523ACC5B38AC76C6
I believe your phone is soft bricked with a dead battery. Find a way to charge your battery and try to RSD again.
Waiting4MyAndroid said:
If your phone is ATT version MB865, then you used the wrong SBF. The one to flash is
InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip md5=2BF9CCD528C05D26523ACC5B38AC76C6
I believe your phone is soft bricked with a dead battery. Find a way to charge your battery and try to RSD again.
Click to expand...
Click to collapse
Actually, I think he is, sorry to say, super-hardbricked. Take a look here, it has all the proper explanations about bricks:
http://forum.xda-developers.com/showthread.php?t=1937112
If he was on ICS and an AT&T phone and flashed a non-AT&T firmware, he is most likely screwed. We have seen this way too many times, sorry to say, but to the OP, Please read more before trying these type of things and use search and not get too antsy before attempting things. This phone even though it has a bootloader lock, you can still very easily hard brick it.
The OP, just might get lucky and be able to charge his phone with an external charger, but I am pretty sure that will not do it.
I would go on ebay or craigslist and buy a working A2 with a cracked screen (much cheaper this way), and change out the board with your screen and such, and you should be back in business.
@Waiting4MyAndroid, next time you try to help someone ask them for more information, so you/we can be of better help, this guys is obviously a noob, and if we knew which region he was from and which phone he has, we/you could have given him the EXACT link to the correct file, and then walked him through what and what not to do. I am not trying to be a jerk. I am just saying that most people do not search or read these forms, they ask in a dire need and even when you give a link to read something, they are in panic mode and still do not read, and just do what they think is the thing you just mentioned, even though it may not be the right thing. I know this has been covered so many times, but I have learned that no matter what people do not read or search no matter what you mention, that is why we see soooooooo many of these types of posts over and over.
jimbridgman said:
Actually, I think he is, sorry to say, super-hardbricked. Take a look here, it has all the proper explanations about bricks:
http://forum.xda-developers.com/showthread.php?t=1937112
If he was on ICS and an AT&T phone and flashed a non-AT&T firmware, he is most likely screwed. We have seen this way too many times, sorry to say, but to the OP, Please read more before trying these type of things and use search and not get too antsy before attempting things. This phone even though it has a bootloader lock, you can still very easily hard brick it.
The OP, just might get lucky and be able to charge his phone with an external charger, but I am pretty sure that will not do it.
I would go on ebay or craigslist and buy a working A2 with a cracked screen (much cheaper this way), and change out the board with your screen and such, and you should be back in business.
@Waiting4MyAndroid, next time you try to help someone ask them for more information, so you/we can be of better help, this guys is obviously a noob, and if we knew which region he was from and which phone he has, we/you could have given him the EXACT link to the correct file, and then walked him through what and what not to do. I am not trying to be a jerk. I am just saying that most people do not search or read these forms, they ask in a dire need and even when you give a link to read something, they are in panic mode and still do not read, and just do what they think is the thing you just mentioned, even though it may not be the right thing. I know this has been covered so many times, but I have learned that no matter what people do not read or search no matter what you mention, that is why we see soooooooo many of these types of posts over and over.
Click to expand...
Click to collapse
Jim your advice to me is well taken. Usually I do ask more questions before I offer advice. In this case the OP "seemed" knowledgeable due to the fact his phone was on CM10/MagicMod. I guess everyone should be treated as a NOOB until proven other wise! Hopefully the OP can still recover his phone with a charged battery.
Sent from my MB865 using xda app-developers app
Waiting4MyAndroid said:
Jim your advice to me is well taken. Usually I do ask more questions before I offer advice. In this case the OP "seemed" knowledgeable due to the fact his phone was on CM10/MagicMod. I guess everyone should be treated as a NOOB until proven other wise! Hopefully the OP can still recover his phone with a charged battery.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
No worries. I was going by his join date of Dec. 2012, and only having posted five times, for noting that he was a noob. I have found that a lot of people can talk the talk well in here, but have maybe used another phone that is not like the A2 and tend to easily mess it up. Especially if this is their first android.
Waiting4MyAndroid said:
Jim your advice to me is well taken. Usually I do ask more questions before I offer advice. In this case the OP "seemed" knowledgeable due to the fact his phone was on CM10/MagicMod. I guess everyone should be treated as a NOOB until proven other wise! Hopefully the OP can still recover his phone with a charged battery.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Thanks VERY MUCH for your help. And yes, this is my first Android, and first time flashing, and as you supposed, noob.
:/ I want to believe it is the battery and with a charging will revive, but I don't know. The "super-hardbrick" thing makes more sense to me.
IT WAS FULLY CHARGED, it can't drain 98% in a few minutes, can it?...
Aaaaanyways, I will see if by charging the battery and trying it will show a light.
(Will it charge the battery in this state? or I'll have to make it by other means?)
Thanks @Waiting4MyAndroid and @jimbridgman for replying.
EDIT: When I plug it in the wall, nothing happens. No LEDs, no Moto logo, just black screen. It doesn't shows life signals. Same happens when plugged to the PC.
WaltLlanos said:
Thanks VERY MUCH for your help. And yes, this is my first Android, and first time flashing, and as you supposed, noob.
:/ I want to believe it is the battery and with a charging will revive, but I don't know. The "super-hardbrick" thing makes more sense to me.
IT WAS FULLY CHARGED, it can't drain 98% in a few minutes, can it?...
Aaaaanyways, I will see if by charging the battery and trying it will show a light.
(Will it charge the battery in this state? or I'll have to make it by other means?)
Thanks @Waiting4MyAndroid and @jimbridgman for replying.
EDIT: When I plug it in the wall, nothing happens. No LEDs, no Moto logo, just black screen. It doesn't shows life signals. Same happens when plugged to the PC.
Click to expand...
Click to collapse
If that is the case then you will have to try either the Macguvyer method:
http://forum.xda-developers.com/showthread.php?t=892026
Or find someone with a similar phone that works, that will let you use their phone to charge your battery with (another A2 or a bionic).
Those are just so you can see if it is a battery issue, but at this point, I am thinking you are hardbricked.
Do you have an AT&T branded phone (there will be an at&t logo at the bottom front of the phone under the capacitive buttons)?
jimbridgman said:
If that is the case then you will have to try either the Macguvyer method:
http://forum.xda-developers.com/showthread.php?t=892026
Or find someone with a similar phone that works, that will let you use their phone to charge your battery with (another A2 or a bionic).
Those are just so you can see if it is a battery issue, but at this point, I am thinking you are hardbricked.
Do you have an AT&T branded phone (there will be an at&t logo at the bottom front of the phone under the capacitive buttons)?
Click to expand...
Click to collapse
Yes, its an AT&T device. I'll try to charge the battery.
/In the case its hardbrick, there's nothing we can do, right? AT ALL?/
WaltLlanos said:
Yes, its an AT&T device. I'll try to charge the battery.
/In the case its hardbrick, there's nothing we can do, right? AT ALL?/
Click to expand...
Click to collapse
You can try and get AT&T to exchange it for a refurb, just tell them you charged it overnight and woke and it was like this. The only thing is that you must have, had the phone less than a year to qualify for this, and you MUST be in the US.
Otherwise you can buy an A2 on ebay or craigslist with a broken screen and put your good screen on that phone and be back in action. There is a thread in the general section that is a sticky on how to exchange your screen with the phone you get that has a broken one. This will be only if you are out of the year warranty or bought this phone and use it outside the US.
http://forum.xda-developers.com/showthread.php?t=1746094
jimbridgman said:
You can try and get AT&T to exchange it for a refurb, just tell them you charged it overnight and woke and it was like this. The only thing is that you must have, had the phone less than a year to qualify for this, and you MUST be in the US.
Otherwise you can buy an A2 on ebay or craigslist with a broken screen and put your good screen on that phone and be back in action. There is a thread in the general section that is a sticky on how to exchange your screen with the phone you get that has a broken one. This will be only if you are out of the year warranty or bought this phone and use it outside the US.
http://forum.xda-developers.com/showthread.php?t=1746094
Click to expand...
Click to collapse
I'm out of US, so I guess the warranty thing won't work. (Damn, I guess if I get out of this, will NOT ever try to handle upgrades, and flashing and this stuff) I bought the Atrix 2 from e-bay..Its (was) pre-paid.
Thank you so much for everything. And well, sorry for the inconveniences.
By the way, can you explain to me, what did I do exactly to the phone? I mean, what I understand is that I took out the "software" that ran everything in the device (including powering on) and didn't replace it with the new one since the process didn't complete. So in the end, I took the "soul" out of it, leaving just the dead "body". Does it make sense?
WaltLlanos said:
I'm out of US, so I guess the warranty thing won't work. (Damn, I guess if I get out of this, will NOT ever try to handle upgrades, and flashing and this stuff) I bought the Atrix 2 from e-bay..Its (was) pre-paid.
Thank you so much for everything. And well, sorry for the inconveniences.
By the way, can you explain to me, what did I do exactly to the phone? I mean, what I understand is that I took out the "software" that ran everything in the device (including powering on) and didn't replace it with the new one since the process didn't complete. So in the end, I took the "soul" out of it, leaving just the dead "body". Does it make sense?
Click to expand...
Click to collapse
What you did was flash a non AT&T firmware to the device, which causes the phone to "hardbrick" AT&T has some checks built into the hardware that will make the phone "die" if this is done. So if you do get another one, just make sure that you ONLY flash the proper AT&T FXZ file on the SBf-droid.com site, they say which ones are AT&T.
You can flash all the "ROMS" you want, you just can not use a firmware (FXZ) that is not AT&T based, so if you bootloop or softbrick, you need to make sure you use this FXZ file for AT&T ICS:
334.7 MiB 2BF9CCD528C05D26523ACC5B38AC76C6 ATT US InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip http://sbf.droid-developers.org/edison/InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip
My guess is that you did not use this file before, and RSD lite began to flash the bootloader, then went to reboot, and the checks happened and saw that the wrong bootloader was flashed and that set off an efuse that "bricked" the phone.
warrenty
Check to see if u have warranty still with motorola. Just give some lame excuse. Dont mention anything about roooting or roms or ull be f'ed. I sent then 2 hard bricked phones so on my 3rd A2 now. Just pay for shipping and it will be back in ur hands in hopefully less than 2 weeks.
Cant enter link cause im newb but motorola com go to service look for a2 and
Its on the bottom left column just enter imei#
widekyle said:
Check to see if u have warranty still with motorola. Just give some lame excuse. Dont mention anything about roooting or roms or ull be f'ed. I sent then 2 hard bricked phones so on my 3rd A2 now. Just pay for shipping and it will be back in ur hands in hopefully less than 2 weeks.
Cant enter link cause im newb but motorola com go to service look for a2 and
Its on the bottom left column just enter imei#
Click to expand...
Click to collapse
That only works, if Motorola warranties the phone in the Country that you live in.
jimbridgman said:
That only works, if Motorola warranties the phone in the Country that you live in.
Click to expand...
Click to collapse
I live in Colombia, and I bought the device on April 2012 on ebay, had it shipped internationally with USPS.
Do you think I can claim warranty for Motorola directly? Obviously not mentioning anything about ROMs, flashing, and anything. But what can I say?
WaltLlanos said:
I live in Colombia, and I bought the device on April 2012 on ebay, had it shipped internationally with USPS.
Do you think I can claim warranty for Motorola directly? Obviously not mentioning anything about ROMs, flashing, and anything. But what can I say?
Click to expand...
Click to collapse
Nope, you can not get moto to warranty it. You are better buying another phone. I would buy one that will be warrantied in your country, just in case something like this happens.
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.
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