Database Info

[Q] Can't downgrade to lower SBF after 4.5.692 - phone is bricked

Hi all,
I am asking this question for a friend who is oversea. She have Motorola Droid 2 Global. Initially, she was using SBF 4.5.608 then she upgraded her phone to SBF 4.5.629. Everything works fine and dandy until she decided to downgrade it to 2.330 in order to wipe her phone and reset it. For some reason, the phone is bricked. She can't downgrade to any lower SBF version. She's getting error message upon boot. Charging doesn't seem to work either.
The error message that showed up is:
Bootloader
D2.35
err A50,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to program
Tranfer Mode: USB.
I am seeking tips and advices from the hive mind and hoping someone can help.
Thank you in advance.
-leapfrog

This is a known problem, threads all over various forums. Basically, until/unless the 4.5.629 SBF gets leaked, nothing can be done. Some people have been able to convince Verizon that the problem was caused by a bad update and get the phone replaced, and Motorola has reflashed it for some as well, but this seems to be on a case by case basis.

are you sure it says
Bootloader
D2.35
Click to expand...
Click to collapse
D2G should say
Bootloader
D0.11
Click to expand...
Click to collapse
looks like she has R2D2 or Droid 2 not D2G
same problem though, maybe, if she upgraded to 4.5.622.A957 not good
find out for sure what model number A957, A956, A955, or A953
I wrote some differences, it's not real precise or finishedThe Difference Between:
The Droid 2, Milestone2, R2D2,and the Droid 2 Global
I think she flashed wrong SBF, if so just flash correct one, should be fine

silver6054 said:
This is a known problem, threads all over various forums. Basically, until/unless the 4.5.629 SBF gets leaked, nothing can be done. Some people have been able to convince Verizon that the problem was caused by a bad update and get the phone replaced, and Motorola has reflashed it for some as well, but this seems to be on a case by case basis.
Click to expand...
Click to collapse
Thanks, I guess it seemed many people have bricked their phone because Verizon decided to stop people from reversing back to older sbf.

sd_shadow said:
are you sure it says
D2G should say
looks like she has R2D2 or Droid 2 not D2G
same problem though, maybe, if she upgraded to 4.5.622.A957 not good
find out for sure what model number A957, A956, A955, or A953
I wrote some differences, it's not real precise or finishedThe Difference Between:
The Droid 2, Milestone2, R2D2,and the Droid 2 Global
I think she flashed wrong SBF, if so just flash correct one, should be fine
Click to expand...
Click to collapse
I sent her the question. I think she tried different SBF and no luck so far.
Thanks!!!

i was gonna try the "bad update and send it into verizon" idea and get my phone replaced, since it doesnt come stock .629 . Thus problem solved??

yourdroidsir said:
i was gonna try the "bad update and send it into verizon" idea and get my phone replaced, since it doesnt come stock .629 . Thus problem solved??
Click to expand...
Click to collapse
if you get a different phone, it should be on 2.4.33 if new, they may try to give you a refurbished
you are going to send it?
they can just flash 4.5.629 and send back to you
they have the SBF, just won't share

Hard brick?

I successfully flashed to att ICS using Jim's method. Then I decided to roll back to 2.3.6 and used Jim's ICS back to 2.3.5 fxz fix zip file. The RSD stopped at 5/19 reboot bootloader for a long time and the screen was off. I hit the power button trying to turn on the screen without thinking. Then I realized that I was flashing! It was too late and I saw FAILED on RSD. My A2 cant turn on anymore. I did not unplug or pull the battery. Any help would be appreciate!

qtqt710 said:
I successfully flashed to att ICS using Jim's method. Then I decided to roll back to 2.3.6 and used Jim's ICS back to 2.3.5 fxz fix zip file. The RSD stopped at 5/19 reboot bootloader for a long time and the screen was off. I hit the power button trying to turn on the screen without thinking. Then I realized that I was flashing! It was too late and I saw FAILED on RSD. My A2 cant turn on anymore. I did not unplug or pull the battery. Any help would be appreciate!
Click to expand...
Click to collapse
DId you replace ALL of the files and then point the RSD to the xml?

Can you boot into fastboot by holding power button and vol down.If can you just reflash it using rsd lite.Tell me more detail about your atrix 2 current rom and which version of rom you are flash with rsdlite.
Sent from my MB865 using xda premium

