Database Info

[Q]Where do I find a full stock rom of 2.3.3 for my i9023, xxxKB3, GRI54?

Hi guys,
Anyone could guide me to where can I find the source to download the full stock rom for the I9023, xxxKB3, GRI54 so that I can flash this into my phone and overwrite my current CM7 before manually flashing to 2.3.4's stock rom and then reroot it again. Will really appreciate it.
Stan.

There is a full 2.3.4 rom available for your phone.

the "released" link under I9023 has a full rom file in this thread.

Issue is I'm currently rooted and on CM7's rom which means I can't just apply the 2.3.4 full rom over it, it won't work this way. Thus I need to flash my phone back to the stock 2.3.3 rom but I can't seem to find one for my phone
Sent from my Nexus S using XDA App

Stanlehh said:
Issue is I'm currently rooted and on CM7's rom which means I can't just apply the 2.3.4 full rom over it, it won't work this way. Thus I need to flash my phone back to the stock 2.3.3 rom but I can't seem to find one for my phone
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
hmm.. i think a full rom is a stock rom.. it will prolly wipe everything, but bring you to stock 2.3.4.
i only read about needing a stock rom when _updating_ with an update file, which is way smaller..
i poested that in the sticky for the otas.. maybe wait, if someone else confirmes that =)
edit: i don't think rooted is a problem, i was rooted myself. it just was gone when i applied the full rom.

so I should try getting the full rom for my 9023, gri54 and just apply update from sdcard at recovery?
After apply CM7'S rom, I noticed my build changed to gri40, will it affect? The available rom for the 9023 is meant for gri54 only
Sent from my Nexus S using XDA App

Stanlehh said:
so I should try getting the full rom for my 9023, gri54 and just apply update from sdcard at recovery?
After apply CM7'S rom, I noticed my build changed to gri40, will it affect? The available rom for the 9023 is meant for gri54 only
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
well, i think it doesn't matter what you have right now, since it's a full rom, not an update. so cm7 well be gone after install and you have a pure android rom.
so either if you are on gri40 or gri54 it doenst matter, cause you will be grj22 afterwards, as long you have an i9023.
before this full rom came up, some ppl downgraded to gri40, in order to use the update grj22-from-gri40. an update requires the correct version installed, but not when using a full rom.
and yeah, just use recovery and install from sd-card. root will be gone and you be having stock recovery again.
hope that helps..

This definitely helped alot.! So I just format /data and /cache and I'm good to go ahead and flash?
Sent from my Nexus S using XDA App

Stanlehh said:
This definitely helped alot.! So I just format /data and /cache and I'm good to go ahead and flash?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
i don't think u even need to do that.. flashing that rom should wipe everything..
at least i think so.. anyway, since u are going from cm7 to stock rom, ur system is gonna be new..
let me know if it worked!
don't forget, if wann root again afterwards, u need to flash a custom recovery again!

eGozelle said:
i don't think u even need to do that.. flashing that rom should wipe everything..
at least i think so.. anyway, since u are going from cm7 to stock rom, ur system is gonna be new..
let me know if it worked!
don't forget, if wann root again afterwards, u need to flash a custom recovery again!
Click to expand...
Click to collapse
my only worry is that after reading about in the forums. After flashing the full 2.3.4's rom onto my phone and thereafter flashing CWM into it again, it won't stay permanently. Any ideas how to go about solving this?

Locking and unlocking the bootloader again should reset the phone to stock rom and factory defaults, wouldn't it?

MrNago said:
Locking and unlocking the bootloader again should reset the phone to stock rom and factory defaults, wouldn't it?
Click to expand...
Click to collapse
not sure, need someone to clarify this.

Stanlehh said:
my only worry is that after reading about in the forums. After flashing the full 2.3.4's rom onto my phone and thereafter flashing CWM into it again, it won't stay permanently. Any ideas how to go about solving this?
Click to expand...
Click to collapse
didn't realise that cwm recovery will be gone afterwards, since i still was able to flash superuser file with cwm. just saw i'm back to stock recovery ;b
found the same as u did in the guide sticky thread to work around that
so did flash the full rom already?

