Database Info

[Q] Stuck in Stock Recovery

After successfully flashing ClockWork RecoveryMod, I placed SU on the root of my SNS, powered it off, went into fastboot, but when I went into Recovery, it just went to Stock Recovery, the Exclamation Mark inside the Triangle with the Android next to it appeared, but no text or anything else is on the screen. I've let it sit for about 15 minutes, and nothing. I also can't do anything by clicking the volume buttons, or the power buttons. I've also unplugged the Phone, held the power button to try to reboot it, held volume-up and power to try to go back into fastboot, but nothing. Should I pull the battery? Why didn't it go into ClockWork RecoveryMod? Command Prompt gave me the whole " sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s" thing...
What do I do? I can't just leave it sitting like this forever.
Edit: I unplugged and replugged it a few times, and it rebooted. But I've tried going back to fastboot and going into Recovery, and I get the same screen, over and over. I've even tried flashing CWRM again, and nothing. I'm using 3.0.2.4. Should I just use 3.0.0.5?

When you are in the stock recovery mode and you see the exclamation mark inside the triangle: Just hold the power button and hit volume up and you will get into stock recovery where you can perform a reboot etc.
Just try 3.0.0.5. There is something wrong with clokwork mod it you just went into stock recovery. You should be fine if you follow one of the guides on this forum.

If you still are using the stock rom. This only applies of on stock root rom because the custom rom have the edited already. You must do this. If you don't then you will have to flash clockwork ever time you reboot.
Reboot your Nexus S
Download and install Root Explorer app from Android Market
Open Root Explorer and navigate to etc directory
Tap on the gray box that says Mount R/W
Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
Once renamed, download and install the app called ROM Manager from Android Market
Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.

Hawky_ said:
When you are in the stock recovery mode and you see the exclamation mark inside the triangle: Just hold the power button and hit volume up and you will get into stock recovery where you can perform a reboot etc.
Just try 3.0.0.5. There is something wrong with clokwork mod it you just went into stock recovery. You should be fine if you follow one of the guides on this forum.
Click to expand...
Click to collapse
I tried it again with 3.0.2.5 from http://forum.xda-developers.com/showthread.php?t=988686. Did not work. Went again into Stock Recovery.
jerrycycle said:
If you still are using the stock rom. This only applies of on stock root rom because the custom rom have the edited already. You must do this. If you don't then you will have to flash clockwork ever time you reboot.
Reboot your Nexus S
Download and install Root Explorer app from Android Market
Open Root Explorer and navigate to etc directory
Tap on the gray box that says Mount R/W
Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
Once renamed, download and install the app called ROM Manager from Android Market
Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.
Click to expand...
Click to collapse
I'm a bit confused with your post.
I am still using the Stock Rom, but I don't have root access.
I've tried, after unlocking the Bootloader, going into Rom Manager and Flashing ClockWork, but it tells me first:
"You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin.su". (...)"
Then, when I still attempt to flash ClockworkMod, it tells me:
"An error occurred while attempting to run priviliged commands!"
I should have told the full story first.
I was once rooted, but it was through ROM Manager and flashing Clockwork from there. But then I had a few issues with my Wifi, and I decided to flash back Stock Rom. I still had an unlocked Bootloader though, so I thought that just redownloading Rom Manager and flashing CWRM and having Superuser installed would work. It didn't. So I attempted to root all over again, this time, manually.
But, I always go back to square one, it seems, when I try to get into Recovery.
What up with that?

After you flash CWM recovery, go straight into recovery from the fastboot menu. Do not reboot. Do not power off. Flash CWM and when it finishes immediately press volume down to select recovery and then press power to go in.
The Nexus S will overwrite CWM with stock recovery every time the phone boots by default. This could be what is giving you trouble.
Sent from my Nexus S using XDA App

matt2053 said:
After you flash CWM recovery, go straight into recovery from the fastboot menu. Do not reboot. Do not power off. Flash CWM and when it finishes immediately press volume down to select recovery and then press power to go in.
The Nexus S will overwrite CWM with stock recovery every time the phone boots by default. This could be what is giving you trouble.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!

