Noob questions. Every time I flash a new rom I become narotic, and I first disable any lagfix, then go to cwm, and factory reset, cache, dalvik, and batt stats all wiped. I'm assuming I don't need to do this if it's a full wipe rom? Can I even skip the lagfix part or is that always necessary?
Also if I'm upgrading a version of a rom, ex, apex 6.4 to 6.5 or any other situation same as this, can I just flash it without doing any prep before hand?
Sent from my GT-I9000 using XDA App
if it's a full wipe ROM than yes, the ROM does all the wiping for you. And if the OP states for you to disable lagfix before flashing than i do so.. also if your just doing an update you can usually just flash over one another. But its always good to check with the ROM dev and see if he suggests any special wipes or whatnot.
Cdub3 said:
Noob questions. Every time I flash a new rom I become narotic, and I first disable any lagfix, then go to cwm, and factory reset, cache, dalvik, and batt stats all wiped. I'm assuming I don't need to do this if it's a full wipe rom? Can I even skip the lagfix part or is that always necessary?
Also if I'm upgrading a version of a rom, ex, apex 6.4 to 6.5 or any other situation same as this, can I just flash it without doing any prep before hand?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You can still do whatever your used to and are comfortable with. BUT this is what I do before flashing any rom.
I go to market and make sure all apps are updated.
Next I go to titanium backup and backup all user apps and system apps with data (I NEVER RESTORE THE SYSTEM APPS OR DATA THOUGH)
Next I boot into recovery and perform a backup (which saves almost Evey aspect of my rom I am on before flashing
I boot back up and then reboot into recovery again.
Then I install whatever rom I am flashing at the time.
I DO NOT WIPE ANYTHING OTHER THAN CACHE WHILE IN RECOVERY AND BEFORE FLASHING THE ROM.
I have NOT had more than 1-2 issues flashing anything since I started using froyo, so that includes any froyo rom, the gingerbread rom that first was made, then Continuum and on my second cappy the same except I also have flashed CM7 on it.
The one or two times I had issues ALL I ever did was boot into recovery and run restore from the previous rom I was on. Then reflash the rom I was trying to get on to. I really have have had NO ISSUES NOT wiping anything other than cache.
I look at it this way, if it works the first time I flash a rom I am golden and do not need to reset up everything. If I have a issue then I CAN start from scratch with a factory reset and wipe cache and dalvich cache IF NEED BE. At least then I am ON the rom I was trying g to go on in the first place.
Then after all seems good I will restore my user apps and some user apps with data with Titanium Backup. So MOST of the time I have changed roms and all is working with no issues in 10 to 15 minutes.
Again this is HOW AND WHY I do it that way. A NANDROID BACKUP and TITANIUM BACKUP are your BEST FRIENDS in these cases.
Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
Thanks for the replies. Very helpful
Sent from my GT-I9000 using XDA App
Cdub3 said:
Thanks for the replies. Very helpful
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
6.5 is a wipe version which would take care of wiping caches. You dont need to disable lagfix. But as someone said always keep a nandroid backup
Also you may want to post these queries in ROM thread for quicker response
I always disable lagfixes just for good measure. Most roms do a full wipe so there's no need for any of the other stuff.
Related
it seems like every rom I install these days restart randomly.
Whats causing this ?
Bad flash probably, with all sure respect sound like user error, try completely clean fresh install
Sent from my GT-I9000 using XDA Premium App
How can everyone be flashing wrong? Most people post that they have the reboot problem. Maybe its an overclocking thing or lock screen issue. Its a bad problem with most roms it looks like.
Sent from my GT-I9000
Well people without the problem aren't going to post are they? And, again, with due respect, a lot of people simply don't know what they are doing or don't read install instructions properly
Sent from my GT-I9000 using XDA Premium App
I don't have this problem on cm7. Try a fresh install of JVR or something, and that includes a repartition and factory reset (which are basically the same thing ).
Sent from my GT-I9000 using XDA Premium App
Sidneymac said:
it seems like every rom I install these days restart randomly.
Whats causing this ?
Click to expand...
Click to collapse
The user
Okay. I guess.
Sent from my GT-I9000
No problems on darky rom 10.2 on my i9000m
Sent from my GT-I9000 using XDA Premium App
Sidneymac said:
Okay. I guess.
Sent from my GT-I9000
Click to expand...
Click to collapse
I know not all users do this, but whenever I flash a new ROM, I generally like to wipe data/dbdata/cache and dalvik from the phone. Then flash the ROM, do a full factory reset and wipe the internal SD card as well. I've never experienced any random reboots personally after following this proceedure.
It means I have to backup and restore apps using Titanium Backup, and copy over all my music again, but I like knowing I've got the cleanest possible installation
Ivegottheskill said:
I know not all users do this, but whenever I flash a new ROM, I generally like to wipe data/dbdata/cache and dalvik from the phone. Then flash the ROM, do a full factory reset and wipe the internal SD card as well. I've never experienced any random reboots personally after following this proceedure.
It means I have to backup and restore apps using Titanium Backup, and copy over all my music again, but I like knowing I've got the cleanest possible installation
Click to expand...
Click to collapse
While I respect the cajones your flashing procedure requires, and agree that it will ensure a perfect ROM flash, every time....it still strikes me a little like doing the dishes by lighting the kitchen on fire.
Unless a new ROM specifically calls for a /data wipe aka factory reset I would propose this less extreme method to the OP which should still solve their reboot problems in most cases:
1) Go into Recovery
2) Clear the Dalvik cache
3) Clear or Format the /cache
4) Format the /system directory (this will not wipe your apps or data, it will just clear the system files that are most likely to cause conflicts with the new ROMK, hence reboots)
5) Flash the new ROM
6) Flash new gapps (optional but usually saves hassles down the line)
7) Fix Permissions
8) Reboot
That should fix you up 9 times out of 10. If you are still seeing reboots, then do a factory reset from recovery to clear out all your apps, reflash your current ROM and then reinstall your non-system apps from either the market or Titanium backup one by one (without data if at all possible). Try to stagger the reinstall so you can try and isolate if the reboot problem is due to a specific app (doubtful since normally an app will fc, not reboot the entire system, but it is possible).
Any questions, let me know, and good luck.
rschenck said:
While I respect the cajones your flashing procedure requires, and agree that it will ensure a perfect ROM flash, every time....it still strikes me a little like doing the dishes by lighting the kitchen on fire.
Click to expand...
Click to collapse
I agree, but when I've had problems (or when I'm installing a completely different ROM), I like to use the procedure I mentioned. It gets rid of any old stuff that might be left behind from a mixture of old ROM's, kernels, themes and apps. I thought trying it might help solve the OP's problem
rschenck said:
Unless a new ROM specifically calls for a /data wipe aka factory reset I would propose this less extreme method to the OP which should still solve their reboot problems in most cases:
1) Go into Recovery
2) Clear the Dalvik cache
3) Clear or Format the /cache
4) Format the /system directory (this will not wipe your apps or data, it will just clear the system files that are most likely to cause conflicts with the new ROMK, hence reboots)
5) Flash the new ROM
6) Flash new gapps (optional but usually saves hassles down the line)
7) Fix Permissions
8) Reboot
Click to expand...
Click to collapse
Agreed.
Sent from my GT-I9000 using XDA Premium App
In 14 hours ive experienced one reboot, but the yesterday I had like 10 reboots.
I usually factory reset etc and most roms clean everything before installing anyways.
And to keep my apps etc when I format the /system directory I guess I should pick the no wipe rom package ?
I'm trying to flash a sense ROM to update my PRL. I'm currently using:
Jaybob's TeamHeroC Rom, the .35 kernal
Firerats 1.5.8 Partition mod
The issue I'm running into is once I install a sense ROM (have tried NFX and Liquidsense so far) I get a never ending white HTC screen, have to pull the battery and back up using Nandroid.
The order I've been trying to do things:
Wipe, Clear cache and Dalvik
Flash Remove 1.5.8
Wipe, Clear Cache and Dalvik
Reboot Recovery
Flash Sense ROM
White screen/won't boot
From there I have to battery pull, wipe, re-flash Firerats and do a nandroid restore to get back where I was. I'm pretty sure I'm leaving out a step, so I was wondering if anyone could give me a clue on what I'm leaving out.
Is it safe to assume u didn't save a backup of ur original ROM right after u rooted ur hero?
If u did then go there to do the prl update.
If not then, try "fresh ROM" first, then try liquid sense or nfx...
But you may to factory reset twice, then under CMR recovery go to mounts and storage and format all but SD card stuff. Most recommend to do it twice .... just to make sure.
Now flash the ROM by itself since u don't need to sign in for anything so no need to flash gapps if ROM doesn't already have it.
Are you using any tweaks perhaps, firerat's? If so I've read that there are issues with that if your system is partitioned too small.
Good luck
Good luck!
Sent from my HERO200 using Tapatalk
When going from an AOSP ROM to Sense and vice versa you format boot, cache, system, data and dalvik cache.
vidaljs said:
Are you using any tweaks perhaps, firerat's? If so I've read that there are issues with that if your system is partitioned too small.
Click to expand...
Click to collapse
Yes, using the Supercharged V6, 3G Supercharger, KAK and Firerats.
I flash the fr-remove before flashing the new ROM. Taking care to format everything had the same results, as did flashing my old backup just after I rooted. I haven't tried flashing another ASOP rom or CM7, but so far it seems I can only restore my most recent backup.
oldredhat said:
Yes, using the Supercharged V6, 3G Supercharger, KAK and Firerats.
I flash the fr-remove before flashing the new ROM. Taking care to format everything had the same results, as did flashing my old backup just after I rooted. I haven't tried flashing another ASOP rom or CM7, but so far it seems I can only restore my most recent backup.
Click to expand...
Click to collapse
Firerats is the issue. Your /system partition is currently too small. I've never had good luck with FR-remove. Re-flash your recovery image prior to flashing Sense. I triple format my /boot, /system, /data, /cache, and Dalvik cache using Clockwork receovery as well. Thank goodness I don't have to do that very often!
im just curious and also i want to be able to get an answer to this question. so that noobs like me that have a rooted and s-off device dont get things mixed up.
is truly necesary to do a full wipe ( data, delvik cache, etc.) to flash anything from a simple tweek to something more complex like a custom rom, or kernel?
Yes...it is truly necessary. The only exception being if it's an upgrade for a ROM you're already using. I.e. upgrading WhateverRom 1.4 to 1.5. Even then though a full or partial(cache and dalvik) wipe is usually recommended. You WILL have many problems if you flash a completely different ROM over another one without doing a full wipe.
Edit: proper procedure would be 1. Download the ROM you want 2. Place it onto your external sd card 3. Boot to recovery 4. Full wipe 5. Flash the .zip 6. Reboot 7. Enjoy 8. (optional) Report bugs to the developer in the thread dedicated to the ROM including as much information as you can about your setup, how the bug was achieved and so on
Sent from my HTC Holiday using xda premium
Monkeymannnn said:
Yes...it is truly necessary. The only exception being if it's an upgrade for a ROM you're already using. I.e. upgrading WhateverRom 1.4 to 1.5. Even then though a full or partial(cache and dalvik) wipe is usually recommended. You WILL have many problems if you flash a completely different ROM over another one without doing a full wipe.
Edit: proper procedure would be 1. Download the ROM you want 2. Place it onto your external sd card 3. Boot to recovery 4. Full wipe 5. Flash the .zip 6. Reboot 7. Enjoy 8. (optional) Report bugs to the developer in the thread dedicated to the ROM including as much information as you can about your setup, how the bug was achieved and so on
Sent from my HTC Holiday using xda premium
Click to expand...
Click to collapse
Thanks a lot for your answer, now, to further clarify my questions,
when you are just installing a simple mod, I.E a kernel, to a rom that already feel comfortable with, and you do an delvik and cache wipe? sometimes it really does not writes its properties over the previous kernel, let me explain.
i tried flashing holics kernell which is an non-overclock kernel with an very stable and battery friendly governor. over an more aggressive kernel like the overclocked Faux 123 v007. the results were that my device showed that the kernel installed was the holics but the cpu frequencies that were being run by the governor were more like the previous kernel and the phone was still overclocked although it wasnt supposed to anymore!
is this due to no doing a full data wipe? besides delvik and cache.
also if i was to do a full wipe. wouldnt i have to have some kind of apps back up system planned out. in order to make the phone looked just like it was before the kernel was flashed.?
I'm not that knowledgeable on kernels, but your best bet (afaik) would be to let your ROM boot up for the first time and then flash the new kernel. Titanium Backup is one of if not the best backup program (backs up apps as well as their data among other things). System data such as contacts, texts, etc. can be backed up and restored, but only to the same or very similar ROMs. You're gonna have problems if you restore data from say a touchwiz type interface to sense. Google backs up your contacts and apps anyways if you let it so they'll be restored and re-downloaded once you sign in with your google account.
Sent from my HTC Holiday using xda premium
With any rom or addons always read the devs instructions
Wiping data, cache and dalvik cache is a very safe bet, as for kernels the rom will flash it for you during the installation however if you are wanting to flash a custom kernel other than one in a rom. Just flash the rom and then the kernel.
ronnie498 said:
most devs will let you know what you need to do when flashing their item.
Click to expand...
Click to collapse
That's something I forgot to mention. ALWAYS read the entirety of the original post(s) from the dev. Also read through as much as you can of the thread from there. Nobody appreciates being asked things that were already covered in the thread. Some don't include full instructions, but most will and what they're telling you is what you need to follow.
Sent from my HTC Holiday using xda premium
Here's what I do...
If flashing a whole Rom (even if its just an update) I wipe everything...data, cache and dalvic
If flashing a kernel/apps/tweaks then I just wipe cache and flavorc cache
Those methods have yet to fail me...also, you don't have to let the Rom boot up before flashing a kernel...you can flash a Rom then immediatly flash a kernel (assuming the kernel is compatible with the Rom)
Sent from my HTC Holiday using Tapatalk 2
mg2195 said:
Here's what I do...
If flashing a whole Rom (even if its just an update) I wipe everything...data, cache and dalvic
If flashing a kernel/apps/tweaks then I just wipe cache and flavorc cache
Those methods have yet to fail me...also, you don't have to let the Rom boot up before flashing a kernel...you can flash a Rom then immediatly flash a kernel (assuming the kernel is compatible with the Rom)
Sent from my HTC Holiday using Tapatalk 2
Click to expand...
Click to collapse
THanks, that answers my questions.
i have yet fail to fallow instructions and there have been very little times when i have got my device stuck,
and most of the times when it happened i was able to find the answer of my questions around the forum,
you guys do a great job. :good:
I want to flash sensation xl.with stock rom.But his owner wants his applications save.Cuz i want be sure his applications will be save or not.I want to flash ics for his phone.
Use mybackup or titanium backup to save the app
Sent from my HTC One V using xda premium
Personally, i flashed Insanly Cool Sense 3 over the stock ROM without factory reset, only wiping dalvik cache and data cache, you can say this is dirty flashing, usually this works if you flash the same version of Android (if you have stock ICS and flash a custom ICS, most probably it will work, but issues can occur, nothing is safe when dirty flashing).
You should do a Nandroid backup from recovery before flashing, in this way you are pretty safe as you can always go back
Hi,
Im currently on ripper rom and want to chane back to wamanlite.
I understand I can do this using cwm recovery but do I need to clear any cache or data whilst doing it.
Cheers
Unless stated otheriwise by the developer I'd always wipe cache and dalvik while flashing a new ROM. This is normally
required and can be obmitted sometimes, but only when upgrading from an older ROM to a newer version of the same ROM.
HTH
almost certainly the ROM installation process will wipe cache and dalvik cache.
clearing data is a different thing, I always do it when changing ROMs just because I like to start fresh, but it's not always necessary. Always a good idea to backup first if you're going to attempt changing ROMs no matter what you do with regards to wiping partitions.
When changing between roms or upgrading to roms that are on a different base, you should always do a nandroid backup first and then do a full wipe / factory reset before flashing the new / other rom.
yuhp i currently run odin mobile so i just slam a titanium pro backup back real fast like then reboot via recovery, wipe dalvik and factory reset, the flash. once ur back in restore titanium and resync google and inabout 15-20 min you can be back to were ur were on your old version or rom and enjoying ur new one a hell of a lot faster,
btw another good tool for rom swapperes is nova launcher. especially if u have a lot of apps. because u can save ur exact layout to the cloud and refresh in less than 2 min, along with all of you personal settings and what not.
TragedysFinest said:
yuhp i currently run odin mobile so i just slam a titanium pro backup back real fast like then reboot via recovery, wipe dalvik and factory reset, the flash. once ur back in restore titanium and resync google and inabout 15-20 min you can be back to were ur were on your old version or rom and enjoying ur new one a hell of a lot faster,
btw another good tool for rom swapperes is nova launcher. especially if u have a lot of apps. because u can save ur exact layout to the cloud and refresh in less than 2 min, along with all of you personal settings and what not.
Click to expand...
Click to collapse
instead of copying me, you can just link to my post next time