Database Info

Please assist -- how to install CWM?

Hi guys. I've got a Samsung Mesmerize and I'd like some assistance getting CWM on my phone so I can properly flash kernels and such. I know next to nothing.
Currently, I am using the stock EC10 ROM with stock recovery. It was simple enough to get, I followed some instructions for adb and did the "adb reboot download" command with my phone to put it in download mode and then used Odin to flash the ROM. This is literally the extent of my knowledge.
I began wanting a new kernel because of the speed and battery life improvements, among other things, that seem to accompany custom kernels. All the instructions I found for flashing them involved CWM, which of course I do not have.
Finally I found an app on the market called "sgs kernel flasher" which claimed to be a very easy way to flash new kernels without using CWM. So I installed it and used it to make a backup of my current kernel, and then I flashed jt1134's 0327-2 kernel which I got from here. All went well.
And that is the state I am at now. I am using the stock EC10 ROM with stock recovery (which I've never used nor do I know how) that I flashed with Odin, and I am using jt1134's 0327-2 kernel that I flashed with sgs kernel flasher.
Now though I believe it would be a very good idea for me to get CWM as it seems to be what is used if something goes wrong with the phone. I have the Voodoo Control app that I got from the market and it states the lagfix is active and has options which I believe enable and disable the lagfix.
From the current state my phone is in, can anybody tell me what I need to do in order to get the latest version of CWM working on my phone? Many thanks in advance and sorry for not knowing what I'm doing!

This Thread. It's only the very first sticky...

AndroidTipster said:
This Thread. It's only the very first sticky...
Click to expand...
Click to collapse
Thanks, I saw that except I literally don't know what I am doing, and I can not find anywhere in that thread that says HOW to install CWM. I get the impression that these threads are written for people who have at least some basic understanding of how this stuff works, which sadly I do not...
And also how do I disable the lagfix to flash things if I don't have cwm? Can it be disabled with voodoo control?

userno69 said:
Thanks, I saw that except I literally don't know what I am doing, and I can not find anywhere in that thread that says HOW to install CWM. I get the impression that these threads are written for people who have at least some basic understanding of how this stuff works, which sadly I do not...
And also how do I disable the lagfix to flash things if I don't have cwm? Can it be disabled with voodoo control?
Click to expand...
Click to collapse
In your voodoo control you can disable it by unchecking the boxes and rebooting. You should hear the lagfix lady when rebooting.
For CWM I actually flashed it with Odin. this thread Will help you in the easiest way possible.

AndroidTipster said:
In your voodoo control you can disable it by unchecking the boxes and rebooting. You should hear the lagfix lady when rebooting.
For CWM I actually flashed it with Odin. this thread Will help you in the easiest way possible.
Click to expand...
Click to collapse
Ah, so if I understand correctly, the process to get CWM is to disable the lagfix in the Voodoo Control application, and reboot the phone. Then put it in debug mode and connect to my PC and use ADB to put it in download mode, and finally use Odin to flash the CWM tar file? Is there anything special I need to do in Odin, like enable certain anything or check any specific boxes?

In Odin, do I flash the tar file in the PIT, PDA, PHONE or CSC field?

To put your phone in Download Mode all you have to do is take the battery out and hold the Volume Down button while plugging your phone up to your computer via USB (yes without the battery in it). There's no need to fool with adb
No offense but this is the exact kind of thing I don't understand. When everyone else in the world follows standard procedure of ODIN'ing the stock ROM with CWM to then be able to flash kernels and all that, why don't you? Every single time a question like this arsises is because someone tried to go out and not do what everybody else does and try to go approach things in some roundabout way.
Lesson for the future and for others - Just follow the instructions and what not in the forums. If you start skipping steps or trying to create your own avenue of accomplishing something you're just going to run into trouble.
For instance
userno69 said:
All the instructions I found for flashing them involved CWM, which of course I do not have.
Click to expand...
Click to collapse
That should've been a hint right there. If they all have instructions that involve CWM, well then **** man, clearly you should get CWM.
Not trying to haze your nuts, just using you as an example for other.
Sent from my SCH-I500 using XDA App

add144 said:
To put your phone in Download Mode all you have to do is take the battery out and hold the Volume Down button while plugging your phone up to your computer via USB (yes without the battery in it). There's no need to fool with adb
Click to expand...
Click to collapse
Thanks. Alright... I flashed the CWM package with Odin and it was successful. Do I have CWM recovery now? I held volume up/down and powered on the phone and it went into a red menu that appears to be CWM and has options for voodoo and such.
I take it this means I was successful? I read somewhere that to finish the installation, I need to flash sdcard/update.zip from recovery, and I do see the option to do that in the red menu. But I'm confused, because it looks like I already have CWM now? Also, in my file manager I do not see a file called update.zip in the /sdcard location, or anywhere. Am I done? Why is that option in CWM if there is no update.zip file (apparently)?
So if I do now have CWM, how do I flash a kernel with it? Appreciate the help, I am learning here.
EDIT:
I know I didn't do this correctly from the start, but that was because in the beginning I was only looking to upgrade to Froyo and keep everything else stock, then I got interested in doing more...

The red recovery menus are CWM.
To flash a new kernel just download it onto your SD card. Then in CWM select, Install zip from SD Card. Then select Choose zip From SD Card and select the kernel.

add144 said:
The red recovery menus are CWM.
To flash a new kernel just download it onto your SD card. Then in CWM choose, Install Update.zip from SD Card. Then choose Select .zip From SD Card and select the kernel.
Click to expand...
Click to collapse
Thanks! Do I actually need to name the kernel file "update.zip" or is that just the arbitrary name of the menu option?

No, sorry couldn't remember exactly the way CWM worded it. It doesn't doesn't have to be update.zip, it can be named anything.zip. It'll take you to navigation type menu where you can move in and out of folders on your SD card and select the appropriate file.

[Q] Pre-rooting procedure?

I'm running stock EE4 but I'm getting ready to root and install one of the debloated ROMs. Currently I have a lot of apps, home screens and ADW Launcher set to my satisfaction and settings tweaked how I like them.
What are "best practices" for pre-rooting backup so all of these are retrievable? I've used Titanium Pro on my tablet so I'm conversant with that process but don't I have to be rooted first? Should I root the phone, install TP, back-up and THEN flash the ROM? Are there alternatives?
Thanks, I await advice.

adw settings you can backup by going to adw settings and doing a backup. Not sure if there is an unrooted version of titanium. Bad part is. You cannot just root if you are EE4 already. 1click and Gingerbreak do not work on EE4. You have to Odin flash a rooted rom. Sorry. Know thats not what you wanted to hear.

dragonstalker said:
adw settings you can backup by going to adw settings and doing a backup. Not sure if there is an unrooted version of titanium. Bad part is. You cannot just root if you are EE4 already. 1click and Gingerbreak do not work on EE4. You have to Odin flash a rooted rom. Sorry. Know thats not what you wanted to hear.
Click to expand...
Click to collapse
Not true. You simply need to use Odin to flash a new kernel which is rooted (pbj by immuts for example). Once you've done this you'll also get CWM. You need to find an Odin package that only contains the kernel.
Once you've done that, with root you can use TiBackup like you've done before and then flash your ROM.

Thanks, fellas. If you're monitoring this thread, would you mind having a look over here?

keithce said:
Not true. You simply need to use Odin to flash a new kernel which is rooted (pbj by immuts for example). Once you've done this you'll also get CWM. You need to find an Odin package that only contains the kernel.
Once you've done that, with root you can use TiBackup like you've done before and then flash your ROM.
Click to expand...
Click to collapse
OK SO, ROOTED means that the ROM has SU capability which is given to it by superuser app. Which allows you to have admin capabilities to change permissions to your filesystem.
The kernel allows you to overclock and undervolt your system while giving access to other HARDWARE specific functions.
Now please explain to me how a KERNEL can give you SuperUser permission to the filesystem if the KERNEL is a bridge between the Hardware and Software. Not saying your wrong, I just don't see how a Kernel can give you root access.

dragonstalker said:
OK SO, ROOTED means that the ROM has SU capability which is given to it by superuser app. Which allows you to have admin capabilities to change permissions to your filesystem.
The kernel allows you to overclock and undervolt your system while giving access to other HARDWARE specific functions.
Now please explain to me how a KERNEL can give you SuperUser permission to the filesystem if the KERNEL is a bridge between the Hardware and Software. Not saying your wrong, I just don't see how a Kernel can give you root access.
Click to expand...
Click to collapse
Indeed, strictly technically speaking you are correct. However after the radio on the charge got updated to EE4 the usual 'back doors' or exploits to get root no longer worked.
Therefore the developers of the kernels for the charge built in the capability to auto root when it boots and hands off the hardware to the software.
If you read the posts for the kernels (e.g. http://forum.xda-developers.com/showthread.php?t=1104634) you would see that.
Cheers!

I stand corrected. It's right there in black and white. Auto-Root on Boot.
We learn something new everyday. Thanks for getting me brought up to speed.

keithce said:
Not true. You simply need to use Odin to flash a new kernel which is rooted (pbj by immuts for example). Once you've done this you'll also get CWM. You need to find an Odin package that only contains the kernel.
Once you've done that, with root you can use TiBackup like you've done before and then flash your ROM.
Click to expand...
Click to collapse
Is flashing a custom kernel, like PBJ, easily done using Odin? Do I use the same procedure when flashing CWM?
The latest version of CWM is not working--the button mapping is all screwed up. So I can't install any .zip files from my SD card -- I just keep seeing this f***ing blue banana.
So do I already need to have CWM installed to install a custom kernel? I'm waiting for someone to post CWM 4.0.0.8 until danalo is able to fix the faulty CWM currently linked for downloading
---Thank you for any help you may provide---

MrMakeIt said:
Is flashing a custom kernel, like PBJ, easily done using Odin? Do I use the same procedure when flashing CWM?
The latest version of CWM is not working--the button mapping is all screwed up. So I can't install any .zip files from my SD card -- I just keep seeing this f***ing blue banana.
So do I already need to have CWM installed to install a custom kernel? I'm waiting for someone to post CWM 4.0.0.8 until danalo is able to fix the faulty CWM currently linked for downloading
---Thank you for any help you may provide---
Click to expand...
Click to collapse
Flashing anything in Odin uses an almost identical procedure unless you're trying to also upgrade the baseband/radio/modem.
Yes, you can flash a kernel using Odin. You just have to make sure that you download the right file to be flashed because it must be in specific format (*.md5).
Here is a link to jt's kernel from this post. Its a root kernel with CWM and also includes the lagfix (reformat to EXT4) that you should be able to flash using Odin.
That should give you a working (although limited functionality) version of CWM so that you can then install everything else and upgrade when a newer working version of CWM comes out.
Basically you just need to get CWM on there once as a starting point and then you can upgrade, update, and do whatever you want from there.

[Q] DEAR GOD please help. Rooting, changing OS, Downloading ROM.

Ok I have been at this for a few hours. I have upgraded the original Samsung Infuse 4G HD's firmware to gingerbread version something or other but it is a leaked release. Sooo now I'd like to root the phone and put a ROM on it. I downloaded everything I believe I need. (Again I have been at this for awhile) I have SOC and KiesMini as well as full Kies. I have downloaded Titanium Backup, ROM manager, and Superuser to the phone. I went to do a root on SOC and it will get to step 6 and freeze. I've read a few things and gathered that I need to download the drivers for the phone again and restart root process. Well it's been and hour and a half and I can find the damn drivers anywhere on the web. I have repeatedly unplugged and replugged the phone to the computer and let it download the drivers. Kies and KiesMini both are unable to connect to the phone. Scratch that Mini connects but doesn't recognize the device, my guess is that it does not have the original firmware on it, then again I don't see how this would stop the program from recognizing the phone itself seeing as though this was just a firmware update. I'm semi new to this so I wouldn't be surprised if I was wrong.
Please if you have a full guide or step by step instructions or just know where the hell to get the drivers online I'd be very appreciative.
Also if this is the wrong thread section, let me know I'll be happy to move it. I believe I am in the right place though.
Thank you,

If I understand correctly, you already rooted your phone once. Then flashed one of the gingerbread leaks and lost root?
I don't think any of the normal root methods will work. I believe you need to flash a certain kernel to get root back.
Or just use GTGs method to get back to stock. Then normal root methods will work.

if all else fails try superoneclick. thats what i used. and once you get it rooted again flash the MIUI mod to your phone. its a great ROM, i highky recommend it. anyways i agree with the guy above. you may need to find a way to flash a different kernal. let us know how it goes.

Imo, i would flash back to stock with with GTG's unbrick... Either flash community kernel to get red CWM or do SOC to get root, download CWM Rom Manager from market and flash CWM Recovery thru there, make sure to choose "Galaxy s i9000" and NOT the MTD. Do it twice just in case or thrice for sure. You should be able flash any ROM through there or reboot to recovery. This has worked for me multiple times. Good luck.
Here is a link from @misterjunky in the wiki thread for the usb drivers:
http://forum.xda-developers.com/showthread.php?p=18138847
Sent from my SGH-I997 using xda premium

I would suggest using GTG's back to stock package, then re-root, flash the leak (if you still want it), and flash Entropy's DD for root, then flash back to the stock kernel.
Reply if you need any help with this, I'll try to reply during school, if I don't, someone else will, or I will after school.

If you need root with gb I assume you flashed a stock kernel. The board elders have stated you can't root gb through superoneclick. That hack was patched. You need to flash a rooted kernel and then flash back to stock if you want stock or just leave it with custom kernel. Read through the uckj2 (I think) thread in development. Linuxbozo gave perfect instructions.
Sent from my SAMSUNG-SGH-I997 using XDA App

It's good that the information is finally getting passed around. Sorry but root it's now done from the kernel end. It's the last backdoor in but Samsung makes it easy on the user end, only problem now is ya gotta wait for developers to compile kernels with initramfs mods.
what you need is.
1. Drivers, Samsung.com infuse product support section. No need for kies.
2. A kernel that roots, entropy has a good one with wifi and sd compatibility.
3. A flash tool such as Odin or heimdall and dependencies. (visual c++ redistributable package from Microsoft download center for heimdall)
4. (optional) a stock uckj2/4/ kernel if you want hdmi to work.
If you use Odin, the custom kernel that will root you needs to be in a ".tar" archive. You put it in the pda slot. After first boot you will have root and have the option to flash back to a kernel with hdmi. once rooted this can be done with sgs kernel flasher if you can't find the .tar version of the stock kernel, you can extract the zimage from the original Odin package and zip it or .rar it and put it on the sd card to be flashed in kernel flasher.
If you use heimdall (my personal preference) you will extract the zimage out of what ever archive it is in. it may be .zip .tar .rar it can even be cwm flashable. You open the tab labeled "flash" load the infuse.pit that gtg made (found with the unbrick package) then click the "add" button select "kernel" for the partition and then browse for the zimage for the root kernel.
Same process to go back to the hdmi kernel for heimdall. Or you can use kernel flasher like I explained above.
No need to go back to stock or wipe data for kernel flashing. That's just overkill and a waist of time.

Dani897 said:
It's good that the information is finally getting passed around. Sorry but root it's now done from the kernel end. It's the last backdoor in but Samsung makes it easy on the user end, only problem now is ya gotta wait for developers to compile kernels with initramfs mods.
what you need is.
1. Drivers, Samsung.com infuse product support section. No need for kies.
2. A kernel that roots, entropy has a good one with wifi and sd compatibility.
3. A flash tool such as Odin or heimdall and dependencies. (visual c++ redistributable package from Microsoft download center for heimdall)
4. (optional) a stock uckj2/4/ kernel if you want hdmi to work.
If you use Odin, the custom kernel that will root you needs to be in a ".tar" archive. You put it in the pda slot. After first boot you will have root and have the option to flash back to a kernel with hdmi. once rooted this can be done with sgs kernel flasher if you can't find the .tar version of the stock kernel, you can extract the zimage from the original Odin package and zip it or .rar it and put it on the sd card to be flashed in kernel flasher.
If you use heimdall (my personal preference) you will extract the zimage out of what ever archive it is in. it may be .zip .tar .rar it can even be cwm flashable. You open the tab labeled "flash" load the infuse.pit that gtg made (found with the unbrick package) then click the "add" button select "kernel" for the partition and then browse for the zimage for the root kernel.
Same process to go back to the hdmi kernel for heimdall. Or you can use kernel flasher like I explained above.
No need to go back to stock or wipe data for kernel flashing. That's just overkill and a waist of time.
Click to expand...
Click to collapse
Awesome instructions but I think it's worth mentioning (and maybe that's why you DIDN'T mention it actually) that you need a pit to flash anything in the front end but unless you WANT to repartition, you should make sure that check box is UNCHECKED after you select the pit.

jvanlew said:
Awesome instructions but I think it's worth mentioning (and maybe that's why you DIDN'T mention it actually) that you need a pit to flash anything in the front end but unless you WANT to repartition, you should make sure that check box is UNCHECKED after you select the pit.
Click to expand...
Click to collapse
Yeah don't repartition!. It's potential for disaster, better left for situations whet you have all the partitions to flash and the phone won't boot after trying without repartition. The pit is just for partition mapping in the new front end. I guess it's designed to work with devices that may have different partitioning as well

jvanlew said:
.... that you need a pit to flash anything in the front end....
Click to expand...
Click to collapse
Talking about heimdall? I think you can use an older version like 1.1 to get around this?
Sent from my SAMSUNG-SGH-I997 using XDA App

rxnelson said:
Talking about heimdall? I think you can use an older version like 1.1 to get around this?
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
This is true. 1.1 works great and doesn't need a pit file. It is also easier if you never used it before. It kinda explains itself.

Dani897 said:
It's good that the information is finally getting passed around. Sorry but root it's now done from the kernel end. It's the last backdoor in but Samsung makes it easy on the user end, only problem now is ya gotta wait for developers to compile kernels with initramfs mods.
what you need is.
1. Drivers, Samsung.com infuse product support section. No need for kies.
2. A kernel that roots, entropy has a good one with wifi and sd compatibility.
3. A flash tool such as Odin or heimdall and dependencies. (visual c++ redistributable package from Microsoft download center for heimdall)
4. (optional) a stock uckj2/4/ kernel if you want hdmi to work.
If you use Odin, the custom kernel that will root you needs to be in a ".tar" archive. You put it in the pda slot. After first boot you will have root and have the option to flash back to a kernel with hdmi. once rooted this can be done with sgs kernel flasher if you can't find the .tar version of the stock kernel, you can extract the zimage from the original Odin package and zip it or .rar it and put it on the sd card to be flashed in kernel flasher.
If you use heimdall (my personal preference) you will extract the zimage out of what ever archive it is in. it may be .zip .tar .rar it can even be cwm flashable. You open the tab labeled "flash" load the infuse.pit that gtg made (found with the unbrick package) then click the "add" button select "kernel" for the partition and then browse for the zimage for the root kernel.
Same process to go back to the hdmi kernel for heimdall. Or you can use kernel flasher like I explained above.
No need to go back to stock or wipe data for kernel flashing. That's just overkill and a waist of time.
Click to expand...
Click to collapse
Sorry I haven't responded until now, I've been incredibly busy. Anywho, so I went ahead and flashed back to stock. So now it is exactly how it should be when I bought it. I run SOC and it gets to running pneuter and stops. I've waited an hour on it and it won't continue. Any suggestions?

Hi
I am using unrooted Infuse phone. Recently i have updated it to official gingerbread UCKL2 through samsung Kies mini.
I want to try ZEUS ROM on samsung infuse. Please let me know how to start in detail as I am new on Linux.
Thanks
Nits

ndhanta said:
Hi
I am using unrooted Infuse phone. Recently i have updated it to official gingerbread UCKL2 through samsung Kies mini.
I want to try ZEUS ROM on samsung infuse. Please let me know how to start in detail as I am new on Linux.
Thanks
Nits
Click to expand...
Click to collapse
That's the ROM i'm trying to get on mine as well, I just cant get the damn phone to root.

I posted a reply in the other thread

[Q][HELP]: captivate stuck at boot after clockworkmod install

Hi all, hope you can help. I installed clockworkmod recovery onto my wife's captivate, and now it won't boot - it's stuck at the "galaxy-S" screen.....I can get it into the YELLOW TRIANGLE screen and once managed to get it into the clockworkmod menu screen.
I believe the phone has android 2.3, not 2.2 on it and this might have been my mistake. The entry point into the kernel is likely different...
how can i fix this? do i need to remove clockworkmod and go back to the stock bootloader? The phone is not rooted, yet (that was the next step).
I haven't been able to find anything in the forums about people that have done (the stupid thing that I did) and installed clockworkmod on a 2.3 phone.
Thanks.

How exactly did you flash cwm? You shouldn't even be able to cause if 3e recovery signature verification?

If you can get to the yellow android screen, that's download mode. You're actually in a good place right now.
To fix where you are, take a look at the development section - there's a post about One-click stock packages. If you're sure she was on Gingerbread, grab one of the non-bootloader Gingerbread stock packages and flash that from download mode.
If you're not sure, I would suggest grabbing one of the Gingerbread stock packages with bootloaders (just to make sure).
In either case, see if you can find a one-click package with ClockworkMod Recovery baked into the kernel (it should say on the post which ones have it). That way you can flash what you want right out of the gate.

thanks. i am quite sure it has gingerbread. the person i bought it from said they did a kies update to 2.3.
i was following the instructions from the cyanogenmod wiki for the captivate: hxxp://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide
after it finished installing the "clockworkmod recovery" i got into this bind. are those instructions for froyo only?

If you followed the instructions about flashing the speedmod kernel, that's where it's hanging. You've got a froyo kernel with a GB rom. Not a big deal, but Android isn't happy about it. Flash a stock GB package, or find a GB kernel with CWM (like boog's) and flash that and you should be ok.

thanks. do i do this using ODIN or heimdall? I installed CWM using heimdall, and in my frantic reading i thought i saw something about installing stock bootloader/rom packages with ODIN after installing CWM could brick it? Or did I misread that?

dolhop said:
thanks. do i do this using ODIN or heimdall? I installed CWM using heimdall, and in my frantic reading i thought i saw something about installing stock bootloader/rom packages with ODIN after installing CWM could brick it? Or did I misread that?
Click to expand...
Click to collapse
Using heimdall is fine (it's also my personal preference between the two, but either will work).
With where you're at, you really shouldn't need to flash any bootloaders. That's pretty much the only area where there is a real risk of hard bricking the phone.
Since Heimdall worked for you once, I'd suggest grabbing the Heimdall one-click I made that's in my signature. You don't need to open it in Heimdall - just download, double-click it, and let it get ready to run. Then connect the phone in download mode and click "flash". You'll have the stock GB rom, with Boog's kernel and CWM all ready to go. You can then flash CM7 from recovery there (you'll probably have to flash it twice, though).
On a side note - flashing stock will wipe your apps. I'm assuming you backed everything up before this. If not, you might need to try and just flash a kernel first, do your backups, then go from there.
(Should you want to do that, go here, grab the one from the "Here is the odin flashable version flash it first if your on stock: Link Mirror" set of links, and then flash that in Heimdall.)

wow, thanks guys, i can breathe easier now. jmtheiss, i got it reflashed to UCKH3 using your one-click package (though now it is AT&T rather than rogers, but i really don't care as long as it works!).
does the one-click root application work with 2.3.4? or is there a more-preferred way to root it now?
Again, thanks so much for the assistance people!

In theory, you should already be rooted (I believe boog's kernel, which was in my one-click, is rooted). If not, go to the bottom of boog's 1st post, and grab the KH3 zip file. Flash that in CWM, and you'll have root permissions.
Or, if you're flashing to CM7, you can just do it from recovery as you are right now. I know from personal experience it works.

thanks everyone. it all worked, and all is good. wife is not an angrybird anymore

dolhop said:
thanks everyone. it all worked, and all is good. wife is not an angrybird anymore
Click to expand...
Click to collapse
Glad to hear that she's not flying over your house shooting explosive eggs. Always a turn for the better.

Had the same problem once before, odin fixed it aswell

[Q] a little help

ive been rooted for a long time now, i have a Moto Attrix 2. recently i did the updated to the 2.3.6 but before i did, i went ahead and did the perminent root method. this helped me keep root. now i want to jump into Roms. i'm not new to this. i had a Droid X proir to the Attrix. so i kinda know my way around. sorta..aha, ive read the process of the rom i want to install on to my phone which is supercharge Rom

So do you have a question, I couldn't tell from your post

awe man, i'm sorry about that.
my question...actually the question is about the process needed to be taken. i read thru the steps to flash supercharge rom V5 but, i have no clue to where start from since i have not flash a rom on this device.? so i'm startin off from scretch i'm sorry about that, i shoulda proof read that..lol, before i posted.

Step 1)Install CW recovery from this link http://forum.xda-developers.com/showthread.php?t=1346977
Step 2) Run it and reboot into recovery
Step 3) MAKE A BACKUP! I repeat MAKE A BACKUP! this is important in case something goes wrong while flashing a new rom you can flash your backup and return your phone to normal.
Once you have learned to do that you can now start flashing roms. Just download the roms and follow the directions in the roms. ALL ROMS REQUIRE CW Recovery to install so you'll get used to it. I just wanted u to follow those 3 steps before you start flashing roms. People forget to make backups and they end up losing all their info.
Read the BEGINNERS GUIDE it has all the info you could ever need.

eL_MeXiCaNo said:
Step 1)Install CW recovery from this link http://forum.xda-developers.com/showthread.php?t=1346977
Step 2) Run it and reboot into recovery
Step 3) MAKE A BACKUP! I repeat MAKE A BACKUP! this is important in case something goes wrong while flashing a new rom you can flash your backup and return your phone to normal.
Once you have learned to do that you can now start flashing roms. Just download the roms and follow the directions in the roms. ALL ROMS REQUIRE CW Recovery to install so you'll get used to it. I just wanted u to follow those 3 steps before you start flashing roms. People forget to make backups and they end up losing all their info.
Read the BEGINNERS GUIDE it has all the info you could ever need.
Click to expand...
Click to collapse
thanks bro, i got that part down, ive been rollin around with a back up for weeks now ..
oh yea and the other thing, when i went and did the forever root before the OTA update, the one thing that didn't update was the baseband.

