Hi all,
I have a friend with an AT&T Atrix 4G. I've had a Droid X and current have a Galaxy Nexus & Nexus 7. I did everything you could do to the X and know my way around the Nexus very well; the atrix is a little confusing to me. moto-fastboot and the idea that SBFing is bad are new concepts to me. On the Droid X, if you were in trouble, you just SBF'd.
My friend had some trouble with his Atrix the other day, he was stuck at the splash screen, we got it half way fixed and he was in a bootloop, and eventually we got a version of CM9 on there: 9.0.0-rco-atrix-kang. The phone is running now but the ROM is unstable. I'd like to know how to safely downgrade to a CM7 ROM. Is it as simple as booting into recovery, wiping, and flashing the earlier rom? Something blur based would be ideal at this point as he's just looking to have a stable phone back. He got into rooting/ roming on his own so I'm not sure what updates, if any, were on there before he started. Is there an easy way to check and see which bootloader version he's on, find out which SBF we can safely use, etc? He does have it unlocked, so that should make things easier (or maybe harder, this Atrix really is a mystery to me...).
TL;DR - How do you safely downgrade an Atrix 4G from CM9 to CM7 and which recovery is the best to be using?
I used to switch between CM10 and CM7 all the time, if the phone is rooted and bootloader is unlocked, it's as simple as wiping data/cache, wiping dalvik, format system, install ROM, boot, reboot, install gapps.
Did your friend follow directions and make a nandroid of original before wiping? That would be the simplest way.
エイトリックス から 送ります
He said he had a backup but that when he restored it it was bootlooping. I'm assuming it was some kind of issue with switching recoveries or something like that. With the Droid X there was a recovery for 2nd-init roms and a recovery for blur roms. With the Nexuses it's mostly TWRP or CWM but as long as you're on the latest you can flash anything. Is there any reason to downgrade recoveries on the Atrix? Is there one "up to date" recovery? I see a lot of posts that point to a 2011 thread with the "latest CWM based recovery" but that seems kind of old...
Alright so I think I have this sorted out for the most part, and my understanding is that RomRacer made a version of CWM that we should be using on the Atrix. I just can't find a link to download the thing, is there a thread in development? When I search all I find is a ton of threads telling me to use it and no one linking it.
Edit: http://forum.xda-developers.com/showthread.php?t=1204500 Right?
Or is TWRP better?
http://teamw.in/project/twrp2/72
Lot of people love TWRP, but I'm one of the few that still uses RomRacers CWM 5.0.2.7 (I think) and no issues flashing CM10.1 (android 4.2.1) Had it for over a year, and works great every time. If it's not broken, don't fix it.
As for the boot loop, those are usually fixed with a wipe. Try wiping everything and restoring.
Edit: Yeah, that seems like the proper thread. Sorry, haven't looked at it since I first rooted my phone. Try TWRP, most people swear by it. The touch does add a nice feature, but I'm too lazy to make the switch.
エイトリックス から 送ります
Once you have an unlocked BL and a custom recovery, switching between pretty much all ROMs is safe so long as you stay away from SBFs.
You can flash to stock rom and then install CM7 :laugh:
ravilov said:
Once you have an unlocked BL and a custom recovery, switching between pretty much all ROMs is safe so long as you stay away from SBFs.
Click to expand...
Click to collapse
Thanks for the help, I'm glad I checked in. On the Droid X whenever anything went wrong and someone posted a thread like this the first ten replies were "Just SBF" - that used to be safe, until they rolled out .621, but that was end-of-life anyway.
I digress; next time I see him we'll iron this out and he'll be off to the races. Thanks again.
Related
Hey guys, nice section you have here. I've been reading all about the Atrix and have a couple of questions to confirm what i'm assuming.
Oh yeah, is the Atrix and Atrix 4G the same? I'm assuming so as i've not seen different specs or sections for it here, just wanted to be 100000% sure as i've never owned an android phone!
If i keep the Bootloader locked, is it impossible for me to hard brick the device? Seeing as though i can't freely flash to a lower firmware? (not including things like upgrading to official firmware and running out of battery etc, that's a sure fire way of bricking
Click to expand...
Click to collapse
Just say i'm on 2.3.4 and i'm rooted and unlocked, if i flash CM7, can i reflash something like Alien or MIUI (when or if it gets ported) without ANY chance of a hard brick (AKA does it touch the bootloader and/or does it carry the risks which the flashing of a lower firmware does?)
Click to expand...
Click to collapse
Would LauncherPro and other theme programs be available across the wide range of ROMS as long as i'm rooted?
Click to expand...
Click to collapse
Thanks for your time guys, i'm busy reading up and watching the few videos on youtube (seriously, hardly anyone makes videos about this phone, what's up with that? ) I do have a cold right about now so will take a rest but i can't sleep knowing that i may soon be getting this phone (if my order for a Samsung Galaxy S (1) is not accepted by Vodafone and their stringent credit checks!)
Thanks again guys, hope to see you around soon!
The phone will be on T-Mobile in the UK. Hopefully!
First and last bump! I was wondering if installing LauncherPro would have any negative effects on the speed of the phone? It's dual core and has 1gb ram so i'm thinking the new launcher would not cause any lag but has anyone tried this and found out that it does indeed lag?
No not impossible, i would think it would be easier to brick with a locked bl.
Yes you can reflash, and no you won't get the "lower fw brick".
Yes you can use other launchers, always.
Thanks a lot mate.
To expand on the 1st answer, is it because with the locked BL, i can't install CWM so technically if i brick, it'll be harder if not impossible to fix it? So in a way, an unlocked BL is safer then, as long as i don't try to downgrade? That sounds kinda awesome!
Also, after the first flash, is it easier to flash another rom or is it the same process? I mean, is the 1st flash always the hardest and longest? Because i'm thinking that the 1st time flash would have me install a lot of things, and the next time i reflash, i can use the things i already installed the 1st time (such as CWM etc) to flash another rom can't i? I just want to be able to swap between a few different ROMS without having to risk a hard brick! Thanks for your answers btw, really appreciate it
coolnow said:
Thanks a lot mate.
To expand on the 1st answer, is it because with the locked BL, i can't install CWM so technically if i brick, it'll be harder if not impossible to fix it? So in a way, an unlocked BL is safer then, as long as i don't try to downgrade? That sounds kinda awesome!
Also, after the first flash, is it easier to flash another rom or is it the same process? I mean, is the 1st flash always the hardest and longest? Because i'm thinking that the 1st time flash would have me install a lot of things, and the next time i reflash, i can use the things i already installed the 1st time (such as CWM etc) to flash another rom can't i? I just want to be able to swap between a few different ROMS without having to risk a hard brick! Thanks for your answers btw, really appreciate it
Click to expand...
Click to collapse
Thats right, the unlocked bootloader is the best way to go if you plan on flashing because of custom recovery.
Yes most likely its about the same process BUT, most if not all ROMs will have instructions on how to flash - make sure you read and follow them dont just "do what you did last time".
Prob the easiest way to swap between ROMs easily is to keep nandroid backups for them through cwm.
As far as it being easier to flash the next ROM because you can "keep things from the last flash".. NO you dont want to keep anything between flashing, meaning you should most likley always wipe data, cache & such unless otherwise specified (sometimes upgrading ROMs from one version to the next you can use a "no wipe" upgrade).
Thanks so much! Will install Nandroid asap when i get it! Also, i didn't mean "keep" things as in data and/or apps or cache or whatever, i meant like the 1st flashing would include installing CWM recovery, but the next time i reflash, i won't have to install that again, or would i? If not, then that's great!
Can't wait to try out Cyanogen Mod, theme it up, install some cool apps and just mess around with it! Bookmarked every section of the Atrix forum so i can easily read through it
Thank you for your time in helping a confused noob out I have read a lot of guides but without the phone in front of me, and me being completely new to this, it's not really sinking in. Once i get the phone physically in my hands, then i bet i'll learn a lot more!
coolnow said:
Thanks so much! Will install Nandroid asap when i get it! Also, i didn't mean "keep" things as in data and/or apps or cache or whatever, i meant like the 1st flashing would include installing CWM recovery, but the next time i reflash, i won't have to install that again, or would i? If not, then that's great!
Can't wait to try out Cyanogen Mod, theme it up, install some cool apps and just mess around with it! Bookmarked every section of the Atrix forum so i can easily read through it
Thank you for your time in helping a confused noob out I have read a lot of guides but without the phone in front of me, and me being completely new to this, it's not really sinking in. Once i get the phone physically in my hands, then i bet i'll learn a lot more!
Click to expand...
Click to collapse
Nandroid backup is a backup through CWM, it is not a seperate app. As far as having to install CWM each time.. No you wont have to, the recovery stays but it should be updated when available, unless stated otherwise. Rom Manager will install the latest version of CWM for you. Doing a backup in CWM is known as a Nandroid backup.
Right, i get it now, i was confusing it with Titanium Backup but i've looked at vids about it and know what it does now. Isn't it risky to read/write from NAND a lot? Hmm
Also, if i Nand backed up my stock firmware (before i flash anything), can i restore from there and return to that stock backup anytime i want? If that's possible then i'm sorted!
coolnow said:
Right, i get it now, i was confusing it with Titanium Backup but i've looked at vids about it and know what it does now. Isn't it risky to read/write from NAND a lot? Hmm
Also, if i Nand backed up my stock firmware (before i flash anything), can i restore from there and return to that stock backup anytime i want? If that's possible then i'm sorted!
Click to expand...
Click to collapse
I dont know of any risks to Nandroid backup, only benefits. I have returned to a Nandroid backup on my Captivate but not on the Atrix, i have created a Nandroid backup on (stock) Atrix and recommend do the same jic. I believe you can return to that stock back up (after flashing) if needed but first check out the section on fruitcakes, there is more info along these lines in that thread.
Reading the section now, makes little sense yet but i'm sure i'll understand. What they basically are are roms that don't touch the BL, so doesn't matter if its a lower firmware than the one i'm on because these fruitcakes don't look at the BL and will flash the firmware without bricking, whereas if i downgraded with a stock firmware or something, they touch the BL and will find out it's unlocked and on a newer firmware so the flashing ends up physically bricking the device. That's what i'm basically assuming. Also, read another thread where the OP said he recovered from a stock nandroid backup from a CM7 rom, which sounds a hell of a lot easier than downgrading carefully using special roms!
coolnow said:
Reading the section now, makes little sense yet but i'm sure i'll understand. What they basically are are roms that don't touch the BL, so doesn't matter if its a lower firmware than the one i'm on because these fruitcakes don't look at the BL and will flash the firmware without bricking, whereas if i downgraded with a stock firmware or something, they touch the BL and will find out it's unlocked and on a newer firmware so the flashing ends up physically bricking the device. That's what i'm basically assuming. Also, read another thread where the OP said he recovered from a stock nandroid backup from a CM7 rom, which sounds a hell of a lot easier than downgrading carefully using special roms!
Click to expand...
Click to collapse
Dont worry it makes more and more sense as you learn and play with it. Your assumption of fruitcakes is my understanding as well. I agree that nandroid backup/restore seams a slightly easier method than fruitcakes, but thought I would include the fruitcake methods for you seeing as how you were concerned of a risk with nand, plus the more reading the better. Also NandBacks do take up a good amount of storage space, but are worth it jic. As long as you read you should be just fine, reading here on xda is the best thing you can do to keep from screwing something up. Good luck.
Thank you mate, i really appreciate your time! If i wasn't so ill, i'd be understanding more i think, but i have to look away every few seconds or else my eyes will explode haha, i guess i'm not getting the Galaxy S anymore, i hope i don't regret it! And with the method of hiding the unlocked bootloader, i'm hoping IF anything bad happens, then i still have a chance of tricking the tricksters who gave us these locked down phones in the first place! Android was supposed to be free and open I'm just glad at the thought of getting rid of my iPhone 3g + iTunes + Quicktime.
Also, in your opinion, is ADW EX better than Launcher Pro?
Is it possible to Hellraise the SGSII (I'm assuming it is an i9100) Oxygen 2.3.2 ROM for our devices? I'm still unsure about all the compatibility issues, but I wanted to ask those who may know before doing something unbelievably dumb.
Well you should be able to use any i9100 rom as long as it can be flashed through CWM, and doesn't need ODIN to install it, i'm not familiar with Oxygen ROM though.
Only thing to be worried about is if the rom has bootloaders included. If it does, stay away.
Other than that, run a backup in cwm before you flash so if it does go bad, you have an easy recovery.
Sent from my páhhōniē
Yeah, I checked for the dreaded Sbl.bin and other assorted bootloaders. Just finished my backup, gonna give it a whirl.
Well, it appears as if I have answered that question, and the answer is "No." The installation keeps aborting, no matter what version I try.
You aren't attempting to install through ROM Manager are you? If so you need to boot into recovery yourself, full wipe, then install. I can't see many other reasons why the install would abort- If that is not the case i'm of no help lol.
No, I booted into recovery, did the various wipes, then tried to install the zip. I tried v2.3 and 2.3.2, with no luck. I'm guessing AdamG put some sort of verification script in to keep dumbass noobs like me from making big mistakes.
Thanks for the update
Sent from my páhhōniē
Oxygen is AOSP-derived, so you'd need to use the CM7 boot.img instead of a Samsung-derived kernel.
If Oxygen enforces device-checking via asserts, you may need to Hellraise an I9100 ROM first. (Although I'm going to be changing this behavior in Hellraiser soon to report the device as a 777.)
Ah, good to know. Well, no harm was done to any phones, so I will consider myself lucky and move on.
Sent from my SAMSUNG-SGH-I777 using xda premium
There is probably some ridiculous, overwhelmingly simple reason for the answer to this question, but take into account that its coming from the guy who has been trying install a ROM for a week unsuccessfully, Anyway, enough personal degradation for the moment, and on to business. It seems to me that every time I have to .spf it gets easier and faster(imagine that). RSDlite is such a perfect format flashing, so why has no one thought of a way to flash ROMS via RSDlite? I understand that getting your proverbial elbows greasy is the fun of this, but for the helpless and hopeless, such as myself, there should be a super simple segue into cool techy stuff for us too!! I'm kidding, I'm not that buried.....I think.
Why would you sbf a rom when it only only takes a couple of minutes to flash a rom?
1, are you rooted?
2, do you have tenfar bar installed?
3, is the rom of choice on SD card?
Where are you having your trouble what rom? How are you trying it? It is pretty simple.
MathiasKnight said:
There is probably some ridiculous, overwhelmingly simple reason for the answer to this question, but take into account that its coming from the guy who has been trying install a ROM for a week unsuccessfully, Anyway, enough personal degradation for the moment, and on to business. It seems to me that every time I have to .spf it gets easier and faster(imagine that). RSDlite is such a perfect format flashing, so why has no one thought of a way to flash ROMS via RSDlite? I understand that getting your proverbial elbows greasy is the fun of this, but for the helpless and hopeless, such as myself, there should be a super simple segue into cool techy stuff for us too!! I'm kidding, I'm not that buried.....I think.
Click to expand...
Click to collapse
Okay, looks like you created a new thread about the same issue...but moving on.
RSD Lite is a Motorola tool, that was initially just supposed to be used by retailers (like VZW and Radioshack) so that they could reset people's phones rather than having to ship the to Moto and send them back to the customer, or for VZW and others to wipe devices and resell them as "refurbished" units. The reason we can't use RSD to create ROM's is the SBF files are signed by Motorola. So if we were to modify them in anyway or try to make our own, it would refuse the files and not flash the device.
Now, from your other thread you posted this:
MathiasKnight said:
Sorry about that, I must have been excited. Unfortunately I spoke too soon. Either that or I'm not meant for this, which I hope is not the case seeing that I'm getting my degree in IT. I finally get bootloader, with ROM and GAPPS placed accordingly(I opted for Eclipse). When the zip is finished uploading and I see confirmation that all was installed correctly, I begin the reboot......and it takes new to an unactivated Droid X2. I've created nandroid after nandroid, with different methods and different ROMS, and I either land there or with a signature error, even in bootstrap. I'm gonna try one more time before I hang up my guns. Maybe.....
Click to expand...
Click to collapse
Could you please outline everything you do, step by step? After you SBF you should have to activate your phone anyway, so that after you root, install bootstrap and then boot into that and apply the ROM and GAPPs the phone should already be activated.
Travisdroidx2 said:
Why would you sbf a rom when it only only takes a couple of minutes to flash a rom?
1, are you rooted?
2, do you have tenfar bar installed?
3, is the rom of choice on SD card?
Where are you having your trouble what rom? How are you trying it? It is pretty simple.
Click to expand...
Click to collapse
The only time I have gotten any response that remotely resembled success was the first time I used System Recovery, but the status bar was incredibly slow, like not moving basically, so I figured after about 25 minutes something was amiss...again. Yes I'm rooted, don't know what a tenfar bar is yet but I'm on it now, and I've got a variety of .zip's that are supposed to be compatible with 2.3.4, and I'm sure they are. I was really kind of joking about the .sbf, but I still think it would be a viable alternative.
MathiasKnight said:
The only time I have gotten any response that remotely resembled success was the first time I used System Recovery, but the status bar was incredibly slow, like not moving basically, so I figured after about 25 minutes something was amiss...again. Yes I'm rooted, don't know what a tenfar bar is yet but I'm on it now, and I've got a variety of .zip's that are supposed to be compatible with 2.3.4, and I'm sure they are. I was really kind of joking about the .sbf, but I still think it would be a viable alternative.
Click to expand...
Click to collapse
Okay, so you've SBF'd to 2.3.4. Rooted using whatever method, and you have the BootStrap recovery installed yes? Then you boot into recovery, wiped data, wiped cache and wiped dalvik cache, then tried installing a zipped ROM from you sd card, and upon restarting you get stuck at the moto M screen?
A couple things. First, when you wipe the dalvik cache (for roms or any mods) the phone has to rebuild that before it can actually boot into Android. This can take anywhere from a few minutes to 5 minutes or upwards. If you've gone 10 minutes and still nothing, all you need to do is pull the battery (so the phone powers off), reinstall the battery, DONT TURN THE PHONE ON, and then plug your phone into your wallcharger. After you plug in your phone, it'll turn itself on, go to the M screen and then go back into the BootStrapRecovery. From there you can redo the steps, wipe everything and then reinstall. However, IF you boot into the stock Android Recovery and wipe cache and data from there, you mucked it up and you'll have to SBF and restart the process.
ALSO, from your previous thread you said you were trying to install Eclipse. What version are you trying? 1.xx eclipse will work on 2.3.4, but Eclipse 2.xx will only work on 2.3.5, which could be another reason you are having issues.
I got rid of CWM Recovery the other day...Got into a Soft Brick using it...Not sure how it happened ...But got out of it none the least using the 1a Method from here...Loaded up TWRP...I would just like to know if I can flash any Rom using it ...It recomends 4 compatible ones...So Im just wondering if I can flash CM 9 or Virtuous...Or am I lookin at a Brick again if I do so...
Im currently runnin Gummy's which I really like but Im a Flashaholic...at least with my S2...And I know Ill do the same with the Prime...So just checkin ...
BTW never had a problem with CWM on my S2...And I flashed a Ton of Roms...Specifically ICS...
ronny71 said:
I got rid of CWM Recovery the other day...Got into a Soft Brick using it...Not sure how it happened ...But got out of it none the least using the 1a Method from here...Loaded up TWRP...I would just like to know if I can flash any Rom using it ...It recomends 4 compatible ones...So Im just wondering if I can flash CM 9 or Virtuous...Or am I lookin at a Brick again if I do so...
Im currently runnin Gummy's which I really like but Im a Flashaholic...at least with my S2...And I know Ill do the same with the Prime...So just checkin ...
BTW never had a problem with CWM on my S2...And I flashed a Ton of Roms...Specifically ICS...
Click to expand...
Click to collapse
There's a custom CWM recovery a guy posted that's supposed to have that issue fixed. I haven't tested it to a different problem with writing to my partition that's just due to an issue my prime had from the previous owner borking something. Recoveries are different on every device. I used CWM exclusively on my Thunderbolt, then I got the rezound and CWM wasn't worth having when it first came out officially, I only run Amon RA on there.
I also had the 1a "brick" which really wasn't anything more than a recovery loop. I've been using TWRP and I'm a flashaholic, and with Gummy, EOS, a CM9 build and AOKP plus a bunch of misc zip files I haven't had any problems with it. If you want me to test something let me know, I'm not at all scared to wipe a device as setup doesn't take me long at all
CharliesTheMan said:
There's a custom CWM recovery a guy posted that's supposed to have that issue fixed. I haven't tested it to a different problem with writing to my partition that's just due to an issue my prime had from the previous owner borking something. Recoveries are different on every device. I used CWM exclusively on my Thunderbolt, then I got the rezound and CWM wasn't worth having when it first came out officially, I only run Amon RA on there.
I also had the 1a "brick" which really wasn't anything more than a recovery loop. I've been using TWRP and I'm a flashaholic, and with Gummy, EOS, a CM9 build and AOKP plus a bunch of misc zip files I haven't had any problems with it. If you want me to test something let me know, I'm not at all scared to wipe a device as setup doesn't take me long at all
Click to expand...
Click to collapse
With the Galaxy s2 that I have I run CWM all the time...On Gingerbread Builds ...never a problem...On strictly ICS builds...never a problem...The problem came from flipping back and forth from GB to ICS...I had 3 soft bricks but got out thru Odin...Now with the newer versions of ICS builds you have to flash a different kernel or Odin it inorder to use CWM...thats to play it safe because there are enuff Hard Bricks that shows a problem...(Sumthin to do with The Framework in the newre ICS Roms)...So Im just careful when I flash...Don't need a Hard Brick...Im gonna stay away from CWM over here...especially the Touch Versions which gave us the first initial problems when flashin with CWM on the XDA Galaxy Forum here...
So Ill be usin TWRP and if its safe to flash the Roms you mention I should be okay...But like you state...every device is different...Ill just try to be careful and keep readin on here and see where the Bricks are cummin from when they occur...Thanx alot for the response...I appreciate it...
Hi, I am looking around for a ROM to install on a friends device and I noticed that the only tutorial I found for this phone is with the BootManager. Does that mean that is the only way to flash a new ROM?
Can I just install CWM through fastboot and install a ROM through recovery?
Do I need to unlock the bootloader on this device?
Thanks in advance. Sorry for the stupid questions but I have never had a Motorola device and am not familiar with the procedures.
nebrando said:
Hi, I am looking around for a ROM to install on a friends device and I noticed that the only tutorial I found for this phone is with the BootManager. Does that mean that is the only way to flash a new ROM?
Can I just install CWM through fastboot and install a ROM through recovery?
Do I need to unlock the bootloader on this device?
Thanks in advance. Sorry for the stupid questions but I have never had a Motorola device and am not familiar with the procedures.
Click to expand...
Click to collapse
The bootloader on the Motorola RAZR is not unlockable.
I've flashed custom ROMs using both SafeStrap and BootMenu (my favourite is BootMenu, here's a link for more info on it: http://forum.xda-developers.com/showthread.php?t=1720351)
The neat thing about the RAZR is that it can be dual-booted using either of these recoveries. I am running both Eclipse ICS and stock Blur.
The most well known ROM for RAZR is probably Eclipse. If you have the GSM model, you'll need a patch or ported version. There are also ported alphas of CM9, 10 and AOKP.
Let me know if you have more questions or want some more links
Fracta1 said:
The bootloader on the Motorola RAZR is not unlockable.
I've flashed custom ROMs using both SafeStrap and BootMenu (my favourite is BootMenu, here's a link for more info on it: http://forum.xda-developers.com/showthread.php?t=1720351)
The neat thing about the RAZR is that it can be dual-booted using either of these recoveries. I am running both Eclipse ICS and stock Blur.
The most well known ROM for RAZR is probably Eclipse. If you have the GSM model, you'll need a patch or ported version. There are also ported alphas of CM9, 10 and AOKP.
Let me know if you have more questions or want some more links
Click to expand...
Click to collapse
Thanks for the response.
So, is SafeStrap and BootMenu a custom recovery, or do I still install CWM or TWRP?
Do you have any experience with the CM10 or AOKP ports? If so, are they at all stable?
nebrando said:
Thanks for the response.
So, is SafeStrap and BootMenu a custom recovery, or do I still install CWM or TWRP?
Do you have any experience with the CM10 or AOKP ports? If so, are they at all stable?
Click to expand...
Click to collapse
SafeStrap and BootMenu are both CWM-based recoveries; they're all you need to flash. I prefer BootMenu, though it was a bit more complex to set up (Eclipse wasn't flashing in SafeStrap for some reason so that's when I started trying BootMenu). BootMenu lets you select which ROM to boot upon powering on the device (stock or the second one you flashed, alternatively you can flash your new ROM on top of the stock system but I don't see why you would), or boot into recovery. If you're really used to basic CWM I'd go for SafeStrap unless otherwise needed though.
I've tried both CM10 and the AOKP JB ROM (these flashed perfectly fine in SafeStrap). The camera doesn't work and apparently deep sleep doesn't either. It wasn't friendly on battery in my experience. I had trouble with data, too (this may have been my APN settings... But at the time I hadn't even tried playing with those because I didn't figure that was my problem). Wiping the cache partition and dalvik cache allowed data every so often on the next boot, but then apps started acting up (likely because of the dalvik wipe) until another reboot... which killed the data again :silly: The general consensus is that data works though. But overall, I wouldn't try it just yet unless you make sure it's installed on your second system and not flashed over your stock one.
Here's the link in case you want a looksie at some Jelly Bean goodness: http://forum.xda-developers.com/showthread.php?t=1801379
I can't say enough good things about Eclipse. Try that if you want. Incredibly stable and all main features are working - fantastic modified AOSP look too. It's my daily driver
Original Eclipse CDMA page: http://forum.xda-developers.com/showthread.php?t=1795493
GSM patches in case that applies to you (the FULL Eclipse port is towards the bottom, ready to flash without patching): http://forum.xda-developers.com/showthread.php?t=1805380
Oh, and finally, SafeStrap recovery: http://forum.xda-developers.com/showthread.php?t=1847599
Just make sure you enable Safe System in recovery and you can go flash-happy without any worry! Disabling Safe System puts you right back to stock (you can re-enable Safe System to go back into the ROM you have installed on there).
So yeah, that's about it! Check out the links; everything you need to know should be in them, and I'll try to help more if you need! Have fun
Edit: CM10 port entered beta today (AOKP port disappeared from the page?). Camera is working as well as other little features; still no deep sleep.