MrNago said:
Locking and unlocking the bootloader again should reset the phone to stock rom and factory defaults, wouldn't it?
Click to expand...
Click to collapse
If you are running CM7 at the moment, stock ROM won't magically appear just because you did lock/unlock.
It will sure wipe data/SD clean, but stock ROM can't just pop up out of no where
Stanlehh said:
not sure, need someone to clarify this.
Click to expand...
Click to collapse
Just format your /system partition, wipe data/factory reset, wipe dalvik, then install 2.3.4 full ROM. To make CWM stick, you have 2 options
1) Without rebooting after you flashed 2.3.4, stay in CWM, use adb
Code:
adb remount
adb root
adb shell mv /system/etc/install-recovery.sh{,.bak}
or you can delete it if you want...I did
adb shell rm /system/etc/install-recovery.sh
2) Root -> reboot -> install ROM Manager -> install CWM -> delete/move /system/etc/install-recovery.sh

[Q] JB update and custom kernel

Hi all,
I'm sorry about my stupid question but I really don't know nothing about that . I had rooted and flashed my NS and installed the matr1x kernel (very good btw), and now I knew that JB will be available to NS. My question is, need I back to stock kernel to receive the update?
Thanks
Sent from my Nexus S using xda app-developers app

Gnng
You have to understand that installing an OTA (official update) on a rooted device regardless of what kernel can cause problems, as it did with my Nexus S before. I suggest you make a NANDroid backup at all times before you install any ROMs, official or Custom. You can also use Titanium backup and others.
There's still a slight while until the new JB 4.1 comes out. It's suggested that you install a Custom JB 4.1 ROM for your Nexus S as though you don't cause any problems. I think it's OK if you do it with the kernel pre-installed. But people always install the Custom ROM THEN they install the Kernel, I think installing a new ROM always overwrites the kernel, if it comes with it.
EDIT:
In short, wait for the JB Custom ROM and you don't have to revert back to stock kernel, when you do the update it will automatically overwrite. Most Custom ROMs come with Stock/ordinary kernels. So then the user can flash whatever kernel they like in your case, matr1x.
Wish you the best of luck, and I am waiting for the Nexus S JB to come out as soon as possible

Ota binary patches the boot image iirc. So it can get all messed up.
Sent from my Samsung Epic 4G using Tapatalk 2

Yeah, what he said!
MДЯCЦSДИT said:
Ota binary patches the boot image iirc. So it can get all messed up.
Click to expand...
Click to collapse

andezzat,
Thank you very much for the help.
andezzat said:
Gnng
You have to understand that installing an OTA (official update) on a rooted device regardless of what kernel can cause problems, as it did with my Nexus S before. I suggest you make a NANDroid backup at all times before you install any ROMs, official or Custom. You can also use Titanium backup and others.
Click to expand...
Click to collapse
I didn't any backup before flashing a new kernel :crying:, so what can I do now if I want my stock kernel back?? What's a NANDroid (I know that is a tool but how can I do it?) ? Is Titanium bkp easily?
There's still a slight while until the new JB 4.1 comes out. It's suggested that you install a Custom JB 4.1 ROM for your Nexus S as though you don't cause any problems. I think it's OK if you do it with the kernel pre-installed. But people always install the Custom ROM THEN they install the Kernel, I think installing a new ROM always overwrites the kernel, if it comes with it.
Click to expand...
Click to collapse
I prefer wait for stock JB Rom and probaby I'll , but, can I already find some JB ROM?
In short, wait for the JB Custom ROM and you don't have to revert back to stock kernel, when you do the update it will automatically overwrite. Most Custom ROMs come with Stock/ordinary kernels. So then the user can flash whatever kernel they like in your case, matr1x.
Click to expand...
Click to collapse
I don't need to remove the kernel even unroot my cell, alright?
Thank you!!

