• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root So did i just brick my Atrix? (Installed new boot animation)

H

h0l7

Lurker
So I installed an old school playstation boot animation after rooting and now I cant get past said boot animation.

As i understand this would be a softbrick and there are ways out of it. I just cant seem to find out how to do such on this particular phone.


UPDATE: So after performing a factory reset it got rid of the new boot animation but is still looping with the stock boot animation. Im thinking i may have corupted my firmware does anyone have the original rom so I can try reflashing it?

UPDATE2: Ok sop aprently i screwed the pooch doing a reset because now i cant seem to figure out how to flash it as super one click freezes every time I try using that method and the RSD keeps giving me a failed to flash error message.

I'm at my wits end here Ive spent an hour before this post and every minute since hunting down information and trying difereent methods on these forums the atrix forums and the xda forums. I really hope someone can help me out of this one.
 
Can you fire up RSD on your phone?

Make sure your phone is turned off
Take out your microSD card and SIM card for the flashing process
While turning the phone on, hold the Volume Up button until it acknowledges RSD
Your device will say “Starting RSD protocol support”
 
Yes i tired both of those but got a flash failed every time i tried to use rsd.

problem is moot now as amazon next day aired me a new phone and i learned never to perform a factory reset on an android phone as it disables usb debugging pretty much locking you out.
 
Same thing happened to me last night. I bought my atrix in Florida on vacation and I live in Canada. I turned my phone off and then it would get to the at&t logo then reboot everytime I tried to turn it on. I tried charging the phone but the phone wouldnt even read the battery, no solution. I tried leaving the battery out for awhile, no solution. I called AT&T and they basically told me to get to florida before my 30day trial ends or im skrewed, no solution. Called motorola, told me to ship it to a family member in the states and have them bring it to an AT&T store to fix it, not a solution. Cut my wrists for 4 hours because i was without android, still didnt help.

FINALLY I restored my phone, lost all my data and the phone rebooted. Now to sell this piece of shit and but the first dual-core HTC on the market! F*** AT&T AND F*** MOTOROLA
 
iPhail said:
Same thing happened to me last night. I bought my atrix in Florida on vacation and I live in Canada. I turned my phone off and then it would get to the at&t logo then reboot everytime I tried to turn it on. I tried charging the phone but the phone wouldnt even read the battery, no solution. I tried leaving the battery out for awhile, no solution. I called AT&T and they basically told me to get to florida before my 30day trial ends or im skrewed, no solution. Called motorola, told me to ship it to a family member in the states and have them bring it to an AT&T store to fix it, not a solution. Cut my wrists for 4 hours because i was without android, still didnt help.

FINALLY I restored my phone, lost all my data and the phone rebooted. Now to sell this piece of shit and but the first dual-core HTC on the market! F*** AT&T AND F*** MOTOROLA
Click to expand...
So youre mad because something you did screwed up your phone and you bought it over 1300 miles away, then you want to blame ATT/motorola?

Thats like blaming a car maker for driving too fast and wrecking your new car.
 
stang99 said:
So youre mad because something you did screwed up your phone and you bought it over 1300 miles away, then you want to blame ATT/motorola?

Thats like blaming a car maker for driving too fast and wrecking your new car.
Click to expand...

Something I did aka turn it off then on again? Thats more like blaming a car for not starting because you parked it...
 
iPhail said:
Something I did aka turn it off then on again? Thats more like blaming a car for not starting because you parked it...
Click to expand...
Well if you parked it because you had decided to rip the electrical cables out and rewired it yourself then expected it to work then yeah, its exactly the same. Reboots are common practice in the tech field so its not like bricking is an expected occurrence unless the end used did something massively stupid.

Blaming the carrier/maker is equally stupid.
 
stang99 said:
Well if you parked it because you had decided to rip the electrical cables out and rewired it yourself then expected it to work then yeah, its exactly the same. Reboots are common practice in the tech field so its not like bricking is an expected occurrence unless the end used did something massively stupid.

Blaming the carrier/maker is equally stupid.
Click to expand...

So you are saying that phones are supposed to continually reboot themselves so the end user cant use them? Im not talking about the random reboots, im talking about boot loops where the phone wont even start, and no I didnt do anything to cause this except power off my phone. If you do your research you will find that its a common problem for people who havent even rooted their device. Blaming the manufacturer for making a defective product seems reasonable to me.
 
h0l7 said:
Yes i tired both of those but got a flash failed every time i tried to use rsd.

problem is moot now as amazon next day aired me a new phone and i learned never to perform a factory reset on an android phone as it disables usb debugging pretty much locking you out.
Click to expand...

Was there some sort of error code that RSD gave you?

I was having issues with RSD. It showed that my phone was connected, but it wouldn't update; I think I was getting an error something like (0X07701) or something to that effect.
 
if you are running windows 7 x64, you might need to try this.

1) Make sure the SBF file is in the install folder of RSD.
2) Name it something like 1.5.2.sbf
4) delete any flasherrorlog.txt files
3) Start RSD and you will get a fail error (0x7000) or something like that
4) close RSD and open a text file calles flashfail.txt or similar
5) you will see the file name (1.5.2.sbf) and a bunch of junk characters after it like this. 1.5.2.sbf
 
=KLRS=ZERO said:
if you are running windows 7 x64, you might need to try this.

1) Make sure the SBF file is in the install folder of RSD.
2) Name it something like 1.5.2.sbf
4) delete any flasherrorlog.txt files
3) Start RSD and you will get a fail error (0x7000) or something like that
4) close RSD and open a text file calles flashfail.txt or similar
5) you will see the file name (1.5.2.sbf) and a bunch of junk characters after it like this. 1.5.2.sbf
Click to expand...
 
=KLRS=ZERO said:
if you are running windows 7 x64, you might need to try this.

1) Make sure the SBF file is in the install folder of RSD.
2) Name it something like 1.5.2.sbf
4) delete any flasherrorlog.txt files
3) Start RSD and you will get a fail error (0x7000) or something like that
4) close RSD and open a text file calles flashfail.txt or similar
5) you will see the file name (1.5.2.sbf) and a bunch of junk characters after it like this. 1.5.2.sbf
Click to expand...
 
You must log in or register to reply here.
Back
Top Bottom