Rooting Gingerbread 2.3.6 (4.5.141) - The Complete Guide

[jeremywh7]

com.motorola.service.main Force Close

Yes...i have similar issue..i guess its because of com.motorola.service main force close...but in my case after i restart my phone...the notification bar stays until any notification comes...once there is a notification then the bar disappears ...it stays disappeared until a force close popup opens...then it appears back again...are you able to boot into CWM... ???

Just wanted to add for others that might be searching, the com.motorola.service.main Force Close issue is due to MotoBlur account issues (older accounts or something). For reference:
forums.motorola.com/posts/804cfff6d8

This issue is what finally drove me to figure out (thanks entirely to XDA) several months ago how to root/unlock/ROM my Atrix. My wife even finally had me root her phone, and do some mods, when she got fed up with her multi-daily reboots.

 

[Daige]

FANTASTIC - a rooting guide that actually WORKS!
(On a european Atrix, if anyone wonders)

Okay, so I'm just a liiittle late when it comes to getting the Atrix (go me, necring forum threads that are way too old to really matter? Well, it did matter to me, since it's the only working root guide around), but I'm really quite new to smartphones overall, so...at least I've finally found a phone I will probably enjoy immensely.

Anyways, the more I searched around the net, the more I realized that either the rooting guides I found were:

1. Incorrect.
2. Not for my operator/carrier.
3. Not for my part of the world.
4. Not for the Atrix.
5. Correct, for my operator/carrier, for my part of the world, for the Atrix...but still didn't work (I got error messages about this or that).
6. Missing important files (quite common, it seems).

So yeah...none of the guides actually worked for me. Finally I stumbled upon this thread and thought I'd give it a try and to amazement it actually worked...and now I'm as a happy as a whale! Or horse. Or something. Dog maybe.

However, I have some feedback:

1. I noticed that on paragraph 5, you used "/" instead of "\" when saying to write "cd c:/android"...and of course, that didn't work (so please update the guide on that point). Are there more instances where you should use \ instead of /? I guess not, since everything seemed to work for me.
2. On paragraph 16, I too got the message that su couldn't be updated.
3. On paragraph 17, I really don't understand where I'm supposed to find that terminal emulator and how to open it?
(EDIT: Read the whole thread and found out I was supposed to download a terminal emulator as a standalone app...not so obvious to new users)

I also would like to see a text saying something like "if you get an error on paragraph 16, or if you can't fulfill paragraph 17, just go to Android Market/Google Play and update the Superuser app" (if that's what we're supposed to do). As of now, I have the Superuser app but still don't really know if my mobile is rooted.
(EDIT: But now I have checked both in the terminal emulator and in su and both tells me that I have root, so...YAY!)

Google Play-links to Superuser and that Superuser Update Fixer would also be appreciated (not that I need them now, but I'm thinking it couldn't hurt to post them in that first post).