Gnng said:
I didn't any backup before flashing a new kernel :crying:, so what can I do now if I want my stock kernel back?? What's a NANDroid (I know that is a tool but how can I do it?) ? Is Titanium bkp easily?
Click to expand...
Click to collapse
A NANDroid backup is a internal memory backup. You can create one by booting into Recovery (Power off your phone and Hold Power and Down on your volume buttons.) If you rooted your phone and unlocked your bootloader (that's what you had to do to flash a new kernel), you should be able to load ClockworkMod or TeamWin Recovery and do a backup of your phone.
Gnng said:
I prefer wait for stock JB Rom and probaby I'll , but, can I already find some JB ROM?
Click to expand...
Click to collapse
There's one rom but it's a port from the SDK and the amount of major bugs is high so it's not recommended but you could try another custom rom meanwhile, I can't go back to stock after trying custom roms, like AOKP and Cyanogenmod 9. Make sure you backup your apps and some settings (not everything will be compatible between stock and custom so pay close attention to which system setting you'll backup) with Titanium Backup.

To sum it all up for you
There's a Jelly Bean release which is unstable and has no sound, and will not be fixed until the REAL version comes out.
NANDroid backs up the whole internal memory on the phone including the system, it can be done from clockworkmod recovery.
Titanium backup, backs up specific settings and information that you choose, available from the playstore.
You don't need to unroot or go back to a STOCK kernel in order to flash a CUSTOM ROM. DO not however flash a STOCK rom after rooting, as at times that can cause problems.
If you want to go back to a STOCK ROM after rooting a device, there's a way, check this guide
http://forum.xda-developers.com/showthread.php?t=1063664
and choose your Nexus S model: To acquire model, go to Settings - About - Baseband version. if it says I9023 at the start that's your Nexus S's model
Choose one of the Fastboot Stock ROMs and use the Fastboot method to flash the ROM. That is a good way to go back to STOCK ROM if anything bad happens
By the way you should expect the new OTA official 4.1 update for the Nexus S to be on your model's page.
NOTE: Using Fastboot to flash a ROM is very clean. However this will delete all your data and if you do everything correctly will lock your bootloader and unroot your phone. So use Fastboot only when you really feel the need to.
Cheers
and stay tuned for Jelly Bean :victory:

andezzat said:
To sum it all up for you
You don't need to unroot or go back to a STOCK kernel in order to flash a CUSTOM ROM. DO not however flash a STOCK rom after rooting, as at times that can cause problems.
Click to expand...
Click to collapse
That means, when I receive the official 4.1 update notification, I should unroot my phone first and just install it after?

Gnng said:
That means, when I receive the official 4.1 update notification, I should unroot my phone first and just install it after?
Click to expand...
Click to collapse
OK first off, do not install the update using the system update method from about, as that is a 100% stuff up if you're still rooted or on a Custom ROM.
However to update I think flashing a stock ROM but USING Clockworkmod works fine!
Someone please confirm, as I am not 100% sure
However what I am sure about is that if you run into any troubles installing your STOCK ROM using Fastboot is very very good and clean, however there are 2 things:
1. You will wipe everything COMPLETELY
2. You need the ROM to be in a fastboot format kind of way for you to flash it
There's a guide and everything for fastboot.
---------- Post added at 12:35 AM ---------- Previous post was at 12:33 AM ----------
Personally I will wait for a custom ROM for 4.1 if it doesn't take too long as that's guaranteed and will obviously be faster and safer to install on a ROOTED device.
Someone still confirm if installing Stock ROM while over Custom ROM while ROOTED through CWM is OK or not!?

Hummm, ok...
I'm already using the Stock ROM, I just flashed a new kernel, and I prefer install the stock kernel and unroot my phone. Just to let it clean.
After I install the JB official update, maybe I flash and root again, depends of Google :laugh:
Do you know where can I download a trust official 4.0.4 kernel from the forums? My phone is a Nexus S I9020AUCKJ1, Version Number: IMM76D
Thanks!!!

Rooting Nexus S [Help]

A while back, I always rooted and unrooted my Nexus S with no problems at all. Now whenever I try to root it, it just goes wrong. I've tried TWRP & CWM, CWM used to always work but now it just messes up. Both TWRP and CWM both give me an error that say Installation Aborted when I try to install a custom rom. I've redownloaded the rom from different browsers and even different PCs but nothing working, still that same error. Does anyone have a guide that is 100% to work without any errors during the process?

What guide are you using?

paul96 said:
What guide are you using?
Click to expand...
Click to collapse
I used this one: http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/

1. Make sure you're running one the more recent versions of the custom recovery. You probably are but there are issues with older versions so just make sure.
2. Boot into what ever recovery you pick and do a full wipe. That is everything gets wiped but your SD card. Factory reset. Format /system etc.
3. Flash your ROM and gapps if they are seperate.
You should not get any errors. If your recovery is current and your flashing a new rom onto a fully wiped system and you still get a error either you're screwing something up or you may have a hardware problem.
To rule out a hw problem flash the factory images with fastboot. If those flash normally and everything works it is almost certainly user error.

albundy2010 said:
1. Make sure you're running one the more recent versions of the custom recovery. You probably are but there are issues with older versions so just make sure.
2. Boot into what ever recovery you pick and do a full wipe. That is everything gets wiped but your SD card. Factory reset. Format /system etc.
3. Flash your ROM and gapps if they are seperate.
You should not get any errors. If your recovery is current and your flashing a new rom onto a fully wiped system and you still get a error either you're screwing something up or you may have a hardware problem.
To rule out a hw problem flash the factory images with fastboot. If those flash normally and everything works it is almost certainly user error.
Click to expand...
Click to collapse
Alright, thanks Do you recommend that I root my Nexus S or should I wait for the Jelly Bean update? I've rooted before and I enjoyed it but now I don't see that many reasons to root, do you have any good reasons?

I have many. My reasons for root don't matter. If you don't have a reason for root then don't root. Its that simple really.
Make sure you're on a stock 4.0.4 rom. When the ota is out install it.
If you want just root on either os at any time just flash su.zip from custom recovery. Its that simple. Having root on a stock rom does not affect the ota process.

albundy2010 said:
I have many. My reasons for root don't matter. If you don't have a reason for root then don't root. Its that simple really.
Make sure you're on a stock 4.0.4 rom. When the ota is out install it.
If you want just root on either os at any time just flash su.zip from custom recovery. Its that simple. Having root on a stock rom does not affect the ota process.
Click to expand...
Click to collapse
What are your reasons for root? Please share?

Getting rid of stuff I don't want in a ROM.
Apps that do things that require root.Titanium backup/autoruns adaway ( ad blocker app alone could be its one point) etc
Changing kernel settings. Bid/bin clocks volts etc.
Being able to have a replacement launcher use the ICS style widget drawer.
Lastly , I simply just can't see having a computer that I don't have root/admin rights to. Its my damn device and I do what I want.

albundy2010 said:
Getting rid of stuff I don't want in a ROM.
Apps that do things that require root.Titanium backup/autoruns adaway ( ad blocker app alone could be its one point) etc
Changing kernel settings. Bid/bin clocks volts etc.
Being able to have a replacement launcher use the ICS style widget drawer.
Lastly , I simply just can't see having a computer that I don't have root/admin rights to. Its my damn device and I do what I want.
Click to expand...
Click to collapse
Oh cool. There is this project that some members from XDA are working on called Sense4All and they are porting Sense to many devices. Im probably going to wait until a fully functionable release is available for the Nexus S. I do like AOKP a lot, so that might be a reason for why I'll root.

You seem to be a little confused with some terms. Root is simply being able to grant superuser permission.
You don't need to root to flash a custom rom on a nexus. Just a unblocked bootloader. You could run aokp or any other rom without root if you wanted to.

albundy2010 said:
You seem to be a little confused with some terms. Root is simply being able to grant superuser permission.
You don't need to root to flash a custom rom on a nexus. Just a unblocked bootloader. You could run aokp or any other rom without root if you wanted to.
Click to expand...
Click to collapse
Oh, I never knew that, haha. Is it possible to flash a custom kernel with an unlocked bootloader or does that require root access?

m1l4droid said:
No you just need a custom recovery. But using that kernel's mods, like BLN, OC, UV, touchwake, etc, requires apps that need root, like NSTools, SetCPU, etc.
Click to expand...
Click to collapse
Oh alright. Now I really wanna root + install a custom rom. Do any of you have a full 100% fully working guide for rooting Nexus S and which rom should I flash first? I already know what kernel I want.

http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0

leap_ahead said:
http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0
Click to expand...
Click to collapse
Thank you so much! I rooted my phone with CWM recovery installed and Paranoid Android + gapps installed

Flashing different roms, whats the deal???

Ok so i've finally decided im ready to unlock and flash. My question is this: whats the deal with returning to stock and redoing everything on certain roms? Can anyone explain to me the variables here?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

once you have your device rooted and have a recovery installed, make a nandroid back up your stock rom, flash whatever rom you want, then if you need to go back to stock rom, just flash the nandroid back up you made. If you want to go 100%, then you will have to find the stock recovery image, and flash that over your custom recovery as well, then just use OTA Rootkeeper... and temp unroot your phone... and viola, your 100% stock again.... but if you plan to go back to 100% stock then DO NOT UNLOCK YOUR BOOTLOADER!! there is no way to lock it again once you unlock it.

I think it's worth while to note
currently the only custom recovery that is able to flash stock is CWM
TWRP is not able to flash a stock rom

KAD79 said:
I think it's worth while to note
currently the only custom recovery that is able to flash stock is CWM
TWRP is not able to flash a stock rom
Click to expand...
Click to collapse
If you flash a stock ROM using CWM you will lose all data on your device, including any backups you made using CWM. So be sure to backup those files to your PC (they're located in the clockworkmod/backup folder of your internal storage) before flashing the stock Asus ROM.
I've been changing my ROM's throughout the day and have basically memorized the process of flashing CWM, root, and ROM's by now

KAD79 said:
I think it's worth while to note
currently the only custom recovery that is able to flash stock is CWM
TWRP is not able to flash a stock rom
Click to expand...
Click to collapse
TWRP can flash stock. I've done it.
Sent from my SGH-I897 using xda premium

Ive read about problems reflashing ROMs when youre on the CM or AOKP. Need to return to stock, then flash other ROMs, dunno why exactly. So is it enough just to restore my stock nand backup or do I need to do something differently? :good:

This is exactly what im talking about. What are the rules when coming from cyan to a stock flavor?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

So lets say right now im ready to unlock and root. I would want to unlock the device, then root, then flash CWM (not twrp) so i could still retrain (and boot in to without reinstalling) my original rom? Because i still want to titanium my apps.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

not sure if I understand your question right, but yeah you can use your stock rom when you root or flash cwm. Untill you wont wipe anything within CWM, theres no reason you coulndt use it. But dont forget to do backup of your stock mate.

I think part of the confusion is defining what "stock" means, and I've got two different views on it over the past few days:
COMPLETE STOCK means flashing ASUS' original stock firmware, which completely wipes out everything on your tablet (including your nandroid backups) and CWM and takes you back to a fully stock tablet (except it will still have unlocked bootloader). From here, if you want to install ROM's like CleanROM or Hydro you have to re-flash CWM each time, then flash the appropriate ROM.
MODIFIED STOCK would be making a nandroid backup of your stock settings as soon as you flash the stock ROM, install CWM, then back it up and you can revert to it accordingly. I don't know if this would break things when you tried to flash Clean/Hydro and so maybe someone can clarify.
I wanted to try both hydro and cleanrom so I spent many hours yesterday flashing between stock/modified stock. Its kind of a pain, but all part of the learning process.
And one thing I want to note both for myself and for anyone else: if you flash stock without removing CWM it'll give you the broken bootloader logo (android on his back w/ exclamation point), and my solution has just been to do a 'wipe data' from the fastboot menu and the stock will work fine. What I mean by this is I've done this at least three times, where I flash STOCK from within CWM and when I try to boot into recovery, I'll get that android. That's because STOCK completely erases everything including CWM so in order to restore the normal operating procedure, you just need to 'wipe data' from within the tablet.
Hope my understanding of these situations is correct, if not anyone can feel free to correct me

People like to experiment with their tablet, they get easily bored with the same thing.
So they go back to stock and flash another rom like Hydro which is stock based because when you flash CM or AOKP it won't let you just flash to Hydro.

KAD79 said:
I think it's worth while to note
currently the only custom recovery that is able to flash stock is CWM
TWRP is not able to flash a stock rom
Click to expand...
Click to collapse
NOT TRUE!
It should be noted that TWRP is now more functional than CWM. TWRP can now flash stock ROMs just fine. It can now restore complete nandroids, including /boot, and it can now flash from and store to the external SD card. It was just recently updated for this, which is why all the information until now has said to use CWM to flash the stock ROM. So, go ahead and use TWRP. It's perfect now.

[Q] Restoring through CWM to stock

hi,i am using stock rom running 4.0.4,i had it rooted too and now i had two queries
1)Is rom manager compatible with Atrix 2??
im asking this because when i open it, it shows u need to install CWM recovery...but no option in that responds...not even intall cwm (1st option in menu)....so i installed CWM using atrix boot strapper app and now still rom manager is not detecting CWM..please help
2)after installing CWM, i had backup my present stock rom..so if i flash a new rom now will that CWM and back up still exist??(because we will wipe data which will remove everyhting right??)
for suppose if i flash jelly bean rom and if i dont like it...can i restore my previous stock rom without bricking my device??
thanks for u r help

vdpraneeth said:
hi,i am using stock rom running 4.0.4,i had it rooted too and now i had two queries
1)Is rom manager compatible with Atrix 2??
im asking this because when i open it, it shows u need to install CWM recovery...but no option in that responds...not even intall cwm (1st option in menu)....so i installed CWM using atrix boot strapper app and now still rom manager is not detecting CWM..please help
2)after installing CWM, i had backup my present stock rom..so if i flash a new rom now will that CWM and back up still exist??(because we will wipe data which will remove everyhting right??)
for suppose if i flash jelly bean rom and if i dont like it...can i restore my previous stock rom without bricking my device??
thanks for u r help
Click to expand...
Click to collapse
1) Rom manager is not compatible with Atrix 2. I would not use it. Why do you need it anyway??
You can use Atrix Bootstrapper to go into CWM recovery . Rest can be done there. Or you can use Boot Menu Manager.
2)Of course! it will still be there! the backup is saved on your SD Card. So as long as you don't format your SD Card. It will be there.

