Database Users

[Q] Howto install cyanogenmod on wildfire

Hi, I would like to install this rom, but I did not found a clear instruction. As I am not so familiar with flashing, I would appreciate if someone can explain step by step what a newcomer has to do, like: how to start, where to download the tools and roms and a step by step installation.
I searched the internet and some forums have instructions like this:
1. Unlock/root your device and install Clockwork Recovery via ROM Manager or Amon_RA's recovery image (You MUST be NAND unlocked!)
2. Do a Nandroid backup!
3. Update your radio if necessary
4. WIPE
5. Install the ROM
5. Optionally install the Google Addon
but this installation steps are not clear. For example: Unlock (how, which tools, where to download), Clockwork recover and Rom Manager (where can I get the latest one, how do I use them), what is NAND unlocked, how do I do an Nandroid backup, how can I update my radio, how do I wipe, how do I instal the ROM and more important where do I get the latest ROM, what are the google addons and where can I found and download them?
I suppose, there are more people like me who will appreciate a clear and easy to understand installation!
Thanks in advance,
M.

metapolis said:
Hi, I would like to install this rom, but I did not found a clear instruction. As I am not so familiar with flashing, I would appreciate if someone can explain step by step what a newcomer has to do, like: how to start, where to download the tools and roms and a step by step installation.
I searched the internet and some forums have instructions like this:
1. Unlock/root your device and install Clockwork Recovery via ROM Manager or Amon_RA's recovery image (You MUST be NAND unlocked!)
2. Do a Nandroid backup!
3. Update your radio if necessary
4. WIPE
5. Install the ROM
5. Optionally install the Google Addon
but this installation steps are not clear. For example: Unlock (how, which tools, where to download), Clockwork recover and Rom Manager (where can I get the latest one, how do I use them), what is NAND unlocked, how do I do an Nandroid backup, how can I update my radio, how do I wipe, how do I instal the ROM and more important where do I get the latest ROM, what are the google addons and where can I found and download them?
I suppose, there are more people like me who will appreciate a clear and easy to understand installation!
Thanks in advance,
M.
Click to expand...
Click to collapse
In my thread there are more relevant instructions.

Hi
I try to figure out how exactly I can flash. As I am not familiar with a lot of things like wording, I don´t really know how to do it and the way of explaining is for me not clear enough to start flashing my wildfire.
For example I visit your thread [2.6.32.21] HCDR.Kernel v4 (Donate) and download the V4 Kernel. I thought it is on file which I start under windows and it does an automatic flash, like the Buzz Rom I used to remove the Vodafone branding - but I realized it is not like this.
I suppose I have to go more deep inside the topic and I wanted to avoid this.

The debrand thing you used is RUU. CM6 is not, so it's not automatic.

http://forceflow.ulyssis.be/2010/10/13/wildpuzzle-rom-for-htc-wildfire/
flashing instructions

I wouldn't mind seeing some more detailed instructions for various things as well. I have flashed my mobile a few times but \i want to flash the kernal so \I can OC on a stock ROM. Unfortunately, there isn't any detailed info on that which I can find.

jcsww said:
I wouldn't mind seeing some more detailed instructions for various things as well. I have flashed my mobile a few times but \i want to flash the kernal so \I can OC on a stock ROM. Unfortunately, there isn't any detailed info on that which I can find.
Click to expand...
Click to collapse
That's exactly the info i am looking for as well.

Go to the hcdr kernel thread, read the instructions which clearly tell you version 4 and above is flashable to any rom... Dl and flash normally

kevin2516 said:
Go to the hcdr kernel thread, read the instructions which clearly tell you version 4 and above is flashable to any rom... Dl and flash normally
Click to expand...
Click to collapse
true, but then again, we are looking for detailed info on how to do this.
like a tutorial for dummies, and that thread is not, they talk about compiling and stuff, i know what it is, but no idea how to do it.

