Database Info

Problems restoring backup with clockwork

Everytime I try and restore a backup from cwm the phone reboots to the first mytouch boot screen and just stays there. Is there something I'm missing on how to restore a backup? I'm using cwm 3.0.0.5, I make a backup, then when I want to restore it, I wipe data and cache and hit restore backup. Once it's finished, I reboot the phone, then it just sits on the boot screen until I eventually decide to pull the battery.

j21blackjack said:
Everytime I try and restore a backup from cwm the phone reboots to the first mytouch boot screen and just stays there. Is there something I'm missing on how to restore a backup? I'm using cwm 3.0.0.5, I make a backup, then when I want to restore it, I wipe data and cache and hit restore backup. Once it's finished, I reboot the phone, then it just sits on the boot screen until I eventually decide to pull the battery.
Click to expand...
Click to collapse
Clockwork Recovery 3.0.0.5 will work only with 2.3 (gingerbread ROMs).
Since the stock ROM is 2.2.1 you need to use recovery image 2.x.
you are in luck though. re-Flash CM7 download Clockwork ROM Manager scroll to the bottom "All clockwork recoveries" and flash the highest 2.x version they have. Then you can restore your back up without problems.

Thanks, I actually found that exact answer about 10 minutes after I posted this. I did just that, flashed cm7 then flashed cwm 2.x. I wanted to try cm7 anyway, but after an hour just trying to get the market to work, I decided to just go back to good old iced glacier.
Sent from my HTC Glacier using XDA App

j21blackjack said:
Thanks, I actually found that exact answer about 10 minutes after I posted this. I did just that, flashed cm7 then flashed cwm 2.x. I wanted to try cm7 anyway, but after an hour just trying to get the market to work, I decided to just go back to good old iced glacier.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I bet you didn't flash gapps or the newer version of it. That's why you couldn't get the market to work.
Sent from my CM7 HTC Glacier using XDA App

coupetastic-droid said:
I bet you didn't flash gapps or the newer version of it. That's why you couldn't get the market to work.
Sent from my CM7 HTC Glacier using XDA App
Click to expand...
Click to collapse
I have no idea what I did, but eventually I got it all worked out. I'm now a very happy cm7 rc1 user with a 1.84GHz smartass kernel.

j21blackjack said:
I have no idea what I did, but eventually I got it all worked out. I'm now a very happy cm7 rc1 user with a 1.84GHz smartass kernel.
Click to expand...
Click to collapse
Glad it worked out for you, but you (and others who may have this problem) could save yourselves a lot of this by downloading TrueBlue's zip (from development sub-forum) and flash it. It has cwm 3.0.0.6 plus stock TMO recovery.
With CM 3.0.0.6 recovery (thanks to Option94 for that), you can backup/restore both Android 2.2.x (CM6) and 2.3.x (CM7). TrueBlue's thread OP gives you instructions on how to use it.
It is a modified ROM Manager that "disguises" cwm's 3.0.0.6 and the stock Recovery as cwm 3.0.0.5 and 2.5.1.4 respectively.
PS - if you use it - don't forget to "thank" him (and Option94 also).
UPdate - if you subsequently update ROM Manager, it does not wipe out the above scheme with the disguised cwm's - it still works the same (at least through ROM Manager 3.0.1.0).

gaww said:
Glad it worked out for you, but you (and others who may have this problem) could save yourselves a lot of this by downloading TrueBlue's zip (from development sub-forum) and flash it. It has cwm 3.0.0.6 plus stock TMO recovery.
With CM 3.0.0.6 recovery (thanks to Option94 for that), you can backup/restore both Android 2.2.x (CM6) and 2.3.x (CM7). TrueBlue's thread OP gives you instructions on how to use it.
It is a modified ROM Manager that "disguises" cwm's 3.0.0.6 and the stock Recovery as cwm 3.0.0.5 and 2.5.1.4 respectively.
PS - if you use it - don't forget to "thank" him (and Option94 also).
Click to expand...
Click to collapse
Did that yesterday, it works great.

Thats awesome news, I was just about to post the question about the 3.0.0.6 backwards compatibility with nandroid backups.. Thanks!