NHS2008 said:
1) Rom manager is not compatible with Atrix 2. I would not use it. Why do you need it anyway??
You can use Atrix Bootstrapper to go into CWM recovery . Rest can be done there. Or you can use Boot Menu Manager.
2)Of course! it will still be there! the backup is saved on your SD Card. So as long as you don't format your SD Card. It will be there.
Click to expand...
Click to collapse
Rom Manager does work with Atrix2. If you're on Stock ICS, you can install CWM on every boot, then flash the Bionic recovery through Rom Manager. That will allow you to use the 1 touch backup in RM, just hit backup rom and everything does what it's supposed to.
Here is the CWM on every boot for Stock ICS.

NHS2008 said:
1) Rom manager is not compatible with Atrix 2. I would not use it. Why do you need it anyway??
You can use Atrix Bootstrapper to go into CWM recovery . Rest can be done there. Or you can use Boot Menu Manager.
2)Of course! it will still be there! the backup is saved on your SD Card. So as long as you don't format your SD Card. It will be there.
Click to expand...
Click to collapse
2)will the CWM recovery exist after flashing new rom or i need to install it again??
when i restore to stock fom JB, it means downgrading the firmware right??
so will there be a chance of bricking or is it same to restore anytime from any version??

vdpraneeth said:
2)will the CWM recovery exist after flashing new rom or i need to install it again??
when i restore to stock fom JB, it means downgrading the firmware right??
so will there be a chance of bricking or is it same to restore anytime from any version??
Click to expand...
Click to collapse
No, your Recovery will be wiped after you flash a new rom, but you can install it again and restore your ROM.
But when restoring a rom, make sure you ARE ON THE ROM you are restoring.
E.g. If you flash JB and want Stock ICS back with your backup. First flash the Stock ICS from RSD and then restore your backup from CWM on it.
Or Vice-Versa.
@41rw4lk, Thanks for rectifying that. I did not bother with Rom Manager much.