fusk said:
true, but then again, we are looking for detailed info on how to do this.
like a tutorial for dummies, and that thread is not, they talk about compiling and stuff, i know what it is, but no idea how to do it.
Click to expand...
Click to collapse
you don't need to compile anything, that was for the previous versions and is for devs only, just flash the kernel v4.1 normally :S, if you read the OP carefully in that thread, you would understand...

kevin2516 said:
you don't need to compile anything, that was for the previous versions and is for devs only, just flash the kernel v4.1 normally :S, if you read the OP carefully in that thread, you would understand...
Click to expand...
Click to collapse
I see what you mean.
So 4.1 can be flashed to any rom, and it is oc ready, it does not need to be compiled, it already is, the compiling story is for devs only, not us mere mortals.
and if i understood it correctly, then when htc pushes their 2.2 update out, it will install with no problem even tho you have another kernal.

I am so sure that Jacobs Thread covers any step of what to do.

Warlord711 said:
I am so sure that Jacobs Thread covers any step of what to do.
Click to expand...
Click to collapse
Actually, it does not, it might do in a tech kinda way.
But where i had my doubts was knowing that flashing a kernel or installing another rom is done the same way, i thought it was two different procedures.

very simple to understand if you ask me. No tech knowledge needed

Cyanogenmod 7 nighly 22 rebooting problem
Hello Jacob
Thank you for the great work but i had a problem before 1-2 weeks i boot on my phone CM7 i was on CM 6 stable fore that and i didnt had any problem now when i boot nigtly build 22 after 1 day work my phone start to reboot everytime when it turns on when i stop my mobile network i didnt had a problem but with mobile it rebooting. what should i do ?
thank you
PS: i using your kernel 4.1 verion

[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] A little help needed upgrading to ICS

Hi all, I'm running a rooted A500 (Android 3.1 build number Acer_A500_4.010.13_COM_GEN2) using the 2.6.36 Honeyvillian 1.0 kernel (so I could OC) and would like to upgrade to a rooted ICS. But since I changed from the stock kernel I get a little confused trying to follow other threads on what to do. The threads seem to start out on topic but tend to drift and for somebody like me, that can make it very hard to understand. I'd like to stay away from a custom ROM, no insult to the hard working dev's intended. You guys have saved alot of my devices from ending up on the top shelf of the closet. I'd like to upgrade to a "stock" rooted ICS with proper bootloader, kernel, etc. If I decide later to try a dev's ROM then I'll always have that option, but since I've never messed with ICS...stock may do all I need. I'd like to root for OC because some of the things I do seem to run better if the device is OC'd. So, what I need are a clear set of instructions on what to do. OTA's dont work, I'm guessing thats because of the root and kernel. Any help would be appreciated. Thanks.

There are 2 threads with Stock rooted ICS roms in the developer section. Read each and choose the one that suits you. Also, you may need to separately update the bootloader. To do this there is a new tool in the developer section called afterota 1.02. This will help automate the process for you.

Thanks Cruise, but thats where the problem comes in. I've read over the threads you mentioned and I get lost. Because the threads are a generic install method and cant be refined to match my exact situation I dont know where to start. I dont know if I need to return to stock kernel before I do anything else or if I can flash the new stuff the way it is. Do I need to flash the bootloader first or the ROM and what about flashing recovery? Thats why I asked for a clear step by step, the Dev threads tend to be a little hard to follow for somebody with my novice knowledge.