Exact same problem has occurred to me as well.
I did replaced the files Jim created to FXZ back to 2.3.6 from ICS
My Battery was fully charged at the time of flashing. Flashing stopped at 5/19 reboot bootloader for 15 mins then tried rebooting it manually but it didn't started.
Now I've tried everything but it is not even starting in Fastboot
Please help me with this, I don't want to start any new thread so posted my problem here.
EDIT: I think this is a common problem as the OP here also have the same problem
http://forum.xda-developers.com/showthread.php?t=1781045
http://forum.xda-developers.com/showthread.php?t=1700775
I only flashed ICS when Jim confirmed that it was possible to revert back to 2..3.5
I think there is a problem in reverting back to 2.3.5 once applied ICS update and people should be aware of that.
Everyone should stop flashing ICS leaks otherwise they might end up bricking their phone forever.

100% same to me.
Up to ICS ok, back to Fxz with RSD and stuck at 5/19 reboot-bootloader step, I disconnected cable and phone black forever.
A lot of people they failed when flash with RSD but no problem, just take battery out and return, boot again to fastboot to re-flash. I think wrong file in Fxz not makes this problem, main cause I still don't know ! Maybe we are unlucky man ?

FXZ is not wrong one as I did used it when I had to flash back to stock from lithium Rom last week. I think phone is dead because it is not even booting into fastboot.. I've tried even booting to our stock recovery by pressing 3 buttons but no luck so far.
Its just very bad few hours back I was running ICS and now my phone is not even booting up.

OMG man!! I should have make a thread about this yesterday, but maybe nobody would of paid attention. I didn't really want this to happen to anyone, when flashing from 4.0.4 back to 2.3.5 it will get stuck at 5/20, something like that saying "rebooting loader". Now my phone with a blackscreen is getting hot when I insert the battery and when I plug it without a battery into my laptop or wallcharger and I dont have warranty. I call it white LED of death, when I plug it in to my laptop without a battery hehe , so I guess i'll be paying maybe 200$ dollar for it to be repaired, well if they repair it though, they charge so much here.. But i'm still trying to look what I can do, before I take it to a repair shop.

I heard about this problem when leak ICS for China/HK market 1 month ago, from xda man, and Jim he warned everybody here take care when coming back GB from ICS leak should make your phone bricked.
Now ATT ICS leak was released and all trusted Devs here confirmed that we can turn back to GB without problem, so I thought that it was safe to do with. Next day Jim posted new thread with new patch file. So sad ... I'm too late, we're too late ...

vinamilk said:
I heard about this problem when leak ICS for China/HK market 1 month ago, from xda man, and Jim he warned everybody here take care when coming back GB from ICS leak should make your phone bricked.
Now ATT ICS leak was released and all trusted Devs here confirmed that we can turn back to GB without problem, so I thought that it was safe to do with. Next day Jim posted new thread with new patch file. So sad ... I'm too late, we're too late ...
Click to expand...
Click to collapse
I didn't even flashed ICS leak first day, I did it second day when Jim confirmed and uploaded a link for new replace files.

prasannapmv said:
I didn't even flashed ICS leak first day, I did it second day when Jim confirmed and uploaded a link for new replace files.
Click to expand...
Click to collapse
So this is the point that I'm very confused, I think that even failed flashing phone still powered on normally : wrong boot.img --> just jamed at boot logo, wrong bootloader --> screen turn on and shows errors; need to be flashed again by RSD or script. Some man here even not flashed anything, just root then reboot and phone dead without any reason.

vinamilk said:
So this is the point that I'm very confused, I think that even failed flashing phone still powered on normally : wrong boot.img --> just jamed at boot logo, wrong bootloader --> screen turn on and shows errors; need to be flashed again by RSD or script. Some man here even not flashed anything, just root then reboot and phone dead without any reason.
Click to expand...
Click to collapse
I guess it has something to do with our bootloader, maybe it's stuck or not even working.

darkmixta said:
I guess it has something to do with our bootloader, maybe it's stuck or not even working.
Click to expand...
Click to collapse
I just talked to a Motorola service person he was saying in some rare cases a inbuilt ROM(read only memory) chip which stores bootloader files gets corrupted and in that case it might not even be possible to boot into fastboot.
I don't know how far he is right but one ting we are sure that our hardware was perfectly ok before flashing FXZ.
For me I even made sure that my battery was fully charged before starting FXZ.

prasannapmv said:
I just talked to a Motorola service person he was saying in some rare cases a inbuilt ROM(read only memory) chip which stores bootloader files gets corrupted and in that case it might not even be possible to boot into fastboot.
I don't know how far he is right but one ting we are sure that our hardware was perfectly ok before flashing FXZ.
For me I even made sure that my battery was fully charged before starting FXZ.
Click to expand...
Click to collapse
Same here I had like 90% battery or more, is you're phone becoming hot? When you plug it in or insert the battery?

