I'm just wondering if my procedure for updating my ROM is correct, as I've only owned a smartphone for about a month, and have only flashed once.
Basically before I was running AOKP build 2 and Franco kernel r79 (or thereabouts) on my Nexus 4. I wanted to upgrade to AOKP build 3, so I backed stuff up, booted up in recovery, wiped my data, cleared the cache, then cleared the Dalvik cache before rebooting. Then it took me back to the initial setup screen, but I got confused when AOKP and Franco Kernel was still installed. I figured I should just open up the browser, download build 3 to the device (since everything is wiped), and then I'll flash that on top of build 2.
Am I supposed to flash back the stock ROM and kernel, or does it not matter since I will be running the same custom ROM?
Likewise, if I wanted to change my custom ROM (like install PA3 or something), then I would definitely need to flash back the stock rom and kernel before proceeding, am I right?
Smeghead_ said:
I'm just wondering if my procedure for updating my ROM is correct, as I've only owned a smartphone for about a month, and have only flashed once.
Basically before I was running AOKP build 2 and Franco kernel r79 (or thereabouts) on my Nexus 4. I wanted to upgrade to AOKP build 3, so I backed stuff up, booted up in recovery, wiped my data, cleared the cache, then cleared the Dalvik cache before rebooting. Then it took me back to the initial setup screen, but I got confused when AOKP and Franco Kernel was still installed. I figured I should just open up the browser, download build 3 to the device (since everything is wiped), and then I'll flash that on top of build 2.
Am I supposed to flash back the stock ROM and kernel, or does it not matter since I will be running the same custom ROM?
Likewise, if I wanted to change my custom ROM (like install PA3 or something), then I would definitely need to flash back the stock rom and kernel before proceeding, am I right?
Click to expand...
Click to collapse
Well since I really only have experience with a tablet and older cell phone I can only speak of my experiences with those. My tablet runs 4.2.2 and the phone 2.2. With both devices I have never had to flash them back to stock to flash an update. Usually a data and cache wipe was sufficient although I will wipe the whole system when flashing a huge update on the tablet.....like from GB to JB.
What helpful people told me when I asked the same question was...
When going to a very different (including the same ROM going to a new android version, ie 4.1 => 4.2) ROM (as in, not just doing a small update on the current one) :
Wipe both caches, wipe /system, wipe /data, and wipe internal sd card and factory reset.
Then flash what you want - ROM => Kernel (if desired) => GAPPs
Wipe caches again.
Done!
I don't know about your particular phone and those ROMs. Is AOKP 2 to 3 a big change ? If so, simply writing 3 over 2 could cause some major problems. I totally messed up and did something like that once and while it wasn't a huge deal I had to start over and do it again because it wasn't usable.
In regards to your description of what you did, you didn't wipe /system, so you didn't wipe your system and so it was still installed like you saw. You'll need to "start over" and wipe everything again. Since the N 4 doesn't have an external SD, I'm guessing you guys wipe /system and like, push the ROM to be flashed to the internal storage ? Maybe ? I have no idea - I've always had an external SD, but since it's a Nexus device I'm sure the procedure is well-covered !
My Kindle Fire tablet also does not actually have an SD card either.....the 8GB memory has been partitioned and originally I would have 5GB available out of 8 which would act as the SD card and 1.09GB for internal or "phone" memory. I have mine even more scrapped down as this one has the ability to either boot into CM7(GB) or the newest CM10.1(JB).
Say for example I went from Android 4.1.2 to 4.2.2.....that's a pretty big update......I would do a full wipe meaning doing it in this order: factory reset, wipe cache, wipe dalvik, and wipe system.
If I wanted to flash a little update of my current 4.2.2 where only some slight tweaks were applied I would just wipe cache and dalvik only. There are times when this simple flash wipe technique WON'T work and you'll probably realize it real quick. There could be any one of a million bugs that could occur and usually they are pretty noticeable. If that happens (sometimes it will, sometimes it won't) the worst case scenario is just going ahead and doing the full wipe.
I'm not knowledgeable on AOKP ROMs so I don't want to venture there. Boot loops are a whole different story and you might want to educate yourself as much as possible because they can happen. I had a couple occurances with a boot loop not too long ago as I was messing with a system font editor and it caused a boot loop. I didn't panic.....I already researched how to handle them so getting it back online was quite easy.
Hope my rambling has helped even a little bit.....
As long as you are just updating the same Rom, you can usually just flash it over (unless the Rom-maker says different).
If there are some fundamental changes in the Rom update, or you are switching to another Rom, then you should wipe it all.
To make it all a bit easier, you can use the Megawipe script:
http://forum.xda-developers.com/showthread.php?t=1832326
Along with the Aroma installer, it's just a few clicks to clean it all up, and ready for a fresh install
Related
This is not a "how to root" post.
I finally said F it and installed clockworkmod and flashed a ROM but I just did a basic one to get my feet wet.
My basic question is how do ROM upgrades get installed. Say I install the latest EaglesBlood ROM and there is an update for it. Do I have to do a complete data/cache clear and re-flash with the newest ROM or is there some sort of updater or is each developer different?
Thanks.
That really depends on what was updated. Most of the time if you are upgrading to a newer version of the same rom, you can get away with just flashing over it, and keeping your data intact. Clearing /cache and the dalvik-cache is recommended. However this is not always the case. Some changes require data wipes to be effective. Usually best to ask in the rom's thread if a wipe is needed.
Also, sometimes you can just do a nandroid backup, install new rom, then reboot into cwm and do an advanced restore just restoring the data partition. Again, it really depends on the rom, and what was upgraded.
Sorry if this has been covered way too many times but I want to make sure.
I have rooted my phone that was running 3.20.502.52 with the AAHK so now I'm on the version it sent me back to and I have done nothing since. I am getting ready to switch to the Jellytime R29 ROM. I know to make a Nandroid backup but I was a little concerned about getting back to the state my phone is right now should anything go wrong or if I don't like it, go back. It seems that I can't just restore my Nandroid through CWM without flashing a different kernel since I'd be coming from a JB ROM.
My current setup is:
Android: 2.3.3
Sense: 2.1
Kernel: 2.6.35.10-gd2564fb
Software 2.47.502.7
So, in order use my Nandroid in case the Jellytime messes up, do I simply have to do a factory reset, and wipe cache, and dalvik-cache (this is considered a "full" wipe, yes?) and then flash a compatible kernel then restore my backup? And if so, can I find that exact kernel somewhere to flash or is there another one you guys can recommend me to use in my situation? OR, can I just straight up restore the Nandroid since the backup should cover the kernel too?
Sorry I'm a newb. I'm trying to learn. All help is greatly appreciated. I'm hoping to flash Jellytime as soon as I know how to recover from it.
1. Welcome!
2. The kernel is included in the backup. You also don't need to wipe anything; just restore the nandroid. Make sure you use a fully updated recovery; make sure using ROM Manager for CWM or the 4ext Updater or Play Store app for 4ext.
3. A full wipe is system, data, and cache. Dalvik is already included if you wipe those. A factory reset only wipes data and cache, leaving system unwiped. In 4ext just choose "wipe all partitions except sdcard."
Alright. I already flashed Jellytime a while ago and so far I see no reason for wanting to go back although I did a quadrant standards test and scored lower than stock. Not sure why, but either way, this was a nice first ROM. What I wiped in cwm was the reset, cache, and dalvic. So far everything is working if I missed anything.
Didn't know wiping wasn't necessary for using backups. Must of missed that in my reading. Thanks though. I'll become less of a newb over time.
I have looked all over and there have been some people that have said how to flash a new kernel, and how it is basically exactly like flashing a rom and don't go into it any further.
Plus it seems like the only people i can find that even mention flashing a new kernel are also making a guide to flash a new rom, so keep the settings form an old rom aren't an issue for them or the people reading those guides.
I have found a rom that I like and want to stick with it, but what I am wondering, is if I want to test out different kernels for potential battery saving abilities, will I have to go through the same process in CWM of wiping the cache/dalvick cach/format system and stuff like that, or can I just flash the new kernel the same way I can flash a baseband, without changing any settings or worry about it deleting anything I have done?
I just don't want to go around *assuming* anything because last time I did that I had to spend 50 bucks on a JTAG
Thanks!
I only use KTkernel and.....
wipe cache
wipe dalvik
install kernel from ext sd or sd
wipe cache
wipe dalvik
fix permissions
rebooot
And just make sure they are TW if you are running a TW rom and AOSP if you are on that type of rom. And have a backup in case something goes wrong.
I have been flashing kernels on two different phones and have never had a problem. Just read and make sure you are doing it right.
Some people say you should wipe cache + dalvik before flashing a kernel, but that's questionable if you really have to. I simply flash and reboot, never experience problems. And definitely make sure it's meant for TW or AOSP, depending on which you are running.
Sent from my SCH-I535 using Tapatalk 2
Flashed several ROMS in my life and have not always wiped all data. Mainly i do dalvik and cache. My phones have always work. Now i have a Razr HD with an unlocked BL with TWRP loaded. I cant seem to get past the initial bootup screen no matter what ROM i flash. What am i missing here guys? Do i need to check the "factory reset" in TWRP along with Dalvik, system and cache?
famac! said:
Flashed several ROMS in my life and have not always wiped all data. Mainly i do dalvik and cache. My phones have always work. Now i have a Razr HD with an unlocked BL with TWRP loaded. I cant seem to get past the initial bootup screen no matter what ROM i flash. What am i missing here guys? Do i need to check the "factory reset" in TWRP along with Dalvik, system and cache?
Click to expand...
Click to collapse
answered here http://forum.xda-developers.com/showthread.php?t=2465695
bweN diorD said:
answered here http://forum.xda-developers.com/showthread.php?t=2465695
Click to expand...
Click to collapse
Not really. The majority of ROMS in question have been 4.2.2 based....
famac! said:
Not really. The majority of ROMS in question have been 4.2.2 based....
Click to expand...
Click to collapse
quote from post 11
"By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot"
bweN diorD said:
quote from post 11
"By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot"
Click to expand...
Click to collapse
Please explain this further to me. My problem is with 4.2.2 ROMS. The fix above is for folks having issues with 4.3 ROMS. Are you suggesting that doing this will also fix my 4.2.2 problems? This is also CWM while i run TWRP. I did a quick look and the two are setup a little difference. I played around with those highlighted instructions and almost accidentally wiped my only backup of my previous state. I actually thought i was toast but somehow i reloaded and went back to my old backup state.
famac! said:
Please explain this further to me. My problem is with 4.2.2 ROMS. The fix above is for folks having issues with 4.3 ROMS. Are you suggesting that doing this will also fix my 4.2.2 problems? This is also CWM while i run TWRP. I did a quick look and the two are setup a little difference. I played around with those highlighted instructions and almost accidentally wiped my only backup of my previous state. I actually thought i was toast but somehow i reloaded and went back to my old backup state.
Click to expand...
Click to collapse
i could be wrong, but in my opinion having the exact same issue even though its a different version, one of the 2 fixes in that thread should work.
the first fix likely doesn't directly apply although i suggest you ensure you have the latest version of your recovery of choice found here http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
second fix (backup ALL data you don't want to loose first as noted above), then do a full wipe as listed above, not just a fdr that doesn't wipe everything on the internal card.
the problem at this point is, you are assuming it wont work because of version differences, i am assuming it will. until you try it, i don't see any point in exploring other options, if there are any.
Dirty flashing when you go to different ROMs is generally not a good idea. Even on 4.2.2, it leaves residual data behind. There's a reason that the devs talk about doing complete wipes in their ROM threads, and there's a reason that they tell you not to talk about bugs unless you use their install directions.
RikRong said:
Dirty flashing when you go to different ROMs is generally not a good idea. Even on 4.2.2, it leaves residual data behind. There's a reason that the devs talk about doing complete wipes in their ROM threads, and there's a reason that they tell you not to talk about bugs unless you use their install directions.
Click to expand...
Click to collapse
Yeah, i am straight now. Did a full wipe and sailed right past the startup animation. Thanks all.
famac! said:
Yeah, i am straight now. Did a full wipe and sailed right past the startup animation. Thanks all.
Click to expand...
Click to collapse
Nice! Glad to see you got it working.
so i had been running my nexus 5 with cataclysm ROM for a while.,today i decided to do a cm12 nightly flash ...i worked well it booted fine, everthing worked well ,flashed gapps ,tibu,restored my apps .now after a reboot i kept getting "system uid inconsistent " errors.I (like a idiot) tried "fix permissions "in TWRP which resulted in a boot loop.so i decided to flash cataclysm rom freshly again.It worked well but now sometimes i get force close errors like "android.process.acore" and sometime google playstore force closes.
i am scared i might have spoiled something,
also the cm12 nightly reflashed bootloader as it was 5.0.2 and also radio ,do these things cause something to break??
how do i return to normal??
I have updated my Radio while I am still using Cataclysm and I didn't face any of the problems you mentioned above. I have also switched from Cataclysm to other ROMs (including CM12) and back couple of times in between and never faced any problems.
I generally wipe everything except Internal Memory when switching ROMs. Did you do the same?
Yes,its a clean flash.
Just a question has this got something to do with the "fix permission" thing I did in TWRP?
Even though I wiped and flashed cataclysm later??
Also I googled around .does a corrupt data partition cause these kind of errors to pop up??
Currently the occurrence of these errors is rare but I've notice reccurent notifications from google playbooks even after I remove the notifications they reappear after some time .
I've decided to use my nexus 5 for a while and see if the problems are reproducible .
But I feel like the only wrong thing I did was "fix permission " in TWRP other than that its was just regular ROM flashing.
Yes... a corrupt data partition might cause this.
Generally I wipe the following when I am flashing a new ROM:
Dalvik Cache
System
Data
Cache
As you see I wipe data as well when I am moving to completely different ROM.
Does that mean my device is not fit for flashing new Roms anymore.?
How can I fix my data partition to be as good as new??
No... What I meant was to wipe the Data partition as well before flashing a new ROM. Wipe all the partitions except the Internal Storage partition. (Note: Data and Internal Storage are not the same)
If that still doesn't work, try flashing the factory image to rollback to stock. Then again flash the recovery and try flashing a custom ROM.
You might try just reflashing the CM12 nightly and see if that fixes it. Otherwise you'll have to flash from fresh. I wouldn't recommend doing a full backup restore if possible.