realityrat said:
Thanks Cruise, but thats where the problem comes in. I've read over the threads you mentioned and I get lost. Because the threads are a generic install method and cant be refined to match my exact situation I dont know where to start. I dont know if I need to return to stock kernel before I do anything else or if I can flash the new stuff the way it is. Do I need to flash the bootloader first or the ROM and what about flashing recovery? Thats why I asked for a clear step by step, the Dev threads tend to be a little hard to follow for somebody with my novice knowledge.
Click to expand...
Click to collapse
If you want to go completely stock (stock kernel, non-rooted), then you need only to install one of the Stock ICS Roms. This set's your bootloader back to a stock condition. So that's simple enough. You can do this through CWM
You said you're on Honeyomb right now. So my suggestion, is to follow these steps to upgrade your a500 to ICS.Go Here and read the steps;
http://forum.xda-developers.com/showthread.php?t=1622425
Pay attention to step 4. You have a choice. Stock Rom with Full Root, or (in small print (stock rom no root).
If you decide to install Stock Rom No Root, then skip steps 5 and 6. Just copy the file to your EXT SD Card, boot to your recovery (pwr & Vol-) and install Zip From SD. It'll be a done deal. Recovery gone, ICS Stock bootloader and rom.
I have you do steps 1-3 because I want you to write down your UID!!!!!! It's the only thing that will save you if something messes up.
Then you can decide if you want to root and install some custom stuff later.
MD

MD, can you run setCPU w/o Root? I didn't think so. Since this OP requests the ability to OC specifically I think that the steps listed would all need to be followed in Civato's post.
RR, Here are the steps I recommend, it's an opinion, and I think the best route to take as a fairly novice rooter, I've done my A500 many times and BN Nooks, but nothing else and am not a DEV, but have professionally been in IT for 20 years...so I use novice loosely here...
First, know why you're getting your CPUID:
http://forum.xda-developers.com/showthread.php?p=25429111#post25429111
Don't forget to BACKUP!!
Second, select which ROM you want on your tab, I recommend putting a couple on the MicroSD card so that you can test them. DON'T INSTALL ANYTHING, JUST PICK A COUPLE OF ROMS AND PUT THE ZIPS ON THE SD.
Don't forget to BACKUP!!
Third, follow the steps in the post that MD listed, read twice, run once...
http://forum.xda-developers.com/showthread.php?t=1622425
Don't forget to BACKUP!!
Fourth, flash one of the ROMs you chose previously while in recovery. Can't give you steps on this because they are all different unless you're just using the option in step 4 of the above post (stock w/ root)
Don't forget to BACKUP!!
Fifth, not sure if you can OC the stock w/ root or not, but if not pick a custom ROM and test several, they're all great, and see what fits your needs best. I use Flexreaper Extreme and love it, posted below, but look at ALL of them and find the one you like best, they're all GREAT! We have great DEVs here.
http://forum.xda-developers.com/showpost.php?p=22964651&postcount=1
Don't forget to BACKUP!!
Good Luck, Have fun, and did I mention to make sure you Backup before each step so that you can get back to that point if you run into issues, and make sure you write down or put in a text file on a different device your CPUID...both very important.
Good luck again!
-DB

Thanks everybody for the info but I think I'll be staying on HC for now. The linked threads are the problem I mentioned in the OP. If you look at those threads with novice eyes they are incredibly hard to follow. Not sure why I cant find simple instructions but I do appreciate everyone's help. Maybe somebody will come up with a guide for dummies. Until then I guess I'm stuck with HC. Thanks again for the info.

Mate, it can be daunting even to experienced flashers...
My advice, go to this thread - http://forum.xda-developers.com/showthread.php?t=1622425
This has been cleaned up to make it easy to understand...
I use the manual method to go to apx mode but each to their own...
Now, follow each step. Make sure each step has been followed EXACTLY. Don't skip ahead or you will regret it, sooner than later...
If you have a doubt, go back a step.
Good idea to read through to the end first, especially the bit about checking you sdk...
Good luck....

Step 1: Install Acer drivers. DONE
Step 2: Get cpuid. DONE used afterota, got cpuid and SBK.
Step 3: Get SBK. DONE (see Step 2) I guess I could verify my cpuid and SBK
using the link in this step.
Step 4: Place ROM's on SD card. DONE
Steps 5 & 6: Enter APX mode and Installing ICS bootloader. NOT DONE
I downloaded the apx utility tool and the V7 flash package. The flash package does NOT contain an .a500apx file. The utility tool instructions say to select the .a500apx file NOT the .zip. Where do I find the correct .a500apx flash package? The last step in the Automated Flashing Tools section says to turn off the tablet and power on. I've read you're supposed to flash a ROM before turning off the tablet. Which one is correct? Can I do this with my current configuration as described in the OP or do I need to return my kernel to stock? And last...is ICS really worth the trouble? Thanks again for everybody's input. I do appreciate everybody taking the time to help out.

realityrat said:
Step 1: Install Acer drivers. DONE
Step 2: Get cpuid. DONE used afterota, got cpuid and SBK.
Step 3: Get SBK. DONE (see Step 2) I guess I could verify my cpuid and SBK
using the link in this step.
Step 4: Place ROM's on SD card. DONE
Steps 5 & 6: Enter APX mode and Installing ICS bootloader. NOT DONE
I downloaded the apx utility tool and the V7 flash package. The flash package does NOT contain an .a500apx file. The utility tool instructions say to select the .a500apx file NOT the .zip. Where do I find the correct .a500apx flash package? The last step in the Automated Flashing Tools section says to turn off the tablet and power on. I've read you're supposed to flash a ROM before turning off the tablet. Which one is correct? Can I do this with my current configuration as described in the OP or do I need to return my kernel to stock? And last...is ICS really worth the trouble? Thanks again for everybody's input. I do appreciate everybody taking the time to help out.
Click to expand...
Click to collapse
According to the written steps., you have to download the flash package you want to use from here;
http://a500bootloaderflash.tk/bundles/20120527/
Save then to the same directory you unzipped the tools.
Just checked and everything is in order, so looks like you missed a step
Actually, you really don't have to flash a rom before restarting. If you have a ICS rom installed, more than likely it will boot. (I hope) However, most custom roms have kernels altered to work with the unlocked bootloader. But I would try with your current ICS configuration. If you have any issues, then you can install the custom ICS rom that you saved on your SD Card.
Is it worth it? I think so. Eventually, all support for HC based roms will end. It's the nature of the beast. Most people will be on ICS, and if you have issues with HC, you may not get any recent support.
It's like having a Froyo rom, and trying to get support when most are on Gingerbread and moving to ICS.
You will get responses like "upgrade your device". I will in the near future, end all support for my HC based roms.
MD

Moscow Desire said:
According to the written steps., you have to download the flash package you want to use from here;
http://a500bootloaderflash.tk/bundles/20120527/
Save then to the same directory you unzipped the tools.
Just checked and everything is in order, so looks like you missed a step
Actually, you really don't have to flash a rom before restarting. If you have a ICS rom installed, more than likely it will boot. (I hope) However, most custom roms have kernels altered to work with the unlocked bootloader. But I would try with your current ICS configuration. If you have any issues, then you can install the custom ICS rom that you saved on your SD Card.
Is it worth it? I think so. Eventually, all support for HC based roms will end. It's the nature of the beast. Most people will be on ICS, and if you have issues with HC, you may not get any recent support.
It's like having a Froyo rom, and trying to get support when most are on Gingerbread and moving to ICS.
You will get responses like "upgrade your device". I will in the near future, end all support for my HC based roms.
MD
Click to expand...
Click to collapse
Thanks for the response MD but I still get confused on the step to download the flash package. When I save the file to my computer it no longer has .a500apx in the file name or extension. for example, "a500-icsv6-pubrecovery0.2.a500apx" (from the index of bundles) is downloaded and saved as "a500-icsv6-pubrecovery0.2.zip" so do I extract it and select that file when asked by the utility tool? The guide for the tool says not to select the .zip but to select the .a500apx file. but I dont see one to select.
Also, you said I didnt have to worry about flashing the ROM before restarting. I am currently running HC 3.1 so will an ICS bootloader boot to a HC ROM.
Again, thanks for taking the time to answer my questions. It is really appreciated.

realityrat said:
Thanks for the response MD but I still get confused on the step to download the flash package. When I save the file to my computer it no longer has .a500apx in the file name or extension. for example, "a500-icsv6-pubrecovery0.2.a500apx" (from the index of bundles) is downloaded and saved as "a500-icsv6-pubrecovery0.2.zip" so do I extract it and select that file when asked by the utility tool? The guide for the tool says not to select the .zip but to select the .a500apx file. but I dont see one to select.
Also, you said I didnt have to worry about flashing the ROM before restarting. I am currently running HC 3.1 so will an ICS bootloader boot to a HC ROM.
Again, thanks for taking the time to answer my questions. It is really appreciated.
Click to expand...
Click to collapse
Ok, the link I sent you, is an index of all apx files. It should download as an apx file (I just now checked, and it downloaded and saved as an apx.)
Not sure why they are saving as zips on your system, as none of them are in a zip format. Try doing a "file save as"
Sorry for confusion about rom. I forgot you have an HC rom. I'm running several threads right now for folks with issues. Downlaod an ICS rom to your SD card, so you can install it after you update your bootloader.
MD
EDIT: If you still have issues getting the apx files, let me know, and I'll re-package them in a real zip file and upload it for you.

Moscow Desire said:
Ok, the link I sent you, is an index of all apx files. It should download as an apx file (I just now checked, and it downloaded and saved as an apx.)
Not sure why they are saving as zips on your system, as none of them are in a zip format. Try doing a "file save as"
Sorry for confusion about rom. I forgot you have an HC rom. I'm running several threads right now for folks with issues. Downlaod an ICS rom to your SD card, so you can install it after you update your bootloader.
MD
EDIT: If you still have issues getting the apx files, let me know, and I'll re-package them in a real zip file and upload it for you.
Click to expand...
Click to collapse
Thanks MD, trying to download the apx files doesnt work for me. Not sure why but .zip is the only option I'm given even if i use "save as". So if you could upload the files for me I'd appreciate it. Also, since I will have to disconnect the tablet from the PC after flashing the bootloader can I just power it off, disconnect from PC, reboot into recovery and then flash the new ICS ROM? I also want to be sure that coming from a stock (but rooted) HC rom with a custom kernel wont affect anything. Thanks again for all your help.

realityrat said:
Thanks MD, trying to download the apx files doesnt work for me. Not sure why but .zip is the only option I'm given even if i use "save as". So if you could upload the files for me I'd appreciate it. Also, since I will have to disconnect the tablet from the PC after flashing the bootloader can I just power it off, disconnect from PC, reboot into recovery and then flash the new ICS ROM? I also want to be sure that coming from a stock (but rooted) HC rom with a custom kernel wont affect anything. Thanks again for all your help.
Click to expand...
Click to collapse
I zipped 4 apx packages for your 500. They have the ICS Booltoader and different recoveries. Unzip them to the same folder as your installation package.
http://www.4shared.com/zip/9TE6rTH-/500Bootloader_package.html
Yes, after you finish the bootloader/recovery installation process, turn tablet off. Press and hold Vol- and PWR till you see 2 lines of text in upper left corner, then release both. This will be your recovery menu. From here, you need to follow the instructions from the Rom page where you got your new Rom for the installation. Pretty simple really.
Also, I can't advise you on which recovery to use. I haven't tried the public recovery or TWRP yet.
MD

Thanks MD. Got the files downloaded. I'm gonna read over the threads a few times and make sure I havent missed anything and I also want to research some of the ROM's available. I'll probably give it a try in the next few days. Thanks again for all your help.

**UPDATE**
After reading the threads multiple times and following the instructions carefully I am now running ICS 4.0.3 with updated bootloader!! Everything went fine with only a couple problems that I was easily able to overcome. I'd like to address those problems so if anybody else has problems, 1: when entering the sbk its important to note that the spaces between the sets of numbers ARE needed, and the 0x at the beginning of each set has to be typed with a lowercase "x". 2: I used ezterry ICS 1.031.00stock- full root with busybox, and more tweaks and a500 public recovery. Following the instructions for this ROM I used the "clean up tablet" option in recovery. This DOES NOT do a full data wipe. So first boot had my custom boot animation and all my other apps and settings still there. ICS didnt like this and kept forcing reboots. I had to do a full data wipe and all is good now. I'm on ICS rooted stock and OC'd and loving it. Thank you all for your help, without your input I dont know if I would've tried this but I'm glad I did and I really appreciate everyone taking time out of their busy schedules to help some guy in NY get some ICS love. Thank you all again!

[SOLVED] Vibrant Root Concerns

Hey there. I rooted my Vibrant successfully, but realized I left some important things out. I used this guide to root my Vibrant: http://forum.xda-developers.com/showthread.php?t=723479
The problems:
1) I can't nandroid (not that I need to, I only have 4 apps)
2) I would like to install either Miui v4 or CyanogenMod 9 but cannot as my recovery screen does not show me the options to do so (I only get the 4 options you normally would get unrooted, such as "Reinstall Packages"), so I'm stuck with the lame default homescreen.
3) I'm currently on 2.1-update1; should I upgrade to 2.2? If so, must I unroot to upgrade, and then reroot? And if this were the case, how do you unroot, and can I reroot using the same method in the link above?
Also, I was looking at this guide: http://wiki.cyanogenmod.com/wiki/Sa...te_Guide#Installing_the_ClockworkMod_Recovery
and noticed the line "This guide assumes the Samsung Vibrant already has Android 2.2 build UVKB5 already installed on it."
Does this mean 2.2 is required to install the CWM Recovery?
Thank you.

