[Guide][CDMA R800x] FXP CM7 to CM9 upgrade. (As of FXP 125)

[Guide][CDMA R800x] FXP CM7 to CM9 upgrade. (As of FXP 125) - Xperia Play General

Hi everybody! I'm Dr...
Nah nm. Anyways well the past 2 days I have been working on switching from FXP CM7 to CM9. Needless to say, the process was abit confusing and did run across some snags along the way. So now that I figured it out with some help. I am returning the favor to the community and putting up this guide. (Also this guide is for users who already have an unlocked bootloader and so. So if you are a new R800x user who JUST unlocked their bootloader using testpoint or so, you too can use this guide)
Keep in mind this guide is based on the changes and tweaks from FXP 125!
So for those who are using a R800x CDMA Xperia play, this is for you.
-= The Prep =-
1: You will need the Flashtool to flash the latest ftf from Verizon. agraceful was nice enough to put it on his cloud storage here. http://www.mediafire.com/?yas7dola6dgd8 (You may wanna disable your AV for this as Kaspersky for me, didnt like the file since it uses exploits to do the stuff to your phone) if the cloud storage is down, this is the thread for the flashtool. http://forum.xda-developers.com/showthread.php?t=1351299
2: The latest Verizon ftf file here. http://forum.xda-developers.com/showthread.php?t=1696233
3: The latest FXP CM9 (remember its zeusc that you are downloading for!) AND the gapps for ICS! (Very important you use the right gapps here), http://forum.xda-developers.com/showthread.php?t=1447542
*OPTIONAL* 4: Mjolnir Kernel (boot.img) - http://forum.xda-developers.com/showthread.php?t=1708459 (Rename that img file to boot.img) (This is a diff kernel which may have some different features and abilities compared to fxp 125, so take a look and choose, atm it has zRam support (compcache) )
*OPTIONAL* 5: Cdma Carrier Name Fix - https://dl.dropbox.com/u/21955004/Carrier Fix.zip (This can either let you use a custom carrier name or least fix it from saying T-Cdma 64)
6: Of course, fastboot, drivers, and drivers for the flashtool which come with flashtool for flash drivers. (Not covered in this guide, cause if you already have CM7 on CDMA.. I am assuming you already have an unlocked bootloader, drivers etc already installed)
Now once you have everything. Time to do some EXTRA note prep work:
1: Make note of your MDN/MSID numbers. (The phone number and 2nd set of number incase you need to manually program your phone if OTA programming doesnt work)
2: Titanium Backup of your apps/data
3: Put the CM9 zip, cdma mega fix, and gapps ics into the memory card root folder. You will need this here to flash in a bit.
4: Kiss your phone bye bye and tell it you love it and that it will be back online soon if you dont mess it up!
Now you are ready to get started!
-= The Upgrade Install Process! =-
1: Turn your phone off, hold the back button and plug in the usb, You should be in the flash mode. Load up flashtool. (Your PC will install the drivers now if it needs to or the flashtool will error and tell you where the drivers are located to install and run its exe file to install)
2: With drivers ready, phone ready, you can drag the verizon ftf file to the main screen of flashtool. It should start up, give you some notes, tell you what you need to do if needed and just start flashing. Wait till its done fully, then you can close out of it, reboot your phone, if it boots up to Verizon screen setup, you have done the job correctly! Grats!
3: Unplug USB, Turn off phone, hold the search button, then plug in the usb again. You will see a blue light on the power button to tell you that you are fastboot mode.
4: Make sure the boot.img (Either the boot.img from FXP 125 zip file or the downloaded one) is in the same folder as your fastboot command! From cmd prompt, be in the directory of your fastboot and type fastboot -i 0xfce flash boot boot.img this should be a quick process and will put the new kernel you need with its cwm recovery built in needed for CM9. After thats done, type fastboot -i 0xfce reboot
5: During the reboot phase, LOOK at the power button. The MOMENT you see it light up "blue" hold the back button. This will load you into CWM where you can get started!
6: Now you SHOULD have your files on your SD card ready to be flashed! If you dont and you forgot. Just go to "mount" and mount the usb storage and then put your files on the sd card. (Silly person forgetting! Remember, its the cm9 zip, cdma fix, and the gapps ics)
7: Now flash the fxp 125 cm9 zip. Will take a min or 2. Once that is done. Do the 4x wipe. Wipe/Factory reset, Wipe Cache, Then goto Advanced, Wipe Devlik, Wipe Battery Stats.
8: Now flash gapps ics
9: (Optional) Flash the Cdma Carrier name fix.
10: Reboot into your phone.
If you see the cool transwarp sliders style android logo. Go WOOT!
-= The Inital Setup =-
Now that you are staring at the new android setup wizard here are my "personal" tips
1: From the setup wizard. I just did the basic, and SKIPPED the sign in part. Get your wifi running once inside if you want. Then load up "Play Market" and sign into google from there.
Why did I do this? Well.. I did it the other way 1st time signed in during the setup process.. and well.. I left the option "Restore phone from google" enabled.. yea.. not smart, next I know its installing EVERY app I had from Google. (Which I guess it was basing it on the google history or using my G1s installed stuff to restore from) By doing it the way above, it doesnt try to start restoring everything. Which is good.
2: Now to program your phone number and so again. Now I did this using pageplus, which is still verizon. For me, the OTA to get my number back in was *228 send. Wait wait wait, and it should program and be done with. Alt numbers are *22890 and *22891 which some update the roaming towers or just an alt form of OTA. Now if none of that works, then do the manual programming.
3: In the market, get titanium backup (and your pro key) and install.
4: The rest you should be able to do yourself as far as restoring goes using titanium backup.
Congrats you are now running ICS CM9 FXP!
Hope this guide helps people who maybe confused and would like a lil thread with something to look over to help them get it going. =)

Reserved..For..Stuff..

-=Tweaks=-
V6 Supercharger - http://forum.xda-developers.com/showthread.php?t=991276 (This is being used to help increase performance of CM9 on our xperia as well as some games that started sluggishing up after the change to ICS)
Volume+ - https://play.google.com/store/apps/details?id=com.TEST.android.lvh&hl=en Well worth the money.. otherwise my emulators sounded too quiet lol. Not to mention Youtube. Now at work, I use Speaker setting 8.

Hey,
You can make the update, as of FXP125 you don't need a separate kernel to get CWM. It's baked in again. Volume keys get you into it.

Mogul345 said:
Hey,
You can make the update, as of FXP125 you don't need a separate kernel to get CWM. It's baked in again. Volume keys get you into it.
Click to expand...
Click to collapse
Done. I left it optional for now. =) Also the only thing I need to confirm on is if we need that cdma mega fix file still... I forgot my XP at home.. (Go figure) so I wont be able to test the update out till tm. Heh.

Mysticales said:
Done. I left it optional for now. =) Also the only thing I need to confirm on is if we need that cdma mega fix file still... I forgot my XP at home.. (Go figure) so I wont be able to test the update out till tm. Heh.
Click to expand...
Click to collapse
I did not have to flash the megafix. All I did was the following (w/ FXP125):
1)Use flashtool to flash new baseband from 2.3.4 FTF (when selecting what to flash, I excluded everything but baseband).
2)Use fastboot to flash the FXP125 kernel.
3)Booted into CWM, wiped data/cache/dalvik cache/battery stats, then flashed FXP125 and the 4/29 Gapps.
Only thing I think needs flashed is the carrier name fix. My phone says T-CDMA 64 again.

Ok thanks. Yea, according to lightningdude the only things in the cdma mega fix was just the gamepad fix (dont know what that is yet) and the cdma carrier name. Gonna try to see about those. While its minor, still good info to have.
Also its being said that we should use V6 Supercharger on the CM9 to improve some games again for XP users.

Ok thanks to lightningdude, I put the cdma carrier name fix in the guide. =)

Mysticales said:
Ok thanks. Yea, according to lightningdude the only things in the cdma mega fix was just the gamepad fix (dont know what that is yet) and the cdma carrier name. Gonna try to see about those. While its minor, still good info to have.
Click to expand...
Click to collapse
Ahh OK. That gamepad fix is the patch to the .idc file changing the button map so circle isn't back in some games.
Sounds like the megafix is just all the preferred patches that were applied to paxChristos' CDMA builds.

Yea, just made life easier. Also I excluded the gamepad fix as thats a personal pref.. cause BUTTON_B vs BACK_ALT mapping can break some apps which devs code for one or the other. Normally everyone is using BACK_ALT. Then emulators which can remap it all anyways works fine with it.
Edit: Ok just updated to 125 myself without the CDMA carrier name thing. My Pageplus comes up as Verizon Wireless, so not sure if the patch was needed, but still its in guide as optional, case you want a custom name or you do get that t-cdma 64 issue.

Mogul345 said:
Hey,
You can make the update, as of FXP125 you don't need a separate kernel to get CWM. It's baked in again. Volume keys get you into it.
Click to expand...
Click to collapse
are you saying that steps 3-5 of the install process is not required since its baked in? Sorry, just getting into the more advanced rooting/customization with the r800x. I'm going to unlock the bootloader (put this off for way to long but with the latest "No ICS from Sony/Verizon" i'm just going to move ahead with my own upgrades, then ftf the verizon 2.3.4, and then hopefully be getting ICS.

blkwhk said:
are you saying that steps 3-5 of the install process is not required since its baked in? Sorry, just getting into the more advanced rooting/customization with the r800x. I'm going to unlock the bootloader (put this off for way to long but with the latest "No ICS from Sony/Verizon" i'm just going to move ahead with my own upgrades, then ftf the verizon 2.3.4, and then hopefully be getting ICS.
Click to expand...
Click to collapse
Looks like the original instructions have been updated. You should follow the instructions as directed in the OP. Steps 3-5 currently are where you flash the boot.img (kernel) you wish to use. It's either FXP's (which would be extracted from the ROM .zip), or Moljnir's or the other one listed. All three have working Clockworkmod recoveries now. At the time these instructions were originally written the recovery in FXP's kernel was busted, the next FXP build fixed it, and that's when I wrote the post you're referring to.

Related

[Updated 2-11-2012] THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs

