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

[mramirezusa]

If you run options 1 completed (unlock) and actually you have the "unlocked tag" at boot everytime (left top corner)

And if you run option 2 completed (root/cwm)

The answer is Yes, but double check if ROM dev are using tenfar cwm or rom manager cwm to make sure you don't run with any problem after

Much appreciated, downloading this one at present, and will try it once I get my grubby paws on it.

In the event this doesn't do the trick, would I be able to install KP's Alien ROM via CWM as an alternative?

Sent from my MB860 using XDA App

 

[Belgarius]

They need to add a X1000 option to the thanks button...

Installed perfectly, once I got past my usual RTFD problems, as in Read The Freaking Documentation.

Only problem that arose is that installing Superuser proved a bit problematic, installed fine, but stopped working on each launch, requiring an FC, but I'll worry about that little problem later.

As an aside, I was unable to install Alien, for whatever obscure reason, CWM was unable to actually find the zip file to install it, and yes, that was with the new version as specified. Tried everything my fried braincells could think of, but apparently, it was not able to read the contents of my external SD, kept showing the internal, no matter how I set it up. Another thing to worry about, should the need arise. I am eternally grateful for your invaluable assistance with all this noobfulness on my part.

 

[wintermute000]

Hey mate what version CWM are we getting with this?

Reason I ask is: I thought it is tenfar (it is right? as we can wipe cache?). Well I installed Redpill ROM and in the instructions they say to put the zip on your external SD card.

In CWM I cannot find any option to locate the zip file on your external card, and I can't find any option to mount it either. When I select what zip to flash it only seems to want to show me my internal SD card. Have I missed something? Also the screenshots look different to in the tenfar thread (the text is in orange for example). Its coming up as v4.1.04 for me

 

[mramirezusa]

Right now V4.1 has ROM manager but it seems some option are broken so I will return to tenfar ones a placed an additional option menu for Official ROM manager, hopefully they will fix it

Hey mate what version CWM are we getting with this?

Reason I ask is: I thought it is tenfar (it is right? as we can wipe cache?). Well I installed Redpill ROM and in the instructions they say to put the zip on your external SD card.

In CWM I cannot find any option to locate the zip file on your external card, and I can't find any option to mount it either. When I select what zip to flash it only seems to want to show me my internal SD card. Have I missed something? Also the screenshots look different to in the tenfar thread (the text is in orange for example). Its coming up as v4.1.04 for me

Sent from my MB860 using XDA App

 

[wintermute000]

OH so we are getting the same one as ROM manager? I don't even have ROM manager installed LOL. Thanks for clearing that up I thought I was on tenfar.

FWIW in recovery my text is orange and version is 4.1.04 is that right and I can use it with ROM manager?
Also I didn't delete install.sh in /system/etc yet I don't seem to be afflicted by the issue where stock keeps overwriting.
(a bit confused by this recovery business)

Once again Great work and many thanks

 

[Belgarius]

I've noticed the same here, might well explain why I was unable to locate the zipfile on my external SD. Showing the same version number and color text as well. Strangely enough, I *thought* I had installed the new version of CWM, so that bears a bit further scrutiny on my part...

 

[mramirezusa]

I JUST UPLOAD A NEW VERSION V4.2 with TENFAR's CWM as DEFAULT in OPTION 2 and I ADDED OPTION 6 OPTIONAL ROM MANAGER

I've noticed the same here, might well explain why I was unable to locate the zipfile on my external SD. Showing the same version number and color text as well. Strangely enough, I *thought* I had installed the new version of CWM, so that bears a bit further scrutiny on my part...

 

[mramirezusa]

I just upload V4.2 now with option 2 default tenfar's CWM

 

[mramirezusa]

OH so we are getting the same one as ROM manager? I don't even have ROM manager installed LOL. Thanks for clearing that up I thought I was on tenfar.

FWIW in recovery my text is orange and version is 4.1.04 is that right and I can use it with ROM manager?
Also I didn't delete install.sh in /system/etc yet I don't seem to be afflicted by the issue where stock keeps overwriting.
(a bit confused by this recovery business)

Once again Great work and many thanks

Orange Letters is ROM Manager, you can flash the recovery partition but not necesary you need the APK in android, but is 100% recommend so you can manage the ROM inside of android OS... I just upload V4.2 that will install Tenfar's by default in option 2, so if you want to swap to Tenfar just re run the script option 2.

About install.sh my script is taking care of this part so dont worry if you already run once is already taking care

And I added option 6 for optional ROM Manager CWM hopefully they will fix it some day soon

 

[mramirezusa]

They need to add a X1000 option to the thanks button...

Installed perfectly, once I got past my usual RTFD problems, as in Read The Freaking Documentation.

Only problem that arose is that installing Superuser proved a bit problematic, installed fine, but stopped working on each launch, requiring an FC, but I'll worry about that little problem later.

As an aside, I was unable to install Alien, for whatever obscure reason, CWM was unable to actually find the zip file to install it, and yes, that was with the new version as specified. Tried everything my fried braincells could think of, but apparently, it was not able to read the contents of my external SD, kept showing the internal, no matter how I set it up. Another thing to worry about, should the need arise. I am eternally grateful for your invaluable assistance with all this noobfulness on my part.

