[Q] hard brick...? - Atrix 4G Q&A, Help & Troubleshooting

i'm sure there is a thread that has my specific problem here somewhere and i deeply apologize. if there is one please direct me to it.
i got my atrix rooted and was looking for a way to revert it back to stock.
i was using rsd lite 5.3.1 and an sbf 1.5.2 i believe and now all i get is a brief screen and then it goes blank. the screen says:
svf:105:1:2
failed to boot 0x1000
then it starts to flash a third line of text but the whole screen goes blank immediately. if anyone has any ideas. i bought it from a private party so i'm not sure if i could get it warranted...
any help or direction would be great.
just for additional info, my battery was charged prior to this happening (92%)

---

Read this

---

thanks. i actually just stumbled across that thread like 30 seconds ago. hope i can fix it. =/

---

Actually, if it shows starting RSD protocol or something to that effect, it can still be fixed.
If it shows nvflash than currently no, it cannot be fixed

---

i'm actually not sure what the third line of text is.
this is actually exactly what it does:
http ://youtu .be/ 3fwcoin3c_I
i'm not allowed to post links yet so i had to space it out.

---

Ah... It says entering Nvflash recovery mode. Sorry, it cannot be fixed. I feel for you, but one of the main 'rules' while using the atrix is to never flash a FroYo sbf over a Gingerbread one.

---

He didn't flash froyo he flashed the version before froyo. And yes your phone is officially a paperweight.
Sent from my MB860 using Tapatalk

---

aramirez723 said:
i'm sure there is a thread that has my specific problem here somewhere and i deeply apologize. if there is one please direct me to it.
i got my atrix rooted and was looking for a way to revert it back to stock.
i was using rsd lite 5.3.1 and an sbf 1.5.2 i believe and now all i get is a brief screen and then it goes blank. the screen says:
svf:105:1:2
failed to boot 0x1000
then it starts to flash a third line of text but the whole screen goes blank immediately. if anyone has any ideas. i bought it from a private party so i'm not sure if i could get it warranted...
any help or direction would be great.
just for additional info, my battery was charged prior to this happening (92%)
Click to expand...
Click to collapse
I just recently did this and my heart sank. I kept trying thou and found a way out. I held down the power button and the volume up key while placing the battery in. It gave me the following message.
SVF:105:1:2
Failed to boot 0x1000
PwrReason: PWR_KEY_PRESS
Starting Fastboot protocol support.
From here I was able to fastboot and unlock the phone and install the CWM recovery. I did fastboot reboot at the end and now I have a functional phone again . Useful information
Also, sorry for digging up an old thread, but it's one of the first ones that google pulls up when you look up that error code.

---

please help, same issue
Hi
I recently did the same thing, however I used 2.3.6 4.5.141 sbf to flash my currently 2.3.6. 4.5.1.45 . There was a problem with a font installer i and this this turned out to be my last restort. RSD Lite failed, twice o nthe 100% completion, something to do with failed to enter BP mode. Note that, on normal power on i am getting failed to boot 1.
Power + Vol Down
entering nvflash recovery, cuts off
After a full night charge, same thing but says battery too low in ddition.
Power + Vol Up
failed to boot 1,
power reason :charger ;
Starting fastboot protol support
Battery too low
prior to allow this battery low issues, when i did the power + vol up and used fastboot, i was abel to run fastboot commands, but was not able to do anythin successufly, example, i got device ID, but erase failed, even oem unlock. I believe the bootloader is still locked due to the update i received 4.5.145. Device is rooted.
Note i had unlocked and rooted and used all sorts of roms before, then reverted back to stock to simply get the 4.5.145 update, then re root.
I really need some assistance, anyone.
neph81 said:
I just recently did this and my heart sank. I kept trying thou and found a way out. I held down the power button and the volume up key while placing the battery in. It gave me the following message.
SVF:105:1:2
Failed to boot 0x1000
PwrReason: PWR_KEY_PRESS
Starting Fastboot protocol support.
From here I was able to fastboot and unlock the phone and install the CWM recovery. I did fastboot reboot at the end and now I have a functional phone again . Useful information
Also, sorry for digging up an old thread, but it's one of the first ones that google pulls up when you look up that error code.
Click to expand...
Click to collapse

---