So you’re a N00B with a brand new Android device, and you have no idea what all this sbf, adb, bootloader talk is all about; you just want to know how to do cool stuff with your new phone and be as cool as all of us Senior Members
Well here’s a Atrix N00B Guide just for you that will hopefully be a good jumping off point for you to start exploring and getting into the world of themeing, ROMing, flashing, etc. Most of this stuff was pulled from various XDA forums, and is easy enough to find, if you just take the time to search for it, but being the nice N00B friend that I am, I thought I’d try and compile most of it one place. So here goes…
*If you can’t figure something out or need help with whatever your particular problem may be, before you go cluttering up the forums with your problem and you get blasted by Senior Members like me use the SEARCH bar at the top of each section and/or thread. I promise you, you are not the first person to have your problem, and more times than not, your problem has been answered more than once. People HATE seeing questions that were just answered one or two pages previously. SO USE THE FREAKING SEARCH BUTTON!!!
*NOTE: Most of the following links are going to be for U.S. AT&T based phones only. Sorry, but that’s what I have and that’s what I know. Most of you BELL & other international guys should find some of this useful though, and most of the links below also have a international build version now.
CLICK HERE FOR UPDATES
Lets start with some basic terminology & general understanding:
What is Root / Rooting?
Put simply, Rooting your device allows you, and/or rooted apps, to access parts of the Linux based Android software that is your OS, and that you would otherwise not be able to access. These tasks can be as simple and beneficial as backing up your system setting, or as complicated as installing custom ROMs, Kernels, etc. (more on this later).
What is a Motorola .SBF file?
SBF stands for Single Binary File, and contains a firmware image that can be installed on your device. i.e. they are more of less what you are installing on your device when you do a OTA (over the air) update; except an actual .sbf file that you download and flash on your own will most of the time not only contain the updated info. in the OTA, but also all the other “stock” info. that came with the device. That’s why when you flash a .sbf file it will return you to a stock/retail device.
What is ADB?
ADB = Android Debug Bridge. So what this basically is, is a command/terminal based interface you can run from your PC, to interact with your device and its file structure. You can PUSH (install) programs, apps, .apk files, etc. to your device, move things around, set permissions, etc. One of the primary things to remember when trying to use adb, is that you need to enable debugging on your device. In fact it’s a good idea to enable this, and leave it that way… forever! This setting can be found on your device under Settings -> Applications -> Development -> USB debugging
Here is a list of helpful adb commands:
http://android-dls.com/wiki/index.php?title=ADB
What is a ROM?
A rom is like a custom firmware image that is made by a Developer either entirely from scratch, or based off of the official firmware package. Some ROMs contain simple changes like changing icons and adding extra options to things, other more complicated ROMs can change the entire Android experience. Which one you will want to flash, will be entirely up to you. Read carefully, and make sure you understand what you are getting into before you flash.
What is a Kernel?
As a rule of thumb, if you have to ask, you probably shouldn’t be messing with this anyway. But hey, best for you to at least know what it is. A kernel is the heart of the device's OS. In simplest terms it’s a connection between your apps and your device’s hardware; i.e. the processor, RAM, etc. A custom kernel can dramatically change the way your device’s hardware performs… for the better and/or the worse.
What is a Bootloader?
The bootloader is a program code that is executed before the device OS starts up, and that instructs that device to boot “normally”. The bootloader can come locked or unlocked from the manufacture. A unlocked bootloader will allow you to install custom ROMs & Kernels (as well as some other neat things) on your device.
What is a odexed and de-odexed framework, and what is the difference between the two?
Just read this:
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
What is CWM Recovery (ClockWorkMod Recovery)?
CWM is a custom recovery program that allows you to backup / restore a full or partial system backup of your device. It also allows you to install flashable .zip files; which is one of the primary installation methods for custom ROMs. It also provides other neat features such as cache wiping, battery reset, and other processes. Long story short, if you are thinking about flashing custom ROMs or just want a really good backup program, incase you FUBAR your device, you need to install this.
What is Fastboot?
Again, just read these for description & helpful Commands:
http://forum.xda-developers.com/showthread.php?t=619153 [Thanks briggie108]
or
http://android-dls.com/wiki/index.php?title=Fastboot
What is all this CM7 stuff about?
CM7 stands for CyanogenMod v7. It's a very popular ROM, b/c of its built-in options, great enchantments and total removal of manufacture software; i.e. all that MotoBlur stuff on your device is gone. It is a stripped down fast and well designed ROM with a custom kernel, that allows for easy flashing of great custom themes (just check out the General Theme Section for Android on XDA). Only a small selection of Android devices have a "official" release of CM7, however almost all Android devices have a "un-official" port for it. The Atrix 4G port is currently in its pre-beta stage and is being worked on by the Atrix Dev-Team.
More info. on CM7 can be found here:
http://www.cyanogenmod.com/
And here:
http://en.wikipedia.org/wiki/CyanogenMod
The #1 rule of CyanogenMod is that you do not ask for timetables!!! You have been warned. If you choose to ignore my warning, ask away and prepare to be blasted until you cry.
Information on the current status of the Atrix 4G port of CM7, as well as a list of current bugs, can be found here:
https://code.google.com/p/atrix-dev-team/
CM7.1 Beta for the Atrix is Available Now!!!
Information, install instructions, etc. can be found here:
http://forum.xda-developers.com/showthread.php?t=1257574
CM7 Nightlies Now Available for the Atrix (a.k.a. Olympus)
*Note: Nightly builds may be unstable, and are unsuppoted by the Dev Team.
http://download.cyanogenmod.com/?device=olympus
Nightly change log can be found here:
http://cm-nightlies.appspot.com/?device=olympus
The current version of CM7 for the Atrix does not yet support the following:
- Webtop
- Fingerprint Scanner
- Pocket Detector
- Horizontal HDMI Mirroring
MY CYANOGENMOD INSTALLATION GUIDE:
http://forum.xda-developers.com/showpost.php?p=19986512&post=234
Theme Chooser Themes for CM7 (200+):
http://forum.xda-developers.com/showthread.php?t=1167075
*Please make sure to search the thread before you post an already answered question. Also, if you have the $ available, please consider a $donation$ to the Atrix Dev Team for their continued hard work (remember, this is still beta, they're still working hard at it).
ATRIX (4.5.91 FIRMWARE) HOW TOs:
Here are some How To Guides that may be helpful to new Atrix 4G owners that have just got thier phone & have the most recent firmware = 4.5.91 (Android 2.3.4). Read each How TO carefully and completely before attempting. If you are unsure of what to do, or how to do it, ask a question first. I will try a put this is a order that somewhat makes sense.
HOW TO FLASH A SBF:
WARNING: If you are on Android 2.3.4 (4.5.91) w/ a unlocked bootloader, do NOT flash back to a earlier sbf version. DOING SO WITH BRICK YOUR DEVICE!!! Use CWM Fruitcake described below instead.
SBF Hints, Tricks & Guidelines:
- Always make sure to flash with a full battery! The last thing you want to do is run out of juice in the middle of a sbf flash; that's a great way to brick your device.
- As a general rule of thumb before flashing a sbf file to your device, you should always download the sbf file to a file path on your computer with the least possible spaces (i.e. the shorter the file path to the sbf file the better). So just download it to the root drive of your computer, such as C:\.
- Also, because these sbf files are so long, this sometimes causes problems with RSD Lite (the program you use to flash the sbf to your device). So, I would suggest you change the file name to something short, like OLYFR.sbf. It doesn’t so much matter what you name the sbf file, just so long as it’s short, does not contain any spaces in the name and you do not change the .sbf file extension. This will help prevent errors when trying to flash (no, I don’t know why, it just does).
- If you are running Windows on your PC, open RSD Lite as a Administrator. Also, when you open RSD Lite, Instead of browsing for the sbf file via the normal “…” button in the program, just drag the sbf file onto the file path bar in RSD Lite. Sometimes, the sbf file will not load when you select it via the browser button in RSD Lite (again I have no idea why).
- Once your sbf file begins to flash to your device, be patient… the device will re-boot at least a couple times in the flash process. Do not get jumpy and disconnect your device until RSD Lite says you are 100% done! Doing so can cause your device to BRICK! If for some reason you have waited for an inordinate amount of time, and it does not say finished, then ask for help on the thread, before unplugging. The same goes for pulling the battery. DO NOT DO THAT!!! Pulling your battery during a sbf flash, is one sure fire way to brick your device. Only pull the battery as a last resort and only after you have asked for help.
- RSD Lite has been updated to v5.3.1, here is the download link:
http://www.mediafire.com/?zz81vf1o2y73d4n
or
http://www.datafilehost.com/download-33dce367.html
STEPS:
1) Have the correct Motorola drivers installed for your PC (i.e. x32-bit or x64-bit).
2) Download RSD Lite (Links above) & install on your PC.
3) Choose a sbf file to download and flash from Motorola Atrix Firmware Super Thread: http://forum.xda-developers.com/showthread.php?t=1125944
If you are currently running firmware 4.5.91, I suggest that you only flash back to this firmware version. Flashing back to a eariler sbf/firmware version may have unintended consequences, the most serious of which is bricking your device.
*Note: U.S. AT&T users should only flash AT&T sbfs, internationl users should only flash their particular sbf versions.
4) Read the above sbf hints, trick, etc. to help prevent RSD Lite problems/errors.
5) Open RSD Lite and load the sbf file that you downloaded.
6) Put your device in RSD Protocol Mode by powering OFF, and upon powering back ON, hold both the power button and the volume UP button. Device should now say "Entering RSD Protocol Mode."
7) Connect your device to your computer via the usb cable, and select your device by clicking/highlighting it in RSD Lite.
8) Select START in RSD Lite and let the sbf flash process fully complete before disconnecting the device from the PC. There will be several reboots and the process make take 5 - 10 minutes to complete a FULL sbf flash.
9) If you have any errors or problems as a question, prefably in the Q&A section.
*Note: After unlocking your bootloader and installing a CWM (*see below), you have the option to flash stock sbf files named "Fruitcakes" that do not require RSD Lite to flash (see information below).
HOW TO UNLOCK YOUR BOOTLOADER FOR ANDROID 2.3.4 (FIRMWARE 4.5.91):
WARNING: If you are on Android 2.3.4 (4.5.91) w/ a unlocked bootloader, do NOT flash back to a earlier sbf version. DOING SO WITH BRICK YOUR DEVICE!!!
Try the automated scrpit in this thread: http://forum.xda-developers.com/showthread.php?t=1182871
or
Try the original unlock method in the Main Pudding Thread: http://forum.xda-developers.com/showthread.php?t=1136261
*Use the instructions on this page for this method: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader]
Directions are in the respective OP
HOW TO ROOT YOUR DEVICE ON ANDROID 2.3.4:
One Click Root For Motorola Phones Running Android 2.3.4:
http://forum.xda-developers.com/showthread.php?t=1255548
Alternative Root Methods:
Follow the instructions in this post:
forum.xda-developers.com/showpost.php?p=15872818
or
These Instructions:
http://briefmobile.com/motorola-atrix-4g-root
*Note: Many of the ROMs you may wish to install, after your boot loader is unlocked, will also include a ROOT package. Check the indiviual ROM OP to make sure though.
HOW TO INSTALL CWM RECOVERY ON 2.3.4:
CWM Options:
With 2.3.4, you now have 2 different options available for CWM Recovery. You should have a unlocked bootloader, be rooted and be on Android 2.3.4 (firmware version 4.5.91), before attempting to flash any of these. Each is described below.
Option 1: RomRacer's CWM
http://forum.xda-developers.com/showthread.php?t=1204500
- This CWM is extremely stable & has multiple features, such as the ability to choose whether to backup the webtop portion of your device, or not. It supports both ext-sd (micro sd card) and internal sd (internal storage). You can also choose from a variety of colors & supports both U.S AT&T and International users. This CWM will also be the official CWM of CM7 ported by the Atrix Dev Team.
- I personally prefer this CWM as it also works with ROM Manager (app from the market - *see details below).
*Note: If you do not have any CWM Recovery installed yet, you can use the fastboot commands in the OP (use the non .zip version to install via fastboot), or you can install via ROM Manager with the below instructions.
*Note: 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.
Install Instructions to Use RomRacer's CWM w/ ROM Manager APP:
1) Download the ".zip" file of your color choice (make sure you choose the right version AT&T or international), and place the .zip file on the sd-card (internal storage).
2) Download ROM Manager from the Market (paid or free, it doesn't matter) and install app.
https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en
3) Open ROM Manager and select "Flash ClockworkMod Recovery," making sure to select the right device (i.e. Atrix 4G). This will flash the current version of CWM to your device, which will also work (see details/limitations discussed below).
4) Now, choose "Install ROM from SD Card", and choose the .zip file that you saved on your internal storage. You should not need to delete any of the cache options. ROM Manager will reboot the device into CWM and flash the .zip automatically, and then reboot again.
5) You should now have RomRacer's custom CWM installed over the ROM Manager version. You can now select Reboot into Recovery from ROM Manager, and it should boot into CWM Recovery.
Option 2: ROM Manager's Stock CWM
https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en
- For install instructions, see steps 1-3 under the RomRacer's CWM.
- Allows for easy CWM updating, as well as ROM updates that are posted by the developer on ROM Manager's servers.
- Current build much better, and allows for both internal & external sd installs/backups.
HOW TO INSTALL FRUITCAKES ON 2.3.4 (GREAT SBF/RSD ALTERNATIVE!!!):
If you have a unlocked boot loader and CWM Recovery installed, and you wish to go back to "stock" you now have a wonderful alternative called Fruitcake. The fruitcake files are essentially stock sbf files that bypass the need to use RSD Lite; they flash via CWM just like any other .zip file that you flash. This is very welcome as it eliminates the need for RSD Lite and the problems associated with it.
You can find your Fruitcake here: http://forum.xda-developers.com/showthread.php?t=1163009
WHAT DO I DO IF MY DEVICE WILL NOT FULLY BOOT??? (i.e. Boot Loop or Soft Brick):
- If you have a bootloop/softbirck after atempting to unlock your bootloader:
a) If you flashed the unlock .sbf, are you sure you booted into fastboot and issued the "fastboot oem unlock" command.
b) If you happen to have a 2.3.4 ROM saved on you device, or a Fruitcake.zip, try booting into Android Recovery and reflashing. Make sure to wipe dalvik cache, cache partition, and format data first though.
c) If you can boot into fastboot, you can fastboot flash the "stock" 2.3.4 Gingerbread .img/system files by following the instructions on this page:
http://forum.xda-developers.com/showthread.php?t=1163342
*Note: The .img files to install via fastboot are located under "Download Gingerbread Stock Images" on the download page.
- If you have bootloop/softbrick after attempting to flash a ROM or Kernel:
a) Did you download the correct version of the ROM or Kernel for your device (i.e. US AT&T vs International).
b) If you're installing a new kernel, did you flash back to the stock kernel first, before trying to flash the different kernel.
c) Are you sure you wiped the dalvik cache, cache partition & formated the data (i.e. The Big Three) before installing the ROM. For a kernel install, just wipe dalvik cache & chace partition.
*Note: If you are using the stock ROM Manager CWM version, then you need to fastboot wipe for fomating data, as this feature does not yet work on ROM Manager. Fastboot command: "fastboot -w".
d) Try re-flashing ROM, after making sure you did the above 3 correctly... still not working, you can hopefully still:
1) Flash a Fruitcake in CWM to give you a clean install. Make sure to wipe "the big 3" first.
2) Can't get into Android Recovery/CWM, try flashing the stock Gingerbread .img files via fastboot. Instructions here:
http://forum.xda-developers.com/showthread.php?t=1163342
The 2.3.4 (4.5.91 Firmware) Section:
Updated ROMs, Kernels, etc. for 2.3.4 (firmware 4.5.91) --- UPDATED 8/14/2011
So with the official release of Gingerbread 2.3.4, a host of new ROMs & Kernels have been released for the Atrix, along with various fixes and mods for those ROMs & Kernels. I'll try and cover the most common ones below, as always if you feel something needs to be added, just let me know.
*Note: Before flashing any of these make sure that you:
1) Have a unlocked boot loader:
http://forum.xda-developers.com/showthread.php?t=1136261
2) Have CWM installed
3) Understand Fastboot/moto-fastboot commands
ROMs & Kernels:
FYI:
Before installing any ROM or Kernel I suggest you do the following to help prevent error, boot-loops, etc. Also, it's a good idea to flash a new ROM or Kernel on a fully charged device:
1) Download which ever ROM or Kernel you plan on flashing and have the .zip on your device ready to flash.
2) Backup your apps (not system data), contacts, etc. Also consider making a CWM backup of your device, just in case.
3) Boot into CWM Recovery
4) Wipe Dalvik Cache (under advanced in CWM)
5) Wipe Cache Partition
6) Wipe data/factory reset
6a) If you're using ROM Manager/CWM you will need to reboot the device after step 5, and upon reboot enter fastboot mode and enter the command: "fastboot -w" or "moto-fastboot -w" if you prefer using moto-fastboot. Then type "fastboot reboot" and upon reboot make sure to enter Android Recovery again, so that you can flash the ROM/Kernel.
7) Install .zip from SD Card (choose the .zip you wish to install)
8) If you installing a radio, theme, kernel, etc. on top of a ROM, I would suggest redoing the whole wipe process again between flashes.
9) Reboot the Device
- If you get a boot loop, try entering Android recovery and re-wiping the chace and data, and perhaps try reflashing the ROM/Kernel. Or if you made a CWM backup, you can always restore that.
ROMS
Stock Gingerbread 2.3.4 (Thanks KennethPenn):
*Note: This is useful if you need to return to stock Gingerbread. Both CWM & Fastboot install available.
http://forum.xda-developers.com/showthread.php?t=1163342
Home Base ROM (by Seanzscreams):
http://forum.xda-developers.com/showthread.php?t=1242721
This is a "stock" Android base ROM, with multiple versions ranging from almost stock with only a few tweaks, to a stock feel with multiple mods, extras, etc.
ASOP Atrix ROM (by Stinebd):
http://forum.xda-developers.com/showthread.php?t=1306550
ASOP = Android Open Source Project - - in other words, it's supposed to make your device as close to a stock Google Android device as possible (i.e. like a Nexus device).
*Note: since this rom is essentially a stock Android experience, many of the Atrix's stock features will not work; like the fingerprint scanner, webtop, etc.
Alien ROM & Theme (by KennethPenn):
*Note: The ROM is separate from the theme, which can be applied afterwards if you wish.
http://forum.xda-developers.com/showthread.php?t=1186537
This is a very stable ROM, however there are a few issues with the Theme portion. The Kernel is stock 2.3.4.
Ninja ROM (by SamCripp):
http://forum.xda-developers.com/showthread.php?t=1173843
Super fast ROM, with Faux123's Kernel included.
Cherry Pie & Pie Crust (by Navalynt):
http://forum.xda-developers.com/showthread.php?t=1189497
Includes optional themes and has a separate international build version.
Aura ROM (by Diviance):
http://forum.xda-developers.com/showthread.php?t=1186990
Includes Faux's Kernel
3 versions to choose from (de-bloat, de-bloat w/ accounts, & w/ all bloat)
DarkSide ROM (by Nottach):
http://forum.xda-developers.com/showthread.php?t=1222108
Includes Faux's Kernel
Multiple Mods available to add to ROM
Theme incorporates many apps
HoneyComb ROM/Theme (by Seanzscreams):
http://forum.xda-developers.com/showthread.php?t=1206767
Based off of Alien ROM w/ a Honey Comb Theme. Different versions are available for different kernel choices.
iBlur ROM (by Marko!):
http://forum.xda-developers.com/showthread.php?t=1305015
Like the look of the iPhone... but hate the iPhone. Give this ROM a try then.
StarWars Rom/Theme (by Seanzscreams):
http://forum.xda-developers.com/showthread.php?t=1200214
Ying / Yang ROM (by Shady_lanem):
http://forum.xda-developers.com/showthread.php?t=1244852
Nice black/white ROM, with all the latest tweaks, mods, etc.
KERNELS
Faux's Kernel (over-clocked @ 1.45 GHz):
http://forum.xda-developers.com/showthread.php?t=1156040
*Note:
- Froyo version, Gingerbread version & CM7 version, each w/ multiple versions avaliable; a enchanced stock kernel @ 1 GHz that allows undervolting, profiles, etc. Also a OC kernel @ 1.3 GHz & 1.45 GHz.
- Make sure you pick the right kernel; i.e. if you are on CM7, use a CM7 kernel, if you are using a Gingerbread based ROM, use the Gingerbread kerenl.
- The overclocked 1.45 GHz kernel may cause heat issues with your battery, thus causing random reboots... suggest undervolting.
Kholk's EternityProject Kernel (over-clocked @ 1.5 GHz):
http://forum.xda-developers.com/showthread.php?t=1153003
*Note:
- Current build based off of Faux's kernel.
- Kernel may cause heat issues with your battery, thus causing random reboots... suggest undervolting.
Clemsyn's Kernel (over-clocked @ 1.4 GHz):
http://forum.xda-developers.com/showthread.php?t=1354502
*Note:
- Based off of Faux's Kernel, but includes additonal optimizations.
- AT&T and CM7 versions available @ either 1.0 GHz or 1.4 GHz.
- B/C of memory timings, this kernel may not work on your device (like mine), and you will not be able to fully boot. Make sure you have a backup kernel to flash incase this happens to you.
OTHER MODS & FIXES:
V6 SuperCharger Script
My Instructions Here: http://forum.xda-developers.com/showpost.php?p=18906120&post=201
Battery Jumping Fix:
*Note: Charge battery to 100% (overnight) & wipe battery stats in CWM (under advanced) before flashing this.
http://forum.xda-developers.com/showthread.php?t=1174349
WEBTOP on 2.3.4:
http://forum.xda-developers.com/showthread.php?t=1169457
Native Tethering MOD for 2.3.4 (included in the above ROMs):
http://forum.xda-developers.com/showthread.php?t=1160452
All Atrix 4G AT&T Radios:
http://www.multiupload.com/G8T8IGZF05
2.3.4 Ported Boot Animations:
http://forum.xda-developers.com/showthread.php?t=1162936
OTHER HELPFUL THREADS:
How To Recover From A Soft Brick:
http://forum.xda-developers.com/showthread.php?t=966405
The Same Thing As This Thread (Posted in the Dev Section), Without All The Fluff:
http://forum.xda-developers.com/showthread.php?t=972423
Theming the Atrix 4G: tools, processes, locations, etc.:
http://forum.xda-developers.com/showthread.php?t=1060199
How To Port A Theme:
http://forum.xda-developers.com/showthread.php?t=1186819
How To Theme Gingerblur / Compiling & De-compiling a Framework (This is what got me started):
XDA Thread Here: http://forum.xda-developers.com/showthread.php?t=1101138&highlight=gingerblur
How To Here: http://briefmobile.com/how-to-theme-gingerblur
List of ROOT APPS available & working on the Atrix:
http://forum.xda-developers.com/showthread.php?t=1099846
A Whole Bunch of Icon Sets (for when you're ready to start customizing):
http://forum.xda-developers.com/showthread.php?t=824656
Widget Locker Themes:
http://forum.xda-developers.com/showthread.php?t=968613&highlight=D3S-L002
How to Manually Deodex Any Atrix ROM:
http://forum.xda-developers.com/showthread.php?t=1162764
Invaluable Resource:
http://gitbrew.org/android/

Terrific Info!
Great job as usual Swiftks!! It's always nice having everything in one place. Sometimes searching XDA can be frustrating with the amount of search results. This should help everyone, not just the noobs.

Good work.. Only way to be useful is its stickied so it isn't lost
Sent from my MB860 using XDA Premium App

Great post/thread, someone should sticky this... Maybe it will help reducing all the generic questions...

Might want to add asking for cm7/miui
Sent from my MB860 using XDA Premium App

Nice thread, just what i needed, i am new to the Atrix and i need all the help i can get. Cheers Dude

What a great thread. I am well versed in rooting and flashing my nexus one, even did some minor development for it. But this is a very useful summary for the atrix, and not everything is the same between devices. For example I had no idea what an sbf file was.

I'm glad this is helping some of you. I thought of a few more details I can add to the OP when I get home today... also, I'll see about trying to get stickyfied.
Sent from my MB860 using XDA Premium App

Swiftks said:
What is Root / Rooting?
Put simply, Rooting your device allows you, and/or rooted apps, to access parts of the Linux based Android software that is your OS, and that you would otherwise not be able to access. These tasks can be as simple and beneficial as backing up your system setting, or as complicated as installing custom ROMs, Kernels, etc. (more on this later).
Click to expand...
Click to collapse
You have made a great post that will help a lot of new people out. For rooting it would be helpful to add that all rooting does is give you the equivalent of the Administrator account, like in Windows.
For your fastboot/bootloader section. I always point new people to this:
http://forum.xda-developers.com/showthread.php?t=619153
Your link is pretty good. I like the one I posted as well. It is a little advanced, but it also has some added fluff for newbies.
Also some advice while flashing in general. Never ever do a battery pull unless you are absolutely 100% sure something went wrong and the phone is frozen. Some mods take a while to install, or the progress bar might not be coded in correctly. I have made some personal mods where the progress bar screwed up. After a couple minutes of freaking out, all of a sudden cwm goes "Ding, done!" so yeah patience is key.

I second that it should be stickied....

Very well written guide. Wish this guidewould have been here when I started flashing. Will be very helpful to the newbies coming to the atrix/xda. Good job.
Sent from my MB860 using XDA Premium App

Woow i feel like dev after reading this lol ^__^
thanks!!

GreAt thread! Question, was my post the one you are talk in about for the non-market apps enabled? I posted that just recently and worked like a charm. I was surprised that it did. It is ironic how an app from app store enables non market apps..lmfao. Great work on thread.

demandarin said:
GreAt thread! Question, was my post the one you are talk in about for the non-market apps enabled? I posted that just recently and worked like a charm. I was surprised that it did. It is ironic how an app from app store enables non market apps..lmfao. Great work on thread.
Click to expand...
Click to collapse
Yeah, I think it might have been.
Am Updating the OP now with some more info.
Sent a request to Mr. Clown for a Stick, and he said they he would do it... so hopefully this thread won't get lost for future noobs.

One thing though is instead of calling it the "noobs" guide? Why not just call it beginners guide cause the new people coming here are probably not gonna have any idea wth a noob is anyway! Great guide besides that though!

Gutterball said:
One thing though is instead of calling it the "noobs" guide? Why not just call it beginners guide cause the new people coming here are probably not gonna have any idea wth a noob is anyway! Great guide besides that though!
Click to expand...
Click to collapse
Makes Sense...

I was a total noob when I picked up my Atrix back in Feb. Proceeded to mess around with things and soft-bricked it. Took me a few days to seach for all of this information and finally get it back to stock. Thanks for putting it all in one spot!!

this just just great work dude.

Can you include a brief explanation about what CWM is?
Edit: Oops... I saw that you've already done this.

yay its stickied...good job man

[Q] First Post!...with a ton of help needed.

HellllOOooOoOo!!
Ok, here goes. First off, I searched. A lot. There is so much conflicting information and opinions out there. I hate to annoy you pros with noob-ness but I have to. Sorry!
Here is the quick version:
Friend gave me an Atrix 4G. He is big on experimenting, rooting, custom ROMs and all that. I am not. At all. I want to use it on t-mobile. I DO get a signal and can text. MMS doesn't work and motoblur wont let me set up an account. This results in no access to email other then Gmail. Basically, I want to bring the phone back to its original (or close as possible) state. Hopefully, that will solve some of my issues.
-Android Version
2.3.4
-Unlocked
-Rooted
-Build Number
olympus_hktw-userdebug 2.3.4 4.5.2A-5_OLH-3110614 test-keys
-Clockwork recovery mod installed (if that matters)
I am not THAT tech savvy but can follow instructions well. I've already been messing around but cant seem to get RSD Lite to actually flash properly. I dont care for customs ROMS, hacking and tinkering. I just want this phone to work as well as possible.
Can anyone give me some personal assistance? Please? Step by step would be great. I'll be refreshing this page often in hopes of responses.

Vul said:
HellllOOooOoOo!!
Ok, here goes. First off, I searched. A lot. There is so much conflicting information and opinions out there. I hate to annoy you pros with noob-ness but I have to. Sorry!
Here is the quick version:
Friend gave me an Atrix 4G. He is big on experimenting, rooting, custom ROMs and all that. I am not. At all. I want to use it on t-mobile. I DO get a signal and can text. MMS doesn't work and motoblur wont let me set up an account. This results in no access to email other then Gmail. Basically, I want to bring the phone back to its original (or close as possible) state. Hopefully, that will solve some of my issues.
-Android Version
2.3.4
-Unlocked
-Rooted
-Build Number
olympus_hktw-userdebug 2.3.4 4.5.2A-5_OLH-3110614 test-keys
-Clockwork recovery mod installed (if that matters)
I am not THAT tech savvy but can follow instructions well. I've already been messing around but cant seem to get RSD Lite to actually flash properly. I dont care for customs ROMS, hacking and tinkering. I just want this phone to work as well as possible.
Can anyone give me some personal assistance? Please? Step by step would be great. I'll be refreshing this page often in hopes of responses.
Click to expand...
Click to collapse
It sounds like you need to set up a proper T-Mobile APN. (you have a T-Mobile SIM card currently installed?)
If you can get on Wifi, try to go the the Play store and download Tweakker or other APN utilities that enter the APN for your based on your carrier.

co.ag.2005 said:
It sounds like you need to set up a proper T-Mobile APN. (you have a T-Mobile SIM card currently installed?)
Click to expand...
Click to collapse
Yes. I have a t-mobile SIM card installed. My concern is what the previous owner may have done and whatever ROM is loaded on this phone. Can I somehow bring it back to stock or get a super stable, close to stock as possible ROM first and then start addressing the quirks I have?

Is this an AT&T branded phone? I'm not sure if getting back to stock is necessary, and if you do get back to stock, you might be SIM locked to AT&T (I could be wrong however). If you want to flash a fresh, stock ROM but still be rooted, SIM unlocked, etc., find a 2.3.6 Fruitcake in this forum or try NottachTrix 4G ROM.
however, I'd wait till others weighed in before doing anything. Honestly, I'd try getting your APN (download Tweakker app and walk through the steps) going now and if that solves your issue, your ROM might be working fine for you... my $0.02
oh, and welcome to XDA!

Vul said:
Yes. I have a t-mobile SIM card installed. My concern is what the previous owner may have done and whatever ROM is loaded on this phone. Can I somehow bring it back to stock or get a super stable, close to stock as possible ROM first and then start addressing the quirks I have?
Click to expand...
Click to collapse
1. Download the fruitcake .zip you want (webtop also, if you want it)
2. Do a full wipe with fastboot (search if you're unsure how to)
3. Boot into recovery and flash the .zip you downloaded from step 1
4. Reboot and you're done
This will put you back to stock. I can't remember if fruitcakes are pre-rooted, but if not you can easily root again.

Alright, now we're getting somewhere.
co.ag
The phone itself says "unlocked" upon startup. I got the network unlock code direct from AT&T because at first the phone wouldn't even recognize my t-mo SIM. Phone is now network unlocked.
Ghost
gonna search now for fruitcake and see what thats all about. Do I need webtop?
Then going to get fastboot. Guess I dont need RSD Lite anymore?
Im doing this because I dont know what the previous owner has done and would like a clean slate. Kind of like changing the oil on a used car you buy, even if the PO says it was done.

Ok so,
I found fastboot with recovery tool and the .exe files within the ZIP dont do anything.
The fruitcake ZIP file I downloaded according to your link, I'm not sure what to do with that. lol
Help?
**am I supposed to be saving these files to the phone itself? If so, where? Internal storage? SD card?

Vul said:
Alright, now we're getting somewhere.
co.ag
The phone itself says "unlocked" upon startup. I got the network unlock code direct from AT&T because at first the phone wouldn't even recognize my t-mo SIM. Phone is now network unlocked.
Ghost
gonna search now for fruitcake and see what thats all about. Do I need webtop?
Then going to get fastboot. Guess I dont need RSD Lite anymore?
Im doing this because I dont know what the previous owner has done and would like a clean slate. Kind of like changing the oil on a used car you buy, even if the PO says it was done.
Click to expand...
Click to collapse
that "unlocked" bit on start up means your bootloader is unlocked, doesn't have anything to do with the SIM card. All this means is that you can flash a ROM since the phone is "unlocked"
Vul said:
Ok so,
I found fastboot with recovery tool and the .exe files within the ZIP dont do anything.
The fruitcake ZIP file I downloaded according to your link, I'm not sure what to do with that. lol
Help?
**am I supposed to be saving these files to the phone itself? If so, where? Internal storage? SD card?
Click to expand...
Click to collapse
the fruitcake .zip goes on your internal sdcard. BUT, before you start doing anything, please go through the stickied threads in this section and read up on how to flash ROMs to your phone. This will include how to wipe your phone using the fastboot commands and how to flash the fruitcake .zip.
start here, read this post
http://forum.xda-developers.com/showthread.php?t=1154600
then follow guides to
"HOW TO INSTALL FRUITCAKES ON 2.3.4 (GREAT SBF/RSD ALTERNATIVE!!!)"
and
"ROMs & Kernels:
FYI:
Before installing any ROM or Kernel I suggest you do the following to help prevent error, boot-loops, etc. Also, it's a good idea to flash a new ROM or Kernel on a fully charged device:
1) Download which ever ROM or Kernel you plan on flashing and have the .zip on your device ready to flash.
2) Backup your apps (not system data), contacts, etc. Also consider making a CWM backup of your device, just in case.
3) Boot into CWM Recovery
4) Wipe Dalvik Cache (under advanced in CWM)
5) Wipe Cache Partition
6) Wipe data/factory reset
6a) If you're using ROM Manager/CWM you will need to reboot the device after step 5, and upon reboot enter fastboot mode and enter the command: "fastboot -w" or "moto-fastboot -w" if you prefer using moto-fastboot. Then type "fastboot reboot" and upon reboot make sure to enter Android Recovery again, so that you can flash the ROM/Kernel.
7) Install .zip from SD Card (choose the .zip you wish to install)
8) If you installing a radio, theme, kernel, etc. on top of a ROM, I would suggest redoing the whole wipe process again between flashes.
9) Reboot the Device
- If you get a boot loop, try entering Android recovery and re-wiping the chace and data, and perhaps try reflashing the ROM/Kernel. Or if you made a CWM backup, you can always restore that."