i have the same issue.i flashed CM7.its installed,now i go into ROM manager and scroll down and select "All ClockworkMod Recoveries" (2.5.1.4) but get "an error accured while flashing your recovery"?
what did i do wrong?am i missing some thing?
i also wanted to know how i install GAPPS while i have CM7 installed? thanks for any help

MTSDAN said:
i have the same issue.i flashed CM7.its installed,now i go into ROM manager and scroll down and select "All ClockworkMod Recoveries" (2.5.1.4) but get "an error accured while flashing your recovery"?
what did i do wrong?am i missing some thing?
i also wanted to know how i install GAPPS while i have CM7 installed? thanks for any help
Click to expand...
Click to collapse
ok i installed GAPPS ..but still having issues with the Clock work recovery

MTSDAN said:
i have the same issue.i flashed CM7.its installed,now i go into ROM manager and scroll down and select "All ClockworkMod Recoveries" (2.5.1.4) but get "an error accured while flashing your recovery"?
what did i do wrong?am i missing some thing?
i also wanted to know how i install GAPPS while i have CM7 installed? thanks for any help
Click to expand...
Click to collapse
Ignore all those BS. Go in Market and download Rom Manager 3.0.1.0 and then flash the latest 3.0.0.5 (orange) recovery image. Then place the GAPP anywhere in your SDCard long as you know where it is. Reboot it in to recovery but selecting it from Rom Manager and then when its booted select Install zip from SDCard> Choose zip from SDCard.
Flash the GApp.zip and be done. Just remember when you flash NB via full wipe you have to flash GApp.zip everytime but if you just mount new NB on top of old one then DO NOT flash GApp.zip again as it will still be on your device as it ment to be installed once in that case.

BlackSHELF said:
Ignore all those BS. Go in Market and download Rom Manager 3.0.1.0 and then flash the latest 3.0.0.5 (orange) recovery image. Then place the GAPP anywhere in your SDCard long as you know where it is. Reboot it in to recovery but selecting it from Rom Manager and then when its booted select Install zip from SDCard> Choose zip from SDCard.
Flash the GApp.zip and be done. Just remember when you flash NB via full wipe you have to flash GApp.zip everytime but if you just mount new NB on top of old one then DO NOT flash GApp.zip again as it will still be on your device as it ment to be installed once in that case.
Click to expand...
Click to collapse
thanks got gapps installed just fine but im having trouble with the rom manager im trying to install the laterClockwork recoveries (2.x)..but i keep getting an error

MTSDAN said:
thanks got gapps installed just fine but im having trouble with the rom manager im trying to install the laterClockwork recoveries (2.x)..but i keep getting an error
Click to expand...
Click to collapse
No you didn't do what I said then. Go to Market> Rom Manager (3.0.1.0)> Download/Install. Then run Rom Manager and flash 3.0.0.5(latest not 2.5.1.2/2.5.1.4). If you use 3.0.0.5 you don't have to worry about 3.x(orange) or 2.x(green) as you can run 2.2/2.3 based without changing it.
3.0.0.5 < not Rom Manager its Recovery.
3.0.1.0 < ver of Rom Manager with 3.0.0.5 Recovery frame.
Problem is for people who don't know it get confusing as 3.0.0.5 could mean Recovery and Rom Manager. As normally other software specify and have different type of scheme for framework and software but in this case they both share same number so it gets little confusing.

ok i installed 3.0.1.0 rom manager from market so now i should have no issues when restoring 2.2.1 roms or 2.3 roms?thanks for the help man im coming from a Vibrant that was lost/stolen..that vibrant was so easy to root lol.thanks again

MTSDAN said:
ok i installed 3.0.1.0 rom manager from market so now i should have no issues when restoring 2.2.1 roms or 2.3 roms?thanks for the help man im coming from a Vibrant that was lost/stolen..that vibrant was so easy to root lol.thanks again
Click to expand...
Click to collapse
Well if you flashed 3.0.0.5 Recovery then no you won't have to worry about Green(2.x EXT3) or Orange(3.x EXT4) as you can flash both.

[Q] ClockworkMod Recovery, ROM Manager, and Nandroid confusion

