Develop Bugs

[Q] Wiping Cache from Recovery? *PLEASE HELP*

Upon booting up via Vol. Down + Power, there are four options (fastboot, recovery, wipe cache, and simunlock). What happens when you wipe cache?
I just installed a new ROM (well updated), couldnt get it to boot as I was stuck on the custom boot screen, but after wipe cache it loads up?
Does this effect the functionality at all? Please help. Thanks

I believe this is a factory wipe, but is a dumbed down version, that does not wipe /sd-ext partitions etc. Just removes /data programs and user info, but won't touch any /system applications.
It is used to reset the phone without actually booting up the OS

Any particular reason why my ROM wouldnt boot up normally but requires a cache wipe in order to boot?

trenwei said:
Any particular reason why my ROM wouldnt boot up normally but requires a cache wipe in order to boot?
Click to expand...
Click to collapse
Soms roms will require you to wipe dalvik cache in order for the new rom to boot (conflicts can be caused), and wiping this cache would do it, however you can just wipe dalvik cache from recovery not this hboot menu.
For future reference when changing roms, especially when changing to someone elses rom (and especially especially when its a different base) you should be doing a full wipe
A full wipe is:
-Data (factory reset)
-Dalvik Cache
-Ext partition (although sometimes you can get away with skipping this one)
You should be able to wipe those three from both Amon-RA and Clockwork Mod recoveries.

NOTE: I am sleep deprived, so this will proberly not make alot of sense
I'm not that technical with the Android system (have worked with linux abit though)
Deleting the cache would remove any saved data from the system. These saved items may contain anything from images to which default program is loaded, to which widgets are loaded on the homscreen.
This is why after a new install the phone takes a little longer booting up, creating all the new files. If you need me to go into cache, use Google.
Another theory would be:
After an upgrade, some files and apps think that the system has changed owners, so their permissions change from read/write to read/only etc.
With this, some system files will become inaccessible, will be unable to be edited and so forth.
A way around this would be to "fix" the permissions of the data, changing the owner of the files allowing read/write permissions
Rom Manager has a nice little feature that allows you to fix permissions, and has come very helpful for me, with my switching to and from OD/Pinky, and restoring LauncherPro, which likes to FC at every restore -.-.

[Q] best way to keep up to date with nightlies?

I'm currently running Synergy, and have been flashing nightlies every so often to keep up wit hthe changes and small errors that I encounter, hoping there's a fix in them, However reflashing a nightly every few days can be a pain as I keep having to reset all of my phone settings (ringtone, notifications, display, accounts, sms, etc...)
What is everyone's opinion of the best way to reliably backup your phone settings to easily restore them to a new rom after a flash?
I use Titanium Backup, but honestly I'm not sure what all the system settings are saved as, or even if that's a good idea as the way settings are setup might have changed from the las tbackup, and don't want to screw things up.
Ideas?

All you have to do is reboot into recovery, wipe cache and dalvik, and then create a nandroid backup of only the data. If you have an ext3 partition and your third party apps are stored there, then also select to backup the sd-ext and your android.secure (if you have paid apps). Now all you have to do after a clean install of Synergy or its nightly builds is to boot to your homescreen, bypass the sign-in stuff, and then remove all of the default homescreen widgets. After that, reboot into recovery, wipe cache & dalvik and then restore the aforementioned backup. When you reboot, all of your settings, data, apps and homescreens will be as they were on your previous installs.
posting & replying via my EVO 4G

