Database Info

Having Withdrawals Already!!!

Ok so today I mow my yard and I plug in my Thunderbolt in to the USB charger on my PC when I come inside my phone is bootlooping. So I think ok whatever I will flash one of the many backup's I made.
So I pull the battery and boot into the bootloader, then when I go into recovery after about 2 seconds the phone powers off and starts bootlooping again??? Ok that's a first for me and I have been flashing and rooting since launch day of the OG Droid, (ok, ok not since the first day but like a month later). So I pull the battery again this time for 30 minutes because I read someone else had something like this happen yesterday. When I put the battery back in same thing! Now I pull the battery for 4 hours...same outcome.
Now I'm thinking RUU time so I grab the stock RUU pull the SD card from my Thunderbolt pop it in my Incredible load the RUU renamed to PG05IMG.zip and put it back in the Thunderbolt. Load the bootloader and flash the RUU. Reboot after it's done and would you believe it...the same thing! the phone won't load past the splash screen before rebooting.
I forgot to mention before trying all this I tried using adb to reboot into recovery and I kept getting "error: device not found" and I know how to use adb.
It's only been about 9 hours since I've been able to use my 2.3.4 GingerBread with parts of 3.0 Sense Thunderbolt and I already having withdrawals how am I going to make the next 2 to 3 weeks while it's being repaired???
Ok end rant...

Go to verizon, swap it for a new one. Warranty case for sure.

bilbobrian said:
Go to verizon, swap it for a new one. Warranty case for sure.
Click to expand...
Click to collapse
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.

I'm loosing faith in the Thunderbolt. I really feel we are all just a bunch of beta testers.

bunklung said:
I'm loosing faith in the Thunderbolt. I really feel we are all just a bunch of beta testers.
Click to expand...
Click to collapse
Huh? Off topic and makes no sense.
//Tap'd on my TBolt while grounded\\

bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
I understand your rooted but if it cant boot up then there is a problem. Just go to verizon and show them. Once they see it cant boot properly they will exchange it or overnight one to you.
I apologize if Im missing something..

bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
You may get away with getting it swapped through warranty. But I can't promise you it won't come back at you. Someone may have a solution for you though. Wouldn't give up yet. Sorry I don't.
//Tap'd on my TBolt while grounded\\

chkmate said:
Huh? Off topic and makes no sense.
//Tap'd on my TBolt while grounded\\
Click to expand...
Click to collapse
*Shrug*
He has a problem, I do too. We both own Thunderbolts. Maybe I should have been more specific.
To each his own. The end.

bunklung said:
*Shrug*
He has a problem, I do too. We both own Thunderbolts. Maybe I should have been more specific.
To each his own. The end.
Click to expand...
Click to collapse
Well then relate your problem with his. Just saying "your losing faith in Thunderbolt" tells me nothing. Don't mean to sound like an a$$, just saying. When I read your first comment I got nothing from it.
That being said...I haven't been a Bolt owner for long, but it does seem like a strange issue. You would think flashing a radio or backup would resolve the issue. But hasn't.
//Tap'd on my TBolt while grounded\\

Definitely sounds like a Warranty Issue. I'd try to get it exchanged if no one can come up for a solution to the problem.

I had a G1 back in the day that had some odd problem and I was rooted, Tmo looked at it and wouldn't touch it. So, I called HTC. I told them that I purchased the phone off Craigslist so Tmo couldn't help me, and asked how the warranty works on their end. They said that since the production of the phone started less than a year ago, they knew it was still eligible for warranty even without a receipt. There would be a triage fee if it was found to be a non-warranty issue, and it was something like $40 including the shipping back. I acted dumb when they asked if it was rooted...asked them what that meant? LOL. Sent it in, they fixed it and sent it back to me, no charge. Fast too. I was very happy and that is why I have stuck with HTC since then. It may or may not work for you, but it was painless for me.

bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
Such chivalry is rare in these days.
Applaud. Best of luck!
Sent from my ADR6400L using Tapatalk

bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
They don't care. Take my word for it. If it never boots they won't care.

I'm actually having this exact same issue. Has anyone found a solution yet or is the only solution to have the phone replaced?

Wow. I thought for sure hbooting the unsigned stock RUU would fix this. How about hbooting a signed ruu? It wouldn't hurt at this point.
Also make sure when you renamed the pgimg05. Zip that there was nothing at the end of the extention. I've heard some people say that windows has been known not to show that full file extension correctly.