EonHawk said:
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
Click to expand...
Click to collapse
No problem.
There is a script located in the /etc folder called install-recovery.sh. it runs every time you boot and installs stock recovery. You have two choices: always use rom manager to flash CWM every time you need to access recovery, or use root explorer to rename install-recovery.sh to install-recovery.sh.bak so that it will not run and will leave CWM installed.
Glad you got it figured out!
Sent from my Nexus S using XDA App

Or a third choice of course would be to install a custom ROM because they tend to not include that script
Sent from my Nexus S using XDA App

EonHawk said:
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
Click to expand...
Click to collapse
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else

buachaille said:
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Actually I think that guide does have two unnecessary steps that cause confusion. After flashing CWM, the guide instructs the user to power off, power on, and then to access recovery. The user should just access recovery immediately after flashing.
EDIT: I guess the problem is just that the bolded part should be added:
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS while holding volume up

buachaille said:
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
That's partly my fault, I never went down to the 2nd Post and saw those Notes, but what's the point of not including that already in the steps in the main Post? He could have just told to go straight from Recovery after flashing CWRM, but decided not to.
matt2053 said:
Actually I think that guide does have two unnecessary steps that cause confusion. After flashing CWM, the guide instructs the user to power off, power on, and then to access recovery. The user should just access recovery immediately after flashing.
EDIT: I guess the problem is just that the bolded part should be added:
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS while holding volume up
Click to expand...
Click to collapse
I think he should just have instructed to place the SU zip on the root of the SD card before flashing CWRM. That way, there wouldn't be a need to reboot to mount the SD to place SU, that way potentially losing the CWRM.

[Q] Update Verification failed in 3e system recovery

Hi all. I'm new to android, but not to modding. I've been with xda for a few weeks and have appreciated the quality of the posts and tutorials. Btw-I have searched the forums and google and am still soo lost.
Any help would be appreciated.
Goal:
-To get stock kd1
Previous Config:
-Black Ice KD1, CWM recovery red, voodoo lag fix, ext4 on all, Bali 3.2 no uv, Juwe ram script
-was previously overclocked using tegrak ultimate to 1.2ghz, but about a day before my error it had been put back to 1.0ghz and tegrak uninstalled.
What I did (error):
-Boot CWM red wipe data, cache, factory reset
-boot download mode, flash T959VKB5-Custom.tar with Odin 1.7
-Phone reboots into stock android recovery (3e)
-selecting reboot phone bring galaxy s splash, then back to recovery
-selecting reinstall packages; it looks for the update.zip but I keep getting verification failed
What I Know
-verification fails because im using default 3e recovery
-i need to use odin to flash a new kernel with the 2e recovery
What I'm confused about
-All kernels that I've found are .zip, odin takes .tar
-I cant use the .zip kernels because I cant install a package
-I cant install a package because verification fails
-verification fails because using 3e recovery
-cant flash kernel with 2e recovery because i dont know how!
So again all comments are appreciated. Thanks for reading.

Mizun0h said:
Hi all. I'm new to android, but not to modding. I've been with xda for a few weeks and have appreciated the quality of the posts and tutorials. Btw-I have searched the forums and google and am still soo lost.
Any help would be appreciated.
Goal:
-To get stock kd1
Previous Config:
-Black Ice KD1, CWM recovery red, voodoo lag fix, ext4 on all, Bali 3.2 no uv, Juwe ram script
-was previously overclocked using tegrak ultimate to 1.2ghz, but about a day before my error it had been put back to 1.0ghz and tegrak uninstalled.
What I did (error):
-Boot CWM red wipe data, cache, factory reset
-boot download mode, flash T959VKB5-Custom.tar with Odin 1.7
-Phone reboots into stock android recovery (3e)
-selecting reboot phone bring galaxy s splash, then back to recovery
-selecting reinstall packages; it looks for the update.zip but I keep getting verification failed
What I Know
-verification fails because im using default 3e recovery
-i need to use odin to flash a new kernel with the 2e recovery
What I'm confused about
-All kernels that I've found are .zip, odin takes .tar
-I cant use the .zip kernels because I cant install a package
-I cant install a package because verification fails
-verification fails because using 3e recovery
-cant flash kernel with 2e recovery because i dont know how!
So again all comments are appreciated. Thanks for reading.
Click to expand...
Click to collapse
your so use to having the recovery file already put into system/bin so you forgot to do it when you flashed kb5
you see after kd1 it was no longer needed to push the recovery file yourself because its been implemented in all the roms since
so look into krlons CWM final and push the recovery file into /system/bin
then try again you wont get the error