Vul said:
Ok so,
I found fastboot with recovery tool and the .exe files within the ZIP dont do anything.
The fruitcake ZIP file I downloaded according to your link, I'm not sure what to do with that. lol
Help?
Click to expand...
Click to collapse
Ok, sorry I wasn't that detailed in my other post and assumed you were on your phone (my bad). First things first, read the N00b guide.
1. Anytime you download CWM .zips, put them on the root of your phone's sdcard. You'll need them there in order access them from recovery. ( note: sdcard=internal sd card & sdcard-ext=external sd card for blur ROMS )
2. Fastboot commands are executed from the command line. Open a command prompt and navigate to the directory containing fastboot.exe in order to use it. The Noob guide should have links to all the fastboot commands you'll need.
3. With the Atrix's unlocked BL, holding Volume Down when turning the phone on will bring up a series of bootmodes to choose from. This is how you get into fastboot, recovery, RSD, etc. Navigate through the choices with Volume Down. Select one by pressing Volume Up. You should only ever really need Fastboot and Android Recovery.
4. CWM is used to flash .zips (ROMS, kernels, apps) while in recovery mode. Use romracer's to make things easier on yourself later.
Read through the N00b guide and this will all make perfect sense.

I have no idea what Im doing. I think because this phone has been tampered with so much already, it's making it extra tough to work with.
I managed to install CM7. Its the only ZIP file that actually seemed to take. I still dont understand fastboot , in the sense that I don;t know when Im supposed to see a command prompt. Also, now, CM7 is asking me to upgrade to premium and I have to pay for it. There doesnt seem to be a free way of installing it so that I can sync all my info through my google account. Ugh. Im not cut out for this but Ive been screwing with this literally since 730 this morning.
**CM7 with google apps packet installed. So far, so good. Im happy with this considering its pretty close to stock gingerbread, kinda like my G2. Now, Im hopefully done messing around. Would be nice if they release a solution for the fingerprint scanner or if I can get my gmail to auto sync but at least I can stop obsessing for the time being. Great help guys, thanks so much!!!!