So I'm trying to update my rooted 3.0.1 euro 3G xoom to the 3.2 Hammerhead ROM, and here's something that is really confusing me:
I've installed ROM Manager 4.3.3.0 from the Market. Then I downloaded and flashed ClockworkMod Recovery 3.2.0.0 R4c via this thread: http://forum.xda-developers.com/showthread.php?t=1074979
So far so good: I can boot to recovery and it looks that everything is working nicely... with the exception of the following:
1) Even though I have CWM installed, ROM Manager won't recognize it. It keeps asking to install it. I haven't done that though because I don't want to overwrite the one I flashed... how can I get ROM Manager to recognize CWM? Or, if I install a different CWM version through the ROM Manager interface, will that overwrite the existing install, or even break something?
2) I can't find Nandroid in the recovery menu of 3.2.0.0 R4c. It says that it should be there in the Wiki (http://forum.xda-developers.com/wiki/index.php?title=How_to_backup_or_recover_via_Nandroid), but no sir. I only have the options Backup and Advanced Backup in recovery; it doesn't say Nandroid anywhere.
The thing is - I made a normal backup and it created a folder with .img files in it, along with a nandroid.md5 file. So is this a full Nandroid backup or not? And should it not be a zip file? Meaning - will I be able to revert to this backup through ROM Manager or CWM later if it's not a zip?
3) Lastly, I want to install the Tiamat 2.1 Hammerhead ROM. solarnz writes in the instructions in step 6 to "install the rom". So do I do that from recovery? Or from ROM Manager? Which brings me back to my first problem, that ROM Manager won't recognize CWM and won't let me install a ROM without it.
Also - can I install the Hammerhead ROM from my rooted 3.0.1 device at all, or should I install 3.1 first?
I know these are a lot of questions all at once, but after hours and hours of searching and reading (and learning a lot!), I still can't figure this part out.
Many thanks to anyone who can help me make sense of this!

bobblack said:
So I'm trying to update my rooted 3.0.1 euro 3G xoom to the 3.2 Hammerhead ROM, and here's something that is really confusing me:
I've installed ROM Manager 4.3.3.0 from the Market. Then I downloaded and flashed ClockworkMod Recovery 3.2.0.0 R4c via this thread: http://forum.xda-developers.com/showthread.php?t=1074979
So far so good: I can boot to recovery and it looks that everything is working nicely... with the exception of the following:
1) Even though I have CWM installed, ROM Manager won't recognize it. It keeps asking to install it. I haven't done that though because I don't want to overwrite the one I flashed... how can I get ROM Manager to recognize CWM? Or, if I install a different CWM version through the ROM Manager interface, will that overwrite the existing install, or even break something?
2) I can't find Nandroid in the recovery menu of 3.2.0.0 R4c. It says that it should be there in the Wiki (http://forum.xda-developers.com/wiki/index.php?title=How_to_backup_or_recover_via_Nandroid), but no sir. I only have the options Backup and Advanced Backup in recovery; it doesn't say Nandroid anywhere.
The thing is - I made a normal backup and it created a folder with .img files in it, along with a nandroid.md5 file. So is this a full Nandroid backup or not? And should it not be a zip file? Meaning - will I be able to revert to this backup through ROM Manager or CWM later if it's not a zip?
3) Lastly, I want to install the Tiamat 2.1 Hammerhead ROM. solarnz writes in the instructions in step 6 to "install the rom". So do I do that from recovery? Or from ROM Manager? Which brings me back to my first problem, that ROM Manager won't recognize CWM and won't let me install a ROM without it.
Also - can I install the Hammerhead ROM from my rooted 3.0.1 device at all, or should I install 3.1 first?
I know these are a lot of questions all at once, but after hours and hours of searching and reading (and learning a lot!), I still can't figure this part out.
Many thanks to anyone who can help me make sense of this!
Click to expand...
Click to collapse
Forget about Rom Manager. You have the correct recovery installed and you have made a "nandroid" backup when you used the backup option in CWM recovery 3.2.0.0 R4c. The Rom you want to flash needs to be on your MicroSD card and that needs to be in your Xoom when you boot into recovery. It is from the CWM recovery menu that you will choose to flash the zip file that will install the Rom. You will need to be able to boot into recovery and you can do it by pressing volume up and power to get to dual core screen, then after 3 seconds, press volume down then volume up and you should be in recovery. Or you could download Quick Boot from the market and use its boot into recovery option (that's what I do).
About the version you need to be on to flash Hammerhead...what does it say? I think you may need to be on 3.1 but just read the OP on the Hammerhead thread...it will tell you the requirements.
Good luck!

Thanks a lot for explaining that okantomi, that's very helpful and reassuring!
The only thing I'm left with now is to figure out the version part... the rom OP doesn't say anything about a required version. Here's the thread btw: http://forum.xda-developers.com/showthread.php?t=1203635
I made my way through the first 18 or so pages of the 434 total pages in that thread, but still couldn't find any info on that. I'll keep looking - not giving up

Quick update... I decided to just go for it. I flashed the 3.2 ROM onto 3.0.1 - it worked perfectly without any hiccups whatsoever. I'm now running Androud 3.2 with 3G and it works beautifully. Can you see that I'm smiling?

bobblack said:
Quick update... I decided to just go for it. I flashed the 3.2 ROM onto 3.0.1 - it worked perfectly without any hiccups whatsoever. I'm now running Androud 3.2 with 3G and it works beautifully. Can you see that I'm smiling?
Click to expand...
Click to collapse
Me too! ;^ )
Enjoy your shiny new Rom!