dougjamal said:
All you have to do is reboot into recovery, wipe cache and dalvik, and then create a nandroid backup of only the data. If you have an ext3 partition and your third party apps are stored there, then also select to backup the sd-ext and your android.secure (if you have paid apps). Now all you have to do after a clean install of Synergy or its nightly builds is to boot to your homescreen, bypass the sign-in stuff, and then remove all of the default homescreen widgets. After that, reboot into recovery, wipe cache & dalvik and then restore the aforementioned backup. When you reboot, all of your settings, data, apps and homescreens will be as they were on your previous installs.
posting & replying via my EVO 4G
Click to expand...
Click to collapse
thanks for the reply. just to be sure I understand you completely, using my current rom, would this be the proper order?
reboot into recovery (I use Amon Ra)
wipe CACHE, & DALVIK-CACHE
backup the following items: [ ]boot, [ ]system, [x]data, [ ]cache, [ ]recovery, [ ]wimax, [ ]sd-ext, [x].android_secure
wipe ALL userdata/factory reset
flash latest rom
boot to homescreen
remove all widgets/icons
reboot into recovery
restore nandroid backup created above
reboot normally
Also, as a side note, when wiping before flashing rom, I usually wipe ALL, CACHE, & DALVIK-CACHE, which are covered above. With the new Amon Ra, should I be wiping any of these as well before I flash? - DATA, SDCARD:.android_secure, BOOT, SYSTEM, SDCARD, SDEXT, DATA:battery stats, DATA:rotate settings?
Thanks for all the info! I appreciate it!

Include the sd-ext in the backup if you have an ext3 partition with apps on it. Other than that, you got it right. As for what to wipe before flashing, if I'm just flashing nightlies, I sometimes only wipe cache & dalvik, but I'm big on wiping EVERYTHING in amonRA's wipe menu EXCEPT the SD card before I flash a rom.
posting & replying via my EVO 4G

okay. thanks.
this is actually a follow up question, but the sd-ext, is that a special partition that I can setup that will expand the base storage of my EVO onto the SD card so I stop getting complaints about running out of space? And can that be setup through Amon Ra?

Issues with various ROMs