If you want download the new V4.2 script and re run option 2 so it can install Tenfar's CWM, I think that's the reason people are having problems, I just checked Alien ROM forum and it said need to be with Tenfar's one because it seem ROM Manager has some broken parts! so Just re run option 2 V4.2 and follow procedure...

 

[sanriver12]

can i use this to just root an OTA 4.5.91?

 

[mramirezusa]

can i use this to just root an OTA 4.5.91?

It only work for "UNLOCKED" BOOTLOADER USERS

but I can suggest if you are lock bootloader user use preinstall method by eval



Sent from my MB860 using XDA App

 

[Belgarius]

I'll give that a try here as soon as I get it downloaded. I am not sure of my method of attempting to install the new tenfar CWM version, being honest, though. I am running under Win 7 64 bit, and installed the version of moto-fastboot that is supposed to work with it, but have encountered a few issues with installing the latest CWM.

Using the command line moto-fastboot reboot does just that, no problems, which leads me to think that the version of fastboot I have installed is in fact the right one, however... issuing the command line that I presume would actually install the .img file plops me back to a screen outlining the proper syntax for the task required.

I am using this:

moto-fastboot recovery recovery-en-goapk-0630-1029.img

(this is the name of the file downloaded and extracted that is supposed to install the new CWM)

And pretty much assuming that this is in fact, a PEBKAC problem here... as in Problem Exists Between Keyboard And Chair...

Again, thanks thousands for your time as well as your assistance. Thanks to you, at least I have a functional device once more, instead of a nifty ornament on my desk.

 

[mramirezusa]

I'll give that a try here as soon as I get it downloaded. I am not sure of my method of attempting to install the new tenfar CWM version, being honest, though. I am running under Win 7 64 bit, and installed the version of moto-fastboot that is supposed to work with it, but have encountered a few issues with installing the latest CWM.

Using the command line moto-fastboot reboot does just that, no problems, which leads me to think that the version of fastboot I have installed is in fact the right one, however... issuing the command line that I presume would actually install the .img file plops me back to a screen outlining the proper syntax for the task required.

I am using this:

moto-fastboot recovery recovery-en-goapk-0630-1029.img

(this is the name of the file downloaded and extracted that is supposed to install the new CWM)

And pretty much assuming that this is in fact, a PEBKAC problem here... as in Problem Exists Between Keyboard And Chair...

Again, thanks thousands for your time as well as your assistance. Thanks to you, at least I have a functional device once more, instead of a nifty ornament on my desk.

Just rename it to something shorter for example recovery.img and issue the command as follow:

moto-fastboot flash recovery recovery.img

And the just:

moto-fastboot reboot

And done!



Sent from my MB860 using XDA App

 

[IIxShockwavexII]

It scared the **** out of me, but it worked. I unlocked from 4.5.91.

 

[jmbradd]

wow that scared the crap out of me (and i've soft bricked my captivate a few times...) Trying to unlock my wifes OTA'd atrix with this script and it did the "failed to boot, no os" deal which the directions clearly state is a possibility if not probability but I didn't see there was a 5 second timer so it went into RSD mode and then I got the dreaded error message that shows up when you hard brick. Add to that that the volume down + power did not bring up the fastboot menu like expected. Dunno how but somehow it managed to get into fastboot and I was able to continue unlocking. Got tenefars CWM on there and going to flash a rom soon. Wish it were as easy as the captivate but i've had a year with that phone and not enough time with this one.

Great script, very detailed instructions and excellent support from the dev in this thread!

 

[wintermute000]

yeah exactly same thing happened to me. I had to pull the battery (very reluctantly) to snap it out of RSD and get back into fastboot. Very very nerve wracking

 

[mramirezusa]

The softbrick "failed to boot /no os" IS NORMAL for first timer unlocking on 2.3.4/4.5.91 as it state in the script

That's way I stated in the script "Do not panic" just select fastboot and continue with the script

wow that scared the crap out of me (and i've soft bricked my captivate a few times...) Trying to unlock my wifes OTA'd atrix with this script and it did the "failed to boot, no os" deal which the directions clearly state is a possibility if not probability but I didn't see there was a 5 second timer so it went into RSD mode and then I got the dreaded error message that shows up when you hard brick. Add to that that the volume down + power did not bring up the fastboot menu like expected. Dunno how but somehow it managed to get into fastboot and I was able to continue unlocking. Got tenefars CWM on there and going to flash a rom soon. Wish it were as easy as the captivate but i've had a year with that phone and not enough time with this one.

Great script, very detailed instructions and excellent support from the dev in this thread!

Sent from my MB860 using XDA App

 

[crlowryjr]

It only work for "UNLOCKED" BOOTLOADER USERS

but I can suggest if you are lock bootloader user use preinstall method by eval



Sent from my MB860 using XDA App

Can definitely +1 this ...
Last night I rooted my official AT&T OTA 2.3.4 with eval's preinstall instructions.
There's something a bit goofy when rooting though ... I got an error when /preinstall/dosu - something about group file or command missing. When I did a /preinstall/su and followed the rest of the instructions everything went fine.

Have to admit ... I'm friggin terrified to do the unlock, and will have to wait until something like CM 7 is available before I'm willing to take the jump.

---Rob

 

[Maroon Mushroom]

awesome work.

if RSD skips over your phone too quickly, try entering into RSD manually using fastboot just so your computer can pick up the appropriate drivers. Then back out and rerun the script like normal. Took me a few tries but I got it!