[Q] Wifi problem ICS, any idea ?

Hello,
I had the official version of ICS on my TF101 (the one with the locked bootloader).
I root, installed rom manager and flash recovery(5.5.0.4) -> backup performed.
Everything was perfect, however I wanted to try CM9 nightly build, I could install it without problem.
The CM9 wifi working on but the rom is not the most stable I wanted to go over the official thanks to my backup.
I ended up with the stock rom official ICS, but not enable the wifi. So I went back on the CM9, and there the WiFi working. I install the Revolution HD and the wifi does not work.
Back on my backup ICS official and still no wifi.
Have you an idea of where this might come?
Thank you in advance.
PS: After the installation of my CM9, my tf101 boot automatically on the recovery, forced to make a cold-booting android to begin.

I think the reboot into recovery thing is a bug that I've read some people have. I personally went back to the Rogue recovery after noticing that 5.5.0.4 didn't have option to access external SD.
Wifi...well...not too sure about that problem. Try to reflash the stock ICS rom back over on top of your backup. CWM is not the most reliable recovery, IMO.
Why don't you try Revolver. I bet that you'd stay on that rom. Oh...and pick up the superwipe lite script from the revolution thread if you haven't already. Good to use when you are swapping roms.

If you are restoring a nandroid, it is normal because nandroid doesn't restore the kernel, so you have to install the rom you want then restore the nandroid.
If you want to use CM9, use the one in my signature. Everything is working.

ricardopvz said:
If you are restoring a nandroid, it is normal because nandroid doesn't restore the kernel, so you have to install the rom you want then restore the nandroid.
If you want to use CM9, use the one in my signature. Everything is working.
Click to expand...
Click to collapse
is that this version of cm9 allows the AZERTY dock keyboard ?
when I install the Revolution HD and the official zip from asus there is still no wifi. there isn't kernel with this method ?

SiNJiN76 said:
I think the reboot into recovery thing is a bug that I've read some people have. I personally went back to the Rogue recovery after noticing that 5.5.0.4 didn't have option to access external SD.
Click to expand...
Click to collapse
I tried to install another recovery by the cwm recovery (flash zip), the install works, but i still have the cwm recovery.

SiNJiN76 said:
I think the reboot into recovery thing is a bug that I've read some people have. I personally went back to the Rogue recovery after noticing that 5.5.0.4 didn't have option to access external SD.
Click to expand...
Click to collapse
Reboot to recovery is a issue present in all aosp roms except mine
zulfurion said:
is that this version of cm9 allows the AZERTY dock keyboard ?
when I install the Revolution HD and the official zip from asus there is still no wifi. there isn't kernel with this method ?
Click to expand...
Click to collapse
Well, it supports more keyboard languages than english, so it should work.
If you want to go back to asus based rom, you must wipe, install the rom you want, boot it and then restore nandroid if you have one

ricardopvz said:
If you want to go back to asus based rom, you must wipe, install the rom you want, boot it and then restore nandroid if you have one
Click to expand...
Click to collapse
I think I already did. But I will still check tonight
thank you

ricardopvz said:
If you want to go back to asus based rom, you must wipe, install the rom you want, boot it and then restore nandroid if you have one
Click to expand...
Click to collapse
Still no wifi

