I am now having issues SBF back to GB. I am not a n00b to flashing my D2G. I had just flash in yesterday back to stock really early before I went to work. So I tried again today and the USB port I was using on the same laptop I use all the time to flash it wanted to download the drivers to switch to BP mode so it took longer than normal so the SBF failed. So I attempted to turn off the phone and start again now it says it finished but still stuck at the boot loader and I get this message.
Bootloader
D0.11
Err:A5,70,70,00,1F
NEW_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
data Cable.
What do I do? I SBF my phone back to stock before like 3 or 4 time with not many problems.
Isn't D0.11 the new boot loader that you cant sbf back? If it is you are stuck with a brick until they find the new sbf file.
hd2life said:
Isn't D0.11 the new boot loader that you cant sbf back? If it is you are stuck with a brick until they find the new sbf file.
Click to expand...
Click to collapse
yup, I did some searching through the forum here and realized I I'm screwed. I have a bricked phone. Attempting to find my flip phone lol
hd2life said:
Isn't D0.11 the new boot loader that you cant sbf back? If it is you are stuck with a brick until they find the new sbf file.
Click to expand...
Click to collapse
no D0.11 isn't new
NEW_MAP Blank
Service Req'd
Click to expand...
Click to collapse
is the problem
likely you were on 2.3.4/4.5.629 update that came out 1 march 2012
and not much can be done till, SBF is leaked
if on verizon, take to store, and tell them the update, bricked your phone
they can either reflash, replace, or send to get reflashed
RSD Lite was created for stores to flash, but seems that they don't all do that anymore
if not, this could have happened, just from failed SBF, maybe
won't hurt to try [TOOL] ezSBF D2G
or check md5 check sum of SBF and use RDS Lite 5.6 or better or downgrade to older version
sd_shadow said:
no D0.11 isn't new
is the problem
likely you were on 2.3.4/4.5.629 update that came out 1 march 2012
and not much can be done till, SBF is leaked
if on verizon, take to store, and tell them the update, bricked your phone
they can either reflash, replace, or send to get reflashed
RSD Lite was created for stores to flash, but seems that they don't all do that anymore
if not, this could have happened, just from failed SBF, maybe
won't hurt to try [TOOL] ezSBF D2G
or check md5 check sum of SBF and use RDS Lite 5.6 or better or downgrade to older version
Click to expand...
Click to collapse
It is cuz of the latest OTA update. I am going to verzion to see if they can help me, cuz right now I have a bricked phone.
sd_shadow said:
no D0.11 isn't new
is the problem
likely you were on 2.3.4/4.5.629 update that came out 1 march 2012
and not much can be done till, SBF is leaked
if on verizon, take to store, and tell them the update, bricked your phone
they can either reflash, replace, or send to get reflashed
RSD Lite was created for stores to flash, but seems that they don't all do that anymore
if not, this could have happened, just from failed SBF, maybe
won't hurt to try [TOOL] ezSBF D2G
or check md5 check sum of SBF and use RDS Lite 5.6 or better or downgrade to older version
Click to expand...
Click to collapse
I tried flash cdt.bin, no luck, but the words "MEM-MAP Blank" is disappeared and error code has changed. ..
I'm keep trying
Sent from my DROID2 GLOBAL using xda premium
zyy757 said:
I tried flash cdt.bin, no luck, but the words "MEM-MAP Blank" is disappeared and error code has changed. ..
I'm keep trying
Sent from my DROID2 GLOBAL using xda premium
Click to expand...
Click to collapse
Is the phone still under warranty?
zyy757 said:
I tried flash cdt.bin, no luck, but the words "MEM-MAP Blank" is disappeared and error code has changed. ..
I'm keep trying
Click to expand...
Click to collapse
which cdt.bin, from 4.5.608 or 4.5.629?
did you just unzip update?
MEM-MAP Blank" is disappeared
Click to expand...
Click to collapse
interesting
Is the phone still under warranty?
Click to expand...
Click to collapse
think he is in china, so not likely an option
sd_shadow said:
which cdt.bin, from 4.5.608 or 4.5.629?
did you just unzip update?
interesting
Click to expand...
Click to collapse
.629 cdt.
Sent from my DROID2 GLOBAL using xda premium
Trilback said:
Is the phone still under warranty?
Click to expand...
Click to collapse
I'm not really care about this
Sent from my DROID2 GLOBAL using xda premium
Related
I was searched for a bootloader SBF last night to service my dead Droid 2, and I came across an amazing site with both, 2.35 and 2.37 bootloader versions, along with the original 2.2 that was shipped with the handset on release.
http://and-developers.com/sbf:droid2
I also have a question, if I wanted to flash back to 2.2, is it the latest (2.37) that won't allow it or did 2.35 block it?
For the record, my process was the following to repair a "Code Corrupt" in bootloader on the Droid 2:
- Download RSD Lite, the bootloader SBF, and the 2.3.20 SBF from MDW.
- Turn phone on, load bootloader SBF via RSD Lite
- The phone will restart, hold "X", and boot into recovery.
- Wipe all
- Pull battery
- Replace battery, hold "Up" on power up (back to flash mode, "Code Corrupt" should be gone)
- Flash SBF
- Pull battery when completed, ("Code Corrupt" will show back up)
- Reload bootloader SBF
- When completed, phone should boot back into a freshly flashed 2.3.20
This was my process, but yours may differ slightly.
UrbanBounca said:
For the record, my process was the following to repair a "Code Corrupt" in bootloader on the Droid 2:
- Download RSD Lite, the bootloader SBF, and the 2.3.20 SBF from MDW.
- Turn phone on, load bootloader SBF via RSD Lite
- The phone will restart, hold "X", and boot into recovery.
- Wipe all
- Pull battery
- Replace battery, hold "Up" on power up (back to flash mode, "Code Corrupt" should be gone)
- Flash SBF
- Pull battery when completed, ("Code Corrupt" will show back up)
- Reload bootloader SBF
- When completed, phone should boot back into a freshly flashed 2.3.20
This was my process, but yours may differ slightly.
Click to expand...
Click to collapse
Nice...im pretty sure this is exactly what i posted in the other thread for you to do. Im glad you got it figured out man. Sbf is something you need to know if your gonna flash roms on this phone
Shot from my level 60 crossbow of awesomness!
Is there an sbf for the r2d2 yet????
Sent from my DROID2 using XDA App
Mr1070 said:
Is there an sbf for the r2d2 yet????
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Oh yeah. Search for Team Black Hat 2.3.20 Triple Threat on Google. Use the full system SBF.
I did it. I'll answer any questions.
Sent from my R2D2 using XDA App
UrbanBounca said:
I was searched for a bootloader SBF last night to service my dead Droid 2, and I came across an amazing site with both, 2.35 and 2.37 bootloader versions, along with the original 2.2 that was shipped with the handset on release.
I also have a question, if I wanted to flash back to 2.2, is it the latest (2.37) that won't allow it or did 2.35 block it?
Click to expand...
Click to collapse
My phone on 2.2.20 has Bootloader D2.35.
Dunno if you can SBF the 2.35 over the 2.37 though.
hatzie said:
My phone on 2.2.20 has Bootloader D2.35.
Dunno if you can SBF the 2.35 over the 2.37 though.
Click to expand...
Click to collapse
I heard its a bad idea to go backwards.
Sent from my DROID2 using Tapatalk
You can change bootloaders all you want. We just don't have the ability to change kernels at this point.
UrbanBounca said:
You can change bootloaders all you want. We just don't have the ability to change kernels at this point.
Click to expand...
Click to collapse
Man it would be awesome if we could. This phone could be amazing with custom kernels. At least we can load modules and overclock though. SOMEONE CRACK EFUSE!
Sent from my ultra fast Liberated Droid 2
I have a question and figured this would be the perfect thread to ask it in.
My bootloader on my Droid 2 is D2.35. Is it worth flashing it to 2.37? Is there any real difference since the kernel is locked anyway?
Thanks for your time.
UlysisAM said:
I have a question and figured this would be the perfect thread to ask it in.
My bootloader on my Droid 2 is D2.35. Is it worth flashing it to 2.37? Is there any real difference since the kernel is locked anyway?
Thanks for your time.
Click to expand...
Click to collapse
If it's bothering you, you can update. You can switch back and forth between them all you'd like. I've noticed recently though, older is better, especially with the tyranny that Motorola has put on Droid's recently.
UrbanBounca said:
If it's bothering you, you can update. You can switch back and forth between them all you'd like. I've noticed recently though, older is better, especially with the tyranny that Motorola has put on Droid's recently.
Click to expand...
Click to collapse
No, I'm not bothered by it at all. It was more curiosity than anything.
And I agree with you on Motorola. That's why I rooted my phone the day after I got it.
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
Hi,
I was stupid and flashed a mod in CWM which now means i can't get past pulsating boot screen. Because you can't access CWm from boot i'm screwed.
Whats the best way to restore the phone back to default. I was on 2.3.6, Do i just flash the fxz file from fastboot and that is it? Which file do use from the HK/TW list here. Do is still need to flash the patch first? http://sbf.droid-developers.org/edison/list.php
Thanks in advance for your help.
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1396650
scroll down to flashing the fxz, and follow it exactly.
Make sure to dl the proper files for your phone. And properly patch the fxz.
Sent from my MB865 using xda premium
Fall of Enosis said:
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1396650
scroll down to flashing the fxz, and follow it exactly.
Make sure to dl the proper files for your phone. And properly patch the fxz.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Thanks for your reply mate.
I have the HK TW version of the phone and was on 2.3.6 (latest OTA) The patch that it talks about is for 2.3.5 right? so if i download the FXZ for 2.3.6 would i still need to apply the patch?
Plus i'm guessing this is the latest one right? "5.5.1-1_GC-109_HKTW_cfc.xml.zip"
Thanks again for help/
ahmadcentral said:
Thanks for your reply mate.
I have the HK TW version of the phone and was on 2.3.6 (latest OTA) The patch that it talks about is for 2.3.5 right? so if i download the FXZ for 2.3.6 would i still need to apply the patch?
Plus i'm guessing this is the latest one right? "5.5.1-1_GC-109_HKTW_cfc.xml.zip"
Thanks again for help/
Click to expand...
Click to collapse
You need the patch. without it you will not be able to get your phone back. There are a few files that are updated in the OTA that CANNOT be flashed back, so it will just fail. the patch makes it skip those, which is not a problem at all and you will never know it.
lkrasner said:
You need the patch. without it you will not be able to get your phone back. There are a few files that are updated in the OTA that CANNOT be flashed back, so it will just fail. the patch makes it skip those, which is not a problem at all and you will never know it.
Click to expand...
Click to collapse
Thanks for everyones help.
Here is what i did,
downloaded correct fxz file
patch files by copying them over the old zip file.
Drag and drop to RSD Lite
Plug in phone in fastboot mode and then install FXZ
Took about 15 minutes to finish. Now got a fully working Phone again.
(I did try it without patching files first and got an error first, so thanks for that tip. That is what i was mostly concerned about)
ahmadcentral said:
Thanks for everyones help.
Here is what i did,
downloaded correct fxz file
patch files by copying them over the old zip file.
Drag and drop to RSD Lite
Plug in phone in fastboot mode and then install FXZ
Took about 15 minutes to finish. Now got a fully working Phone again.
(I did try it without patching files first and got an error first, so thanks for that tip. That is what i was mostly concerned about)
Click to expand...
Click to collapse
glad to here. the first fxz is always scary, but I soft bricked 23 times in one day once, so I am well used to it, LOL.
lkrasner said:
glad to here. the first fxz is always scary, but I soft bricked 23 times in one day once, so I am well used to it, LOL.
Click to expand...
Click to collapse
Tell me about it. I can do all the basics and imo i think i know quite a lot about this stuff. But when something goes wrong you do start panicking a bit. Plus i just wanted to make sure i was doing everything 100% correct to avoid doing more damage to my phone.
what patching is
ahmadcentral said:
Thanks for everyones help.
Here is what i did,
downloaded correct fxz file
patch files by copying them over the old zip file.
Drag and drop to RSD Lite
Plug in phone in fastboot mode and then install FXZ
Took about 15 minutes to finish. Now got a fully working Phone again.
(I did try it without patching files first and got an error first, so thanks for that tip. That is what i was mostly concerned about)
Click to expand...
Click to collapse
hello,
can you tell me what that patching exactly means and how to do that. please help ,i got my phone softbricked
nani7
i have a motorola atrix 2 at&t(MB865).my phone was 2.3.6
1. I try to flash this firmware 5.5.1-EDEM-28-37-MEARET_cfc.xml.zip from this site http://sbf.droid-developers.org/edison/list.php with rsd.at 7/20 rsd was writting fail.i tried again with same result.after this my phone had problem with boot.the only method for boot was "vol down"+"vol up"+"power" and after i was pressing "Normal powerup".after all these my phone booted normal and worked normal.
2.after i flashed the Blur_Version.55.13.25.MB865.ATT.en.US.zip (ics) from this http://forum.xda-developers.com/showthread.php?t=1779968 and my phone was working normal but with the same problem with the boot.
3.after i tried to use this utillity http://forum.xda-developers.com/showthread.php?t=1805975 .this process had some failure and after this my phone is unable to boot.
with "vol down"+"vol up"+"power" i can choose normal power up, but phone stucks at boot image.in addition i can choose recovery and phone boots at recovery mode.i choose to update from sd with this file Blur_Version.55.13.25.MB865.ATT.en.US.zip but my phone writes that its unable to flash this.
4.after i try to flash InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.zip with rsd.the rsd wrote fail at 3/20 in addition i use the replace.zip with the same result.
5.after i try again the 3rd step with same results.
can anyone help me?
This whole mess started when you tried to flash MEARET firmware on your AT&T phone. NEVER mix firmware!
And trying recovery at this point is not going to work, as the ICS zip is just a large patch file for 2.3.6. And since it failed on the fxz, a portion of your system is missing so ICS won't install. You need to fxz back.
What step is the script falling at? A screenshot would be helpful.
And for the future, please post questions in the Q&A form.
Sent from my SAMSUNG-SGH-I727 using xda premium
you mean at 3rd step?
sorry.please move this thread at q&a
Yes the script from step three is what's going to save you here.
But we need to know where it's failing at.
Sent from my SAMSUNG-SGH-I727 using xda premium
i can see that problem is with cbt, recovey and cdrom partition.
Uh oh.
Which ICS version did you install? Please show need the thread.
I need to know which leak it was.
Sent from my SAMSUNG-SGH-I727 using xda premium
Blur_Version.55.13.25.MB865.ATT.en.US.zip
Well I hate to tell you man. But you are soft bricked until we find an fxz for ICS.
Recovery and cdrom are failing because cdt.bin isn't flashing. And we haven't found a fix for this yet.
Although the strange thing is that this shouldn't be happening on the first leak... but it is...
So you're bricked mate.
Sent from my SAMSUNG-SGH-I727 using xda premium
ok, i will wait.
thanks.
but please explain to me.i had a motorola a1200 and a siemens sx1.when i flashed a firmware, all the flash memory erased and new data wrote at flash.if i had bootloader, all was fine.the only method to brick a phone was to replace the battery when flash the bootloader(or flash false bootloader).
at A2, why when i write a new bootloader and new mbr(and partition table?) is necessary to flash the same or newer edition of firmware?this is because bootloader is locked?
i thought when i flash a new firmware, all the flash memory erased and writes new data(at the begining the bootloader, after mbr with partition table, after the image(i think this is the kernel of linux) and all other the data)
macnick said:
i have a motorola atrix 2 at&t(MB865).my phone was 2.3.6
1. I try to flash this firmware 5.5.1-EDEM-28-37-MEARET_cfc.xml.zip from this site http://sbf.droid-developers.org/edison/list.php with rsd.at 7/20 rsd was writting fail.i tried again with same result.after this my phone had problem with boot.the only method for boot was "vol down"+"vol up"+"power" and after i was pressing "Normal powerup".after all these my phone booted normal and worked normal.
2.after i flashed the Blur_Version.55.13.25.MB865.ATT.en.US.zip (ics) from this http://forum.xda-developers.com/showthread.php?t=1779968 and my phone was working normal but with the same problem with the boot.
3.after i tried to use this utillity http://forum.xda-developers.com/showthread.php?t=1805975 .this process had some failure and after this my phone is unable to boot.
with "vol down"+"vol up"+"power" i can choose normal power up, but phone stucks at boot image.in addition i can choose recovery and phone boots at recovery mode.i choose to update from sd with this file Blur_Version.55.13.25.MB865.ATT.en.US.zip but my phone writes that its unable to flash this.
4.after i try to flash InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.zip with rsd.the rsd wrote fail at 3/20 in addition i use the replace.zip with the same result.
5.after i try again the 3rd step with same results.
can anyone help me?
Click to expand...
Click to collapse
Use rsdlite and flash the Asian or Chinese stock firmware worked for me when I had this issue now I'm running 4.1.1 cm10 jb and its awesome!
If this works for you hit my thanks button
P.s phone must be in fast boot mode
Sent from my MB865 using XDA Premium HD app
Code:
whiteboi-hakz
can you tell to me which firmware you mean? and where i can find.
Code:
Fall of Enosis
i forget to tell you that i did the ics ota update from at&t.
so maybe i have the same problem with others...
macnick said:
Code:
whiteboi-hakz
can you tell to me which firmware you mean? and where i can find.
Code:
Fall of Enosis
i forget to tell you that i did the ics ota update from at&t.
so maybe i have the same problem with others...
Click to expand...
Click to collapse
http://sbf.droid-developers.org/edison/list.php
There is the firmware you wanted dude
Download retail Chinese
Sent from my MB865 using XDA Premium HD app
macnick said:
Code:
Fall of Enosis
i forget to tell you that i did the ics ota update from at&t.
so maybe i have the same problem with others...
Click to expand...
Click to collapse
If you did the OTA ICS update you WILL NOT be able to flash the FXZ back. We have no way out of this right now. And if you are bootlooping or stuck on the splash screen then you are bricked. Sorry mate.
Please read these threads:
http://forum.xda-developers.com/showthread.php?t=1897042
http://forum.xda-developers.com/showthread.php?t=1882335
whiteboi-hakz said:
http://sbf.droid-developers.org/edison/list.php
There is the firmware you wanted dude
Download retail Chinese
Sent from my MB865 using XDA Premium HD app
Click to expand...
Click to collapse
Whiteboi, thanks for your consideration of others but PLEASE, research before you try to help others. For one thing, he is on an MB865 AT&T phone and therefore MUST download the firmware for an AT&T phone. The international versions of the A2 are completely different, including radio, WiFi and the like. NEVER mix firmwares.
Also, he already flashed international firmware which is what got him into this predicament in the first place. He also installed the OTA update for ICS for which there is NO GOING BACK. Read the threads I gave him and educate yourself man.
I applaud you generosity, but if he wasn't already bricked, your advice would have surely/quite possibly bricked him. Be careful man.
Read, read, read!
Fall of Enosis said:
If you did the OTA ICS update you WILL NOT be able to flash the FXZ back. We have no way out of this right now. And if you are bootlooping or stuck on the splash screen then you are bricked. Sorry mate.
Please read these threads:
http://forum.xda-developers.com/showthread.php?t=1897042
http://forum.xda-developers.com/showthread.php?t=1882335
Whiteboi, thanks for your consideration of others but PLEASE, research before you try to help others. For one thing, he is on an MB865 AT&T phone and therefore MUST download the firmware for an AT&T phone. The international versions of the A2 are completely different, including radio, WiFi and the like. NEVER mix firmwares.
Also, he already flashed international firmware which is what got him into this predicament in the first place. He also installed the OTA update for ICS for which there is NO GOING BACK. Read the threads I gave him and educate yourself man.
I applaud you generosity, but if he wasn't already bricked, your advice would have surely/quite possibly bricked him. Be careful man.
Read, read, read!
Click to expand...
Click to collapse
Dude it works and he can then reflash his fw so what's the big deal the one I bricked was at&t non international and that method worked great but I'll take your advice man
Sent from my MB865 using XDA Premium HD app
i tried your method without any Success.
so "fall of enosis" is right.maybe the solve of the problem is to find an ics firmware(from at&t????)
macnick said:
i tried your method without any Success.
so "fall of enosis" is right.maybe the solve of the problem is to find an ics firmware(from at&t????)
Click to expand...
Click to collapse
OK well was worth a try I guess ay try his method and let's us know
Sent from my MB865 using XDA Premium HD app
macnick said:
i tried your method without any Success.
so "fall of enosis" is right.maybe the solve of the problem is to find an ics firmware(from at&t????)
Click to expand...
Click to collapse
Yeah man, if you OTA'd to ICS then I can almost guarantee it will fail at step 3 of the flash process which is the cdt.bin. If you are using the script it will also fail on the recovery portion and the cdrom portion. These are both because of the cdt.bin As of right now, we have no fix for this. Once again, this is the reason we are recommending people to ONLY use the first leak, and not OTA to ANYTHING unless it's 2.3.6 GB. Once again, reference the links I sent you.
You're bricked sir.
Until we find an ICS fxz. Which might be A LONG TIME.
Time to get a replacement/new phone.
Fall of Enosis said:
Yeah man, if you OTA'd to ICS then I can almost guarantee it will fail at step 3 of the flash process which is the cdt.bin. If you are using the script it will also fail on the recovery portion and the cdrom portion. These are both because of the cdt.bin As of right now, we have no fix for this. Once again, this is the reason we are recommending people to ONLY use the first leak, and not OTA to ANYTHING unless it's 2.3.6 GB. Once again, reference the links I sent you.
You're bricked sir.
Until we find an ICS fxz. Which might be A LONG TIME.
Time to get a replacement/new phone.
Click to expand...
Click to collapse
Thanked you as earned it man
Sent from my MB865 using XDA Premium HD app
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.