I would also like to know has this new version sudden death fix ?
Guys, everyone probably has the same question in mind. Can someone please answer. This the SDS fix is included in this version, I am sticking to the stock recovery.
Is your 64GB microSD formatted as exFAT ? If yes, the official CWM will likely *NEVER* support exFAT due licensing issues (exFAT is closed source and owned by Microsoft)
Just format it as FAT32; there is really no advantage to use exFAT over FAT32 !!
Is it possible to remove this files
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
without root with USB Debug off with Aroma Filemanager?
Yesterday I installed CWM with Odin, launched it, made full backup , but after reboot it changed to stock.
Now I have some problems to reflash it again. It stucks in the beginning or in the middle of flashing Recovery(or at the Setup Connection).
I'm trying to save data from internal to external memory because of blocked pattern lock on S3.
Guys, help me out please, I'm missing something here:
- I installed recovery-cwmtouch-6.0.2.8-GTI9300.tar by the book, no error.
When the phone reboots, CWM is not present anywhere inside the appdrawer.
When I boot vol up+home+power it boots in Stock Recovery.
Previously I rooted my S3 with CF-root CF-Auto-Root-m0-m0xx-gti9300.zip.
What am I missing here?
Stock Recovery being reflashed after a reboot?
There is an auto recovery restore system on stock roms that will reflash the Stock Recovery on a Stock Rom. If the restore files are renamed then CWM Recovery should not be overwritten after a reboot.
You need to be rooted and then delete or rename the following files:
Quote:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I got this and then stop...nothing
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping....
You can flash any recovery over any other recovery without any problems.I am on NeatRom with Philz recovery can I flash ClockworkMod Touch 6.0.2.8 normally?
i know,that my question is already asked in the threat,but no answer...
is there the SDS fix in CWM 6.0.28?
Walkthrough video by TotallydubbedHDQUESTION: Why are the backups size soo small now compared to the previous cwm backups?
ANSWER: Basically on the new cwm all the data is stored in a blobs folder in the clockworkmod folder. The backups folder now doesnt hold the actual data and instead the system and data files contain links to the files in the blobs folder (with the hash of the file as its filename). When you perform another backup only the changes have to be added so it performs incremental backups instead of full backups everytime. You can still flash different roms and back them up as any new data is stored in the blobs folder with the links in the backup folder. Several backups can share the same blobs file so over several backups the total file size of all the backups will be much much smaller. When you delete a backup via cwm you can then free space of the blob files that are no longer needed to keep everything tidy and make sure that no files are stored that arent referenced to any backup. If you don't free the space then any unused files will automatically be deleted when the next backup is performed.
You can then flash recovery without it being overwritten.