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
Hey, guys (and girls? )! Just got a new DEFY+ couple of days back and I'd like to get the most out of it. It's already working all smooth and sexy, but I'm sure it can do better. So I need some assistance
Phone info:
DEFY+ (MB526)
Android 2.3.4
System 45.0.74.MB526.Retail.en.DE
Kernel 2.6.32.9-gbad50c3
Build 4.5.1-134_DFP-74
I've rooted it yesterday and I'm pretty sure it was successful, since the phone is working and I've got SuperUser on it since then (I've followed the root part of the all-in-one super DEFY guide thread)
About backing up, I would like to be able to go back to my old backup at any time. Is that even possible? I know I probably never will go back to it, but I like to play things safe. If it is possible, could you teach me how or point me to some nice guide/thread on that?
When it comes to flashing, I'd like to try CM, WAJKIUI and MS2G. Any more ROMs that are a must try? Now, I didn't quite understand... Are there different versions for defy and defy+? Or...which ROMs are compatible with defy+? I've read somewhere that all defy ROMs can't use defy+'s battery properly, so that's what concerns me. Nandload? How to?
I'm sorry if these are stupid questions, I've tried finding out everything from the guides, but I just didn't find enough information... I do have RSD (v5.0.0, is it okay?) and the drivers, all set up. I'm not asking for anyone to write an essay for me, it will be perfectly fine if you just point me to some (really really) good guides. I'll be grateful for any and every answer!
*EDIT #1* Well, I've tried to learn some more... Let's go step by step. Should I install 2ndInit app or some other custom recovery app?
I can beg if need be
"*EDIT #1* Well, I've tried to learn some more... Let's go step by step. Should I install 2ndInit app or some other custom recovery app?"
Hi,
as I've seen the guides, yes.
I've defy, so I didn't try it, but heard from many people with defy+ with CM or MIUI.
BUT before it I suggest to you:
- get a stock sbf of your rom. It is necessary if you want get back the original factory state. hope here you find it: http://forum.xda-developers.com/showthread.php?t=966537
- install titanium backup from market (I know this, but you can install any similar app) and make a full backup (all user and system app). It saves all data, installed apps with settings ...
- make backup of your contacts and sms-s with stock app (it is possible I think)
- make backup of your sd content
After that you can install 2ndinitdefy. Follow the instructions in the program. I suggest 1.4.2 version. If it doesn't work go to 2.0. The 2.0 has instructions not on the main screen but in its menu.
After the 2 reboot (regarding 2ndinit install) you can do a nandroid backup with clockworkmod recovery.
Reboot, push vol down at blue led (after start with 8-10 sec). You are at bootloader. Use vol up/down to navigate and power to enter a menu. Go to recovery-> custom recovery->backup and recovery->backup all. It takes some time. You can save this nandroid to computer (just for safety ) You find it in sd/clockworkmod/backup.
Now you have backups. Go ahead, install the custom rom of your choice.
I recommend WajkIUI. You find the link in my signature and you find installing instructions in Wajk's first post. And of course there are defy+ users in that thread as I remember, you can ask question there.
ps: everything is your responsibility
Was it helpful? Just use thank button
Good luck bro/sis !!!
Thank you for such a long reply!
I have installed 2ndInit, using the v2.0 installer, but I chose the stable version of the 2nd init itself, instead of the latest one. That stable one said it was meant for CM and MIUI, so I'm guessing I'll be alright with WajkIUI as well!
I'll follow the steps you gave me for making a complete backup of everything on my phone and then I'll start looking for a ROM that's fully mb526 compatible (I need >10 posts to be able to post in the development section :/ )
P.S. I'm a bro
I see. This 10 post rule a bit annoying. But as I know you can send private message to anyone. In the Wajkiui thread there are some people with 526.
I've got my 10 posts Thank you once more and I'm sure we'll be talking again soon!
I'm having a hard time finding a full SBF of my stock ROM...
It's 4.5.1-134_DFP-74 (Android 2.3.4)
I don't really understand the codes in that name, so can someone please tell me if I could flash some close to this sbf if I ever need to? I've found some with just that value after "...DFP-" different. Would they be okay?
Please let me know! I wanna load up something different, but don't want to do so until I have a full sbf as well, just in case of emergency
niksy+ said:
I'm having a hard time finding a full SBF of my stock ROM...
It's 4.5.1-134_DFP-74 (Android 2.3.4)
I don't really understand the codes in that name, so can someone please tell me if I could flash some close to this sbf if I ever need to? I've found some with just that value after "...DFP-" different. Would they be okay?
Please let me know! I wanna load up something different, but don't want to do so until I have a full sbf as well, just in case of emergency
Click to expand...
Click to collapse
You should ask Walter79. I found similar sbf as yours in his thread /forum.xda-developers.com/showthread.php?t=966537/ at "my roms" link:
www.4shared.com/folder/YpyTOtp4/Defy-roms.html
Bests
Mate, thanks for the info, but I've already found and flashed a full .sbf The topic said it was 2.3.4, while it turned out to be 2.3.5, but I don't mind, got my phone working again after a failed flashing of cm7.2..!
Cheers
hey!
I'll be getting my X5 u8800 black this monday.
it comes stock 2.2
and i have had an iphone for quite some time, so im very outdated on the android systems.
Is there a complete guide for this phone on how to root, upgrade, which roms are best etc.? I tried browsing the android development forums, but wasnt very successful in finding too good answers.
My intention anyhow is to get ICS on it(if it's working yet?) and/or possibly install other cool ROM's. Remembering fondly CM with my x10 mini, this would probably where i would start. battery improvement seems to be a must on this phone for my use, and i guess there are rom,apps etc. that are great at these tasks.
if anyone could point out where to look, or where to be reading, i'd be extremely happy.
This is the best topic there is about ICS in huawei U8800:
http://forum.xda-developers.com/showthread.php?t=1492957
Little guide for rooting and installing CWM recovery:
http://forum.xda-developers.com/showthread.php?t=1420728
Good backup mirror from the fellow user R4DK0:
http://forum.xda-developers.com/showthread.php?t=1546883
I have latest version of Aurora ICS (2.02) and everything I need for phone is working, but as we all can read from the dzos topic there still are some bugs.
is there a working guide for the 2.2?i need to get a new sd card before upgrading to 2.3, but i would like to root it now anyhow
i tried the guide for 2.3. and superoneclick claims it to be working, but no SU command pops as one would expect. it does not show in root check, root explorer and other root checking devices either...
erkkiboy83 said:
is there a working guide for the 2.2?i need to get a new sd card before upgrading to 2.3, but i would like to root it now anyhow
i tried the guide for 2.3. and superoneclick claims it to be working, but no SU command pops as one would expect. it does not show in root check, root explorer and other root checking devices either...
Click to expand...
Click to collapse
Did you follow exactly the specified steps?
Maybe you didnt enable log? or maybe you enabled the usb cable to the PC?
I am only asking cause you might have slipped a step and noone else had any problem using this guide
http://forum.xda-developers.com/show....php?t=1420728
didnt work with superoneclick, but managed to root it with superboot from modaco
So,
I followed the guides for rooting, installing cmrecovery, and installing aurora.
stuck on aurora bootscreen now...for about 20 minutes...what to do!
erkkiboy83 said:
So,
I followed the guides for rooting, installing cmrecovery, and installing aurora.
stuck on aurora bootscreen now...for about 20 minutes...what to do!
Click to expand...
Click to collapse
Did you wipe data/factory reset, cache partition and dalvik(this one is in advanced subfolder) before installing aurora.zip?
All of these should be wiped in first time. When you upgrade 2.0x to the newer version then only cache and dalvik needs to be wiped.
It's imperative that you upgrade to the official 2.3 version from Huawei before installing any ROM based on the 2.6.35 Linux kernel. Note that there are several 2.3 updates due to severe bugs in the earlier ones. Also note that only some of them come with an unlocked bootloader. You'll make your own life easier if you get one of those, as you won't have to root the system first then (in fact, you don't need to root 2.2 before installing CWM on it), only enter the pink screen and copy CWM over. As far as I know, the B518 update is the latest you should install. Get it from R4DK0's mirror: http://qrac.zapto.org/Stock%20ROMs/U8800V100R001C00B518G001%20(Beta1.0)(Overseas%20Normal)(Gingerbread).zip
Install that (copy dload folder to SD card, turn off phone, hold volume up+down + power), then download one of the 2.3 CWM recoveries, 5.0.2.7 or 5.5, and install that. Now you can flash any 2.6.35 based ROM, including Aurora.
So I am new to the whole Root and ROM Android arena. And I came up with a few questions that hopefully you guys can help me with.
1. I read people saying they lost their ROOT after an update from 4.1 to 4.2 or 4.2.1 to 4.2.2? How did this happen for them?
Do you have to Un-root and flash to stock before updating to a different build (Such as 4.1 to 4.2 or 4.2.1 to 4.2.2)?
2. Right now I am using a custom ROM on Android Version 4.2.2.... if a new Custom ROM with a new android version released (Let's say 4.2.3) can I flash from one Rom to the other with just wiping Cache/Factory wipe and Dalvik Cahce or is there something else I would need to do because of the Android version update?
Sorry those two questions above are very similar but I wanted to ask them both ways.
3. If I were to get bored of the Custom ROM I am currently on. Are there any Best Practices "rules" I should know about when switching from one custom ROM to another?
4. Last if I am on a custom ROM with a nightly build..... is it more common to update to every nightly build that releases? Or is it more common people to only pick and choose choice nightly build versions. And if people do update to every new Nightly build.... can you update too much and destroy your device?
Sorry guys I know these seem like very basic questions..... and Yes I did search the forums. However while I found some very basic answers nothing went into great depth in explanation. All the answers seemed to be very vague.
does anyone have some suggestions on where to find these answers?
1. If you are on stock, rooted, and you update versions of the OS, you are essentially UPDATING the /system partition. That is how you lose 'root' when upgrading. If you modify any system files while rooted, you have to either revert to stock or change those modified files back to the original before running the update.
2. Just run FACTORY RESET in your custom recovery and flash the new custom rom. No need to wipe any caches (/cache is wiped during a factory reset anyway). It doesnt matter what version to what version. Sometimes new versions might require new bootloaders, but you will be bombarded with that information here if that becomes the case.
3. See number 2. Its the same thing. backup your apps with Titanium Backup, do a Factory Reset in custom recovery and flash new rom....done.
4. doesnt matter. you can update as much or as little as you like. some people prefer stability over new shiny, but then others are just crack-flashers....and will literally flash ANYTHING posted to see what happens
Pirateghost said:
1. If you are on stock, rooted, and you update versions of the OS, you are essentially UPDATING the /system partition. That is how you lose 'root' when upgrading. If you modify any system files while rooted, you have to either revert to stock or change those modified files back to the original before running the update.
2. Just run FACTORY RESET in your custom recovery and flash the new custom rom. No need to wipe any caches (/cache is wiped during a factory reset anyway). It doesnt matter what version to what version. Sometimes new versions might require new bootloaders, but you will be bombarded with that information here if that becomes the case.
3. See number 2. Its the same thing. backup your apps with Titanium Backup, do a Factory Reset in custom recovery and flash new rom....done.
4. doesnt matter. you can update as much or as little as you like. some people prefer stability over new shiny, but then others are just crack-flashers....and will literally flash ANYTHING posted to see what happens
Click to expand...
Click to collapse
Thanks I really appreciate the response. :good: You'd be surprised how many "Tiny Parts" of answers you get from searching. Very rarely the whole answer you need.
I am glade to hear that Question 2 only requires you to just factory rest. From the misinformation gathered on other forums... I was starting to think you had to flash back to stock before updating to another Custom ROM Build.
@20mmrain
You've probably looked at a number of posts by confused newbs. For better or worse, this site is nothing like a moderated wiki, so you find treasure mixed in with trash.
Rooters fall into four broad classes:
(a) Those that "root & modify" stock ROMs
(b) Those that abandon stock and use custom ROMs and kernels
For each of the above cases, there are diligent and careful users who make full (nandroid) backups... and lazy idiots who do not. It is almost always the lazy idiots you observe coming in here in a panic, independent of whether they are in class (a) or (b).
Beyond that, newbs taking approach (a) seem to perpetually labor under the false impression that their modified versions of a stock ROM should be able to be upgraded by the OTA process - when in fact that there is absolutely no reason to believe that. The OTAs carefully check hundreds of different files before they perform any changes; if even a single one of them has been altered, the OTA aborts without making any changes.
It is *possible* that if none of those hundreds of files are changed that an OTA will succeed on a "nearly stock" ROM. When this happens though, it is quite typical that:
- the "su" binary (part of a root kit) in either /system/bin or /system/xbin gets its' setuid permissions reset by a recursive permission-setting command in the OTA
- the custom recovery can possibly be overwritten by the new stock recovery.
Folks tend to refer to either of the above as "losing root". True in principle, but they are trivially fixed up - if the user actually understands how Android rooting works. (With fastboot, you simply reflash the custom recovery, boot into that and reflash the same root kit originally used).
It's too bad that folks who put together rooting guides seem to neglect putting an emphasis on making backups. They give you both security and freedom.
Bottom line: whatever you choose to do, make nandroid backups. You don't need to keep them all on the tablet - but for convenience reasons, you should have at least one known good ROM as a backup available to be restored.
good luck
Wow that is a really in-depth explanation and that is exactly what was looking for! Since I have been working in the IT world for years I will say with pride that I am an individual who believes in safety first and always back up any important project I am working on! So I am happy to hear I made the right decision there.
I guess a great deal of my questions also stem from working in a windows based world for so long ....that I am still learning Linux/android.
Right now I do keep a nandroid backup on my nexus 7 but only one. How backups do you have? And do you just keep the rest on a thumb drive?
Sent from my Nexus 7 using xda app-developers app
20mmrain said:
Right now I do keep a nandroid backup on my nexus 7 but only one. How backups do you have? And do you just keep the rest on a thumb drive?
Click to expand...
Click to collapse
At the moment I have 6 on the tablet - all generated in the last 60 days. Two in the last two days (one a rooted stock/jdq39, another a cm10.1 nightly). Plus recent TiBu market app & data backups. 32 GB model, so I have plenty of room.
That doesn't reflect any particular strategy or goal. I hook it up to a PC every once in a while and at that time either copy off any backups worth saving or delete them. Most of the those I have on the PC will eventually be deleted as well without ever being used. You could use a USB key if you want to. Really you only need to keep one on the tablet - mostly as a convenience in case you wedge your daily driver ROM with some random mod: you can restore a working ROM right from your tablet rather than having to find a USB key or return to your PC to get the tablet booting again.
There is one type of ROM backup that I think is very useful to keep a permanent copy of - a pure stock ROM. The reason for that is that any radio images (tilapia) or bootloader upgrades that are *sometimes* delivered by OTA can be trivially installed by:
- make a backup of the current ROM
- restore a pure stock ROM backup (including the stock recovery! ***)
- take the OTA
- ***soft-boot a custom recovery and make a backup of the NEW stock ROM (including its' recovery!)
- hard-flash the custom recovery to the tablet
- restore the backup from the first step above.
Doing things this way is the safest possible way to install either a bootloader or a radio image. Not only that, but for folks that prefer to mod stock ROMs, it gives them a backup archive of /system to recover arbitrary (stock) files from.
*** soft-booting a recovery is the most convenient way to capture a stock recovery as part of a nandroid backup. I.E.
Code:
fastboot boot recoveryimagefile.img
If you hard-flash a custom recovery before you make a nandroid backup of a stock ROM, you lose the opportunity to get a copy of the stock recovery along with the rest of the stock ROM.
good luck