I'm not sure how you don't have CWM recovery if you followed the guide as it is written. Maybe its because the 2.1 is updated? I would do the following and see if that's all it takes. You definitely don't want to update to stock 2.2 via Kies or anything of that nature.
Worst case scenario, we can have you Odin back to stock JFD. You'll be smooth sailing from there.
Search the forums and find the update.zip for CWM for our Vibrant.
Put that on the lowest level of your INTERNAL storage. Not your microsd card. For example f:\update.zip
Now go to your boring 4 option stock recovery and select reinstall packages. It will reboot to the same boring screen. Select reinstall packages again, and it will reboot into Clockwork Mod Recovery.
Let me know if that does anything for you. Also what version of stock recovery do you have?

Toast6977 said:
Search the forums and find the update.zip for CWM for our Vibrant.
Click to expand...
Click to collapse
Can pull that directly from my signature, if OP wants. (Only works on Eclair [JFD] build btw)
Also OP, You will have to have a ROM that you are going to want to flash saved on your Internal SD card. Jsut download it, put in a folder and follow the ROM OP's instructions. Since you are fresh and new, I would NOT suggest flashing anything of ICS or JB until you get the hang of things first.
Read, read and then read somemore. When it comes time to flash ICS or beyond, there is a guide in my signature. Good luck and make sure to hit Toast's "Thanks" button. He is a good asset to have around here.

Wow! I was hesitant to even check today, let it alone this early! Did not think that I would have two very useful replies waiting for me. Thanks guys, much appreciated!
I'll try the Odin thing out first before I even try to flash (you need root first before flashing, I'm assuming). Just out of curiosity, what is JFD and Odin? I'm still gonna try it out using the guides found here, but just curious.
EDIT: Damn, it worked like a charm! Now I have CWM. The mistake I made was that I only installed the Superuser/ROOT and not both. Gonna play with it for a bit now

I'm glad that your issue was solved
If you have any other questions/issues feel free to hit us up. We tend to lurk around these parts from time to time.
--you could now modify the title of this post to add [Solved] to the title or contact Oka1 and let him know it's case closed.--

Toast6977 said:
I'm glad that your issue was solved
If you have any other questions/issues feel free to hit us up. We tend to lurk around these parts from time to time.
--you could now modify the title of this post to add [Solved] to the title or contact Oka1 and let him know it's case closed.--
Click to expand...
Click to collapse
Thank you for teaching me the etiquette around here as well

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