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

[Rred]

Figured it out! Didn't have the USB drivers installed, so the RSD lite window didn't do anything when it popped up and quit out.

So you successfully rooted a 4G using which method??

And the problem was only that you didn't have the, what, USB drivers for the phone installed on your computer? Or, what USB drivers exactly where?

 

[Kershek]

So you successfully rooted a 4G using which method??

And the problem was only that you didn't have the, what, USB drivers for the phone installed on your computer? Or, what USB drivers exactly where?

I used the automatic method, step 1 (bootloader), then step 2 (root).

My issue was that I didn't load the USB drivers here: http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers

 

[tritn]

link die

 

[dennis789]

What is the normal amount of available RAM after a fresh reboot?

 

[palmbeach05]

What is the normal amount of available RAM after a fresh reboot?

Correction: what's the normal amount of available RAM after a normal reboot? Answer that, and you have your answer.

Sent from my MB860 using xda app-developers app

 

[hernanchoh]

It is possible to you to upload the file again? i have a motorola atrix 4g from att and i try to unlocked it with the unlocked code that att provided me but for some reason the code didn´t work and some body else make a process to try to unlocked the phone but i don´t know what they did but i think the phone its know hardbrick.

If i turn on the phone it shows on the screen:

svf: 105: 1: 2
failed to boot 0x1000
no OS detected, going to RSD mode in 5 seconds

Press a key to stop count down
Availibles modes here:

1. rsd
2. fastboot
3 nvflash
4 bp hw bypass rsd
5 bp hw bypass qc dload
6 bp hw bypass bp only
8 bp sw bypass rsd
9 android recovery
10 boot android
11 device uid
12 console=t tySO, 115200n8
13 early USB enumeration
14 bp tools

vol up to select, vol down next choice
current choice is mode: rsd
staring fastboot protocol support
battery is too low to flash


if i pwr with vol up shows:

svf: 105: 1: 2
failed to boot 0x1000
pwrReason: Charger
staring fastboot protocol support
battery is too low to flash

Can i fix it? or its completely dead?

Thanks for you help.

 

[Zeljko1234]

Here you can find files for unlocking but it's look like that yours is hard bricked

https://dl.dropboxusercontent.com/u/23255832/Atrix Unlock/AUTOMATIC_UNLOCK_V4.2.zip

 

[Rred]

If the wrong unlock code is entered six (?) times, the phone hard locks and according to Moto and AT&T, that's "forever". Supposedly this changes something in the phone and no one, not even Motorola, can re-program the phone to unlock the carrier subsidy lock after it has been hard locked.

So if you had someone screwing around with your phone and the code AT&T gave you does not work, that's probably the answer. I had the same problem with an at&t refurbished phone, apparently the previous owner blew the hard lock and that locked it forever.

You can still use a locked phone with AT&T MVNO's like Red Pocket, H2O, or Simple (Simply?) Wireless but not with T-Mobile. Which is not a total loss since only AT&T MVNOs will be able to get full data service on an AT&T phone anyhow.

 

[atmosphere1991]

could you help me

is there any solution to help the hard brick? thanks and waiting for your answer

 

[hardcpp]

Hi, i'm a little confused i tryed many time to unlock my motorola atrix 4G on android 2.3.6 with ORANGE FR carriere but every time i got BOOT ERROR 1 and i can't go in fastboot mode, when i try to reboot my phone on recovery the phone crash and restart normarly

my operator is orange FR
the only way i found to get my device work normaly is the moto updater utility to recover my phone but i cant unlock it :/

Sorry for my english, i hope someone have the solution

 

[ukmed]

Error

So Ive got to RSD lite loading, and under the status box it says:

" Failed flashing process. Failed flashing process. Phone [0000]: Phone did not re-enumerate after RAM-downloader was sent. (0x703E); phone connected"

The phone screen is showing the red M and at the top it states "sec_exception: febe, 35, 35"

Ive tried pulling the battery and continuing but it fails to connect to the device, I get to the fast boot part and the DOS type box just states "waiting for device"

Im new to all this so simple idiot language would be appreciated, thanks for your help in advance.

 

[abbots]

unlocking/rooting att 141 success

fwiw, in case this is of use to anyone:

I just got brand new Atrix, came with Android A2.3.6 and AT&T 141 builds, locked boot loader, new phone

using this thread, it rooted with no real issues (enable USB debug 1st... (I forgot till...))

http://forum.xda-developers.com/showthread.php?t=1769497

using this thread, it unlocked boot loader (I think it's more or less duplicate of similar XDA thread, the sbf file seems identical)

http://saifhassan.info/a-noobs-guide-to-unlock-motorola-att-atrix-bootloader-4-5-141-flash-roms.html

How to Unlock Motorola Atrix Bootloader (4.5.141) AT&T

BUT if you brick your phone.....

 

[suhridkhan]

Appreciate it.

:good: Worked perfectly on my AT&T Atrix 4g 4.5.145 with GB 2.3.6

 

[sandeep1415]

Hi....i used this unlock tool..and unlocked and rooted successfully. But CMW doesnt flash properly..after. flashing cwm..uts stays for the first restart and from restart its entering into stock recovery...i also tried flashing using cmd fastboot..it doesnt work either..CMW is not staying permanently..has any one faced similar issue..why its happening and how to flash cmw permanently...

Sent from my MB860 using xda app-developers app

 

[sandeep1415]

I did the same...but there is some thing wrong with recovery...no mater 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
Update: there is a file in system/etc/install-recovery.sh & etc/install-recovery.sh which need to be deleted or renamed (http://forum.xda-developers.com/showthread.php?t=1302423&page=13) so i renamed those two files..and flashed cwm again and it seemed to be working..tried three times..
Sent from my MB860 using xda app-developers app

 

[Zeljko1234]

Try to manually flash recovery. Guide and links are here.

 

[sandeep1415]

Thank you zelijko...But itried flashing in that way too..

Try to manually flash recovery. Guide and links are here.

I already flashed orange version using the same method...But again after flashing android recovery booted into stock recovery...not into CWM...But i found the solution now..which i updated in my earlier post... Thank you...:good:

 

[Dadbeh]

the link in the original post is broken

 

[sandeep1415]

New link

the link in the original post is broken

I have uploaded the same file here

 

[comp72]

Just to make sure...

I've done stuff like this before but I have a fear of commitment and I was just wanting to know that if any body has had trouble with version 4.1.145, and if I brick my device, are there any stock ROMs that will allow me to restore my device in the unlikely event that I will.

Just wondering.