Database Info

CWM won't stick...Even with locked bootloader

I rooted according the directions found here: http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/ after getting a new Nexus S 4G.
Even after locking the bootloader. It goes to the Android-with-box then to the Exclaimation-point-inside triangle. When I volume-up and power-button from that screen, an "Android Recovery <3e>" comes up...
Does anyone know what might be going on? And how do I get my custom recovery to stick?

Well, that's my post, so ill try to help. First, and don't take this the wrong way, but did you follow those instructions to a T? When you boot into bootloader, your pushing CWM to you phone with the fastboot command?
Sent from my Nexus S 4G using XDA App

mikeyinid said:
Well, that's my post, so ill try to help. First, and don't take this the wrong way, but did you follow those instructions to a T? When you boot into bootloader, your pushing CWM to you phone with the fastboot command?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...

TonyArmstrong said:
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
Click to expand...
Click to collapse
Apparently alot of people have this issue, me included. I seen some posts about using root explorer to change the name of the recovery image if it shows up in system /ext. Sounds crazy but I hear it doesn't show up on all phone's. IV come to terms with having to fastboot every time I flash but I'd love to see a fix. Have you tried Amons recovery?

TonyArmstrong said:
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
Click to expand...
Click to collapse
Have you flashed recovery through Rommanager when your phone boots up?

You have to flash a non-stock kernel, the recovery gets overwritten on reboot. So if you flash CWM and reboot without flashing a custom kernel you will be back to stock recovery.
Edit: oops maybe I was wrong lol, maybe it isnt the kernel. im assuming you flashed the recovery in fastboot?

mbh87 said:
You have to flash a non-stock kernel, the recovery gets overwritten on reboot. So if you flash CWM and reboot without flashing a custom kernel you will be back to stock recovery.
Edit: oops maybe I was wrong lol, maybe it isnt the kernel. im assuming you flashed the recovery in fastboot?
Click to expand...
Click to collapse
No, I dont think your wrong bro. It makes sense. Ill test your theory soon.

Tony, when you push CWM, are you able to boot into recovery by hitting volume down twice to recovery and hitting power? If so, I suggest you flash this ROM. Its stock rooted and you will not have problems with CWM sticking. You dont even have to wipe to flash it...

I've read on some methods for rooting that there is a file /system/etc/install-recovery.sh (or something like that, should be able to find it by mounting system in recovery and adb shell ls /system/etc then using adb shell rm -r /system/etc/install-recovery.sh).
Though after I fastboot flashed the recovery, booted into recovery, did a nandroid, I formatted /system before I flashed CM7, so that would've killed the file anyways.

david1171 said:
I've read on some methods for rooting that there is a file /system/etc/install-recovery.sh (or something like that, should be able to find it by mounting system in recovery and adb shell ls /system/etc then using adb shell rm -r /system/etc/install-recovery.sh).
Though after I fastboot flashed the recovery, booted into recovery, did a nandroid, I formatted /system before I flashed CM7, so that would've killed the file anyways.
Click to expand...
Click to collapse
I just had CWM, never had any issues. Im not sure what dictates whether that file is there or not. Im guessing that since tony is so quiet though he got it figured out..

whats amazing is i dont have this script and its one of the things holding the one click up :x
also its part of init.rc so technically a new kernel would.. in theory wipe that out...

mikeyinid said:
Have you flashed recovery through Rommanager when your phone boots up?
Click to expand...
Click to collapse
I did flash CWM through Rom Manager. That didn't work the first few times. It stalled...

mikeyinid said:
Tony, when you push CWM, are you able to boot into recovery by hitting volume down twice to recovery and hitting power? If so, I suggest you flash this ROM. Its stock rooted and you will not have problems with CWM sticking. You dont even have to wipe to flash it...
Click to expand...
Click to collapse
I got it to stick -- or at least i thought I had it. I followed the initial instructions provided in a previous thread. And per the instructions, I download Rom Manager and I installed CWM through it (again).
I'm going to wipe my phone fully -- reinstall the base 2.3.4 with the the stock recovery, via the IMG files for GRJ22 and start over...See what happens then.