Droid_Boi86 said:
thanks bro, i got that part down, ive been rollin around with a back up for weeks now ..
oh yea and the other thing, when i went and did the forever root before the OTA update, the one thing that didn't update was the baseband.
Click to expand...
Click to collapse
Dont worry about ever doing the forever root there's a root method for 2.3.6
Before flashing any rom I suggest you flash the 2.3.5 FXZ and update to 2.3.6 and then root it. This way you start from a fresh base and don't have any random bugs that would take a long time to hunt down and fix due to coming from a non-stock rom.

Ask away. What questions do you have? I recommend installing CWM on Recovery zip (and download the remove script while your at it you might want that). Revoke root rights to Bootstrap after installing the on boot zip. It takes one cycled reboot for the script to take effect. Make sure it works before installing any ROMs. Read the Read Me file for supercharged before installing. That's a few tips from me. Oh, if you have a windows based PC install and know how to use RSD lite and the fxz file in case of a disaster. In other words incase you can't recover from some unforeseen event using your phone and CWM Recovery alone. Make sure your battery is fully charged before installing a new ROM. Off the top of my head those tips come to mind.
Sent from my MB865 using XDA

KEB64 said:
Ask away. What questions do you have? I recommend installing CWM on Recovery zip (and download the remove script while your at it you might want that). Revoke root rights to Bootstrap after installing the on boot zip. It takes one cycled reboot for the script to take effect. Make sure it works before installing any ROMs. Read the Read Me file for supercharged before installing. That's a few tips from me. Oh, if you have a windows based PC install and know how to use RSD lite and the fxz file in case of a disaster. In other words incase you can't recover from some unforeseen event using your phone and CWM Recovery alone. Make sure your battery is fully charged before installing a new ROM. Off the top of my head those tips come to mind.
Sent from my MB865 using XDA
Click to expand...
Click to collapse
whats the reason for denying bootstrap su? ive seen this before and im a 3year android user/flasher and ive yet to deny my bootstrap su after installing anything. so, just wondering why.

