Related
Hey!
Well I'm back.. I had a G1 when it first came out(pre order)... I lasted with that thing a couple of months and couldn't deal with it being so buddy at first and just missed my BB in general.
Anyway, I've been wanting to get an Android phone, being that I'm still in contract I didn't want to pay full price, I found a mytouch 3g for 65 bucks... SO I went for it.
I got it today with 1.6, I just read up all day at work and successfully rooted, and installed about 4 Roms so far, right now I'm on the latest CM6 with Google apps(booting now)... I might stick with this one for now...
Now for one question, and forgive me if it has been asked, I managed to do everything else without asking so I deserve one noob post right?
If I ever want a new ROM, do I need to wipe everytime? Or is there a much simpler way after the initial load?
I see some people installing a new rom very often, do you re-download all your apps?
thats pretty much what i do (re-download all my apps) im not sure if you have to wipe every time im fairly sure it depends on the rom your flashing but overall i know it is a good thing to do a wipe before flashing a new rom every time because if not there could be things left over from the previous rom and if it boots it will have force closes and all kinds of nasty stuff
in summary yes to my knowledge you should wipe every time before flashing a new rom im not sure if you have to- i just do
i could be wrong, this is just my take on it
wrong section!
moving to general​
If you're using AOSP (Android Open Source Project) builds (basically anything that does not include HTC Sense, MotoBlur ect) then no, you should be fine without a wipe, all your apps, app data, and settings will remain intact.
Should you need to wipe, you can backup your apps by typing this in to the terminal.
mkdir /sdcard/app
cp /data/app/* /sdcard/app
cp /data/app-private/* /sdcard/app
Then wipe (including dalvik cache!) flash the new ROM from recovery, wipe dalvik cache again and restore them
mount /sdcard
cp /sdcard/app/* /data/app
And you're done
Thanks for the tips. Sorry bout the wrong section!
Anyway, I installed the Cyangen(sp?) modded rom, the latest one on there site, Rc3 I believe? Besides the older phone being a little slow it seems to run great so far.
jmejiaa said:
Thanks for the tips. Sorry bout the wrong section!
Anyway, I installed the Cyangen(sp?) modded rom, the latest one on there site, Rc3 I believe? Besides the older phone being a little slow it seems to run great so far.
Click to expand...
Click to collapse
CM-6.0.0-RC3-DS is NOT the latest version. The latest is now CM-6.1.0-RC1-DS.
The latest for CM-6.0.0 is simply CM-6.0.0-DS.
The RC stands for Release Candidate. Which means it's still exerimental.
CM-6.0.0-RC1 is VERY OLD (experimental).
CM-6.0.0-RC2 is PRETTY OLD (experimental).
CM-6.0.0-RC3 is OLD (experimental).
CM-6.0.0 is STABLE (official release!).
CM-6.1.0-RC1 is NEW (experimental).
CM-6.1.0-RC2 is NOT YET RELEASED.
etc etc etc.
Hello everyone,
I tried search the answer but only found something in a different phone section and it was not clear.
My question...I have already flashed with the Ice rom and it works fine...when I decide to change roms and flash a NEW one...what are the steps I must do for it to work correctly?
Thanks in advance for any help,
Brian K
If you're staying with the same rom (i.e. upgrading to a newer version of the same rom) - back up, wipe cache/dalvik cache, then flash
If you're changing rom but staying with Sense-based roms - do the same and see if you have any issues. If you do run into issues - wipe data/cache/dalvik cache, reboot.
If you're going from AOSP to Sense or Sense to AOSP - back up, wipe data/cache/dalvik cache, flash.
Its just do the same thing you did the first time. Make sure to do a full wipe and flash
Sent from my HTC Glacier using XDA App
dnguyen1988 said:
Its just do the same thing you did the first time. Make sure to do a full wipe and flash
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Might be a lil off topic but I think it might be related.....you said 'do the same thing you did the first time'....so i'm guessing first time means the first time i flash a custom rom?? And if so, does that mean for the first time i flash a custom rom should i do a full wipe???
Thanks!
Paso876 said:
Might be a lil off topic but I think it might be related.....you said 'do the same thing you did the first time'....so i'm guessing first time means the first time i flash a custom rom?? And if so, does that mean for the first time i flash a custom rom should i do a full wipe???
Thanks!
Click to expand...
Click to collapse
Yes you are correct. The post above mine is way more detailed. You should also do a nandroid backup of the rom you're on now in case you wanna go back.
Sent from my HTC Glacier using XDA App
The best way to move between ROMs is to make a nandroid + Titanium backup. Fully wipe. Flash your new ROM. Carefully re-import settings from Titanium if all seems to be working well. In the event of a failure, roll back to your nandroid copy.
Im really sorry but I still dont understand...I mean I kinda do but dont want to mess up and because of that, I'm trying to have a clear pic in my head.
Example...when you flash for the first time you have to:
flash recovery
wipe data/cach/etc
drop the rom onto the sd card
select the rom from sd card
reboot phone
Do you have to do ALL the same steps again, if you want to try a NEW rom...or no?
If no...what steps do you do differently?
Also...as for the Nandroid backup...do you do this everytime also, or just once?
Again, Im really sorry to be such a newb...but I am trying...I have just about every guide...its just that most guide are not for newbs and alot of times they are outdate. Dont get me wrong I appreciate the guides...I TRULY Do, I just dont want to mess this phone up.
Thanks in advance for any help
Brian K
Repeat everything as you listed it except for flashing a new recovery (unless moving to/from a Froyo/Gingerbread; as recovery differs between Froyo and GB). I usually only make nandroid backups once I have found a ROM that I like and have it working well. It's a system restore! Then if I want to tinker with the "shiny new ROM" that just came out I can load it up and play with it. If it doesn't work well or at all, just roll back to your faithful fully working nandroid copy you made.
Kline said:
Repeat everything as you listed it except for flashing a new recovery (unless moving to/from a Froyo/Gingerbread; as recovery differs between Froyo and GB). I usually only make nandroid backups once I have found a ROM that I like and have it working well. It's a system restore! Then if I want to tinker with the "shiny new ROM" that just came out I can load it up and play with it. If it doesn't work well or at all, just roll back to your faithful fully working nandroid copy you made.
Click to expand...
Click to collapse
Actually switching between Froyo and GB has been made even easier by the new ClockWorkMod Recovery... TrueBlue's method works amazingly... Find it here http://forum.xda-developers.com/showthread.php?t=944681... Flash it like you would a ROM via CWM... His zip also INCLUDES the STOCK RECOVERY so if you ever want to recalibrate the battery you can do so by going into Rom Manager and selecting 2.5.1.4 as your recovery, when done just switch back by selecting 3.0.0.5 and that will load up 3.0.0.6..
To answer OP's Question...
Step 1) NANDroid backup (Backup and Restore > Backup > press trackball)
Step 2) wipe data/cache/dalvik (I always do each of them twice for safe measures); Like someone here already said, if upgrading to a new version of THE SAME ROM BUT ITS BEEN UPDATED, just wipe CACHE AND DALVIK. Otherwise, wipe all 3.
Step 3) Install zip from sdcard > choose zip from sdcard > select the ROM you want to install.
P.S. FYI I WOULD DO THIS FIRST!!!!! For flashing TrueBlue's 3.0.0.6 to be able to flash both froyo and gingerbread roms without changing the recovery each time (which is a pain in the ass btw) FOLLOW STEP 3 EXACTLY. The only difference is you will choose GlacierRecovery_to_RomManager.zip instead of whatever Rom you want. Reboot, go into RomManager, scroll to the bottom and select All ClockWorkMod Recoveries, choose 3.0.0.5 and it should say successfully flashed. Reboot into recovery and make sure at the bottom it says CWM 3.0.0.6. If it does, congrats, if not, reboot and reflash it, and continue to do this until you see CWM 3.0.0.6 at the bottom of the recovery screen.
PM me if you can't get it to work and want some more help with anything!
Hello,
I want to say it again, that the people in the Android forums are so much more helpful then back when I had a iphone and needed help. The people over in the iphone forums would sometomes help, but most of all, they would be rude.
Android forum techs are the BEST!
As for the Nandroid backup...this part also is a bit confusing, cause a few guides/videos show them doing the nandroid after they do the 3 wipes. However, I thought it made sense to do it first like you said.
Last night at around 4am I flashed CM7 with no problem and it is truly amazing. I am started to make sense just a little bit of all this but right now...I still cant wrap my head around the whole flashing recovery process.
Please understand I.m not just asking for answers, I am also reading as much as possible...I am making an effort.
Thanks so much everyone,
Brian K
No problem. If you have any questions I'd be glad to answer them for you or direct you in the direction for your answer. Just pm me like I said.
Just continue to read read read.. That's why I did and this is the first phone I've rooted or done anything with and I've become knowledgeable with some of the easier concepts and I'm trying to learn more complicated concepts as I go along.. Everyone had to start somewhere, and most of us here on xda realize this which is why we are so happy to help as long as these questions aren't asked and answered 4000 times.
P.S. Where ever you read/watched to wipe before NANDroiding I would advise to not go back to that because that is COMPLETELY the wrong thing to do!!
Sent from my HTC Glacier using XDA App
No prob Brian I know I wasn't as detailed as other ppl who helped but if you have any questions just pm me.
Sent from my HTC Glacier using XDA App
I know I keep saying this but so far everyone here is sooo freakn helpful. Im shocked cause when I had a iphone and did the whole jailbreak thing...the people over there where very rude.
dont worry dnguyen1988...u were nice enough to help out and I promise to take you up on the offer for help
Amac1222...just to be clear...your saying to do a Nandroid backup before wiping ANYTHING...yes?
Thanks again for everything,
Brian
Yes, even when updating your rom, you can always move the nandroid off your sd to an external hd. Or you can delete them as you move up updates, (i.e. Build 41 to 42 to 43 delete 41 once you know 42 is good to backup to if needed). When I flash kernels I tend to not nandroid each time although I should. As a super noob I would and I used to until you are comfortable.
The basic thing is you always want something to fall back on in case you get stick in a boot loop or stuck on the mytouch screen.
Sent from my HTC Glacier using XDA App
Wondering something here...when i wiped my device, i went thru rom manager and did the wipe device thing to wipe all user data to clear out CM7.0.
after that i installed virtuous to try it out, and i noticed in root explorer in the system>app folder, there were CM apk's in there. does virtuous use CM stuff in their roms?
if not, why would they show up even after a full wipe?
Also, has anyone here ever had issues changing from a non sense rom to a sense and back to non sense in a matter of 2 hours?
well, if they are any of the CM specific apps like:
CMparts or CMstats or CMwallpapers (I think there are a few more, can't remember off the top of my head), then it sounds like a case of a "format" that didn't actually format. you wouldn't be the first person to deal with this problem with rom mgr and CWM recovery.. it is known to be finnicky when it comes to formatting partitions (among other things ).
thankfully, we have a tool now that will give you a true, clean format of /system /data and /cache partitions without having to manually run the commands every time (like I know some of us have been doing).
if you are the kind of guy, like myself, who likes to perform a clean wipe between roms, I'd highly recommend downloading that and using it instead of the rom manager/CWM recovery options.
tackleberry said:
Also, has anyone here ever had issues changing from a non sense rom to a sense and back to non sense in a matter of 2 hours?
Click to expand...
Click to collapse
Can't answer your first question, but on my old Hero, I swapped from an AOSP ROM to a Sense ROM once almost every hour for a day because I couldn't make up my mind. Nothing bad happened to it and my father is using it now with no ill effects.
pmcqueen said:
well, if they are any of the CM specific apps like:
CMparts or CMstats or CMwallpapers (I think there are a few more, can't remember off the top of my head), then it sounds like a case of a "format" that didn't actually format. you wouldn't be the first person to deal with this problem with rom mgr and CWM recovery.. it is known to be finnicky when it comes to formatting partitions (among other things ).
thankfully, we have a tool now that will give you a true, clean format of /system /data and /cache partitions without having to manually run the commands every time (like I know some of us have been doing).
if you are the kind of guy, like myself, who likes to perform a clean wipe between roms, I'd highly recommend downloading that and using it instead of the rom manager/CWM recovery options.
Click to expand...
Click to collapse
yes i saw that program pop up when i was tying in the topic for this post! sounds like a great program wish it was posted a couple of days earlier lol. ill try when i get my device back.
wondering tho if these half ass wipes that CWM does caused my problems. i usually wipe when changing a type of rom, even with CM7 (nightly to RC for example). if i flash a nightly, i usually do a wipe every 2 nightlies.
Not sure what you mean by half ass wipes,lol, but I've never trusted the system wipe to do the job. I always do cache and dalvik along with it.
Sent from my HTC Vision using XDA App
enserio said:
Not sure what you mean by half ass wipes,lol, but I've never trusted the system wipe to do the job. I always do cache and dalvik along with it.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
i do too. half ass saying there is stuff not wiped lol
tackleberry said:
i do too. half ass saying there is stuff not wiped lol
Click to expand...
Click to collapse
Yeah... as amazing as CWM recovery is, the wipe process can be a bit.... lacking sometimes. If you don't use amazinglarry's superg2wipe script, then I would at least manually wipe through recovery before switching roms - this way you can be at least get most of the artifacts and "ghosts" left over from your last rom.
Sorry for bumping this old thread, I came across it while googling.
I've always used "wipe data/factory reset" in CWM. But that only wipes your /data and /cache partition.
Now, i only recently found out "wipe /system" under "mounts" in CWM. Meaning, I had never wiped my /system partition before, while swapping between 50 roms (be it AOSP or Sense). And I never had any problems. But the best way to fully wipe your system, is to do every partition manually + dalvik and battery stats.
Hi,
I would like to know if someone already experienced this kind of bug.
Whenever I try to wipe data or cache with TWRP or CWM Recovery, first step (wiping data) goes ok, then it totaly freezes at the second step, and if I hard reboot the phone, none of the data has been wiped away.
Any help would be grateful, thank you. :victory:
Let it run..... it takes 10 to 15 minutes to complete.
Sent from my LG-D800 using Tapatalk
+1 or go into settings and change it to rm -rf and it will be a lot quicker.
This a simple guide I made for the note 3. Seeing these 2 questions being asked alot here so posting it here. Will need to edit it a bit so currently it's a WIP.
NOTE- First thing you should do before flashing roms/kernels for the first time is backup EFS.
How to flash CLEAN flash roms -*This is how I flash roms(even updates of the same rom) and the method i recommend to users. It is better to take 10 mins to set your phone again rahter than wasting more time to fix issues that could have been avoided by a clean flash.
NOTE- This is a MUST when changing roms.
1. Make a nandroid backup in recovery
3. Wipe data/factory reset
4. Wipe system
5. Wipe cache
6. Wipe dalvik
7. Flash ROM
8. Flash gapps
9. Flash kernel(optional)
10. Reboot
11. Wait 10 mins, then do another reboot
12. Enjoy
How to DIRTY flash roms -*This method is used by users when flashing a update of the same rom.*
NOTE- Some users follow this and some just flash the rom without wiping anything.
Note- If you flash rom that has aroma installer you will need to edit the updater script to make sure the aroma doesn't wipe system before flashing rom.
1. Make a nandroid backup in recovery
3. Wipe cache
4. Wipe dalvik
5. Flash ROM
6. Flash gapps
7. Flash AK kernel(optional)
8. Reboot
9. Wait 10 mins, then do another reboot
10. Enjoy
How to SUPER CLEAN flash roms -*This is the method that I recommend to your that have weird issues, even after clean flashing.
Will be adding this method. Need to edit it a bit.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
How to flash flash kernels -*Many users say to wipe cache/dalvik but it's useless as neither if their partitions are affected when flashing a kernel.
1. Boot into recovery*
2. Flash kernel*
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
@Khizar welcome back man, good to see you're writing guides again. Get that RC title again!
Sent from my OnePlus One using Tapatalk VIP
nicholaschum said:
@Khizar welcome back man, good to see you're writing guides again. Get that RC title again!
Sent from my OnePlus One using Tapatalk VIP
Click to expand...
Click to collapse
Yeah let's hope ppl actually read and my time editing see stuff to make it for OPO isn't wasted.. These forums seem to be worse than the note 3 ones.. Man saw this guy today who apparently couldn't find the link to gapps that was posted in the OP.. SMH
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Khizar said:
This a simple guide I made for the note 3. Seeing these 2 questions being asked alot here so posting it here.
Click to expand...
Click to collapse
While this is true, it's because people are too lazy to use the search feature or at least look at the stickies. But the information is out there already.
[GUIDES][Q&A]How-To Guides For Beginners + Q&A
CafeKampuchia said:
While this is true, it's because people are too lazy to use the search feature or at least look at the stickies. But the information is out there already.
[GUIDES][Q&A]How-To Guides For Beginners + Q&A
Click to expand...
Click to collapse
I've seen that thread, it's pretty useful bit I wouldn't say "the information is out there already. If you read the thread his instructions are just telling users how to wipe and flash roms.
The point of my thread was, or still is, to list all the different ways to flash roms. Clean, dirty, super clean. Most new users don't know the difference.
With that being said I am not saying anything negative about the guide nor am I comparing the 2 guides. Think that I should add that, on the Internet things are usually misinterpreted.
I am simply making a bit know detailed and specify guide just for flashing roms.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Amazing as usual! You're a treasure, my friend! So happy to see you back on xda!
Plus... do you really want me to tell you how we "dirty flashers" flash roms? love you man, you're perfect!
NOTE- This is a MUST when changing roms.
1. Backup EFS -Not necessary every time you flash a ROM.
2. Make a nandroid backup in recovery -Not necessary every time you flash a ROM.
3. Wipe data/factory reset
4. Wipe system
5. Wipe cache
6. Wipe dalvik
7. Flash ROM
8. Flash gapps
9. Flash AK kernel(optional) -There are many kernels available for our device, not just AK.
10. Reboot
11. Wait 10 mins, then do another reboot -Not necessary.
12. Enjoy
Transmitted via Bacon
daxgirl said:
Amazing as usual! You're a treasure, my friend! So happy to see you back on xda!
Plus... do you really want me to tell you how we "dirty flashers" flash roms? love you man, you're perfect!
Click to expand...
Click to collapse
Haha no comments... ?
timmaaa said:
NOTE- This is a MUST when changing roms.
1. Backup EFS -Not necessary every time you flash a ROM.
2. Make a nandroid backup in recovery -Not necessary every time you flash a ROM.
3. Wipe data/factory reset
4. Wipe system
5. Wipe cache
6. Wipe dalvik
7. Flash ROM
8. Flash gapps
9. Flash AK kernel(optional) -There are many kernels available for our device, not just AK.
10. Reboot
11. Wait 10 mins, then do another reboot -Not necessary.
12. Enjoy
Transmitted via Bacon
Click to expand...
Click to collapse
Did you read the first few sentence of the OP? Like I said it's a WIP and I need to edit stuff.
But after seeing your edits, the only thing I agree I need to edit out is doing an EFS backup every time you flash a rom. Nandroid is a must IMO, you never know when you'll be unlucky.
As for the "there are many kernels avaliable".. It says optional next to it for a reason.
And about waiting 10 after a rom/kernel and rebooting not being necessary, from my experience it helps let the rom/kernel settle. There was a time when devs used to recommend that. I still do that and recommend it.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Khizar said:
Haha no comments... ?
Did you read the first few sentence of the OP? Like I said it's a WIP and I need to edit stuff.
But after seeing your edits, the only thing I agree I need to edit out is doing an EFS backup every time you flash a rom. Nandroid is a must IMO, you never know when you'll be unlucky.
As for the "there are many men kernels avaliable".. It says optional next to it for a reason.
And about waiting 10 after a rom/kernel and rebooting not being necessary, from my experience it helps let the rom/kernel settle. There was a time when devs used to recommend that. I still do that and recommend.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Click to expand...
Click to collapse
Yeah I did read it and that's why I was putting forth my constructive criticism. The nandroid isn't an absolute must every time you flash though, if you have at least one nandroid on your phone at all times you have insurance against the unknown, whether or not you do that with every flash is purely optional (as opposed to describing it as essential, because it just isn't).
There's a reason devs don't recommend to reboot a second time after a ROM flash anymore, because it isn't essential either.
I only mentioned the kernel because it might seen as favouritism, and it's always best to remain objective in a guide thread.
I'm detecting animosity in your reply. Don't get me wrong, I'm all for having resources, I'm about to add your thread to my index thread so folks can find it easier. I'm just pointing out things that aren't actually essential every time a ROM is flashed, trying to save the user unnecessary time and effort.
Transmitted via Bacon
---------- Post added at 07:45 PM ---------- Previous post was at 07:38 PM ----------
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
timmaaa said:
Yeah I did read it and that's why I was putting forth my constructive criticism. The nandroid isn't an absolute must every time you flash though, if you have at least one nandroid on your phone at all times you have insurance against the unknown, whether or not you do that with every flash is purely optional (as opposed to describing it as essential, because it just isn't).
OK. I agree with this, I'll change it to optional and have a bold warning that you should have atleast one nandroid just in case at all times.
There's a reason devs don't recommend to reboot a second time after a ROM flash anymore, because it isn't essential either.
OK this one I am kinda biased about, have had the same discussion with many others. I've always experienced that if I use a rom/kernel right after I flash everything is a bit laggy. If I wait 10 mins and reboot, everything is a lot smoother.
I only mentioned the kernel because it might seen as favouritism, and it's always best to remain objective in a guide thread.
Hmm.. You do have a point, I'll edit that bit.
I'm detecting animosity in your reply. Don't get me wrong, I'm all for having resources, I'm about to add your thread to my index thread so folks can find it easier. I'm just pointing out things that aren't actually essential every time a ROM is flashed, trying to save the user unnecessary time and effort.
Feedback is always welcome. I appreciate you taking the time and commenting here.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks for adding the thread to the index. :good:
Khizar said:
Thanks for adding the thread to the index. :good:
Click to expand...
Click to collapse
No worries mate. All good, and well done on the thread!
Transmitted via Bacon
Khizar said:
Yeah let's hope ppl actually read and my time editing see stuff to make it for OPO isn't wasted.. These forums seem to be worse than the note 3 ones.. Man saw this guy today who apparently couldn't find the link to gapps that was posted in the OP.. SMH
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Click to expand...
Click to collapse
CafeKampuchia said:
While this is true, it's because people are too lazy to use the search feature or at least look at the stickies. But the information is out there already.
[GUIDES][Q&A]How-To Guides For Beginners + Q&A
Click to expand...
Click to collapse
Nice job and I agree it was getting a little crazy in here as well with the how do I flash this rom crap. I thought this was self explanatory but it seems to be a lot of first timers in here.
I know you said your instructions are a WIP but simply remember when you are ready to put out the finished product you must think as they do the super duper noobs and try and make it as flashing for dummies as possible. They will hold on to your every letter.
I agree that a recent nandroid is needed and honestly I keep 2 at least on my phone because I have been burnt with a corrupted backup before. Also who wants to restore a rom from 2 months ago.... :good:
Nice work
If I may I would like to make some suggestions ??? may I? And no... not as a dirty flasher... if is OK with you, I will...
playya said:
Nice job and I agree it was getting a little crazy in here as well with the how do I flash this rom crap. I thought this was self explanatory but it seems to be a lot of first timers in here.
I know you said your instructions are a WIP but simply remember when you are ready to put out the finished product you must think as they do the super duper noobs and try and make it as flashing for dummies as possible. They will hold on to your every letter.
I agree that a recent nandroid is needed and honestly I keep 2 at least on my phone because I have been burnt with a corrupted backup before. Also who wants to restore a rom from 2 months ago.... :good:
Nice work
Click to expand...
Click to collapse
Yes I think I'll try to make it simpler and more easier for new users to understand, a dummy proof version as you said. Thanks for your feedback.
daxgirl said:
If I may I would like to make some suggestions ??? may I? And no... not as a dirty flasher... if is OK with you, I will...
Click to expand...
Click to collapse
Since when have you needed to ask for permission Anna..? Anyways all suggestions are welcome.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Khizar said:
Yes I think I'll try to make it simpler and more easier for new users to understand, a dummy proof version as you said. Thanks for your feedback.
Since when have you needed to ask for permission Anna..? Anyways all suggestions are welcome.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Click to expand...
Click to collapse
Well we already know that I am a polite non xda material
Sooooooo here we go...
1. When you wipe data in any recovery, it includes AT LEAST 3 things: a. Format data partition b. Eliminate dalvik exec files along with that (since dalvik cache sits on data partition) c. Format cache
So after wiping data, there is not reason to wipe cache and dalvik cache, since they have already been cleaned as a whistle.
2. During rom installation, new framework jars are being pushed over /system/framework. It's enough for just android.policy.jar to be replaced, the android will rebuild all dalvik upon boot (hence the "Android is upgrading. Optimizing xx app out of xxx"). All the major jars upon replacement will wipe dalvik and rebuild it. It's enough to have 1 byte of difference.
So I guess that summorizes the need for wiping dalvik cache.
3. As for wiping system. Well things are a bit more controversial here. Since any normal rom updater script has as first command "mount /system" and as second command "delete recursive /system", it seems like there is no need as well. BUT!!!
There seems to be a discussion whether formatting system (which is done when it's unmounted) the way recovery does it in "mounts and storage " is more "thorough and effective" then recursively deleting it (when it's mounted) by the updater script.
So I can see the point in formatting system! Well, a little...
Hey, don't get me wrong, I admire this guide and I think it's super helpful! I just always feel the need to set things straight with this "triple wipe" that everyone keeps recommending.
Imo, wipe data is simply enough that is IF you're not a dirty flasher. ..
Now to the last part! You guys all have pretty uh the same sqlite vs in all those aosp/cm/aokp roms.
All I am saying: sometimes you can try to flash without wipe, if there is a problem, which in most cases there won't be, some individual data/data databases can be deleted and rebuilt. Maybe we should write a guide on dirty flashing I am certainly good at THAT
daxgirl said:
Well we already know that I am a polite non xda material
Sooooooo here we go...
1. When you wipe data in any recovery, it includes AT LEAST 3 things: a. Format data partition b. Eliminate dalvik exec files along with that (since dalvik cache sits on data partition) c. Format cache
So after wiping data, there is not reason to wipe cache and dalvik cache, since they have already been cleaned as a whistle.
2. During rom installation, new framework jars are being pushed over /system/framework. It's enough for just android.policy.jar to be replaced, the android will rebuild all dalvik upon boot (hence the "Android is upgrading. Optimizing xx app out of xxx"). All the major jars upon replacement will wipe dalvik and rebuild it. It's enough to have 1 byte of difference.
So I guess that summorizes the need for wiping dalvik cache.
3. As for wiping system. Well things are a bit more controversial here. Since any normal rom updater script has as first command "mount /system" and as second command "delete recursive /system", it seems like there is no need as well. BUT!!!
There seems to be a discussion whether formatting system (which is done when it's unmounted) the way recovery does it in "mounts and storage " is more "thorough and effective" then recursively deleting it (when it's mounted) by the updater script.
So I can see the point in formatting system! Well, a little...
Hey, don't get me wrong, I admire this guide and I think it's super helpful! I just always feel the need to set things straight with this "triple wipe" that everyone keeps recommending.
Imo, wipe data is simply enough that is IF you're not a dirty flasher. ..
Now to the last part! You guys all have pretty uh the same sqlite vs in all those aosp/cm/aokp roms.
All I am saying: sometimes you can try to flash without wipe, if there is a problem, which in most cases there won't be, some individual data/data databases can be deleted and rebuilt. Maybe we should write a guide on dirty flashing I am certainly good at THAT
Click to expand...
Click to collapse
1. I get what you're saying with the wiping being a little excessive, again this comes down to experience. My guide is made from what I have personally experienced.
Factory reset does wipe cache and dalvik but I am a believer in "better safe than sorry". Same thing with wiping system even though, like you said, most updater scripts wipe system. Also the bigger reason WHY I am firm in saying atleast wipe data and system is cuz I have noticed in sometimes that when I wipe system as opposed to only wiping data, the experience is better so I have come to the conclusion that the recoveries manual wiping options are to be trusted more.
2. You're right about the dirty flashing, you'll be happy to hear I've been flashing dirty since I got the phone. Now dirty flashing different roms is a bit tricky but I have had success, however even if it gets messy I always have a backup.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Khizar said:
9. Wait 10 mins, then do another reboot
Click to expand...
Click to collapse
I can not understand this step? After the first reboot the new OS booted UP, you must set in and installing the Google APPS update if it available. After the first bootup, why should the users rebooting the device?
Criton30 said:
I can not understand this step? After the first reboot the new OS booted UP, you must set in and installing the Google APPS update if it available. After the first bootup, why should the users rebooting the device?
Click to expand...
Click to collapse
After the first boot up, Java has to create it's working areas for the OS to function well, and it configures the kernel and miscellaneous trash handling (if dirty flashed). Rebooting will clear the supposedly terminates "completed services" after they were used to configure Android on first boot, hence things like kernel will be set on next boot, and on the next boot, you will have a clean Daily Driver configuration.
Also, it's like "why do you reboot your computer after a new install of a big program?", well, for it to settle, and to reinitiate the program. In this case, Android was setting up all your working directories on your internal storage, clearing out junk it may have had, and also rebuilding of the VM. That's a lot of work. Why not reboot to make sure everything that has been sitting on idle after making all these folders, would be terminated completely so just to make sure everything goes right.
nicholaschum said:
After the first boot up, Java has to create it's working areas for the OS to function well, and it configures the kernel and miscellaneous trash handling (if dirty flashed). Rebooting will clear the supposedly terminates "completed services" after they were used to configure Android on first boot, hence things like kernel will be set on next boot, and on the next boot, you will have a clean Daily Driver configuration.
Also, it's like "why do you reboot your computer after a new install of a big program?", well, for it to settle, and to reinitiate the program. In this case, Android was setting up all your working directories on your internal storage, clearing out junk it may have had, and also rebuilding of the VM. That's a lot of work. Why not reboot to make sure everything that has been sitting on idle after making all these folders, would be terminated completely so just to make sure everything goes right.
Click to expand...
Click to collapse
so if I understand you correctyl, after the first bootup after the OS installation I must reboot the phone before setting up the google account and soo on?