Iconia A500 SOD fix (at least for me)

I've been dealing with SOD (Sleep Of Death) problem since official OTA ICS update. On HC everything (except calendar) was fine, but after official ICS update I was having SOD almost every sleep longer then few minutes.
Tried WiFi/sync tricks etc.
What helped ? Well..
1. hardware reset (Vol+ / Pwr / RotateLock)
2. factory reset (from Settings Menu)
3. full update via sd card (Vol- / Pwr)
OFFICIAL ROM: 7.014.16 - 041.213.01 - COM_GEN1 (ICS)
(Acer_A500_7.014.16_041.213.01_COM_GEN1_1336732099520_45282ff4.zip)
and once again:
4. hardware reset (Vol+ / Pwr / RotateLock)
5. factory reset (from Settings Menu)
...I know that hardware & facory reset are pretty much the same, but...It helped...

mayekk said:
I've been dealing with SOD (Sleep Of Death) problem since official OTA ICS update. On HC everything (except calendar) was fine, but after official ICS update I was having SOD almost every sleep longer then few minutes.
Tried WiFi/sync tricks etc.
What helped ? Well..
1. hardware reset (Vol+ / Pwr / RotateLock)
2. factory reset (from Settings Menu)
3. full update via sd card (Vol- / Pwr)
OFFICIAL ROM: 7.014.16 - 041.213.01 - COM_GEN1 (ICS)
(Acer_A500_7.014.16_041.213.01_COM_GEN1_1336732099520_45282ff4.zip)
and once again:
4. hardware reset (Vol+ / Pwr / RotateLock)
5. factory reset (from Settings Menu)
...I know that hardware & facory reset are pretty much the same, but...It helped...
Click to expand...
Click to collapse
Does t means I have to re-install all applications?

