Database Info

[Q] ClockworkMod vs Stock Recovery

Hi guys, fist post here, hopefully not a noobish one.
anyway.... I want to know why it is so important to install ClockworkMod? I mean, stock recovery isn't enough to work with, or fastboot for flashing, and "cat" or "bb" commands for dumping and system backups?.
That's it, Thanks for your help!!.

I didn't even check out the stock recovery, flashed CWM out of habit.
Usually the primary reason is so that you can flash "unsigned" zip updates to the phone, but I understand from some posts here that the stock recovery lets you do that.
Other big reasons are ability to make nandroid back ups and some extra features like mounting partitions while in recovery. I don't think the stock lets you do that.

distortedloop said:
Usually the primary reason is so that you can flash "unsigned" zip updates to the phone
Click to expand...
Click to collapse
I'm trying to update the framework-res.apk with an unsigned zip, I having no problem, but there is no change too.
I tried to apply a UOT Kitchen update, and its not working too.
Any tip?

NVMENOR said:
Hi guys, fist post here, hopefully not a noobish one.
anyway.... I want to know why it is so important to install ClockworkMod? I mean, stock recovery isn't enough to work with, or fastboot for flashing, and "cat" or "bb" commands for dumping and system backups?.
That's it, Thanks for your help!!.
Click to expand...
Click to collapse
CW has lots of extra features and options, that the stock recovery does not offer
many of which features are crucial to save your phone on those Crap Happens! moments

the brilliance of clockwork recovery is it lets you basically update to most any ROM just like an OTA update, from anywhere you are. sure, you can also just download any ROM thru the browser, but using clockwork along with ROM manager is the brilliance of it all...

Clockwork Recovery removes the need for renaming all of your flashable zips to update.zip every time. Enough said.

I think I found the perfect balance:
Code:
fastboot boot recovery-clockwork-X.X.X.X-crespo.img