Hey Guys,
So I've been having some issues with various ROMs on my LTE Galaxy Nexus. I first tried flashing to bigxie's build last week and that was yielding various bug reports. I flashed again with the same results (even without loading my backed up apps from Titanium Backup).
So I went back to stock... all was well again.
I just flashed to axi0m's ROM with Apex kernel. It has awesome performance but I keep getting force closes for random apps: Chrome to Phone, Trebuchet, etc.
I feel like at this point, its something I'm doing wrong or something wrong with my phone. I have followed the instructions to the T for each ROM install...
My order or process is as follows:
-Format data
-Erase partition cache
-Erase mount & storage /system (for axi0m)
-Load ROM
-Load GAPPS (applicable to bigxie's ROM)
-Reboot
Anyone have any ideas for me?

Well, I'll start by saying that I have ALWAYS run into issues when trying to use custom kernels. I've resorted to sticking with the kernel that comes with whatever ROM I install. This always seems to provide the most stability for me.
Next time you flash a ROM I recommend following the process that's worked extremely well for me on all my previous phones, including this one...
1. Put the ROM on your SD card
2. Reboot into Recovery
3. Do a Nandroid backup of your current ROM
4. Wipe Data/Factory Reset
5. Wipe Cache Partition
6. Go into Mounts
7. Format /system
8. Flash new ROM
9. Go into Advanced and Wipe Dalvik Cache
10. Fix Permissions (Also in Advanced)
11. Reboot phone
12. Sign into your Google account (1st step in the setup screen)
13. Let the phone sit for 10 full minutes without touching it
14. Reboot phone again

You don't need to format data, erase partition.
All you really need to do is:
1. Download the ROM, Kernel (if desired), gapps (if required)
2. Verify its MD5 hash [optional... but I recommend doing it, google HashTab]
3. Put the files onto your phone's internal storage.
4. Reboot into recovery mode.
5. If its a new ROM, wipe data(factory settings),cache,dalvik. If its the same ROM but upgrading, then just skip this step.
6. Flash ROM, Kernel (if you downloaded one.. verify its compatible, meaning don't flash franco kernel on a 4.0.2 ROM), gapps
7. Reboot.
Having FC problems? boot into Clockwork and fix permissions.
Afraid something might not go well? do a nandroid, but I'm pretty experienced at flashing so I've avoided at doing nandroid but since you're still not familiar with the steps. Nandroid backup can be very useful.

I definitely agree with checking the MD5 sum. That should be step 1 after downloading the ROM. I know you don't 'have' to format /system but it's just an extra precaution I've always taken and I have never had a problem with it.

sn0warmy said:
I definitely agree with checking the MD5 sum. That should be step 1 after downloading the ROM. I know you don't 'have' to format /system but it's just an extra precaution I've always taken and I have never had a problem with it.
Click to expand...
Click to collapse
Oh, I didn't know you mentioned it too. I only looked at the OP. I guess it couldn't hurt, why not?
Another thing to mention, when you flash a new kernel.. it's best to wipe dalvik cache (before or after.. preferably before) then flash the kernel.

zephiK said:
Oh, I didn't know you mentioned it too. I only looked at the OP. I guess it couldn't hurt, why not?
Another thing to mention, when you flash a new kernel.. it's best to wipe dalvik cache (before or after.. preferably before) then flash the kernel.
Click to expand...
Click to collapse
I didn't mention checking the MD5 sum, I was just agreeing that it is an extremely important step.

Ok, so I seemed to have resolved a lot of issues by wiping the davlik cache. I was flashing to the stock launcher w/ 4x5 grid (without search) and it required a wipe of the davlik cache. This seemed to clear up the force closes. So far, i have been loving my axi0m ROM.
Now if Samsung/Google can push a new update to fix the radio issues w/ data :|

[Q] *wipe*

Hi all!!
I know it is a very very, VERY dumb question because seems that everyone knows the answer and mostly because i am in my 3rd ROM and most of then suggested/requsted a fullwipe. So I searched the forums and wiki but i don't have a clue about what is a full wipe or super wipe or *wipe*
Sorry for that quanstion and thanks if you could answer.

diassuncao said:
Hi all!!
I know it is a very very, VERY dumb question because seems that everyone knows the answer and mostly because i am in my 3rd ROM and most of then suggested/requsted a fullwipe. So I searched the forums and wiki but i don't have a clue about what is a full wipe or super wipe or *wipe*
Sorry for that quanstion and thanks if you could answer.
Click to expand...
Click to collapse
Full wipe: Format data, cache, dalvik cache. It does not touch your SDcard data.
Edit: Usually people also Wipe Battery Stats. I found it unnecessary so I forgot to include. It may also involve formatting your SDcard if you have funky stuffs in there. (apps2SD for example)
If you use ClockwordMod, for example, you would have to choose Format data/factory, then Advanced => Wipe Dalvik Cache and Wipe Battery Stats
Super wipe:
Fallen Spartan said:
Basically it does the following:
1) Call erase_image on CACHE, SYSTEM, USERDATA, and BOOT partitions
2) Mount /sd-ext (if it exists) and delete all files from it
3) Delete all files in the /sdcard/.android_secure directory which is where all the froyo apps2sd files live
4) Run e2fsck (file system repair) on the your ext partition
5) Log all output to the /tmp/wipe.log file (if you care)
You will need to power off and reboot back into recovery after running this to install a new rom....as you won't have one on device
If you forget and try to boot normally you will get stuck at splash screen, then you will have to pull battery to power off.
Click to expand...
Click to collapse
To super wipe you often need a zip file and flash it in recovery. Example:
http://forum.cyanogenmod.com/topic/19959-superwipe-for-g2-w-gps-fix/

an added note
fastboot wipe is still the cleanest wipe
<fastboot -w>
i tend to over kill so do fastboot wipe first
then boot into recovery and do a factory reset and wipe cache, dalvik cache again
then do a superwipe.
sounds like over kill? well it keeps me from having issues when changing roms - i change often so these 3minutes spent save me lots of time later

demkantor said:
an added note
fastboot wipe is still the cleanest wipe
<fastboot -w>
i tend to over kill so do fastboot wipe first
then boot into recovery and do a factory reset and wipe cache, dalvik cache again
then do a superwipe.
sounds like over kill? well it keeps me from having issues when changing roms - i change often so these 3minutes spent save me lots of time later
Click to expand...
Click to collapse
blimey...
out of interest should i be wiping anything when i restore from a backup?

Yes
Especially if there was data coruption
Sent from my HTC Vision using xda premium

