Hi All,
I need real help with ClockworkMod Recovery. I have been installing Android on HD2 using storage card (haret.exe) method. Then I moved to NAND without any problems.
But I am not able to understand ClockworkMod Recovery at all. I looked at lots of threads and also the main thread for ClockworkMod Recovery. I know how to install it. I have installed it on my phone. But for some reason I was stuck in the loop after installing the ROM {[22 JAN] -=MDJ's CyanogenMod 7 v. 2.6 [A2SD+][GRH78C][RMNET][Kernel: MDJ S10.4 OC]}. I did exactly same as the video tutorial says. My radios and HSPL is fine. Coz I am able to use the same ROM in NAND mode. But still in ClockworkMod Recovery mode the phone kept restarting and never got to the main screen.
I also do not know what ext2, ext3, ext4 partitions are. Do I need to make them before installing the ROM? Also on the main thread for ClockworkMod Recovery, it has 3 partition files. 250MB, 350MB and 450MB. I do not know what that is. Which one to use for which ROM and what are the differences between them?
What is the use of ClockworkMod Recovery if I have to flash this partitions every time I install new ROM?
Also can someone tell me what backing up the ROM means? Does it mean I can back up my current one and flash new one, and if I do not like the new one I can restore the old one in the same state (with my APPS and SETTINGS)?
Please please help me with ClockworkMod Recovery fundamentals. I would really appreciate it.
One more thing, I would not post a question if I haven't looked around enough for answers. As you can see I have been doing this from months, but only asked one question before and this is the second one. So please do not take me for someone who does not look around for answers. I do, its just that I did not find anything real good to explain me from the bottom. So please someone help me out.
Thanks in advance.
EXT partitions can be thought of as extended partitions on your SD card. They are used to "extend" your storage capacity. Some ROMS place some of the ROM files on the SD-EXT partition. This is done particularly for the EU HD2 where it has only half the storage on-board that the TMOUS HD2 does. If you are using a ROM that requires one you do have to create the partitions before installing/flashing the ROM.
The three different flash.cfg files on the CWM thread are files used to instruct DFT how to re-partition your on-board storage (NAND). There are several partitions, up to 16 at the moment. Some ROM's use 4 partitions, some use 6 or more. Typically, non-CWM ROM's use only 4 partitions (boot, system, data, cache), whereas CWM ROM's use those same ones as well as a miscellaneous and recovery partition.
The main reason for the different files is that some ROM's use more space for the system partition. The different flash.cfg files just simply allocate more or less space to the system partition.
You don't technically have to flash new partitions every time you flash a new ROM. As long as you know how to modify the ROM to work with your current partition setup it will work. Or, get ROM's that use the same type of partition layouts. Since the release of CWM, more ROM's are becoming available for installation via the ZIP deployment method in CWM, which means they ALL use the same partition (with exception of the system partition size) setup.
If you have a TMOUS HD2 with plenty of onboard storage it's easier to just create a larger system partition and never have to worry about repartitioning. That's what I did. I have a 450 MB system partition and every time I deploy a new CWM ZIP ROM I don't have to repartition anything.
You nailed it on the head about backing up via CWM. It backs up all your partitions (boot, system, cache, sd-ext, data, etc) and saves them to your SD card. That way you can flash a new ROM or do a hard reset. Then later if you want you can do a full restore and be exactly where you left off before doing so. That is, if you flash a ROM that has the same partition layout. If you flash a ROM with a different partition layout, the restore may or may not work until you repartition the same as the original ROM was when you flashed it.
The only issue with all this is that since there isn't a set standard yet for ROM's and their partition layouts any ROM chef can define their own partition scheme which can make for a hassle when trying different ROM's. I expect that at some point there will be a standard set of partitions that will be used between all different chefs to make things easier. CWM ROM deployments and updates are definitely the future of this and how all native Android devices are handled. I imagine that will become the case down the road for the HD2 as well.
Hopefully that clears it up for you a bit. Sorry about writing a novel...
Digital Outcast said:
EXT partitions can be thought of as extended partitions on your SD card. They are used to "extend" your storage capacity. Some ROMS place some of the ROM files on the SD-EXT partition. This is done particularly for the EU HD2 where it has only half the storage on-board that the TMOUS HD2 does. If you are using a ROM that requires one you do have to create the partitions before installing/flashing the ROM.
The three different flash.cfg files on the CWM thread are files used to instruct DFT how to re-partition your on-board storage (NAND). There are several partitions, up to 16 at the moment. Some ROM's use 4 partitions, some use 6 or more. Typically, non-CWM ROM's use only 4 partitions (boot, system, data, cache), whereas CWM ROM's use those same ones as well as a miscellaneous and recovery partition.
The main reason for the different files is that some ROM's use more space for the system partition. The different flash.cfg files just simply allocate more or less space to the system partition.
You don't technically have to flash new partitions every time you flash a new ROM. As long as you know how to modify the ROM to work with your current partition setup it will work. Or, get ROM's that use the same type of partition layouts. Since the release of CWM, more ROM's are becoming available for installation via the ZIP deployment method in CWM, which means they ALL use the same partition (with exception of the system partition size) setup.
If you have a TMOUS HD2 with plenty of onboard storage it's easier to just create a larger system partition and never have to worry about repartitioning. That's what I did. I have a 450 MB system partition and every time I deploy a new CWM ZIP ROM I don't have to repartition anything.
You nailed it on the head about backing up via CWM. It backs up all your partitions (boot, system, cache, sd-ext, data, etc) and saves them to your SD card. That way you can flash a new ROM or do a hard reset. Then later if you want you can do a full restore and be exactly where you left off before doing so. That is, if you flash a ROM that has the same partition layout. If you flash a ROM with a different partition layout, the restore may or may not work until you repartition the same as the original ROM was when you flashed it.
The only issue with all this is that since there isn't a set standard yet for ROM's and their partition layouts any ROM chef can define their own partition scheme which can make for a hassle when trying different ROM's. I expect that at some point there will be a standard set of partitions that will be used between all different chefs to make things easier. CWM ROM deployments and updates are definitely the future of this and how all native Android devices are handled. I imagine that will become the case down the road for the HD2 as well.
Hopefully that clears it up for you a bit. Sorry about writing a novel...
Click to expand...
Click to collapse
Amazing explanation. Thanks a lottt man. Just one more question, I have TMOUS HD2 abd I did the same thing as you said. 450MB of partition. And then tried to install the MDJ's CM7 ROM. I got the message saying the ROM is successfully installed. and then I rebooted my phone. But it kept rebooting itself. Any particular reason you know of?
jalshah05 said:
Amazing explanation. Thanks a lottt man. Just one more question, I have TMOUS HD2 abd I did the same thing as you said. 450MB of partition. And then tried to install the MDJ's CM7 ROM. I got the message saying the ROM is successfully installed. and then I rebooted my phone. But it kept rebooting itself. Any particular reason you know of?
Click to expand...
Click to collapse
Is this using the 400 MB flash.cfg file from the CWM thread? The reason I ask is that I checked that flash.cfg file and the boot partition is flagged as the bootable partition. I'm not familiar with the CM7 ROM from MDJ, but is it set to deploy via CWM with a boot folder in the ZIP file?
Also, have you run logcat (if you're familiar with that) while the issue is happening to see what is going on?
To be very frank I did not understand what you just told me sir. Only thing I can tell for sure is I downloaded the .zip file from the thread at http://forum.xda-developers.com/showthread.php?t=877777 . And I do not know what logcat is. I am sure you must be thinking that I am an idiot. Forgive me for my ignorance.
Google is your friend!
I'm a better one: http://wiki.cyanogenmod.com/index.php?title=Logcat
Edit: very interesting read by the way, Digital Outcast. Much appreciated!
Digital Outcast said:
Is this using the 400 MB flash.cfg file from the CWM thread? The reason I ask is that I checked that flash.cfg file and the boot partition is flagged as the bootable partition. I'm not familiar with the CM7 ROM from MDJ, but is it set to deploy via CWM with a boot folder in the ZIP file?
Also, have you run logcat (if you're familiar with that) while the issue is happening to see what is going on?
Click to expand...
Click to collapse
Thanks a lott Digital Outcast for this amazing explanation. I hope I can get the Recovery mode working. I will try some different roms and see what can be done. meanwhile if you get chance please explain me your response "Is this using the 400 MB flash.cfg file from the CWM thread? The reason I ask is that I checked that flash.cfg file and the boot partition is flagged as the bootable partition. I'm not familiar with the CM7 ROM from MDJ, but is it set to deploy via CWM with a boot folder in the ZIP file?
Also, have you run logcat (if you're familiar with that) while the issue is happening to see what is going on?"
Thanks a lott once again.
To all the devs around here. Great work by the way!! Not that I wanna know all the technical details, but it would be nice to get an overview of how things work together on the GT.
I have a PC Windows and Linux background, but I don't fully understand as of yet how things blend together on the tab.
Can you explain a few things;
How come flashing a ROM doesn't wipe the entire system? Is a rom pretty much the same as a ghost image for PC?
How are system files (OS) differentiate with your media/videos for example.
If you install a custom kernel (see pershoot for example), will installing a rom overwrite the newly installed kernel, or do they reside in a different place on the disk? If so, can you explain.
How are things separated on the GTAB? Where is CWM installed, is it something similar to a PC bios that you flash with a custom bios?
The internal memory is split up (probably partitioned but it could be something else) into the system area and the user area that acts like the sd card does in most android devices. System files are in the system area, your media files are on the part acting like an sd card.
ROMs contain their own kernel which will overwrite your custom kernel but as long as the custom kernel is compatible with the ROM you can flash the custom kernel over the ROMs kernel. Im not sure if touchwiz and non-touchwiz need different kernels like htc sense.
I dont know where cwm is installed but its separate from the os.
That's a good start, but id love to hear more about the inner workings of everything. I don't want to know if X is compatible with Y. I just want to know how to work together and why A isnt overwriting B.
Wrong section buddy, go to the Q&A
i going to oversimplify this a bit to focus on the relevant portions of ROM flashing.
System partition - this is where the android operating system is installed. It contains the all of the files and apks for android to run. System apks are located here - stuff like the browser, gmail, contacts, calendar, etc. Just the apps are stored here, not their settings.
Boot partition - this is the kernel
Data partition - this is where all of your data is stored. Data includes all settings (including os settings like wifi passwords, brightness level, etc.), as well as any apps you have downloaded as well as their settings and data (example, the angry birds apk is here as well the angry birds data that contains your game progress.) Also the setting and data for the system apks mentioned above (like Gmail and the browser) are stored here.
Sdcard - on android phones this is a separate partition, but on tablets it is a pseudo partition - really just a folder on the data partition but treated like a separate partition most of the time.
When you flash a ROM without wiping anything you are just overwriting the system and boot partitions, that's why all of your data stays in tact.
Cool thanks, can someone describe how does the different options in CWM affect those partitions?
What is wiped when you do a factory reset? cache? and davlik?
I would also be interested in knbowing where does CWM resides.
Thanks
mickey78 said:
Cool thanks, can someone describe how does the different options in CWM affect those partitions?
What is wiped when you do a factory reset? cache? and davlik?
I would also be interested in knbowing where does CWM resides.
Thanks
Click to expand...
Click to collapse
A factory reset in cwm wipes data and cache. Davlik cache is wiped separately through the advanced menu. You can also wipe system, data, cache, and sdcard in the mounts section of cwm.
Cwm is a replacement of the stock recovery partition that shipped on your tablet or phone.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Hi mates,
When we are flashing a Custom Rom from the CWM, we are normally instructed by the Devs only to do few steps on CWM like “Wipe Data/Factory Data Reset, Wipe Cache etc.. which we simply follow, but most of the people don’t know, including me, what these options and many other options of CWM are really standing for.
When I googled, I could not find a thread which explains about these options in a single thread, so I would like to share with my friends about what I found the Common Options of the CWM here...
Obviously these are commonly applicable for all the devices which are having CWM, but I am always concern about my favorite Galaxy S II.
People who are completely new to Recovery and these options, I suggest them to read this thread first and give a thanks to it's author.
What Is Recovery & Download Mode?
The oder and segregation of the below items in the CWM menu may vary or some of them may be removed in different custom recoveries designed by respective Developer.
CLOCKWORKMODE BASED RECOVERY MENU
1) Reboot Menu :
reboot system now
This one is self-explanatory.
2) Install Menu :
choose zip from (internal/ external) sdcard /
Lets you install any zip file (with any name) from any location on your SD card. The file can be for a ROM, a kernel, an application, a theme or any mod as long as it is in recovery-flashable zip format.
apply /sdcard/update.zip
This one is essentially the same as the ‘apply update from sdcard’ option of the main menu. widely used option for installing a ROM that you have downloaded and copied to your SD card. Entering this option will bring up a screen that will allow you to browse your SD card for the zip file.
apply update from sdcard
This can be used for installation of any official or unofficial update, ROM, kernel, theme etc. that is in a zip format installable from recovery, as long as the file is named update.zip and it has been placed on the root of your SD card (i.e. not in any sub-folder). Selecting this option will bring up a rather annoying confirmation prompt but this has saved us on multiple occasions from a lot of trouble we would have been into due to accidental key presses.
toggle signature verification
Turns the signature verification on and off. When signature verification is on, you will not be able to install any custom ROMs that haven’t been signed by the developers (most custom ROMs aren’t signed). Switching it off skips the signature verification check and proceeds with the installation.
toggle script asserts
Seldom-used option for a vast majority of users. It simply turns script asserts on or off. If you don’t know about these (I don’t), it’s best not to change this option.
3) Wipe Menu
wipe data/factory reset
This option wipes all user data on the device as well as cache. Doing this will leave your phone in the state it was in when you bought it or when any custom ROM was first installed. It will also wipe any sd-ext partition that you might have setup. (see more about sd-ext below under partition)
wipe cache partition
This is a good practice to do this before flashing any ROM. The /cache partition just stores temporary files that are not critical to device operation and can be re-generated easily, this Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery.
Wipe Dalvik Cache
Allows you to wipe the cache for the Dalvik virtual machine. The dalvik cache wipe is quite similar to cache wipe but it stores the post ran java applications. Since Android is JAVA based, it uses the same java virtual machine for compiling. The dalvik cache just stores post-compiled applications in order to speed up the system. Wiping this just forces the system to re-cache those application. It causes no problems but a slight hint of lag on first boot. This is required before most ROM installations and at other occasions too, for fixing some problems.
Wipe Battery Stats
Wipes the saved battery usage statistics and effectively recalibrates the battery. Useful in various scenarios when Android isn’t showing correct battery levels.
4) Nandroid menu
backup and restore Undoubtedly one of the most important features provided by a custom recovery, the backup and restore feature – also known as Nandroid backup – allows you to take a snapshot of your phone’s entire internal memory including all partitions, and save it on the SD card.
Backup
Takes a Nandroid backup, as explained above.
Restore
Lets you restore a previously taken backup. Entering this option presents you with a list of existing backups from the SD card that you can choose from for restoration.
Advanced Restore (new options are available separately to restore from external or internal SDcard in the latest CWM)
This option is similar to the Restore option but once a backup has been selected to be restored, this option allows you to choose what parts of it to restore. You can choose to restore the boot, system, data, cache and sd-ext partitions.
5) Storage menu
mounts and storage
Allows you to perform maintenance tasks on all the internal and external partitions of your android device
mount/unmount /system, /data, /cache, /sdcard, /emmc.
These options let you toggle between mounting or unmounting these respective partitions. Most users don’t need to change these options.
format system, data, cache, sdcard or sd-ext
These let you directly format any of these partitions. Take extreme care with this option as formatting any of these partitions will result in losing all data on them, especially the boot and system partitions. Formatting the system partition will remove your ROM and leave your phone without an operating system while wiping the boot partition may brick your phone unless you restore or flash another one before rebooting your device. See below more explanation about these partitions.
mount USB storage
Lets you enable USB mass storage mode for your SD card right from recovery so that you can connect it to your computer via USB and transfer any files to/from it without having to leave recovery.
6) Advanced
This section contains a few options most users will not require, Here are the options from this section:
Report Error
In case of errors, this feature can be used to save a log of recent ClockworkMod recovery operations on the SD card that you can later report from Android using ROM Manager.
Key Test
Lets you press any of the hardware keys to see if they are properly functioning, and to see their key codes.
Partition SD Card
This option gives you a no-frills way to partition your SD card properly for use with ROMs that support data2ext (a very handy hack for low internal memory devices that enables an /sd-ext partition on the SD card to be used as the internal user data storage i.e. as the /data partition). Once this option is selected, you will be given options to choose the sizes for the /sd-ext partition as well as an optional /swap partition on the SD card, and will then automatically format it for you, leaving the remaining space for normal SD card usage. This option will wipe all data from your SD card so use it with caution!
Fix Permissions
Fixes the file permissions for the internal memory partitions back to default. This is very useful as a fix for several errors and Force-Closes that start appearing after you or an application you installed and provided root access end up messing up the permissions of important files.
PARTITIONS :
The Android uses several partitions to organize files and folders on the device. Each of these partitions has a distinct role in the functionality of the device, but not many Android users know the significance of each partition and its contents. In this guide, we will take you on a tour of Android partitions, what they contain and what can be the possible consequences of modifying their content.
Let’s start with a list of standard internal memory partitions on Android phones and tablets. These are:
• /boot
• /system
• /recovery
• /data
• /cache
• /misc
In addition, there are the SD card partitions.
• /sdcard
• /sd-ext
Note that only /sdcard is found in all Android devices and the rest are present only in select devices. Let’s now take a look at the purpose and contents of each of these partitions.
/boot
This is the partition that enables the phone to boot, as the name suggests. It includes the bootloader and the kernel. Without this partition, the device will simply not be able to boot. Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
/system
This partition basically contains the entire operating system, other than the kernel and the bootloader. This includes the Android user interface as well as all the system applications that come pre-installed on the device. Wiping this partition will remove Android from the device without rendering it unbootable, and you will still be able to put the phone into recovery or bootloader mode to install a new ROM.
/recovery
The recovery partition can be considered as an alternative boot partition that lets you boot the device into a recovery console for performing advanced recovery and maintenance operations on it. We have already learnt about this partition and its contents above.
/data
Also called userdata, the data partition contains the user’s data – this is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially performs a factory reset on your device, restoring it to the way it was when you first booted it, or the way it was after the last official or custom ROM installation. When you perform a wipe data/factory reset from recovery, it is this partition that you are wiping.
/cache
This is the partition where Android stores frequently accessed data and app components. Wiping the cache doesn’t effect your personal data but simply gets rid of the existing data there, which gets automatically rebuilt as you continue using the device.
/misc
This partition contains miscellaneous system settings in form of on/off switches. These settings may include CID (Carrier or Region ID), USB configuration and certain hardware settings etc. This is an important partition and if it is corrupt or missing, several of the device’s features will will not function normally.
/sdcard
This is not a partition on the internal memory of the device but rather the SD card. In terms of usage, this is your storage space to use as you see fit, to store your media, documents, ROMs etc. on it. Wiping it is perfectly safe as long as you backup all the data you require from it, to your computer first. Though several user-installed apps save their data and settings on the SD card and wiping this partition will make you lose all that data.
On devices with both an internal and an external SD card – devices like the Samsung Galaxy SII – the /sdcard partition is always used to refer to the internal SD card. For the external SD card – if present – an alternative partition is used, which differs from device to device. In case of Samsung Galaxy S series devices, it is /sdcard/External_sd while in many other devices, it is /sdcard2. Unlike /sdcard, no system or app data whatsoever is stored automatically on this external SD card and everything present on it has been added there by the user. You can safely wipe it after backing up any data from it that you need to save.
/sd-ext
This is not a standard Android partition, but has become popular in the custom ROM scene. It is basically an additional partition on your SD card that acts as the /data partition when used with certain ROMs that have special features called APP2SD+ or data2ext enabled. It is especially useful on devices with little internal memory allotted to the /data partition. Thus, users who want to install more programs than the internal memory allows can make this partition and use it with a custom ROM that supports this feature, to get additional storage for installing their apps. Wiping this partition is essentially the same as wiping the /data partition – you lose your contacts, SMS, market apps and settings.
Now whenever we install a ROM or mod that requires we to wipe certain partitions before the installation, we should be in a better position to know what we are losing and what not and thus, we’ll know what to backup and what not.
Best Regards
http://forum.xda-developers.com/showthread.php?t=1134290
Yep. Been done before a long time ago. Tho I do admire your initiative in putting the info together
Stifler69 said:
http://forum.xda-developers.com/showthread.php?t=1134290
Click to expand...
Click to collapse
No Doubt this one should be on the top of this thread,
What a simple and awesome explanation about the Recovery & Download mode, many thanks to pulser_g2
I know, majority of users only need the simple steps and shortcuts, they don’t care what’s happening internally and theoretically, but some are really curious to know…
Many thanks mate....
zaheedahmed said:
No Doubt this one should be on the top of this thread,
What a simple and awesome explanation about the Recovery & Download mode, many thanks to pulser_g2
I know, majority of users only need the simple steps and shortcuts, they don’t care what’s happening internally and theoretically, but some are really curious to know…
Many thanks mate....
Click to expand...
Click to collapse
Nah mate you do what you have to do. It is a good thread and provides good information. Nice work. Just wanted to show you Pulsers thread as well though because he has done something similar to yours long time ago..But anyway good work and if you need any help let me know
Thanks, will save later text in PDF and keep it on PC just to have one more tutorial about things
Awesome write up!! Brilliant!
As you are so knowledgeable about CWM, perhaps I can ask you a question?
When I do a backup, it says that no external SD card was found, so it skipped the external?
When I check under mounts, the only option for the external SD card is to UNmount.... This would suggest that the card is mounted, correct?
So how would I go about backing up the external card too?
Thanks!
Sent from my SGH-I727R using xda premium
Question, if i do nandroid backhp through CWM, i suppose it saves files that i dl such as apps/games, or i need to download later again 600mb+?
Sent by powaaaaah of GT-I9100 Taparatatatalk!
shaggyskunk said:
Awesome write up!! Brilliant!
As you are so knowledgeable about CWM, perhaps I can ask you a question?
When I do a backup, it says that no external SD card was found, so it skipped the external?
When I check under mounts, the only option for the external SD card is to UNmount.... This would suggest that the card is mounted, correct?
So how would I go about backing up the external card too?
Thanks!
Sent from my SGH-I727R using xda premium
Click to expand...
Click to collapse
Thank you for your appreciation,
I would like to express once again as I mentioned in the starting of the thread that this is only a humble effort of the undersigne that I searched for such information and combined at one place here....
As far as I know about your problem of SD card storage, this is a compatibility issiue which varries on one custom recovery to another, also one SD card to another. such issues are fixed by developers in their latest versions of recoveries.
I experienced once the same issue which was resolved when I changed my SD card.
And my current (touch) recovery of Redpill v1.3 allows me to Backup and restore from external SD card with all available options flowlessly.
Thanks
X-Plosiv said:
Question, if i do nandroid backhp through CWM, i suppose it saves files that i dl such as apps/games, or i need to download later again 600mb+?
Sent by powaaaaah of GT-I9100 Taparatatatalk!
Click to expand...
Click to collapse
Between CWM & Titanium, you should not have to download anything.
Sent From my Two Tin Cans & String Device on The Wookie Network
X-Plosiv said:
Question, if i do nandroid backhp through CWM, i suppose it saves files that i dl such as apps/games, or i need to download later again 600mb+?
Sent by powaaaaah of GT-I9100 Taparatatatalk!
Click to expand...
Click to collapse
Of course it backs up all your installed apps and system data along with the ROM, but it do not back up the additional data which is downloaded and stored in User's partition of your SD card by the applications, such data will remain on your SD card untill you format it, available to support your apps when you return to the previous ROM.
awsome eplanation
as above posts say awsome explinationculdnt b clearer now then all
zaheedahmed said:
Of course it backs up all your installed apps and system data along with the ROM, but it do not back up the additional data which is downloaded and stored in User's partition of your SD card by the applications, such data will remain on your SD card untill you format it, available to support your apps when you return to the previous ROM.
Click to expand...
Click to collapse
Yes, but when I do format/wipe all, I guess then it deletes all that is on SD card as well, such as game files and music? If so, I'd rather just copy paste it on my PC, then after doing all wipes and formats, just copy back from PC
Zaheed, you are far too humble! Your post was brilliant, informative & timely.
Sent From my Two Tin Cans & String Device on The Wookie Network
X-Plosiv said:
Yes, but when I do format/wipe all, I guess then it deletes all that is on SD card as well, such as game files and music? If so, I'd rather just copy paste it on my PC, then after doing all wipes and formats, just copy back from PC
Click to expand...
Click to collapse
When you do normal wipes (data/ factory reset, cache, dalvik) before installing/restoring ROM, it won't touch any data which is saved in your SD Card normally, but it is more safer if you back such application data to you PC which normally find in a folder "Android/ Data /xxx" in the root of SDcard
Thanks for info.
I have read a lot on this but am still nor clear whether a wipe data/factory reset includes a full cache wipe. Most rom install instructions tell you to do both, but it seems a wipe cache is redundant if you factory reset.
SimboXXX said:
Thanks for info.
I have read a lot on this but am still nor clear whether a wipe data/factory reset includes a full cache wipe. Most rom install instructions tell you to do both, but it seems a wipe cache is redundant if you factory reset.
Click to expand...
Click to collapse
Yes, you are right, I also understand the same, but the option for merely wiping cache is kept for using in some odd situations, like when we fingered to the ROM and got some error, then we got a no-wipe version of the existing ROM to reflash, such case we need only to wipe cache…. I have got an error recently on CWM when I reflashed my no-wipe Checkrom v6 without wiping anything, then I wiped only cache, problem solved…..
what ever may be the theory, do as the developers directed for their ROM…..NO RISK
shaggyskunk said:
Zaheed, you are far too humble! Your post was brilliant, informative & timely.
Sent From my Two Tin Cans & String Device on The Wookie Network
Click to expand...
Click to collapse
thanks mate...
Thanks for the thread, you can never know too much. On second thoughts, there's probably no danger of that.
What would be really good if you have the knowledge, is a detailed guide on CWM Edify scripting. I'm sure many people would find that useful, especially me. There doesn't seem to be a lot of good guides or information on the language, at least I can't find them yet. If you have any good links I'd definitely appreciate it as well.
Here's another bit of information, that answered a question I had....
In case anyone else has this question...
Here is the answer from:
http://android.stackexchange.com/qu...ter-no-sd-ext-found-skipping-backup-of-sd-ext
" This means you do not have an ext3/4 partition on your sdcard. This really ins't a big deal, this is like a legacy part of the nandroid backup process. CM doesn't "officially" support the sd-ext partition any more anyhow."
Hope it helps someone else... In the end, the answer is pretty straight forward.
Sent From my Two Tin Cans & String Device on The Wookie Network
Sent from Down The Rabbit Hole, using Tapatalk 2
Why? It's been stuck at 60.5mb used and 1.2GB free according to Diskinfo forever now. Ever since I restored Madvane's unrooted B180 backup & then flashed root with Magisk.
Why does it bother me? Because I have no idea what I'm talking about and I feel like maybe Cache is storing in the Data Partition where I install my apps...? Is it?
Also with 1.2GB free in the Cache parition & 1.2GB free in the System Partition, can I just partition those and make the Data partition bigger for more available Internal Storage for apps and stuff? I mean I have external storage as default location but so many files still get installed on internal and I'd like to expand that if I could alter these partitions.
Anybody done that before or can answer my questions? Thanks! Images attached
Anyone ?
I have not read of anyone here repartitioning internal storage. I don't think it's as simple as repartitioning a PC hard drive with a GUI tool.
Do you have any tools in mind to do this repartitioning? I think it would be a highly risky operation, so be sure to make full backups and note all the original settings of existing partitions before repartitioning.
You can Google threads on people repartitioning internal storage for other phones, but note the ones who ran into problems and bricked their phones.
I wouldn't mess with the partition sizes, personally.. in theory it works, but it can trigger some arcane safeguards added by oems.
Try wiping the cache partition in twrp..? Could have gotten bugged, which would throw an error and require reformatting
Is there any indication of a problem with the cache partition?
It's biggest usage would be to download an OTA file, so unless that's happening, I would expect cache partition to remain remain mostly empty as OP reported. Probably what's in there is TWRP or stock recovery logs - you can confirm with a root file manager.
Wiping the cache partition as suggested won't harm anything and it would be interesting to know what it's reported usage is after wipe and reboot.
divineBliss said:
Is there any indication of a problem with the cache partition?
It's biggest usage would be to download an OTA file, so unless that's happening, I would expect cache partition to remain remain mostly empty as OP reported. Probably what's in there is TWRP or stock recovery logs - you can confirm with a root file manager.
Wiping the cache partition as suggested won't harm anything and it would be interesting to know what it's reported usage is after wipe and reboot.
Click to expand...
Click to collapse
I guess that was my question too. If there was any idication of an issue here. Seeing that free space I'd like to have it though.
On another note. There's no indication of anything being wrong with my Data partition but I formatted it to ext4 back when I bricked my phone in a hope it would fix something. But it seems fine. IDK what they default partition type was.
My data partition is ext4, which I believe is the stock default type.
divineBliss said:
My data partition is ext4, which I believe is the stock default type.
Click to expand...
Click to collapse
Thanks man you've been allot of help. Have you tried L-Speed? I'm thinking about trying it. I do have Kernel Auditiur installed. Don't use it.
Nothing is broke but thought about trying L-Speed.
Never heard of it. If you try it, let us know what you think.
WifiGhost said:
Thanks man you've been allot of help. Have you tried L-Speed? I'm thinking about trying it. I do have Kernel Auditiur installed. Don't use it.
Nothing is broke but thought about trying L-Speed.
Click to expand...
Click to collapse
divineBliss said:
Never heard of it. If you try it, let us know what you think.
Click to expand...
Click to collapse
I just tried it seems like a nice and easy way to tweak performance or battery.
I prefer kernel adiuator myself.. L Speed has too many generic settings which do next to nothing for actual performance, reminiscent of the many garbage tweak programs that have been out there for years. K.A. allowed for better control of the cpu governor settings, which allowed me to negate some of the impact of emui's 'battery optimization'. A little bit of entropy tweaking on top of that, and I no longer experience nearly the amount of choppiness