Wait, I'm confused. Why would you flash stock images when your already stock? If you follow the instructions in the link you posted in the op there is no reason you shouldn't be rooted. Have you actually even booted into recovery?
TonyArmstrong said:
I got it to stick -- or at least i thought I had it. I followed the initial instructions provided in a previous thread. And per the instructions, I download Rom Manager and I installed CWM through it (again).
I'm going to wipe my phone fully -- reinstall the base 2.3.4 with the the stock recovery, via the IMG files for GRJ22 and start over...See what happens then.
Click to expand...
Click to collapse
Sent from my Nexus S 4G using XDA App

I realllyyy don't suggest flashing a recovery with rom manager. I'm not bashing ROM Manager, I'm a paid user, but the way that it flashes recoveries is unsafe. I've had it almost brick my Evo and I've seen it brick other phones.
Just use fastboot... if you can't get that working, you probably shouldn't be messing with the phone.

mikeyinid said:
Wait, I'm confused. Why would you flash stock images when your already stock? If you follow the instructions in the link you posted in the op there is no reason you shouldn't be rooted. Have you actually even booted into recovery?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I'm rooted successfully. I feel more comfortable (with recovery acting flaky) with unrooting and starting over from scratch...
Call me kooky, but a bone-stock unrooted phone with no user data, no nothing, is how I got it, so why not return it to that state and start over. That's the only way I know to insure that whatever I do is not influenced by any data, bad file permissions, etc. that could hose rooting and installing recovery.

TonyArmstrong said:
I'm rooted successfully. I feel more comfortable (with recovery acting flaky) with unrooting and starting over from scratch...
Call me kooky, but a bone-stock unrooted phone with no user data, no nothing, is how I got it, so why not return it to that state and start over. That's the only way I know to insure that whatever I do is not influenced by any data, bad file permissions, etc. that could hose rooting and installing recovery.
Click to expand...
Click to collapse
OCD, I know the feeling lol. What got it to stick?