NHS2008 said:
No, your Recovery will be wiped after you flash a new rom, but you can install it again and restore your ROM.
But when restoring a rom, make sure you ARE ON THE ROM you are restoring.
E.g. If you flash JB and want Stock ICS back with your backup. First flash the Stock ICS from RSD and then restore your backup from CWM on it.
Or Vice-Versa.
@41rw4lk, Thanks for rectifying that. I did not bother with Rom Manager much.
Click to expand...
Click to collapse
but downgrading to stock ICS from JB will brick my mobile right??
is there any problem if im not on the rom im restoring??
(im a newbie and i dont know much..even not found these after searching a lot..thats the reason im asking all these)

41rw4lk said:
Rom Manager does work with Atrix2. If you're on Stock ICS, you can install CWM on every boot, then flash the Bionic recovery through Rom Manager. That will allow you to use the 1 touch backup in RM, just hit backup rom and everything does what it's supposed to.
Here is the CWM on every boot for Stock ICS.
Click to expand...
Click to collapse
how is it possible to flash bionic recovery through RM...all the menu options are disabled for me there even after CWM installed through bootstrap

vdpraneeth said:
2)will the CWM recovery exist after flashing new rom or i need to install it again??
when i restore to stock fom JB, it means downgrading the firmware right??
so will there be a chance of bricking or is it same to restore anytime from any version??
Click to expand...
Click to collapse
I don't think any recovery exist after flashing a new rom. We have a locked bootloader, so we can't replace the stock recovery.img, all of our recoveries hijack the boot process to work. CM10 and PA I believe have a built in recovery, and that's about as close as you'll get to having a recovery exist after flashing a rom.
As far as restoring from JB, I believe you can downgrade to ICS, but you'll have to look at the JB thread to be certain. I'm on AT&T so I haven't had an opportunity to try JB (officially). CM10 is based on JB, but for our phone with the locked bootloader, it's more of a pseudo experience and is based on our ICS framework.
As for bricking, there is always a chance to brick, that's part of the mod game, but if you read and pay attention to what you have and what you're doing, you'll be alright.