dsexton702 said:
your so use to having the recovery file already put into system/bin so you forgot to do it when you flashed kb5
you see after kd1 it was no longer needed to push the recovery file yourself because its been implemented in all the roms since
so look into krlons CWM final and push the recovery file into /system/bin
then try again you wont get the error
Click to expand...
Click to collapse
Thank you. This definately sounds like the answer I'm looking for. But how would i go about pushing the file to the system if I cant boot my phone?
Will droid explorer still do that?

Mizun0h said:
Thank you. This definately sounds like the answer I'm looking for. But how would i go about pushing the file to the system if I cant boot my phone?
Will droid explorer still do that?
Click to expand...
Click to collapse
I think it'd be easier to get a ROM like this one:
http://forum.xda-developers.com/showthread.php?t=1063696
It already comes rooted so you can throw in the custom recovery file, then go back to a completely stock build (I think that's what you want).
After you flash that rom with odin, get both the files in the first post of this thread:
http://forum.xda-developers.com/showthread.php?t=1099374
You'll be able to get into CWM from there and that'll give you more flexibility.
You probably won't be able to get into download mode from the bootloop you're getting, so do a battery pull, then put the battery back in, hold down both volume keys, and while those are still pressed, press the power button. You should get a screen with a big yellow triangle with an exclamation mark in the middle, which you probably already know is download mode.

Thanks for the quick response. Worked like a charm until, only through impatience, come across another problem.
I was following the steps from this thread
http://forum.xda-developers.com/showthread.php?t=1141550
-I got cwm, flashed ext4 converter, flashed black ice, and then i wanted to install bali 3.1
-By mistake i downloaded the non uv package to the sd card. So out of impatience pulled the sd card and dropped the uv one on their.
-not to my surprise cwm didnt see any changes. so i went to advance, then reboot recovery
Now my phone boots straight to galaxy s splash and stays there. I cant access cwm or download mode. Any ideas?

Did you have bali 2.1 or higher before flashing the ext4 converter? If you don't it will soft brick, from what I know. Flash odin and restart.
Sent from my SGH-T959V using XDA Premium App

Mizun0h said:
Thanks for the quick response. Worked like a charm until, only through impatience, come across another problem.
I was following the steps from this thread
http://forum.xda-developers.com/showthread.php?t=1141550
-I got cwm, flashed ext4 converter, flashed black ice, and then i wanted to install bali 3.1
-By mistake i downloaded the non uv package to the sd card. So out of impatience pulled the sd card and dropped the uv one on their.
-not to my surprise cwm didnt see any changes. so i went to advance, then reboot recovery
Now my phone boots straight to galaxy s splash and stays there. I cant access cwm or download mode. Any ideas?
Click to expand...
Click to collapse
Check your mounts to make sure they are
Code:
unmount
mount
mount
unmount
You'll need to reflash a rom using odin though, you won't be able to use CWM until you do.

Thank you. worked great.

[Q] Can't replace 3e Recovery?

I've followed the instructions and the videos...I cannot get my Infuse to allow me to install a new ROM. I had a Captivate previously and flashed frequently. Tried to resist rooting & flashing but finally ran out of patience waiting for AT&T.
So I have root. I've copied the recovery file from the SDCard to the /system/bin...made sure the permissions were all copied from the original recovery. I reboot into recovery and re-install packages.
I then downloaded ROMManager and installed. Reboot into Recovery (3e) and re-install packages which then brings me to the green font CWM. If I choose to install zip from SD I don't specifically see any errors on the screen, but I end up getting brought back to 3e reboot...which never goes anywhere.
I haven't been able to find much help on this searching...I can't be the only one having this issue.

Flash community kernel through Odin and you'll have fully working recovery...flash...wait til it starts to boot....pull battery...replace batt ...hold vol up, vol down and power til Samsung logo appears and let go and it will boot into red CWM then your good to flash away
Sent from my SAMSUNG-SGH-I997 using xda premium

[Q] How to revert back to stock everything without root on GT-i9020T?

How do I revert back after one-click root to the stock everything including radio, rom, build, etc. I am currently running Cynagon mod RC1 7 and have had numerous issues, I would just like a clean, simple cut answer so I can give this to someone for the holidays, any help would be mightly appreciated, as i've asked this in the past and can never seem to get a clear cut answer, thanks.

wierd165 said:
How do I revert back after one-click root to the stock everything including radio, rom, build, etc. I am currently running Cynagon mod RC1 7 and have had numerous issues, I would just like a clean, simple cut answer so I can give this to someone for the holidays, any help would be mightly appreciated, as i've asked this in the past and can never seem to get a clear cut answer, thanks.
Click to expand...
Click to collapse
Just flash a full rom, it should restore the radio, the recovery, and the OS. Then do a reset to factory defaults if you are paranoid.
Get the proper rom for you phone here:
http://forum.xda-developers.com/showthread.php?t=1063664
If you're on T-Mobile, you have an i9020-T, this should work for you. It is the full 2.3.6 image.
http://android.clients.google.com/p...a25375426.signed-soju-ota-189904.1ada2537.zip

Is this also working if you're coming from stock unrooted ICS 4.0.3 ?
And
Is there any risk of loosing IMEI if you're going full ROM ?

mahanddeem said:
Is this also working if you're coming from stock unrooted ICS 4.0.3 ?
And
Is there any risk of loosing IMEI if you're going full ROM ?
Click to expand...
Click to collapse
I have reverted back from 4.0.3 yesterday by reflashing the full 2.3.6 rom without any issues. I'm not sure I understand what you mean by losing IMEI.
My phone works just fine after doing this (more than once!).

pcbroch said:
Just flash a full rom, it should restore the radio, the recovery, and the OS. Then do a reset to factory defaults if you are paranoid.
Get the proper rom for you phone here:
http://forum.xda-developers.com/showthread.php?t=1063664
If you're on T-Mobile, you have an i9020-T, this should work for you. It is the full 2.3.6 image.
http://android.clients.google.com/p...a25375426.signed-soju-ota-189904.1ada2537.zip
Click to expand...
Click to collapse
Ok here's my problem i did the ics update earlier before you told me this and still having issues, now when I go to recovery I get a android with his chest open with a red caution sign on it...how could I just format everything, essentially make it the way it was out of box so I could start over...because of all the issues I'm currently having.

When you get to that point, you need to hold down power then press vol up. Then you will be able to flash the zip. You need to put the zip on the phone first though, unless you have CWM recovery, in which case you can mount the sdcard section and move it across then, and flash it after.

OK thanks...Just please let's summarize this
1.You were on I9020T bone stock , unrooted
2.You had GB 2.3.6
3.You updated manually (or OTA) to 4.0.3
4.You decided to revert to GB 2.3.6
5.You used exactly the same method of manual update (stock recovery after copying the .zip file and in this case the full ROM of 2.3.6 to SD)
6.You followed the stock recovery steps and chose the .zip 2.3.6..
7.After everything was setup , you booted into GB 2.3.6 without any problems
Is that right ? or better if you make the exact detailed steps you did to revert to GB 2.3.6 would be apreciated
Thanks

furiannn said:
When you get to that point, you need to hold down power then press vol up. Then you will be able to flash the zip. You need to put the zip on the phone first though, unless you have CWM recovery, in which case you can mount the sdcard section and move it across then, and flash it after.
Click to expand...
Click to collapse
Tried, but then I get this error:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: !less_than_int(1316544229. getprop("ro.build.date.utc"))
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Any help?

I think u need a custom recovery to be able to revert back to gingerbread
Sent from my Nexus S using XDA App

Raver27 said:
I think u need a custom recovery to be able to revert back to gingerbread
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
how would I go about flashing the custom recovery? I tried to flash another full rom package with the recovery in it and like i said i got that error...

Do you have a folder in windows where you have been flashing stuff from, using fastboot?
If so, just get this recovery image http://forum.xda-developers.com/showthread.php?t=988686
Download either the blue or green 5023 image. Doesnt matter which just changes colour of mod place the file in the same folder as the fastboot.
Next, with the phone off and after attaching the phone to USB, turn it on while pressing vol-up and power. You should see the boot option screen, the fastboot screen. Leave the phone there.
Now go back to cmd window in windows, and browse to the folder where you have all the fastboot files and where you have put the above image file. Then type in the following:
fastboot flash recovery <image name.img> (without the < >)
press enter and it'll flash the recovery and then you can install the old version of android

furiannn said:
Do you have a folder in windows where you have been flashing stuff from, using fastboot?
If so, just get this recovery image http://forum.xda-developers.com/showthread.php?t=988686
Download either the blue or green 5023 image. Doesnt matter which just changes colour of mod place the file in the same folder as the fastboot.
Next, with the phone off and after attaching the phone to USB, turn it on while pressing vol-up and power. You should see the boot option screen, the fastboot screen. Leave the phone there.
Now go back to cmd window in windows, and browse to the folder where you have all the fastboot files and where you have put the above image file. Then type in the following:
fastboot flash recovery <image name.img> (without the < >)
press enter and it'll flash the recovery and then you can install the old version of android
Click to expand...
Click to collapse
I don't believe I have a folder as such, being a person who is not familiar with the lingo, etc of all this i rooted it with one-click mod, and just flash things through this, are you saying I can flash things externally? sorry to sound like a bum, but i'm trying to understand thanks.

No problem, we're all noobs once, hell i still am and only just coming to terms with it all! Just need to do a bit of researching, but heres the basics...
fastboot lets you flash stuff to the phone from windows, when the phone is attached to the USB and is in fastboot mode (just turned on, from vol-up/pwr).
Can unlock the boot loader and flash recovery images from there. Once thats done, most other stuff can be done from within the new recovery mode, clockworkmod being the one that everyone uses.
over at nexusshacks it's explained really well how to root your phone. And he provides a zip with everything you could want. That zip is the folder I was talking about in the last post. It comes with drivers to install when you first plug the USB in and the PC recognises the phone. Download the pack, install them drivers and then go back to my last post and take it from there
http://downloadandroidrom.com/file/NexusS/rooting/nexussrootnew.zip
EDIT: Also do a full wipe/data reset just before you flash the new rom

furiannn said:
No problem, we're all noobs once, hell i still am and only just coming to terms with it all! Just need to do a bit of researching, but heres the basics...
fastboot lets you flash stuff to the phone from windows, when the phone is attached to the USB and is in fastboot mode (just turned on, from vol-up/pwr).
Can unlock the boot loader and flash recovery images from there. Once thats done, most other stuff can be done from within the new recovery mode, clockworkmod being the one that everyone uses.
over at nexusshacks it's explained really well how to root your phone. And he provides a zip with everything you could want. That zip is the folder I was talking about in the last post. It comes with drivers to install when you first plug the USB in and the PC recognises the phone. Download the pack, install them drivers and then go back to my last post and take it from there
http://downloadandroidrom.com/file/NexusS/rooting/nexussrootnew.zip
EDIT: Also do a full wipe/data reset just before you flash the new rom
Click to expand...
Click to collapse
I'm using clockwork right now, but it seems to be corrupted, im running 4.0.3 right now on a full rom package, so your saying I should still do this? I think i may have done all that before, as the phone is rooted, but I used the one-click method instead.

Just download that file and then you'll have what you need on your pc to do what i mentioned above. Plug the phone in and reflash the new recovery which will not harm it, and then you'll be able to stick gingerbread or ICS back on. You gotta try things out otherwise you'll not understand what is going on. I dont know of any one click thing that will let you go back to default as it was before. After it flashes the new recovery, scroll down to "recovery" on the screen and press the power button, dont restart the system.
In hindsight, while the one click methods are easy to use, theyre getting used by people that dont do the necessary research to learn about the rooting and flashing process. This means you end up skipping so much that you learn about the whole rooting and flashing proocess when doing it manually, which in turn means you have more trouble getting out of it if you want it back to the way it was! No offence intended here, but you just need to man up and do it! All will be well

[Q] Confused regarding the terms: CWM recovery, A2 bootstrap, Bootmenu manager

I have an US ATT Atrix2 with ICS (via OTA). CPU @ 1GHZ. I have rooted it. My next 2 goals are: 1.Try the Overclock mod 2. Later try NUMA Rom or perhaps the Paranoid Rom.
Next I have been searching & reading all over about CWM recovery etc. I have used these threads:
http://forum.xda-developers.com/showthread.php?t=1396650
http://forum.xda-developers.com/showthread.php?t=1511616
http://forum.xda-developers.com/showthread.php?t=1346977
But I am pretty lost/confused regarding the terms: CWM recovery, A2 bootstrap, Bootmenu manager.
So I'll try to summarize my questions
1. Bootmenu manager: Is this the stock menu that shows up when holding down both vol button and powering on? What is the purpose/use of this?
-I see options: Normal power up, recovery, AP fastboot, BP tools. Can someone explain these or is there a thread?
-Is the AP Fast-boot mode used in conjunction with RSDLite to restore stock ROMs (stock ICS)?
-Can FXZ (.zip's) that custom roms come in be flashed from SD cards with this Bootmenu manager?
2. CWM recovery? Atrix2 bootstrap? I suppose both these go together and is essentially a "3rd party" recovery program? that allows us:
-to take/restore full backups and flashing of FXZ's?
-this is not same as the "ap fasboot" and using RSDLite?"
-AND this can be removed/uninstalled?"
I was looking at MOD OC/UC/init.d thread:
It says: "reboot into recovery you are using (you must be rooted with bootstrap, not sure if will work with bootmenu....)". What exactly do I need here?

gcretro said:
I have an US ATT Atrix2 with ICS (via OTA). CPU @ 1GHZ. I have rooted it. My next 2 goals are: 1.Try the Overclock mod 2. Later try NUMA Rom or perhaps the Paranoid Rom.
Next I have been searching & reading all over about CWM recovery etc. I have used these threads:
http://forum.xda-developers.com/showthread.php?t=1396650
http://forum.xda-developers.com/showthread.php?t=1511616
http://forum.xda-developers.com/showthread.php?t=1346977
But I am pretty lost/confused regarding the terms: CWM recovery, A2 bootstrap, Bootmenu manager.
So I'll try to summarize my questions
1. Bootmenu manager: Is this the stock menu that shows up when holding down both vol button and powering on? What is the purpose/use of this?
-I see options: Normal power up, recovery, AP fastboot, BP tools. Can someone explain these or is there a thread?
-Is the AP Fast-boot mode used in conjunction with RSDLite to restore stock ROMs (stock ICS)?
-Can FXZ (.zip's) that custom roms come in be flashed from SD cards with this Bootmenu manager?
2. CWM recovery? Atrix2 bootstrap? I suppose both these go together and is essentially a "3rd party" recovery program? that allows us:
-to take/restore full backups and flashing of FXZ's?
-this is not same as the "ap fasboot" and using RSDLite?"
-AND this can be removed/uninstalled?"
I was looking at MOD OC/UC/init.d thread:
It says: "reboot into recovery you are using (you must be rooted with bootstrap, not sure if will work with bootmenu....)". What exactly do I need here?
Click to expand...
Click to collapse
Cwm is the same for all phones, Google for clockwork mod recovery.
We have three implementations of cwm for our phone. They are the following.
1) bootmenu manager - it is as I said an implementation of cwm, but adds in a few features like dual booting 2 ROMS, and gets you the ability to get to it on every boot.
2) bootstrap - a no frills version of cwm, and you can not get into it on every boot without a hack. Most things in here are known to work 100% with bootstrap.
Now there are some things that need to be modified to work with boot menu, and others will just work, trying will usually not hurt you as you can fxz if you bootloop.
3) Cwm is also built into the cm based roms, cm10, cm10.1, PA, etc. This version allows you to get to it on every boot by hitting the volume down button when the blue led lights up.
Hope this cleared it up a little bit.
If something says it works with bootstrap only, then that is what you need, but again it might, just might work with boot menu, and prolly just has not been tested.