cscs3 said:
Does t means I have to re-install all applications?
Click to expand...
Click to collapse
yes, but you can use titanium backup or similar app to do it for you...

I have a A501 and want to get rid of this sod problem. so i took the last "Ice Cream Sandwich 4.0.3 (LEAK)" Rom from http://forum.xda-developers.com/showthread.php?t=1816560 and tried to install the update.zip file from the sd card. When i get to the recovery it starts but crashes after a few seconds. Do i habe to install a different recovery or unlock my bootloader? I'm a little bit confused...can somebody give me a short hint? Thx.

captainn said:
I have a A501 and want to get rid of this sod problem. so i took the last "Ice Cream Sandwich 4.0.3 (LEAK)" Rom from http://forum.xda-developers.com/showthread.php?t=1816560 and tried to install the update.zip file from the sd card. When i get to the recovery it starts but crashes after a few seconds. Do i habe to install a different recovery or unlock my bootloader? I'm a little bit confused...can somebody give me a short hint? Thx.
Click to expand...
Click to collapse
This is probably because of a couple of reasons.
1. You didn't do the incremental update. The available update files are incremental patch files, which means you have to have the others installed before you install the latest. Or at least part 1 and 2 of the original leak.
2. You didn't decrypt the file and remove the "update.zip". Generally, you can't just rename these update files to "update.zip". So the latest OTA you took, you should decrypt it "if it needs it", open in 7zip or Winzip and pull the update.zip file and copy that to your EXT SD card.
The final Official release build, was build .021. So if you still get SOD on .021, then chances are you have one of the later revision tablets, and may have to wait a long time until Acer releases another update, as the later revisions only account for a very small percentage.
Or, you can install the unlocked bootloader, and try one of the newer kernels we have.
MD

Moscow Desire said:
This is probably because of a couple of reasons.
1. You didn't do the incremental update. The available update files are incremental patch files, which means you have to have the others installed before you install the latest. Or at least part 1 and 2 of the original leak.
2. You didn't decrypt the file and remove the "update.zip". Generally, you can't just rename these update files to "update.zip". So the latest OTA you took, you should decrypt it "if it needs it", open in 7zip or Winzip and pull the update.zip file and copy that to your EXT SD card.
The final Official release build, was build .021. So if you still get SOD on .021, then chances are you have one of the later revision tablets, and may have to wait a long time until Acer releases another update, as the later revisions only account for a very small percentage.
Or, you can install the unlocked bootloader, and try one of the newer kernels we have.
MD
Click to expand...
Click to collapse
Thanks for your replay. So what i did was to install all available OTA updates. Then i downloaded the full package Ice Cream Sandwich 4.0.3 (LEAK) from the site above, extracted the update.zip from this archive and put it on the external sd card. i think that is all i have to do. And my current build number is Acer_AV041_A501_1.021.00_EMEA_DE...so don't know exactly if "[LEAK]Acer A501 ICS (COM_GEN1). Build number 041.126.01" is the same version.
And i tried to unlock my bootloader but the next funny thing is that i tried that Afterota-Tool, but it stucks at 3/4 "Flashing recovery...".
I don't want to loose my 3G-Feature and i saw that nearly all roms are only for A500. Which kernel and rom would you recommend for me?
Looking forward for your replay. Thx a lot!

captainn said:
Thanks for your replay. So what i did was to install all available OTA updates. Then i downloaded the full package Ice Cream Sandwich 4.0.3 (LEAK) from the site above, extracted the update.zip from this archive and put it on the external sd card. i think that is all i have to do. And my current build number is Acer_AV041_A501_1.021.00_EMEA_DE...so don't know exactly if "[LEAK]Acer A501 ICS (COM_GEN1). Build number 041.126.01" is the same version.
And i tried to unlock my bootloader but the next funny thing is that i tried that Afterota-Tool, but it stucks at 3/4 "Flashing recovery...".
I don't want to loose my 3G-Feature and i saw that nearly all roms are only for A500. Which kernel and rom would you recommend for me?
Looking forward for your replay. Thx a lot!
Click to expand...
Click to collapse
You current build is cooked my friend. Unless you want Acer repair.
Most of all OTA ICS Updates are Com Gen 1 now. Not sure what acer had in mind. But I believe it has duetch or danish language.
You have to use a 501 update if you want to use 3g and GPS.
My question, were you successful in booting to your system after installing the updates correctly? That is my primary question. If so, make sure you have USB debugging turned on.
But I need to know exactly what your tablet is in now before going further. Does it boot into the OS after running the updates?
MD

Moscow Desire said:
You current build is cooked my friend. Unless you want Acer repair.
Most of all OTA ICS Updates are Com Gen 1 now. Not sure what acer had in mind. But I believe it has duetch or danish language.
You have to use a 501 update if you want to use 3g and GPS.
My question, were you successful in booting to your system after installing the updates correctly? That is my primary question. If so, make sure you have USB debugging turned on.
But I need to know exactly what your tablet is in now before going further. Does it boot into the OS after running the updates?
MD
Click to expand...
Click to collapse
I don't know exactly which updates you are talking about. I installed all the available ota updates and the tablet booted correctly after this. If you mean any other update via sd-card i can only tell you that i was not able to install one of them. what do you mean with "cooked"? sorry for stupid questions
My USB debugging ist turned on, firewall and uac off.
Thx.

captainn said:
I don't know exactly which updates you are talking about. I installed all the available ota updates and the tablet booted correctly after this. If you mean any other update via sd-card i can only tell you that i was not able to install one of them. what do you mean with "cooked"? sorry for stupid questions
My USB debugging ist turned on, firewall and uac off.
Thx.
Click to expand...
Click to collapse
The only stupid question, is the one that doesn't get asked
What is the current version you are on? (settings/about tablet) The current build should be .021
MD

Moscow Desire said:
The only stupid question, is the one that doesn't get asked
What is the current version you are on? (settings/about tablet) The current build should be .021
MD
Click to expand...
Click to collapse
Android 4.0.3
Kernel 2.6.39.4+
Image Acer_AV041_A501_RV20RC05_EMEA
Build Acer_AV041_A501_1.021.00_EMEA_DE
P/N FM.S14A0.02A
Is it all you need?

captainn said:
Android 4.0.3
Kernel 2.6.39.4+
Image Acer_AV041_A501_RV20RC05_EMEA
Build Acer_AV041_A501_1.021.00_EMEA_DE
P/N FM.S14A0.02A
Is it all you need?
Click to expand...
Click to collapse
Yes, you have build .021 But I am surprised it's not WW_Com_Gen_1
This is the latest Acer build. So stay with it.
Ok, info for you, I am currently working with kernel dev's to maybe get something better as far as kernels, that may help with your SOD if you still have it.
For right now, let us work on things. This may take a few days.
As with Unlocked Bootloader and CWM recovery.
Here is what you should do.
GET YOUR UID NUMBER and write it down.
1. Make sure your Acer drivers are installed.
2. Using After OTA, only install the Patched Bootloader.
3. If you already have the patched bootloader installed (you see Skirlax_CZ bootloader text when you boot),
Did it install the patched bootloader?
MD

Moscow Desire said:
Yes, you have build .021 But I am surprised it's not WW_Com_Gen_1
This is the latest Acer build. So stay with it.
Ok, info for you, I am currently working with kernel dev's to maybe get something better as far as kernels, that may help with your SOD if you still have it.
For right now, let us work on things. This may take a few days.
As with Unlocked Bootloader and CWM recovery.
Here is what you should do.
GET YOUR UID NUMBER and write it down.
1. Make sure your Acer drivers are installed.
2. Using After OTA, only install the Patched Bootloader.
3. If you already have the patched bootloader installed (you see Skirlax_CZ bootloader text when you boot),
Did it install the patched bootloader?
MD
Click to expand...
Click to collapse
So in Afterota i open the tab advanced and there i can choose "browse for custom bootloader" and i can choose between different binary files. I think "bl_ics_ac_v8.bin" or "bl_ics_pb_v8.bin" should be right. What's the difference, what's the right one?

captainn said:
So in Afterota i open the tab advanced and there i can choose "browse for custom bootloader" and i can choose between different binary files. I think "bl_ics_ac_v8.bin" or "bl_ics_pb_v8.bin" should be right. What's the difference, what's the right one?
Click to expand...
Click to collapse
Well, I did things the old fashioned way.
If I am to guess. the first one is CWM recovery included, and the second is Public Recovery included. I never used this tool
I would choose door number 1
BTW, there are other methods to install these things. But let's see what happens. Personally, I don't use these all in 1 tools. Got too many of them in the forums. But, let's see what happens.
If not successful, we'll use My method. And you will learn something in the process.
MD