darkmixta said:
Same here I had like 90% battery or more, is you're phone becoming hot? When you plug it in or insert the battery?
Click to expand...
Click to collapse
yes its getting heated when connected to a wall socket or on a battery.

Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium

prasannapmv said:
yes its getting heated when connected to a wall socket or on a battery.
Click to expand...
Click to collapse
Hahaha, what should we do? Yesterday I felt like throwing my phone into the wall man and just %$#@ Motorola, this is like the biggest failure ever!! Hard bricked without doing something wrong.. Wish I could go back in time sometimes and I don't even have warranty which sucks, what are you gonna do?
Really hard to hard brick? http://forum.xda-developers.com/showpost.php?p=28324515&postcount=10
We hard bricked so easy..

jimbridgman said:
Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I was already using RSD 5.7

jimbridgman said:
Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I did not. It is 5.6. That may be the reason. I got my A2 from att in Nov 2011, so I guess it is the same earlier version, right?

To those with the issue, can you not get back into ap fast boot? Either hold both volume buttons down with power, then select it from the menu, or i have found that holding up with power will boot you right into fastboot.
Sent from my MB865 using xda premium

Fall of Enosis said:
To those with the issue, can you not get back into ap fast boot? Either hold both volume buttons down with power, then select it from the menu, or i have found that holding up with power will boot you right into fastboot.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Nope they can not even power on anymore. This is what we all feared. The hk leak had this same thing in it...
Looks like moto will be warrantying a bunch of phones.
I am just not sure why I can still do it...
We have had way too many of these now for it to be user error or an accident.
Sent from my SAMSUNG-SGH-I747 using xda premium

Atrix 2 bricked.

I'm pretty sure i screwed myself here, but hopefully there might be a chance to fix it. I was flashing my phone back to stock gingerbread by using RSD, my phones data cord wiggled itself out when i bumped my desk, now its bricked. :\ any possibility of fixing this?

TinnuiN said:
I'm pretty sure i screwed myself here, but hopefully there might be a chance to fix it. I was flashing my phone back to stock gingerbread by using RSD, my phones data cord wiggled itself out when i bumped my desk, now its bricked. :\ any possibility of fixing this?
Click to expand...
Click to collapse
Can you still get into AP fastboot?
Sent from my MB865 using xda premium

There's totally still hope
It takes some pretty bad luck for this to actually kill it
just needs to run again, maybe manually
BUT, we need more detail to help. what version of the phone (ATT, SEARET, etc), what os version were you on before (ICS leak 1, 2, ota, GB, etc), what step was it on when it failed, what does the phone do now (totally dead, white light only, can turn on into fastboot with boot failure, etc.)
also, how much battery did you have when you tried to flash.
be specific, and we can help, do not lose hope quite yet.

lkrasner said:
There's totally still hope
It takes some pretty bad luck for this to actually kill it
just needs to run again, maybe manually
BUT, we need more detail to help. what version of the phone (ATT, SEARET, etc), what os version were you on before (ICS leak 1, 2, ota, GB, etc), what step was it on when it failed, what does the phone do now (totally dead, white light only, can turn on into fastboot with boot failure, etc.)
also, how much battery did you have when you tried to flash.
be specific, and we can help, do not lose hope quite yet.
Click to expand...
Click to collapse
I can still boot to AP fast boot, in fact thats all it boots from, i was running SVC6, so 2.3.6 and i was trying to roll back to 2.3.5 so i could update to ota ICS. when i turn the phone on all it does is boot to AP fast boot.

Its an AT&T atrix 2, the battery was at 70% when flashing, and i was on step 6, i tried re running it, it stayed on step 1 for hours.

Did you make sure to patch the fxz?
Sent from my MB865 using xda premium

Axis_Drummer said:
Did you make sure to patch the fxz?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
after it was to late.

TinnuiN said:
after it was to late.
Click to expand...
Click to collapse
If you can still access fastboot, you're still ok. Just try it again. Once you patch the file, you shouldn't have to do it again.
If it's not playing well try a different computer.
If you can't access fastboot, and no lights at all will come on, you may be out of luck man..
Sent from my MB865 using xda premium

TinnuiN said:
I'm pretty sure i screwed myself here, but hopefully there might be a chance to fix it. I was flashing my phone back to stock gingerbread by using RSD, my phones data cord wiggled itself out when i bumped my desk, now its bricked. :\ any possibility of fixing this?
Click to expand...
Click to collapse
Have you tried this????
http://forum.xda-developers.com/showthread.php?t=1539167
Sent from my MB865 using xda premium

Okay, now i have a new problem, the battery is to low to program, if i plug the phone into the wall then i can get it to boot to the AP menu, and if i plug it into my computer i can get it to show a white solid light. any ideas?