thelostcoin said:
Hi
I recently did the same thing, however I used 2.3.6 4.5.141 sbf to flash my currently 2.3.6. 4.5.1.45 . There was a problem with a font installer i and this this turned out to be my last restort. RSD Lite failed, twice o nthe 100% completion, something to do with failed to enter BP mode. Note that, on normal power on i am getting failed to boot 1.
Power + Vol Down
entering nvflash recovery, cuts off
After a full night charge, same thing but says battery too low in ddition.
Power + Vol Up
failed to boot 1,
power reason :charger ;
Starting fastboot protol support
Battery too low
prior to allow this battery low issues, when i did the power + vol up and used fastboot, i was abel to run fastboot commands, but was not able to do anythin successufly, example, i got device ID, but erase failed, even oem unlock. I believe the bootloader is still locked due to the update i received 4.5.145. Device is rooted.
Note i had unlocked and rooted and used all sorts of roms before, then reverted back to stock to simply get the 4.5.145 update, then re root.
I really need some assistance, anyone.
Click to expand...
Click to collapse
I was able to get rid of the "battery too low" message by popping my battery out, cutting up a usb cable, and then plugging the cable into a usb charger ac adapter. The two cables I needed were red and black. Red went on positive lead. Black went on negative lead. I had to let it charge for at least a few hours. This is kind of dangerous and can cause a fire. Don't leave it unattended. Make sure the battery never gets hot. Mine never even got warm. I used three pieces of tape to secure the cable to the battery. I used scissors to cut the tape. One large piece of tape to hold the majority of the cable. One small piece of tape to hold the two shielded red and black wires in place, and another small piece of tape on the end to hold the wires onto the leads. Be careful not to let the wires cross over onto the any of the other leads.
But now I'm stuck. If I hold vol down, it will say "booting into nvflash recover mode" and then quickly go black. The led light goes off also. It's very quick...maybe half a second. I had to take a picture of it in order to be able to read what it says. If I hold vol up it will go to fastboot. If I press nothing it says "failed to boot 1". I can't go to rsd protocol or do anything else.

---

once bricked phone no longer charges battery you must buy a wall battery charger or a 5 wire usb cable. I bought the wall charger and extra battery for 15 bucks off ebay. battery must be fully charged before unbricking your phone. you need to flash the proper pudding files for the version you are running. i used xatrixweb.webs.com to fix my bricked phone worked great

---

overboard1978 said:
once bricked phone no longer charges battery you must buy a wall battery charger or a 5 wire usb cable. I bought the wall charger and extra battery for 15 bucks off ebay. battery must be fully charged before unbricking your phone. you need to flash the proper pudding files for the version you are running. i used xatrixweb.webs.com to fix my bricked phone worked great
Click to expand...
Click to collapse
In my case, xatrixwebs.webs.com is what hard bricked my phone.

---

fragmentalstew said:
In my case, xatrixwebs.webs.com is what hard bricked my phone.
Click to expand...
Click to collapse
worked very well for me once i used a full battery. and had to read up his instructions forgot to mention fail to boot XXXX automaticly puts phone in a rsd protocal state after 5 seconds if you dont touch it i beleive it was step 2 where he said to select rsd but phone would read fail to boot just run rsd there and after phone boots with stock software.

---

fragmentalstew said:
I was able to get rid of the "battery too low" message by popping my battery out, cutting up a usb cable, and then plugging the cable into a usb charger ac adapter. The two cables I needed were red and black. Red went on positive lead. Black went on negative lead. I had to let it charge for at least a few hours. This is kind of dangerous and can cause a fire. Don't leave it unattended. Make sure the battery never gets hot. Mine never even got warm. I used three pieces of tape to secure the cable to the battery. I used scissors to cut the tape. One large piece of tape to hold the majority of the cable. One small piece of tape to hold the two shielded red and black wires in place, and another small piece of tape on the end to hold the wires onto the leads. Be careful not to let the wires cross over onto the any of the other leads.
But now I'm stuck. If I hold vol down, it will say "booting into nvflash recover mode" and then quickly go black. The led light goes off also. It's very quick...maybe half a second. I had to take a picture of it in order to be able to read what it says. If I hold vol up it will go to fastboot. If I press nothing it says "failed to boot 1". I can't go to rsd protocol or do anything else.
Click to expand...
Click to collapse
failed to boot 1 is rsd protocol run rsd on your computer it will find it

---

overboard1978 said:
failed to boot 1 is rsd protocol run rsd on your computer it will find it
Click to expand...
Click to collapse
Holy ****! Thank you so much.