[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

[Q] Unrooting problem

So i did something stupid right after rooting my Relay. I deleted basic stock files that are necessary for the phone to function properly. I was able to copy them from my current phone (rooted T-Mobile G2/Desire Z) onto an SD card and in turn push them back onto my Relay. My problem is that I still get error messages constantly after boot up and the simplest tasks can take hours (not to mention I can't use phone, contacts, messaging). I have seen all over the web (and XDA) about unrooting the phone and retuning it to stock. I was thinking that I could unroot, then reroot my Relay and that will solve my problem.
I was all set to unroot when I encountered yet another issue. Samsung-updates.com and sammobile both direct you to download the firmware files from hotfile. Hotfile has been shut down due to copyright infringement. Where I can find the stock firmware files now that hotfile has been shut down?
Please help me as I anxiously await using my new phone without the extra bloatware!
Thank you,
RockinRita

RockinRita said:
I was all set to unroot when I encountered yet another issue. Samsung-updates.com and sammobile both direct you to download the firmware files from hotfile. Hotfile has been shut down due to copyright infringement. Where I can find the stock firmware files now that hotfile has been shut down?
Click to expand...
Click to collapse
Would Samsung's Kies software be able to restore it to stock, or is it too far gone for Kies to work?

Bobby Tables said:
Would Samsung's Kies software be able to restore it to stock, or is it too far gone for Kies to work?
Click to expand...
Click to collapse
Without the stock files wouldn't Kies be pointless?

The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.

Pushing on a Relay
RockinRita said:
So i did something stupid right after rooting my Relay. I deleted basic stock files that are necessary for the phone to function properly. I was able to copy them from my current phone (rooted T-Mobile G2/Desire Z) onto an SD card and in turn push them back onto my Relay.
Click to expand...
Click to collapse
I did a very similar thing to my Relay and I can only get it boot off of the SD card. I am curious how you performed the push. I assumed that you
used adb push, but how?
Thanks,
Lou

scopedial said:
I did a very similar thing to my Relay and I can only get it boot off of the SD card. I am curious how you performed the push. I assumed that you used adb push, but how?
Thanks,
Lou
Click to expand...
Click to collapse
I copied the files from my rooted HTC Desire Z/ T-Mobile G2 to a spare SD card I have and then I inserted that card into my Relay and started it up. It took me a few hours to get passed all the error messages that constantly pop up. And then I went into my files, external SD and moved the files over to the system folder on the Relay. After several reboots, the error messages still are coming up which I why I need to unroot it and reroot it.

Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
You may have just saved me, Magamo! Thank you for saving them to Drive! Once I get on my old slow Dell laptop (i'm on my Chromebook now- which unfortunately doesn't support most things) I'll try to flash your files and update you here since I cannot comment on your post as I have not posted enough myself.

Stock ROM Restore Method I Used
Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?

furboom1240 said:
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?
Click to expand...
Click to collapse
I'll be honest, you've got me on this one. I've never used ODIN, and am not well versed in its use. But yes, this is sounds like a more technical way of doing it without the CWM flashables I've mentioned. -- Impossible in some situations. For example, my fiancee's phone's USB port has died for all purposes other than charging, So if I'm to send it in for a warranty repair, I'll have to use the method I posted.

Confused here
Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
Magamo,
I'm sorry, but I'm still totally confused here. Not sure how to flash the files in. I downloaded Kies and both of the zip files from your post. Successfully updated the firmware and my error messages are gone, but I don't have CWM on it. I extracted your files, but now what? I'm not very technologically inclined so this is all Greek to me.
furboom1240 said:
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?
Click to expand...
Click to collapse
furboom,
What is T699UVBMC5_HOME? How do I get the md5 sum of it? How do I use CWM to format /system? How do I get to stock restore? Again, I'm sorry for asking so many questions, i just have no clue what I'm doing here.
Thanks,
Rockin Rita

RockinRita said:
Magamo,
I'm sorry, but I'm still totally confused here. Not sure how to flash the files in. I downloaded Kies and both of the zip files from your post. Successfully updated the firmware and my error messages are gone, but I don't have CWM on it. I extracted your files, but now what? I'm not very technologically inclined so this is all Greek to me.
furboom,
What is T699UVBMC5_HOME? How do I get the md5 sum of it? How do I use CWM to format /system? How do I get to stock restore? Again, I'm sorry for asking so many questions, i just have no clue what I'm doing here.
Thanks,
Rockin Rita
Click to expand...
Click to collapse
If you don't have CWM, or some other custom recovery running on this, how did you get root in the first place? The easiest way to get root is to use heimdall or ODIN to flash CWM or another custom recovery, then flash Superuser or SuperSU using your new custom recovery.
The .zip files I linked are only meant to be flashed through recovery. Not Kies, not ODIN, not any other method.

Got it!!
With the help of this site (http://www.celldekho.com/how-to-unroot-samsung-galaxy-s-relay-4g/) and the file it linked to on rapidshare, along with your tip Magamo, I was able to unroot my Relay successfully. I'll reroot it later when I have the time and make sure not to delete important files LOL Thanks so much for the help!

[Q] Howto heimdall flash cwm recovery ??

Hi guys, my Galaxy tab 7.7 is still completely stock: Honeycomb and Touchwiz...... :crying: High time to move on!
Ultimately, I'd like to be able to try a few ROMs, using a ROM manager. When I want to install CWM from Google Play, it indicates that I need to manually install a recovery. I found found daniel_hk's tar files for the P6800 (CWM recovery)
I'm using a Linux PC, and I want to use Heimdall to flash. There is nothing on the Tab that needs to be preserved. (for the record: I've spent quite some time reading lots of threads on this, Googling stuff; and I I have experience with Linux arch & gentoo, so I am very used to doing my homework, but now I really need some help THANKS
My questions
1. Are these the correct steps I need to take? If not please correct me.
- flash CWM recovery
- reboot the Tab
- install CWM (as an app, from Google Play)
- then get Root? Using what app / method?
- flash the wanted ROM, using Heimdall, installing it using the ROM manager
2. it is enough to flash the recovery image, don't I need a cache.img as well? It's not in Daniel's .tar....
3. how will I flash? I don't really understand the heimdall GUI.... So , if i simply use the terminal, would I use
heimdall flash --no-reboot --RECOVERY recovery.img or is it better to leave the --no-reboot out ?
4. Will the recovery image (there is one for cwm 6.0.3.0 and cwm 6.0.4.3) only work with the corresponding cwm? Or will any image do?
Thank you all very much! [off topic ]Although the Linux kernel is in Android, for some reason it is hard to really understand it, maybe because words like 'firmware' or 'ROM' and 'kernel' seem to have a different meaning in Android/Phones compared to Linux/x86 PCs. That, plus you can 'brick' your PC - unless your flashing a BIOS or something : [/off topic ] Again, thanks in advance !

Never mind, i could not wait. I flashed with --no-boot, but then had to reboot manually. I will post a manual when I'm ready. So far: CWM installed, Root obtained, KitKat installed.

help with backups

So I have a j700p on boost, rooted it thanks to messi, installed xposed (credits to him too) and I'm using flashfire to flash zips. The problem is I want to install a custom rom and experiment with more risky things, which I'm too afraid to do because I can't backup and restore easily without a custom recovery.
Now I was doing some reading looking for guaranteed compatible roms for my phone, and a couple posts said that you don't need cr too install a custom rom since we have flashfire, however, that still doesn't cover backing up the phone and restoring without cr available. Should I brick my device or get it stuck in a boot loop I don't want to have to wipe and start with stock rom then reroot and install all my stuff again and again.
That leaves me stuck wondering what I should do. Should I just wait patiently while someone develops a cr for it (which I haven't seen anyone post about doing)? Or man up and hope some of these work? I really want to try to create a compatible twrp, but I know nothing about coding with xda, or with any language for that matter. I wouldn't know where to begin with it anyways.
Sorry if it seems like this isn't really a question but the above paragraph contains the questions I have.
Thx for reading!

What id do since its a custom rom and a custom roms dont require the userdata partition with the custom system. Stock roms require a userdata partition with the stock system to be flashed in a tar. id make a backup of the custom roms system, boot, and custom recovery in img format and then use unified toolkits basic toolkit to make the system and boot and custom recovery img a single odin flashable tar with the auto detect partitions option before it builds it.. test it just to make sure it flashes.
Partitions backup and restore..
https://play.google.com/store/apps/details?id=ma.wanam.partitions
Unifed toolkit
http://www.skipsoft.net/download/uat-v152/
Toolkit instructions.. download it.. extract it to c:... copy youre custom recovery and boot image and custom system imgs to unified toolkits input folder... go into unified toolkit run it the first time download some files then press 99 for basic tookit.. press 8 for make odin flashable tar... pick make single image of multiple images.... pick auto detect images.... let it build... exit once its done then go to unified toolkits output folder and there is you're odin flashable tar.

CoffeeNAndroid said:
What id do since its a custom rom and a custom roms dont require the userdata partition with the custom system. Stock roms require a userdata partition with the stock system to be flashed in a tar. id make a backup of the custom roms system, boot, and custom recovery in img format and then use unified toolkits basic toolkit to make the system and boot and custom recovery img a single odin flashable tar with the auto detect partitions option before it builds it.. test it just to make sure it flashes.
Partitions backup and restore..
https://play.google.com/store/apps/details?id=ma.wanam.partitions
Unifed toolkit
http://www.skipsoft.net/download/uat-v152/
Toolkit instructions.. download it.. extract it to c:... copy youre custom recovery and boot image and custom system imgs to unified toolkits input folder... go into unified toolkit run it the first time download some files then press 99 for basic tookit.. press 8 for make odin flashable tar... pick make single image of multiple images.... pick auto detect images.... let it build... exit once its done then go to unified toolkits output folder and there is you're odin flashable tar.
Click to expand...
Click to collapse
Thx for the fast reply like always coffee! That's the thing though, I'm on stock rom rooted and xposed, but I'm trying to get custom rom, but there's no custom recovery for boost mobile j7. I'm not worried about actually installing without the custom recovery (thank you once again chainfire) my issue is I can't restore any rooted backups on a bricked or bootlooping phone WITH that same bricked or bootlooping phone because because the recovery is stock, so the only option is to flash a stock rom back on, root it again, xpose it, then try again. The solution to this would be to make an Odin, adb, or fastboot flashable back up of the rooted stock rom I have now, but I can't make a flashable backup like that because there's no custom recovery to make one, do you see my dilemma?

Datipad said:
Thx for the fast reply like always coffee! That's the thing though, I'm on stock rom rooted and xposed, but I'm trying to get custom rom, but there's no custom recovery for boost mobile j7. I'm not worried about actually installing without the custom recovery (thank you once again chainfire) my issue is I can't restore any rooted backups on a bricked or bootlooping phone WITH that same bricked or bootlooping phone because because the recovery is stock, so the only option is to flash a stock rom back on, root it again, xpose it, then try again. The solution to this would be to make an Odin, adb, or fastboot flashable back up of the rooted stock rom I have now, but I can't make a flashable backup like that because there's no custom recovery to make one, do you see my dilemma?
Click to expand...
Click to collapse
You could make a stock tar rooted with stock recovery but youd have to include youre userdata partition since its on stock and you could do that with the toolkit and it would be odin flashable..

So do i have to use partitions backup and restore to get the partitions? because boot and recovery dont show up in the list, also my J7 isnt showing up on toolkit either with drivers installed and updated.
edit: Wont show up in windows explorer but shows in devices, tried switching to ptp mode and still no luck, trying to unistall driver and reinstall it but it looks like its also having trouble doing that
edit2: Got my phone to show up, and all is good with pc to phone connection, but the app still cant detect boot or recovery for some reason. I tried searching and so far i cant find anyone else who had the same problem, nor do any search results for that even exist. Ill keep trying though.