rob219 said:
whats the reason for denying bootstrap su? ive seen this before and im a 3year android user/flasher and ive yet to deny my bootstrap su after installing anything. so, just wondering why.
Click to expand...
Click to collapse
Because if you dont deny bootstrap SU after FLASHING CWM ON STARTUP zip then you will not get CWM everytime you boot up, it's a bug. So if you want CWM everytime you boot your phone you have to deny bootstrap SU. Other than that IDK the exact technical details on why it does this, it just does.

KEB64 said:
Ask away. What questions do you have? I recommend installing CWM on Recovery zip (and download the remove script while your at it you might want that). Revoke root rights to Bootstrap after installing the on boot zip. It takes one cycled reboot for the script to take effect. Make sure it works before installing any ROMs. Read the Read Me file for supercharged before installing. That's a few tips from me. Oh, if you have a windows based PC install and know how to use RSD lite and the fxz file in case of a disaster. In other words incase you can't recover from some unforeseen event using your phone and CWM Recovery alone. Make sure your battery is fully charged before installing a new ROM. Off the top of my head those tips come to mind.
Sent from my MB865 using XDA
Click to expand...
Click to collapse
thanks alot man, as far as the RSD lite goes i kno my way aroung that. so i should be good. but as for the first thing you suggested. about the CVM on Recovery Zip? i wanna learn how to do that, meaning install CVM properly. if you could explain or shot me a link to where i read up on it.