TinnuiN said:
Okay, now i have a new problem, the battery is to low to program, if i plug the phone into the wall then i can get it to boot to the AP menu, and if i plug it into my computer i can get it to show a white solid light. any ideas?
Click to expand...
Click to collapse
You need to charge your battery somehow if you don't have wall charger try Mcgrubber method...
Sent from my MB865 using xda premium

[Q] Hard Bricked GS3

Hello, I just got my new GS3 yesterday. Eager to root and ROM and all the fun stuff. I rooted and unlocked, and used Odin to flash CWM Recovery. Flashed the latest version of Android Revolution HD 16. I wiped cache, dalvik, the whole 9 yards. I did not WIPE boot.img though. Flashed Android Revolution 16, it all went good. Clicked Reboot Phone in CWM Recovery and nothing. No LED light on when plugged into USB or via wall charger. No Download mode, or recovery. Nothing, like nothing at all. Anything you guys suggest?
EDIT: I am not sure if it is Hard Bricked. When I plug it into my PC, it makes a sound. Also tries to install a driver and fails every time.
EDIT2: Okay guys, my fault. Downloaded a ROM that was meant for a different model/type GS3 forum when I have a Verizon GS3 (SCH-1535). Anyone know how to fix this problem? Please disregard this incorrect forum post.

If you flashed anything related to the international S3, Google search J-tag! Or return the device and play dumb...

droidstyle said:
Google search J-tag! Or return the device and play dumb...
Click to expand...
Click to collapse
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?

T Greezy said:
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?
Click to expand...
Click to collapse
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.

droidstyle said:
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.
Click to expand...
Click to collapse
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?

T Greezy said:
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?
Click to expand...
Click to collapse
No that verifies what i previously posted.

droidstyle said:
No that verifies what i previously posted.
Click to expand...
Click to collapse
I have faith, thought. I can maybe push something using ADB you think?

You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app

josh995 said:
You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!

T Greezy said:
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!
Click to expand...
Click to collapse
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!

No one is going to stop you. You flashed an international ROM on an s3. This is a known method of hard bricking your s3.
Sent from my SCH-I535 using xda app-developers app

T Greezy said:
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!
Click to expand...
Click to collapse
That sounds about right. Luckily it's $60 and not $600 for a new phone
Sent from my SCH-I535 using xda app-developers app

Same thing happened to me. Needed a j-tag but risked calling Verizon told them my phone wouldn't come on all they asked me was if I damaged it with water or heat. (Either Verizon doesn't care or actually they just scrap the phone) I was rooted and unlocked but flashed the wrong carrier rom. Now I have a replacement phone that cost me $0.
They sent me the 16g and not the 32g by mistake I figured I've pushed my luck enough
Sent from my SCH-I535 using Tapatalk 2

First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.

ericerk said:
First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.
Click to expand...
Click to collapse
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.