Moscow Desire said:
Well, I did things the old fashioned way.
If I am to guess. the first one is CWM recovery included, and the second is Public Recovery included. I never used this tool
I would choose door number 1
BTW, there are other methods to install these things. But let's see what happens. Personally, I don't use these all in 1 tools. Got too many of them in the forums. But, let's see what happens.
If not successful, we'll use My method. And you will learn something in the process.
MD
Click to expand...
Click to collapse
*LOL* Tool doesn't work at all...so i will do it by using another method...can you recommend one that really works= :fingers-crossed:

captainn said:
*LOL* Tool doesn't work at all...so i will do it by using another method...can you recommend one that really works= :fingers-crossed:
Click to expand...
Click to collapse
Ehhhh,,, we're gonna do it my way now.
Ok, keep in mind, it's late in Moscow, and I have a baby that will need bath (long process) and other family duties.
Let's get your computer prepared the way it should always be when dealing with the dark side of android.
Your tab is running now, and that's good. You have a .021 build. Ok. But let;s see if we can make it better.
First thing, and I hope you have Windows XP or Windows 7.
Download and install the Android SDK.
http://developer.android.com/sdk/index.html
Now, next, is the Oracle Java Platform (JDK)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
After you do these 2 things, well, we can move over to the dark side.
Now, after everything is installed, I want you to do something.
Connect your tab with USB debugging on. (Never turn this off)
Open Windows explorer, go to C:\program file (x86)\Android\Android-sdk\platform tools . Open a command window here (SHIFT & Right mouse click)
Then type adb devices in the CMD window. Should show device connected and some numbers.
This tells me the drivers are installed.
If not, You have to install Acer USB drivers from the website.
Then try again.
And that, is as far as I go tonight, too late.
Tomorrow, I will give you a lesson in NVFlash and fastboot.
Rule number 1. Drivers, Drivers, Drivers. This was just to prepare your system.
To save some time, for tomorrow, shut down your tab.
Using a paper clip, or needle or something. Press and hold the pin hole button near the USB port. Hold it. Then, press and hold PWR button. Wait 4 seconds, release PWR only. 1 second later, release the pin hole.
Tab should be black. PWR button white. You may get vibrate.
This is what we call APX mode.
When you connect your tab to your PC, after a few seconds, the PC should recognize this as (Recovery Mode, APX Mode, or Download Mode)
Will need to know what it says. If it says nothing, but gives you an error in Windows device manager, then Houston, we have a problem. And the problem is the drivers. And you need to fix it. You may have to manually select from a list or tell it where the drivers are.
And that is all for tonight Mate. Baby needs bath.
MD

Thank you very much. I installed the bootloader, the recovery and the tegraowner ics rom for the A501. It looks great and it seems that SOD is now part of the history 3G is also working. Great success :laugh:
Thanks for your help and to all developers!

captainn said:
Thank you very much. I installed the bootloader, the recovery and the tegraowner ics rom for the A501. It looks great and it seems that SOD is now part of the history 3G is also working. Great success :laugh:
Thanks for your help and to all developers!
Click to expand...
Click to collapse
Great! Was waiting to hear!
Not that I demand it, but, it's customary to hit the "thanks" button for those that help
Always remember, you have a "fastboot" bootloader, so if something happens, you can boot to the Fastboot, and do things like install boot.img's (kernels), Custom Recoveries, and some other things. That's why you installed Android SDK. Also, you have ADB capability as well.
Rock On!
MD

Moscow Desire said:
Great! Was waiting to hear!
Not that I demand it, but, it's customary to hit the "thanks" button for those that help
Always remember, you have a "fastboot" bootloader, so if something happens, you can boot to the Fastboot, and do things like install boot.img's (kernels), Custom Recoveries, and some other things. That's why you installed Android SDK. Also, you have ADB capability as well.
Rock On!
MD
Click to expand...
Click to collapse
In addition: Now i am using "ICS Evil Alex Unleashed Ver 2". I switched because gps is not working when using tegraowners rom. Now it seems, that all important features are working! Thanks a lot for your rom!

I have the official A500 ICS, didn't do anything other than the OTA upgrade, and it worked fine until I installed some additional apps, it started to do the SOD. Then I uninstalled the latest apps I added, more likely instagram, and the SOD went away, till now at least. So, if you can't get it to work, maybe a factory reset to clear out all the apps might help, then, add apps slowly to see find out which one actually act bad.

Moscow Desire said:
Ehhhh,,, we're gonna do it my way now.
Ok, keep in mind, it's late in Moscow, and I have a baby that will need bath (long process) and other family duties.
Let's get your computer prepared the way it should always be when dealing with the dark side of android.
Your tab is running now, and that's good. You have a .021 build. Ok. But let;s see if we can make it better.
First thing, and I hope you have Windows XP or Windows 7.
Download and install the Android SDK.
http://developer.android.com/sdk/index.html
Now, next, is the Oracle Java Platform (JDK)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
After you do these 2 things, well, we can move over to the dark side.
Now, after everything is installed, I want you to do something.
Connect your tab with USB debugging on. (Never turn this off)
Open Windows explorer, go to C:\program file (x86)\Android\Android-sdk\platform tools . Open a command window here (SHIFT & Right mouse click)
Then type adb devices in the CMD window. Should show device connected and some numbers.
This tells me the drivers are installed.
If not, You have to install Acer USB drivers from the website.
Then try again.
And that, is as far as I go tonight, too late.
Tomorrow, I will give you a lesson in NVFlash and fastboot.
Rule number 1. Drivers, Drivers, Drivers. This was just to prepare your system.
To save some time, for tomorrow, shut down your tab.
Using a paper clip, or needle or something. Press and hold the pin hole button near the USB port. Hold it. Then, press and hold PWR button. Wait 4 seconds, release PWR only. 1 second later, release the pin hole.
Tab should be black. PWR button white. You may get vibrate.
This is what we call APX mode.
When you connect your tab to your PC, after a few seconds, the PC should recognize this as (Recovery Mode, APX Mode, or Download Mode)
Will need to know what it says. If it says nothing, but gives you an error in Windows device manager, then Houston, we have a problem. And the problem is the drivers. And you need to fix it. You may have to manually select from a list or tell it where the drivers are.
And that is all for tonight Mate. Baby needs bath.
MD
Click to expand...
Click to collapse
Great tutorial!
I have a500 with ota ICS. Rooted. Locked bootloader. And working fine, but I think it could be better..
I am used to flashing rom and kernel on my android phone, but it looks like it is a bit more difficult on this device..
If I want to try another rom, should I follow your tutorial first? Or what do I do?
Oh, and what rom do you recommend? - I need fast, reliable and everything working.. Nothing fancy is required
Sent from my A500 using xda app-developers app

Installing Atrix-MROM on an Atrix 4G with 4.5.145 update.

Just incase anyone with an Atrix 4G and 4.5.145 firmware, I followed the instructions in the following threads to successfully install Atrix-MROM on a brand new Atrix 4G ATT with the latest update.
1- Bootloader Unlock: http://forum.xda-developers.com/showthread.php?t=1182871
2- Root: http://forum.xda-developers.com/showthread.php?t=1769497
3- CWM Flash: http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot
4- Atrix-MROM Flash: http://www.montuori.net/android-mrom/atrix-mrom/
Thank you Michael Montuori, the Atrix-MROM is awesome.

Rooting (step 2) is completely irrelevant and unnecessary. I've said this before. Still not sure why people constantly think rooting does anything if they're going to flash a new ROM anyway.

ravilov said:
Rooting (step 2) is completely irrelevant and unnecessary. I've said this before. Still not sure why people constantly think rooting does anything if they're going to flash a new ROM anyway.
Click to expand...
Click to collapse
I think this is because, normally, they would need it to flash CWM. But it doesn't happen on Atrix. .

Yeah, that's pretty much what I thought. People scarred/traumatized by other brands/phones and thinking everything is the same on all the other ones.
Oh well. Hopefully they'll learn one day. Hopefully a little sooner than the Atrix REALLY becomes obsolete.

ravilov said:
Yeah, that's pretty much what I thought. People scarred/traumatized by other brands/phones and thinking everything is the same on all the other ones.
Oh well. Hopefully they'll learn one day. Hopefully a little sooner than the Atrix REALLY becomes obsolete.
Click to expand...
Click to collapse
This is my first smart phone, and I am absolute noob in this field.
I have been using Nokia 1216 and similar monochrome display phones before it.

In that case, I gues you're actually doing quite well really... If you came from mono dumbphones straight to this and have already flashed a custom ROM, that's actually kinda impressive.

Thanks!!!
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM

pinofly said:
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
Click to expand...
Click to collapse
Glad it helped you.

pinofly said:
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
Click to expand...
Click to collapse
Please can you tell me, where i found the tool for unlock bootloader of step 1, because the link is outdated, thank you.

aarizaga said:
Please can you tell me, where i found the tool for unlock bootloader of step 1, because the link is outdated, thank you.
Click to expand...
Click to collapse
It is in that thread. You can search: automatic_unlock_v4.2.zip
Or here it is:
h t t p s:// w w w . d r o p b o x . com/s/sr6ooho4zf9wqvo/automatic_unlock_v4.2.zip
Scan it first..

The MROM is simply amazing. Best battery life so far trying the cm7 based roms!
Sent from my MB860 using xda app-developers app

I am a neewbie, and when i learned how to flash custom roms, i was wondering, it is really necesary to root if you want a custom ROM?
now i was clarified.
So if want original firmware, and root acces, i just need an unlocked bootloader? And for rooting, can i just flash a fruitcake?
Sent from my MB860 using xda app-developers app

Hi, Thank you mmontuori for the excellent Rom and hard work to do it, and to Ravilov for the help.
I want to thanks in the post of the MROM in the development forum, but I can't do it because I don't have enough posts.
Well I finish yesterday to put all in order, only my contacts information I fail to restore.
The Go Backup didn't work.
One question, I don't installed the sv kernel, is necesary? because I feel that the battery it drain very quickly.
The rest appear so far to work very well, checking the holo launcher.

are you 100% sure everything on first post works with an ATRIX 4G 4.15.1455 from AT&T wiht the original motoblur?
i am newbee but wants to learn. its probably could i kill the phone?
thx!