And then, after successful root, maybe some advice about what to do next, like installing recovery image (or so I've heard?) and go on with flashing and such stuff.

Heck, rooting and flashing is way too tricky, not really user-friendly at all...maybe that's the point? Scaring the living crap out of people?

But once again, THANKS for this WONDERFUL thread!!!

 

[stangfx]

hello,
I have a Motorola Atrix ATT
4.5.145.MB860.ATT.en.US
Android 2.3.6

I have a problem. Everything goes well until:
c: \ Android> cp / preinstall / su / system / bin /

He answered: c: Android: not found

Can you help me please?

(sorry for my English)
stan

 

[palmbeach05]

are those spaces there when you run the root procedures or did you just put them there in the post?

Sent from my MB886 using xda app-developers app

 

[andresrivas]

c: \ Android>

this is the error.

I think that such command (cp /preinstall/su /system/bin/) must be executed in a adb shell, not windows' cmd. Also, as @palmbeach05 mentioned, there shouldn't be any spaces, except the ones between "cp" and "/preinstall" and between "su" and "/system"

 

[Daige]

this is the error.

I think that such command (cp /preinstall/su /system/bin/) must be executed in a adb shell, not windows' cmd. Also, as @palmbeach05 mentioned, there shouldn't be any spaces, except the ones between "cp" and "/preinstall" and between "su" and "/system"

Well...yes and no.

You ARE using the windows cmd window but the whole procedure requires that you have installed the adb file before using the cmd window.

Also, use a space in the code when there is a space in the code, otherwise: don't.

I followed this guide exactly like it's printed, step by step. I only encountered errors on paragraph 5 (because one was supposed to use a backslash) and on paragraph 16 and 17 (but by then, the phone was already rooted).

So to stangfx and others who still experience problems, I cannot stress this enough:
Follow the guide exactly step by step. Do everything that is printed and do it exactly as it says. Don't to anything else. If you follow the guide everything SHOULD work (but I guess there can always be exceptions).

 

[ravilov]

Even worse than that...

"c:\Android>" means the shell prompt, not something you type in. Use some common sense, man! You mght have destroyed your su binary now because of improper shell redirection.

 

[Daige]

Even worse than that...

"c:\Android>" means the shell prompt, not something you type in. Use some common sense, man! You mght have destroyed your su binary now because of improper shell redirection.

Well, you do type in "c:\Android" at paragraph 5, but after that there's no need to type it in again, since you're already in the right part of the file system. However, since he got an error saying that there was no such thing as "c:\Android" there, I really can't see how he can have destroyed something there, since nothing really happened?

 

[Prince.Evo]

Nice trickk . Thanks boss


Sent from my GT-N7100 using Tapatalk

 

[gradd]

good thing i found this thread. i was digging the whole development section and those guides were rather confusing for an average joe, haha! i have unlocked, root and flashed cwm a year ago and i completely forgotten everything. so i needed to refresh my memory coz im dealing with a friend's atrix / untouched. :laugh:

 

[jhojo21]

MB861

Hi, I just ordered an atrix from amazon. Looking at the atrix, It says AT&T but on the description, it says MB861, I think it's the korean version. Will this method work for that atrix

 

[palmbeach05]

Hi, I just ordered an atrix from amazon. Looking at the atrix, It says AT&T but on the description, it says MB861, I think it's the korean version. Will this method work for that atrix

yes

 

[CyberpunkShadow]

Thank you

Just bought my third Atrix. Previous ones had hardware failures.I unlocked their bootloaders about a year ago, but for the new one, this thread served as a helpful reminder. :good:
Still can't believe how ahead of its time this phone was, by the way!

 

[xistose]

You are the Guy

Luv u man :victory:

Moderator Edit: Do not quote the whole OP

 

[clovehitch]

Excellent!!

I had some issues with updating SU, but everything else went fine on 2.3.6 4.5.145. Would fail checking version. Uninstalling and installing the updated version of su then updating through google play store took care of it.
Time to look at unlocking the bootloader and a custom rom. Thanks again, wish I had the time to try this years ago.

 

[ryanriot]

I have the Motorola Droid X2 with GingerBread 2.3.6 I believe

Fastboot.exe is not being recognized as a command

 

[andresrivas]

Check that you are positioned on the durectory where is fastboot, or that you have that dir on your path

Enviado desde mi MB860 usando Tapatalk 2

 

[DTravis]

Hi ,

I used this method to root my Atrix, now I would unlock the bootloader to try CM7 ROM.
Unfortunately I was not successful with method described here:

briefmobile.com/how-to-unlock-the-atrix-4g-bootloader

my output is :
...
(bootloader) OEM unlock is not implemented
OKAY [ 0.001s]
finished. total time: 0.001s

I should mentioned, I tried to install new ROM using ROM Manager 5.5.3.7, not successfully. Showing current Recovery: ClockworkMod 5.0.2.0. When trying to enter CWM setup it says "Failed to boot 2 / Starting RSD mode". I'm not able to backup via this app, neither by boot menu (Entering Android Recovery mode = "Failed to boot 2").

Is the method using RSDlite + *.sbf file safe ? (not to brick my phone)
If so, what *.sbf file I should use?

My system says following :

System version
45.0.27.MB860.NonEFIGSRetail.en.EU

BaseBand version
N_01.100.00R

Webtop version
WT-1.2.0-133_22

Kernel version
2.6.32.9
[email protected]#2

Build number
4.5.2A-74_OLE-27

Am I screwed? Any step by step instruction would be more than welcome.

Thanks a lot!
Travis

 

[ravilov]

Whoa dude, your post is a big mess.

First of all, you're asking here about a guide that is not here. With the huge amount of guides available on this forum, why would anyone know (or care) about random guides found at other random sites?

Second of all, do you know the difference between rooting and BL unlocking, and what is the purpose of each? If not you should look it up, and then re-read what you just said and compare it to what you linked.

Third of all, you're starting off by trying to install a ROM? Talk about jumping ahead.

Suggestion: do a LOT more reading before attempting ANYTHING. By the looks of it, you're definitely not ready to mess around with any phone.
Also, once you DO get to a stage where you know what you're doing, forget about ROM toolbox or any similar GUI-ish tool and use command line tools as that is the only reliable method to get anywhere.

 

[DTravis]

Ravilov, do you really think I would post here if any of the procedures/tutorials posted over the internet to unlock bootloader worked?
Off course I know the difference between rooting and unlocking bootloader ! Sorry to say, but your reply was not helpful at all.

The reason I posted my message here is because I used this procedure (from the first post, should mention in previous message) to root my phone and now mentioned procedure for unlocking bootloader doesn't work.

The major problem of all procedures written over the internet is that are multi copies of the original one and it is very difficult to find the source, to find out what each step does exactly for example!
To confirm my saying... The guy on the video about unlocking and rooting Atrix here doesn't really look like he knows what he is doing! So it is really mess to find the correct sources/people who really know what they are doing.

So to rephrase my question.
"When I rooted my phone using procedure in the first post, what would be the way of unlocking bootloader, please?"