I do have a question for the op and the other guy who flashed an international ROM. Were did you get them and how did you find then ( like was it a site you googled?) I've noticed a lot of these lately and am wondering if it's something that can be avoided (besides the obvious read what you're flashing)
To the adb guy there us no recovery on his phone it was overwritten by part of the international ROM. he needs to JTAG his phone, don't call Verizon. You did this to your own phone, pay the 60 and learn your lesson.
Sent from my SGS3 running Eclipse 2.1

droidstyle said:
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.
Click to expand...
Click to collapse
One day someone is going to find a way to unbrick the hard brick, lol. Eventually. Anyways, if it was "dead" then why would it show my S3 as "QHSUSB_DLOAD"? and attempts to install a driver. I'm gonna try to find the right driver to manually install, and troubleshoot from there. I mean come on guys, be optimistic. How great if this problem was RESOLVED? Also, the download mode got wiped/overwritten from a different ROM for a different model of the GS3. What about the Recovery? CWM? If I can just magically, somehow, maybe even push some type of command. Even maybe ADB? Or something in the terminal. I'm really trying to find a solution. So in the future, we will have a SOLUTION.
Anyways, I'm going to be shipping my GS3 Monday or Tuesday for Samsung to repair (If they can) or replace for no charge!
Wish me luck guys, gonna be really thinking out of the box.

Hope you can figure it out. But someone had a way to fix a hard brick.... The JTAG
Sent from my SGS3 running Eclipse 2.1

Okay guys, I've actually have gotten some good progress, I hope! I came across a thread that a guy named (therockk) he also, hard bricked his S3. Sent him a PM, and he told me he got ODIN to recognize his hard bricked S3 "WITHOUT" download mode. He said he found a driver for QHSUSB_DLOAD and manually applied the driver update. His PC, then recognized his S3 as a ID CODE: COM10 - I do not know what that means, I asked around. Some people say that it is the code for when your phone is connected in Download Mode? Nevertheless, this is good in my eyes. The phone as now, recognized as COM10 in ODIN, in its hard-bricked stage. This could be that also, maybe, the phone will be recognized in ADB/Fastboot commands. Maybe we can get something going here guys! I'm trying to look on the bright side. I'll keep you posted.
EDIT: Okay guys, was looking at some screenshots of the CODE ID's. Like I said, my buddy "therockk" said he got ODIN to recognize his phone as a COM10, while being hard-bricked. I am guessing there are different CODE ID's for each model/version of the S3. I did make an observation that he, has a different model S3 ( i747 ) and he got his to see COM10. Which means it was Added!! - My Verizon S3 (SCH-1525) should come up as COM4 when the PC recognizes it. When I do get my PC to recognize my S3, I will confirm that my SCH-1535 phone comes up as COM4, if not, I will confirm the correct CODE ID. therockk's i747 came up as a COM10, that is confirmed.
EDIT 2: Okay guys! Updated the driver successfully! QSHUSB_DLOAD is now Qualcomm HS-USB QDLoader 9008 (COM8). I feel like we're getting closer. Now to see if Odin will pick it up!

I can probably help you through this problem after work tonight if you are still having trouble. Just pm me around 10pm est
Sent from my SCH-I535 using xda app-developers app

[Q] Atrix 2 Bricked After Jellybean Fail PLEASE HELP

Hey guys,
I'm somewhat new to Jailbreaking and Rooting Android Devices. I was working on my rooted 4.0.4 Atrix 2 today and wanted to install JellyBean. My first attempt I used the RSD lite program to install it. Found it I was using the wrong ROM (I'm a noob) and was stuck at the bootloader. Then, I used Wonderful RSD lite to use my fxz I downloaded. I'm pretty sure i downloaded the wrong one, so It flashed and got to step 5 and then gave me a fail. Now the device won't power on and it's either because I went from a soft brick to a hard brick. Or, the battery died. i have the original charging which i'm doing right now. Please help I'm scared ****less.

ITGuy420 said:
Hey guys,
I'm somewhat new to Jailbreaking and Rooting Android Devices. I was working on my rooted 4.0.4 Atrix 2 today and wanted to install JellyBean. My first attempt I used the RSD lite program to install it. Found it I was using the wrong ROM (I'm a noob) and was stuck at the bootloader. Then, I used Wonderful RSD lite to use my fxz I downloaded. I'm pretty sure i downloaded the wrong one, so It flashed and got to step 5 and then gave me a fail. Now the device won't power on and it's either because I went from a soft brick to a hard brick. Or, the battery died. i have the original charging which i'm doing right now. Please help I'm scared ****less.
Click to expand...
Click to collapse
If you can still get into fastboot mode, then it isn't hardbricked yet. What model is your phone? If it is AT&T branded, DO NOT FLASH IT!! It is for Asian retail, and international phones only.
Sent from this thing.

1BadWolf said:
If you can still get into fastboot mode, then it isn't hardbricked yet. What model is your phone? If it is AT&T branded, DO NOT FLASH IT!! It is for Asian retail, and international phones only.
Sent from this thing.
Click to expand...
Click to collapse
Yeah, I was able to get it into Fastboot. When I was able to (Past Tense) I tried re-flashing it with RSDLite using a FXZ. But, I believe it was the wrong one and It attempted to flash and got stuck at 5/23 which was the bootloader. And now it won't boot, but I do believe it charges. Just won't turn on at all. It is under warranty

ITGuy420 said:
Yeah, I was able to get it into Fastboot. When I was able to (Past Tense) I tried re-flashing it with RSDLite using a FXZ. But, I believe it was the wrong one and It attempted to flash and got stuck at 5/23 which was the bootloader. And now it won't boot, but I do believe it charges. Just won't turn on at all. It is under warranty
Click to expand...
Click to collapse
I sent you a pm
Sent from this thing.

1BadWolf said:
I sent you a pm
Sent from this thing.
Click to expand...
Click to collapse
Thanks. I replied

Maybe you just suck at installing ROMs and should hold the jumpers yourself.

Not ITguy420 said:
Maybe you just suck at installing ROMs and should hold the jumpers yourself.
Click to expand...
Click to collapse
I hate to say this, it looks like you have hard bricked your A2. If it is still under warranty, return it to the vendor and play dumb. Do not tell your vendor that you tried to do a fxz. Good luck.