Atrix 4g ATT 4.5.145 working well with CM 7.2
I have an Atrix 4g that was about to be retired or sold, and decided to instead make it an android project to learn about modding and possibly make something useful out of an old device.
After combing the forums on this site and others, realized there was some risk involved of a hard brick, but since this is not my main phone anymore, I wasnt too worried about. I'll share the results...
The phone was running gingerbread 2.3.6, ATT 4.5.145 build
#1) Root phone (http://forum.xda-developers.com/showthread.php?t=1769497)
Step 10 did generate an error for me, I had to issue the alternate command and it worked fine.
I downloaded root checker by JOEYKRIM on google play store to ensure it was rooted properly afterwards.
#2) Backup the phone in case of trouble (I used titanium backup from google play store, requires rooting from step 1)
Add a schedule to backup all and execute the schedule now. Pretty easy stuff
#3) Unlock bootloader (http://forum.xda-developers.com/show....php?t=1182871)
This is probably the most dangerous step. I used the link above and would like to add a few comments. The link above is a script written to automate the process for those not terribly familiar with the android tools ADB and fastboot. This script is capable of unlocking your bootloader, fixing some common problems that happen along the way, and installing clockworkmod so you can access android recovery mode to install custom ROMs. However, it seems to come with an older version of the clockworkmod, therefore I used it for the bootloader only (option 1 from main menu). I also had to execute option 3 afterwards as I did get the failure to boot 0x1000 error. Long story short.. I used option 1, then option 3 and skip the rest.
#4) PUSH ROM files of your choice to phone (I used Cryogenmod 7.2 latest from http://download.cyanogenmod.org/?device=olympus)
You should also copy any other addon ROMs of your choice to the phone at this time as well. Google store app is one that is not included with CM 7.2 and you can get here (make sure to pick the one for the version of CM you are choosing) http://wiki.cyanogenmod.org/w/Google_Apps
To push the files to your phone, simply boot your phone in the stock ROM, connect it to your PC with usb, and make sure the USB connection notification is set to USB mass storage. You can then copy the ROM files in zip form to the root directory of the drive letter of the phone from your PC just like you'd copy to a USB stick. Change the USB notification/communication mode on the phone back to stock setting of motorola phone app afterwards, as this dismounts the internal SDCARD storage and the phone wont remount it until you do.
This is out of order from some of the other guides. The reason to place the ROM files first before anything else, is so you can install clockworkmod to make recovery possible, then go right into it and install the ROMs from recovery mode. I had some issue with installing recovery with CWM first, then CWM not working if the phone booted into the stock rom (looks like the recovery was overwritten. I simply had to have the ROM files ready to go then do CWM all at once to make this work.
#5) Install CWM clockworkmod. (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot)
Follow the steps under installing recovery under fastboot. A link is provided for the latest CWM 5.0.2.0, which is what I used instead of the 4.0 version included in the unlock bootloader script mentioned in MY step 2.
At step 7, my phone appeared to hang at Flash boot: SOS. Some other users reported this as well. I just let the phone sit there for 3-5 minutes to make sure it was done with the operation. I then manually rebooted the phone holding down volume down button and holding power button until the phone powered down. If the phone is still connected to the PC, it will automatically power back on, so continue to hold the volume down until fastboot appears, then tapped volume down to cycle through the menu and chose Android recovery from the boot menu and press volume UP to execute it. CWM loaded up just fine and I was able to choose recovery ROMs we pushed in step #3 of my guide there and reboot.
Sorry if this is not as detailed as it could be, but I wrote this a bit after the fact without taking screenshots or writing down every step of the way. This is my best recollection of what I went through and figured I'd share as many consider this a gamble with the Atrix 4g and ATT 4.5.145.
Overall experience with the CM 7.2 ROM:
I've been running the phone for a bit now with cryogenmod 7.2 without issue. The battery life is fanastic and there are many nifty options included with CM 7.2 I have not experienced the random reboots or overheating some others have mentioned.
The only issues I've ran into so far, the latest youtube app from google store does not seem to play videos. You can install a QR code scanner app from google play store of your choice, then download the youtube app that worked for me via QR code from http://forum.xda-developers.com/showthread.php?p=18157961#post18157961
Additionally, internal storage (what's considered the SDCARD on this phone) was not mounted by default in CM 7.2. Reference this to fix it. http://forum.xda-developers.com/showthread.php?t=1481252
I hope this helps users out there with old Atrix 4g's considering giving them new life. I'm going to try CM 10.x soon to see how jellybean runs on the Atrix 4g. Wish me luck!
Vengaence

Vengaence said:
I have an Atrix 4g that was about to be retired or sold, and decided to instead make it an android project to learn about modding and possibly make something useful out of an old device.
After combing the forums on this site and others, realized there was some risk involved of a hard brick, but since this is not my main phone anymore, I wasnt too worried about. I'll share the results...
The phone was running gingerbread 2.3.6, ATT 4.5.145 build
#1) Root phone (http://forum.xda-developers.com/showthread.php?t=1769497)
Step 10 did generate an error for me, I had to issue the alternate command and it worked fine.
I downloaded root checker by JOEYKRIM on google play store to ensure it was rooted properly afterwards.
#2) Backup the phone in case of trouble (I used titanium backup from google play store, requires rooting from step 1)
Add a schedule to backup all and execute the schedule now. Pretty easy stuff
#3) Unlock bootloader (http://forum.xda-developers.com/show....php?t=1182871)
This is probably the most dangerous step. I used the link above and would like to add a few comments. The link above is a script written to automate the process for those not terribly familiar with the android tools ADB and fastboot. This script is capable of unlocking your bootloader, fixing some common problems that happen along the way, and installing clockworkmod so you can access android recovery mode to install custom ROMs. However, it seems to come with an older version of the clockworkmod, therefore I used it for the bootloader only (option 1 from main menu). I also had to execute option 3 afterwards as I did get the failure to boot 0x1000 error. Long story short.. I used option 1, then option 3 and skip the rest.
#4) PUSH ROM files of your choice to phone (I used Cryogenmod 7.2 latest from http://download.cyanogenmod.org/?device=olympus)
You should also copy any other addon ROMs of your choice to the phone at this time as well. Google store app is one that is not included with CM 7.2 and you can get here (make sure to pick the one for the version of CM you are choosing) http://wiki.cyanogenmod.org/w/Google_Apps
To push the files to your phone, simply boot your phone in the stock ROM, connect it to your PC with usb, and make sure the USB connection notification is set to USB mass storage. You can then copy the ROM files in zip form to the root directory of the drive letter of the phone from your PC just like you'd copy to a USB stick. Change the USB notification/communication mode on the phone back to stock setting of motorola phone app afterwards, as this dismounts the internal SDCARD storage and the phone wont remount it until you do.
This is out of order from some of the other guides. The reason to place the ROM files first before anything else, is so you can install clockworkmod to make recovery possible, then go right into it and install the ROMs from recovery mode. I had some issue with installing recovery with CWM first, then CWM not working if the phone booted into the stock rom (looks like the recovery was overwritten. I simply had to have the ROM files ready to go then do CWM all at once to make this work.
#5) Install CWM clockworkmod. (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot)
Follow the steps under installing recovery under fastboot. A link is provided for the latest CWM 5.0.2.0, which is what I used instead of the 4.0 version included in the unlock bootloader script mentioned in MY step 2.
At step 7, my phone appeared to hang at Flash boot: SOS. Some other users reported this as well. I just let the phone sit there for 3-5 minutes to make sure it was done with the operation. I then manually rebooted the phone holding down volume down button and holding power button until the phone powered down. If the phone is still connected to the PC, it will automatically power back on, so continue to hold the volume down until fastboot appears, then tapped volume down to cycle through the menu and chose Android recovery from the boot menu and press volume UP to execute it. CWM loaded up just fine and I was able to choose recovery ROMs we pushed in step #3 of my guide there and reboot.
Sorry if this is not as detailed as it could be, but I wrote this a bit after the fact without taking screenshots or writing down every step of the way. This is my best recollection of what I went through and figured I'd share as many consider this a gamble with the Atrix 4g and ATT 4.5.145.
Overall experience with the CM 7.2 ROM:
I've been running the phone for a bit now with cryogenmod 7.2 without issue. The battery life is fanastic and there are many nifty options included with CM 7.2 I have not experienced the random reboots or overheating some others have mentioned.
The only issues I've ran into so far, the latest youtube app from google store does not seem to play videos. You can install a QR code scanner app from google play store of your choice, then download the youtube app that worked for me via QR code from http://forum.xda-developers.com/showthread.php?p=18157961#post18157961
Additionally, internal storage (what's considered the SDCARD on this phone) was not mounted by default in CM 7.2. Reference this to fix it. http://forum.xda-developers.com/showthread.php?t=1481252
I hope this helps users out there with old Atrix 4g's considering giving them new life. I'm going to try CM 10.x soon to see how jellybean runs on the Atrix 4g. Wish me luck!
Vengaence
Click to expand...
Click to collapse
Cwm 5.0.2.7 is the up to date recovery (possibly outdated now, see new 4.3.1 for recovery (haven't tried it out yet))
Everything you just posted has already been mentioned over several threads over the past 3 yrs. We all are well aware of these instructions, long before you essentially copied, pasted, and edited into your own words, that detail the process of rooting, unlocking the bootloader, flashing a custom recovery, and flashing a custom ROM.
Sent from my MB886 using xda app-developers app

palmbeach05 said:
Cwm 5.0.2.7 is the up to date recovery (possibly outdated now, see new 4.3.1 for recovery (haven't tried it out yet))
Everything you just posted has already been mentioned over several threads over the past 3 yrs. We all are well aware of these instructions, long before you essentially copied, pasted, and edited into your own words, that detail the process of rooting, unlocking the bootloader, flashing a custom recovery, and flashing a custom ROM.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
The tone of your response implies that I'm trying to take some sort of credit for other people's work. The reason I posted is I've noticed some folks fairly recently with doubts about this process working specifically with this exact phone and ATT 4.5.145, and I wanted to share my experience and encourage others to do it if they were on the fence. I appreciate the work of this forum and other folks who have poured hours of time into these custom projects to make the android experience better.
I notice that you are a senior member. I'd suggest that replies are restricted on this forum to constructive responses, and not negative ones.
Thank you!

Vengaence said:
The tone of your response implies that I'm trying to take some sort of credit for other people's work. The reason I posted is I've noticed some folks fairly recently with doubts about this process working specifically with this exact phone and ATT 4.5.145, and I wanted to share my experience and encourage others to do it if they were on the fence. I appreciate the work of this forum and other folks who have poured hours of time into these custom projects to make the android experience better.
I notice that you are a senior member. I'd suggest that replies are restricted on this forum to constructive responses, and not negative ones.
Thank you!
Click to expand...
Click to collapse
Actually it was more along the lines of you were repeating things that have been said already time and time again. That was the true meaning of my post. I do apologize if it may not have been conveyed in a manner that my intention clear.
Also, the recovery. I just flashed the new one from the new 4.3.1 thread. It is indeed an update, bringing it up to revision 6.0.4.6. This is a huge step forward and lays the groundwork for 4.4 (most kk roms require at a minimum cwm 6.0.4.4)
Sent from my MB886 using xda app-developers app

CWM versions for Atrix 4g
palmbeach05 said:
Actually it was more along the lines of you were repeating things that have been said already time and time again. That was the true meaning of my post. I do apologize if it may not have been conveyed in a manner that my intention clear.
Also, the recovery. I just flashed the new one from the new 4.3.1 thread. It is indeed an update, bringing it up to revision 6.0.4.6. This is a huge step forward and lays the groundwork for 4.4 (most kk roms require at a minimum cwm 6.0.4.4)
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------
I notice you have an MB886, Atrix HD according to your signature. This thread is for the Atrix 4G. I'm not sure if you realized this. Maybe that is the reason why we are not seeing eye to eye. The Atrix 4g is older and is quirky and there have been many horror stories. I havn't seen many of those stories with the Atrix HD and things are more straight forward.
According to http://www.clockworkmod.com/rommanager
the latest CWM for the Atrix 4G is 5.0.2.0 and that's what is used by http://forum.xda-developers.com/showthread.php?t=2613829
as well to install later versions of CM such as 10.2 on the Atrix 4g. It's also what I used for CM 7.2
On your Atrix HD, CWM 6.0.4.x should be used.
Vengaence

Vengaence said:
--------------------------------------------------------------------------------------------------------------------------------
I notice you have an MB886, Atrix HD according to your signature. This thread is for the Atrix 4G. I'm not sure if you realized this. Maybe that is the reason why we are not seeing eye to eye. The Atrix 4g is older and is quirky and there have been many horror stories. I havn't seen many of those stories with the Atrix HD and things are more straight forward.
According to http://www.clockworkmod.com/rommanager
the latest CWM for the Atrix 4G is 5.0.2.0 and that's what is used by http://forum.xda-developers.com/showthread.php?t=2613829
as well to install later versions of CM such as 10.2 on the Atrix 4g. It's also what I used for CM 7.2
On your Atrix HD, CWM 6.0.4.x should be used.
Vengaence
Click to expand...
Click to collapse
Ah, correct and incorrect my friend. While my signature may point out what device i am currently on, it does not reflect my past. A peice of supporting evidence is over in AtrICS v2.0 (see home button fix)
As far as cwm goes, cwm has unofficial builds as well. Look through one of the threads, it will point you to a link about recoveries and there does exist a 5.0.2.8. EDIT It was Romracer's recovery, accesed through the unlock bootloadrr thread a few threads down from this one. The 5.0.8.x i think was more like a 5.8.1.8, but i think that was a touch version? Now CM and the other threads may say the 5.x is ok for all of our roms, but as android moves forward, so must our support from libs, apps, kernels, scripts, and of course, recoveries. That is why i promoted the 6.0.4.6 revision both here and in the new 4.3.1 thread.
Sent from my MB886 using xda app-developers app

[GUIDE] How to: Install CM10.2 on LOCKED bootloader [Xperia SP]

Disclaimer:
I am not to be held responsible for any actions that you take by following this guide that result in harm to your device. Sony devices are almost impossible to brick.
pre-requirements:
You're going to need the following things:
Flashtool
CWM Xperia SP Package
.266 4.3 kernel
.257 firmware
DooMLoRD easy rooting toolkit
CyanogenMod 10.2 Package & gapps
Step 1:
extract Flashtool, place the .257 firmware file in the firmwares folder and then run flashtool, flash the .257 firmware. This process could take 5-10 minutes.
To do this, click the electric bolt symbol in FlashTool, and select Flashmode, select .257 and then when the prompt says to connect your device in flashmode, power off your phone and holding volume down, plug your phone into the computer. This will then flash the files.
Turn your phone back on and enable USB debugging in android development settings.
Step 2:
Extract DooMLoRD's easy rooting toolkit and make sure that you have your phone connected and adb is enabled, while the phone is powered on run the script and this will then root your phone, do this by double clicking runme_win.bat, your phone will reboot in this process and it will be rooted.
Step 3:
Time to install a custom recovery, unpack the CWM Xperia SP package listed above. Make sure your phone is still turned on and in adb mode (USB debugging enabled) and then run install.bat from the package. You will need to accept a superuser request prompt on your phone meaning that you will need your phone screen on. Recovery is now installed.
Step 4:
Copy the CyanogenMod 10.2 package & google apps package to your phone, reboot into clockwork recovery by pressing the volume UP button once when you see the blue LED light up and feel a short vibration while your phone is booting. In CWM choose factory reset, and then install the two files we put on your phone using install zip from sd card option. Use volume rockers to navigate and power button to select options. Make sure you install CM zip then Google apps zip
Step 5:
After installing the ROM, power off your device in CWM and then connect your device in FlashMode again (hold vol down while plugging into computer) and then flash the .266 kernel only file. Reboot your phone.
Step 6:
Enjoy! You now have CyanogenMod and CWM installed on your phone, even with a locked bootloader. Recovery is now accessed with volume down.
I appreciate thanks greatly, and any issues I can help with and you can discuss them in this thread. I hope I have helped.
KeiranFTW

awesome

That. It's one good guide that anybody can follow. Just one question. Will this rom be as stable as normal cm, will it be full cm or just a stripped down version
Sent from my C5303 using Tapatalk

can this rom be flashed on ROOTED device running 4.3

zolaisugly said:
That. It's one good guide that anybody can follow. Just one question. Will this rom be as stable as normal cm, will it be full cm or just a stripped down version
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
I don't see why it can't be as stable as normal CM.. The only thing that isn't working at the moment is GPS, everything else to be honest it runs smoother than stock.
I'm going to work on getting AOKP to work if they have a compilable 4.3 branch. I'm also going to try and encourage ROM devs to add locked bootloader support and I shall show them how
pchetan2 said:
can this rom be flashed on ROOTED device running 4.3
Click to expand...
Click to collapse
Just follow the steps, if you have CWM installed on your XSP with 4.3 already all you need to do is flash the ROM in CWM nothing else..
I posted method for 4.1.2 because I'm presuming the user does not have root, and this is only rootable firmware.
Sent from my C5303 using Tapatalk

Awesome job to able get this rom on my lock xperia sp bro. And also am looking forward from you ,that you will bring other roms on my lock xperia sp which is the best phone ever.:good:

To have root on CM I need to flash SuFix as in existenz?

I have never used cm roms before...when the gps. Is fixed I will try rhis out,sadly I use gps alot due to work and driving into towns I don't know etc...
(Q) Due to limited space on sp can we use apps like link2sd and foldermount.
Or does the scripts not run.
Sent from my C5303 using Tapatalk

radeon6002 said:
To have root on CM I need to flash SuFix as in existenz?
Click to expand...
Click to collapse
Nope, su binary is included and root is already in the ROM.
CyanogenMod also features its own root permissions app (Settings -> Superuser) so you dont even need to install supersu or any equivalent, it works out the box.
zolaisugly said:
I have never used cm roms before...when the gps. Is fixed I will try rhis out,sadly I use gps alot due to work and driving into towns I don't know etc...
(Q) Due to limited space on sp can we use apps like link2sd and foldermount.
Or does the scripts not run.
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Theoretically yeah, these scripts should run. I will look into it soon
Sent from my C5303 using Tapatalk

I had just posted a thank-you in another thread for the same - outstanding work. A big thank-you from one who prefer not to touch the BL
And thanks for the lucid instructions. Will download the stuff when I am off work.:good:

yeah i did it succesfully ..need to wipe data and factory reset .then install the rom and gapps....... thank you a lot

Note: the link to the 257 firmware is dead.
[not applicable to those who already rooted their phones ]
EDIT:
Just installed the rom. Also 'upgrage' kernel to 266 (had preferred 254 as it was faster, but with this new rom...)
Question:
a. could one just live with 254 kernel instead of flashing 266 at the end?
b. Now that I have flashed 266, could I re-flash to downgrade (just the kernel) to 254 later on?
Fun time - rom is working on my device.
Thanks a million!

headache59 said:
Note: the link to the 257 firmware is dead.
[not applicable to those who already rooted their phones ]
EDIT:
Just installed the rom. Also 'upgrage' kernel to 266 (had preferred 254 as it was faster, but with this new rom...)
Question:
a. could one just live with 254 kernel instead of flashing 266 at the end?
b. Now that I have flashed 266, could I re-flash to downgrade (just the kernel) to 254 later on?
Fun time - rom is working on my device.
Thanks a million!
Click to expand...
Click to collapse
If you flashed the .254 kernel your Phone won't boot...you just get a bootloop. You need. 266
don't downgrade kernel without downgrading rom as well.
Sent from my C5303 using Tapatalk

Great work by @bagyusz and @KeiranFTW for the initial spark idea. I thot all was lost when i got vendorlocked sp.
I would love to have MIUI (4.3 based) using cm10.2 as base. @OP, if you have any experience of using MIUI patchrom, please help me.
The steps i have already done are:
1. make workspace
2. Make firstpatch
3. Make fullota
now i have to diff and patch the smalis, but not sure exactly how many smalis need to be patched for boot, and how do i know when to stop.
Having LB means to test my port, i have to go thru all the hassle of flash ftf, rooting and then check for every failed attempt.
THanks in advance
Yasir
I know there is an MIUI thread already there, but the OP states its for UBL only, plus he uses 4.2.2 as base. so thot this might be the right place.
---------- Post added at 09:01 PM ---------- Previous post was at 08:56 PM ----------
btw, @ keiran...
I once thot about this... can u confirm im true....
what if we dont format /system partition in updater script of cm.zip... every time, we flash, system wont be formatted so recovery will stay, and if there was something wrong with cm.zip, we can try to fix and flash the new cm.zip and it will overwrite the previous versions of every file hence we know it boots or not.
If it boots, we can do a clean install.
Correct me if im wrong here. Thanks

neXus PRIME said:
Great work by @bagyusz and @KeiranFTW for the initial spark idea. I thot all was lost when i got vendorlocked sp.
I would love to have MIUI (4.3 based) using cm10.2 as base. @OP, if you have any experience of using MIUI patchrom, please help me.
The steps i have already done are:
1. make workspace
2. Make firstpatch
3. Make fullota
now i have to diff and patch the smalis, but not sure exactly how many smalis need to be patched for boot, and how do i know when to stop.
Having LB means to test my port, i have to go thru all the hassle of flash ftf, rooting and then check for every failed attempt.
THanks in advance
Yasir
I know there is an MIUI thread already there, but the OP states its for UBL only, plus he uses 4.2.2 as base. so thot this might be the right place.
---------- Post added at 09:01 PM ---------- Previous post was at 08:56 PM ----------
btw, @ keiran...
I once thot about this... can u confirm im true....
what if we dont format /system partition in updater script of cm.zip... every time, we flash, system wont be formatted so recovery will stay, and if there was something wrong with cm.zip, we can try to fix and flash the new cm.zip and it will overwrite the previous versions of every file hence we know it boots or not.
If it boots, we can do a clean install.
Correct me if im wrong here. Thanks
Click to expand...
Click to collapse
No need to, I am creating build repository that will be able to build CyanogenMod using the cyanogenmod build system, basically I just add the files that are needed for the hack into the repository and then I will be able to build CM and flash it straight off - I'll do this so when the ROM is built it includes recovery and hijack in the /system partition and so when you flash it, it will still be there.
As soon as I get access to a build server I will build AOKP for locked bootloader (jb-mr2)

All work except my wifi. It's grayed out. I got data though...
Just to note: that I was on 4.1.2 (254) rooted when I flashed this rom and GAPPS. After which I flashed the 266 kernel.
Edit:
I did a factory reset under recovery (CWM) and now my wifi has turned on (blue). Unfortunately I am away from my wifi (home) point, so can't test it out fully.
Back to reinstalling of data...

babicsbalu said:
Well done, nice job! :highfive:
Click to expand...
Click to collapse
Don't quote the whole post.

Just preparing for this, I downloaded the kernel from the main thread not the one linked by KeiranFTW do we only need to flash the kernel.sin or do we need other files like fotakernel.sin like when flashing existenz?

Oblox said:
Just preparing for this, I downloaded the kernel from the main thread not the one linked by KeiranFTW do we only need to flash the kernel.sin or do we need other files like fotakernel.sin like when flashing existenz?
Click to expand...
Click to collapse
The link on both threads only feature the .266 kernel - for use after installing cyanogenmod.
The .257 is the full firmware for rooting purposes.
I have already rooted my SP previously therefore, I merely installed CM and flashed the .266 kernel at the end of the process (actually I used my country's version, unchecked all but kernel only) - worked for me.

headache59 said:
The link on both threads only feature the .266 kernel.
I flashed the kernel at the end of the process (actually I used my country's version, unchecked all but kernel only) - and it worked for me.
Click to expand...
Click to collapse
Ahh ok, does the countries kernel make any difference whatsoever?

Database Users

welcome