Automatic bootloader UNLOCK/ROOT for AT&T 1.26/1.57/1.83/4.5.91 [UPDATE 07/31/11]

[sandeep1415]

No trouble at all...i have done it i am on .145..and it works perfectly fine.... thr can be a slight issue with cwm...but by just renaming two files you can avoid that.

Sent from my MB860 using xda app-developers app

 

[lonestarranger]

This method worked like a treat after I thought I was screwed with a hard-brick.

Hard Bricked.
SVF message: 105:1:2
Failed to Boot 0x1000

Thanks a lot sandeep1415 for the re-upload! This is the only script/tool that actually worked..

 

[mike4peace]

nothing happens

my problem is that failed to boot 0x1000. cmd says type 3 for my problem but i couldnt get to fastboot mode. anything helps a lot guys. when i plug usb cable without battery green led light lights up when i plug the battery after that, failed to boot nigtmare comes again and then phone closes

 

[crlowryjr]

This method worked like a treat after I thought I was screwed with a hard-brick.

Hard Bricked.
SVF message: 105:1:2
Failed to Boot 0x1000

Thanks a lot sandeep1415 for the re-upload! This is the only script/tool that actually worked..

Thanks a ton ... I pulled my old Atrix out the cupboard to use as a media player in the office, and got the No Operating System error following the Motorola and the Pudding instructions didn't help either. This got me back up and running in a blink.

---Rob

 

[jeremywh7]

cause of com.motorola.service.main Force Close

I did the same...but there is something wrong with recovery...no matter how many ways or how many times i flash android recovery is not entering into cwm... and ever since i rooted i am having com.motorola.service.main FC's.i guess this service deals with notifications sms/app notifications [...]

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

This post helped me finally figure out several months ago how to root/unlock/ROM my Atrix (thanks to XDA!) so I could do away with MotoBlur entirely...been on MROM ever since. My wife even finally had me root her phone, and do some mods, when she got fed up with her multi-daily reboots.

 

[andresrivas]

Nice finding! That's the spirit, searching and invesrigatibg led you to the cause and the solution of this problem
Cheers!

Hit the damn thanks button instead!
Enviado desde mi MB860

 

[mgmcgill]

Does this work for ATT Motorola Atrix 4G__GB 2.3.6__4.5.145?

I have tried the auto boot loader unlock tool and I didnt see my device listed when the CMD prompt brings up the second window. I may need to re-install motorola drivers. I will re-install drivers and try again then report back for the 4.5.145 people.

 

[palmbeach05]

does this work for att motorola atrix 4g__gb 2.3.6__4.5.145?

I have tried the auto boot loader unlock tool and i didnt see my device listed when the cmd prompt brings up the second window. I may need to re-install motorola drivers. I will re-install drivers and try again then report back for the 4.5.145 people.

read before asking questions! You are in the motorola atrix 4g section here on xda! You have a motorola atrix 4g running gb 2.3.6, revision 145. Noob or not, if you were able to type and post something here, you can also do this thing called reading or using that oh so scary search feature! Members are lectured on this daily!

 

[andresrivas]

Does this work for ATT Motorola Atrix 4G__GB 2.3.6__4.5.145?

I have tried the auto boot loader unlock tool and I didnt see my device listed when the CMD prompt brings up the second window. I may need to re-install motorola drivers. I will re-install drivers and try again then report back for the 4.5.145 people.

If your version isn't listed, then don't use automatic methods. Go fo the manual ones or do a deeper search

Enviado desde mi MB860 usando Tapatalk 2

 

[jeremywh7]

Does this work for ATT Motorola Atrix 4G__GB 2.3.6__4.5.145? [...]

Back when I researched this stuff almost a year ago, I ended up using these:
http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
http://forum.xda-developers.com/showthread.php?t=2276302
http://forum.xda-developers.com/showthread.php?t=1154600

