So I currently have Das BAMF 3.0 flashed onto my HTC Thunderbolt. It's working perfectly fine; but say I wasnt to flash another ROM, do I have to wipe my data and cache again via clockwork recovery? (yes I backed my phone up and backed up with titanium back up)
Yes or you will run into issues like me
Sent from my ADR6400L using XDA App
When switching between ROMs from different devs one should always wipe data/cache. Different devs sometimes use different packages for some of the base system apps and the data usually won't "mesh". If you don't wipe, you may not notice a problem initially...but a few day's later you'll be asking "Why does XXXX force close on me?"
Only time you shouldn't have to worry about wiping is if you're flashing nightlies or incremental versions of a rom where not much has changed unless the dev states otherwise in the release post.
Related
I flash chingys latest version of gingeritis which is VIII .. I had flash the gb radio he suggested and did a full wipe... But when the phone starts up I get no service what so ever I can't even turn the radio off or on.. ...help??
Sent from my ADR6400L using XDA App
Check the md5 of the radio and redownload if it doesn't match. If it matches reflash both. Wipe everything a few times before flashing the Rom.
I have flashed a couple of the Different releases of Chingy's ROM and had not problems other than the FC on weather on the old ROMs. Now that it has been fixed it is literally flawless and smoother than stock with the goodies of GB.
This is what I did and do everytime I flash a ROM. Overkill yes but I have NEVER had a ROM take badly, or not boot up on the tb or droid like so many stories I keep hearing.
My Method:
1) Backup, Backup Backup. Everything. I use Ti Pro only for the stuff I cannot download anymore: Wifi Teth, Music Search and Download, etc. because Restoring old apps is never as good as downloading from the market. I also backup all my texts to Gmail using SMS backup. And Folder Organizer has a backup, and of course nandroid.
2) Boot to Recovery
3) Wipe like you went #3 I wipe once everything once, then wipe Cache, then Dalvik, then Battery stats, the Wipe again. Only once b/c Chingy's ROMs wipe as well. If it was another ROM I would wipe one more
4) Then Update.zip
5) Then Wipe again.
6) Then Update.zip
7) Then boot. (no service b/c the Radio hasnt been updated yet)
8) Then turn OFF.
9) Turn back on holding down and install Radio.
10) Now I'm running my favorite ROM on the tb to date Gingeritis VIII
I still havent rebooted it since I put it on this morning and I have restored all my Widgets, and 150+ apps and 3000+ txts. I have synced with my accounts mail fb and everything. Im also running Sense live weather Wallpaper and Lockscreen widget.
Flawless.
haha i do the same so i thought i was paranoid, glad to see its just precautionary and others do it too
the reason i ask is i want to know if anyone has had a problem going from rom to rom with out going back to there back up then flashing the new rom?
must wipe before going to different rom. you may have issues booting up.
affliction said:
the reason i ask is i want to know if anyone has had a problem going from rom to rom with out going back to there back up then flashing the new rom?
Click to expand...
Click to collapse
I've had no problem at all. I always do a full wipe before flashing a new rom though. If you don't want to do a full wipe, and you're only updating the same rom (for instance, from viper 1.1 to viper 1.2 or something), then you could try minimally wiping cache and dalvik cache. I always recommend a full wipe for best results though. I consider a full wipe to be wiping system, boot, data, cache, dalvik cache, and sd-EXT (if you have an EXT partition on your sd card)
I've successfully flashed joelz' ShooTeR ReWInD 3D over stock OTA w/o wipe with no issues and then flashed Evervolv's Absurd over that with no wipe and no issues.
USSENTERNCC1701E said:
I've successfully flashed joelz' ShooTeR ReWInD 3D over stock OTA w/o wipe with no issues and then flashed Evervolv's Absurd over that with no wipe and no issues.
Click to expand...
Click to collapse
That will most likely start giving you problems eventually, if you continue not to wipe. Things from one rom will start showing up in the next rom you flash, and you'll most likely start getting weird little bugs here and there. At least it always did with my Evo 4G. A full wipe is usually recommended, but every flasher has their own techniques.
k2buckley said:
That will most likely start giving you problems eventually, if you continue not to wipe. Things from one rom will start showing up in the next rom you flash, and you'll most likely start getting weird little bugs here and there. At least it always did with my Evo 4G. A full wipe is usually recommended, but every flasher has their own techniques.
Click to expand...
Click to collapse
+ 1 to full wipe, you will get bugs eventually, might battery life or maybe apps won't install or work, right now might be cause all the roms are mostly the same with no heavy customization but when they start messing a lot with roms you migh get screw
If you don't have an Evo3d well you don't have an Evo3d
Both these roms are based on the stock OTA ROM for 3VO. Also "format("ext4","EMMC", "/dev/block/mmcblk0p23")" is written into the updater-script of both ROMS, wiping the /system partition prior to install. Flashover issues usually happen when you start throwing AOSP and ports into the mix. That being said, I'm meticulous about backups and will never blame an issue in a flashover on the ROM without a fresh install or a peek into the zip to ensure the issue exist.
USSENTERNCC1701E said:
Both these roms are based on the stock OTA ROM for 3VO. Also "format("ext4","EMMC", "/dev/block/mmcblk0p23")" is written into the updater-script of both ROMS, wiping the /system partition prior to install. Flashover issues usually happen when you start throwing AOSP and ports into the mix. That being said, I'm meticulous about backups and will never blame an issue in a flashover on the ROM without a fresh install or a peek into the zip to ensure the issue exist.
Click to expand...
Click to collapse
It's still best to do a full wipe if you ask me. I do it even if I'm flashing the exact same ROM with say, one tweak in one of my battery icons or something. I always wipe lol.
yeah i just hate dealing with a full wipe everytime so i figured i would get some opinions on the issue right now im running steel rom and want to flash viper so im not sure what i want to do
My friend and I flashed MUIU onto his Vibrant we were coming from trigger 3.2. Everything was going great it work for about a few hours then a force close kept appearing.
android.process.acore
It will not let him use his keyboard or even get to his messaging app.
We have wipe data cache and davilk and even went to ROM manager and fix permissions.Still didn't work. Should I just ODIN back to stock re-root and find a different ROM or can this be fix's.
Need more information, like what version of MIUI you installed, did you make sure it was the one made for the Vibrant and not a different Galaxy S variant, did you follow all the instructions, did you wait the full 10 mins after first flashing it, did you try restoring all your apps + data with a non-MIUI backup program like Titanium Backup, did you try to restore system apps...
Anyway, try a complete re-install of MIUI. Follow the instructions posted in the MIUI thread to a "T".
I installed the latest build off of the thread in the vibrant forums. And yes I used titanium to do a restore
Sent from my ADR6400L using xda premium
I didn't wait ten minutes. What does that do. There weren't any instructions just wipe and flash.
Sent from my ADR6400L using xda premium
http://forum.xda-developers.com/showthread.php?t=1123922
that is the Rom we flashed
I think you might want to start from scratch and follow this link:
http://forums.miui.us/showthread.php?1189-Installing-MIUI-from-any-Non-MIUI-rom
As a rule you generally can not jump immediately from a non-MIUI rom to MIUI without resetting some parameters. In addition, you also need to be on FROYO bootloader instead of Gingerbread.
Anytime I run into issues with any ROM the first thing to try is a simple re-flash of the ROM. This fixes problems 97% of the time. If all else fails ODIN will take care of any other problems for the other 2% of the time. The other 1% is left open as nothing in life is perfect
I flash all MIUI/CM7 ROMs from a clean stock setup to ensure a good flash.
Hello,
I was using a CM7 ROM on my atrix, and I took the proper steps to install Nottach's ROM (Meaning, cache, data, system were wiped). I was happy with Nottach's ROM, and with Blur (gasp). But, I wanted to try out CM9. I flashed it, and camera didn't work, so I tried AOKP. Everything worked, except for a little bit of beta instability. I made a few system changes (ICS only- sleep policy, data connectivity, simple stuff), and defaulted to the internal SD card. I decided I didn't like ICS like I though I would, so I wiped and restored my backup. now, I'm stuck with non-working wifi and bluetooth. Also, the phone is rebooting at every turn. Hardly usable. Any suggestions? I have compeltely wiped the internal and external card, system, dalvik, cache, data, etc. I also tried the 2.3.4 fruitcake CWM .zip. no better. My phone went out of warrenty last week, literally 5 days ago. motorola is no help, and neither is AT&T because I am not a contract customer- I'm using it on straight talk.
Richard
Ricksta said:
Hello,
I was using a CM7 ROM on my atrix, and I took the proper steps to install Nottach's ROM (Meaning, cache, data, system were wiped). I was happy with Nottach's ROM, and with Blur (gasp). But, I wanted to try out CM9. I flashed it, and camera didn't work, so I tried AOKP. Everything worked, except for a little bit of beta instability. I made a few system changes (ICS only- sleep policy, data connectivity, simple stuff), and defaulted to the internal SD card. I decided I didn't like ICS like I though I would, so I wiped and restored my backup. now, I'm stuck with non-working wifi and bluetooth. Also, the phone is rebooting at every turn. Hardly usable. Any suggestions? I have compeltely wiped the internal and external card, system, dalvik, cache, data, etc. I also tried the 2.3.4 fruitcake CWM .zip. no better. My phone went out of warrenty last week, literally 5 days ago. motorola is no help, and neither is AT&T because I am not a contract customer- I'm using it on straight talk.
Richard
Click to expand...
Click to collapse
If you have a look at Nottachtrix thread. A lot of people are having problem with wifi because of the latest faux kernel. Try doing a fastboot erase of everything including boot and then installing the fruit cake.
You can have a quick look at how to fast boot erase in the general section. Try search functionality.
Sent from my MB860 using XDA
I would also suggest doing a full fastboot wipe and installing the CM7 RC1 nightly that way you can escape blur but that just me lol for sure a full fast boot wipe or from your current frootcake maybe trying flashing a diffrent kernel
This phone was an insurance replacement from ATT, so alway a bit wary of these refurbished phones.
So for the longest time it has always been a bit glitchy, hanging, and unstable. I assumed it was a software problem, and something i had done wrong when flashing...but now I am wondering if maybe my phone is a lemon. Lately it has been rebooting randomly on its own,
I wanted to try flashing back to stock, just to start from scratch, and I did with Da G's stock rom . Then i just rooted it with Da G's root, and put on CWR. Then I flashed King Kang Rom. It's been still real buggy. Maybe I need to to stock ICS or JB then flash a ROM? OR maybe it's just this phone....either way not real happy with the stability i've been dealing with.
If youve tried multiple roms and stock roms and its still buggy then its probably the phone, I have got so many replacement phones that were duds
Are you doing a wipe between all those roms or just flashing one over the other? That could be a major problem that is easily fixed.
Yes, i do full wipes/factory reset in CWM every time.
I know i have seen some guys say you must flash like 3 times, so maybe i'm not flashing it enough times or something..? i also saw someone say don't touch your phone for 15 minutes after flashing. i have no idea if these tricks actually work or what. doesn't seem to be a definitive rule book on how to flash the right way
How are you restoring your apps? TB or letting Play reinstall them?
using TB. I usually do a just apps reinstall, then data
Was the TB backup from a different version of android, i.e. GB, ICS then installed on JB?
yes, i did create it on an ICS rom. you think that could be causing me problems?
Good possibility. I had the same issue. Moved from CM9 to CM10 and restored through TB. Lots of FC and reboots. Wiped and let Play reinstall everything, now its smooth.
great thought and worth a shot if that's what could be causing a problem. so did you lose all your data then with all apps? msgs, etc? sucks to start from complete scratch. i'll even miss call log
Lost data, but was able to d/l everything else. Messages and call logs were gone. It is worth it to have a working phone with out glitches. Let me know if it works.
Well a good test is to install a known solid ics problem free ROM like Padawan or Black ice? (exact name escapes me). If it works for u then over clock it to 1836 with setcpu and u will have a ROM VERY close to the JB rom smoothness but actually works.
If u still have problems then u may very well have a flaky phone.
(Oh yeah don't get to worried about stuff like wipe 3 times etc...old wifes tales. I haven't done that for over a year on 3 android phones. ). Also it is Safe to restore apps AND data with titaniumb (just not system data).
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
+1 on the old wives tale. Seems more like a placebo effect. I only wipe once, and I've flashed roms on tons of phones.
Sent from my Galaxy Nexus using xda premium
tried installing padawan...so far so good, have not overclocked yet....will report back
Some roms will format your system partition prior to flashing the rom while others do not.
Beyond the wipe of data, cache, dalvik and such, it is wise to go into " mounts and storage" and format the system partition while in CWM recovery.
This ensures that nothing remains on the device before the new rom image is pushed to the system partition.
I agree that wiping 3 times is a bit over the top, but wiping the entire image base before flashing a new one is almost always mandatory.....g
For future reference, you can back up call and sms logs and restore them without causing lags or fc. The logs are simple .xml files.