[WARNING] Don't Hard Brick Your Atrix! Look Here.

yokozuna82 · Jul 9, 2011 at 2:54 AM

What's nvflash recovery mode

PAulyhoffman · Jul 9, 2011 at 3:04 AM

nvflash is a tool for tegra2 devices. You will need Dev cable you can make or buy and SBK. when you get that I'll tell you how to use nvflash.

anomaly460 · Jul 9, 2011 at 3:11 AM

People returning their bricked phones for a warranty related replacement, is the reason why Moto did not want to unlock the bootloaders in the first place.....I hope the people that jumped in too soon and bricked replace their phones by honest means...

msd24200 · Jul 9, 2011 at 3:40 AM

AllTheWay said:
Gotcha. ;-)

Sent from my MB860 using XDA Premium App

you make it home to try it out yet?

Ilkinansr92 · Jul 9, 2011 at 3:45 AM

anomaly460 said:
People returning their bricked phones for a warranty related replacement, is the reason why Moto did not want to unlock the bootloaders in the first place.....I hope the people that jumped in too soon and bricked replace their phones by honest means...

yeh i hope i can get my phone replaced but its not that their bootloader briked our phones its flashing back to 1.83 that did it.

msd24200 · Jul 9, 2011 at 3:50 AM

Ilkinansr92 said:
yeh i hope i can get my phone replaced but its not that their bootloader briked our phones its flashing back to 1.83 that did it.

they had to have changed something i wouldn't be surprised is we don't end up seeing a new rsd, but of course thats purely speculation right now.

munchy_cool · Jul 9, 2011 at 3:54 AM

msd24200 said:
they had to have changed something i wouldn't be surprised is we don't end up seeing a new rsd, but of course thats purely speculation right now.

the only thing I can think off is the partition sizes ..

msd24200 · Jul 9, 2011 at 3:55 AM

msd24200 said:
they had to have changed something i wouldn't be surprised is we don't end up seeing a new rsd, but of course thats purely speculation right now.

don't try the 1.26 i just read this

jnl- over on irc tried and it bricked

geishroy · Jul 9, 2011 at 3:55 AM

has anyone tried going from the OTA update to the 2.3.4 cwm rom? if so does it work?

msd24200 · Jul 9, 2011 at 3:56 AM

munchy_cool said:
the only thing I can think off is the partition sizes ..

that makes since, so that means even if one uses samcripp's method to revert back, you still couldn't use sbf on any of the older builds right?

kennethpenn · Jul 9, 2011 at 4:05 AM

msd24200 said:
that makes since, so that means even if one uses samcripp's method to revert back, you still couldn't use sbf on any of the older builds right?

This "method" will not take care of this problem... it just flashes your system back to 1.8.3. You still have a brickable phone.

msd24200 · Jul 9, 2011 at 4:36 AM

kennethpenn said:
This "method" will not take care of this problem... it just flashes your system back to 1.8.3. You still have a brickable phone.

Do you think this will be the release build? If so we may be stuck for a while!

Sent from my MB860 using XDA Premium App

NibblerWeather · May 1, 2011 67 0 0

Surely moto is aware of this? Perhaps they will update the "get your phone on official software " sticky on the support forums. Kenn, thanks for posting this, saved my phone.

Sent from my MB860 using XDA Premium App

samcripp · Jul 9, 2011 at 4:50 AM

msd24200 said:
Do you think this will be the release build? If so we may be stuck for a while!

Sent from my MB860 using XDA Premium App

you are not stuck on anything, you can return to 183 by flashing system and boot img, just dont use sbf. theoricly speaking thats what kenns rom does, he flashes all the imgs except bl and radio (the radio as you see is a secondary flash). i really dont see how thats much different. no one is stuck. just dont use sbf to flash back. and you are cheddar!

with that said, this looks to be the OTA official, and the support that kenn got an sbf of it. once this goes live, this will be the norm, no flashing back.

samcripp · Jul 9, 2011 at 5:13 AM

geishroy said:
has anyone tried going from the OTA update to the 2.3.4 cwm rom? if so does it work?

it is safe to use kenns rom, give it a chance is very nice. make sure before you do that, to pull the boot and system imgs of your phone

players_inc17 · Jul 9, 2011 at 5:17 AM

i to had a hard brick. phone wasnt booting. only thing was red indecation light keep blicking. sbf back to 1.8.3 didnt do anything. THIS IS WHAT I DID TO FIX IT. i sbf all the way back to 1.2.6 that got my phone back functional finally! then manually update with ota's till i reach back up to 1.8.3. then fast boot oem unlock again, then fastboot cwm, then flash gb 4.5.91 and now everything is back up and working.

the2dcour · Jul 9, 2011

Compilation of info from bricked users: some started from fresh clean 1.8.3 (no pudding), kenneth started from 2.3.3. Everyone went to "official" OTA 2.3.4 from moto test server. Kenneth and another went back to 1.8.3 without eating their pudding, bricked. Another went to pudding after 2.3.4 failed to flash/softbricked but retained RSD/Fastboot, then flashed 1.8.3 and bricked as per other users.

THEORY: Flashing 1.8.3 with pudding built in may fail but leave you with RSD/fastboot intact. Do not try this unless you have a throwaway atrix (throw it at me?)

FACT: fastboot flashing system/osh/etc is completely SAFE (for now?) That is, kennethpenn's CWM update version is safe, and other CWMs constructed as such.

ADVICE: Unlocked users should not flash anything without unlocked bootloader BUILT IN. If in doubt, use fastboot and avoid radio/bootloader updates till further notice.

ricko2169 · Jul 9, 2011

kennethpenn said:
What is this?
This is a warning that multiple users, including myself, have hard bricked their devices by SBF flashing to 1.8.3 after installing an official 4.5.91 update.
How can I avoid this brick?
You can avoid bricking your device by not flashing any over-the-air updates to Android 2.3.4. Instead, try flashing the 2.3.4 zip over here.
What if I already flashed the official 4.5.91?
If you flashed the official update from XDA or by downloading through a dev-blur server (note: this excludes this ROM), you should avoid flashing SBF files in RSD Lite. We've confirmed this problem exists when users flash the 1.8.3 build specifically. It may happen with other SBF files, though.

What happens when you hard brick?
The error shows:

SVF:105.1:2
Failed to boot 0X1000

I bricked mine with the 1.5.7 SBF after installing the official 4.5.9.1 update too. I flashed the update only 1.8.3 SBF, did the 4.5.9.1 update and was having small issues with already installed programs so i thought I'll do the 1.5.7 full SBF then update OTA to 1.8.3 and voila hard brick

congtin2005 · Mar 16, 2011 47 8 0

Is there anyway to fix hard brick?

jruweaver · Jul 9, 2011 at 5:31 AM

players_inc17 said:
i to had a hard brick. phone wasnt booting. only thing was red indecation light keep blicking. sbf back to 1.8.3 didnt do anything. THIS IS WHAT I DID TO FIX IT. i sbf all the way back to 1.2.6 that got my phone back functional finally! then manually update with ota's till i reach back up to 1.8.3. then fast boot oem unlock again, then fastboot cwm, then flash gb 4.5.91 and now everything is back up and working.

Please explain further. How did you achieve the initial brick?

[WARNING] Don't Hard Brick Your Atrix! Look Here.

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Retired Forum Moderator / Retired Recognized Devel

Senior Member

Senior Member

Retired Recognized Developer

Retired Recognized Developer

Senior Member

Senior Member

Senior Member

Member

Senior Member