Recovery Twrp vs CWR - Verizon Samsung Galaxy S III

Any advantage over one from the other
Sent from my GT-N8013 using xda app-developers app

I Rio Wonder about that
Sent from my GT-I9100 using xda premium

this will be interesting hearing everyone's imput ... tho its all based on personal preferenceim sure .. i like cwr

I have used both in the past and still prefer CWM....no reason other than its what I learned to use when i was a noob....now Im a noob veteran.

droidstyle said:
I have used both in the past and still prefer CWM....no reason other than its what I learned to use when i was a noob....now Im a noob veteran.
Click to expand...
Click to collapse
I will second this, I like them both, in fact I still use TWRP on my Nook Tablet, but I've been using Koush's stuff for so long, over 3 or 4 phones now, that it just seems natural for me to use CWM.

TWRP for me. Its much faster and has nice features.

I use to be a CWM fan, that was until I started using TWRP on my Rezound. From then on I use TWRP, but I don't mind good ole CWM every once in a while.

TWRP because it's faster and the UI is easier to use simply because the tiles are large.

I like Amon Ra best of all. Oopps...wrong thread LOL!. I use TWRP on my Bionic and CWM on the Galaxy. Like mentioned above, CWM is what I learned on and for some reason it feels like more hands on.

Let me say this. My friend was running CM10 all the way from like september. I tried updating it in CWM but it gave me assert errors. Reflash TWRP on it, and flash latest nightlies no problem. Dirty flash too, just wipe dalvik and cache.