derekwilkinson said:
I realllyyy don't suggest flashing a recovery with rom manager. I'm not bashing ROM Manager, I'm a paid user, but the way that it flashes recoveries is unsafe. I've had it almost brick my Evo and I've seen it brick other phones.
Just use fastboot... if you can't get that working, you probably shouldn't be messing with the phone.
Click to expand...
Click to collapse
I used fastboot to install CWM initially (fastboot flash recovery recovery-xxxxx.zip -- can't remember the filename right now). The directions for rooting the NS4G state explicitly to use ROM Manager to flash the recovery to "make sure it sticks" after initially pushing it to the phone via fastboot.
It's obviously a hack, but apparently it works more often than it fails.
I'm a paid user of ROM Manager as well. I have to admit, it was fine to flash Amon Ra to my Evo. Since I'm new(er) to the NS4G, I'm going to defer to those with more expertise and follow the directions given.

TonyArmstrong said:
I used fastboot to install CWM initially (fastboot flash recovery recovery-xxxxx.zip -- can't remember the filename right now). The directions for rooting the NS4G state explicitly to use ROM Manager to flash the recovery to "make sure it sticks" after initially pushing it to the phone via fastboot.
It's obviously a hack, but apparently it works more often than it fails.
I'm a paid user of ROM Manager as well. I have to admit, it was fine to flash Amon Ra to my Evo. Since I'm new(er) to the NS4G, I'm going to defer to those with more expertise and follow the directions given.
Click to expand...
Click to collapse
well the "make sure it sticks" flashing with rom manager doesn't make any sense. the only way the recovery would be overwritten is if the ROM you flash over writes it or in fastboot

mikeyinid said:
OCD, I know the feeling lol. What got it to stick?
Click to expand...
Click to collapse
Yeah, I'm very anal when it comes to this kind of stuff...I was a developer for a little bit (Java middleware, then on to the front-end stuff) where regression testing was important. Sometimes, it's best to reload things piece by piece to see what breaks what. Then go from there.
I haven't gotten it to stick yet; gonna get some sleep and start over tomorrow. I used fastboot to push the stock boot, bootloader, system, recovery, and userdata IMGs a moment ago, and the phone is back to bone stock.

[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..

[Q] Uber noob stuck and scared

So I've been reading these forums for days on end now before I touch my phone again. Is my order of things to do correct? (HTC One XL (AT&T))
1. Root
2. Supercid
3. Unlock bootloader
---Currently here---
4. Install CWM/make a backup
5. Relock bootloader
6. Flash a RUU (1.88?)
7. Unlock bootloader
8. Flash a rom
9. Enjoy
As shown above, I rooted, have su on my screen and I can get into the bootloader by vol down+power. I had a scare trying to install RUU 1.85 but I think it failed because my bootloader is unlocked?
Basically everything I do on my phone scares me now. I opened my bootloader today so I can see what stock recovery looked like. I got some weird icons that scared me. I cannot stay where I am because I cannot get OTA updates, and I cannot flash updates myself. HELP!
Thanks, people on this forum are awesome, but you all know too much to be able to write a proper noobs guide.

Valitri said:
So I've been reading these forums for days on end now before I touch my phone again. Is my order of things to do correct? (HTC One XL (AT&T))
1. Root
2. Supercid
3. Unlock bootloader
---Currently here---
4. Install CWM/make a backup
5. Relock bootloader
6. Flash a RUU (1.88?)
7. Unlock bootloader
8. Flash a rom
9. Enjoy
As shown above, I rooted, have su on my screen and I can get into the bootloader by vol down+power. I had a scare trying to install RUU 1.85 but I think it failed because my bootloader is unlocked?
Basically everything I do on my phone scares me now. I opened my bootloader today so I can see what stock recovery looked like. I got some weird icons that scared me. I cannot stay where I am because I cannot get OTA updates, and I cannot flash updates myself. HELP!
Thanks, people on this forum are awesome, but you all know too much to be able to write a proper noobs guide.
Click to expand...
Click to collapse
Those steps are correct EXCEPT for 5, 6 and 7. You don't need those if you're flashing a custom rom, only if you're staying official and using an RUU. We can flash insecure boot.img files now which allow us to jump around firmware versions without blowing up. Just make sure you do a factory reset from recovery before flashing a new custom rom to prevent any weird bugs (you can use Titanium Backup to backup all your apps). Also, I would personally recommend flashing TWRP over CWM. It's a little more friendly in terms of UI and has a bit more functionality baked in.
Edit: And just FYI, the RUU did fail because your bootloader was unlocked. And now you know.

Are you on 1.85 already? If so you are set. But if you aren't, relock the downloader by connecting your phone to your computer via USB in fastboot and typing fastboot OEM lock, upgrade to 1.85 and then unlock the bootloader once again.

stnguyen09 said:
Those steps are correct EXCEPT for 5, 6 and 7. You don't need those if you're flashing a custom rom, only if you're staying official and using an RUU. We can flash insecure boot.img files now which allow us to jump around firmware versions without blowing up. Just make sure you do a factory reset from recovery before flashing a new custom rom to prevent any weird bugs (you can use Titanium Backup to backup all your apps). Also, I would personally recommend flashing TWRP over CWM. It's a little more friendly in terms of UI and has a bit more functionality baked in.
Edit: And just FYI, the RUU did fail because your bootloader was unlocked. And now you know.
Click to expand...
Click to collapse
Thanks for confirming why the RUU failed. I was scared because it never said it failed or errored. I let it run for 90+ minutes and finally did a hard reset on my phone.
I downloaded Titanium but I don't understand where the backups go. How to save them or how to use them for recovery. I also don't understand how people talk about this phone having an SD card when it doesn't.
I saw TWRP and it looked like the better option but I thought a lot of the roms needed CWM to flash from. I guess I really don't fully understand how to flash a rom then.
This is so weird because I jailbroke my iPhone 3g, and tried multiple roms on my cousins Droid X a long time ago.
Easy question. If you stick with roms, any reason to ever relock the bootloader?
Thanks

Lilshaun said:
Are you on 1.85 already? If so you are set. But if you aren't, relock the downloader by connecting your phone to your computer via USB in fastboot and typing fastboot OEM lock, upgrade to 1.85 and then unlock the bootloader once again.
Click to expand...
Click to collapse
I'm on 1.73
As the previous poster said, if I want custom roms I shouldn't even bother with the RUU? Is the RUU just a way to get the most updated factory settings because of root? Also do RUUs cancel root?

Valitri said:
Thanks for confirming why the RUU failed. I was scared because it never said it failed or errored. I let it run for 90+ minutes and finally did a hard reset on my phone.
I downloaded Titanium but I don't understand where the backups go. How to save them or how to use them for recovery. I also don't understand how people talk about this phone having an SD card when it doesn't.
I saw TWRP and it looked like the better option but I thought a lot of the roms needed CWM to flash from. I guess I really don't fully understand how to flash a rom then.
This is so weird because I jailbroke my iPhone 3g, and tried multiple roms on my cousins Droid X a long time ago.
Easy question. If you stick with roms, any reason to ever relock the bootloader?
Thanks
Click to expand...
Click to collapse
1. You never need to relock the bl unless you're RUU'ing
2. TWRP and CWM do the same thing, what you can do with one you can pretty much assume you can do with the other
3. Titanium Backup (I refer to it as TiBu) stores the backup files on your phone in a Titanium Backup folder on your sd card. You use the TiBu app itself to batch restore your apps. So this mean you're gonna have to redownload it manually from the Play Store after a factory wipe. You also have the option or restoring your apps with data and also restoring system data. In my experience, restoring system data is always a bad idea and will cause weird behavior. Restoring app data also sometimes has weird consequences, depending on the app, so I usually just restore my apps without data and individually restore data to apps I know will have no issue and are a pain to set up again.
4. We refer to it as an sd card because it technically still is one, just soldered onto the board.
5. Yes, RUU will get rid of root. It returns your phone to its factory state (except it doesn't touch your user data)
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
Lilshaun said:
Are you on 1.85 already? If so you are set. But if you aren't, relock the downloader by connecting your phone to your computer via USB in fastboot and typing fastboot OEM lock, upgrade to 1.85 and then unlock the bootloader once again.
Click to expand...
Click to collapse
Upgrading to 1.85 isn't necessary since we can flash boot.img and jump between versions

Thank you. I will run a backup from titanium and download it to my computer. Then I will flash TWRP, then try some roms.

Valitri said:
Thank you. I will run a backup from titanium and download it to my computer. Then I will flash TWRP, then try some roms.
Click to expand...
Click to collapse
You can have TiBu sync to a Dropbox, Google Drive, or Box account too. The scheduling feature is real nice. I have mine running the 2 default scheduled backup tasks every morning at 6am and then automatically uploading to Google Drive provided that I am plugged in and on WiFi.
I have it run every morning just in case I do something stupid during the day.
Oh and make sure to watch your internal storage space. CWM/TWRP backups take up A LOT of space, around 1GB (that's off the top of my head, I know it's around there somewhere). Manage your backups carefully, deleting ones you don't need.

you dont need to bootloader unlock before you upgrade to 1.85. just get the unlock code and then, with a locked bootloader, update RUU to 1.85. then afterwards unlock bootloader with unlock code.bin.

Valitri said:
Thank you. I will run a backup from titanium and download it to my computer. Then I will flash TWRP, then try some roms.
Click to expand...
Click to collapse
Titanium is just for backing up apps not the entire phone. Sorry if you knew that, it just sounded like you didn't.
You need to flash TWRP and do a backup with it. This will backup your entire phone. In case you ever run into issues you know that you have a backup of your phone from when it was fully functional. This stays on your phone and if you ever need to restore it you do so from within TWRP.

pside15 said:
Titanium is just for backing up apps not the entire phone. Sorry if you knew that, it just sounded like you didn't.
You need to flash TWRP and do a backup with it. This will backup your entire phone. In case you ever run into issues you know that you have a backup of your phone from when it was fully functional. This stays on your phone and if you ever need to restore it you do so from within TWRP.
Click to expand...
Click to collapse
Right, think of a TWRP/CWM backup as the equivalent of a Windows System Restore Point or a Mac Time Machine Backup. It's pretty much a snapshot of your system that you can jump back to in order to revert anything you did that screwed things up.

[Q] First Time Root Help Please?

Hello everyone,
I just bought a Verizon Galaxy S3 and I am in the process of rooting it. Im kinda freaking out because things really arent going that well for me. So far what I've done is root and unlock bootloader. Here is where the problem starts. When I try to reboot into CWM recovery it just boots me into the normal android recovery. Is this normal? every video I have watched shows people manually rebooting straight into CWM. The only way I can get it to work is if I go into EZ recovery and press "Flash" then "Reboot Into Recovery" buttons.
My second area of confusion is regarding the IMEI backup. Is this something everyone does when flashing roms on this phone? I am very confused as to what I'm supposed to do. Do I use the adb or download a terminal app from the play store? If someone could clarify that would be great !
Sorry if these questions are pathetic but this is my first time doing this and it's a learning experience I geuss. Here are the links to the guides I used for what I have done so far.
http://forum.xda-developers.com/showthread.php?t=1762709
http://forum.xda-developers.com/showthread.php?t=1852255
Thanks

I recently saw someone have a problem getting custom recovery persist, and another member pointed out a step you needed to do to get it to stick. I'll see if I can locate that post and add it to this post.
As far as IMEI goes, you only need to back it up once, and then you are good to go. Perform step a followed by step b in the backup thread.

apacseven said:
I recently saw someone have a problem getting custom recovery persist, and another member pointed out a step you needed to do to get it to stick. I'll see if I can locate that post and add it to this post.
As far as IMEI goes, you only need to back it up once, and then you are good to go. Perform step a followed by step b in the backup thread.
Click to expand...
Click to collapse
Alright thanks, so for most people once they flash it once it should stay every time they reboot into recovery? I have probably the noobiest question of all time, what does flashing CWM recovery even do? is it like flashing a rom where it just gets baked in to the OS permanently? Or does it actually provide a backup of data because I thought thats what nandroids were for.

Havent found exactly what I was recalling as far as the recovery problem, but I found something in a thread below this that makes me think maybe your bootloader wasnt unlocked properly. What version (if any) of ez recovery did you use?
Also, flashing CWM (ideally, at least) replaces the stock recovery with the clockworkmod recovery. Then, when you boot into CWM, that is where you make a backup (nandroid) of your current ROM. Once you have backups made you can quickly switch between ROMs by restoring the nandroids.
I hope I understood your question correctly and also answered it properly.

apacseven said:
Havent found exactly what I was recalling as far as the recovery problem, but I found something in a thread below this that makes me think maybe your bootloader wasnt unlocked properly. What version (if any) of ez recovery did you use?
Also, flashing CWM (ideally, at least) replaces the stock recovery with the clockworkmod recovery. Then, when you boot into CWM, that is where you make a backup (nandroid) of your current ROM. Once you have backups made you can quickly switch between ROMs by restoring the nandroids.
I hope I understood your question correctly and also answered it properly.
Click to expand...
Click to collapse
Yes you did, thank you so much. In the tutorial I used it was saying that the newer versions of EZ unlock were having problems so I downloaded version 1.2. How do I proceed if my bootloader was unlocked improperly? Also, I went in to EZ recovery and flashed CWM and made a nandroid backup if this matters.
Thanks so much for your help.

If you used version 1.2 then my point was moot. So you can only get into CWM if you install CWM from ez recovery and then hit reboot into recovery? If you do the hold vol up + home button while powering on it always takes you to stock recovery?

Yep its very weird. Not sure what to do.

Someone else will likely be able to chime in on how to correct this, unfortunately (or fortunately? lol) it hasnt happened to me so I havent had to deal with it. Its not a huge deal so I wouldnt worry about it.
Personally I use TWRP recovery. You can try that and see if it will stick, you can always go back to CWM later. Try it in ez recovery, or Goo manager from the play store (I use goo manager). If you want to try installing it from goo manager, install the app, hit menu, then select install open recovery script.

K cool. So would it hurt me if I just used ez recovery to flash and reboot everytime I need to get into CWM? Also for goo manager does that install the one you were talking about or CWM?
Sent from my SCH-I535 using xda app-developers app

Goo manager is only for TWRP recovery. And as long as the backups are being stored and you can access them the next time you get into CWM, it doesnt matter. Like I said, hopefully someone will be able to tell you how to correct this issue and we will both learn a thing or two from it.

Did you follow Step 12 in Section 2 in the first link you posted?
You have to make sure to go to CWM v6.0.1 in the drop down and install that version of Clockwork Mod Recovery.
I'm not sure if that's the cause of your issue, but you may want to check into that

Yep i did that
Sent from my SCH-I535 using xda app-developers app

Can someone please help D:
Sent from my SCH-I535 using xda app-developers app

How to Switch from TWRP to ClockWorkMod?

Hello, I'm needing a bit of advice on what to do when switching from my current recovry, TWRP, to ClockWorkMod. I do realize that some say it was never ported over right to the One X, but I'm needing to use it to test a theme for a dev that uses Universal Flasher. I'm pretty sure I can just go into the CWM app and click "Install CWM" but I'd like to make sure I don't corrupt my recovery If anyone could help me that'd be great!
*Edit* Whoops, I didn't realize that the One X was not officially supported. So seeing that, could I just flash the CWM recovery.zip in TWRP and then again once I'm in CWM to make sure it sticks?
The theme is here if you'd like to take a look- http://forum.xda-developers.com/showthread.php?t=1843805

tanner4137 said:
Hello, I'm needing a bit of advice on what to do when switching from my current recovry, TWRP, to ClockWorkMod. I do realize that some say it was never ported over right to the One X, but I'm needing to use it to test a theme for a dev that uses Universal Flasher. I'm pretty sure I can just go into the CWM app and click "Install CWM" but I'd like to make sure I don't corrupt my recovery If anyone could help me that'd be great!
The theme is here if you'd like to take a look- http://forum.xda-developers.com/showthread.php?t=1843805
Click to expand...
Click to collapse
Cwm will cause problems
Sent from my HTC One XL using xda-developers app

absolutelygrim said:
Cwm will cause problems
Sent from my HTC One XL using xda-developers app
Click to expand...
Click to collapse
Yes, but could you please elaborate on that? I understand people think it was never properly ported to our phone, but I'm needing to use it to test a theme for a dev. The only reason I'm wanting to use CWM is that his theme uses Universal Flasher, which isn't supported by TWRP.

tanner4137 said:
Hello, I'm needing a bit of advice on what to do when switching from my current recovry, TWRP, to ClockWorkMod. I do realize that some say it was never ported over right to the One X, but I'm needing to use it to test a theme for a dev that uses Universal Flasher. I'm pretty sure I can just go into the CWM app and click "Install CWM" but I'd like to make sure I don't corrupt my recovery If anyone could help me that'd be great!
The theme is here if you'd like to take a look- http://forum.xda-developers.com/showthread.php?t=1843805
Click to expand...
Click to collapse
sure you can overwrite twrp by flashing cwm, but why would that theme only be flashable through universal flasher ??
if you're gonna go to cwm better make a nand backup and a full backup of your sd and pull all of it onto your computer. CWM on hox has some unpredictable reactions.

Here's your answer : you don't want to ..If u want I will laugh when u accidently f up and sd card gets wiped and u can't mount and have to reflash twrp

Crappyvate said:
sure you can overwrite twrp by flashing cwm, but why would that theme only be flashable through universal flasher ??
if you're gonna go to cwm better make a nand backup and a full backup of your sd and pull all of it onto your computer. CWM on hox has some unpredictable reactions.
Click to expand...
Click to collapse
I actually found in the CWM forum for the One X that one guy who has an AT&T version of the One X, like me, tried using CWM and erased EVERYTHING on the phone rendering it useless. I'm really hesitant with this now. I'll contact the dev and see if he can somehow make it work on TWRP (doubt it, but it's worth a shot)

And the international cwm is mot for us that's for endeavor you'd have to dig up a old thread somewhere in this forum ..but don't install the one from Rom manager

tanner4137 said:
I actually found in the CWM forum for the One X that one guy who has an AT&T version of the One X, like me, tried using CWM and erased EVERYTHING on the phone rendering it useless. I'm really hesitant with this now. I'll contact the dev and see if he can somehow make it work on TWRP (doubt it, but it's worth a shot)
Click to expand...
Click to collapse
let me repeat what i said earlier: if you cannot be talked out of it. just make a nand backup and a full sd backup and pull it on your computer, that way if something happens you can just restore everything, just seems like a lot of work to test a theme, must be some THEME

I pm'd the dev of that theme he said flash cwm to flash theme then just flash back twrp. Im about to do it soon to flash the theme. Id backup sdcard first though.