Related
Hey guys,
I have had a HTC Diamond for quite some time now, I love(d) it! But I wanted to try out a new ROM. As you know a new non OEM ROM requires an unlock.
A quick search brought me to this link: http://forum.ppcgeeks.com/showthread.php?t=36062
As it clearly states: THIS IS FOR CDMA DIAMONDS ONLY!
Well, I have a GSM phone... At the time I had never heard of "CDMA" so I went through with the instructions.
My phone shutdown, and wont come on again.
I have tried to hard reset with out any luck. Only sign of life is when I connect it to my computer/charger it gets hot (no light tho)
Is there any way to bring my baby back to life? =)
All help is really appreciated!
Welcome to the forum
Have a look here:
http://wiki.xda-developers.com/index.php?pagename=HTC_Diamond
Perhaps a hard reset will be required (Back up your data)
Good luck,
Thank you
I had a look there before posting. The main problem for me is that the phone wont enter the bootscreen at all. No reaction when I push the power button
Is there a prog/app that allows me to start up the phone from my computer?
I have insurance on the phone, so I can get it repaired. Will they notice that I messed with the lock?
If so, how can I make sure they dont? Please help me!
Hi,
I think your device is what is technically known as proper ****ed
Get it into service station. It is unlikely they would be able to tell, no boot loader or any life at all, nah i doubt it. They will probably replace the main board....... and next time, use the right forum
Good luck my friend.
timmymarsh said:
Hi,
I think your device is what is technically known as proper ****ed
Click to expand...
Click to collapse
I couldn´t say it better
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Help! Same problem
I have no power to the device. Tmobile sent me a new sensation but i would like to try and fix the old one before i send it back, only have 5 more days.
Its not the battery or the sd since they both work fine in new phone.
Windows reads the same thing when on usb. No drivers. No power No nothing????
Can anyone help please or am i done for?
anarchyuk said:
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Click to expand...
Click to collapse
Could you explain what you did to cause this? I really hope you were messing with things other than what most people have done, otherwise, this could be a real problem for the rest of us.
Matt
Yes i would also like toknow what You did please
Sent from my HTC Sensation 4G using XDA Premium App
mrg02d said:
Could you explain what you did to cause this? I really hope you were messing with things other than what most people have done, otherwise, this could be a real problem for the rest of us.
Matt
Click to expand...
Click to collapse
+1
10Char
If you did brick there is a thred in the dev's that can and will show you how to unbrick and you can shop and decide on witch Rom you won't to go with look at it this way you have the best of both worlds good luck
Sent from my HTC Sensation 4G using XDA App
Had an issue today similar to yours, unlocked the bootloader today and kept the stock rom. Tonight I started deleting the bloatware, mainly using root explorer, no issues really. Used titanium backup to "force remove by exploit" I think its called. Did that and phone went black, tried powering back on, pulled battery etc, nada.
Ended up plugging device to usb charger and booted into bootloader, rebooted from there and its fine.
I ran into this tonight. See this thread:
http://forum.xda-developers.com/showthread.php?t=1198585
Short story -- Clockwork Recovery is bugged and won't charge the phone. Your battery level is too low to power on, so you need to use another method to get some power into it.
I did this:
http://dl.dropbox.com/u/15034469/tmp/recovery_fail.jpg
And yeah it's a lame problem.
Ahh, so this is not really a bricked phone, but a case of CWM dead battery! Good to know, as its an "easy" fix then. I was afraid that the phone, simply S-off and perm rooted, had somehow crashed permanently.
Matt
Straight Bricked
For me its not the battery, when tmobile sent me a new sensation i used my old battery, sdcard and sim and the battery still had around a 75% charge. I cant boot from usb i cant do anything. Its completely dead.
As for what i did?
I had been flashing multiple roms and kernels for 2 weeks. Overclocking, undervloting bla bla. No issues a wipe and flash couldnt take care of. I think i did a wipe and flash of a new rom and thats it. Dead. Wish i could remember exactly what it was. I guess im gonna mail it back since i have a new one and probably get charged full retail if they see its s-off and root.
blackstarnino said:
I had been flashing multiple roms and kernels for 2 weeks. Overclocking, undervloting bla bla. No issues a wipe and flash couldnt take care of. I think i did a wipe and flash of a new rom and thats it. Dead. Wish i could remember exactly what it was. I guess im gonna mail it back since i have a new one and probably get charged full retail if they see its s-off and root.
Click to expand...
Click to collapse
Ahh..So it wasnt the silly CWM ordeal then. That sucks!
Try to pinpoint what you were doing right before this happened. Were you wiping something? (what were you wiping) Were you flashing a ROM? (What were to flashing)
Try to provide more details, as I am sure some of the devs here will be looking to jump all over it shortly.
EDIT: Were to making sure to check that the ROM you were flashing was meant for your version of the phone as well as the files not corrupted? I know it sounds silly, but its something to rule out.
Matt
happened to me too on two batteries. I believe that it is due to overclocking the cpu. because the battery stats are calibrated for a slower CPU speed, it drains it past the failsafe point to pure failure. CWM will recognize CPU for the given ROM. i flashed back to S-ON and regular RUU 1.29 and charging my batteries again for the correct CPU + battery stats. wish me best of luck
Wow, am i that stupid
Not positive but i think i figured out what i did. Something really stupid.
I think i flashed: [Desire] InsertCoin CM7/STOCK 1.1.0
So am i fully bricked?
Gotta put the phone in the mail tomorrow.
Do you think they will see that its s-off or if its (truly) bricked can they not?
Nino
blackstarnino said:
Not positive but i think i figured out what i did. Something really stupid.
I think i flashed: [Desire] InsertCoin CM7/STOCK 1.1.0
So am i fully bricked?
Gotta put the phone in the mail tomorrow.
Do you think they will see that its s-off or if its (truly) bricked can they not?
Nino
Click to expand...
Click to collapse
They'll know....
actually... having worked in a few cell phone repair / refurbish facilities... i can tell you that they won't even look. they just plug the phone up to their bench and it overides everything and does a fresh flash. from there they just replace plastics to make it look like a brand new phone. if they are unable to flash it at the bench, they replace internals. so relax... no one will know or care what you did to it. these places get thousands of phones a day. and each tech at the bench has a quota to get through.
Thanks for your feedback guys. Shipping it off now...
Still cant believe it. Still have my n1 from launch day and it took everything i could throw at it. Still kicking like a beast. **** my g1 is still running cm4 i think lol.
anarchyuk said:
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Click to expand...
Click to collapse
I'm in the same situation. This sucks. I tried to get back S-ON. Did you receive a new phone?
So you flashed a desire ROM.... Well no ****...
Sent from my Transformer TF101 using xda premium
I used the hack kit to try and root my htc inspire. Now all my phone will do is start to boot. It will display the htc logo and the a black fog animation will appear and my screen will turn black. I can still get into the bootloader but I can't seem to do anything else. I also went the IRC section and tried to get some help but all the guy would do is call me a liar and wouldn't help. If I need proof of this I took screen shots of the conversation to prove that I wasn't receiving any help. That is why I am posting this thread to hopefully get my phone working again. Thanks for any help in advanced.
DWSXxRageQuitxX said:
I used the hack kit to try and root my htc inspire. Now all my phone will do is start to boot. It will display the htc logo and the a black fog animation will appear and my screen will turn black. I can still get into the bootloader but I can't seem to do anything else. I also went the IRC section and tried to get some help but all the guy would do is call me a liar and wouldn't help. If I need proof of this I took screen shots of the conversation to prove that I wasn't receiving any help. That is why I am posting this thread to hopefully get my phone working again. Thanks for any help in advanced.
Click to expand...
Click to collapse
You are probably having drivers problems. Try fixing that and rerun the hack kit from the black screen. If not the best is to make a livecd (ubuntu). All that is in the manual...
Ok. If you had read all of the effen manually carefully, you would know what to do.
But since your here. Run the hack kit again. And i dont know that you have driver problems. Same thing happened to me when j hacked my inspire on Ubuntu
Yea. Just plug your phone in, and re run the hack kit.
You should've educated yourself before you began messing with rooting and messing with the software on your phone. While its rare, bricking DOES happen and we can't help you after that. Educate yourself, and read the EFFING MANUAL. Good luck
HTC_Phone said:
Yea. Just plug your phone in, and re run the hack kit.
You should've educated yourself before you began messing with rooting and messing with the software on your phone. While its rare, bricking DOES happen and we can't help you after that. Educate yourself, and read the EFFING MANUAL. Good luck
Click to expand...
Click to collapse
Actually the phone is not bricked. If it was bricked he should thow it away. The Kit couldn´t finish due to drivers issues. He should sort that out and then rerun...He should have checked connectivity before starting..as you said it is all in the manual....
He never said it was bricked..
You could just send the phone to me jkjk rerun the kit it happened to me and it now works perfect <3
Sent from my Inspire 4G using xda premium
HTCinspiration said:
He never said it was bricked..
Click to expand...
Click to collapse
HTC sorry I read bull**** and that is what I answered!! I was at the office and made a quick reply...just one thing to add, the phones bricked that I have seen until now, were never consequence of the Hack Kit but their users...
Issue has been resolved.
I have already fixed my problem. After many of hours playing around with my phone I was able to get it back to factory settings. The reason that the root messed up is that I had a bad sd card to make a gold image. I used a new 1 gb sd card that I had laying around and was able to achieve root without any issues. Thanks for all the responses.
I think I posted this in the wrong forum, I suppose I was a little confused on my phone
I have a US AT&T version of the i727 Skyrocket. I think i accidentally flashed an improper kernel:
http://forum.xda-developers.com/showthread.php?t=1369977
I didn't realize I was browsing the wrong forum *sigh*.
Anyway, when I went to reboot after installing the kernel in CWM, I get a black screen. If I hold down both volume buttons and plug in USB, I get nothing. It doesn't seem to put it in download mode. There, it doesn't get recognized in ODIN.
What are my options here? Would a "jig" actually do anything in this case? I can't tell the scenarios it can actually recover from and not.
Hard brick, its done
Jtag or send to samsung
hedpe said:
I think I posted this in the wrong forum, I suppose I was a little confused on my phone
I have a US AT&T version of the i727 Skyrocket. I think i accidentally flashed an improper kernel:
http://forum.xda-developers.com/showthread.php?t=1369977
I didn't realize I was browsing the wrong forum *sigh*.
Anyway, when I went to reboot after installing the kernel in CWM, I get a black screen. If I hold down both volume buttons and plug in USB, I get nothing. It doesn't seem to put it in download mode. There, it doesn't get recognized in ODIN.
What are my options here? Would a "jig" actually do anything in this case? I can't tell the scenarios it can actually recover from and not.
Click to expand...
Click to collapse
If it does absolutely nothing, i'd say you bricked it which is quite possible if you flashed something for another phone. I don't think a jig will do you any good, based on things i've read before. Not 100%. Maybe someone else will give you some better input.
thanks for the replies. I can't get it in to download mode at all, so I'm afraid it's hard bricked.
Are there any guides to doing the jtag repair yourself? I'm pretty tech-savvy and comfortable opening up the phone, etc. I could get my hands on a jtag unit.
I just don't want to keep bricking it and sending it out for another $50. I'd rather have a solution where I can fix it myself.
hedpe said:
thanks for the replies. I can't get it in to download mode at all, so I'm afraid it's hard bricked.
Are there any guides to doing the jtag repair yourself? I'm pretty tech-savvy and comfortable opening up the phone, etc. I could get my hands on a jtag unit.
I just don't want to keep bricking it and sending it out for another $50. I'd rather have a solution where I can fix it myself.
Click to expand...
Click to collapse
I don't know any off hand, but why would you keep bricking it?
xcrazydx said:
I don't know any off hand, but why would you keep bricking it?
Click to expand...
Click to collapse
I'd hope not to, but on my first try I bricked it. I've never bricked my Nexus S after a ton of crappy kernels. Sigh...
Doesn't look like anyone has figured out a homebrew JTAG solution.
hedpe said:
I'd hope not to, but on my first try I bricked it. I've never bricked my Nexus S after a ton of crappy kernels. Sigh...
Doesn't look like anyone has figured out a homebrew JTAG solution.
Click to expand...
Click to collapse
Well, jtag for this phone was just made possible only a month or two ago. There may be a guide somewhere, but I dunno. You flashed something from a completely different phone, any time you do that you are pretty much guaranteed a brick. Just pay attention to what you're doing, man. Read more and flash less.
xcrazydx said:
Well, jtag for this phone was just made possible only a month or two ago. There may be a guide somewhere, but I dunno. You flashed something from a completely different phone, any time you do that you are pretty much guaranteed a brick. Just pay attention to what you're doing, man. Read more and flash less.
Click to expand...
Click to collapse
Right, understandable. Lesson learned there.
I can't tell if this is legitimate or not:
http://www.jtagbox.com/2012/03/page/2/
$50 isn't too bad. Obviously doing it yourself, if you could, would be better. I'd be on the safe side though and have mobiletech (i'm assuming you know about them), do it.
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.