zulfurion said:
Still no wifi
Click to expand...
Click to collapse
What is the problem? Wifi doesn't turn on? your network doesn't show up? you can't connect to your network?
You can always try other roms and see if wifi works. but if you have a dock i recommend to use my CM9 build which has working dock battery

wifi doesn't turn on. Block on "wifi activation..."

Same problem with the Revolver 4

It works with another recovery.
Sorry for my noobness, and thank you for your help.

[Q] Custom recovery and CWM Recovery-on-boot for stock ICS

I've looked all over this forum and I hope that I can get a definitive answer here. I don't feel like my use case is that unique but I'm going to be as specific as possible and hopefully get as concise and complete an answer as possible.
Until recently, I was running a custom GB-based ROM. When I was running GB, I used the Atrix 2 Bootstrapper and RAZR-CWM-Recovery-on-boot-J.Y.Daddy (or whatever it's called) to get CWM Recovery on boot and make backups and so on.
I ran the return to stock script from my GB ROM and am now running the stock ICS ROM that I got from the official OTA upgrade from AT&T. I've obviously rooted it.
I want to make a backup of my current stock rooted ROM with CWM Recovery. To my knowledge, the old bootstrapper method does not work on the official ICS OTA upgrade. I don't want to multi-boot with BMM, I just want a custom recovery so I can run CWM Recovery to backup/restore/possibly flash a new ROM.
I know that most of the new ROMs include their own custom backup, but that leaves me with no way to get back to the new stock ICS ROM (to my knowledge, I may be wrong).
If the simple solution is not possible and the only solution is to install Numa or Paranoid or the unofficial CM ROM, that's fine, I'd just like to know.
Thanks in advance.

My advice would be to just use BMM from the play store, edit the recovery.fstab as shown in that thread.. And make a backup with that.. Use tar format I think (if there's a choice - sorry I have not made a backup on this phone in a while).
That should be good to restore with other recoveries.. Plus you can uninstall BMM and don't need to multi-boot..
But, wait, I thought the old a2 bootstrapper worked fine on ics...?
Sent from my MB865 using xda app-developers app

alteredlikeness said:
But, wait, I thought the old a2 bootstrapper worked fine on ics...?
Click to expand...
Click to collapse
I actually haven't tried it yet, that's just the general "feeling" I got from what I had read thus far. I was up super late last night fixing three or four soft bricks before I got my phone to a working state again and now I'm taking the cautious route. The bootstrapper doesn't count as a custom recovery, though, for the purposes of creating a backup with CWM Recovery, right? As in I'll still need to find a custom recovery to run a backup.
That is, of course, assuming I don't just use BMM to take my backup now. I suppose I had planned to go with a custom ROM eventually anyway, probably Numa, or maybe the CM ROM (if it gets a little more stable here pretty quickly, I suppose).
I'm pretty pleased with the stock ICS ROM over my old custom GB ROM (SCv6), which is why I'm now circumspect about trying out a new custom ROM without having a way to easily get back to where I am now (because I lost my backups the first time, like an idiot).
Thanks for the reply.

wormmd said:
I actually haven't tried it yet, that's just the general "feeling" I got from what I had read thus far. I was up super late last night fixing three or four soft bricks before I got my phone to a working state again and now I'm taking the cautious route. The bootstrapper doesn't count as a custom recovery, though, for the purposes of creating a backup with CWM Recovery, right? As in I'll still need to find a custom recovery to run a backup.
That is, of course, assuming I don't just use BMM to take my backup now. I suppose I had planned to go with a custom ROM eventually anyway, probably Numa, or maybe the CM ROM (if it gets a little more stable here pretty quickly, I suppose).
I'm pretty pleased with the stock ICS ROM over my old custom GB ROM (SCv6), which is why I'm now circumspect about trying out a new custom ROM without having a way to easily get back to where I am now (because I lost my backups the first time, like an idiot).
Thanks for the reply.
Click to expand...
Click to collapse
why not multi boot using BMM? checkout Numa, it has all the stock ICS goodness but debloated and much faster. see for urself
i'm using it and its much better than ICS stock

wormmd said:
To my knowledge, the old bootstrapper method does not work on the official ICS OTA upgrade.
Click to expand...
Click to collapse
The bootstrapper does work with ICS.
I don't want to multi-boot with BMM, I just want a custom recovery so I can run CWM Recovery to backup/restore/possibly flash a new ROM.
Click to expand...
Click to collapse
Well apart from bootstrapper and BMM we don't have any other custom recovery for Atrix 2.
I know that most of the new ROMs include their own custom backup, but that leaves me with no way to get back to the new stock ICS ROM (to my knowledge, I may be wrong).
Click to expand...
Click to collapse
Well there's always the fxz way
alteredlikeness said:
My advice would be to just use BMM from the play store, edit the recovery.fstab as shown in that thread.. And make a backup with that.. Use tar format I think (if there's a choice - sorry I have not made a backup on this phone in a while).
Click to expand...
Click to collapse
Yup as altered said.But from my understanding you don't want to multi-boot right? Then you don't need to edit recovery.fstb.Just install it from play store install the hijacks and make a backup(in tar format preferably you'll find the option in there)
wormmd said:
that is assuming I don't just use BMM to take my backup now.
Click to expand...
Click to collapse
I really don't see logically why would you be so hell bent to avoid BMM.
I'm pretty pleased with the stock ICS ROM over my old custom GB ROM (SCv6), which is why I'm now circumspect about trying out a new custom ROM without having a way to easily get back to where I am now (because I lost my backups the first time, like an idiot).
Click to expand...
Click to collapse
You can do two things:
1.Install BMM make a backup of your current system.Install the custom ROM you want.Restore whenever you feel like.
2.Install BMM.Edit recovery.fstb(don't go after the name you just have to edit some text).Leave your current system on system 1.Install any ROM you like on system 3 and/or above.No need to restore.Switch between your choice of system whenever you wish.
---------------------------------------------------
May the -Mass times Acceleration-be with You...

[Q] Install CM via Odin?

Hi eveyone, I updated my stock from 4.0 to 4.1 through odin and it was really painless. Sorry if this sounds lazy but can you install cm the same way? Doing the whole CW etc. seems a lot of steps - i'd rather upload one file only if possible. Thanks!

Guiyoforward said:
Hi eveyone, I updated my stock from 4.0 to 4.1 through odin and it was really painless. Sorry if this sounds lazy but can you install cm the same way? Doing the whole CW etc. seems a lot of steps - i'd rather upload one file only if possible. Thanks!
Click to expand...
Click to collapse
i do not think you can install zip with odin

LitD said:
i do not think you can install zip with odin
Click to expand...
Click to collapse
Thanks. You cannot - what I mean is: is CM ever realeased as a TAR-compatible ODIN file?

That can certainly be done. But it's not the norm.
Sent from my SGH-T699 using Tapatalk

James chdset
Nardholio said:
That can certainly be done. But it's not the norm.
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
Thanks Nardholio. I'm obviously missing some important feature CWM offers thatthe "odin process" does not. Is it seamless backup amd restore? Or is it the possibility of adding patches and new stuff - say, gapps on top of CM?
Thanks again!
G.

Deleted because I reposted in the intended thread

Guiyoforward said:
Thanks Nardholio. I'm obviously missing some important feature CWM offers thatthe "odin process" does not. Is it seamless backup amd restore? Or is it the possibility of adding patches and new stuff - say, gapps on top of CM?
Thanks again!
G.
Click to expand...
Click to collapse
CWM offers both of those things as an advantage, yes. You also can use CWM with the Stock image to gain the backup and restore features, amongst others.
And really, if you're already running Stock JB, the process is as simple as:
Place The cm-10.2-XXXXXXXX-NIGHTLY-apexqtmo.zip and gapps zip files on your phone, either on the 'internal' or external SD Card. (This even is optional, as they can be sideloaded if you have adb)
Flash CWM with Odin or Heimdall.
Reboot into recovery
Flash the cm nightly.zip
Flash the gapps.zip
wipe /cache with CWM.
Issue a factory reset with CWM.
Reboot to system.
If you're still on ICS, then you just need to add the steps of flashing the JB-stock-modem.zip and JB-stock-bootloader.zip before flashing the cm-nightly.zip (Turn GPS OFF before flashing these, specifically the modem, just to be on the safe side)
If you perform a backup with CWM before flashing anything, you can restore your stock system as you please.
If you simply want to root your relay, flash an appropriate recovery flashable zip copy of Superuser or SuperSU instead of flashing anything else.
kilr00y, along with providing the JB-stock-modem and JB-stock-bootloader recovery-flashable zip files, also provided a JB-stock-image.zip that can be used to go back to a stock-like system.
CWM allows you for a much greater amount of control over your phone, even when still running a stock image, due to the flexibility of being able to flash new applications directly to the system directories (such as Superuser/SuperSU) without having to have everything be signed by Samsung.

Magamo said:
CWM offers both of those things as an advantage, yes. You also can use CWM with the Stock image to gain the backup and restore features, amongst others.
And really, if you're already running Stock JB, the process is as simple as:
Place The cm-10.2-XXXXXXXX-NIGHTLY-apexqtmo.zip and gapps zip files on your phone, either on the 'internal' or external SD Card. (This even is optional, as they can be sideloaded if you have adb)
Flash CWM with Odin or Heimdall.
Reboot into recovery
Flash the cm nightly.zip
Flash the gapps.zip
wipe /cache with CWM.
Issue a factory reset with CWM.
Reboot to system.
Click to expand...
Click to collapse
THANKS! This is by far the easiest step by step instructions I've seen, and gladly I'm on stock JB already.
Will give this a try
thanks again!

just booted into apex CM 347 nightly after the... ehem... peculiar apex logo thanks a lot for your effort.
now, I am a noob but can find my way around. I still think the whole process (CM and co, not the relay 4g per se) is a bit convoluted and underdocumented. just an example: I downloaded the IMG file from CWM but it took me a while to figure out that I had to transform it into md5 for it to play nice with odin, etc.
buy hey. I'm going to setup my system.
thanks everyone!!

Guiyoforward said:
just booted into apex CM 347 nightly after the... ehem... peculiar apex logo thanks a lot for your effort.
now, I am a noob but can find my way around. I still think the whole process (CM and co, not the relay 4g per se) is a bit convoluted and underdocumented. just an example: I downloaded the IMG file from CWM but it took me a while to figure out that I had to transform it into md5 for it to play nice with odin, etc.
buy hey. I'm going to setup my system.
thanks everyone!!
Click to expand...
Click to collapse
In all honesty, ODIN itself is an underdocumented POS, the recovery.img file (or in this case, the renamed apexq_recovery-10.2.img file if you were following along with the wiki) comes right from the build process, it can be flashed directly without much tooling about with it using heimdal, which is an open source replacement for ODIN, that works very well. Heimdall can be used optionally with a GUI, but I personally use it from the command line, to get it to flash a recovery image to the recovery partition of a Relay, it's simply:
heimdall flash --recovery apexq_recovery-10.2.img

Guiyoforward said:
just booted into apex CM 347 nightly after the... ehem... peculiar apex logo thanks a lot for your effort.
now, I am a noob but can find my way around. I still think the whole process (CM and co, not the relay 4g per se) is a bit convoluted and underdocumented. just an example: I downloaded the IMG file from CWM but it took me a while to figure out that I had to transform it into md5 for it to play nice with odin, etc.
buy hey. I'm going to setup my system.
thanks everyone!!
Click to expand...
Click to collapse
How did you transform the img to md5 (I can also take the cwm in md5 format from the root thread, am I right?) ?
So I can flash anything without root using this method (even recovery) ? I couldn't do this with my desire Z, it's confusing me !
Which recovery should I flash to use cm10.2 (the cwm or the apexq_recovery-10.2.img ?) ?
=> If I use an older recovery I can't flash any jelly been rom's ?

robuser007 said:
(I can also take the cwm in md5 format from the root thread, am I right?)
Click to expand...
Click to collapse
yes, you can
robuser007 said:
So I can flash anything without root using this method (even recovery) ? I couldn't do this with my desire Z, it's confusing me !
Click to expand...
Click to collapse
there are several differences. you can flash recovery via odin to a not rooted device
robuser007 said:
Which recovery should I flash to use cm10.2 (the cwm or the apexq_recovery-10.2.img ?) ?
Click to expand...
Click to collapse
google 'install cyanogenmod samsung relay' and follow 'how to install cyanogenmod for samsung relay' wiki. 'installing cyanogenmod from recovery' is the same as for desire z