That said, my phone had .141 when I rooted/unlocked it. My wife's phone had .145, and I rooted it fine, but didn't go beyond that (thought I expect to be attempting this soon, once I give her my now-ICSROM'd Atrix. From what I'd read though, the same procedure should (?) work for .145 too. I'll just post the notes I have from all this, in case this helps someone...

Unlocking Atrix 4G Bootloader 4.5.145, and flash 'romracer's ClockWorkMod (CWM) recovery image:
NOTE: the OEM ROM will not boot once the phone is unlocked, so be prepared to flash a new ROM!
1.  Extract 4547-fix-try2.sbf and fastboot files (to C:\unlock\ or whereever)
2.  Install RSDLite & open RSDLite.
3.  Power off your phone and back on (will reboot automatically if connected to USB). Hold volume down until you see "fastboot" at the top of the screen. Press the volume down until you see "RSD" then press volume up button. It'll say "Starting RSD Protocol"
4.  You'll see that RSDLite has detected your phone in the menu. ("SE Flash Olympus")
5.  Now Click the "..." button in RSDLite & navigate to the 4547-fix-try2.sbf file, then click Start.
6.  Wait until you phone restarts and you see a "Failed to boot 0x1000" error. (Just ignore it. Cause we're gonna flash a new ROM anyway).
7.  It will auto-start RSD mode and say "Starting Fastboot protocol support"
8.  Open Command Prompt with Admin Privilege and change directory (cd) to the extracted fastboot files.
9.  Run:
fastboot devices
To verify if your devices is recognized
10. Run:
fastboot oem unlock
To get the unique ID to unlock your phone.
(bootloader) Unlocking your device can permanently VOID your warranty.
(bootloader) This process cannot be reversed.  If you wish to proceed,
(bootloader) reissue the unlock OEM command containing the unique ID
(bootloader) of your device: {your unique device ID}
11. Finally, run:
fastboot oem unlock {the id given in the previous step}
12. Hopefully the phone says "Device is now unlocked." and the cmd window shows:
(bootloader) Device is now unlocked
OKAY
finished.

ClockWork Mod recovery:
==============================
Note: http://forum.xda-developers.com/showthread.php?t=1154600
If you already have a different version of CWM Recovery installed, and want to switch to RomRacer's, then first check to see if a file labeled "install-recovery.sh" @ /system/etc/. If the file is there, delete it, before proceeding with the install of RomRacer's version.
==============================
13. Erase the recovery:
fastboot erase recovery
14. Then flash romracer's CWM recovery:
fastboot flash recovery recovery.img

 

[latebloomer56]

I am hoping someone has the files needed to unlock bootloader on my Atrix MB860 2.3.4, as the links were outdated.

I know I am late for the party but please help me revitalise my old spare phone.

Thank you in advance! And Hi!!

 

[Dark9781]

Here you go

http://www.mediafire.com/download/10f83rrqura05rg/unlock_v4.2.zip

 

[akp277]

suceed to get fastboot mode after boot error and finally unlocked

Thanks for the nice script. I have been using atrix 4g since couple of years and yesterday I dare to unlock the boot loader for the first time.

I have atrix 4g, running 2.3.4/4.5.91 stock ROM with rooted done. As per the instruction I choose option #3 and as expected I got the boot error. Now as advised, I powered off and tried to get fastboot mode by pressing power button with volume down. The green LED comes for few seconds and the screen goes blank and nothing happened. I thought my phone became dead, I played a little bit with patience.

I powered on the phone (without holding volume key). Then it gives boot error with no OS and after displaying few instruction it goes to RSD mode automatically which is by default first instruction. Note that the second option was fastboot which I wanted to get. So I again rebooted and just after the boot error I pressed volume down which goes into fastboot mode and then I could easily follow the 6th steps of the original post and finally my phone was unlocked.

Hope this will help to beginners like me. Thanks again to mramirezusa for this nice automatic bootloader.

 

[umangsagar]

I am hoping someone......i!!

thanks for asking this

Here you go.....

thanks for the link


and thanks to the maker for such wonderful program

 

[baptenda]

Thanks for the link @Dark 9781

 

[juliaodobrasil]

Thanks for the new link.

 

[BruceAM]

MAIN.BAT ran but then...can't access google play

Help. Ran MAIN.BAT after unzipping. Did options #1 and #2. After step 9 said rm: can' remove '/system/etc/install-recovery.sh'":no such file or directory and repeated this with install_recovery instead of the dash. Everything continued fine.

When to Goggle Play (no MARKET) and found superuser but when click install, it just shows grey bar without progress. No download progress. Spoke to Google tech support and they had me do all their steps to figure it out without success.

Any ideas?

 

[palmbeach05]

Help. Ran MAIN.BAT after unzipping. Did options #1 and #2. After step 9 said rm: can' remove '/system/etc/install-recovery.sh'":no such file or directory and repeated this with install_recovery instead of the dash. Everything continued fine.

When to Goggle Play (no MARKET) and found superuser but when click install, it just shows grey bar without progress. No download progress. Spoke to Google tech support and they had me do all their steps to figure it out without success.

Any ideas?

If you open the script, you'll see that your entire first paragraph was not needed, but it is wise to point out that you installed a massively outdated recovery if you did use the provided recovery (more up to date recovery is available as well as bigpart recovery for cm11)

Google Play has replaced Market years ago. Don't go updating your superuser. Head over to chainfire's superuser thread (regular or beta version) and flash it via cwm while removing the superuser that was installed via the script that you used.

 

[BruceAM]

Still Hanging

If you open the script, you'll see that your entire first paragraph was not needed, but it is wise to point out that you installed a massively outdated recovery if you did use the provided recovery (more up to date recovery is available as well as bigpart recovery for cm11)

Google Play has replaced Market years ago. Don't go updating your superuser. Head over to chainfire's superuser thread (regular or beta version) and flash it via cwm while removing the superuser that was installed via the script that you used.

Thanks.
I went online and found that for Atrix 4 the latest was CM7. So I downloaded it. I push it to the sdcard.
When I installed the zip file from sdcard, it found the file and it executed in seconds (I thought it would take longer since file is huge)
When I then rebooted, all I get is red M, FROZEN.
I recovered from the frozen through restore.
I am back where I started with Android 2.2.2 and 4.1.83.

Thoughts?

 

[palmbeach05]

Thanks.
I went online and found that for Atrix 4 the latest was CM7. So I downloaded it. I push it to the sdcard.
When I installed the zip file from sdcard, it found the file and it executed in seconds (I thought it would take longer since file is huge)
When I then rebooted, all I get is red M, FROZEN.
I recovered from the frozen through restore.
I am back where I started with Android 2.2.2 and 4.1.83.

Thoughts?

The latest official ROM is CM7.2 like you found. The latest unofficial ROMs are here on xda (CM9/10/10.1/10.2/11/12 (preview)).

Did you wipe data/cache when you installed CM7?

Sent from my ATRIX HD using XDA Free mobile app