gcretro said:
I have an US ATT Atrix2 with ICS (via OTA). CPU @ 1GHZ. I have rooted it. My next 2 goals are: 1.Try the Overclock mod 2. Later try NUMA Rom or perhaps the Paranoid Rom.
Next I have been searching & reading all over about CWM recovery etc. I have used these threads:
http://forum.xda-developers.com/showthread.php?t=1396650
http://forum.xda-developers.com/showthread.php?t=1511616
http://forum.xda-developers.com/showthread.php?t=1346977
But I am pretty lost/confused regarding the terms: CWM recovery, A2 bootstrap, Bootmenu manager.
So I'll try to summarize my questions
1. Bootmenu manager: Is this the stock menu that shows up when holding down both vol button and powering on? What is the purpose/use of this?
-I see options: Normal power up, recovery, AP fastboot, BP tools. Can someone explain these or is there a thread?
-Is the AP Fast-boot mode used in conjunction with RSDLite to restore stock ROMs (stock ICS)?
-Can FXZ (.zip's) that custom roms come in be flashed from SD cards with this Bootmenu manager?
2. CWM recovery? Atrix2 bootstrap? I suppose both these go together and is essentially a "3rd party" recovery program? that allows us:
-to take/restore full backups and flashing of FXZ's?
-this is not same as the "ap fasboot" and using RSDLite?"
-AND this can be removed/uninstalled?"
I was looking at MOD OC/UC/init.d thread:
It says: "reboot into recovery you are using (you must be rooted with bootstrap, not sure if will work with bootmenu....)". What exactly do I need here?
Click to expand...
Click to collapse
^^^what he said. Plus a couple threads that I found very useful:
http://forum.xda-developers.com/showthread.php?p=20389449
And:
http://forum.xda-developers.com/showthread.php?p=32113181
They are a bit old, but the info is still relevant.
Sent from this thing.

Thx.
1. So with an all stock ICS, the factory menu that I get by holding both vol buttons and power is of no use to us? (and it's not any implemention of CWM). How is this factory menu referred to around here?. (Till I read your explanation above, I figured that call Bootmenu manager).
2. Before I try any roms, I want to take a complete back up the rooted ICS I have (so I can 100% restore and not loose anything incl my apps). What do I need to install for this? CWM Bootmenu manager or CWM bootstrap?
3. If I install the CWM bootmenu manager, you mention it gives the option on every boot. Will this be a nuisance need human intervention for normal power on?

gcretro said:
Thx.
1. So with an all stock ICS, the factory menu that I get by holding both vol buttons and power is of no use to us? (and it's not any implemention of CWM). How is this factory menu referred to around here?. (Till I read your explanation above, I figured that call Bootmenu manager).
2. Before I try any roms, I want to take a complete back up the rooted ICS I have (so I can 100% restore and not loose anything incl my apps). What do I need to install for this? CWM Bootmenu manager or CWM bootstrap?
3. If I install the CWM bootmenu manager, you mention it gives the option on every boot. Will this be a nuisance need human intervention for normal power on?
Click to expand...
Click to collapse
1. It is used to get into fastboot mode to flash an fxz. It is called stock recovery.
2. Either one will work.
3. It's set to time out and boot automatically after a few seconds. Human intervention is only needed if you want to use the recovery mode. Its not a, nuisance, it's a very handy tool for getting out of boot loops.
Sent from this thing.

1BadWolf said:
1. It is used to get into fastboot mode to flash an fxz. It is called stock recovery.
2. Either one will work.
3. It's set to time out and boot automatically after a few seconds. Human intervention is only needed if you want to use the recovery mode. Its not a, nuisance, it's a very handy tool for getting out of boot loops.
Sent from this thing.
Click to expand...
Click to collapse
Appreciate your time and Jim's!. A2 Bootstrap are settling in after I watched this youtube video https://www.youtube.com/watch?v=XcWpL_OJx8c
It explains A2 bootstrap and additionally "CWM_on_boot" mod (by JY Danny). I see one has to successfully boot into the phone to be able to launch A2 bootstrap which may not be possible in case of a screw up. Hence the advantage of doing the CWM on boot mod. (And using CWM boot strap, there is no need for RSDLite?). Is my understanding correct?
Now "Stock Recovery" and it's AP Fast-boot mode: is to be used in conjunction with RSDLite to flash stock ROMs (stock ICS)? (esp in case of a screw up). But the same can this also be done via CWM's "install from zip from sd card"?

gcretro said:
Appreciate your time and Jim's!. A2 Bootstrap are settling in after I watched this youtube video https://www.youtube.com/watch?v=XcWpL_OJx8c
It explains A2 bootstrap and additionally "CWM_on_boot" mod (by JY Danny). I see one has to successfully boot into the phone to be able to launch A2 bootstrap which may not be possible in case of a screw up. Hence the advantage of doing the CWM on boot mod. (And using CWM boot strap, there is no need for RSDLite?). Is my understanding correct?
Now "Stock Recovery" and it's AP Fast-boot mode: is to be used in conjunction with RSDLite to flash stock ROMs (stock ICS)? (esp in case of a screw up). But the same can this also be done via CWM's "install from zip from sd card"?
Click to expand...
Click to collapse
Well see you hit upon the one major issue with this device. It is that since we have a locked bootloader, we can't flash anything to the recovery partition on the phone, so that means that if you screw up your rom/image CWM is really useless to you, since it actually sits on the system partition with the ROM itself. Now bootmenu manager does place a set of files on the pre-install partition and is a little safer in that respect, but the core of it is still on the system partition, so if you bootloop bad enough, you will not be able to get into bootmenu or bootstrap even with the on every boot hack by J. Y. Daddy.
If the above happens and you can not get into CWM at all, then it is time to use RSD lite and flash the fxz. The FXZ is really your "backup" or your way out of a screw up.
You can backup all day long with CWM, but if you can't get to CWM to restore it, what good is the backup. You can just as easily fxz, and go the play store and install all of your apps again, and sync your contacts online with google, and you are back up and running in a little more time than a CWM restore anyhow.
The ONLY reason for CWM for this phone is to be able to flash ROMs, it really does not serve much more of a purpose. Now I will say that the CWM that is built into the CM based ROMS does not have as much of an issue in a bootloop as the other 2 CWM versions, so installing a CM based ROM may be your best bet, but most of them do have the "stock" camera app working, so you will need to use a 3rd party app to make that work, also the camera flash has issues too, but that be fixed as well.
Again all these things point out your choices and the faults of the CWM implementations we have here, so it really is your choice as to what is best for you and your useage. You can also try them all out, one at a time, and see which one is best for you.

jimbridgman said:
... so if you bootloop bad enough, you will not be able to get into bootmenu or bootstrap even with the on every boot hack by J. Y. Daddy.
If the above happens and you can not get into CWM at all, then it is time to use RSD lite and flash the fxz. The FXZ is really your "backup" or your way out of a screw up....
Click to expand...
Click to collapse
I got it. So the ultimatesavior, is having the trio: Stock ICS fxz, RSD lite & the stock recovery's AP FAST boot (which i suppose in part of the factory bootloader).
Can you confirm/correct the steps below for this?
1. Hold pwr button and vol up&down.
2. Select AP Fastboot. Connect USB cable to computer.
3. Open up RSDLite 6.0, select the FZX and start it? (I read about keeping the FZX zip file in like C:\ and not a long path and also drag & drop the FXZ instead of browse)
4. and bam! all stock working atrix2 :victory:

gcretro said:
I got it. So the ultimatesavior, is having the trio: Stock ICS fxz, RSD lite & the stock recovery's AP FAST boot (which i suppose in part of the factory bootloader).
Can you confirm/correct the steps below for this?
1. Hold pwr button and vol up&down.
2. Select AP Fastboot. Connect USB cable to computer.
3. Open up RSDLite 6.0, select the FZX and start it? (I read about keeping the FZX zip file in like C:\ and not a long path and also drag & drop the FXZ instead of browse)
4. and bam! all stock working atrix2 :victory:
Click to expand...
Click to collapse
Jim is much more knowledgeable than I am, but you've outlined it exactly the way I always do it.:thumbup: The only thing I would add to that is to make sure you have a good charge on your battery. I read somewhere that it should be 80%, but I always get a full charge to 100% just to be sure. If the battery dies or gets too low it will cause BIG problems. I found that out the hard way.
Sent from this thing.

1BadWolf said:
Jim is much more knowledgeable than I am, but you've outlined it exactly the way I always do it.:thumbup: The only thing I would add to that is to make sure you have a good charge on your battery. I read somewhere that it should be 80%, but I always get a full charge to 100% just to be sure. If the battery dies or gets too low it will cause BIG problems. I found that out the hard way.
Sent from this thing.
Click to expand...
Click to collapse
.....and make sure you have the most recent Motorola drivers installed, and use the USB cable that came with your phone. Also it is recommended to use the rear USB connector on PC.
Sent from my MB865