Droid_Boi86 said:
thanks alot man, as far as the RSD lite goes i kno my way aroung that. so i should be good. but as for the first thing you suggested. about the CVM on Recovery Zip? i wanna learn how to do that, meaning install CVM properly. if you could explain or shot me a link to where i read up on it.
Click to expand...
Click to collapse
Sorry KEB - not to step on your toes or anything, but...
Get and install the A2 Bootstrap from here.
You can now boot into "Recovery" mode through the Bootstrap app. You can test it first or you can just go and get the CWM on Boot zip files here. Download the two zip attachments in the first post to your sdcard.
Then open the A2 Bootstapper app - click the top button, then ok, then the 2nd button.. and viola! It will boot into recovery.
Then wipe your cache partition, and dalvik cache, and install zip from sdcard. "...Global..." zip makes it boot into recovery every time you reboot, and the "..Remove.." zip removes it.
Good luck. Happy reading!

alteredlikeness said:
Sorry KEB - not to step on your toes or anything, but...
Get the A2 Bootstrap from here.
Get ROM Manager from the Google Play Store.
Install both.
You can now boot into "Recovery" mode through the Bootstrap app. You can test it first or you can just go and get the CWM on Boot zip files here. Download the two zip attachments in the first post to your sdcard.
Then open the A2 Bootstapper app - click the top button, then ok, then the 2nd button.. and viola! It will boot into recovery.
Then wipe your cache partition, and dalvik cache, and install zip from sdcard. "...Global..." zip makes it boot into recovery every time you reboot, and the "..Remove.." zip removes it.
Good luck. Happy reading!
Click to expand...
Click to collapse
thanks for that good explaination on that. now i gotta figure out why my laptop isn't seeing my phone...=/

Droid_Boi86 said:
thanks for that good explaination on that. now i gotta figure out why my laptop isn't seeing my phone...=/
Click to expand...
Click to collapse
Make sure you have the drivers downloaded for the Atrix 2.

thethird84 said:
Make sure you have the drivers downloaded for the Atrix 2.
Click to expand...
Click to collapse
By "seeing your phone," do you mean ADB-wise? Settings -> Applications -> Development -> USB Debugging (enable)

PM me if you need any help. I have Supercharged V5 update 2 running and I love it. there are some things you need to do to make sure it works right though.

thanks alot! i will do..