Thanks
demkantor said:
an added note
fastboot wipe is still the cleanest wipe
<fastboot -w>
i tend to over kill so do fastboot wipe first
then boot into recovery and do a factory reset and wipe cache, dalvik cache again
then do a superwipe.
sounds like over kill? well it keeps me from having issues when changing roms - i change often so these 3minutes spent save me lots of time later
Click to expand...
Click to collapse
I Agree!
That's why i want to know about wipes.
Thanks a lot!

Best way to wipe? Lol

What do you do to make your roms run great everytime. Wipe data 1x, 2x, 3x. Etc. I get force closes and wondering if I didn't wipe right. I also got boot manager with miui stable as rom 1. It's been acting wierd lately. Hoping Simone can give me tips on flashing through clockwork and installing through boot manager for best results.
Sent from my ADR6300 using xda app-developers app

I don't use boot manager, but for a clean install of a ROM, format boot and system, and wipe data/Factory Reset, all just once.
cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache

Boot to cwm recovery.
Go to mounts and storrage menu.
Format every option available except emmc and sdcard.
Flash rom of your choosing.

PonsAsinorem said:
I don't use boot manager, but for a clean install of a ROM, format boot and system, and wipe data/Factory Reset, all just once.
cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache
Click to expand...
Click to collapse
Exactly what this guy said. Wipe data/factory reset takes care of /data, /datadata, and /cache all in one stroke. All that's left is /boot and /system

Also, with MIUI you may need to clear out your app cache regularly. Use this App Cache Cleaner, it's super simple. That should help your fc problems.

These are the steps I follow when flashing ROMs. Seems to work well for me:
Reboot your phone into Bootloader Mode. (You can do that by pressing and holding the Volume Down and Power buttons until HBOOT boots.)
Using the Volume keys, highlight Recovery and select it by tapping the Power button. Your phone will now boot to Recovery Mode.
Create a NANDroid backup of your current ROM. Go to Backup and Restoreand select Backupon the next screen. Wait until recovery finishes backing up your ROM.
Once done, go back to the main menu and perform a full wipe:
[*] ----> Select Wipe data/factory resetand confirm the action on the next screen.
[*] ----> Select Wipe cache partition and confirm the action on the next screen.
[*] ----> Go back to the main menu and select Advanced.From there, select Wipe Dalvik Cache and confirm the action on the next screen.
Select Install ZIP from SD card.
Select Choose ZIP from SD cardand locate the ROM.zip file. Confirm the action on the next screen to flash the ROM to your mobile phone.
Go back to the main menu and flash GoogleApps.zip in the same manner as in steps 6 and 7.
Go back to the main menu and select Reboot system now. This will reboot your phone with the new ROM.

What I normally do is boot into cwm and just do the factory reset/data wipe and that makes everything run nice and smooth whenever i flash a new rom.

ardax said:
Exactly what this guy said. Wipe data/factory reset takes care of /data, /datadata, and /cache all in one stroke. All that's left is /boot and /system
Click to expand...
Click to collapse
Yes. I find that if you don't also do /boot and /system some things linger that can cause problems. I did not do this recently and it still remembered Wifi locations, brought up an old wallpaper and sounds choices via music and ringtones were severely limited. Don't be afraid, do what the man says!!

CyanoLou said:
Yes. I find that if you don't also do /boot and /system some things linger that can cause problems. I did not do this recently and it still remembered Wifi locations, brought up an old wallpaper and sounds choices via music and ringtones were severely limited. Don't be afraid, do what the man says!!
Click to expand...
Click to collapse
No need to format boot. Some devices don't even support that option. Plus flashing a new ROM always flashes a new boot.img in its place which overwrites the old one. System is OK but then you have to flash gapps with updates where before its optional. Wiping system isn't a bad idea on sense ROMs as it doesn't always get wiped by the script. On aosp it does and on cm it wipes system after backing up gapps.
Also WiFi and wallpaper choices are stored in datadata not system. If wallpapers come back after a factory reset that is due to Google restore. Sound choices are stored in a database that needs to rebuild after a wipe.
Sent from my Galaxy Nexus using Tapatalk 2

And in swoops tiny wielding the clue-by-four.
Normally I'll only wipe /system if I'm switching ROMs. Updating dailies doesn't require it.