My method on 2.3.6

[Doogiedoo]

I know there have been varying posts on the subject, but I thought I would share my experience with the update. I originally started out on a bootloader unlocked, rooted, At&t branded Atrix. I had installed the 2.3.4/4.5.91 fruitcake previously and had been using it for some time. When the update came down I rolled back to stock recovery using fastboot and after the installation of the update, the phone gave me an failed to boot 4. I used rsd to flash the official 2.3.4/4.5.91. I received a failed to boot 1. (After going to launder my, now soiled, trousers) I noticed that when I plugged the phone in, RSD still recognized the phone, even though it did not show the "entering RSD mode" tag. It occured to me to attempt to flash pudding using the 4.2 auto unlock. Immediately after flashing pudding the phone booted up and everything was working fine.
At this point I rooted and installed clockwork on the phone using the same 4.2 tool. I then used Voodoo OTA Rootkeeper to back up my root. Unfortunately the tool installs clockwork in order to root the phone, so I had to flash back to stock recovery using fastboot. . I then booted, downloaded, and then installed the update.
After the update the phone rebooted, and gave me "failed to boot 2, starting RSD mode". At which point I installed pudding again using the tool. Rebooted after having installed pudding, the phone booted beautifully. I used OTA Rootkeeper to restore my root after the boot. Everything is working fine and it is on current version 4.5.141. I hope this helps someone else, or maybe someone to find a more simple, straight-forward way of doing this.

 

[ghost_og]

I know there have been varying posts on the subject, but I thought I would share my experience with the update. I originally started out on a bootloader unlocked, rooted, At&t branded Atrix. I had installed the 2.3.4/4.5.91 fruitcake previously and had been using it for some time. When the update came down I rolled back to stock recovery using fastboot and after the installation of the update, the phone gave me an failed to boot 4. I used rsd to flash the official 2.3.4/4.5.91. I received a failed to boot 1. (After going to launder my, now soiled, trousers) I noticed that when I plugged the phone in, RSD still recognized the phone, even though it did not show the "entering RSD mode" tag. It occured to me to attempt to flash pudding using the 4.2 auto unlock. Immediately after flashing pudding the phone booted up and everything was working fine.
At this point I rooted and installed clockwork on the phone using the same 4.2 tool. I then used Voodoo OTA Rootkeeper to back up my root. Unfortunately the tool installs clockwork in order to root the phone, so I had to flash back to stock recovery using fastboot. . I then booted, downloaded, and then installed the update.
After the update the phone rebooted, and gave me "failed to boot 2, starting RSD mode". At which point I installed pudding again using the tool. Rebooted after having installed pudding, the phone booted beautifully. I used OTA Rootkeeper to restore my root after the boot. Everything is working fine and it is on current version 4.5.141. I hope this helps someone else, or maybe someone to find a more simple, straight-forward way of doing this.

Thanks for the info. Do you mind if I re-post in this thread over in the dev forum? I noticed your post count is too low to post over there.

I just got my phone back from Motorola after they fixed a shattered screen. I had sent it in with an unlocked BL, running a CM7 kang. They sent it back running stock .141.

Since I didn't do the update, I had no idea how to proceed re-unlocking it. But it sounds like between you and Nottach, I should be ok with the pudding unlocker(knock on wood).

 

[ummkiper]

how did you get rid of superuser on fruitcake?

 

[Doogiedoo]

Thanks for the info. Do you mind if I re-post in this thread over in the dev forum? I noticed your post count is too low to post over there.

I just got my phone back from Motorola after they fixed a shattered screen. I had sent it in with an unlocked BL, running a CM7 kang. They sent it back running stock .141.

Since I didn't do the update, I had no idea how to proceed re-unlocking it. But it sounds like between you and Nottach, I should be ok with the pudding unlocker(knock on wood).

Not at all, if it's any use to anyone, feel free to repost it. Also, I had a hardware problem (screen banding) on my atrix and sent it back for repairs. When it was returned, it no longer showed unlocked. The bootloader was still unlocked, but I had to reapply the unlock sbf to get it to show again (before using another rom).

how did you get rid of superuser on fruitcake?

I still had it installed on fruitcake, but lost it (well, rather lost root access, as the app "superuser" is still there but not functional) when I installed the sbf file initially. I'm not sure if flashing pudding or using the automatic unlock on the fruitcake initially would have worked. I didn't think to try it initially.

 

[ummkiper]

Cool,thanks for the info.

Sent from my Nexus One using xda premium