vdpraneeth said:
but downgrading to stock ICS from JB will brick my mobile right??
is there any problem if im not on the rom im restoring??
(im a newbie and i dont know much..even not found these after searching a lot..thats the reason im asking all these)
Click to expand...
Click to collapse
UNLESS you have AT&T phone you should be just fine with ref lashing the ICS.
YES. there is a big problem if you are not on a ROM you are restoring.
Its like you are trying to comlete your jigsaw puzzle by putting pieces from some another jigsaw puzzle.

vdpraneeth said:
how is it possible to flash bionic recovery through RM...all the menu options are disabled for me there even after CWM installed through bootstrap
Click to expand...
Click to collapse
You need to use the CWM on every boot setup, the Atrix2Bootstrap alone won't do.

41rw4lk said:
You need to use the CWM on every boot setup, the Atrix2Bootstrap alone won't do.
Click to expand...
Click to collapse
yes...my phone is an AT&T version...though im using it with IDEA.....
so if i install CWM on every boot,then rom manager will detect it and work right??

vdpraneeth said:
yes...my phone is an AT&T version...though im using it with IDEA.....
so if i install CWM on every boot,then rom manager will detect it and work right??
Click to expand...
Click to collapse
Yes. I will say though, if you're on an AT&T branded phone with AT&T firmware, do NOT try to flash the new JB FXZ. It doesn't matter who your carrier is, it matters what firmware your phone is using. So, if you're on AT&T then you need to make sure that the things you flash are for AT&T, or else you will brick and that will be then end of that.