raider3bravo said:
Wow. I thought for sure hbooting the unsigned stock RUU would fix this. How about hbooting a signed ruu? It wouldn't hurt at this point.
Also make sure when you renamed the pgimg05. Zip that there was nothing at the end of the extention. I've heard some people say that windows has been known not to show that full file extension correctly.
Click to expand...
Click to collapse
I thought hbooting the stock RUU would fix it as well, and yep it was named correctly. It's funny because it would stay on the hboot screen as long as I let it with no issue what so ever but within 2 seconds of going into recovery it would reboot.
I went back to Best Buy today as that is where I bought it to see how much they would charge to ship it out to be fixed. The mobile manager remembered me because I was 1st on the pre-order list. (I'm sure we all remember the train wreck the Best Buy pre-orders became) So any way he really went out of his way to help me. He said he has had 3 other Thunderbolts brought in for the same issue. He was able to send my phone in under their Black Tie program.
I told him I rooted the phone and was willing to pay for the repairs but he said he was pretty sure that the other 3 phones were not rooted. He said that he knew FOR SURE that at least one of the phones was not rooted because the lady that owned it did not have any branches in her family tree, (his words not mine). Since he has seen it 3 times he was not charging me. He only asked that I had the stock hboot on the phone. I had already flashed that in my attempt to get it running.

I'm with cstrife, I managed to destroy my tab with a mix of flashing and charging via outlets in India. It bootlooped for a while then just kind of gave up and began to display a strange download screen when I plugged it in to charge. I brought it to VZW and played stupid, I told them I woke up and it had this weird screen... I had a brand new one at my door the next morning and haven't heard a word from them... It probably just costs more to check it out deep enough to find out its rooted than it does to just give you a refurbished one, gut swap yours, and then send to someone else as a refurbished one...
Sent from my SCH-I800 using XDA App

Had this happen to me and just pulled my SD card, rebooted and it was fine. Not saying it will work for u but give it a shot.
Sent from my ADR6400L using XDA App

bp328i said:
I thought hbooting the stock RUU would fix it as well, and yep it was named correctly. It's funny because it would stay on the hboot screen as long as I let it with no issue what so ever but within 2 seconds of going into recovery it would reboot.
I went back to Best Buy today as that is where I bought it to see how much they would charge to ship it out to be fixed. The mobile manager remembered me because I was 1st on the pre-order list. (I'm sure we all remember the train wreck the Best Buy pre-orders became) So any way he really went out of his way to help me. He said he has had 3 other Thunderbolts brought in for the same issue. He was able to send my phone in under their Black Tie program.
I told him I rooted the phone and was willing to pay for the repairs but he said he was pretty sure that the other 3 phones were not rooted. He said that he knew FOR SURE that at least one of the phones was not rooted because the lady that owned it did not have any branches in her family tree, (his words not mine). Since he has seen it 3 times he was not charging me. He only asked that I had the stock hboot on the phone. I had already flashed that in my attempt to get it running.
Click to expand...
Click to collapse
Honesty turned out to be the best policy in this case. Congrats.
Sent from my ADR6400L using Tapatalk

MrHawaii said:
Honesty turned out to be the best policy in this case. Congrats.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Thanks, now I just have to wait 2 to 3 weeks to get it back. What to do with all that time!!!

[Q] Should Verizon replace my phone?

I was running cm7 on my phone, and was throwing on the audio fix to get better speaker volume, which sent the phone into a boot loop. I tried to put my phone into hboot (power+volume-) which it does not. It tries to boot every time. I've tried probably 50+ times and same result. I'm guessing it has to deal with the poor built buttons on this phone and the volume down just does not work. My question is despite the fact I'm rooted and running cm7, am I safe to say this is a hardware issue? I just don't want to send in my phone to Verizon and get billed for the fact the phones "tampered" with.

Should verizon replace your phone after you borked it? I think you already know the answer

xebryus said:
I was running cm7 on my phone, and was throwing on the audio fix to get better speaker volume, which sent the phone into a boot loop. I tried to put my phone into hboot (power+volume-) which it does not. It tries to boot every time. I've tried probably 50+ times and same result. I'm guessing it has to deal with the poor built buttons on this phone and the volume down just does not work. My question is despite the fact I'm rooted and running cm7, am I safe to say this is a hardware issue? I just don't want to send in my phone to Verizon and get billed for the fact the phones "tampered" with.
Click to expand...
Click to collapse
long of it, no they shouldn't. will they? who knows, depends on if you tell them the truth or not.

Should they? Technically no. Will they? Sure. They would be happy to.

but he didnt break it if the loop comes from a hardware defect,all he did was get it to fail sooner than later basically what happened to others,so technically yes they should,or can anyone prove the software killed the hardware.
sent from a screamin' bamfed out tbolt

satseaker said:
but he didnt break it if the loop comes from a hardware defect,all he did was get it to fail sooner than later basically what happened to others,so technically yes they should,or can anyone prove the software killed the hardware.
sent from a screamin' bamfed out tbolt
Click to expand...
Click to collapse
Honestly, it doesn't matter if anyone can prove the software did it or not. He voided his warranty by rooting. But they likely will replace his phone, driving up the costs for future phones.
You rooted your phone. Take it for what it is...a non-warrantied phone.

Touchy
I will start off by saying I don't have a solid answer but being as it is a hardware problem they "should" fix it. Will they? Probably not. They'll take one look, see it's rooted, and tell you that you broke it by tampering with it. All bets are off as soon as the phone is rooted...unless you can unroot and take it in I think you're in trouble but since the button is broken you can't do anything with it. Good luck and let us know what you were able to get done.

I see what you guys are saying from a moral standpoint. I'm just angry cause I know for a fact my buttons are not up to par to what they're supposed to be. I don't want to fraud the companies over something that is my fault, but in this case I'm almost positive it's related to the fact this phone was not built too well. I dunno, do "authorized retailers" handle claims with faulty hardware or just official Verizon wireless stores?

This is why you should have ADB installed and working on your computer. Hook up the phone via USB, get into ADB and reboot into recovery. There are a few threads out there for ADB you should be able to find them using Google, hopefully that will be able to help you.

If you can get into the boot loader with and then you might be able to save your phone.. Maybe, not clear take your as card out and import the rhi, they might work...
Sent from my ThunderBolt using XDA App

if you can prove that the failure was not caused by rooting, then they should fix it for you under warranty. but that is hard to prove.

xebryus said:
I see what you guys are saying from a moral standpoint. I'm just angry cause I know for a fact my buttons are not up to par to what they're supposed to be. I don't want to fraud the companies over something that is my fault, but in this case I'm almost positive it's related to the fact this phone was not built too well. I dunno, do "authorized retailers" handle claims with faulty hardware or just official Verizon wireless stores?[/QUOTE
Did you try BOTH volume buttons at the same time? This got me to bootloader.
Click to expand...
Click to collapse

Just say you tried to install the last update and your phone wont boot now. They won't know the difference.

dpham00 said:
if you can prove that the failure was not caused by rooting, then they should fix it for you under warranty. but that is hard to prove.
Click to expand...
Click to collapse
Caused by rooting or not, there is NO warranty once a phone is rooted. Has nothing to do with what caused the malfunction.
ADB reboot bootloader or recovery should work though, as long as he catches it with the right timing during the loop.
Sent from my ADR6400L using XDA App

Well update on the situation. I called Verizon telling them I can't turn on my because it "freezes" when it tries to boot up every time. He told me to try a hard reset (try to go into hboot) and I told him I tried that at least 30 times and it won't. I said I think there's something wrong with my buttons because they're not very responsive and stick really easily (which they do) and he said they're overnighting a phone to me. That was yesterday, its waiting for me at home. I'm gonna send my old phone back asap.
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.

you're probably aright since they might just get it and toss it in the "to be refurbed" bin. It costs a lot of money to test every return. Good luck and let us know how it turns out.

xebryus said:
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
Click to expand...
Click to collapse
If they do find out, they will charge you. Don't know if they will, but be prepared for the worst.
Sent from my ThunderBolt using Tapatalk

Yes, they get broken down abd only really check for water/physical damage
Sent from the Swag ThunderBolt ADR6400L with some GingerLove (Gingeritis 1.0) using XDA Premium App
Must Watch Before Any Forum Post http://goo.gl/b4IJJ

xebryus said:
Well update on the situation. I called Verizon telling them I can't turn on my because it "freezes" when it tries to boot up every time. He told me to try a hard reset (try to go into hboot) and I told him I tried that at least 30 times and it won't. I said I think there's something wrong with my buttons because they're not very responsive and stick really easily (which they do) and he said they're overnighting a phone to me. That was yesterday, its waiting for me at home. I'm gonna send my old phone back asap.
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
Click to expand...
Click to collapse
Congrats on getting a new phone I guess.
I have noticed Verizon has been VERY accomodating with these phones. One call is all that's needed to get a new phone. Im guess they're so generous because they devices have been so finnicky so far and they just want to keep people pleased for now.
I envision them cracking down hard sooner or later though. They're not stupid. They've already come down on tethering and such, so it probably wont be long until they get hardcore on replacements.

My son works for VZ...
and he takes your calls... and this is what he told me. Anything covered under insurance (Asurion), they really don't check/don't care about rooting. VZ, on the other hand, will look pretty extensively if it's covered under the warranty. They will look for rooting or anything else that would break warranty coverage.

[q] need opinion!!

Hey guys
I gave my cousin my infuse 4g, which was running gtg's Infused latest ROM.
According to her, she was at the mall and she pulled out the phone from her pocket and all she saw was infinite logo bootloop.
At first to me it seemed like a soft brick but it's not recoverable.
When I put the battery in, it goes into infinite samsung logo bootloop.
Three button combo to CWM doesn't work, the download mode jig also does not work.
when i put the download jig in, the yellow downloading mode logo shows up for 2 seconds and then the phone turns off. and the process repeats.
When i put the charging cable in, it infinitely loops the "battery picture", turning off 1 second later everytime and turning back on...
I plan on taking it back to the AT&T Service Shop for a chance at claiming a replacement device.
So here's my question.
I've tried everything I can to get this thing back to a working state, but to no avail.
Does this mean that the engineers at the service center will also not be able to get it back up (meaning that they won't be able to tell that i've voided the warranty)?
I mean, something is seriously wrong with this infuse. it won't even go to download mode.
I bought this device back in July 2011, so I'm still under that 1 year manufacturer's warranty.
Do you guys think I will be able to get a replacement device?
Thanks guys!
EDIT: here are the visual descriptions of what i'm talking about.
http://www.youtube.com/watch?v=bYiZbgI3rnk&feature=channel&list=UL
http://www.youtube.com/watch?v=ZxvIj76MkjA&feature=channel&list=UL

jhong91 said:
Hey guys
I gave my cousin my infuse 4g, which was running gtg's Infused latest ROM.
According to her, she was at the mall and she pulled out the phone from her pocket and all she saw was infinite logo bootloop.
At first to me it seemed like a soft brick but it's not recoverable.
When I put the battery in, it goes into infinite samsung logo bootloop.
Three button combo to CWM doesn't work, the download mode jig also does not work.
when i put the download jig in, the yellow downloading mode logo shows up for 2 seconds and then the phone turns off. and the process repeats.
When i put the charging cable in, it infinitely loops the "battery picture", turning off 1 second later everytime and turning back on...
I plan on taking it back to the AT&T Service Shop for a chance at claiming a replacement device.
So here's my question.
I've tried everything I can to get this thing back to a working state, but to no avail.
Does this mean that the engineers at the service center will also not be able to get it back up (meaning that they won't be able to tell that i've voided the warranty)?
I mean, something is seriously wrong with this infuse. it won't even go to download mode.
I bought this device back in July 2011, so I'm still under that 1 year manufacturer's warranty.
Do you guys think I will be able to get a replacement device?
Thanks guys!
EDIT: here are the visual descriptions of what i'm talking about.
http://www.youtube.com/watch?v=bYiZbgI3rnk&feature=channel&list=UL
http://www.youtube.com/watch?v=ZxvIj76MkjA&feature=channel&list=UL
Click to expand...
Click to collapse
jhong91,
It is not often but several other users have reported similar hard power loops that you're describing.
If you go back through the Q/A thread, there are a few with this.
Some users have succeeded in restoring their device via jtag method - by mobiletech or something like that.
Others opted for the replacement and was successful too.
Look through the last 20-40 pages...(garen21, brazcub may have similar situation ) Others have been told that it was due to corrosion of the battery terminal or bad circuit board.

qkster said:
jhong91,
It is not often but several other users have reported similar hard power loops that you're describing.
If you go back through the Q/A thread, there are a few with this.
Some users have succeeded in restoring their device via jtag method - by mobiletech or something like that.
Others opted for the replacement and was successful too.
Look through the last 20-40 pages...(garen21, brazcub may have similar situation ) Others have been told that it was due to corrosion of the battery terminal or bad circuit board.
Click to expand...
Click to collapse
Hello,
thanks for the reply!
if the problem really is, as you may have kindly pointed out, with the circuit board or bad battery terminal, do you think it's unrecoverable even by the AT&T technicians (or mobiletechvideo's jtag service)?
Also, this is my first time dealing with warranties on smartphone.
If they happen to find out that I have voided the warranty by rooting the phone, the worst thing that could happen is not getting a replacement device right? they can't charge me or penalize me right?
Thanks in advance!

You will be OK.
I bricked mine and sent it in, they didn't even realize it was rooted and sent me a new one. Just don't mention it man. Also its better if you take it to a smaller att store, they seem to be a bit cooler then the big corporate stores
Sent from dr0id using Tapatalk 2 beta 5

eZdubzitmk4 said:
You will be OK.
I bricked mine and sent it in, they didn't even realize it was rooted and sent me a new one. Just don't mention it man. Also its better if you take it to a smaller att store, they seem to be a bit cooler then the big corporate stores
Sent from dr0id using Tapatalk 2 beta 5
Click to expand...
Click to collapse
did you go to a retail store? or an official device support center?
thanks!

A retail store
Sent from dr0id using Tapatalk 2 beta 5

eZdubzitmk4 said:
A retail store
Sent from dr0id using Tapatalk 2 beta 5
Click to expand...
Click to collapse
ok, i thought I was supposed to go to device support center..
i guess i'll go to retail first and then device support center if they should redirect me there..
anyways,
thanks man!

Yeah it all depends on the person, most are pretty cool and try to help.
But others just send you away to support
Sent from dr0id using Tapatalk 2 beta 5

[Q] Back to ICS from CM10 - Atrix 2

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.

[Q] Odd Phone Behavior after flashing H810PR10 (Lost 30GB of memory?)

It would appear that, in my habit of ruining everything, I failed the low effort boot and bricked my new LG G4. Thankfully, I remembered that in this instance you can flash the stock firmware to return to default. Unfortunately, the US firmware wasn't available, but apparently the Puerto Rico one was. I flashed that and got my phone back working just fine, kind of.
First, it doesn't lock normally. Usually, I set it to the 10 minute lock delay, where I just have to swipe unless 10 minutes have passed, then it requires the password. Instead of going to a lock screen, it skips that and just goes right into the phone. It's probably a settings thing, but it's weird.
The worst thing is that I have apparently lost 30GB of storage to "miscellaneous". When I plug it into my computer, it says that I only have 1GB of storage on the whole phone. What is going on here?

Same thing happened to me. Your not gonna be able to flash anything else because of the space on the phone, and can't get the System Image onto a MicroSD card to try and fix it either. I tried both then I just called up AT&T and told them about a problem which I did encounter with the flash making noise when turned on. They replaced the phone
Not sure if there is an actual work around to get the space back but what happened was you flashed it to the wrong partition.

I have the same issue. No one has figured it out yet

TheProblemCauser said:
Same thing happened to me. Your not gonna be able to flash anything else because of the space on the phone, and can't get the System Image onto a MicroSD card to try and fix it either. I tried both then I just called up AT&T and told them about a problem which I did encounter with the flash making noise when turned on. They replaced the phone
Not sure if there is an actual work around to get the space back but what happened was you flashed it to the wrong partition.
Click to expand...
Click to collapse
The problem is that I'm not encountering any issues like that so far. I doubt that they'd replace an issue caused by failed root.

Sorry for the double post, but is there any way that I can create a situation where I could get my phone replaced? I just got it, so it still is under warranty.

Flash the ATT system image back on to it and brick it is about your only option.
Sent from my LG-H810 using Tapatalk

Nynten said:
Sorry for the double post, but is there any way that I can create a situation where I could get my phone replaced? I just got it, so it still is under warranty.
Click to expand...
Click to collapse
Best case scenario would be to call them up and tell them your phone got bricked due to an update. Then let them know that you needed the said phone in a working condition until you can get a replacement.
Or tell them a bull**** problem, normally they send you the replacement then you ship yours out to them. Done this twice already I'm on my 3rd G4

TheProblemCauser said:
Best case scenario would be to call them up and tell them your phone got bricked due to an update. Then let them know that you needed the said phone in a working condition until you can get a replacement.
Or tell them a bull**** problem, normally they send you the replacement then you ship yours out to them. Done this twice already I'm on my 3rd G4
Click to expand...
Click to collapse
Can I just take it to the shop bricked "from an update" and get a new one there or do I have to mail it in?

How do I flash the stock att .Img with a full system data. Sorry of this is a noob question

Nynten said:
Can I just take it to the shop bricked "from an update" and get a new one there or do I have to mail it in?
Click to expand...
Click to collapse
You probably can. Its still under warranty so you should still get it replaced

TheProblemCauser said:
You probably can. Its still under warranty so you should still get it replaced
Click to expand...
Click to collapse
You can take it to a shop, but they will still call customer service and you will have to mail it in still. I paid extra to have a next day replacement.
Was told they don't switch phones in store anymore. Had a few local friends confirm their warranty replacements were done the same way from in store. I'm not sure if that is a national policy, regional, or local. I can say I did like it better when they could switch out in store.

Anybody come up with another solution besides sending the phone back??? I won my phone off a att contest. So I doubt if att will do anything about it. Plus I can't install the stock Img and re soft brick the phone because I don't have anymore space