Related
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
OK, the CM7 ROM for the Samsung Galaxy S i9000 has now hit the CM7 Mainstream and has matured in leaps and bounds over the last few weeks. The installation method has therefore ALSO matured by leaps and bounds.
However, there has been a downside to all that advancement...namely that there are lots and lots of incorrect install procedures floating around out there and even more misunderstandings as to what/how/when/why you install CM7 on your SGS i9000.
Therefore, this is intended to be the definitive guide about how to install CyanogenMod 7 (or CyanogenMod 7.1 if you are a stickler for such things since that is the most recent stable version but for the purposes of this guide it is STILL CM7) on the i9000 right here, right NOW. As things change, the first post of this thread will be updated.
If you have any questions/comments about the CM7 install procedure, post them here.
If you have any questions/comments about CM7's features, capabilities, battery life or anything OTHER THAN installing it...look HERE or HERE.
Before we do anything....make sure of the following:
* Your phone is fully charged.
* You have confirmed you can get into download/recovery with the three button method.
* You have used Titanium Backup to backup your apps (yes, there may be some factory defaulting happening soon).
* You have taken a Nandroid backup via Clockwork Mod, just in case the early steps go south.
* You have used a third party program to back up your SMS messages (if so desired)
* You have made your peace with your loved ones and said all your goodbyes...maybe left a nice note or something.
Remember, this will be one of the most harrowing, horrific experiences of your life. Grown men have been known to gnaw off their own legs during this procedure, unable to face the deepening horror their feeble minds cannot hope to comprehend.
Are you SURE you want to install CM7?
Very, VERY SURE?
OK, its your funeral, I am just here for the open bar.
OK, here we go....
FIRST STEP!!!!! THE PRE-INSTALLATION TANGO!!!!
Boy are you lucky to be doing this now. Recently CM7 was improved so that it works just fine with either Froyo or Gingerbread Bootloaders. It used to be that when you installed CM7 with Gingerbread bootloaders, a puppy died in agony. Now, the cuddly little puppies are safe thanks to the hard work of the CM7 Devs.
However, if for some strange reason you have still have Eclair installed currently, smash your head repeatedly against a wall for being such a stinking Luddite. Once you wake up, update to Froyo or Gingerbread and then come back and start this again. Plenty of threads on XDA will help you do that. Go read one and flash froyo or gingerbread via ODIN, we'll wait right here with the car running.
Don't know how to use ODIN? Not sure about all those little checkboxes? Befuddled by those driver thingies? Unsure how to click on the links above while using a Commodore64? Well, we won't wait in the car THAT long. If this is the case then you absolutely shouldn't be flashing CM7 yet my poor lost child, educate yourself for awhile and then come back, or just buy a used iPhone.
OK, still with me? ONWARDS.
SECOND STEP!!!!! THE NITTY GRITTY DETAILS, AKA THE CALM BEFORE THE STORM!!!!!
Here is the point where you need to do all sorts of things that you may have already done.
If you have already done them, GOOD, you are very, very clever and ahead of the game. Give yourself a gold star.
If you don't know how to do any of these things, then you shouldn't be here yet. Go search for things you don't understand in the general and Q&A forums for the i9000 and when you feel you are better grounded in the arcane mysteries of flashing custom ROMS, come back and we will have a joyous reunion and try this again.
OK, so what do you do in STEP TWO?
* Doublecheck that you can indeed get into Download Mode using Vol Down+PWR+Home, and into Recovery with Vol Up+PWR+Home. If not, go away and search XDA for a way to fix that.
* Root your phone.
* Confirm you have Clockwork Mod recovery running. If not, use Odin to flash this Speedmod kernel if you are on Froyo. If you are on Gingerbread flash the TalonDev kernel using the v2.2 tar (yes I know the TalonDev kernel has lagfix automatically enabled, but as your file system will be grabbed and ripped out still beating and then replaced with a better one by the CM7 Installer, it really doesn't matter). There are two different versions of the v2.2 tar available but don't panic. Use TalonDEV-0.2.2R2-I9000-1200-JVP.tar first...if that doesn't work for you, try TalonDEV-0.2.2R2-I9000-JVP.tar. One of the two should work for you. (Thanks to chan1628 for testing them the hard way)
* Install ROM Manager (I STRONGLY suggest you buy the Premium version if possible to make flashing Nightlies easier. It is quite cheap with a lot of great features and is one of the core apps you will use on your phone from here on in...plus Koush deserves your support).
* Take another nandroid backup (even if you took one already) and confirm your Titanium Backup is up to date (and includes a backup of ROM Manager).
* Confirm that you are rooted.
* Backup your contacts to either Exchange, Gmail or your SIM card.
* Write down your correct APNs and your IMEI, just in case.
* Take a backup of your efs folder and save it somewhere.
* Post a note on your monitor reminding yourself to breathe.
* Say goodbye to your Samsung apps like Snap2Go and Daily Briefing, they won't work with CM7.
* Pour yourself a stiff drink
Confused? Not sure how to root your phone or worried about voiding your warranty? Really curious about what these APN things and where can you find them? Hoping to sync your phone with iTunes once CM7 is installed? Then go away, do some searching, get up to speed and I will see you later. I mean it...avaunt ye. Scram. Exeunt with all due alacrity. Happy reading.
Also, if you are getting errors concerning CWM, or cannot get into CWM3 Recovery, then search XDA (or the comments to this thread) for a solution. I cannot help you. I am not an expert on Clockwork Mod, I am just here to get CM7 running for you, or kill you and steal your girlfriend in the attempt. Clockwork Mod is YOUR lookout.
Still here? Did all that? CWM Recovery working properly? Crossed all your i's and dotted your t's? Forward then. Things get REALLY BAD from here on in. Whatever happens next, I am truly, truly sorry.
THIRD STEP!!!!!! THE COMPLEX, AGONIZING EXPERIENCE OF FLASHING THE ROM ITSELF!!!
Are you sure you are ready for this? Are you quite, QUITE sure?
It is not too late to turn back....and if you do no one will think less of you. I promise.
Positive you are where you want to be?
Brave, brave darling. Take my hand and lets do this then....there are two possible methods to use now that you are at the Third Step..Method the First uses the ROM Manager and is by far the simpler of the two. However if the ROM Manager doesn't work for you or if you have a sudden premonition of flaming disaster about it....don't cry. Man up and go to the manual method listed after Method the First, known quite coincidentally as Method the Second.
Method the First!
Open ROM Manager from your App Drawer.
Select Flash ClockworkMod Recovery.
When it asks you what phone you are using, scroll down until you find Galaxy S MTD and select it (Galaxy S is what CM7 calls the i9000 series...CM7 is weird that way).
When it asks what version to use, select CMW3.
By the way, if ROM Manager tries to argue with you during this process, or tells you your phone may not be supported, ignore it and click OK or Continue or whatever it takes. It just worries over what you may be about to do to yourself.
Confirm that under Flash ClockworkMod Recovery it now reads Current Recovery: ClockworkMod 3.x.x.x. This means that now you should be able to see CyanogenMod zips and nightlies (if you have ROM Manager Premium) in ROM Manager. Hoorah!
Now, the moment of truth arrives...select Download ROM.
Next close your little eyes tightly and select CyanogenMod or CyanogenMod Nightlies (if you see that one). Either one will do.
Down the road, you will use the CyanogenMod Nightlies files to update...assuming you survive the next 15 minutes. However when installing you can use the single file in the CyanogenMod folder (there for Free users) or the latest Nightly in the CyanogenMod Nightlies folder...same difference.
So click the file of your choice and stand back...well, not too far back because there is more stuff you have to do.
If/when you are asked if you wish to reinstall Google Apps, it is highly recommended that you do so, so check the little box. This saves many headaches and potential fc's down the line.
When you are asked what you wish to do to prepare for the new ROM, you can choose to do another Nandroid Backup, Clear Data and Cache (wiping the device) and/or Clear the Data Cache. No need for another Nandroid backup, but select the other two and hit OK.
Now let the ROM Manager make some magic. It will take a couple minutes but likely not nearly as long as you expect, so go out and make tea or paint the Sistine Chapel or something.
While you are gone your device will do all the wiping and installing, back up your efs folder and apply the new file system you will need. You will NOT need to apply any lagfix or mess about with tweaks or whatnot....CM7 does it all for you and no other options are possible....so don't ask.
Method the Second!
If for whatever reason you are having trouble working with ROM Manager in the previous method and are therefore stuck, you can do the following to flash CM7 manually.....but if you have a weak heart or tend to get squeamish...I implore you to look away.
Download this most recent version of CM7 from http://download.cyanogenmod.com/?type=nightly&device=galaxysmtd
Then download the most recent set of Google Apps from http://goo-inside.me/gapps
Place both on your SD card.
Go into Recovery using the handy-dandy Three Button Skidoo (NOT by using the command "Reboot to Recovery" found in ROM Manager...you have been warned).
Do a Factory Reset (wiping data so if you forgot to backup your apps before....whoops)
Wipe the Dalvik and Cache (just in case).
Select Install Zip from SD Card and flash first the CM7 zip, and then the gapps zip. No need to reboot in between. Finally fix permissions.
NOTE: If you are one of those people who have done some research and have also downloaded one of the CM7 custom kernels which you wish to flash as part of your install (if you haven't don't worry about it, I don't recommend using a custom kernel before you have spent some time with the stock kernel, but some people think they are 1337)...make certain you flash the Nightly BEFORE the custom kernel, otherwise you will totally confuse the installer and very bad things will happen which will require you to flash back to a Samsung ROM using ODIN and start all over again.
Once everything has completed, THEN reboot into CM7 (HOO-RAH) and continue to the Fourth Step. Hurry, hurry, scroll back up....
GO!!!
Oh, WAIT A MINUTE....When you have done all the stuff in the Fourth Step, do this too...go to ROM Manager, and select Flash ClockworkMod Recovery. ID your phone as Galaxy S MTD when it asks and select CWM3...it will tell you that your phone is not supported or some such but have it install it anyway. What the heck does it know. Doing so will ensure you can find your the Nightly updates using ROM Manager Premium in the future.
OK, now go on to the Fourth Step...really this time...
GO! GO!
FOURTH STEP!!!!! STEP OUT INTO THE LIGHT AND BREATHE THE FREE AIR
That's it, you are done. Throw back that drink now...or if you don't want it, I'll take it.
Your phone will show the CM7 SGS splash screen for a bit, then the CM7 boot animation for a while longer (spin, spin, spin)...and then you will be in CyanogenMod 7.
If you find that the boot animation never seems to end, or keeps restarting...DON'T PANIC. This happens to some people when flashing CM7 for the first time. Just go to recovery and flash the Nightly again, you should be fine. If you used ROM Manager the first time, the nightly will be in the ROM Manager folder on your SD card.
Where is all the pain, the agony, the brain bending complexity reducing scholars to madness that I warned you about?
OK, I lied...but I had to make sure you were serious.
Now restore your apps (remember that is best to do fresh from the Market, but if you use TB then be sure to reinstall just the APP, not APP + DATA, and NO SYSTEM APPS) and put all your contacts and email addresses back and so on.
Also, remember that your external SD card is now located in the /emmc directory. Why? Because that is how it is in CM7, so cope. It really is NOT that tough to get used to. However, if you want to have some kicks, go into the CM7 Dev thread and ask where your external_sd card has gone a few times to watch people go berzerk yelling at you. Fun, fun, fun.
From here on in, you can install nightly updates to stay on the bleeding edge of CyanogenMod, as well as to allow yourself to experience the terror of waiting for that boot animation to stop again and again and again. You can look at the Nightly Wiki for instructions on different flashing strategies.
You may also install custom kernels and alternate modems via Recovery if you wish, but be sure that they are CM7 compatible. The ones you used back on Samsung ROMs won't work for you any more.
Carry on, and enjoy your new ROM.
As always, if this procedure bricked anything or gave your dog syphilis, it isn't my fault. By God, I WARNED you. If you liked it, or it worked out well for you, feel free to click Thanks and heap praise in the comments.
Finally, all due honour and thanks to the incredible Devs and Maintainers of TeamHacksung and the SGSTEAM listed below. Find their profiles and donate to them, they have earned it.
* codeworkx - http://twitter.com/codeworkx
* atinm - http://twitter.com/atinm
* coolya - http://twitter.com/coolya
Great guide, just want to make a quick addition...
rschenck said:
OK, so what do you do in STEP TWO?
* Root your phone.
* Confirm you have Clockwork Mod recovery running. If not, flash the Speedmod kernel.
Click to expand...
Click to collapse
I couldn't complete this step during my exciting first install of CM7
If anyone has trouble getting Clockworkmod Recovery running, and you can't manage to flash a new kernel using Odin/heimdall please read:
[RECOVERY] 3e Recovery Modded w/ No Verification
I just skimmed through it but wouldn't this require you to buy rom manager premium?
runedrune said:
I just skimmed through it but wouldn't this require you to buy rom manager premium?
Click to expand...
Click to collapse
No. The premium version is only required to download nightlies directly through the app. Download them manually, then point rom manager at the zip on your sdcard & install.
Yay! First thanker! Nice guide too.
runedrune said:
I just skimmed through it but wouldn't this require you to buy rom manager premium?
Click to expand...
Click to collapse
Not the install, that is free as far as I know. Installing nightlies via ROM Manager needs Premium. Plus I suggested people buy Premium anyway.
sambwel said:
No. The premium version is only required to download nightlies directly through the app. Download them manually, then point rom manager at the zip on your sdcard & install.
Click to expand...
Click to collapse
Exactly. The instructions tell you to use rom manager to download CM7. Just thinking that http://download.cyanogenmod.com/?device=galaxysmtd should be included too for those that can't buy rom manager.
But anyway great guide rschenck. Hopefully it'll save us from unnecessary questions.
runedrune said:
I just skimmed through it but wouldn't this require you to buy rom manager premium?
Click to expand...
Click to collapse
Yepp true story!
IF you want to download roms and stuff from Rom manager you do have to have premium.
I have no plans to install yet (still waiting for the stable release) but really this guide has no boring part. Very informative and easy to follow. Just wanna say thanks for this guide. KUDOS!
Nice tutorial man. I want to instal cm7 and this tutorial is very helpfull. Hope this topic get sticky :d
upgrading to latest
just to clarify, I'm (thanks to you!) on v11 due to some people suggesting me that version over v14. After reading some I would like to flash the new experimental build (v15?) in order to do so I:
1) charge it up
2) do a nandroid backup /done
3) wipe data/factory reset + wipe cache in CMW /not sure about this, I've read some diferent post about what to wipe. Some said that when upgrading only cache + dalvik will do just fine. This is the main issue.
4) flash the v15 (update-cm-7-05282011-NIGHTLY-GalaxyS-signed.zip) through CMW
+ all that other stuff like preparing myself for long agonizing experience and stuff
thanks in advance!
James.q said:
just to clarify, I'm (thanks to you!) on v11 due to some people suggesting me that version over v14. After reading some I would like to flash the new experimental build (v15?) in order to do so I:
1) charge it up
2) do a nandroid backup /done
3) wipe data/factory reset + wipe cache in CMW /not sure about this, I've read some diferent post about what to wipe. Some said that when upgrading only cache + dalvik will do just fine. This is the main issue.
4) flash the v15 (update-cm-7-05282011-NIGHTLY-GalaxyS-signed.zip) through CMW
+ all that other stuff like preparing myself for long agonizing experience and stuff
thanks in advance!
Click to expand...
Click to collapse
You are quite correct...when upgrading all you need to do is wipe dalvik cache. You can also take a nandroid backup if you wish to be extra careful but there is no need to wipe data for an upgrade.
Sent from my GT-I9000 using XDA Premium App
rschenck said:
You are quite correct...when upgrading all you need to do is wipe dalvik cache. You can also take a nandroid backup if you wish to be extra careful but there is no need to wipe data for an upgrade.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
thanks! .. so is it just wipe cache or both wipe cache + wipe dalvik cache in advanced menu? I get confused with that
James.q said:
thanks! .. so is it just wipe cache or both wipe cache + wipe dalvik cache in advanced menu? I get confused with that
Click to expand...
Click to collapse
Wipe cache is in the main cwm menu, wipe dalvik is in advanced...and you can wipe them both.
Sent from my GT-I9000 using XDA Premium App
Thanks mate, you made my day! I haven't laughed so hard in a while ...
James.q said:
thanks! .. so is it just wipe cache or both wipe cache + wipe dalvik cache in advanced menu? I get confused with that
Click to expand...
Click to collapse
Yes, you should do both
A few small edits and clarifications added...
Good job on this guide.
You kids gave it easy. Back in my day, we had to flash our phones in Morse code.
Sent via XDA Premium app on my GT-I9000 running CM7 (GB 2.3.4)
bump...and if anyone who has used this guide has feedback or suggestions, please comment with them.
How come when i go to download rom i cannot see cyanogen mod there?
I did buy the rom manager
Here's what you need to do!!
First, make a NANDROID BACKUP of your stock, rooted setup.
TRUST ME on this, you'll use it to do things like GPS fixes, PRL updates etc.
Use Amon Ra. DON'T use ROM Manger. Backup everything except Cache.
On that Nandroid you'll want Titanium Back Up, GPS Status and updated Maps installed.
For ROMS, if it were me, and I knew what I did now, I would start with the Sense ROMS, since you're used to that, just to see what a GOOD Sense ROM feels like.
Always wipe everything in Amon Ra, except the SD Card itself (Although people will argue with me that it's not necessary). Trust me on this, too, ok?? Just do a full wipe and erase any doubts when you have issues that it was wipe related.
Then, once you realize that Sense is boring, give CM 7 a shot, or better yet, MIUI!
AND READ READ READ READ READ as much as you can before you do dumb things.
And conratz!! It's about time!
Exactly what i was looking for, thanks! :]
Thanks! I was looking for this as well, in the process of creating a complete backup with amon ra. Was kinda wondering what I should flash tho, sense bores me
I've had them all, and I'm locked in MIUI now
So you're saying backup the following?
Boot
System
Data
Recovery
Wimax
Sd-ext
.andriod-secure
that's everything but cache - why not cache?
Also, what's a good rom if Battery life is most important... one that undervolts?
Cache is just temp files. You don't need them, but everything else, yes.
You only need boot data system and Wimax. I reccomend using a format all zip between rom flashes.
Sent from my PC36100 using XDA Premium App
What do you recommend for backing up SMS?
I entered my beta key and I'm stuck at zerging root....
its been around 5 minutes.
gab2012 said:
I entered my beta key and I'm stuck at zerging root....
its been around 5 minutes.
Click to expand...
Click to collapse
This thread isn't the place for help rooting. Plenty of others, or post in Q&A.
Key thing is to backup, at least, your WIMAX. It's almost impossible to lose your WIMAX partition anymore, but better be safe than sorry.
You could nandroid everything.. but it's kind of pointless. There are RUUs out to flash back to stock, and zips you can flash too. Mainly just ease of use since the nandroid will already be on your SDcard.
Also as hipkat says, do yourself a favor and don't use ROM Manager. Don't use CWM recovery either (well, it's up to you but it's pretty old now). Amon_RA is the mature stable recovery, and the TeamWin recovery is the new kid on the block... functional but not as robust yet.
Sorry about that lad, and yeah I will backup everything if I can get the damn thing to work
It looks like quite a few people are having issues. Just hang tight and see if there is a fix.
Also check the guide over in the development section to make sure you got the step %100.
Well, I just got it!, uninstalled HTC sync and drivers, reinstalled the HTC drivers and ran the .exe zerging root passed!
Said no to Clockwork and installed Amon RA from fastboot, then flashed SU and now I'm ready to backup
dsotm82 said:
What do you recommend for backing up SMS?
Click to expand...
Click to collapse
I use SMS Backup and Restore by Ritesh Sahu from the market. Haven't had any problems so far.
HipKat said:
Here's what you need to do!!
First, make a NANDROID BACKUP of your stock, rooted setup.
TRUST ME on this, you'll use it to do things like GPS fixes, PRL updates etc.
Use Amon Ra. DON'T use ROM Manger. Backup everything except Cache.
On that Nandroid you'll want Titanium Back Up, GPS Status and updated Maps installed.
For ROMS, if it were me, and I knew what I did now, I would start with the Sense ROMS, since you're used to that, just to see what a GOOD Sense ROM feels like.
Always wipe everything in Amon Ra, except the SD Card itself (Although people will argue with me that it's not necessary). Trust me on this, too, ok?? Just do a full wipe and erase any doubts when you have issues that it was wipe related.
Then, once you realize that Sense is boring, give CM 7 a shot, or better yet, MIUI!
AND READ READ READ READ READ as much as you can before you do dumb things.
And conratz!! It's about time!
Click to expand...
Click to collapse
+1 - I would recommend getting Root Explorer and flashing a kernel to help extend the battery. You may also look into WIFI Tether
Thanks for this defiantly useful...time to start flashing
Thanks for the reminder, I am new to rooting this phone. (Not new to rooting, had HTC phones from G1 and MT3G, in those I am GTG.) Installed CM7 latest one. But I am interested in MIUI ones and the videos looks awesome!!!
MIUI has come a long way form when I tried it a few months ago...
Sick. Thanks for the heads up. Also, I appreciate the To-Do List. This is my first venture into rooting, so as you can imagine, it all seems a bit overwhelming at first.
Sent from my PC36100 using XDA App
Rvinfinite said:
Sick. Thanks for the heads up. Also, I appreciate the To-Do List. This is my first venture into rooting, so as you can imagine, it all seems a bit overwhelming at first.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
NP! That's why I'm here!
Im not rich or I would have got a newer version tablet by now, but if anyone who helps has a donate button I have no issue donating a couple dollars to the person who helps me get this done, Thanks. Or just a couple dollar PP gift. better than nothing I guess.
I just want to be sure I dont mess anything up here. I have a nexus 7 wifi model.
I used NRT to unlock and root and all seems fine. Am I correct in this:
I use nandroid backup to backup first
Put ROM file on device (where do I put it?)
Wipe (is this done via nexus root toolkit or is ok do do in the custom recovery?)
Then what, boot into recovery and find the ROM and install it via recovery install button?
Then do I do the same with a kernal? Where do I put it?
Then done?
I know there are guides around but for a complete newbie I need to be sure cause I dont always see a complete fully explained step by step. Just like when I was stock not getting SU to work after rooting via nrt, I did read to flash SuperSU.zip, but had no idea how, then when I found the file and thought maybe install from recovery meant same as flash, I didnt know the message about messing the device up was normal so I was afraid at first.
THANKS to any replies,
Been unsure for days now trying to make sure my ducks are in a row before i commit to a ROM/Kernal. I want to CPU control for both under and overclocking etc. Mainly overclock just a little. I must say I love root already, got stuff to work I couldn't before
1. Create nandroid- there's a free app called something like nandroid on line - very simple to use
1a. I'd also recommend backing up with titanium backup app. It means you can keep your app data (e.g. game progress) when switching between ROMs, unlike a nandroid which is just a backup of your device as a restorable image
2. Put ROM file on device - ROM will be a .zip file, out it wherever you want, as long as you remember where it is
3. Put kernel anywhere on device - easiest to find a kernel with .zip format (recommend M-kernel)
4. Wipe - from custom recovery
5. Hit install in your custom recovery, I always flash kernel and then ROM, but I don't think it really matters
Install from recovery and flash are the same thing.
I'd recommend only flashing ROM or kernel and sticking with that set up for a few days, then flashing the other desired element. That way, if anything goes wrong then it's easier to pinpoint.
Good luck!!
Sent from my HTC Desire C using xda app-developers app
THANKS! Don't see a donate button, did you want anything?
No, of course not! God luck!
Sent from my Nexus 7 using xda app-developers app
butler0607 said:
5. Hit install in your custom recovery, I always flash kernel and then ROM, but I don't think it really matters
Click to expand...
Click to collapse
Actually that completely matters. Flashing a kernel before rom is worthless because the rom contains a kernel that will replace whatever you have just flashed.
If you want to run a custom kernel on a rom it is recommended to boot into the rom first before flashing the kernel.
Pirateghost said:
Actually that completely matters. Flashing a kernel before rom is worthless because the rom contains a kernel that will replace whatever you have just flashed.
If you want to run a custom kernel on a rom it is recommended to boot into the rom first before flashing the kernel.
Click to expand...
Click to collapse
If I just want root access and overclock should i just flash kernal and forget a rom?
can i revert back to stock kernal if need to? ask cause need to find a kernal that has V4L enabled for a usb camera app i use currently to use an inspection camera via usb on my tablet. I guess i need to read what various roms and kernals add. do i need to do both. Hard to know what to pick out of them, lol.
Thanks for advice.
Anyone know of a list to show ROMs with V4L enabled? None seem to mention it?
I have read and see different suggestions around on various sites. What all do I wipe? I have read cache, dalvik cache, plus other stuff. What all must I wipe before flashing a rom or kernel? I did a nandroid backup already.
PirateGhost, Ill donate a couple dollars if you help, thanks.
Thanks.
When going from one rom to a different one all you need to do in custom recovery is select factory reset.
This wipes out your currently installed apps, their settings, but doesn't touch your 'sdcard'
Wiping dalvik is pointless as it's automatically handled in the rom process, and cache is wiped in factory reset.
When switching kernels follow the instructions provided by the dev. If no instructions are provided, it's safe to assume you just flash without wiping anything.
When doing this, I'd recommend titanium backup too. When you do a factory reset, all apps are lost, but some data is kept (not sure on the details). Basically Titanium allows you to restore all your apps with data when you change ROMs.
Sent from my Nexus 7 using xda app-developers app
Pirateghost said:
When going from one rom to a different one all you need to do in custom recovery is select factory reset.
This wipes out your currently installed apps, their settings, but doesn't touch your 'sdcard'
Wiping dalvik is pointless as it's automatically handled in the rom process, and cache is wiped in factory reset.
When switching kernels follow the instructions provided by the dev. If no instructions are provided, it's safe to assume you just flash without wiping anything.
Click to expand...
Click to collapse
Thanks! Ill donate a couple dollars later today when I get back from the doctor.
I have not put any customs ROM(s) on yet, so is it the same still? All I have done so far is unlock/root with custom recovery and nandroid backup....
butler0607 said:
When doing this, I'd recommend titanium backup too.
Click to expand...
Click to collapse
Yeah I backed up the one app I needed to via TB, I just recently unlocked and rooted so lost most app data anyway and have only added one back so far. Thanks.
butler0607 said:
When doing this, I'd recommend titanium backup too. When you do a factory reset, all apps are lost, but some data is kept (not sure on the details). Basically Titanium allows you to restore all your apps with data when you change ROMs.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
No data is kept except what's on the sdcard. Mostly only game saves and some basic stuff. Apps databases are wiped during factory reset.
Pirateghost said:
No data is kept except what's on the sdcard. Mostly only game saves and some basic stuff. Apps databases are wiped during factory reset.
Click to expand...
Click to collapse
Thanks, Ill donate a couple bucks. had bad day yesterday so wasn't on much.
Is it normal for the donate link to be missing the regular PayPal security info on the browser?
eBandit078 said:
Is it normal for the donate link to be missing the regular PayPal security info on the browser?
Click to expand...
Click to collapse
I have no idea what this means.
Pirateghost said:
I have no idea what this means.
Click to expand...
Click to collapse
Maybe Ill just do it and change my password when finished. Thanks. Sorry not replied yet have been in a lot of pain Only a couple dollars but better than nothing I guess. Thanks for your help. Ill be back online tonight to do it.
eBandit078 said:
Maybe Ill just do it and change my password when finished. Thanks. Sorry not replied yet have been in a lot of pain Only a couple dollars but better than nothing I guess. Thanks for your help. Ill be back online tonight to do it.
Click to expand...
Click to collapse
Not forgot about you, had family issues, holiday etc, well did forget but I'll look into why it does that and figure it out. Sorry for delay.
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?