There isn't an objective answer that I can give. I'm biased towards pretty much anything that is alternative to what everyone else is using. Also, I have no data that would indicate one recovery is better than another. So here's my purely subjective answer.
I prefer TWRP over CWMR for several subjective reasons:
Coming from the original Moto Droid on vzw, I ran RZrecovery (a moded version of SPrecovery, which had an OC'd kernel and lots of options as well as charging while in recovery way before I had seen it anywhere else). Basically, I'm not accustomed to CWMR.
I'm not a fan of the differential backups that CWMR defaults to. I know it takes up more space to have an IMG or TAR for each partition I choose, but I'm a crack flasher and go back and forth between TouchWiz and AOSP based roms all the time. I need to be able to keep my backups completely seperate. No blobs. I need a golden master for each ROM I flash. With a 64GB externeal SD card and a 32GB internal card, I rarely run out of space.
I can name backups while booted into TWRP before you create the backup. The whole date being wrong in every recovery thing is indeed annoying.
I like the terminal. I prefer to root, flash, hack, etc etc on my own without help from apps and or pre-built tools (except for dsixda's android kitchen, which is so bloody easy to use it blow my friggin mind). So I don't need or want ROM Manager to do much of anything for me. I even flash TWRP via the terminal. GooManager always runs in the background, and hasn't really ever had the most up to date versions of TWRP, so I ditched it pretty fast. I hate apps that run in the background when I'm not using them.
I like the look and feel of TWRP. Its feels like a teeny version of android with a small but very functional UI. Only thing missing is a terminal emulator that I could use from within TWRP itself. (Choosing a command file to run just isn't the same, but it has come in handy)
I also like having backups go to a folder that is labeled with the device's SN. Seems like a really fantastical feature in the making, like a cloud based storage for TWRP could be somewhere off in the future, where you could backup multiple devices to one online storage space.
Its the only "alternative" in town. I like "alternative" aka not so main stream stuff, which is odd cause I'm not a fan of Alt Rock. More of a Hendrix, Zepplin "classic rock" (aka blues based rock n roll with lots of riffs on the minor pentatonic scale) kind of person.
Um, I don't really have an 8th reason. But I would like an OC'd kernel in TWRP to help speed up backups, but I dunno how viable that is.
Ta,
ALQI

alquimista said:
Um, I don't really have an 8th reason. But I would like an OC'd kernel in TWRP to help speed up backups, but I dunno how viable that is.
Click to expand...
Click to collapse
Tempting, but with backups/flashing/recovery, I think slow and steady wins the race.

I used to use cwm, but with the change to blobs all of my backups stopped working. Even ones I just made.
so I stopped trusting it.
I switched to twrp. The backups are larger I think, but I trust them more.
Sent from my SCH-I535 using xda app-developers app

Haven't had any problems with TWRP, and it was the first I used. So pretty much just became acquainted with it and haven't seen a reason to switch.

I use CRW on my phone and TWP on the Kindle Fire. The best advice I can give is use what ever method the dev tells you to use, if he goes out of his way to mention it there is probably a good reason behind it.
One thing about CRW I wish would get fixed is the file name date being wrong (When it saves a file it gives the file a name based on the date but all current versions save it with an incorrect date (it thinks its 1970 lol) If i dont change it right away I end up with a bunch of mystery backups.
Another thing to remember about the latest CRW's is the blob. To save space during the saving of a backup a file (blob) is created that has any redundant info shared by backups in it. So all the info for your latest backup file isn't all in the file with that backups name some or most of it is in the blob file. So if you want two or three backups from your phone saved to your home computer make sure you take the entire clockworkmod file because if you take just the individual CRW backup file (1970 -blah-blah-blah) you will be missing all the info on the blob. CRW will let you restore with the partial file and that can get ugly fast.

I've always used cwr but I will give twrp a shot, love trying new stuff. And the date issue with cwr is really annoying. I'm sure it could be renamed but I don't want to change anything and get an md5 mismatch.
Sent from my SCH-I535 using xda app-developers app

Related

[Q] Where are the Pros at?!

Hi there,
I have a few questions and after trying the search function, I decided to start a new thread!
I am used to using Acronis True Image or Ghost on my PC, to backup entire Operating Systems. Is there anything like that for Android?
I would like to be able to backup a ROM, install another ROM, and then, if i want to, switch between them...
After installing a stock ROM again, I was surprised to see that it wasn't that bad at all...it was actually relatively quick. Why shouldn't I just remove all the crap of a stock ROM and use that instead of using a custom ROM?!
thanks,
Georgios
Yes inside of cwm there is a backup mode you can use. It does exactly what you mentioned just have to make sure your not hopping from a rom that's incompatible with another rom/partition etc,and you'll be fine. Other than that its your choice on how you like your phone. Me personally I would not of kept this phone without our devs on here I love their Roms and kernels. Imo
.......infuse.....Infused....infusion.........
Backing up ROMs
Don't know about backing up the ROM, but you really should wipe your phone before installing a new ROM unless you KNOW otherwise. Afterall, each ROM will re-write parts of your phone's operating system. Wiping before each install will ensure you start out clean. There is a program called "Odin" that will make this an easy process. There are different versions of Odin and each one can perform different tasks, so read up on using it BEFORE you jump in head first. Odin can be used to install individual files, like kernals, or master clear your phone or it can take your phone back to stock. Most ROM devs will include in their instructions what you need to do to install ROM. Although I believe it's hard to brick the Infuse (unless you jump in head first), IT CAN HAPPEN!
Read Read Read!
Regarding restoring your programs to make it easier, Titanium Backup is probably the best at backing up your programs. Afterall, restoring ALL your programs can cost you alot of time if you don't have a program like the ones you use on your PC.
Note that you must pay for the Pro Titanium Backup to be able to use the "Batch" feature. The batch feature will allow you to reinstall selcted programs automatically without any interaction. Without "Batch", you will have to keep pushing the install button for every program you want to reinstall THE PRO VERSION IS WELL WORTH THE SMALL AMOUNT YOU PAY!
For me, installing ROMs is kind of an addiction. Installing the ROMs are fun. Granted they take a little time, but..........
Sorry to be long winded as I didn't know whether you were asking as a newbie to the ROM world
tyshemi said:
Yes inside of cwm there is a backup mode you can use. It does exactly what you mentioned just have to make sure your not hopping from a rom that's incompatible with another rom/partition etc,and you'll be fine. Other than that its your choice on how you like your phone. Me personally I would not of kept this phone without our devs on here I love their Roms and kernels. Imo
.......infuse.....Infused....infusion.........
Click to expand...
Click to collapse
Thanks for the fast reply! I actually tried to create a backup/restore with cwm. it worked fine. However, I didn't try to bring back another ROM yet. I wonder if the current backup is going to be deleted if you install with cwm another ROM?! With Acronis/Ghost you install Windows, create an Image to another partition or hidden partition. You can then install another version of windows and do the same thing, create the Image, store it on another partition and you can then bring back which one you like!
G
MaverickCoast said:
Don't know about backing up the ROM, but you really should wipe your phone before installing a new ROM unless you KNOW otherwise. Afterall, each ROM will re-write parts of your phone's operating system. Wiping before each install will ensure you start out clean.
Click to expand...
Click to collapse
Thats what I thought. It makes sense, I do the same thing when installing windows...
There is a program called "Odin" that will make this an easy process. There are different versions of Odin and each one can perform different tasks, so read up on using it BEFORE you jump in head first. Odin can be used to install individual files, like kernals, or master clear your phone or it can take your phone back to stock.
Click to expand...
Click to collapse
I am gonna give it a try...
Most ROM devs will include in their instructions what you need to do to install ROM. Although I believe it's hard to brick the Infuse (unless you jump in head first), IT CAN HAPPEN!
Click to expand...
Click to collapse
I hope not!!!
Read Read Read!
Click to expand...
Click to collapse
Doing it right now
Regarding restoring your programs to make it easier, Titanium Backup is probably the best at backing up your programs. Afterall, restoring ALL your programs can cost you alot of time if you don't have a program like the ones you use on your PC.
Click to expand...
Click to collapse
Gonna give this one a try as well...
Note that you must pay for the Pro Titanium Backup to be able to use the "Batch" feature. The batch feature will allow you to reinstall selected programs automatically without any interaction. Without "Batch", you will have to keep pushing the install button for every program you want to reinstall THE PRO VERSION IS WELL WORTH THE SMALL AMOUNT YOU PAY!
Click to expand...
Click to collapse
OK...
For me, installing ROMs is kind of an addiction. Installing the ROMs are fun. Granted they take a little time, but..........
Click to expand...
Click to collapse
I am the same way...but now I have twin boys and plenty of sleepless nights! I don't need the extra "work"...
Sorry to be long winded as I didn't know whether you were asking as a newbie to the ROM world
Click to expand...
Click to collapse
Its all good! Thanks!
...one more thing: I believe CWM is storing the backup on the local sd card, right?! If there would be a way to change the path to the external sd card, it would be perfect...
thanks,
G
MaverickCoast said:
Don't know about backing up the ROM, but you really should wipe your phone before installing a new ROM unless you KNOW otherwise. Afterall, each ROM will re-write parts of your phone's operating system. Wiping before each install will ensure you start out clean.
Click to expand...
Click to collapse
BTW, what is the best for wiping the phone clean? doing through CWM???
thanks,
G
neavissa said:
BTW, what is the best for wiping the phone clean? doing through CWM???
thanks,
G
Click to expand...
Click to collapse
Yes cwm is best for wiping the phone, and you should be able to change the path to.save if not just move it with an app like root explorer.
.......infuse.....Infused....infusion.........
Wiping phone
neavissa said:
BTW, what is the best for wiping the phone clean? doing through CWM???
thanks,
G
Click to expand...
Click to collapse
To get back to stock, I've used GTG's Ultimate Unbrick/Return to stock, found here: http://forum.xda-developers.com/showthread.php?t=1116251
I just prefer using Odin. CWM is an internal program. Odin is an external program.
Just my preference
neavissa said:
...one more thing: I believe CWM is storing the backup on the local sd card, right?! If there would be a way to change the path to the external sd card, it would be perfect...
thanks,
G
Click to expand...
Click to collapse
that would be difficult for most users, im sure you'd have to get into the recovery image and edit it a bit. you may just be able to copy the backup to the external card manually.
im a fan of stock-ish roms as well but im also a flash junkie, seems deodexed roms run a little choppier at times, i cant verify this but stock phones in the store never seem too laggy despite all the memory mods and "lag-fixes" we use around here. i think it may also have to do with the build environment for the custom kernels, some just work better than others despite similarities in the feature set and shared sources among the community. i reember a while back when i got my captivate a developer had a thread discussing toolchains and there effect on wakeup lag which was an issue early on in i9000 development.

[Recovery] Rogue XM Touch Recovery v1.5.0-R1 (CWM-based v5.0.2.8) [2012-05-25]

Rogue XM Touch Recovery v1.5.0-R1
(CWM-based Recovery v5.0.2.8)
For the Asus Transformer TF101​
First off, thank you to...
Team Rogue
Koush
CyanogenMod Team
j-r0dd
Solarnz
Roach2010​
All I did slap together all their hard work to make it work on the TF101.​
Sources
Rogue Recovery
The source and more info for Rouge Recovery is available in the Xoom release thread from Team Rogue. I have not made any modifications to it to work with the TF101. You can find that thread here:
http://forum.xda-developers.com/showthread.php?t=1235170
The discussion of the touch release in that thread begins here:
http://forum.xda-developers.com/showthread.php?t=1235170&page=13#123​
Recovery Kernel
I used the kernel from Roach2010's ClockworkMod Recovery 3.2.0.1 release here:
http://forum.xda-developers.com/showthread.php?t=1213723​
Device Tree
Mostly based on AOKP's TF101 device tree, just picked out the parts needed to compile the recovery. Particularly BoardConfig.mk:
https://github.com/rburrow87/android_device_asus_tf101_recoveryonly​
Updates
[2012-05-25] 1.5.0-R1 (5028-based)
Updated to Rogue XM Recovery v1.5.0 which is touch-enabled with the same features as before. See the Xoom release thread for more information on Rogue Recovery:
http://forum.xda-developers.com/showthread.php?t=1235170
Can also finally use the boot to recovery option available in some ROMs thanks to the recovery boot loop fix from Roach2010 from here:
http://forum.xda-developers.com/showthread.php?t=1213723
Workaround for small menu targets
http://forum.xda-developers.com/showpost.php?p=26142147&postcount=151
If I can figure out a way to just make the menu items taller, I'll make an update. Otherwise I'm waiting for Rogue to implement it first.​
[2012-01-14] 1.3.0-R1 (5027-based)
Original release, non-touch​
Info
Mounting as USB storage does not work. (Accessing the tablet or SD card from your computer when plugged in via USB)​
Installation
I tested this the best I could, but use at your own risk. I am not liable for data loss, spontaneous combustion, temporal anomalies, or anything in between.
Just flash the attached zip from CWM.
There's also an nvflash version that has the recovery.img in it and will only flash the recovery if you prefer that method. Or just so you don't have to unpack the blob file if you need the recovery.img.​
Misc:
I did this because I thought it'd be nice to have a newer recovery for our TF101s, but also because I want to learn to do some sort of development even if it's just building for similar devices. I'm still new to using anything like git or using C/Java like this so don't expect miracles right away if bugs come up! I have some experience with other languages, but not in this kind of application.
Thank you, looks nice. Doing a nand backup right now with it.
there was someone in one of the ics threads, looking for this, they,ll be chuffed to bits.
Sent from my HTC Desire using XDA App
Cam you just rename this img if u wanna flash with nvflash?
Sent from my Dell Streak using Tapatalk
baseballfanz said:
Thank you, looks nice. Doing a nand backup right now with it.
Click to expand...
Click to collapse
Awesome!
will8578 said:
there was someone in one of the ics threads, looking for this, they,ll be chuffed to bits.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I saw that post! I've been watching that thread and trying it out when there's an update.
80slovechild said:
Cam you just rename this img if u wanna flash with nvflash?
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
To do that, you have to extract the zip and then unpack the blob file... but I updated the OP with an extra nvflash version that flashes just the recovery and gives you the recovery.img.
Finally...a relatively current back up for the TF!!
THANK YOU!!
Backing up with 3201, then installing this.
Beautiful work!! Works flawlessly!
Finally! A 5.x.x.x CWM recovery
Does this allow flashing from both internal and external?
On my Galaxy Nexus, they also have a touch softkey mod that has softkeys for up, down, back, and select. Not a big deal but something cool to look into if you get bored.
LTE EX Galaxy Nexus - CM9 AOKP
Asus Transformer - Revolver
Can we get a list of features? I've never flashd CWM 5.x.x.x so just curious, and would make a good addition I think..
luna_c666 said:
Can we get a list of features? I've never flashd CWM 5.x.x.x so just curious, and would make a good addition I think..
Click to expand...
Click to collapse
It's basically the same as 3207 with the ability to flash from and back up to internal memory.
And seems a bit more stable.
Worked for me. Way way way better color scheme and it booted quick! Thanks!
wackydroid said:
It's basically the same as 3207 with the ability to flash from and back up to internal memory.
And seems a bit more stable.
Click to expand...
Click to collapse
its definitely not the same as v3.x.... that being said however, simply look at the android_bootable_recovery github to see the differences since v3.x
I think with the latest versions its even possible to use the mount usb with the tablets own MicroSD card where-as in the v3.x tree it wasnt (thanks to v5.x's inclusion of dual mount support, specifically done to support devices with large internal storage)
Still, i have to agree with everyone else, its REALLY nice to finally see a v5.x CWM... using it on my HD2, Evo Shift, and HeroC, it really was a surprising difference from when I was sticking with v3.x
Just awesome!!! Thanks so much!
this needs to be moved to the dev section, but great job!
Sent from my Transformer TF101 using xda premium
Thanks! Installed successfully on two separate rooted B60 TF101's(ARHD 3.2, and Krakd 1.4.2)without any issues. Works great nice job!
New recovery works great!
Just flashed this without any issue. Nice look and feel. Are there more options available under the 'wipe' option, such as ability to wipe only cache or Dalvik cache like the 3.2.0.1 had? I haven't had a chance to look yet and didn't want to chance inadvertently wiping my device. Thanks.
[EDIT] I've now had time to look around and answer my own question. Yes, the other wipe options are there under the wipe menu item. Good to not see that sd card error all the time. So far it seems pretty flawless and better looking, too. I had to reflash my ROM last night and got to put it through it's paces.
Good job and thanks for carrying forward with recovery.
I did notice that at least on mine, I saw no 'connection' between the progress bar when doing a full advanced backup to the plugin SDCARD (normal backup as in the old days), or in other words, no sign of progress despite it working fine. I'm looking around the code to see what might have caused that.
The other interesting change not mentioned is that the backup file format/suffix is now .tar instead of .img. I tried using Titanium to restore an app from the backup with the .tar files, and it worked fine. Is .tar what the current versions of cwm are using?
Lastly: I know that to burn a kernel you have to use blobs on the tf101, so which .tar file contains the kernel blob? (I've not yet analyzed this yet and have assumed that you have to actually burn a kernel afterward to get one in place). What I was wondering is if we could get the equivalent of 'boot.img' from other v5 cwm's that are around, but I suppose ours would have to burn a blob rather than just unpack a .tar file.
EDIT: After reading through the original post about Rogue Recovery, I realized that in the last / prior release notes it mentioned this:
*Progress indication disabled by default again for speed (create /sdcard/clockworkmod/.hidenandroidprogress to enable progress)
Which took care of my initial gripe so check on off to me not reading enough ..
Thanks again --
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
jwilliamf said:
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
Click to expand...
Click to collapse
I also did a back up and restore and my Wifi is fine.
I did not do the advance backup just the regular backup.
Someone else reported this wifi problems using Roach's 3.2.0.1 CWM also.
jwilliamf said:
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
Click to expand...
Click to collapse
Hmm, weird, I'm not sure why the recovery would break that unless it's failing to restore something or possibly failed to back something up. I did several backups and restores when I was checking to see if everything worked and never encountered that. Maybe try restoring the one giving your trouble a couple of times to see if it comes back?
hachamacha said:
Good job and thanks for carrying forward with recovery.
I did notice that at least on mine, I saw no 'connection' between the progress bar when doing a full advanced backup to the plugin SDCARD (normal backup as in the old days), or in other words, no sign of progress despite it working fine. I'm looking around the code to see what might have caused that.
The other interesting change not mentioned is that the backup file format/suffix is now .tar instead of .img. I tried using Titanium to restore an app from the backup with the .tar files, and it worked fine. Is .tar what the current versions of cwm are using?
Lastly: I know that to burn a kernel you have to use blobs on the tf101, so which .tar file contains the kernel blob? (I've not yet analyzed this yet and have assumed that you have to actually burn a kernel afterward to get one in place). What I was wondering is if we could get the equivalent of 'boot.img' from other v5 cwm's that are around, but I suppose ours would have to burn a blob rather than just unpack a .tar file.
EDIT: After reading through the original post about Rogue Recovery, I realized that in the last / prior release notes it mentioned this:
*Progress indication disabled by default again for speed (create /sdcard/clockworkmod/.hidenandroidprogress to enable progress)
Which took care of my initial gripe so check on off to me not reading enough ..
Thanks again --
Click to expand...
Click to collapse
Looks like somewhere around CWM 4 is when the switch to tar was made. It has better the speed along with the ability to back up and restore the correct filesystem. Sounds like the progress thing was added somewhere around then as well.
[ Found here: https[colon]//plus.google[dot]com/103583939320326217147/posts/G4VQuCpR25y Sorry, can't make outside links yet. ]
Looking at a kernel zip, it uses dd to put the blob in /dev/block/mmcblk0p4, which is also where the recovery goes... I clearly need to learn more about what's going on here when flashing a kernel or recovery to the same thing and what the function of the blob is.
Looking in the nandroid backuip system tar though, it grabs the /system/lib/modules folder which some kernel zips add to, so the nandroid is backing that up. I'm not sure if nandroid, at least in its current state, is able to back up or restore the kernel itself because of the whole blob thing?
Hmm, perhaps I should make a feature list instead of just saying look at the Xoom release thread!

[TOOL] G2X Cleanup Batch *** WARNING *** WILL FORMAT INTERNAL SD

If you are going to flash and ICS ROM after this tool please make sure to first install a GB then ICS otherwise your SD card will not be accessible. I am trying to find a fix but it has been illusive. This statement will be removed once a fix has been found and OP updated.
Now with CWM Touch!
This method uses NVFLASH to recreate all partitions and formats them, thereby getting rid of the file allocation pointers and hence renders data inaccessible without effort.
Note: I have never seen a file come back to life or its data affect other files without effort on the users part or a temporary glitch once the partitions and pointers have been overwritten. Please post a reply with evidence if you have seen it.
Benefits:
The contents of the zip file can be used to super clean G2X before a new ROM flash. This tool recreates all the partitions in the phone so wipes the pointers to all files (everything). The method it employes has existed from before. The files here will stop short of pushing a ROM, so that you can push your favorite ROM.
Prerequisites:
G2X (Will not work on O2X due to different partition table)
Desire to have a clean install of your favorite ROM
Backup your data
*** WARNING ***​
This tool will wipe both phone internal memory and internal SD card. External SD card content is safe.
Don't say you haven't been warned!
What to do:
Download the attached Zip file.
Take out the battery (assuming you have backed up your data on external SD card, computer or elsewhere), connect the device via USB while holding VOL+ and VOL- together. Don't let go of the volume buttons until the device is recognized.
(I typically leave Device Manager open to see when it shows up in the list under "USB Controllers").
Launch flash.bat, sit back and wait until the process finishes (generally a good idea to open a command prompt, CD to the directory and then run the file).
Unplug, put battery in, reboot into CWM recovery (pushed by this tool) by holding VOL- first, then pressing and holding POWER).
Flash your favorite ROM.
Enjoy!
I made this package because I could not get the bluetooth to work with G2x GB 2.3.3 (and below). The issue was a disconnect problem where both the phone and headset would still think they were connected but in audio would not be routed for a call or media. After this procedure my phone has not had an issue for almost 3 weeks now. I have tried it with two ROMs and 3 different headsets without any issues.
I guess I will not toss this phone after all .
Putting it out there in the hope that it may help others solve some of their issues as well. I suspect bad data stays in places not touched by other methods.
Your comments are most welcome.
[Update]
Klathmon has made an newer version with CWM 5.0.2.8. RP by Klathmon can be found here:
http://forum.xda-developers.com/showpost.php?p=24768294&postcount=66
I have tested the windows version but linux one is untested. Use at your own risk.
[Update]
Now with CWM Touch!
Thanks to everyone who has contributed on this thread with a drive to positive change! You work/comments/suggestions are very much appreciated.
References:
http://forum.xda-developers.com/showthread.php?t=1248644. This link was the inspiration for the current work.
Link to CWM Touch development thread. I took the image posted there: http://rootzwiki.com/topic/22984-recovery-touch-enabled-cwm-5813/
[EDIT] The zip file should be fixed now. Darn work machine does something to the upload.
was just about to flash the new hellfire rom and saw this tool! will try it out and see how things go
edit: yeah corrupt zip on my end too.
The zip file seems to be corrupt. Could you re-upload plz
worked great on my end, no problems.
khanggle said:
worked great on my end, no problems.
Click to expand...
Click to collapse
The real test is how stable your ROM would stay with this method to wipe than any of the other methods.
I guess only time will tell .
wow this method really blaze hellfire much thanks to your( you) & (rom dev)
Ohh I like this. Thank you for sharing .
This thing is faster than nullifier, and I especially like how you don't need to be in CWM to use it. It just seems like doing it in "update mode" would allow better manipulation of the phone's internals.
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
He states in OP that it doesn't write anything, therefor doesn't "nullify". It formats and partitions.
dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
mansa_noob said:
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
MWBehr said:
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
Click to expand...
Click to collapse
Done. OP updated to reflect. Thanks for clarifying that. It was not my intention to state that this tool does anything any other does, or does not.
I think we are all trying to do the same thing... get rid of the issues when swapping ROMs like _____. I can't seem to think of a good analogy here .
thanks for clarifying the OP, that makes much more sense
and no i wasnt trying to say you were reinenting the wheel, just trying to understand what your tool is actually doing
and also i do understand that it would take effort to get data off any type of storage device once the partition has been erased. i deal with wiping hard drives in a data center all the time. we use a DOD wipe tool that writes 1s and 0s over a drive a minimum of three full times to eradicate the data
but with this tool doing it outside of CWM, it sounds like it may do a better job of it
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
I was thinking the same thing but seems easy enough .. add the cwm img to the dir and edit the .cfg file. Hopefully that should get the new CWM flashed
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
mansa_noob said:
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
Click to expand...
Click to collapse
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
PL0X_Kleiner said:
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
i think it would be pointless unless you are super paranoid
dodgefan67 said:
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
i think it would be pointless unless you are super paranoid
Click to expand...
Click to collapse
Nobody is twisting any arms here... Use it if you want to, don't if you don't want to.
I saw benefit so posted so that others may benefit as well.
Sent from my LG-P999 using XDA
Ok so question, why are you killing all the data on your internal SD card? Why not just the individual partitions that the phone uses? Your destroying data that don't need to be destroyed before flashing a rom...
Sent from my LG-P999 using xda premium
It does not have to be destroyed. I just haven't had a chance to test without recreating emmc yet.
Next step. Likely tomorrow. Would like to test before release.
Sent from my LG-P999 using XDA
[edit] BTW, I do want to restate that there is some data that needs to be destroyed which is not being taken care of by other methods. I don't believe it is in the emmc, but rather it resides in one of the other partitions. Most methods out there are only working in the /data, /system and /cache domain.
My original problem (bluetooth disconnect) which happens to be a problem for some in the community even now was only completely fixed by this method.

[Rooting & ROM Flashing VZW GS3] Noob Questions

I apologize in advance for asking the following noob questions. I have been an iPhone user for 3 years and wanted to take advantage of the GS3, which I am loving even without it being rooted. I am fairly tech-savy and believe I'll have no problem rooting my phone. There are just a few things I want to thoroughly understand. I've been sold on the fact that I want to root my phone to gain control of it, remove the bloatware, and extend it's battery life, etc. If there is a thread or posting or website somewhere that explains what I need to know very well, please direct me!!
I was looking for some major tips on the best way to achieve my goal of rooting and flashing to a new ROM...If someone could, PLEASE answer EVERY question. I'd like to fully understand how to get to my goal of rooting and flashing to a desired ROM without bricking it. If this gets desires attention, it could be a great sticky posts for other newbies!
1. First and foremost...What is a kernal? I see things about CM9/CM10 kernals. Is it something like a ROM? How is it related/different?
2. What is the CMW, what is a Touch Wiz?
3. What is the overall best way for a newbie to root their phone and install a desired ROM? Odin or???
4. As I understand thus far, there is rooting, then there is ROM flashing, and then there is something to do with unlocking the bootloader... I'd like to fully understand all of these.
Here's my goal and what I'm seeking help on... I think I want to use the Synergy ROM. What is the first step I must do? Do I somehow root my phone and then use Odin to flash to the Synergy ROM? Or is the first step simply opening Odin, connecting phone, and flashing to Synergy ROM? Do I not even use Odin to flash to Synergy? I'm confused here based on the install info in Synergys FAQ - do I use Odin at all??? Do I need to back anything up? Do I need to download or use some app to block Verizon OTA updates permanently??
In the Q&A of the Synergy ROM thread, it states:
You should have an unlocked bootloader if you wish to take full advantage of this ROM.
Click to expand...
Click to collapse
Must I unlock the bootloader seperately via this thread here, or do ROMs or other kernals (or whatever) have the unlocked bootloader built-in?? Do I install the bootloader before I root or after I root? What's the best way to unlock the bootloader(mmmeff's EZ-Unlock App, Terminal Emulator, or Adam Outler's Casual for Rooting/Cwm/Unlocking Bootloader)? Also, how do I keep the bootloader from being updated OTA, to keep from having problems????
I think that answers most/all of my questions. I'd hugely appreciate a response and answers to clarify all this, or links to some post or site I'm missing that explain all this to me. My goal to to root my phone, likely install a ROM, and do all this without bricking it, and hopefully without voiding any warranties (though not a big deal).
Thanks a bunch in advance!!
All the answers you seek can be found in droidstyle's guide. It's a sticky in the development section.
Sent from my SCH-I535 using xda app-developers app
Introduction to Rooting:
This is meant as a very basic disccussion for people completely new to rooting and Android. As a result, it will omit many details and simplify others. If there is a blatant mistake, please let me know and I'll correct it, but if there's something that's just not QUITE right, chances are it's simplified on purpose. Also, it's not meant to be a rooting guide (as there are excellent ones out there already) so much as an explanation of concepts most of us take for granted, but noobies don't.
DISCLAIMER: I, nor anyone else referenced (or not) in this thread, am not responsible for what you do with your phone. Rooting and otherwise altering your phone has the potential to brick your device, void your warranty, and many other horrible horrible things. Perform these actions at your own risk.
What is root/rooting?
In Unix-style operating systems, "root" is the name of the user who has all permissions and is therefore able to run/modify/change/delete just about anything. If you're familiar with Windows, this account is called Administrator. The default account (that's you!) on an Android phone does NOT have these privileges. Rooting is the process of obtaining them (i.e. obtaining root access). Once you root, you can "flash" new software onto your phone without restriction. This is great because you now have control over what programs are on your phone, what your UI looks like, how your phone handles resources, what kernels you run, and more!
Once your phone is rooted, you don't always wield all of that power. You control your access to all these new abilities with a program called SuperUser (available on the market and baked into ROMS). This program can grant these special rights to any other program that requests them. So let's say a program wants to write data to a place it's not allowed. It will ask SuperUser to up its privileges and then BAM! it can write where it wants to. You yourself can gain SuperUser privileges in a shell by typing su. Then YOU can read, write, and execute to your hearts desire.
Before you root:
Before rooting, there are some basic things you should know. A lot of people rush into it without bothering to learn everything they should. Sometimes it goes well, and sometimes it doesn't.
Phone partitions: Your phone has a number of partitions. The important ones to know at first are:
1. System - this partition is essentially what you think of when you think of the operating system, the Android UI, and preinstalled
apps. When people talk about flashing ROMs (e.g. CyanogenMod, Synergy, etc), they are talking about flashing a new system
partition.
2. Boot - this is the kernel and ramdisk. The kernel is responsible for managing the interactions between the phones software (including the ROM) and the
hardware. Altering the kernel can increase/decrease performance, battery life, and more because it manages applications and system resources. When
you flash a new kernel, it flashes to the boot partition. You may not notice a big difference like you do when changing ROMS, but behind the scenes, your
phone's performance can be drastically altered. A *LOOSE* analogy is that the ROM is like the body and interior of your car (including exterior color, AC,
stereo, heated seats, TV in headrests, etc.) and the kernel is like the engine. You may not see it, but you'll know it's there if it's awesome or it sucks.
3. Aboot - this was largely unimportant for newbies until the bootloader lock/unlock situation. The short story is that aboot contains functions which
authenticate the boot partition (that's the kernel, remember?). It checks to see if your boot partition is Verizon legal and if not, it aborts the boot process
and politely tells you to contact Verizon. This authentication is what is referred to as a "locked" bootloader. It prevents you from completely booting the
phone with a custom kernel. The bootloader is "unlocked" by replacing the stock aboot partition with one that does NOT check up on the boot partition.
This is important because it allows us to run whatever kernel we want.
4. Data - this contains user installed apps, settings, contacts, bookmarks, etc, etc, etc. You can wipe this partition (as opposed to the above partitions) and
still boot into the operating system. You will have just lost all your setting and apps. This is called a factory/data reset.
5. Cache - this is stuff that you frequently use so it's kept available for better performance. You can wipe it without much consequence.
6. Recovery - this partition contains a separate operating system that allows you to recover from a corrupted/absent/otherwise jacked up operating system. It
has other functions as well. The big ones are to backup your device and restore said backups, to wipe certain partitions, and to flash things to your
phone (i.e. install new ROMs, recoveries, or other programs). The stock recovery is limited so you will definitely want a custom recovery, created by the
fine devs in the community, on your device.
What is a ROM and what is a kernel? I touched on this above. A ROM is what goes on the system partition. It contains what you think of as the Android OS including the UI and preinstalled apps. It controls how programs interact with you, the user. A kernel controls how those programs interact with the phones hardware. You need both a ROM and a kernel to have a functional phone.
How do I get started rooting and flashing?
There is an excellent guide stickied in the development thread here http://forum.xda-developers.com/showthread.php?t=1762709. However, many of us
forget what it's like to be a COMPLETE newbie and to someone who has no idea about anything, even fantastic guides like that can be a little intimidating.
You can follow the steps, but may not understand what you're doing. The steps to take to start out with are:
1. Make sure you understand what I've written above. Make sure you are comfortable with the possibility of bricking your phone.
2. Root your device. As I said above, this is simply gaining root/Admin/whatever you want to call it access on your phone. In and of itself, it does NOT alter
the ROM or kernel or much of anything else. However, there are many different ways to obtain root and some of them DO alter these things. The easiest
and safest way to root (IMO) is to use Noxious Ninjas excellent tool. http://forum.xda-developers.com/showthread.php?t=1792342. If you like it, I
encourage you to donate or at least "Thanks" him. It works by taking advantage of debugfs permissions to get su (remember this from above??) onto
your phone with permissions set so you can run it. It therefore doesn't change ROMs or anything else. You won't lose data, apps, or anything else. It just
sneaks su right onto your current setup.
3. Install a custom recovery. This will allow you to do all the fun stuff I talked about above. I recommend installing EZ-recovery from the market and flashing
CWM 6.0.1.0.
1. Install EZ-recovery
2. Under the "Recovery" heading, click the Recovery radio button and select CWM 6.0.1.0 next to it.
3. Click flash
4. Backup everything as if your life depended on it. This means backing up your IMEI as shown here
http://rootzwiki.com/topic/32397-tutorial-imeibackup-nv-with-qpst-us-variants/ and making a nandroid. A nandroid is an image of your phone
including your ROM, your data, and your kernel(depending on what phone you have). You can restore a nandroid backup and you'll be right back where
you were before flashing or changing things around. The steps to making a nandroid are:
1. Turn off your phone.
2. Hold down volume up, home, and power until recovery appears.
3. Use the volume rocker to go to "backup and restore" and hit the power button
4. Select backup and then select the external (default) or internal (labeled "internal") SD card
You can restore a nandroid in a similar fashion (although you should wipe data/cache first - see below).
5. Unlock the bootloader. You must do this seperately from flashing ROMs and kernels. Refer to this thread http://forum.xda-developers.com/showthread.php?t=1839791 and give appropriate thanks! A warning...if you mess up your aboot partition, there's really nothing (that I know of) you can do to revive your phone besides send it to someone with JTAG or back to Verizon.
You're now ready to start flashing ROMs.
As a precursor, there are ROMS that are based on TouchWiz modified Android from Verizon/Samsung and there are ROMS based on AOSP (e.g. CyanogenMod). TW roms need a TW kernel and AOSP roms need an AOSP kernel. Until you get comfortable with everything, I would stick with TW. Also, some roms come with kernels and will flash the kernel to your boot partition as well as the ROM to your system partition. Some ROMs don't come with kernels. ALWAYS ALWAYS ALWAYS read the OP of a rom you want to flash to find out kernel information as well as how to install the rom and anything else you may need to know. The general steps to flashing a ROM are (remember to read the OP for specifics):
1. Backup apps, data, call log, contacts, messages, etc. My program of choice for much of this is Titanium Backup available on the market. Buy it as you'll
use it a billion times.
2. Download the ROM you want and check the MD5
3. Place the ROM on the root of your SD card. Do NOT unzip it.
4. Reboot into recovery and make a nandroid backup
5. Wipe data/factory reset and wipe cache. Wipe it more than once if paranoid.
6. Go to "install zip from sdcard" and select the ROM you want
7. If you want/need to flash a kernel, install that zip from the sdcard too with the same command
8. Reboot and restore all that you backed up
Remember:
- ALWAYS backup before doing anything
- verify MD5
- wipe data and cache (unless told not to by the ROM dev)
- NEVER accept an OTA (having a custom recovery should block OTAs anyway)
PS. The techniques, tools, roms, etc in this post are not mine and arte the products of hours of hard work by multiple devs. Please thank them accordingly.
Bleelas said:
Introduction to Rooting:
This is meant as a very basic disccussion for people completely new to rooting and Android. As a result, it will omit many details and simplify others. If there is a blatant mistake, please let me know and I'll correct it, but if there's something that's just not QUITE right, chances are it's simplified on purpose. Also, it's not meant to be a rooting guide (as there are excellent ones out there already) so much as an explanation of concepts most of us take for granted, but noobies don't.
DISCLAIMER: I, nor anyone else referenced (or not) in this thread, am not responsible for what you do with your phone. Rooting and otherwise altering your phone has the potential to brick your device, void your warranty, and many other horrible horrible things. Perform these actions at your own risk.
What is root/rooting?
In Unix-style operating systems, "root" is the name of the user who has all permissions and is therefore able to run/modify/change/delete just about anything. If you're familiar with Windows, this account is called Administrator. The default account (that's you!) on an Android phone does NOT have these privileges. Rooting is the process of obtaining them (i.e. obtaining root access). Once you root, you can "flash" new software onto your phone without restriction. This is great because you now have control over what programs are on your phone, what your UI looks like, how your phone handles resources, what kernels you run, and more!
Once your phone is rooted, you don't always wield all of that power. You control your access to all these new abilities with a program called SuperUser (available on the market and baked into ROMS). This program can grant these special rights to any other program that requests them. So let's say a program wants to write data to a place it's not allowed. It will ask SuperUser to up its privileges and then BAM! it can write where it wants to. You yourself can gain SuperUser privileges in a shell by typing su. Then YOU can read, write, and execute to your hearts desire.
Before you root:
Before rooting, there are some basic things you should know. A lot of people rush into it without bothering to learn everything they should. Sometimes it goes well, and sometimes it doesn't.
Phone partitions: Your phone has a number of partitions. The important ones to know at first are:
1. System - this partition is essentially what you think of when you think of the operating system, the Android UI, and preinstalled
apps. When people talk about flashing ROMs (e.g. CyanogenMod, Synergy, etc), they are talking about flashing a new system
partition.
2. Boot - this is the kernel and ramdisk. The kernel is responsible for managing the interactions between the phones software (including the ROM) and the
hardware. Altering the kernel can increase/decrease performance, battery life, and more because it manages applications and system resources. When
you flash a new kernel, it flashes to the boot partition. You may not notice a big difference like you do when changing ROMS, but behind the scenes, your
phone's performance can be drastically altered. A *LOOSE* analogy is that the ROM is like the body and interior of your car (including exterior color, AC,
stereo, heated seats, TV in headrests, etc.) and the kernel is like the engine. You may not see it, but you'll know it's there if it's awesome or it sucks.
3. Aboot - this was largely unimportant for newbies until the bootloader lock/unlock situation. The short story is that aboot contains functions which
authenticate the boot partition (that's the kernel, remember?). It checks to see if your boot partition is Verizon legal and if not, it aborts the boot process
and politely tells you to contact Verizon. This authentication is what is referred to as a "locked" bootloader. It prevents you from completely booting the
phone with a custom kernel. The bootloader is "unlocked" by replacing the stock aboot partition with one that does NOT check up on the boot partition.
This is important because it allows us to run whatever kernel we want.
4. Data - this contains user installed apps, settings, contacts, bookmarks, etc, etc, etc. You can wipe this partition (as opposed to the above partitions) and
still boot into the operating system. You will have just lost all your setting and apps. This is called a factory/data reset.
5. Cache - this is stuff that you frequently use so it's kept available for better performance. You can wipe it without much consequence.
6. Recovery - this partition contains a separate operating system that allows you to recover from a corrupted/absent/otherwise jacked up operating system. It
has other functions as well. The big ones are to backup your device and restore said backups, to wipe certain partitions, and to flash things to your
phone (i.e. install new ROMs, recoveries, or other programs). The stock recovery is limited so you will definitely want a custom recovery, created by the
fine devs in the community, on your device.
What is a ROM and what is a kernel? I touched on this above. A ROM is what goes on the system partition. It contains what you think of as the Android OS including the UI and preinstalled apps. It controls how programs interact with you, the user. A kernel controls how those programs interact with the phones hardware. You need both a ROM and a kernel to have a functional phone.
How do I get started rooting and flashing?
There is an excellent guide stickied in the development thread here http://forum.xda-developers.com/showthread.php?t=1762709. However, many of us
forget what it's like to be a COMPLETE newbie and to someone who has no idea about anything, even fantastic guides like that can be a little intimidating.
You can follow the steps, but may not understand what you're doing. The steps to take to start out with are:
1. Make sure you understand what I've written above. Make sure you are comfortable with the possibility of bricking your phone.
2. Root your device. As I said above, this is simply gaining root/Admin/whatever you want to call it access on your phone. In and of itself, it does NOT alter
the ROM or kernel or much of anything else. However, there are many different ways to obtain root and some of them DO alter these things. The easiest
and safest way to root (IMO) is to use Noxious Ninjas excellent tool. http://forum.xda-developers.com/showthread.php?t=1792342. If you like it, I
encourage you to donate or at least "Thanks" him. It works by taking advantage of debugfs permissions to get su (remember this from above??) onto
your phone with permissions set so you can run it. It therefore doesn't change ROMs or anything else. You won't lose data, apps, or anything else. It just
sneaks su right onto your current setup.
3. Install a custom recovery. This will allow you to do all the fun stuff I talked about above. I recommend installing EZ-recovery from the market and flashing
CWM 6.0.1.0.
1. Install EZ-recovery
2. Under the "Recovery" heading, click the Recovery radio button and select CWM 6.0.1.0 next to it.
3. Click flash
4. Backup everything as if your life depended on it. This means backing up your IMEI as shown here
http://rootzwiki.com/topic/32397-tutorial-imeibackup-nv-with-qpst-us-variants/ and making a nandroid. A nandroid is an image of your phone
including your ROM, your data, and your kernel(depending on what phone you have). You can restore a nandroid backup and you'll be right back where
you were before flashing or changing things around. The steps to making a nandroid are:
1. Turn off your phone.
2. Hold down volume up, home, and power until recovery appears.
3. Use the volume rocker to go to "backup and restore" and hit the power button
4. Select backup and then select the external (default) or internal (labeled "internal") SD card
You can restore a nandroid in a similar fashion (although you should wipe data/cache first - see below).
5. Unlock the bootloader. You must do this seperately from flashing ROMs and kernels. Refer to this thread http://forum.xda-developers.com/showthread.php?t=1839791 and give appropriate thanks! A warning...if you mess up your aboot partition, there's really nothing (that I know of) you can do to revive your phone besides send it to someone with JTAG or back to Verizon.
You're now ready to start flashing ROMs.
As a precursor, there are ROMS that are based on TouchWiz modified Android from Verizon/Samsung and there are ROMS based on AOSP (e.g. CyanogenMod). TW roms need a TW kernel and AOSP roms need an AOSP kernel. Until you get comfortable with everything, I would stick with TW. Also, some roms come with kernels and will flash the kernel to your boot partition as well as the ROM to your system partition. Some ROMs don't come with kernels. ALWAYS ALWAYS ALWAYS read the OP of a rom you want to flash to find out kernel information as well as how to install the rom and anything else you may need to know. The general steps to flashing a ROM are (remember to read the OP for specifics):
1. Backup apps, data, call log, contacts, messages, etc. My program of choice for much of this is Titanium Backup available on the market. Buy it as you'll
use it a billion times.
2. Download the ROM you want and check the MD5
3. Place the ROM on the root of your SD card. Do NOT unzip it.
4. Reboot into recovery and make a nandroid backup
5. Wipe data/factory reset and wipe cache. Wipe it more than once if paranoid.
6. Go to "install zip from sdcard" and select the ROM you want
7. If you want/need to flash a kernel, install that zip from the sdcard too with the same command
8. Reboot and restore all that you backed up
Remember:
- ALWAYS backup before doing anything
- verify MD5
- wipe data and cache (unless told not to by the ROM dev)
- NEVER accept an OTA (having a custom recovery should block OTAs anyway)
PS. The techniques, tools, roms, etc in this post are not mine and arte the products of hours of hard work by multiple devs. Please thank them accordingly.
Click to expand...
Click to collapse
THANK YOU!!!!! Very helpful! I had no idea I needed EZ-Recovery to flash CWM as the primary recovery tool - that saved me big time as I was about to unlock the bootloader later today.
After posting this last night, and awaiting responses, I was browsing and trying to take in as much as I could. I finally realized that each section in the linked guide is a different way to either root or install a ROM. After I figured this out, and read about Odin being best for newbies, I decided to take the risk and wing it, even though I wasn't 110% sure.
So, now I'm rooted and have ROM manager/CWM installed, TiBu, and ES File Explorer installed. Now I'm just trying to figure out what I can/cannot remove as far as bloatware. A few items I'm sure I'd like to keep (working), so I don't want to mess with anything that might be used in another app/widget....Which brings me to my next question...
What's the best way to remove bloatware? I found an excel spreadsheet online that shows what's safe/unsafe to remove but I'm confused as to what I should do to get rid of items I NEVER want, and how to turn off items I MAY want in the future. If I freeze these items, do they stay frozen upon reboot, and until I unfreeze, or otherwise? What's the difference between a .APK package and a single process, etc?
Thanks in advance! I feel like I entered Android Elementary last night and already graduated to Android Junior High!
P.S. The captchas on this site to post ARE THE WORST CAPTAS IVE SEEN IN MY ENTIRE FRIGGIN LIFE, MY GOD!!!! I must refresh it 20x til something is RELATIVELY clear. Seriously????
ike034 said:
1...
Click to expand...
Click to collapse
Me too..... But the post are suppose to me helpful and or contribute in some way....
But at least we can thank all over the place......
Weioo said:
THANK YOU!!!!! Very helpful! I had no idea I needed EZ-Recovery to flash CWM as the primary recovery tool - that saved me big time as I was about to unlock the bootloader later today.
After posting this last night, and awaiting responses, I was browsing and trying to take in as much as I could. I finally realized that each section in the linked guide is a different way to either root or install a ROM. After I figured this out, and read about Odin being best for newbies, I decided to take the risk and wing it, even though I wasn't 110% sure.
So, now I'm rooted and have ROM manager/CWM installed, TiBu, and ES File Explorer installed. Now I'm just trying to figure out what I can/cannot remove as far as bloatware. A few items I'm sure I'd like to keep (working), so I don't want to mess with anything that might be used in another app/widget....Which brings me to my next question...
What's the best way to remove bloatware? I found an excel spreadsheet online that shows what's safe/unsafe to remove but I'm confused as to what I should do to get rid of items I NEVER want, and how to turn off items I MAY want in the future. If I freeze these items, do they stay frozen upon reboot, and until I unfreeze, or otherwise? What's the difference between a .APK package and a single process, etc?
Click to expand...
Click to collapse
Glad to hear you're rooted and learning a lot! Now you're opening another HUGE can of worms, namely how Android organizes the application framework, what are services, processes, activities, tasks etc. You may have already found the information you're looking for, but a montrously dumbed down version is that the APK is a package containing the compiled program and all the extraneous files it needs to run while a process is an actively running application. In order to debloat, you can either freeze an application with another program like TiBu, or you can manually freeze it by changing the app extension, or you can delete the APK, or you can remove it from the rom you want BEFORE you even flash it. What you choose depends on your goals...why you want to debloat.
Weioo said:
THANK YOU!!!!! Very helpful! I had no idea I needed EZ-Recovery to flash CWM as the primary recovery tool - that saved me big time as I was about to unlock the bootloader later today.
After posting this last night, and awaiting responses, I was browsing and trying to take in as much as I could. I finally realized that each section in the linked guide is a different way to either root or install a ROM. After I figured this out, and read about Odin being best for newbies, I decided to take the risk and wing it, even though I wasn't 110% sure.
So, now I'm rooted and have ROM manager/CWM installed, TiBu, and ES File Explorer installed. Now I'm just trying to figure out what I can/cannot remove as far as bloatware. A few items I'm sure I'd like to keep (working), so I don't want to mess with anything that might be used in another app/widget....Which brings me to my next question...
What's the best way to remove bloatware? I found an excel spreadsheet online that shows what's safe/unsafe to remove but I'm confused as to what I should do to get rid of items I NEVER want, and how to turn off items I MAY want in the future. If I freeze these items, do they stay frozen upon reboot, and until I unfreeze, or otherwise? What's the difference between a .APK package and a single process, etc?
Thanks in advance! I feel like I entered Android Elementary last night and already graduated to Android Junior High!
P.S. The captchas on this site to post ARE THE WORST CAPTAS IVE SEEN IN MY ENTIRE FRIGGIN LIFE, MY GOD!!!! I must refresh it 20x til something is RELATIVELY clear. Seriously????
Click to expand...
Click to collapse
Have you decided on a ROM you want to use yet? Personally I think that takes a lot of the decisions about de-bloating out of the equation. Pick a ROM, flash it, and see what you got? I first did the de-bloated root method and didn't have the stock e-mail app! While it is easy to download an e-mail app from the play store I was still shocked that it was considered bloat by the builder of the particular de-bloated version I chose.
Currently I am on Synergy 1.7 r23 with Darkhorse theme. I also like the Color in HD theme but can't decided between the two.
Bleelas said:
Glad to hear you're rooted and learning a lot! Now you're opening another HUGE can of worms, namely how Android organizes the application framework, what are services, processes, activities, tasks etc. You may have already found the information you're looking for, but a montrously dumbed down version is that the APK is a package containing the compiled program and all the extraneous files it needs to run while a process is an actively running application. In order to debloat, you can either freeze an application with another program like TiBu, or you can manually freeze it by changing the app extension, or you can delete the APK, or you can remove it from the rom you want BEFORE you even flash it. What you choose depends on your goals...why you want to debloat.
Click to expand...
Click to collapse
Awesome, the explanation of what a .APK is helped a TON! Thank you!
dan_joegibbsfan said:
Have you decided on a ROM you want to use yet? Personally I think that takes a lot of the decisions about de-bloating out of the equation. Pick a ROM, flash it, and see what you got? I first did the de-bloated root method and didn't have the stock e-mail app! While it is easy to download an e-mail app from the play store I was still shocked that it was considered bloat by the builder of the particular de-bloated version I chose.
Currently I am on Synergy 1.7 r23 with Darkhorse theme. I also like the Color in HD theme but can't decided between the two.
Click to expand...
Click to collapse
I know you've been helping me in my other thread. Thanks again for everything! I believe you know now, I am on Synergy r46, running quite stable so far but I haven't done much to the phone since flashing.
I've got a noob question... is there any way to back up your IMEI and install the samsung drivers from a Mac besides running Parallels or VMware? I rooted using Adam Outler's Casual and would like to start flashing ROM's but don't want to risk it without backing up my IMEI first.
See the note in this thread that backing up IMEI is obsolete. Nowadays you use the method linked from that thread, which does not involve making a backup first.
Weioo, I'd like to thank you for your intelligent questions, willingness to read, and attitude in this forum. It's good to see someone posting in the correct place, educating theirself, and not coming into the forum saying something like "plz help my phone wont boot and i didnt read enouf". So, respect. :good:
Anyway, to add something to this thread. What version of Clockwork Recovery are you using? If you're using version 6+, let me say a little how to manage your backups. The new CWR stores its backups in /sdcard/clockworkmod/backup/, which will only be about 20mb in size - this is normal. The backup file is just sort of an index, and the other couple hundred megabytes meat of the backup is stored as a ton of tiny files in /sdcard/clockworkmod/blobs/. If you ever need to clean up space on your phone's storage, always delete the backup file and do not touch the blobs directory. When you make your next backup, CWR will clean up the space freed from deleting that backup file.
What's actually going on is that instead of making one big file as a copy of a phone's complete image (as CWR did in previous versions), it saves space by backing up each file individually. If you have two backups with the exact same file (having the same hash), CWR deduplicates that by only backing it up once. The blobs folder has each fine, with the hash as its filename, and the backup file includes which hashes (filenames) it needs to function. When very few things change in between backups, the new backup only has to add new blobs for the things that changed (and thus have a different hash). You don't delete the blobs directly because it's not obvious which ones are used and which aren't. When CWR cleans up space, it reads the backup files and deletes blobs that aren't associated with any existing backups.
rednukleus said:
See the note in this thread that backing up IMEI is obsolete. Nowadays you use the method linked from that thread, which does not involve making a backup first.
Click to expand...
Click to collapse
Okay thanks, but if I do flash something and lose my IMEI, to do that process I'd need to be running Parallels or VMware on my Mac. Basically I'm trying to figure out if there is another way to do this using a mac or would I need to buy one of those programs if I lose my IMEI?
Great beginner post
lazarus2405 said:
Weioo, I'd like to thank you for your intelligent questions, willingness to read, and attitude in this forum. It's good to see someone posting in the correct place, educating theirself, and not coming into the forum saying something like "plz help my phone wont boot and i didnt read enouf". So, respect. :good:
Anyway, to add something to this thread. What version of Clockwork Recovery are you using? If you're using version 6+, let me say a little how to manage your backups. The new CWR stores its backups in /sdcard/clockworkmod/backup/, which will only be about 20mb in size - this is normal. The backup file is just sort of an index, and the other couple hundred megabytes meat of the backup is stored as a ton of tiny files in /sdcard/clockworkmod/blobs/. If you ever need to clean up space on your phone's storage, always delete the backup file and do not touch the blobs directory. When you make your next backup, CWR will clean up the space freed from deleting that backup file.
What's actually going on is that instead of making one big file as a copy of a phone's complete image (as CWR did in previous versions), it saves space by backing up each file individually. If you have two backups with the exact same file (having the same hash), CWR deduplicates that by only backing it up once. The blobs folder has each fine, with the hash as its filename, and the backup file includes which hashes (filenames) it needs to function. When very few things change in between backups, the new backup only has to add new blobs for the things that changed (and thus have a different hash). You don't delete the blobs directly because it's not obvious which ones are used and which aren't. When CWR cleans up space, it reads the backup files and deletes blobs that aren't associated with any existing backups.
Click to expand...
Click to collapse
This should be stickied!!
My apologies for the newb questions, but last night I modded my phone to Eclipse 2.1 version 10-20-12 with the latest GAPPS 10-21-12 ( http://forum.xda-developers.com/showthread.php?t=1934572 ). This latest GAPPS seems to be missing a bunch of applications including GMAIL registration (to access the Play store successfully) as well Google Now and many other Google based apps (Google Maps, Google Voice, etc etc). I don't believe the ROM was installed incorrectly - I went through the prerequisite Wipe Cache/Wipe Partition/Wipe Dvalik Cache and even Fix Permissions. Also the Voice Search application is missing, but maybe that's tied in with the Google suite of apps not running correctly.
Being that I'm a newb on this site I can't post the question over on the Eclipse page (not allowed access with less then 10 posts) but I find it impossible to properly register/access Google Play as well as using any of the Google Apps. I went ahead and downloaded Google Now separately and installed the APKs but this just resulted in the program crashing when the GPS is enabled (keeping it disabled keeps Google Now at the "Initializing" screen).
Thanks for any support that can be provided.
ResolveD
Disregard the previous post - used GAPPS from 10-12-12 (w/o Dvalik cache wipe) and Google Now, Voice Search, G-mail register, Google Play all work fine now. The only issue I see is presently with the Google Now browser not scrolling through links, but you can always use the magnifying glass (which shows you previews of the webpages it finds).
Anyways HIGHLY RECOMMENDED ROM!!! Eclipse 10-20 build (4.1.2) w/10-12 GAPPS. Easily the best ROM out there so far :laugh:
Deleting System apps
Now that I have finally rooted my VZW GS3, and installed Titanium Backup Pro, am I able to delete system apps from there without damaging anything? I have not installed a custom ROM, all I have done is root, unlock bootloader and install CWM. I want to get rid of bloatware (e.g. Polaris Viewer) can I use TI BU Pro?
levilib said:
Now that I have finally rooted my VZW GS3, and installed Titanium Backup Pro, am I able to delete system apps from there without damaging anything? I have not installed a custom ROM, all I have done is root, unlock bootloader and install CWM. I want to get rid of bloatware (e.g. Polaris Viewer) can I use TI BU Pro?
Click to expand...
Click to collapse
Yes.
Sent from my SCH-I535 using xda app-developers app
levilib said:
Now that I have finally rooted my VZW GS3, and installed Titanium Backup Pro, am I able to delete system apps from there without damaging anything? I have not installed a custom ROM, all I have done is root, unlock bootloader and install CWM. I want to get rid of bloatware (e.g. Polaris Viewer) can I use TI BU Pro?
Click to expand...
Click to collapse
Just wanted to add that it may be better to just freeze the apps, or at least run a nandroid backup so you can revert to stock. Without all system apps intact an OTA update would fail.
apacseven said:
Just wanted to add that it may be better to just freeze the apps, or at least run a nandroid backup so you can revert to stock. Without all system apps intact an OTA update would fail.
Click to expand...
Click to collapse
I'm not worried about an OTA update, and I made a nandroid, I just want to make sure I'm not going to delete anything important. are there any apps you can think of that I would want to delete but it would cause problems?

[Q] What is your preference on CWM vs TWRP?

I wanted to get some opinions because I saw a friend use twrp and it looked pretty nice, but cwm is good too.
Diumlol said:
I wanted to get some opinions because I saw a friend use twrp and it looked pretty nice, but cwm is good too.
Click to expand...
Click to collapse
TWRP all the way. Only thing I see it doesn't have is battery stats wipe, but you can use an app or a root file manager for that. It's touch for free, has more options for back/restore, is faster, supports open scripts, has a file manager(made my crash course in init.d scripts and tweaks much easier just by letting me delete a script or copy an old backup of a file back over and reboot), has a terminal(useful for things like restoring permissions to an individual file), and is able to format sd-ext in ext4 instead of ext3(big boost for my sd-ext partition), moreover there is no limit big or small to the size of swap and sd-ext partitions).
Diumlol said:
I wanted to get some opinions because I saw a friend use twrp and it looked pretty nice, but cwm is good too.
Click to expand...
Click to collapse
yes cwm is good but twrp is better
TWRP better than CWM
Try this one
Diumlol said:
I wanted to get some opinions because I saw a friend use twrp and it looked pretty nice, but cwm is good too.
Click to expand...
Click to collapse
I used to have TWRP installed, but after I installed my last ROM, I noticed that my backup created a 0 folder, and another 0 folder in it with duplicate folders, so I made a little research and I found Philz touch recovery.
I haven't had that issue again, and it works fine.
You can find it here: http://forum.xda-developers.com/showthread.php?t=2028103
TWRP, easier to use and better UI.
my favourite is cwm :good:
I've only recently gotten into the Rooting/Modding "scene" but I've caught the addiction.
I find myself now backup up (what I find) stable instances, and installing new roms over and over.
I started with TWRP because of the guide I initially used to root my phone, but I have since switched to CWM..
I switched to CWM initially as the ROM I was installing recommended it, but since I have grown to it's simplicity.
Keep in mind when using these recoveries, that some people will find that they get errors using one or the other when installing new roms..
So in using these, I would say it can be based on personal taste, and what's been working for you.. but if you find a rom that errors during install, some developers on these forums may suggest something just as simple as switching to another version of that recovery, or switching from TWRP to CWM (and vice versa).
Are these answers technically based? I mean, is there any technical difference between them?
I only got errors on installing Int2Ext4 saying invalid zip file which also happened on another ROM with CWN and Int2Ext. So I unzipped it, pushed it back to phone and used TWRP's file manager to copy to /system/etc/init.d and its terminal to set proper permissions. When CWM errored, I had to use ADB to do what TWRP let me do right on the phone. Both ways worked but TWRP saved headaches in that instance
Sent from my Wildfire S A510e using xda app-developers app
They both work well, but in my experience twrp is faster and have a more user friendly interface.
i think more people use a cwm,i have system cyanogenmod i i love use a cwm with this software
Twrp- because its less painful thanks to touch.Makes it easier and fast to navigate
chiragjn said:
Twrp- because its less painful thanks to touch.Makes it easier and fast to navigate
Click to expand...
Click to collapse
There is CWM with touch for a while now... :good:
I have used both and I didn't find any difference, but maybe I just did very basic stuff.
I have painfully (and maybe stupidly) found out that TWRP has an option to wipe /system and, with that, it will wipe ITSELF! :silly:
I am using cwm,its very good！

Categories

Resources