Related
I don't want to run custom ROMs, I like the Gingerbread from Google and want to easily continue to receive updates.
That being said, I want to be able to run DroidWall and AdFree, and have to have root to do so.
Is there a way to get root, without installing a custom recovery or Clockwork or anything? And still easily receive updates to Gingerbread?
IDtheTarget said:
I don't want to run custom ROMs, I like the Gingerbread from Google and want to easily continue to receive updates.
That being said, I want to be able to run DroidWall and AdFree, and have to have root to do so.
Is there a way to get root, without installing a custom recovery or Clockwork or anything? And still easily receive updates to Gingerbread?
Click to expand...
Click to collapse
I don't think you can apply the su zip file from the stock recovery, but you can try. If it were that easy, there'd be news of it all over the net!
I think you're going to have to unlock the bootloader and then do the fastboot install of CWM.
I'm on stock Gingerbread, but rooted. I prefer CWM to stock recovery...more options, and especially nandroid backup. I got my 2.3.2 update faster than most, because I was still able to push it manually rather than wait for OTA to someday show up, so no issue there, you just have to wait for someone to post its url.
The 2.3.1 and 2.3.2 updates have a script that rewrites stock recovery on top of CWM if you're on either of those, so you get back to stock with each reboot.
If you're running Android 2.3.1 then use http://forum.xda-developers.com/showthread.php?t=882333 to root.
Android 2.3.0 will be GRH55. Paul hasn't updated SuperBoot for Android 2.3.2.
This method definitely works. I performed it while I was testing the device for any hardware defects. I was able to be rooted without changing the recovery. Make sure you have ADB drivers and 2.3 SDK for the Nexus S installed.
IDtheTarget said:
I don't want to run custom ROMs, I like the Gingerbread from Google and want to easily continue to receive updates.
That being said, I want to be able to run DroidWall and AdFree, and have to have root to do so.
Is there a way to get root, without installing a custom recovery or Clockwork or anything? And still easily receive updates to Gingerbread?
Click to expand...
Click to collapse
First and foremost, you should understand that installing a custom recovery will do nothing to block your ability to receive updates from Google nor will it affect your system in anyway. However, if you follow one of the root methods like this one you will install the custom recovery needed to fix permissions to gain root access but if you ignore the step that has you change the name of a file through root explorer, the next time you reboot your custom recovery will be overwritten by the stock one and you will retain root.
Again, its important to know that having a custom recovery allows you to do a lot more than just flash roms. You can do back ups of your NAND memory that allow you to save all of your data, files, settings, et cetera in the case of catastrophic failures or the need to get a replacement handset. If you do a backup maybe once a month and keep them on your computer, you will always be able to restore your phone exactly back to how it was before issues arose.
There is really no downside to having a custom recovery like Clockwork Recovery Mod, but if you are really against it for moral reasons (that is literally the only reason you would not want to install it) then use the method I described and you will be rooted without CWM.
Agreed with what Kenvan said, the Nexus S is a 'unlocked' bootloader phone and considered a "developer phone." The phone is meant to be altered with a bunch of modifications and hacks.
Not sure why you want to cripple your phone by not flashing custom ROMs. They're created to fascinate the Android experience with improvements made to it. But everybody has their reasons, and are entitled to them right?
Just pointing out my 2 cents. Especially when you're on a forum where a large % of the community are here to modify their phones to the highest extent.
zephiK said:
Not sure why you want to cripple your phone by not flashing custom ROMs. They're created to fascinate the Android experience with improvements made to it. But everybody has their reasons, and are entitled to them right?.
Click to expand...
Click to collapse
LOL. Not flashing custom ROMs is hardly "crippling your phone".
That's like saying not installing a turbo-charger is crippling your porsche...
But I agree, once the custom stuff out there is into actual full public-release, I'll be testing it, but meanwhile a Nexus S on Gingerbread stock is a fine experience...BEST experience on any Android I've had, even supercharged Nexus One and Galaxy S i9000 ROMs.
distortedloop said:
LOL. Not flashing custom ROMs is hardly "crippling your phone".
That's like saying not installing a turbo-charger is crippling your porsche...
But I agree, once the custom stuff out there is into actual full public-release, I'll be testing it, but meanwhile a Nexus S on Gingerbread stock is a fine experience...BEST experience on any Android I've had, even supercharged Nexus One and Galaxy S i9000 ROMs.
Click to expand...
Click to collapse
you both make good points. My point was that there its no reason not install a custom recovery, even if one is staying stock
Sent from my Nexus S
I agree. No reason to not use CWM recovery. Google should buy rights to it from him.
IDtheTarget said:
I don't want to run custom ROMs, I like the Gingerbread from Google and want to easily continue to receive updates.
That being said, I want to be able to run DroidWall and AdFree, and have to have root to do so.
Is there a way to get root, without installing a custom recovery or Clockwork or anything? And still easily receive updates to Gingerbread?
Click to expand...
Click to collapse
I'm wondering the same thing myself.
I just found out that it's possible to boot into the Clockwork recovery without flashing it first. I managed to do this by booting into fastboot mode (power + volume up) and then do
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
This was on a stock but rooted 2.3.2, and the bootloader was locked. I didn't try to apply any update.zip, but nandroid backup seemed to work perfectly.
If you don't remove/delete the "/etc/install-recovery.sh" file once you've flashed a new recovery then you *should* find that the default/stock bootloader is re-applied on the first reboot.
As others have mentioned though, there are plenty of benefits to applying a custom recovery although I do understand the reasons you may not want to.
Thanks, all! Okay, maybe I *will* do the Clockwork Recovery then.
The reason I don't want custom ROMs: I had a Vibrant, and was using Team Whiskey's ROMs, and got "Compulsive ROM disorder". Every TW ROM was better than the last, and I found myself flashing every time they came out with a new one.
I'm going to Afghanistan in a couple of months (leaving for some training on Tuesday), and if I can get Internet at all, I won't have the bandwidth to be constantly downloading the newest, coolest ROM. The stock Gingerbread is good enough for me, and I want to keep it. Plus, that way if my wife has problems with her Nexus S while I'm gone, I have another just like it with me to figure out what's wrong with hers.
I just need root to run DroidWall and AdFree so that if I *do* manage to get a data plan out there, I won't run up huge fees because somebody wants me to buy Viagra or something.
Thanks again!
shrivelfig said:
This was on a stock but rooted 2.3.2, and the bootloader was locked. I didn't try to apply any update.zip, but nandroid backup seemed to work perfectly.
Click to expand...
Click to collapse
Wow, that's a great find.
IDtheTarget said:
Thanks, all! Okay, maybe I *will* do the Clockwork Recovery then.
The reason I don't want custom ROMs: I had a Vibrant, and was using Team Whiskey's ROMs, and got "Compulsive ROM disorder".
Click to expand...
Click to collapse
I fully understand that about the Compulsive ROM flashing disorder. I developed a bit of a case of it with the DocRambone ROMs on my Galaxy S i9000. It became a full time job just keeping up with the forum posts in the thread there. Hundreds of posts per day...ugh! But a sweet ROM.
As I'm sure you've ascertained by our other replies to you, having custom recovery is a benefit whether you flash roms constantly or not.
The ability to do a Nandroid and have a nice working backup of your entire system to fall back on is a major plus, as is the ability to wipe dalvik-cache if you're having issues.
Good luck in Afghanistan!
Thanks!
Yes, I've decided to do the recovery for the Titanium backup as well.
Now if I can only get it to work!
I manually updated to 2.3.2 yesterday, then just now started to try rooting using the directions here: http://forum.xda-developers.com/showthread.php?t=895545
But I keep getting a signature error on the SuperUser flash. I'm guessing it has something to do with the new update.
IDtheTarget said:
Thanks!
Yes, I've decided to do the recovery for the Titanium backup as well.
Now if I can only get it to work!
I manually updated to 2.3.2 yesterday, then just now started to try rooting using the directions here: http://forum.xda-developers.com/showthread.php?t=895545
But I keep getting a signature error on the SuperUser flash. I'm guessing it has something to do with the new update.
Click to expand...
Click to collapse
No, the su file should flash just fine, many of us no problems with it rooting on 2.3.2.
Which version of clockwork recovery did you flash? That post was linking to 3.0.0.0, but that one is buggy, and you want to get 3.0.0.5.
Try this one: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Push via fastboot.
distortedloop said:
No, the su file should flash just fine, many of us no problems with it rooting on 2.3.2.
Which version of clockwork recovery did you flash? That post was linking to 3.0.0.0, but that one is buggy, and you want to get 3.0.0.5.
Try this one: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Push via fastboot.
Click to expand...
Click to collapse
No, the problem was that I'm an idiot who hasn't had enough sleep.
I'd flashed that image but wasn't getting into Clockwork recovery. I downloaded ROM Manager and flashed that recovery and was able to update Super User.
Now my problems are (1) I can't rename /etc/install-recovery.sh because it's a read-only file system, and (2) I can't re-install my Astro Pro file manager until Google fixes the market to recognize the new update...
Thanks for the help!
IDtheTarget said:
No, the problem was that I'm an idiot who hasn't had enough sleep.
I'd flashed that image but wasn't getting into Clockwork recovery. I downloaded ROM Manager and flashed that recovery and was able to update Super User.
Now my problems are (1) I can't rename /etc/install-recovery.sh because it's a read-only file system, and (2) I can't re-install my Astro Pro file manager until Google fixes the market to recognize the new update...
Thanks for the help!
Click to expand...
Click to collapse
Try root explorer.
You don't have Titanium Backup to restore Astro...? Every root user should grab that.
You could rename it via adb shell.
Hook up to adb, connect.
run su
remount /system as writable.
use linux mv command to rename it.
I believe you can connect as su to the phone with adb while booted into CWM recovery. Then use CWM menu to mount /system, then do the commands from your computer's terminal or dos shell. Only advantage to this way is you don't have to figure out the proper syntax for remount of /system.
distortedloop said:
You don't have Titanium Backup to restore Astro...? Every root user should grab that.
You could rename it via adb shell.
Hook up to adb, connect.
run su
remount /system as writable.
use linux mv command to rename it.
I believe you can connect as su to the phone with adb while booted into CWM recovery. Then use CWM menu to mount /system, then do the commands from your computer's terminal or dos shell. Only advantage to this way is you don't have to figure out the proper syntax for remount of /system.
Click to expand...
Click to collapse
Couldn't use Titanium backup until I rooted...
Thanks! I used the following command to change permissions:
mount -o remount,rw /dev/block/mtdblock3 /system
Then I:
cd \etc
mv install-recovery.sh install-recovery.sh.000
Looks like I'm set! Although there are still those few apps that aren't showing up yet after the update. Updating the market should be part of Google's checklist when pushing updates...
I've used the SuperBoot method twice and it's exactly what you're looking for. Stock ROM, Stock Recovery, and a rooted device with superuser permission.
Just got T-Mobile OTA 1.63.531.2
I can't get it to flash with CM Recovery. Tried with sig verification off. Phone should be s-offed.
Here it is if anyone wants:
http://lts.cr/Bhqv
.....next time post in the general. And rename it PG59IMG.zip and flash it in hboot
Thanks. I posted here so someone can see the source for developing if needed.
How do I get to hboot again with cm recovery?
pull your battery then put it back in and hold volume down and power. Then it will say confirm and press yes
Revolutionary hboot finds the zip file, does the loading bar but then does nothing. Have to choose fastboot, recovery, factory reset, simlock or image crc.
well it shouldve flashed...idk what to say....is in the root of the sdcard and named PG59IMG.zip
Yup I'm going to try the variant at
http://forum.xda-developers.com/showpost.php?p=23802172&postcount=7
This type of file is not a file to flash with the bootloader
Ran into this before trying to manually update a mytouch 4g
Is a regular update file like we used to do with update files on nexus one a so forth.
They have changed the way the updates work though and can not be flashed manually from what I have seen..
Needs to be in like a secure location probably /cache/ota or something like that.
Crap, so what do I do? Do I need to use that full update that does seem to work? But that also does a wipe?
ohh ya your right now that i look at the update.zip....just download the full update and flash that in hboot...dont forget to rename to PG59IMG.zip
Anyway to avoid a wipe?
well backup all your apps with titanium backup...then restore them with titanium
I've manually flashed the OTA updates that come to the phone. They flash thru stock recovery, not hboot or CWM. I don't think it matters what you name it, you just select it. And I'm not positive, but it might require a fully stock device.
Edit: I was S-OFF when I did tho. I think Blue might have tried with S-ON, and it wouldn't happen. Can't remember for sure tho
lol too much work to get stock recovery...just let him flash the full image
xmc wildchild22 said:
lol too much work to get stock recovery...just let him flash the full image
Click to expand...
Click to collapse
Ah yeah, I didn't read the whole thread carefully enough. But in any case, just letting people know those OTA update packages do work in stock recovery, lol.
aw man, i want stock recovery now. i have way too many customizations to lose it all
wing_addict_usa said:
aw man, i want stock recovery now. i have way too many customizations to lose it all
Click to expand...
Click to collapse
You can DL and flash stock recovery easily enough, just go to Blue6IX's Developer Reference thread, and go to the Recovery section. It could be worth a try, but I'm not sure the update will work with your customized setup. Might have to do as xmc suggested.
You need a stock recovery to flash an OTA - as mentioned above, it's not a PG59IMG.zip type of file or any other that hboot can process.
Custom recoveries can't process this type of update.
This thread should probably be in general, as it's more of asking for help then providing a solution.
Sent from a digital distance.
I have a zip I made the other day I named it some crazy file name and flashed in cwm, It's bone stock deodexed thanks to blue....while I'm getting ready for Easter I can upload the ROM or whatever....It's a simple kitchen zip
Sent from my myTouch_4G_Slide using Tapatalk
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
yuma80 said:
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
Click to expand...
Click to collapse
The problem with ROM Manager is that it messes up the files when flashing a ROM or any file. It is more advised to use CMW Recovery.
yuma80 said:
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
Click to expand...
Click to collapse
Rom Manager should not be used on the G2x. If you flash a rom and something goes wrong and you can not boot you are dead in the water. Use Nvidia CWM instead.
http://forum.xda-developers.com/showthread.php?t=1056847
Yes thanks. I understand that I shouldn't use ROM Manager, but I want to know what it does and why it doesn't work. For starters anybody know where it writes CWM to?
Worse comes to worse I'm just going to dump /dev/block/mmc* and look for strings or disassemble the apk or something...
yuma80 said:
Yes thanks. I understand that I shouldn't use ROM Manager, but I want to know what it does and why it doesn't work. For starters anybody know where it writes CWM to?
Worse comes to worse I'm just going to dump /dev/block/mmc* and look for strings or disassemble the apk or something...
Click to expand...
Click to collapse
I've always been curious about the details of a 'fake flash' too.. please let us know if you figure out any details.
Rom manager has been around since the original Droid from Verizon. The fake flash you refer to isn't actually a fake flash. It actually flashes CWM recovery. It just doesn't work on this particular phone. I may be wrong on the exact details but the G2x partitions and drivers require the use of NVflAsh to install the CWM. However, there are many phones that once they have been rooted, the user can install Rom Manager and use the Flash Recovery option to install their CWM recovery. There are also times when a particular recovery version (ie.. 5.0.5. Or 4.6.3) works better than another on one particular phone. Rom manager allows users an easy way of flashing between those CWM versions by simply pushing the flash button.
So in summary of a long response... it is only called a fake flash because it looks like it worked on our phone , but in fact it does not. We have to use NVflash to flash our recovery.
If it looks like I'm remotely right ( which I think I am..) hit that thanks button. (Shameless request, I know)
From my understanding, the "fake flash" that ROM Manager does is that it doesn't actually flash CWM like NVFlash does (on the recovery partition) but still puts the CWM files on your SD card saying that you do have it installed (sdcard/clockworkmod) so when you try to flash/install a ROM, it can't put it anywhere. I don't think it will flash anything, but people mess up their devices by wiping data/system and such...
OR...
Maybe it does flash CWM to your device but it has the partition tables all messed up?
One or the other lol, it's just a guess for both options but I believe the first one is right.
I've wondered for a while why rom manager is included in roms for the g2x when it's not advised to use it
Sent from this
DorisTheHeavy said:
I've wondered for a while why rom manager is included in roms for the g2x when it's not advised to use it
Sent from this
Click to expand...
Click to collapse
To rename your nandroid backups .
buru898 said:
To rename your nandroid backups .
Click to expand...
Click to collapse
I never thought about that. I was always unsure what flashing CWM with ROM Manager would do when it's already on my phone using NVFlash.
Since our phones have a dual partition in it. I think it flashes to the internal 1 gig memory so then loading another rom writes over it.
Sent from my LG-P999 using xda premium
OK, I finally had some time to do some poking around. Some of this is guess-work since I was too lazy to verify 100% exactly what it does when you specify that you're running a G2X.
Anyway, in it's settings DB it says this phone's recovery partition is read-only, and there's no flash command set, so I guess it doesn't try to flash it directly. It looks like it's relying on the Google stock recovery image to do the flashing instead, so it downloads a recovery-update.zip to the SD card and writes a script to /cache/recovery and reboots the phone into recovery mode. Google stock recovery would execute the script in /cache/recovery, which says to apply recovery-update.zip, but the actual stock recovery on the phone is either not Google stock, or has been modified; it doesn't bother to execute scripts, it just does a factory-reset (clear /cache, /data, etc) so that's why it doesn't work.
Meanwhile, ROM Manager writes to it's DB that it just flashed CWM version X.Y.Z and happily displays that every time it runs, even though that's not true.
I used NVFlash and moved on with my life.
Just got my first device rooted.
Now i have installed a ROM.
I feel awesome.
But then i read this
"With ROM Manager you can back up your existing ROM, flash new ROMs, and install custom themes or kernels. It features a long list of ROMs which is frequently updated and you can install ROMs to the SD card or OTA (over the air). If you want to unlock features like premium ROMs, update notifications, and automatic backups, then you’ll need to spring for the premium version."
So now i am trying to figure out what custome themes are and what custom kernels are compared to the Avatar ROM i installed.
behedwin said:
Just got my first device rooted.
Now i have installed a ROM.
I feel awesome.
But then i read this
"With ROM Manager you can back up your existing ROM, flash new ROMs, and install custom themes or kernels. It features a long list of ROMs which is frequently updated and you can install ROMs to the SD card or OTA (over the air). If you want to unlock features like premium ROMs, update notifications, and automatic backups, then you’ll need to spring for the premium version."
So now i am trying to figure out what custome themes are and what custom kernels are compared to the Avatar ROM i installed.
Click to expand...
Click to collapse
Now let me put this simple. The ROM is the operating system of your device (OS). You know what a theme is. Its just changing the way things look can be your icons, interface shade/colour,etc. Its just visuals. And the next is kernel. Kernels are the thing which links your OS and hardware. Literally they are responsible for the way your phone behaves. Custom kernels has tweaks whicj can improve your device's performance, the battery drain, way your processor's I/O works.. It helps you to do things like over clock and under clock,etc. But it is risky as your manufacturer has made a stable kernel for your device and these custom kernels may be unstable. Sure thing you dont want to mess with em unless you know what you are doing. Now as you have choice to do things like changing ROMs and Kernels using Rom manager, i would recommend you to use CWM and flash zip files which has ROMs and Kernels made specifically for your device as this is more safe. But be sure to have a backup as installing something not meant for your device will brick it. Dont worry. Have a backup and also Odin with stock rom incase its really hard bricked. If it helped hit thanks button plz..
haridevil99 said:
Now let me put this simple. The ROM is the operating system of your device (OS). You know what a theme is. Its just changing the way things look can be your icons, interface shade/colour,etc. Its just visuals. And the next is kernel. Kernels are the thing which links your OS and hardware. Literally they are responsible for the way your phone behaves. Custom kernels has tweaks whicj can improve your device's performance, the battery drain, way your processor's I/O works.. It helps you to do things like over clock and under clock,etc. But it is risky as your manufacturer has made a stable kernel for your device and these custom kernels may be unstable. Sure thing you dont want to mess with em unless you know what you are doing. Now as you have choice to do things like changing ROMs and Kernels using Rom manager, i would recommend you to use CWM and flash zip files which has ROMs and Kernels made specifically for your device as this is more safe. But be sure to have a backup as installing something not meant for your device will brick it. Dont worry. Have a backup and also Odin with stock rom incase its really hard bricked. If it helped hit thanks button plz..
Click to expand...
Click to collapse
Awesome now i have a good hint of what each thing are.
Now this lead me to some more questions.
Since i have already rooted my device. I have installed Avatar ROM and tested some others...
But i never made any backups... Is it to late for that?
Is my best choice to download Titanium Backup and backup everything with that application?
You said something else about Odin, how to backup aswell with that?
What is CWM and how does it differ from Rom Manager?
When i install a ROM i download a zip file, put it on my device SD card
Boot the phone in and wipe data, wipe cache, wipe delvik (or whatever it is called) and last install the new .zp file.
behedwin said:
Awesome now i have a good hint of what each thing are.
Now this lead me to some more questions.
Since i have already rooted my device. I have installed Avatar ROM and tested some others...
But i never made any backups... Is it to late for that?
Is my best choice to download Titanium Backup and backup everything with that application?
You said something else about Odin, how to backup aswell with that?
What is CWM and how does it differ from Rom Manager?
When i install a ROM i download a zip file, put it on my device SD card
Boot the phone in and wipe data, wipe cache, wipe delvik (or whatever it is called) and last install the new .zp file.
Click to expand...
Click to collapse
CWM is clockword mod recovery. An advanced recovery which has more options than stock recovery. I guess you already has cwm. Probably it must be what you used to flash the Rom and clear cache. Now to Titanium backup, it backs up the whole phone, so do cwm. As we use CWM for our flashing and other things, cwm backups should be enough unless you got space on your sd to have many backup files. And if your phone is working perfectly right now then its never late to take a cwm backup as if you ever encounter a bootloop while tweaking, you can restore your phone. Sometimes even cwm fails to fix your phone. This is where Odin comes in handy. Odin is a pc software which can be used to flash the stock Rom of your device. You can search and find the Stock Rom for your device and region if you google. You can find how to flash using odin guides out there. Flashing stock rom via odin will remove every traces of ever tweaking your phone which includes rooting, flashing of custom roms and kernels,etc. Your device will be just like when you bought it. This is helpful when you want to take your phone to service centres as rooting and doing other stuffs will void your warranty. Hopes this helps...
haridevil99 said:
CWM is clockword mod recovery. An advanced recovery which has more options than stock recovery. I guess you already has cwm. Probably it must be what you used to flash the Rom and clear cache. Now to Titanium backup, it backs up the whole phone, so do cwm. As we use CWM for our flashing and other things, cwm backups should be enough unless you got space on your sd to have many backup files. And if your phone is working perfectly right now then its never late to take a cwm backup as if you ever encounter a bootloop while tweaking, you can restore your phone. Sometimes even cwm fails to fix your phone. This is where Odin comes in handy. Odin is a pc software which can be used to flash the stock Rom of your device. You can search and find the Stock Rom for your device and region if you google. You can find how to flash using odin guides out there. Flashing stock rom via odin will remove every traces of ever tweaking your phone which includes rooting, flashing of custom roms and kernels,etc. Your device will be just like when you bought it. This is helpful when you want to take your phone to service centres as rooting and doing other stuffs will void your warranty. Hopes this helps...
Click to expand...
Click to collapse
Thank you.
I can tho not figure out how to know for sure if i have CWM or not. I have no apps called that.
And how do i do a CWM backup if i can start CWM some other way than using an app icon ?
behedwin said:
Thank you.
I can tho not figure out how to know for sure if i have CWM or not. I have no apps called that.
And how do i do a CWM backup if i can start CWM some other way than using an app icon ?
Click to expand...
Click to collapse
CWM is a shell and not an app and it cannot be installed on android os so you cant access it through your Rom but you can run it whenever you need it but through stock recovery. CWM comes as a .zip file which should be selected from stock recovery or in other words flash it. It will open cwm recovery. And you can access advanced recovery options which stock recovery doesn support. Well search and download cwm for your device, place it sd card root(not inside any folder), run it using install update option on your stock recovery, it will open cwm which will be in yellow colour themed. Select backup and restore opt in it and select backup. That will take care of taking full backup of your device.
haridevil99 said:
CWM is a shell and not an app and it cannot be installed on android os so you cant access it through your Rom but you can run it whenever you need it but through stock recovery. CWM comes as a .zip file which should be selected from stock recovery or in other words flash it. It will open cwm recovery. And you can access advanced recovery options which stock recovery doesn support. Well search and download cwm for your device, place it sd card root(not inside any folder), run it using install update option on your stock recovery, it will open cwm which will be in yellow colour themed. Select backup and restore opt in it and select backup. That will take care of taking full backup of your device.
Click to expand...
Click to collapse
Awesome, this thread have cleared many small things that come as so obvious for those that have done this for some time.
Perfect for me to quick understand what I am reading in threads and other sources.
I have now a CWM backup, Titan Backup and installed Odin and found my stock ROM to use if things goes to ****.
behedwin said:
Awesome, this thread have cleared many small things that come as so obvious for those that have done this for some time.
Perfect for me to quick understand what I am reading in threads and other sources.
I have now a CWM backup, Titan Backup and installed Odin and found my stock ROM to use if things goes to ****.
Click to expand...
Click to collapse
Well.. Thats good to hear. And there was none other than me. And anyway a small precaution, never interrupt while you are flashing through Odin coz it will hard brick your device which is literally R.I.P to your device.
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