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
Related
so yesterday i returned my moto xoom because it was overheating b4 i even rooted it. i got a nexus s and now it is bricked. 2dasy im going to have 2 return it. can any1 help me figureout a good excuse to tell the future shop return people? looks pritty bad i return 2 devices in less then 24 hours
edit: the last thing i did was flash gri74 back to stock. im guessin the bootloader is my issue. soo my phone technically isnt hacked or unlocked. just bricked so they cant see my device was rooted.
sounds like you overcooked the SNS setting it too high?
did you install any custom ROM ?
have you tried flashing it back to stock?
does the phone turns on at all?
make sure the battery is fully charged
AllGamer said:
sounds like you overcooked the SNS setting it too high?
did you install any custom ROM ?
have you tried flashing it back to stock?
does the phone turns on at all?
make sure the battery is fully charged
Click to expand...
Click to collapse
i didnt cook anything i dont think
no rom
phone wont turn on or even accept a charge i dont tihnk
wont respond to any commands ro show in adb or fastboot.
and ther batytery was at 90% when this happened.
any1 think of a good excuse
just tell them the phone was very hot when you woke up after leaving it charging overnight
defective phone
AllGamer said:
just tell them the phone was very hot when you woke up after leaving it charging overnight
defective phone
Click to expand...
Click to collapse
thx thats exactly what i did. grabbed a htc desire hd instead since nexus s is for the advanced user. i consider myself an advanced user but i had major issues wth the nexus s. even after reflashing gir74 or whatever it was called, i didnt have a working radio. which i tried flashing and resulted in a brick. thx alot 4 the advice. and i hope the nexus users create a noob proof guide 4 this phone as if sum1 with as much expierience with android as me is having issues, i can only imagine whut a complete noob would b thinkin about if he tried rooting. check my htc desire noob proof video guide here:
http://forum.xda-developers.com/showthread.php?p=12813521#post12813521
im quite sure if someone creates a thread like this, people will have less issues with the nexus plus the creator will get lots of thx you's and all around respect from the community. just an idea thou. worked 4 me with my desire as i had like 17 thx u's until march 30th when i created the thread. now im up 100 plus 11,000 views. good luck to you all
there are many fool proof guide for the SNS
there's no possible way to brick this phone
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!
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.
Hey there,
I received my Nexus 5 some days ago, I rooted it with the CF-AutoRoot, it worked fine, but since today, it is bricked. By the magic operation of Jesus maybe, who knows.
It don't boot, I don't see anything on the screen, I don't know if it is turned on or off… It just won't reply. To anything, fastboot, adb or whatever else. I can't boot in recovery or something else.
I think I have a splendid bricked late-2013 phone… I followed some tutorials to unbrick phones, the power + trick, but nothing.
The only thing I have on a windows computer is a "tadam" when I plug the USB, but that's it, no fastboot or adb, no screen, nada. But this sound of a plugged USB device. Knuh…
What the hell can I do ?
Shall I call Google tomorrow for RMA ?
ps: i saw some threads like me, i followed replies, but after a 4 hours searching, I don't wake up my phone
Have you given this a try? http://forum.xda-developers.com/showthread.php?t=2513937
esskayy said:
Have you given this a try? http://forum.xda-developers.com/showthread.php?t=2513937
Click to expand...
Click to collapse
yap, but no more results…
I think I tried all solutions on xda, no one worked :s
Flayks said:
yap, but no more results…
I think I tried all solutions on xda, no one worked :s
Click to expand...
Click to collapse
Hmmm... sounds like your bootloader is corrupt dude Weird, you are like the third today who has bricked the Nexus. All you can do now is RMA it and hope for the best.
esskayy said:
Hmmm... sounds like your bootloader is corrupt dude Weird, you are like the third today who has bricked the Nexus. All you can do now is RMA it and hope for the best.
Click to expand...
Click to collapse
Damned… why
Please, Google, don't be cruel with me
Flayks said:
Damned… why
Please, Google, don't be cruel with me
Click to expand...
Click to collapse
If the phone is truly bricked, and it seems like it is, then Google won't be able to boot up the phone so they won't know you've unlocked the bootloader
esskayy said:
If the phone is truly bricked, and it seems like it is, then Google won't be able to boot up the phone so they won't know you've unlocked the bootloader
Click to expand...
Click to collapse
That's what I think too, but how to explain that like someone don't know what is about… "helow my phone won't boot, it is black, I can't do anything… send me another one, please"? :cyclops:
doesn't boot*
*grammar police*
Flayks said:
That's what I think too, but how to explain that like someone don't know what is about… "helow my phone won't boot, it is black, I can't do anything… send me another one, please"? :cyclops:
Click to expand...
Click to collapse
Yh, that will work There are legitimate cases of phones not booting up so they may think you are one of them. Also I doubt the Google representative will care much for the reason. Their job is just to arrange the RMA
Flayks said:
That's what I think too, but how to explain that like someone don't know what is about… "helow my phone won't boot, it is black, I can't do anything… send me another one, please"? :cyclops:
Click to expand...
Click to collapse
That would work. Just don't say "send me another" ask "what do I do now"
apristel said:
doesn't boot*
*grammar police*
Click to expand...
Click to collapse
ups, thx.
esskayy said:
Yh, that will work There are legitimate cases of phones not booting up so they may think you are one of them. Also I doubt the Google representative will care much for the reason. Their job is just to arrange the RMA
Click to expand...
Click to collapse
Yep, I will call the support…
jd1639 said:
That would work. Just don't say "send me another" ask "what do I do now"
Click to expand...
Click to collapse
I would like to…
Thankz!
" I messed up my phone, even though it was completely fine when I bought it, I'll accuse google of producing a bad / faulty phone. "
Sounds legit.
If you CANNOT afford the risk that comes with modding, DONT do it. You/others who do this are very disgusting. GOOGLE did nothing wrong. YOUR phone was fine when you got it. Don't be a chump. You have to PAY to play.
MODS I'd close this thread due to FRAUD.. I HATE threads like this, People f/up their phones and expect everyone else to pay.
apristel said:
" I messed up my phone, even though it was completely fine when I bought it, I'll accuse google of producing a bad / faulty phone. "
Sounds legit.
If you CANNOT afford the risk that comes with modding, DONT do it. You/others who do this are very disgusting. GOOGLE did nothing wrong. YOUR phone was fine when you got it. Don't be a chump. You have to PAY to play.
MODS I'd close this thread due to FRAUD.. I HATE threads like this, People f/up their phones and expect everyone else to pay.
Click to expand...
Click to collapse
How do you know the phone isn't booting due to his bootloader being unlocked? He even said it was fine and it was not booting today....
Sent from my Nexus 5 using XDA Premium 4 mobile app
Because it booted afterwards. Thats how. .
I received my Nexus 5 some days ago, I rooted it with the CF-AutoRoot, it worked fine, but since today, it is bricked.
Click to expand...
Click to collapse
apristel said:
Because it booted afterwards. Thats how.
Quote:
I received my Nexus 5 some days ago, I rooted it with the CF-AutoRoot, it worked fine, but since today, it is bricked.
Click to expand...
Click to collapse
Maybe I was not clear in my first message but I rooted it, yes, but it worked! Since 3 days it works. But today, I really don't know why, I don't update or something else like changing rom (I'm on stock rom etc), it doesn't boot anymore.
That's it…
Flayks said:
Maybe I was not clear in my first message but I rooted it, yes, but it worked! Since 3 days it works. But today, I really don't know why, I don't update or something else like changing rom (I'm on stock rom etc), it doesn't boot anymore.
That's it…
Click to expand...
Click to collapse
I feel for you that your phone isn't working. Fraud isnt the answer. do you HONESTLY feel you'd get the same answer from Google if you told them that you rooted/unlocked and now your phone isn't working?
just saying that those who f up and make everyone pay for it are wrong. I personally like paying 400 for the 32gb device. I'd rather not pay 500 because of people who mess up and now make the cost/device go up due to rma's that are not legit.
Code:
The issuance of an RMA/RGA is a key gatekeeping moment in the reverse logistics cycle, providing the vendor with a final opportunity to diagnose and correct the customer's problem with the product (such as improper installation or configuration) before it is returned. As returns are costly for the vendor and inconvenient for the customer, any return that can be prevented benefits both parties.
Dude you need to chill a little. Unlocking your bootloader does not completely null warranty. If you brick your phone via software then you are responsible.
By the sounds of what is happening with the op, he has not changed anything to end up in this predicament. As with the other purple with similar problems (unlocking bootloader resulting in brick) can hardly be pointed at them.
Clearly something is happening which is out of user control which is causing these bricks.
If the ROM fails to boot it will throw you back to the bootloader.
If the bootloader fails you have a brick (not 100% true but not going into that now)
The facts are that the op has unlocked the bootloader which is a legitimate task and has for unknown reasons ended up with a corrupt bootloader.
This should still be covered as the op has not fine anything to solicit what had happened.
Sent from my Nexus 4 using xda app-developers app
apristel said:
I feel for you that your phone isn't working. Fraud isnt the answer. do you HONESTLY feel you'd get the same answer from Google if you told them that you rooted/unlocked and now your phone isn't working?
just saying that those who f up and make everyone pay for it are wrong. I personally like paying 400 for the 32gb device. I'd rather not pay 500 because of people who mess up and now make the cost/device go up due to rma's that are not legit.
Code:
The issuance of an RMA/RGA is a key gatekeeping moment in the reverse logistics cycle, providing the vendor with a final opportunity to diagnose and correct the customer's problem with the product (such as improper installation or configuration) before it is returned. As returns are costly for the vendor and inconvenient for the customer, any return that can be prevented benefits both parties.
Click to expand...
Click to collapse
Personally from my own experience, as the disclaimer on the bootloader unlock screen states 'This MAY void your warranty', telling Google the truth would be his best bet. Call Google, advise that the bootloader was unlocked and worked for 3 days and then it suddenly stopped booting.
If you bought a Nexus 5 and don't plan to do anything to it then that's up to you. However some of us buy Nexus devices because of the ease of development on them. Google facilitate this with the ability to unlock the bootloader and have no justifiable reason to refuse an RMA when all the OP has done is unlock said bootloader.
Why don't YOU stop being a **** and get off this thread. Please.
Anyone else bricked their phone like this? Managed to un-brick mine from an identical situation, if anyone is still stuck like I was I'll try and make a little "guide" to help others
daniel.kusy said:
Anyone else bricked their phone like this? Managed to un-brick mine from an identical situation, if anyone is still stuck like I was I'll try and make a little "guide" to help others
Click to expand...
Click to collapse
Apparently yes, I'm not the only one. It would be great if you try to explain your solution!
:crying:
Basically the 4.4.4 update hard bricked my phone, won't even boot into bootloader. I made no modifications at all, not even root, only unlocking the bootloader. I was on the phone to motorola for half an hour trying to get a replacement, but they wouldn't hear a word of it because the boot loader is unlocked so apparently it's all my responsibility, not their's at all for pushing a corrupted file...
Basically stick to 4.4.2 as long as you can. If anything, 4.4.4 is a downgrade, at best a side-grade. Much like 4.4.x all together really - really wish i'd stayed on 4.3
So I there anything i can do to unbrick it? I'm buying a new one anyway, but might use the "bricked" one for testing ROMs or something but if I can't get to fastboot there's nothing much I can do.
Moto G will not power up
Plug it into the charger
Hold the VOL DOWN key
While still holding the VOL DOWN key, press and hold the POWER key
Hold both keys down for over 120 seconds. This is more than two minutes and will seem like a long time. You might want to time yourself to make sure you hold it longer than two minutes.
After holding the keys down for more than two minutes, release them.
The Flash Boot screen will display, and the Normal Reboot option will be highlighted
Press the VOL UP key and the device will start a normal reboot.
If you have tried the above and it didn't work, try this:
Plug in the phone for 15 minutes.
Proceed to Step 2 above.
Source: https://forums.motorola.com/posts/3d5eadc25d
Broken_motoG said:
:crying:
Basically the 4.4.4 update hard bricked my phone, won't even boot into bootloader. I made no modifications at all, not even root, only unlocking the bootloader. I was on the phone to motorola for half an hour trying to get a replacement, but they wouldn't hear a word of it because the boot loader is unlocked
Click to expand...
Click to collapse
If the bootloader has mysteriously become unlocked, then clearly you did modify the phone and they are entitled to decline a refund. This is made perfectly clear when the procedure to unlock is executed.
That's why you should be careful of anything you do with the phone once the bootloader is unlocked.
Broken_motoG said:
:crying:
Basically the 4.4.4 update hard bricked my phone, won't even boot into bootloader. I made no modifications at all, not even root, only unlocking the bootloader. I was on the phone to motorola for half an hour trying to get a replacement, but they wouldn't hear a word of it because the boot loader is unlocked so apparently it's all my responsibility, not their's at all for pushing a corrupted file...
Basically stick to 4.4.2 as long as you can. If anything, 4.4.4 is a downgrade, at best a side-grade. Much like 4.4.x all together really - really wish i'd stayed on 4.3
So I there anything i can do to unbrick it? I'm buying a new one anyway, but might use the "bricked" one for testing ROMs or something but if I can't get to fastboot there's nothing much I can do.
Click to expand...
Click to collapse
Hi, DO NOT take that from Motorola, because you live in the UK which is in Europe (Thats important) Motorola are legally obliged to help you as unlocking the bootloader/loading custom ROMs on to your device is seen as a legitimate practice and not a voiding act of your statuary warranty.
As long as you don't alter hardware they are NOT entitled to decline a refund/replacement under the circumstances, however they can refer you to the retailer you purchased it from but the rules still stand that they have to help you get a new/refurbished phone or a refund
Use this to prove it to them and make them pay up: http://fsfe.org/freesoftware/legal/flashingdevices.en.html
Hope this could be of assistance to you and I'm sorry if its off-topic but it needs to be made clear to all EU Motorola owners
TechMinerUK said:
Hi, DO NOT take that from Motorola, because you live in the UK which is in Europe (Thats important) Motorola are legally obliged to help you as unlocking the bootloader/loading custom ROMs on to your device is seen as a legitimate practice and not a voiding act of your statuary warranty.
As long as you don't alter hardware they are NOT entitled to decline a refund/replacement under the circumstances, however they can refer you to the retailer you purchased it from but the rules still stand that they have to help you get a new/refurbished phone or a refund
Use this to prove it to them and make them pay up: ht tp:// f sfe.org/f reesoftw are/legal/flash ingdev ices.en.html
Hope this could be of assistance to you and I'm sorry if its off-topic but it needs to be made clear to all EU Motorola owners
Click to expand...
Click to collapse
Thanks for that - didn't realise that law existed, but that will be really helpful :laugh::laugh::laugh::laugh:
Broken_motoG said:
Thanks for that - didn't realise that law existed, but that will be really helpful :laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
No problem, I checked on it before I installed CM on my Moto G last week
Hope I could help and good luck with the phone
Good luck with unbricking your phone, but oh no, I've already downloaded the 4.4.4 update!
Oh wait, my phone works just fine...
And if it immediately bricked your phone, how do you know that "If anything, 4.4.4 is a downgrade, at best a side-grade."?
startersorders said:
Good luck with unbricking your phone, but oh no, I've already downloaded the 4.4.4 update!
Oh wait, my phone works just fine...
And if it immediately bricked your phone, how do you know that "If anything, 4.4.4 is a downgrade, at best a side-grade."?
Click to expand...
Click to collapse
I don't want to get off-topic but if an update bricked your phone its a pretty BIG downgrade as it went from a phone with many uses to a paperweight (allbeit a pretty paper weight) as it has lost functionality and its the softwares fault.
Its personal opinion
OP needs to establish if he has simply not encountered the ''Moto G won't turn on' issue. I included instructions above. It could all be just bad timing.
Broken_motoG said:
:crying:
Basically the 4.4.4 update hard bricked my phone, won't even boot into bootloader. I made no modifications at all, not even root, only unlocking the bootloader. I was on the phone to motorola for half an hour trying to get a replacement, but they wouldn't hear a word of it because the boot loader is unlocked so apparently it's all my responsibility, not their's at all for pushing a corrupted file...
Basically stick to 4.4.2 as long as you can. If anything, 4.4.4 is a downgrade, at best a side-grade. Much like 4.4.x all together really - really wish i'd stayed on 4.3
So I there anything i can do to unbrick it? I'm buying a new one anyway, but might use the "bricked" one for testing ROMs or something but if I can't get to fastboot there's nothing much I can do.
Click to expand...
Click to collapse
I don't think this is anything to do with the update. If it was we would have heard about it from more that just you.
After all mine works perfectly fine after the update and I'm UK Tesco.
dethrat said:
I don't think this is anything to do with the update. If it was we would have heard about it from more that just you.
After all mine works perfectly fine after the update and I'm UK Tesco.
Click to expand...
Click to collapse
Same here and plenty of subtle improvements (get rid of the Carrier name woo-hoo) and bug fixes in 4.4.4 - (several features of my Automation app - MacroDroid suddenly work when they didn't before), not to mention one or two security patches. Slightly better battery life and noticeably smoother animations are a nice bonus too. New Dialler is a big improvement - the old one was ugly.
neu - smurph said:
Same here and plenty of subtle improvements (get rid of the Carrier name woo-hoo) and bug fixes in 4.4.4 - (several features of my Automation app - MacroDroid suddenly work when they didn't before), not to mention one or two security patches. Slightly better battery life and noticeably smoother animations are a nice bonus too. New Dialler is a big improvement - the old one was ugly.
Click to expand...
Click to collapse
It depends, my friend who has a Moto G update to 4.4.4 lost all functionality of his apps and his clock stopped working. It just depends as his phone wasn't rooted with no bootloader unlock
TechMinerUK said:
I don't want to get off-topic but if an update bricked your phone its a pretty BIG downgrade as it went from a phone with many uses to a paperweight (allbeit a pretty paper weight) as it has lost functionality and its the softwares fault.
Its personal opinion
Click to expand...
Click to collapse
Of course a bricked phone is useless, but something obviously went wrong with the OP's phone, and its probably a coincidence that it happened while updating. It's the absurdity of the comments "DO NOT download the 4.4.4 update" and "4.4.4 is a downgrade" that got me to post, because its pretty clear that many people have updated without any issue.
Not besmirching the OP's problem, and like I said, I wish him well in getting his phone working.
Also, depending how old the phone is and where you bought it from, isn't it an option just to return it to the seller for an exchange. Just tell them it stopped working and you want a replacement phone?