41rw4lk said:
Yes. I will say though, if you're on an AT&T branded phone with AT&T firmware, do NOT try to flash the new JB FXZ. It doesn't matter who your carrier is, it matters what firmware your phone is using. So, if you're on AT&T then you need to make sure that the things you flash are for AT&T, or else you will brick and that will be then end of that.
Click to expand...
Click to collapse
thanks a lot...
what are the ROMS avaialble for us???
can i reflash stock ICS from any of those ROMS safely??
thank you

vdpraneeth said:
thanks a lot...
what are the ROMS avaialble for us???
can i reflash stock ICS from any of those ROMS safely??
thank you
Click to expand...
Click to collapse
CM10
PA
Numa
MIUI (had battery issues, but I think they got it all worked out)
there's a few, you'll just have to look. Most of the time, if something is not meant for AT&T, the devs will post in the description that it isn't compatible. If you want stock ICS back at anytime, you can do yourself a favor and make a backup of your stock ICS all setup the way you like it, so you can restore if needed. If all else fails, there is an Official ICS FXZ that will get you back to stock ICS.

41rw4lk said:
CM10
PA
Numa
MIUI (had battery issues, but I think they got it all worked out)
there's a few, you'll just have to look. Most of the time, if something is not meant for AT&T, the devs will post in the description that it isn't compatible. If you want stock ICS back at anytime, you can do yourself a favor and make a backup of your stock ICS all setup the way you like it, so you can restore if needed. If all else fails, there is an Official ICS FXZ that will get you back to stock ICS.
Click to expand...
Click to collapse
my main question is :
will downgrade to ICS cause brick??
how do i create my own backup for stock ICS??

vdpraneeth said:
my main question is :
will downgrade to ICS cause brick??
how do i create my own backup for stock ICS??
Click to expand...
Click to collapse
You're killing me smalls. You're on ICS already, you're not downgrading anything, nor can you downgrade ie. Gingerbread. There is no Official JB for AT&T, so that's not an issue. CM10 is a JB based rom built on an ICS frame, (for our phone at least), and again, you're not downgrading.
To make a back up, boot in to CWM or whatever recovery you're using (not stock), and click backup. You might hit up the noob thread to get an idea of the terminology and basics for our device. Not trying to be rude, but you're running yourself in circles. You got to walk before you can run.